Re: [Gtk-gnutella-devel]GTKG chooses wrong charset/encoding for filenames on disk

[Haxe <ha...@pa...>]

On Wednesday 28 September 2005 23:55, Christian Biere wrote:
> And with respect to storing files: No, it's bad. I've seen showing
> the correct filename in the "save as" dialog and then store some
> corrupt filename with question marks in it.

That is probably a symptom of exactly what I just tested and found=20
correct.

When I use Firefox with locale de_DE.utf8 and save a file as "B=E4r", it=20
ends up on the Disk as the bytes 42 C3 A4 72 (hex), which is the=20
correct representation of "B=E4r" in utf-8.

When I start Firefox with locale de_DE@euro and save a file as "B=E4r", it=
=20
ends up on the Disk as the bytes 42 E4 72 (hex), which is the correct=20
representation of "B=E4r" in iso-8859-15.

But in the latter case, E4 is not a valid utf-8 character. So, when I=20
start a filemanager or console with a utf-8 locale set, it displays the=20
filename as "B?r", because the name contains a byte that doesn't make=20
sense in the locale charset (utf-8).

So, if you have problems with files saved by firefox apparently=20
containing question marks, you probably just have to set a correct=20
locale before you start Firefox (and your file manager, of course).

Hauke