Required Infrastructure

• Interested languages must have a locale
• How to handle verb-noun ambiguities
• This is mostly requirements for Firefox localisation
• Fennec would be very similar and doesn't need specific Infrastructure

Provide the Mozilla l10n files

• L10n files: .dtd and .properties files used by Mozilla
• Needs to be attached when you report a bug to add a language
• Use po2moz/other script to create L10n files out of the PO files that has the updated translations, for language teams (daily)
• pomigrate 2 script to update the PO files to correspond to the new English files
  • Some translated strings might be marked as fuzzy if the source has changed
• Copy to download area (document URL)
  • Host at download.locamotion.org, to be done by Friedel and Walter
  • A tarball of L10n files per language as the output to be downloaded
• Split up build_ff_langs.sh into l10n->PO and PO->l10n files
• CGI application to request generating the Mozilla l10n files
  • Errors should be sent by the language teams to the Localise Software mailing list

Adding/Starting a new language

• moz2po script to generate pot files from L10n files, from which po files for each language are created
• Work stable releases until no new languages are being accepted
• Work on next (new) release after that
  • Update PO files in Pootle (via POT files) on each slush/firm string freeze

Languages translating from another source language

• Translating from French/Arabic/Portuguese
• Online: a script to generate PO files in French for example, to be used in Pootle as an alternative language, to help teams understand the source strings.
• Offline: need a script to add the translated strings of the alternative language as comments in the English PO files

Language Packs

• Automatically generated with POT files
• Link to built language packs from ANLoc site
  • Daily language packs have the same filename
  • Link to latest language pack
  • Link to directory containing previous language packs
• Language teams are responsible for uploading language packs to AMO

Servers

• Pootle server: will be used for
  • Online translation through Pootle
  • Hosting translated strings in PO files (from Pootle, or by uploading offline translations)
  • Generating tarballs of PO files for each language
  • Available downloads of PO files tarball

• L10n Mozilla sever: will be used for
  • Daily back ups of language PO files tarball
  • Running the scripts to generate Mozilla L10n files
  • Available downloads of L10n files tarball, that will be needed for attachement and for building the language packs