Confirmed users, Bureaucrats and Sysops emeriti
1,737
edits
Verbatim:Development/filetypes: Difference between revisions
m
no edit summary
mNo edit summary |
|||
| Line 1: | Line 1: | ||
[[Verbatim]] » Development Planning » Interaction with file types | [[Verbatim]] » Development Planning » Interaction with file types | ||
=== 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 [[Update:Remora_Localization#Static_Strings_.28PHP_and_gettext.29|defined here]]. | |||
2) The main interface also uses [[Update:Remora_Localization#Dynamic_Strings|dynamic strings]] for the category names, application names, platforms, etc. These are already [https://addons.mozilla.org/en-US/firefox/localizers updatable via the web], are dependant on [https://bugzilla.mozilla.org/show_bug.cgi?id=430121 bug 430121], and are '''not planned for our initial launch''' | |||
3) There are [http://svn.mozilla.org/addons/trunk/site/app/locale/en_US/pages/ 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 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: | |||
* [https://bugzilla.mozilla.org/show_bug.cgi?id=430122 Bug 430122 – Provide writable interface for add-on metadata strings] | |||
* [http://developer.mozilla.org/en/docs/Localizing_an_extension Localizing an Extension] | |||
* [http://developer.mozilla.org/en/docs/Localizing_extension_descriptions Localizing Extension Descriptions] | |||
* [http://developer.mozilla.org/en/docs/Localizing_extension_metadata_on_addons.mozilla.org Localizing extension metadata on AMO] | |||
=== Localizing Firefox === | === Localizing Firefox === | ||
| Line 12: | Line 30: | ||
2) The second type of L10n on mozilla.com are custom .lang files ([http://svn.mozilla.org/projects/mozilla.com/trunk/fr/includes/l10n/ French example]). These are used by the legacy [http://svn.mozilla.org/projects/mozilla.com/trunk/includes/l10n_moz.class.php l10n_moz] class. The file format is very simple and documented in that class. | 2) The second type of L10n on mozilla.com are custom .lang files ([http://svn.mozilla.org/projects/mozilla.com/trunk/fr/includes/l10n/ French example]). These are used by the legacy [http://svn.mozilla.org/projects/mozilla.com/trunk/includes/l10n_moz.class.php l10n_moz] class. The file format is very simple and documented in that class. | ||
=== Localizing | === Localizing mozillaparty.com === | ||
Looks like mozillaparty is using the ISO-639-2 standard (as used by CakePHP 1.2) and so it isn't compatible with any of our libraries/code. We'll have to write something to convert it at some point. | |||
2) | |||
=== Localizing SUMO === | === Localizing SUMO === | ||
| Line 37: | Line 46: | ||
Questions about file types, please email [mailto:djst@mozilla.com David Tenser]. | Questions about file types, please email [mailto:djst@mozilla.com David Tenser]. | ||