Re: [Afpfs-ng-devel] precompose and decompose

[Michael U. <mu...@re...>]

HAT wrote:

>>> 3) decompose: sample only
>> There is no decomposition, since the MAC filesystem does the appropriate
>> conversions before writing. I was not aware of any problems related to
>> the missing functionality so far ...
> 
> Yes.
> It is a problem which standard or implementation is important.

Hi,

hmm, I'm not sure what you mean here ...

> How is a table[] in lib/unicode.c generated?

The data is generated from

ftp://ftp.unicode.org/Public/UNIDATA/UnicodeData.txt

taking the values for "canonical decompositions" from column #5.

I've compared this file with

http://www.unicode.org/Public/5.0.0/ucd/UnicodeData.txt

and they are identical. This would IMHO mean that we are up to date at
least with respect to the set of "officially" defined decompositions.

The resulting table was further checked against:

http://developer.apple.com/technotes/tn/tn1150table.html

and decompositions not marked "illegal" in tn1150table were removed from
the result.

Please let me know, if there is a newer version of the unicode
decomposition table for HFS Plus.

> This is not at least based on Unicode 3.2.
> We should discuss which version to adopt.
> I think that we should use the newest version 5.0.0.

Your suggestion (from your first message) to change the internal
character representation in lib/unicode.c from UCS2 to UCS4 absolutely
makes sense, although there are currently no decompositions in the range
> U+010000 used by HFS Plus that I'm aware of.

Of course it is necessary to handle this character range cleanly when
sending the strings through precompose().

Will you be able (and willing ... ;-)  ) to do the rewrite? I might do
it as well, but am not sure when I will find the time to actually do so.

If you have a patch, I will help with the testing, though.

Thanks + Best regards ... Michael