Hi all, I've either made a mistake, or I have a question, or both (or maybe two questions, in that case).
I got an update to glibc the other day, and took the opportunity to check my userlocales because they are not always working as I want (basically ISO-8859-15 characters do not always appear under all circumstances). Originally, I had my locales set up as per the documentation at http://www.gentoo.org/doc/en/guide-localization.xml in the format en_US.UTF-8/UTF-8 and [EMAIL PROTECTED]/ISO-8859-15 and the like (replacing de_DE with nl_NL, of course), but when I got the glibc upgrade I didn't look at that again, but instead at /etc/locales.build which says # This file names the list of locales to be built when glibc is installed. # The format is <locale>/<charmap>, where <locale> is a locale from the # /usr/share/i18n/locales directory, and <charmap> is name of one of the files # in /usr/share/i18n/charmaps/. All blank lines and lines starting with # are # ignored. Here is an example: # en_US/ISO-8859-1 So I looked in the referenced directories and here's what I came up with: en_US/ISO-8859-1 en_US/ISO-8859-15 en_US/UTF-8 nl_NL/ISO-8859-1 [EMAIL PROTECTED]/ISO-8859-1 nl_NL/ISO-8859-15 [EMAIL PROTECTED]/ISO-8859-15 nl_NL/UTF-8 [EMAIL PROTECTED]/UTF-8 Glibc built fine (afaict), but my problem is that I now don't know what to export with a LANG variable. For example, if I want [EMAIL PROTECTED]/UTF-8, how do I export that as opposed to [EMAIL PROTECTED]/ISO-8859-15 (or worse, ISO-8859-1)? Was I supposed to give the locales individual names as the Localization Guide implies? locales.build doesn't indicate that you can do that (and in fact, I thought perhaps the reason why language exports were mildly borked might be because I had done so). Should I just get rid of the 'extra' locales (ISO-8859-15 and ISO-8859-1)? Since I guess I'm going to try to stick to UTF-8, maybe I don't really need them (I was mostly covering my butt, concerned that my current and future network connections might not support UTF-8, since they're mostly to Windows machines). I guess I've made a mistake, but I'm not quite sure what to do about it. Since fixing it will most almost certainly require a recompile of glibc, and since compiling glibc takes nine-tenths of forever, I'd like to get it on with it as soon as possible (sigh). So any hints would be appreciated. Thanks, Holly -- gentoo-user@gentoo.org mailing list
