| 1 |
Hi, |
| 2 |
|
| 3 |
On Wed, 02 Nov 2005 15:53:11 +0100 |
| 4 |
Holly Bostick <motub@××××××.nl> wrote: |
| 5 |
|
| 6 |
> [...] |
| 7 |
> /etc/locales.build |
| 8 |
> |
| 9 |
> which says |
| 10 |
> |
| 11 |
> # This file names the list of locales to be built when glibc is installed. |
| 12 |
> # The format is <locale>/<charmap>, where <locale> is a locale from the |
| 13 |
> # /usr/share/i18n/locales directory, and <charmap> is name of one of the files |
| 14 |
> # in /usr/share/i18n/charmaps/. All blank lines and lines starting with # are |
| 15 |
> # ignored. Here is an example: |
| 16 |
> # en_US/ISO-8859-1 |
| 17 |
> [...] |
| 18 |
> Glibc built fine (afaict), but my problem is that I now don't know what |
| 19 |
> to export with a LANG variable. |
| 20 |
> |
| 21 |
> For example, if I want nl_NL@euro/UTF-8, how do I export that as opposed |
| 22 |
> to nl_NL@euro/ISO-8859-15 (or worse, ISO-8859-1)? |
| 23 |
|
| 24 |
Note the comment you've cited: The format is "locale/charmap". This |
| 25 |
generates the locale data for a certain "language" (it's a little bit |
| 26 |
more than just language, though) for the specified charmap. |
| 27 |
|
| 28 |
In LANG/LC_* you only set the locale. The charmap is (semi-) |
| 29 |
automatically chosen, which makes sense, since it's terminal dependant |
| 30 |
which charset is used. |
| 31 |
|
| 32 |
> Was I supposed to give the locales individual names as the Localization |
| 33 |
> Guide implies? locales.build doesn't indicate that you can do that (and |
| 34 |
> in fact, I thought perhaps the reason why language exports were mildly |
| 35 |
> borked might be because I had done so). |
| 36 |
|
| 37 |
nl_NL@euro/ISO-8859-1 didn't make much sense to me (and maybe causes |
| 38 |
some failures when building?), but other from that it seemed OK. |
| 39 |
|
| 40 |
> Should I just get rid of the 'extra' locales (ISO-8859-15 and |
| 41 |
> ISO-8859-1)? Since I guess I'm going to try to stick to UTF-8, maybe I |
| 42 |
> don't really need them (I was mostly covering my butt, concerned that my |
| 43 |
> current and future network connections might not support UTF-8, since |
| 44 |
> they're mostly to Windows machines). |
| 45 |
|
| 46 |
All the terminals you're using support UTF-8? |
| 47 |
|
| 48 |
> I guess I've made a mistake, but I'm not quite sure what to do about it. |
| 49 |
> Since fixing it will most almost certainly require a recompile of glibc, |
| 50 |
> and since compiling glibc takes nine-tenths of forever, I'd like to get |
| 51 |
> it on with it as soon as possible (sigh). So any hints would be appreciated. |
| 52 |
|
| 53 |
How does the "borkism" of your locales manifest? |
| 54 |
|
| 55 |
|
| 56 |
-hwh |
| 57 |
-- |
| 58 |
gentoo-user@g.o mailing list |
Archives