Closed
Bug 384281
(land-ta)
Opened 18 years ago
Closed 16 years ago
Land Tamil localization on trunk
Categories
(Mozilla Localizations :: ta / Tamil, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: Pike, Unassigned)
References
Details
Attachments
(1 file)
25.25 KB,
patch
|
Details | Diff | Splinter Review |
I'm going to land the tamil localization on trunk and add it to the incubator.
There is apparently a good deal of work to be done still to get the localization ready to branch for a 2.0.0.x release.
The code I'm landing is a slight modification of attachment 194438 [details], I'll attach the corresponding diff to this bug.
Making this bug depend on the Tamil bugzilla component for now, so that we can move the bug once that's up.
Reporter | ||
Comment 1•18 years ago
|
||
The diff of what I landed is attached. Basically, I replaced region.properties with a current version from the MOZILLA_1_8_BRANCH, there were no localized entries in the original anyway. I removed the sherlock plugins and the reference to dictionary.com, that's not necessary for fx 2.0.0.x onward. We will have a separate bug to find out if there are good alternatives for search and rss readers for Tamil.
I replaced bookmarks.html with a current version, too, please translate the titles of the links. The links itself should be good.
I added Tamil to incubator, too, http://l10n.mozilla.org/buildbot/ will show new test runs within some 5 minutes of your check-ins. An initial overview of what's left to be done can be seen in the logs (stdio link) of the comparison step, for example, http://l10n.mozilla.org/buildbot/linux-incubator/builds/18/step-moz%3Acomparelocales/0.
http://lxr.mozilla.org/l10n/source/ta should show up within the next 24 hours, http://bonsai-l10n.mozilla.org/ has it already, see my initial check-in for example in http://bonsai-l10n.mozilla.org/cvsquery.cgi?treeid=default&module=all&branch=HEAD&branchtype=match&dir=l10n%2Fta&file=&filetype=match&who=&whotype=match&sortby=Date&hours=2&date=explicit&mindate=2007-06-13&maxdate=2007-06-14&cvsroot=%2Fl10n
Reporter | ||
Updated•18 years ago
|
Comment 2•18 years ago
|
||
Hi Axel,
I will work on this bug. please assign it to me.
Reporter | ||
Comment 3•18 years ago
|
||
Mugunth, please check in with Veera on this.
If the two of you have patches to land, I can land those, too, as long as Veera's setup is acting up. Attaching them here would work, for example.
Reporter | ||
Comment 4•17 years ago
|
||
Hi here, what's the current state of art for Tamil? I have seen check-ins by Veera 'til July 27th.
I fixed one regression by those check-ins just now, which reverted my fix to bookmarks.html, so now there are language packs for testing again, on http://l10n.mozilla.org/~buildslave/incubator/.
The current translation coverage is at 44%, so there seems to be room for further fixes.
Reporter | ||
Comment 5•17 years ago
|
||
The latest stats on l10n.mozilla.org are
http://l10n.mozilla.org/buildbot/compare/linux-langpack/734, which reports 548 entries missing in existing files, 399 entries missing in new files, and 37% changed, comparing against Firefox 2.
I wonder if we should drop Firefox 2 as a target for the Tamil localization.
What do you guys think?
Reporter | ||
Updated•17 years ago
|
Blocks: fx-l10n-ta
Comment 6•17 years ago
|
||
I use comparelocales.pl. Is there any better comparing tool?
It doesn't says any missing entries the last time I checked.
Reporter | ||
Comment 7•17 years ago
|
||
Yes, very much so. http://developer.mozilla.org/en/docs/Compare-locales is the tool to use.
That will give you a report similar to the one I linked to in comment 5, it's the same code running in the background, just with a stdout output.
Reporter | ||
Comment 8•17 years ago
|
||
I checked in a fixed version of bookmarks.html again. It'd be nice to not have to do that every time. Titles still need translation.
Comment 9•16 years ago
|
||
Pike, can we resolve this bug now?
Reporter | ||
Comment 10•16 years ago
|
||
Yep.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•