L10n/HomePage/Status/2009-10-14
From MozillaWiki
< L10n
« previous meeting | index | next week »
Meeting Details
- 9:00 AM Mountain View Time (UTC -7)
- 650-903-0800 x92 Conf# 206 (US/INTL)
- irc.mozilla.org #l10n-drivers for back channel
- (notetaker: sethb)
Attendees
axel, sethb, clouserw, gandalf, timr
Meeting Notes
Firefox / Fennec updates
Web L10n
- Mozilla Europe in Serbian released just after MozCamp
- Mozilla Europe in Bulgarian should be done by the end of the month
- Caitlin sent her last edits to Fennec pages to Steven yesterday, hopefully Pascal can (re)-start QA for them tomorrow night
- Thunderbird team have difficulties providing stable content for localization, hopefully they will have this done by the end of the week
- Bugs for 3.6 pages (in-product and product) filed, apparently lmesa leads the in-product pages and Tara the product ones, very early stages, no final content yet
- Looks like marketing is thinking of a minisite for 5 years of Firefox
- JDLL event in center of France this week (Thursday to Saturday), lots of French speaking mozillians coming (17), we are turning that into a mini-mozcamp with booth, conferences and activities around it (l10n sprint for AMO, bug triaging for Thunderbird/Kompozer, fun activities around 5 years of Firefox...)
AMO
- AMO 5.2
- Roughly all locales are behind by ~500 strings
- Danish, Spanish, Polish are up-to-date
- AMO has more strings than any other project
- Every release has about 60 strings
- 85% of strings are developer hub
- Enabled Adrian's l10n validator
Stuff AMO team could do better:
- Release schedule only allows teams to push every 3 weeks
- Mismatch in waiting for l10n and how fast the AMO team wants to move
Productization and de-betaing
- Stas sick today, but covered in yesterday's bug triage call
Testing
- Update on multi-lingual QA
- Need to communicate our strategy better
- Here is one attempt: http://people.mozilla.com/~timr/L10n/L10nQAStrategyDiagrams.pdf
- Other ideas with MultiLingual QA
- Add locales
- Get them testing on the locales we have already examined
- Test planning for locales
- Mobile testing
- Website testing
- They have a file format that they use to do tests, but they haven't been quite clear on what they use to test. Could be XLIFF.
Tools
- Signoff App: Bugs needing to be filed
- Need some form of review from web-dev
- Need to make sure the thing stays up
- Need a development agenda/plan
- Not clear how we work to 1.1
- Set up a development environment