[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: gcc and utf-8 source
> I have to use LANG=hu_HU instead... I can't understand why the hu_HU.UTF-8
> locale consumes much more disk space than the hu_HU locale,
That's easy to see why
damjan:/usr/lib/locale$ d -lh mk_MK.utf8/LC_COLLATE mk_MK/LC_COLLATE
-rw-r--r-- 80 root root 862K 2004-05-25 06:34 mk_MK.utf8/LC_COLLATE
-rw-r--r-- 2 root root 22K 2004-05-25 06:36 mk_MK/LC_COLLATE
The UTF-8 locale contains rules for collation of maybe most of the
characters in Unicode.
> and actually,why do I need to have both on my system for both to work,
> why can't glibc convert charsets runtime if necessary?
It will add more complexity and certainly more confussion.
> This way I can't even use hu_HU.CP852
> or hu_HU.iso-8859-16 if I'd happen to need them for some strange reason.
You can.. first create the locales:
localedef -f IBM852 -i hu_HU hu_HU.CP852
localedef -f ISO-8859-16 -i hu_HU hu_HU.iso-8859-16
and then use them:
LANG=hu_HU.CP852 date
LANG=hu_HU.iso-8859-16 date
--
damjan | дамјан
This is my jabber ID --> damjan@xxxxxxxxxxxx <-- not my mail address!!!
--
Linux-UTF8: i18n of Linux on all levels
Archive: http://mail.nl.linux.org/linux-utf8/