L10n/HomePage/Status/2009-11-18
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
pascal, axel, wil, timr, stas & sethb
Meeting Notes
Firefox / Fennec updates
Firefox
- 67 builds are green
- 9 missing strings for af, bg, ka
- 151 strings for es-MX, ku, mn
- lots missing for oc and sr
Need to figure out with Beltzner on what to do with some of the locales...
Fennec
- https://bugzilla.mozilla.org/show_bug.cgi?id=523296
- mfinkle is changing a string deep in toolkit
- Fixable, but not if we are string frozen on Firefox since this is also being used
- Can't change the key for this bug
- Axel suggests to effectively create a new entity used by the old entity
- File will always be messy
- https://bugzilla.mozilla.org/show_bug.cgi?id=528655
- Stas has to review each and every description entry in existing plugins
- Have never used in Firefox
- Have changed the meaning
- Adding one more string that we have a very difficult time tracking
- Compare locales does not check this string
- Change in UI breaks the way we do search engines
-
Can no longer put the search in list.txt file because it refinances the specific search XML filesthat works (Axel) - Effectively we need to fork every locale, plus commonly reused plugins like google
- We can pull en-US for search plugins
-
- Every localizer needs to clone the en-US plugin to reuse it in their localization
- Stas has to review each and every description entry in existing plugins
Possible solutions --
- Scenario 1: Stas is not totally overwhelmed
- Description not being used anywhere else on the Web
- Maintaining it can also be tough
- Scenario 2: Back out change and keep it as is, but this can be hard because Fennec has been exposing this string
- Changed the description and we realized used it only because the string got changed it…
- Scenario 3: No productization in this release
- Scenario 4: Ship with existing <Description> and don't make the "Integrated" UI change
- Is the existing "Integrated" so critical that we need to translate it?
- Is it super critical to have it in en-US?
- Scenario 5: Removing any English text from description entirely
- Not good UI
Meta-feedback
- Adding 20+ strings in the last 48 hours
- Changing search engines is big problem
Web L10n
- FF 3.6 WN and FR localization has been started
- Updated webpages for Weave Sync branding
- Collecting SMS updates for Fennec
- Google Snippets
- TB3 ongoing work
- Patch for FF 3.6 beta 3 that fixes bugs that are not listed on Product Details for FF 3.6 beta 3
- bug 528572
AMO
- Started AMO 5.4 and freeze on November 26
- Python .po files are different than PHP .po files. clouserw working on script
Productization
- RSS policy: modified script
- Helped verify new suggestions so there are no hidden redirects
- de-beta is coming along nicely including this list.
Tools
- Sign-off app
- Confused on what to move to Amsterdam
- Gandalf and Axel have had a chat on what to work next
- LDAP auth review might be needed by clouserw
- Haven't made a whole lot of progress of https request for the load balancer
- Verbatim (with support for Verbatim, AMO, and SUMO) expected to go live today
Testing
- 15 locales are scheduled to get testing by Multilingual QA. Finalizing the list and seeking approval from shaver
- Working on test automation with consultants
- boxObject which exposes the geometric size, if boxObject of child goes over the size of the parent, then we get an error
- Fennec localization testing from Aakash