On Friday 29 November 2002 23:53, Shachar Shemesh wrote:
> As for Debian - yes, they have the same "problem" (i.e. - no problem at
> all), except they ask you which locales you want compiled when you
> install the proper language, and so I didn't have to fool around with
> localedef at all.
Once I wanted to add a feature to KDE which automatically ran localedef to
generate a locale according to your KDE Locale settings (KDE has separate
settings, undependant of libc locales), but then I realized there was no
portable way of generating locales without needing root perms. glibc tries to
look for locales in I18NPATH (so you can set it to point to the user's dir),
but what about AIX? Solaris?...
Then again, I wonder why it's so expensive that glibc cannot compose those
locales on-the-fly?
> One thing, though. If your'e using UTF-8, shouldn't you write:
> localedef -i he_IL -f UTF-8 he_IL.UTF-8
> instead?
"A locale name is typically of the form language[_terri�
tory][.codeset][@modifier], where language is an ISO 639
language code, territory is an ISO 3166 country code, and
codeset is a character set or encoding identifier like
ISO-8859-1 or UTF-8."
The ".codeset" part is a convention. As much as glibc cares, can be
he_IL.foobar -- as long as you set the same name in LC_ALL / LANG, it'll use
a UTF-8 locale.
=================================================================
To unsubscribe, send mail to [EMAIL PROTECTED] with
the word "unsubscribe" in the message body, e.g., run the command
echo unsubscribe | mail [EMAIL PROTECTED]
