admin wrote:Opening the app for German will also open it for any other language. The question will be only which language I will allow. If you have a good french translation it would take me 10 seconds to add French to the "allowed" languages. That's my currrent plan.
Reading the topics from this afternoon I'd have said exactly the same. I think that's the best solution for the moment. Even while doing this job you might learn more for future decisions.
Just to say: there is one level more of freedom! Because, as I interpret your words, you are especially thinking about XY itself. This has the highest demand for correctness and timing dependency.
But there is another part: help in it's internal form, and (even more freedom) in the pdf. As these don't have the restrictions of fitting the program (in means of field-length etc.) they are more independent. And the pdf is even more independent, as it tells "I'm version 11.00" - so everybody can imagine more or less differences if the current XY is 12.30
(This wouldn't be fine for the internal help, and impossible e.g. for the names of new options inside XY code.)
So I think a Russian (or whatever) translation of the help pdf could be done anytime, referring to the original English XY-commands, and referring to the XY-version it is made for.
OK: this would make a demand for you to make a kind of change-log for changes in help - to enable a translator to update the translation without searching for each change...