Revision of Software Localisation Wiki from Tue, 11/08/2009 - 12:37

  • OpenID login failed.
  • OpenID login failed.

Tech Team roles

Localisation Process

Glossmaster


  • Single file per language
  • On Pootle server (check with IT+46)
  • Encourage to use PO

Pootle


  • Just an account on the Pootle server
  • Testing while translating

OR

  • Download PO file from the Pootle server
  • Translate with Virtaal/POEdit
  • Upload when they are done
  • Join translate-pootle mailling list

Virtaal


  • 3 files: virtaal.po, 1 for GTK (<200 words), 1 for gtkspell (12 words)
  • Locales are necessary to work (check with Martin)
  • Encourage teams to submit their GTK translation through to GNOME project
  • Translate over Pootle server
  • Download and upload/email
  • join the mailing list

Firefox


  • Localised copy is a different version
  • Language pack: FF extension that has different version with different languages
  • Build the language pack

Jargon


  • Official release
    • Available on main web-site
    • Localised installer
    • Localised search engines/bookmarks
    • Per language
    • Translated web-pages
  • Language pack
    • On AMO (addons.mozilla.org) site
    • Install "Locale switcher"
    • Search engine, bookmarks, etc. in original language (en-US)
    • Distribute it on ANLoc website for testing
  • Productisation
    • Non-translation localisation (search engines and bookmarks)

Translation timeline


|-
(Translate ~ 5k words?)

  • Register language team on Mozilla's wiki
  • Sign Mozilla contributors' agreement (required for VCS access)
1st language pack

Put on ANLoc site for testing

(Translate ~ 10k words?)

  • Create Mozilla bugzilla account
  • Report bug to request VCS access, attach translation files
  • Report bug to request language to be added to product (FF)
  • First commit by Mozilla
Language pack on addons.mozilla.org sandbox (experimental on AMO)

(Translate ~ (close to) 100% done)


(Mozilla is in control from this point onward)
Do productisation (needed to be in Beta?)


Beta
Fixes

Snippets, Mozilla.com web pages

Official release


Fennec


  • 244 string/1076 words
  • Similar process to Firefox
  • Mozilla is doing localised builds

Testing/Review/Validation


TODO: Complete in Wednesday morning session

Infrastructure


  • Interested languages must have a locale
  • How to handle verb-noun ambiguities

Provide the Mozilla l10n files


  • L10n files: .dtd and .properties files used by Mozilla
  • Use po2moz/other script to create PO files for language teams (daily)
  • Copy to downoad area (document URL)
    • Host at download.locamotion.org, to be done by Friedel and Walter
  • Split up build_ff_langs.sh into l10n->PO and PO->l10n files
  • CGI application to request generating the Mozilla l10n files
    • Errors to be sent to mailing list
  • 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

Language Packs


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

Terminology


  • One file for Pootle and Virtaal
  • One file for Firefox
  • Document tips
  • Monitor terminology projects for each of the language teams
  • Discuss with Martin on the best approach if people want to modify terms on the terminology list
  • DIfferent starting points for languages that are part of the terminology project and those who are not
    • Convert from GlossMaster with new script (extend csv2po), or
    • Create with poterminology
  • Untranslated terms to appear as part of the terminology list in Pootle and Virtaal (suggestion)

Guidelines for documentation


  • Do not add terms if you are not sure about it

Priorities


TODO: Complete in Wednesday afternoon session

Timeline


TODO: Complete in Thursday morning session

Marketing & distribution


TODO: Complete in Wednesday morning session

Documentation of the process


TODO: Complete in Thursday morning session

Terminology


  • If you unsure of a term, do not add it
  • Verb-noun ambiguities?
  • How to add terms
  • QA guidelines
  • Document Mozilla process

Partial translations (end September)


TODO: Complete in Wednesday afternoon session