Axel mentioned that we can generate installers with the missing
entities by adding the en-US
Is this already available? or is it by adding the l10n-merge tool
somehow?
That depends on the make-jars rewrite, see bug 439050. That patch isn't
ready for review yet.
As people complained about the noise in the l10n group, it might be a
good idea to just ask me directly on these things, as I am really the
one that would know. Or just .builds, not sure how much that group minds.
Axel
This is how we've been building files with the Translate Toolkit -
replacing the source text when a translation doesn't exist. This way we
always get usable translations, even if incomplete.
Friedel
I added a small script to Silme to do this ./script/l10nmerge.py:
You have three kinds of merges implemented:
-t1: merges l10n entities over source files (en-US)
-t2: merges missing entities at the end of l10n files
-t3: merges missing entities where they should be in the l10n files.
This is just a proof of concept, but a usable one :)
Greetings
Zbigniew Braniecki
--
Mozilla (http://www.mozilla.org)
It could be nice if the build will shown something when it opens if
there is a missing entity. Maybe a javascript popup with the strings
missing, or maybe a about:l10n page as a start page.
This obviously will only be for "nightly" builds
Axel