The Hungarian 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 The number of changes here is moderate, but not outlandish * "225 entries missing in existing files, 877 entries missing in new files" [2.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 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. p.s. András, I tried to Assign this bug to Kami per https://wiki.mozilla.org/L10n:Teams:hu but his e-mail does not seem to be in our bugzilla. Also I was unable to (quickly) join http://tech.groups.yahoo.com/group/mozilla_hu/ to report this there (though I understand only English)
AFAIK Kami is working on it. I asked him to take this bug.
Yes, I am working on it. Please assing to bug to me, thanks! KAMI
After first update the status is: Locale Tree % Errors Missing Warnings Reported Obsolete Unchanged Web bugs hu sea_aurora 85 3 66 6 0 50 1317 1 (1)
I plan to update translation today.
First, complete translation for UI is ready. https://l10n-stage-sj.mozilla.org/builds/builders/compare/144927 Build properties: branch releases/l10n/mozilla-aurora buildername compare buildnumber 144927 en_branch releases/comm-aurora en_revision 01ee10211fe3 l10n.ini suite/locales/l10n-aurora.ini l10n_branch releases/l10n/mozilla-aurora l10n_revision be40a4e2c6e8 locale hu revision be40a4e2c6e8d250482878a90d57dd78815d955e revisions ['en', 'l10n', 'services_sync'] services_sync_branch releases/mozilla-aurora services_sync_revisi 210714b766cd services_sync_revisi 210714b766cd slavename cs tree sea_aurora Bugfixes may possible.
Status: NEW → ASSIGNED
Thank You, Our aurora builds are still busted however, (searchplugins related -- not caught by the compare-locales) make: *** No rule to make target `dmoz.xml', needed by `libs'. Stop. See the related fix used by tr/ (Turkish) http://hg.mozilla.org/l10n-central/tr/diff/8433fd332c1d/suite/searchplugins/list.txt Also feel free to see the build-log for your locale which shows up at http://ftp.mozilla.org/pub/mozilla.org/seamonkey/nightly/latest-comm-aurora-l10n/ (look for |hu| locale code, and the later build#, we don't do a good job cleaning up yet)
Ok I also get up beta to work on both paralel. I will check the file list.txt. When is beta deadline? I will try to finish all related work this week (including the weekend).
list.txt fixed on beta and aurora too. Should I convert the old plugins to the new format?
I am hoping to spin beta 3 in about 24-36 hours, final is to be released monday evening (so a final build sunday evening) I am *hoping* to do the b3 and final with the same locale list of course! (In reply to comment #8) > list.txt fixed on beta and aurora too. Should I convert the old plugins to > the new format? KaiRo, you know more about this part, answer?
(In reply to comment #8) > list.txt fixed on beta and aurora too. Should I convert the old plugins to > the new format? You can do what you like there, as long as you follow the guidelines I set up in https://wiki.mozilla.org/SeaMonkey/Localization/SignoffChecks - if you need any other than the default ones (which you only need to list, not copy), it's usually better to take newer ones off e.g. mycroft.mozdev.org than to rewrite the old ones yourself.
kami, from where I sit, the reason I filed this bug is now resolved. If you want to use this to track more stuff that is fine by me, otherwise we can RESO/FIXED this. Thank you again.
Then we can close it.
Status: ASSIGNED → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.