Closed Bug 800550 Opened 7 years ago Closed 5 years ago
[sm] [Fx] New localization: Samoan
Samoan has been translated on Pootle over the last few weeks: http://mozilla.locamotion.org/sm/firefox/ The team has made good progress and where complete with all translations for the end of Aurora 17. The attached tarball is the state of these translations post the migration to Aurora 18 (although they have already translate many of these new strings).
OS: Mac OS X → All
Hardware: x86 → All
Summary: New Localisation: Samoan → [sm] [Fx] New localization: Samoan
Good morning, I am the team leader for Samoan, please assist with getting Samoan into Mozilla Aurora 18 or provide me with any requirements that I have yet to fulfill. I want to keep momentum up and have something concrete for my community to test/use. I have already translated most of the new strings for 18. Regards ChrisB
Comment on attachment 670536 [details] Samoan Firfox 18a2 Hi Chris, thanks for your work. There's quite a bit translation work to do still. My metrics show less than 60%, most localizations are above 80, good ones in the mid 90s. Dwayne can guide you to the next best buckets on locamotion. I also recognized a few translations that happen to be wrong localizations. In intl.properties, I found various translations of keywords, and in toolkit/defines.inc, "English (US)" is translated instead of saying "Samoan". I'd want you guys to go through the more technical details of the localization, and just extend the translation work, and then request review again. You can see the technical notes I go through on https://developer.mozilla.org/en-US/docs/Localization_technical_reviews, if you want to read along. I'm not sure if 18 is a realistic target, I'd favor having some time to build up users on aurora before going to beta.
Attachment #670536 - Flags: review?(l10n) → review-
Hello, thanks for the reply, I'm not sure about the under 60%? Can someone let me know what I'm missing please. My count is 90% completed. I think 18 is a very realistic target for me, I'm very keen and committed, and I already have users/testers in 2 countries. I have had 2 news articles on my work where I mentioned the Mozilla as well locally and another in progess OS interest is high, and a lot of people are just waiting for it to be available. My other accomplishments are spreading the Mozilla project far and wide. I want to keep momentum up. I just need to be shown what I need to focus on and then I'll get it done. I'm allocating 2 weeks to complete Mozilla Firefox, then I'm moving on to another language. So any technical assistance would be appreciated. Regards ChrisB
Axel -> I'd propose Samoan in 18 but looking at a review before it goes out the gates into beta. That way at least Chris has an easy testing platform. Chris -> Axel's 60% is based on his scripts that will only count translations, so a copy of en->en will not count. I did a quick check on your strings there are a number that should be translated and not left in English. You can use the 'unchanged' e.g. http://mozilla.locamotion.org/sm/firefox/user1/translate.html#filter=checks,unchanged I'd suggest going through each goal in the order of priority and checking those. Obviously some things should remain unchaged but e.g. http://mozilla.locamotion.org/sm/firefox/user1/translate.html#filter=checks,unchanged&unit=1746610 should really be translated.
(In reply to Dwayne Bailey from comment #4) > Axel -> I'd propose Samoan in 18 but looking at a review before it goes out > the gates into beta. That way at least Chris has an easy testing platform. Sorry, we should get the technical issues fixed before doing builds. We're very short on resources (I'm on vacation already, Milos has 4 new localizations to drive) for 18, adding code that breaks the web and may or may not be caught later doesn't sound like a good idea.
Ok, done the one you pointed out and some of the rest, will have them all done by tomorrow night. I need to go to work now, so anything else, just let me know and I'll sort it out when I get back to the workshop. regards ChrisB
This is a new tarball of all translations for Aurora 18. This passes compare-locales and I think all other technical issues are addressed. Translation state is very good, essentially everything is done and we're at 99% translated. 1131 units are unchanged i.e. same as en-US, there are some that I think should be translated but on the whole the ones that aren't are in most cases highly technical so probably best left in en-US. Missing strings are in mobile, security and notnb goals - so not important for an average desktop user.
Attachment #682391 - Attachment description: Urdu Firefox 18a2 translations v2 → Samoan Firefox 18a2 translations v2
Pike, Can you please look this.
Pike, Can you please look at this.
Comment on attachment 682391 [details] Samoan Firefox 18a2 translations v2 Sorry for the lag, I expect that the status quo changed a good deal from what's in this attachment, can I get an updated one to look at?
Updated to latest Aurora 21. There have been some, but not many, translation in 21. The translation status show mostly a good 20 completion but missing strings seem to be the new parts in 21.
Comment on attachment 722225 [details] Samoan Firefox 21a2 (actually sah, Sakha) Thanks for the update, .... and now for Samoan? (this was Sakha, sah, not sm)
Attachment #722225 - Flags: review?(l10n) → review-
Now with my head attached, the correct language.
Comment on attachment 723476 [details] Samoan Firfox 21a2 v2 Can I get a new attachment? In particular given that the export scheme changed, and as there's new contributions, that'd be useful. Thanks and sorry for the lag
Hello Axel, I haven't done a check for critical errors yet. Sorry. Only just got back into it after a long hiatus. In another week it would be a much better product. Regards ChrisB
Updated Samoan tarball as requested
Comment on attachment 8343698 [details] Samoan (sm) 27.0a2 2013-12-06 b10de71 r-, there are a bunch of technical problems with this patch. sm/toolkit/defines.inc shouldn't have a translation of English, but "Samoan". sm/toolkit/chrome/global/intl.properties: intl.accept_languages=sm, sm should probably be something ending in en-US, en, but for sure not double Samoan. font.language.group=x-sisifo That value doesn't exist in http://mxr.mozilla.org/mozilla/source/browser/components/preferences/fonts.xul. intl.menuitems.insertseparatorbeforeaccesskeys=Mo'i should be true, and not a translation thereof. Generally speaking, all of these have comments that explain what should have been the value.
Attachment #8343698 - Flags: review?(l10n) → review-
Chris, I've seen that there's localization work to do, and there's also a bunch of technical stuff to fix. We only have three weeks left on Aurora for 28, it seems that 29 might be a better target? How's the testing going?
Cleaning up, this bug hasn't seen traction since January. Resolving this INCOMPLETE for now, if there's renewed interest, please feel free to reopen. The questions from comment 21 would become open questions then again, too.
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.