Closed Bug 667147 Opened 11 years ago Closed 4 years ago
Please consider updating Sea
Monkey localisation for locale Georgian
The Georgian locale was shipped in SeaMonkey 2.0 and changes to work in SeaMonkey 2.2 There will be no more SeaMonkey 2.0 releases. We want to create an update offer for SeaMonkey 2.0 users on this locale to 2.2 [or 2.3 if you are unable to update in time] once shipped. Final spin for 2.2 is in ~1 week, and is off the l10n/mozilla-beta Mercurial branch. Signoff https://l10n-stage-sj.mozilla.org/shipping/dashboard?av=sea2.2 Failing time to complete in time for SeaMonkey 2.2, our 2.3 release will be about 6 weeks later, coming off the "rapid release train" with Firefox 6/Thunderbird 6. See current status of that tree at https://l10n-stage-sj.mozilla.org/dashboard/?tree=sea_aurora The changes against 2.2 are large, but not insurmountable and while the deadline for 2.2 is quite close we would appreciate you updating in time, failing that you should be able to complete in time for 2.3! * "1180 entries missing in existing files, 1177 entries missing in new files" ** Many of those are also entries from Core Gecko/Firefox. If you are no longer able to continue doing localization for our product, please let us know and we (SeaMonkey, with a bit of input from you) can decide on the best way forward for any of our combined users on your language and our EOL'd branch.
Gia Shervashidze, any thoughts/progress on this front? (of course I notice you are behind on Firefox signoffs as well) Pike what is our story on the Firefox front for this locale, ADU's etc.?
(In reply to comment #1) > Gia Shervashidze, any thoughts/progress on this front? (of course I notice > you are behind on Firefox signoffs as well) > > Pike what is our story on the Firefox front for this locale, ADU's etc.? ping, Pike. Peeked at the l10n dashboard and looks like the last Firefox we shipped with this locale was 3.6 as well. So what is our plan here?
I don't have a plan, tbh.
Punting to 2.5, if not resolved or no response by then, I plan to morph this to removing |ka| from our [current] automation entirely (all-locales)
(In reply to Justin Wood (:Callek) from comment #4) > Punting to 2.5, if not resolved or no response by then, I plan to morph this "tracking-seamonkey2.5: +": overdue now. > to removing |ka| from our [current] automation entirely (all-locales) SM 2.0 shipped ka, SM 2.1 to 2.6 did not. Afaik, SM 2.0 updates are to SM 2.4.1 (only). Hence, do morph this bug. (sadly)
Since the ka locale build is no longer up to date with the current SeaMonkey, and rather leaving your users stranded on a very security-vulnerable release, we plan to update your users to the most-current en-US build. If you disagree, please get in touch with us ASAP along with an estimate for when your locale will be shippable again.
my problem is - pushing the localization (seems TortoiseHG ignores me) no problems with localization - can provide aggregated (aurora & comm) latest version during next 3 days if one could be so kind to upload it...
Sure, if you are willing to (continue) to provide patches/diffs for ka, we can ensure it gets pushed. We should (seperately) work to get your HG access restored though.
well... You can find latest version of aggregated ka here: http://giasher.nekeri.net/ka_all_06162012.zip sure there could/must be (i hope - few) problems as for HG access - its restored, but seems i miss some stupid setting in configuration and have problem with committing Thanks
Gia: Did you resolve your hg problems?
Gia: ping, you still interested in this? :-)
unfortunately not, even after kind help from Pasacal https://bugzilla.mozilla.org/show_bug.cgi?id=834235 one can find latest full Georgian l10n version for (February 2013) here: http://giasher.com/ka_UTF8.zip
"unfortunately not" was the answer to question regarding resolving HG problem
(In reply to Gia Shervashidze from comment #13) > "unfortunately not" was the answer to question regarding resolving HG problem The bug you linked was strictly about svn (which is for websites among other things) (In reply to Gia Shervashidze from comment #12) > one can find latest full Georgian l10n version for (February 2013) here: > http://giasher.com/ka_UTF8.zip Sadly we can't commit to updating the l10n ourselves via a zip, I'm happy to help work with you directly to get your access straightened out, please see me on IRC (irc.mozilla.org/#seamonkey) or e-mail me directly, and we can arrange figuring this out. I'm also open to Skype/Vidyo video calling if it helps you (and you are able to communicate in spoken English) [I'm off to bed at this moment though, so unable to help tonight]
@A.C. You're currently the only translator for Georgian, so you already have a ton on your plate. Should we drop Georgian from SeaMonkey and Thunderbird? https://l10n.mozilla.org/teams/ka
> Should we drop Georgian from SeaMonkey and Thunderbird? > https://l10n.mozilla.org/teams/ka So, to be precise, there are 800 missing strings in SeaMonkey and 1300 strings in Thunderbird, or those numbers don't measure progress of the translations? I meant, if these projects are partially translated, then I can try to finalize them to preserve previous localizers' work. But, if I have to start translating from the beginning, I think, I won't manage to do it.
If we add the projects to Pontoon, it will reflect the current status in the repository, you don't have to start from scratch: - Thunderbird: ~1400 strings missing out of ~8000 total strings. - SeaMonkey: ~800 strings missing out of ~7300 total strings.
OK, then I'll do it. You can add them to Pontoon.
Added (Lightning is a piece of Thunderbird). Consider them lower priority projects, also be aware that they basically ship on a ESR cadence (every 6 Firefox releases). https://pontoon.mozilla.org/ka/ Ian Neal is in charge of SeaMonkey l10n, while Philipp Kewisch [:Fallen] is in charge of Thunderbird, in case you have any questions.
Assignee: giasher → georgianization
Looks like SeaMonkey is at 100%, closing this bug.
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.