Comment 12 for bug 679715

All command line tools are not localized. Either we need to localize *all* comand line tools or none. But there is no easy way to integrate this in a "higher" level. And this will create a *lot* of new strings.

The version of gettext at gnuwin32 is outdated. They are at 0.14, the offical release is 0.18.1. But currently I have no time to test, I must fix the open issues you left with the merge.

There are more issues with your translations of nona:
1.) There could be an issue with 2-byte strings (e.g. japanese translation), I fear they don't work with your the current implementation.
2.) One sentence should only be in one translated string, don't split one sentence into different strings. This makes it for the translator impossible to get the sense and translate it (e.g. in an other language there could be a other word order).
example:
    << " " << _X("The following output formats (n option of panotools p script line)") << std::endl
    << " " << _X("are supported:") << std::endl
3.) Don't use name/argv[0] in sentences
e.g. std::cout << name << "-" << _X("GPU does not support this projection. Switch to CPU calculation.") << std::endl;
First issue: on windows argv[0] can contain the full path. This make it hard to read
Second: The translator does not know that the application adds "nona-" to translated text. In an other language than english the sentence could also start with an other word than "GPU".