Closed Bug 455145 Opened 13 years ago Closed 13 years ago
We need a few changes to fennec to make it blend nicely with our l10n infrastructure. hg makes that a simple patch, nicely, which I attached. Changes: - move the localizable files from chrome/locale/en-US to locales/en-US/chrome - slightly change the structure internally to ab-CD.jar - move branding into ab-CD.jar - add an l10n.ini (no filter.py, as I don't think we need one right now) I didn't add any repackaging logic, right now, you should be able to create localized builds with --enable-ui-locale and do full builds. The localization files should reside in l10n-central/ab-CD/mobile. Tested locally on a mac build for just en-US.
Attachment #338446 - Flags: review?(mark.finkle)
Comment on attachment 338446 [details] [diff] [review] move localizable files into mobile/locales/en-US, minor build foo and l10n.ini Going to wait to land this until some patches that touch locale are landed. Then I'll unbitrot this patch and land it.
Attachment #338446 - Flags: review?(mark.finkle) → review+
Same as Axel's patch. I just updated it for changes: * searchplugin stuff * additions to locale Landing
Attachment #338446 - Attachment is obsolete: true
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Can we already create a subfolder l10n-central/ab-CD/mobile in which we can put the contents of mozilla-central/mobile/locales/en-US to start localizing?
(In reply to comment #4) > Can we already create a subfolder l10n-central/ab-CD/mobile in which we can put > the contents of mozilla-central/mobile/locales/en-US to start localizing? I am ok with that, but let's get Pike to comment on that.
And it would be nice if the builds would show up on a dashboard somewhere. Axel?
we have l10n builds
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.