Ove Kaaven <[EMAIL PROTECTED]> wrote:
>> I didn't understand yours "it is impossible to have two Unicode chars map
>> to the same ASCII value". Would you say it more popular please?
>
>Example:
>
>002D;HYPHEN-MINUS;Pd;0;ET;;;;;N;;;;;
>00AD;SOFT HYPHEN;Pd;0;ON;;;;;N;;;;;
>2010;HYPHEN;Pd;0;ON;;;;;N;;;;;
>2011;NON-BREAKING HYPHEN;Pd;0;ON;<noBreak> 2010;;;;N;;;;;
>2013;EN DASH;Pd;0;ON;;;;;N;;;;;
>2014;EM DASH;Pd;0;ON;;;;;N;;;;;
>2015;HORIZONTAL BAR;Pd;0;ON;;;;;N;QUOTATION DASH;;;;
>
>These are just SOME of the Unicode chars that may map to the ASCII minus
>sign "-" (0x2d). It is also common to map accentuated chars to their base
>chars, e.g. "S WITH CARON" to a plain "S", when the appropriate character
>does not exist in the codepage.
Thank you. Now I see it. But it means that information from .txt files at
unicode.org should be used for generation CP -> Unicode table only,
and Unicode -> CP table should be generated using something else.
I think at start it will be not so critical to miss some characters,
then it could be quite easy fixed.
>> Now question about process of generation. When to generate files? In the
>> compile time or in process of "make install"? I propose the second one. But
>> due to the latest debates in the newsgroup about install script it seems
>> that not all like to use it.
>
>It has always been possible to run Wine without *needing* to do "make
>install", so why not create them during compilation? Generation is just
>another word for compilation, isn't it?
I thought that "make install" would just add creating and copying of generated
NLS files to the same directory where .so's are copied and adding this feature
is quite simple.
>> And the very important for me:
>> I can write conversion/generation utility, but I am not able to mess with
>> make files and I need help with it.
>
>Makefiles aren't that complicated?
Of course no :-). But time is critical to me, and learning and understanding
make files is time consumable. Plus I think I need some help with them anyway.
Dmitry.
