Verbatim:Development/filetypes

Verbatim » Development Planning » Interaction with file types

Localizing Firefox

Firefox is localized using .dtd and .properties files L10n Overview. Need information

Localizing mozilla.com

Mozilla.com is currently using two methods of L10n:

1) Most of mozilla.com is flat files. This means /en-US/index.html is the English front page and /fr/index.html is the French front page. This lets us provide slightly different content (eg. news stories) tailored for each locale. All .html files will have PHP content that should not be altered.

2) The second type of L10n on mozilla.com are custom .lang files (French example). These are used by the legacy l10n_moz class. The file format is very simple and documented in that class.

Localizing AMO

AMO is also a mix of L10n styles:

1) The main interface is using not-quite-standard .po files. Instead of using English strings, we're using placeholder strings as defined here.

2) The main interface also uses dynamic strings for the category names, application names, platforms, etc. These are already updatable via the web, are dependant on bug 430121, and are not planned for our initial launch

3) There are a few complete localized pages (similar to how mozilla.com is done). These are used for large chunks of localized data on AMO.

Update:Localizers provides localizer documentation.

Localizing SUMO

Need information

Localizing Add-ons & their metadata on AMO

not currently planned. While possible, this isn't one of the goals for our first milestone. For more information:

• Bug 430122 – Provide writable interface for add-on metadata strings
• Localizing an Extension
• Localizing Extension Descriptions
• Localizing extension metadata on AMO