I once wondered why we used Popt instead of Getopt...
until i noticed that Popt has superior I18N error messages.
is there a good reason to change?
bob
Jon A. Cruz wrote:
On Mar 13, 2008, at 3:19 PM, Krzysztof Kosiński wrote:
Hello
Can anyone review the patch provided here: https://bugs.launchpad.net/inkscape/+bug/195220 It moves the commandline option parsing from popt to GOption and shortens main.cpp a fair bit, but I'm not sure how does Inkscape open files
- does it
(1) use UTF-8 filenames or (2) filenames in the system encoding? This patch will be ok if 2 is the case, and I believe 2 is the standard practice with Glib.
That's actually a bit tricky. It should actually be using neither of those encodings. Instead it should be using the third type of encoding which is filename encoding (GTK apps have to juggle system, internal/UTF-8 *and* filesystem)
The standard with GLib has been that it uses filesystem encoding. Sometimes filesystem encoding is the same as system encoding (in which case you'll notice no difference). Other times filesystem encoding is different.
What makes it even trickier is that the filesystem encoding can be the original one used waaaaaaaay back when the filesystem was installed. For example I've seen Japanese systems that have a Linux distro installed that uses UTF-8 as the system and filesystem encodings *but* on a specific box use ISO-2022-JP for the filesystem instead since it was an older system that had been upgraded.
This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel