On Wed, 2005-01-12 at 02:30 +0100, Bastian Kleineidam wrote: > On Tue, Jan 11, 2005 at 02:37:17PM -0600, Joe Wreschnig wrote: > > Is there documentation on $CHARSET anywhere? I'd like to have > > "definitive" environment variable to set, and if $CHARSET is it, great. > > For GTK, $CHARSET tells programs about filesystem encodings. > See also the old bug report about gringotts: > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=206618&archive=yes > > If $CHARSET is not set, any GTK program assumes UTF8 filename > encoding. Setting G_BROKEN_FILENAMES=1 prevents this and always > tries to use the locale charset (which is bad anyway, because > the locale charset changes, filesystem encoding not). > See http://www.gtk.org/gtk-2.2.0-notes.html and look for > G_BROKEN_FILENAMES.
Unfortunately, although 0.8 is a big step towards being able to do this, it won't fix this problem. We translate GTK ListStore contents directly into filenames (and vice versa) in several places where it's nontrivial to convert between encodings now. One of the main tasks slated for 0.9 is a big cleanup of the Properties dialog, which should make this bug much easier to fix. -- Joe Wreschnig <[EMAIL PROTECTED]>
signature.asc
Description: This is a digitally signed message part
