Localisation Processes

Localisation Methods


  • Online:
    • Localisers just need an account on the Pootle server
    • We can integrate the terminology lists as a project on Pootle server

OR

  • Offline:
    • Download PO file from the Pootle server
    • Translate with Virtaal/POEdit
    • Upload when they are done (needs an account on the Pootle server)
    • How can we integrate the terminology lists??

Glossmaster


Suggestions? (need to check with IT+46)


  • Single file per language
  • On Pootle server
  • Encourage to use PO

Pootle


  • 1 file ~ 1500 words (==> 12 to 15 hours)
  • Join translate-pootle mailing list
  • Online translation of Pootle allows for testing while translating

Virtaal


  • 3 files (virtaal.po, 1 for GTK (<200 words), 1 for gtkspell (12 words)) ~ 1500 words (==> 12 to 15 hours)
  • Locales are necessary to work (check how to add new locales if needed with Martin)
  • Encourage teams to submit their GTK translation through to GNOME project
  • Join the mailing list

Firefox


  • About 23000 words, some are very rare error messages and are very hard to translate, usually left untranslated
  • Localised copy is a different version
  • Language pack: similar to a Firefox extension that has enables a different languages to the current version used.

Jargon


  • Official release
    • Available on main web-site
    • Localised installer
    • Localised search engines, bookmarks
    • A release for each official language
    • Translated web-pages
    • Translated snippets
  • Language pack release
    • Is a step in the road for official release
    • On AMO (addons.mozilla.org) site
    • Install "Locale switcher" extension
    • Search engine, bookmarks, etc. in original language
    • Can be distributed on ANLoc website for testing
  • Productisation
    • Non-translation localisation (search engines, bookmarks webmail, etc. customization)

Translation timeline

|-
Stages
Language Team
Mozilla
Start Point

  • Register language team on Mozilla's wiki
  • Sign Mozilla contributors' agreement (required for VCS access)
  • Create Mozilla bugzilla account

Translate ~ 5k words?

  • Build 1st language pack
  • Put on ANLoc for testing

Translate ~ 10k words?

  • Build 2nd language pack
  • Put on Addons website
Mozilla approves language pack
Language pack on addons.mozilla.org

  • Get pack tested and reviewed
  • Report bug to request Mercurial access, attach translation files
First commit by Mozilla
Have Mercurial access
Report bug to request language to be added to product (FF)
Mozilla starts making the daily builds
Daily Builds

  • Check if it builds correctly on the dashboard
  • Start testing the installer, bookmarks, etc.

Translate ~ 100% done
Start work on productisation, Snippets, Mozilla.com web pages
Mozilla builds Beta (Mozilla is in control from this point onward)
End

  • Finalise productisation, Snippets, Mozilla.com web pages
  • Fixes
  • Perform Litmus tests
Official release

Fennec


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