Angus Leeming <[EMAIL PROTECTED]> writes:
| Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
| > Georg Baum <[EMAIL PROTECTED]> writes:
|
| > | > Should a call to gettext (_()) give us utf8 or ucs4?, so far I am
| > | > inclined to go for utf8.
| > | If we only knew which variant results in less conversions.
| > Conversion between the different unicode encodings are pretty cheap.
|
| > | Since the po files will eventually be in utf8 it seems natural
| > | to use utf8 for _(), too.
|
| Why? Given that "conversion between the different unicode encodings are
pretty
| cheap", why not have the LyX core use a single UCS4 encoding and require
| conversion only on input/output. Especially given the fact that the frontends
| will have to perform the conversion from UTF-8 to UCS-4 to their encoding of
| choice. That just seems like we're making work for ourselves.
Actually I guess that using a mix of utf-8 and ucs-4 is the cop-out to
have everything work as soon as possible.
A full change to ucs-4 will require more code changes than a mix.
| I just don't get the need/desire for more than one encoding in the kernel.
Come code a bit and you will see all the corners that hit you on the
shinbone.
But sure IMHO we should evetually move towards common internal
encoding all over... except that might not be practical sine all the
external interfaces will need different ones...
donno.
--
Lgb
