| 1 |
On Thu, 2003-10-30 at 14:09, Mamoru KOMACHI wrote: |
| 2 |
> > unicode, or utf-8 ? |
| 3 |
> |
| 4 |
> I personally vote for unicode, but if it is going to be enabled by |
| 5 |
> default (i.e. Gentoo support UTF-8 immediately after installation), |
| 6 |
> utf8 seems adequate rather than unicode. I just don't want to add |
| 7 |
> utf7, utf16, utf32 USE flags for each encoding but have unicode USE |
| 8 |
> flag which will support Unicode encodings (if any). |
| 9 |
|
| 10 |
Exactly. "unicode" should denote adding support for UCS-* or UTF-* |
| 11 |
encodings and internal representations. |
| 12 |
|
| 13 |
> > There ought to be some magic to convert locales to utf-8 as well if |
| 14 |
> > this is enabled. |
| 15 |
|
| 16 |
> I'm thinking that it isn't time to make the USE flag default yet |
| 17 |
> (liquidx is working on getting UTF-8 down on Gentoo system). Anyhow, |
| 18 |
> creating unicode/utf8 USE flag and making it default are two different |
| 19 |
> matters and we can discuss them separately. |
| 20 |
|
| 21 |
From my point of view, "unicode" USE flag encompasses UTF-8 support. I |
| 22 |
think they are the essentially the same problem. Think of it this way, |
| 23 |
treating them as separate issues would be like treating iso2022-jp as a |
| 24 |
separate issue to Japanese support. |
| 25 |
|
| 26 |
Anyhow, the generation of UTF-8 locales can be accomplished by a patch |
| 27 |
to glibc which could be applied depending on the unicode USE flag. I've |
| 28 |
got one such patch around, I'll submit a bug to track it in bugzilla |
| 29 |
soon. |
| 30 |
|
| 31 |
Cheers, |
| 32 |
|
| 33 |
-- |
| 34 |
Alastair 'liquidx' Tse |
| 35 |
>> Gentoo Developer |
| 36 |
>> http://www.liquidx.net/ | http://dev.gentoo.org/~liquidx/ |
| 37 |
>> GPG Key : http://dev.gentoo.org/~liquidx/liquidx_gentoo_org.asc |
| 38 |
>> FingerPrint : 579A 9B0E 43E8 0E40 EE93 BB1C 38CE 1C7B 3907 14F6 |
Archives