Bug#272478: libglib2.0-0: Shouldn't require to set G_FILENAME_ENCODING in non UTF-8 locale

Laurent Martelli Laurent Martelli <laurent@aopsys.com>, 272478-quiet@bugs.debian.org
Mon, 20 Sep 2004 20:15:17 +0200


>>>>> "Sebastien" == Sebastien Bacher <seb128@debian.org> writes:

  Sebastien> severity 272478 wishlist tag 272478 + wontfix thanks

  Sebastien> Hi,

  Sebastien> This has already been discuted again and again upstream,
  Sebastien> there is no better solution than the current one to have
  Sebastien> a working utf-8 support.  I'll add some pointers to
  Sebastien> previous discussion a big later. For the moment I change
  Sebastien> the severity of the bug to wishlist + wontfix since
  Sebastien> upstreams are not going to change that.

If a user wants UTF-8 filenames, shouldn't he use an utf-8 locale ?
And all will be fine for him with a patch like mine. The current
behavious is completly bogus with a non utf-8 locale since programs
use the locale's encoding for filenames. Am I missing something ?

-- 
Laurent Martelli
laurent@aopsys.com                                Java Aspect Components
http://www.aopsys.com/                          http://jac.objectweb.org