Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Minor
-
Resolution: Won't Fix
-
Affects Version/s: 1.9.3
-
Fix Version/s: None
-
Component/s: Language
-
Labels:None
-
Environment:language localization
-
Affected Branches:MOODLE_19_STABLE
Description
I am afraid automatically incorporating translations (localizations) from other projects will kill Moodle localization efforts on the whole. Rather than saving time, you get a mix of terminology that is impossible to maintain. If you concentrate on the end user's requirements, such a procedure is absolutely ungrounded. You cannot ensure consistence of term usage, not to mention that fact that (at least the HU counterpart) is half English, half Hungarian, and the Hungarian is produced by someone who is apparently anyone but a specialist proficient in orthography and grammar.
The obvious misconception is related to the assumption that each term in each language is translated in one single (and appropriate) way.
I'd suggest a check phase is included after automatic and uncontrolled import of translations from other projects and before implementation, so that the translators can streamline new terminology with the one they use and Moodle users are accustomed to. Otherwise, localizations will definitely be an unmaintainable mess.
Karoly Fabricz
Moodle HU localizer
Hi Karoly,
Thanks for your concern. At the moment, we are in a test phase. TinyMCE will be standard in Moodle 2.0., which is not expected before the summer.
As translator, you are of course free to replace the whole file.