mirror of
https://github.com/mozilla/gecko-dev.git
synced 2025-02-14 20:22:00 +00:00
2259382328
======== https://hg.mozilla.org/integration/gaia-central/rev/955e63dc2d09 Author: Dale Harvey <dale@arandomurl.com> Desc: Bug 830157 - Remove uppercase text transform on shared headers. r=arnau ======== https://hg.mozilla.org/integration/gaia-central/rev/8393ca75be72 Author: Fabien Cazenave <fabien@cazenave.cc> Desc: Merge pull request #11304 from fabi1cazenave/l10nContacts-bug898992 Bug 898992: l10n.js should keep track of untranslated elements, r=julienw ======== https://hg.mozilla.org/integration/gaia-central/rev/f9e9f16457fa Author: Ben Kelly <ben@wanderview.com> Desc: Bug 898992: unit tests ======== https://hg.mozilla.org/integration/gaia-central/rev/9fae9096f6ef Author: Fabien Cazenave <fabien@cazenave.cc> Desc: Bug 898992: l10n.js should keep track of untranslated elements If a document embeds an inline JSON dictionary, l10n.js translates the document right away without loading other l10n resources. It usually works fine because our build system ensures the inline JSON dictionary contains all the necessary keys to handle the declarative content; but if an app adds some dynamic content to the document, when the user language is changed there might be some untranslated elements -- e.g. the "Add Contact" form in the Contacts app. With this patch, l10n.js keeps track of untranslated elements: * if an inline dictionary is used, untranslated elements will be translated as soon as all external l10n resources are loaded; * instead of raising a JS warning each time an element can't be translated, l10n.js now sends one unique warning with all missing l10n keys when the document is translated.
An explanation of the Mozilla Source Code Directory Structure and links to
project pages with documentation can be found at:
https://developer.mozilla.org/en/Mozilla_Source_Code_Directory_Structure
For information on how to build Mozilla from the source code, see:
http://developer.mozilla.org/en/docs/Build_Documentation
To have your bug fix / feature added to Mozilla, you should create a patch and
submit it to Bugzilla (https://bugzilla.mozilla.org). Instructions are at:
http://developer.mozilla.org/en/docs/Creating_a_patch
http://developer.mozilla.org/en/docs/Getting_your_patch_in_the_tree
If you have a question about developing Mozilla, and can't find the solution
on http://developer.mozilla.org, you can try asking your question in a
mozilla.* Usenet group, or on IRC at irc.mozilla.org. [The Mozilla news groups
are accessible on Google Groups, or news.mozilla.org with a NNTP reader.]
You can download nightly development builds from the Mozilla FTP server.
Keep in mind that nightly builds, which are used by Mozilla developers for
testing, may be buggy. Firefox nightlies, for example, can be found at:
ftp://ftp.mozilla.org/pub/firefox/nightly/latest-trunk/
- or -
http://nightly.mozilla.org/