On 1/24/14 9:30 AM, Neil wrote:
Since we're not allowed to move locale files on branches, is it possible
for a jar.mn to refer to locale files from another part of the tree?
Yes, these days you can actually do that.
Look at what we're doing in mobile/android/locales/jar.mn, with the
chunks like
relativesrcdir dom/locales:
locale/@AB_CD@/browser/overrides/charsetTitles.properties
(%chrome/charsetTitles.properties)
We're using that to steal overrides, but that part is really just packaging.
Axel
PS: for others, "not allowed" in this case means "very strongly frowned
upon". This is about devtools files that are going to move again in the
future. Our external l10n tools don't support picking up moving a file
in the repo, and they don't move files in their UX, so it's an awful
amount of work to actually move files. This gets worse due to some
locales moving on central, but then the majority only sees this on merge
day, and then you need to remember, and there's all kind of new stuff,
and doh. For many localizers, this is just strings disappearing in one
place, and translating the same strings from scratch somewhere else.
Thus, we can, but really to the final location, etc.
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
