Comment 13 for bug 679715

On January 10, 2011 12:38:18 pm tmodes wrote:
> All command line tools are not localized. Either we need to localize
> *all* comand line tools or none.

agree. I only started with one CLI-tool and with one case of non-wx
transaltion in a GUI as a proof of concept. Once things work well in those,
the next step will be to localize *all* other CLI tools and non-wx
translations in GUI tools.

> this will create a *lot* of new strings.

I am aware of this. I do not expect things to happen overnight, neither on my
end, nor on the translators end. But the long term goal is to localize
everything.

> 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.

That's OK. Don't feel under pressure. The merge of the new feature is more
important than the localization.

> 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.

what makes you fear so? can you point me in a direction where I can read
about the issue and try to solve it? I have no experience with translationn
to 2-byte strings.

> 2.) One sentence should only be in one translated string, don't split one
> sentence into different strings.

OK, will fix. No time now, but it is the next thing I intend to do on the
i18n branch.

> 3.) Don't use name/argv[0] in sentences

This was already in use in nona before I continued using it. I thought it was
a good thing and applied it consistently. From your feedback I understand it
is not a good things and I will revert it consistently. It will need to be
fixed in the default branch as well.

Thanks again for your feedback and your patience.