![](https://secure.gravatar.com/avatar/dc940f48c5635785f32941f1fbe6b601.jpg?s=120&d=mm&r=g)
On Dec 6, 2008, at 12:56 PM, Krzysztof Kosiński wrote:
I'm getting back to work on the GIO transition.
The first thing that must change in order to move to GIO is the parameter parsing (to open files it's best to use Gio::File::create_for_commandline_arg, and for this filenames in filename encoding are needed). However, this will interfere with the shell mode. I don't think this is an useful feature - an embedded scripting language would be a lot better - but probably there's someone who relies on it, so it should be preserved until there's a replacement. I would like to reuse the option parser from the main application, but then I have to parse the command line into argc and argv myself, because that's what g_option_context_parse accepts. Does anyone know whether there's an "officially blessed" way of parsing a command line into argc and argv?
Regards, Krzysztof Kosiński
One factor to consider is MS Windows.
If things come through a standard command-line, they get converted to "Current ANSI Code page" and any characters not in that get lost. If representative test characters (Latin-1, but not Cp1252, Cp1252 but not Latin-1, neither Latin-1 nor Cp1252, etc) are not run through, then it is hard to know things don't work.