Quote:
Originally Posted by ixtab
@JustAMan: *missing* entries in a locale file should normally not be an issue (because they will be taken from the default entry then). However, *wrongly translated* ones are probably the cause of all this weirdness. I don't have the time to do it, but try to write a script which finds entries where
- the german "translation" is the *same* as the original en_US one
- and the russian one is *different* from the original.
These are likely to cause problems.
Update: This task will probably be much simpler if you work on the source .properties files ("tx pull -a" first, then look around the files). I'm only referring to the de translation as the "reference implementation" because it seems to be working correctly for everyone, and it's 100% complete.
|
I wrote the tool to compare localizations.
What it does is:
* takes some "model" language that seems to be working fine (e.g. "de")
* compares all de.properties and en_US.properties to find out what properties inside those are identical
* compares all other languages .properties and en_US.properties
* generates .html reports for all other languages showing folders, property names & values if:
- value for given property name is different for given language and en_US
AND
- value for given property name is identical for en_US and "model" language
That way it should be easier to find out "out-translated" localizations.
I'm attaching the tool and its report:
loc-report.zip
To use the tool do "tx pull -a -s" and run "python report.py <model_language>" in tx working directory.
Those reports are generated with German localization as a model.
ixtab,
Can you have a look at those reports? I'm especially interested in Russian one, you know
but this tool should generate reports useful for other languages as well.
Maybe by analyzing this we can create a list of properties that
shouldn't be translated, rather than say vaguely "don't translate something that is too short".