After some time spent chatting with Alexander in IRC, here is my understanding of the initial part of the bug dealing with the SUPPORTED file:
1) make localedata/install-locales will run a localedef for every locale listed in the SUPPORTED file 2) if someone wants to go with the individual localedef commands, yet needs a locale not included in the book, they can get the command syntax from the SUPPORTED file (which makes it handy to have around) ex: there is a line in that file that says "kk_KZ/PT154" so the localedef command would be "localedef -i kk_KZ -f PT154 kk_KZ" 3) The SUPPORTED file lists only the locales that are "currently supported and somewhat tested" by the glibc maintainers, however many others work that are not in the file. According to Patrakov, those others are best left as an advanced topic outside the book (would a link be apropo?) I'm not aware of those "extra" locales are for the more obscure country codes or what. Alex can probably shed some light on that. So basically, the question is whether or not the SUPPORTED file should be installed in /usr/share/i18n for documentational purposes and what, if anything, should be done for locales that aren't listed in the file, but work. Apparently, some distros patch the file before building glibc so that extra locales will be installed. After installation, though, SUPPORTED becomes only a doco file. -- Archaic Want control, education, and security from your operating system? Hardened Linux From Scratch http://www.linuxfromscratch.org/hlfs -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
