https://bugzilla.novell.com/show_bug.cgi?id=162501 User mfabian@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=162501#c17 --- Comment #17 from Mike Fabian 2008-03-25 15:55:51 MST --- What about the hy_AM.armscii-8 locale? Does anybody really need that? Any reasons why one cannot use hy_AM.UTF-8? Anyway, if the locales ja_JP.SHIFT_JISX0213 and hy_AM.ARMSCII-8 are available in glibc and listed by the “locale -a” command, shouldn’t they be accepted in the spelling as they are listed by the “locale -a” command? “locale -a” lists the UTF-8 locales like ja_JP.utf8. That doesn’t look so nice to me because UTF-8 is the preferred spelling, i.e. it would be nicer if it were listed as ja_JP.UTF-8 by the “locale -a” command. But as ja_JP.utf8 and ja_JP.UTF-8 are treated as identical by glibc and it doesn’t cause problems if users look at the output of “locale -a” and then set LANG=ja_JP.utf8 because this works as well. Shouldn’t the weird legacy locales like ja_JP.SHIFT_JISX0213 and hy_AM.ARMSCII-8 also be accepted in the way they are listed by “locale -a”? Certainly they should be avoided, but unfortunately they are there. Not accepting them in the way as listed by “locale -a” just adds to the confusion. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.