catkin |
03-04-2010 01:56 AM |
Quote:
Originally Posted by sahko
(Post 3885099)
Why do you want to change that?
|
Good question, especialy as /etc/profile.d/lang.sh includes the comment:
Code:
# There is also support for UTF-8 locales, but be aware that
# some programs are not yet able to handle UTF-8 and will fail to
# run properly. In those cases, you can set LANG=C before
# starting them. Still, I'd avoid UTF unless you actually need it.
Unfortunately it is atually needed, for Bacula. According to the Bacula Main Reference (available as PDF or HTML at http://www.bacula.org/en/?page=documentation), in the "13.1 Critical Items" section: " Bacula assumes all filenames are in UTF-8 format. This is important when saving the filenames to the catalog. For Win32 machine, Bacula will automatically convert from Unicode to UTF-8, but on Unix, Linux, *BSD, and MacOS X machines, you must explicitly ensure that your locale is set properly. Typically this means that the bf LANG environment variable must end in .UTF-8. An full example is en US.UTF-8. The exact syntax may vary a bit from OS to OS, and exactly how you define it will also vary."
It would be nice to set it for Bacula only but that would require front-ending a lot of executables and I'm not confident of being able to identify them all. Actually it would be very nice because setting $LANG to en_GB.UTF-8 (the closest available for Indian English) is already causing breakage: - mrxvt (terminal emulator) positions the CLI cursor incorrectly and cannot do command line editing. It does not support UTF-8 so that's fair enough. Unfortuantely I'll have to change terminal emulator and that is likely to require a lot of time to get the new one set up and working nicely.
- dvd+rw-format is outputting unexpected characters which broke the locally written backup script until fixed with export LANG=en_US.
|