Jon Griffiths jon_p_griffiths@yahoo.com writes:
This patch adds two new conversions to libs/unicode, in preparation for their use by an upcoming patch adding FoldStringA/W. The first converts from any unicode number into its unicode 0-9 representation. The second maps from compatibility characters to unicode.
The rationale for placing them in libs/unicode is that both these conversions may be required by calls other than FoldString (at least the numeric mapping will be used to parse native language digits in oleaut32).
IMO you should export the FoldString functionality from libs/unicode, not the tables. Also I'm not sure how you built the tables, but they need to be generated from the Unicode standard data, and the code to do that should be added to cpmap.pl.
Hi,
--- Alexandre Julliard julliard@winehq.com wrote:
IMO you should export the FoldString functionality from libs/unicode, not the tables.
OK, can do.
they need to be generated from the Unicode standard data, and the code to do that should be added to cpmap.pl.
The data for the numeric conversion is in the Unicode data, but it doesn't match MS's as of XP. The other mappings will no doubt differ slightly too. I take it we don't care?
Cheers, Jon
===== "Don't wait for the seas to part, or messiahs to come; Don't you sit around and waste this chance..." - Live
jon_p_griffiths@yahoo.com
__________________________________ Do you Yahoo!? The New Yahoo! Shopping - with improved product search http://shopping.yahoo.com
Jon Griffiths jon_p_griffiths@yahoo.com writes:
The data for the numeric conversion is in the Unicode data, but it doesn't match MS's as of XP. The other mappings will no doubt differ slightly too. I take it we don't care?
Not really; if an app depends on the difference we can always tweak the generated tables. But we are already using the standard Unicode data for everything so it's better to be coherent.
-
Alexandre Julliard -
Jon Griffiths