On Jun 8, 2011, at 12:57 PM, Alexander Best wrote: > *however* when i save a file via the gtk save dialog (lets say from within > chromium), the filename only gets displayed correctly in the gtk open dialog. > > saving a file "ÄÖÜäöüß.html" from chromium's gtk dialog returns the following > under the console or an X term: > > otaku% ls|grep html|hd > 00000000 c3 84 c3 96 c3 9c c3 a4 c3 b6 c3 bc c3 9f 2e 68 |Ã.Ã.Ã.ÀöÌÃ..h| > 00000010 74 6d 6c 0a |tml.| > 00000014
That's a UTF-8 representation; c3 84 is Unicode U+00C4 aka "LATIN CAPITAL LETTER A WITH DIAERESIS". > when i start gnome and use the open dialog both the `touch`ed "ÄÖÜäöüß" file > as > well as the "ÄÖÜäöüß.html" saved by chromium looks fine. > > is gtk maybe switching to unicode when saving non-asciichars, instead to > ISO8859-15? however when it accesses a filename it can understand unicode as > well as ISO8859-15? Yes, that appears to be the case. > can i instruct gtk to always use ISO8859-15 when saving filenames? Dunno. Fortunately, ISO 8859-15 can be stored on FreeBSD's UFS filesystem without lossage-- other character sets can't since UFS doesn't do Unicode per se, just UTF-8. Regards, -- -Chuck _______________________________________________ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
