>> Should a combination like LANG=fr_FR LC_CTYPE=en_US.UTF-8 >> result in something equivalent to LANG=fr_FR.UTF-8? >In theory yes. In real life no. localedef compiles the locale files for >fr_FR to binary data files that assume fr_FR's encoding (ISO-8859-1 or >ISO-8859-15), and therefore refuse to load when the encoding is in >fact UTF-8.
what about LANG=fr_FR.UTF-8 LC_CTYPE=en_US.UTF-8 ? for UTF-8, the ctype information would be the same, right? (case, whitespace, etc ) If this is not the case, is there any locale which will correctly ctype() all of unicode? When programming, I avoid the ctype function itself. I think its better to convert to utf-8 on input (if its not already) and use generic unicode ctype functions. -- Linux-UTF8: i18n of Linux on all levels Archive: http://mail.nl.linux.org/linux-utf8/
