Jürg Billeter wrote:
Yes but it may introduce problems elsewhere as e.g. glib (and so gtk+)
uses UTF-8 as default filename encoding, independent of your LANG
variable - which is IMO the only sane filename encoding but is obviously
problematic for non-UTF-8 console users.
Every sane distro sets the G_FILENAME_ENCODING or (obsolete)
G_BROKEN_FILENAMES variable. Read this page:
http://www.linuxfromscratch.org/blfs/view/svn/postlfs/profile.html
After you are sure about your locale settings, create the /etc/profile.d/i18n.sh file:
cat > /etc/profile.d/i18n.sh << "EOF"
# Set up i18n variables
export LC_ALL=[ll]_[CC]
export LANG=[ll]_[CC]
export [EMAIL PROTECTED]
EOF
The LC_ALL variable sets the same value for all locale categories. For better control, you may prefer to set values individually for all categories listed in the output of the locale command.
The G_FILENAME_ENCODING variable tells applications such as Glib and GTK+ that filenames are in the default locale encoding and not in UTF-8 as assumed by default.
Do you think that setting G_FILENAME_ENCODING should be moved to Glib2
page instead?
By defaulting to UTF-8, Glib2 developers essentially say that "ls" is
broken and that every bash script writer should call iconv before
displaying filenames. Thus, I disagree with their default.
And now LFS is broken in all UTF-8 based locales (mainly due to ncurses
and console bootscript). The breakage is critical enough to prevent
non-English users from typing/seeing text in their language in some
important applications. English people wouldn't call this critical
because their native language uses only ASCII characters and pound sign,
thus the breakage occurs only on rare-for-them characters. But it's
still there.
Making LFS work in the upstream-imposed limits for both UTF-8 and
traditional locales is scheduled for LFS 7.0, but UTF-8 will not be the
default and its use will still be discouraged.
--
Alexander E. Patrakov
--
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
