|
For the first time I encounter an English translation in a Django project that is already in English. It gave me hard time to figure out where the "recent badges" string is as in the code it is "recent awards" and in the 'en' translation it is converted to "recent badges". Is there a specific reason for having an English translation? |
|
Although much has changed in the meantime, when we first started working on this project, there was already a translation, and we couldn't get rid of it straight away because there were some nasty "engrish" translated into semi-correct English. So we kept the translation, but after a while, even though we corrected most of the errors in the source, the translation revealed useful if, for example, you want to change a couple of prompts without hacking the source, and making updates harder. 2
but this makes translation into other languages much harder because one cannot find a phrase he wants to translate in the translation file.
(15 Oct '10, 06:46)
omat
Never did a translation (at least a complete one), so I don't have a strong opinion. But I was convinced that when you do a translation you translate everything from the ground up and not just only a couple of selected strings. Anyway, this should not be a problem when the source and translation fully converge.
(15 Oct '10, 07:02)
Hernani Cerq... ♦♦
it's really a bad practice to use the translations as string replacements for english. it makes translating the files into other languages extremely hard. i'm already 15% into a translation and just found out about this concept. seems like i have to redo it all over again
(20 Feb, 01:37)
0food
|
