On Wed, 22 Feb 2012, Jaka Kranjc wrote: [...]
Also in my previous email I forgot to mention that the /Unix line is missing from both start.exe usage strings, not just the one I mentionned before. Hopefully you will have noticed that already.
Too bad, I missed it. The two usage strings are identical though, so why not split the formalities away after the strings are thawed? Translators that don't use tools with translation memory will just have more work this way.
That's what should happen eventually. In fact start's messages need a thorough rework because it's a pain to work with right now. Also there's probably improvements to be made for all command line tools with regards to line wrapping. But it's going to take some work and that will all have to wait after the 1.4 release as we are in a string freeze right now.
On Wednesday 22 of February 2012 22:25:30 Francois Gouget wrote:
Too bad, I missed it. The two usage strings are identical though, so why not split the formalities away after the strings are thawed? Translators that don't use tools with translation memory will just have more work this way.
That's what should happen eventually. In fact start's messages need a thorough rework because it's a pain to work with right now. Also there's probably improvements to be made for all command line tools with regards to line wrapping. But it's going to take some work and that will all have to wait after the 1.4 release as we are in a string freeze right now.
Then I suggest it be split into separate strings for each command/parameter line and context added to mention any wrapping limit. Maybe even just the parts in the second column, so you don't have to bother checking whether people accidentally translated the flags. This would be optimal from a translator's perspective, but I fear the other programmers would revolt in disgust. :)
LP
-
Francois Gouget -
Jaka Kranjc