Bug#217261: galeon: browsing unicode filenames doesn't appear.

[Sebastien Bacher]

Sven Luther <sven.luther@wanadoo.fr> writes:

> Yeah, sure, brain dead choice, at least until debian officially supports
> a full UTF-8 desktop, which it currently does not.

Brain dead choice ? I don't think so, UTF-8 choice is an upstream choice
to a technical problem ... do you know a solution to manage differents
locales in a proper way ? 
BTW the Gnome desktop is UTF-8 ready.

> Ah, yes.
>
> But then, how will it work out, if i have UTF-8 filesystems on my box,
> and the CD has something else ?

Yes, just set G_BROKEN_FILENAME (again)


> And having files simply disapear is worse yet. Also, i seriously don't
> believe that there is no sane way around this, just displaying a ? like
> many apps do or something such, should be ok, no ? This is typically a
> decision made by 7bit locale users who don't care.

No, that's a technical solution ... support of multi-locales is not
possible. Just set G_BROKEN_FILENAME, you'll have iso-8859-15 encoding
files ok and UTF-8 one with some A@ instead of broken encoding (instead
of your "?" ... is it really such a big difference ?)


> default, but just making the files vanish is bad, and definitively a
> bug, which hopefully should be fixed.

G_BROKEN_FILENAME exists, the "broken" part of the name is not really
clear, should rather be named G_COMPAT_MODE or something like that, but
works ...

> Mmm, probably will never happen, so let's keep this open until debian is
> ready to go to a full UTF-8 system, which it clearly is not yet.

Ok, so I'll tag it as a wontfix.


Cheers,

Sebastien Bacher