translate / pootle

Online translation tool
http://pootle.translatehouse.org
GNU General Public License v3.0
1.49k stars 287 forks source link

Source language should not be translatable #1710

Open rimas-kudelis opened 13 years ago

rimas-kudelis commented 13 years ago

Version: 2.1.x

Friedel says that there is already some special treatment done to Templates language. Same treatment should be done to the project's source language. E.g. if I'm translating FROM English, it doesn't make much sense to display English among the TARGET languages available for translation. IMO, it should simply be omitted from the list, but if not, at least it should be treated the same way as Templates is (perhaps it should actually be treated that way INSTEAD of Templates)?

alaaosh commented 13 years ago

as of r16297 if source language is acting as the templates provider then translations will not be saved to disk

rimas-kudelis commented 13 years ago

Sorry, I don't quite understand what you mean. In particular, what is the difference between the source language and the templates provider? Under what circumstances are these languages different?

alaaosh commented 13 years ago

Pootle identifies a templates translation project, this is the explicit templates language is present otherwise it is the source language.

the idea is if explicit templates lang exists then that's what the user wants (bugs in detection not withstanding), if it is confusing you just delete the language :-)

this bug is not resolved in r16297, but that's as far as we can go in a bug fix release. the real fix will have to wait.

transl8bzimport commented 13 years ago

Originally posted by Chris Leonard:

I am not sure I agree with the logic here. There are cases where the original English string contains a typographical error and one might want to be able to override that string until it can be fixed by the developer

In many projects the process of translating en_US (source language) into en_GB serves an important function by having another English speaker review the original strings thoroughly for typographical errors and poor syntax. It should come as no surprise that not every developer has the best language writing skills.