Closed
Bug 439240
Opened 17 years ago
Closed 17 years ago
Thunderbird 3.0 in ta-LK - Tamil (Sri Lanka)
Categories
(Thunderbird :: Build Config, enhancement)
Thunderbird
Build Config
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 474781
People
(Reporter: iamsarves, Assigned: sipaq)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9) Gecko/2008052906 Firefox/3.0
Build Identifier: Thunderbird 3.0
We are from Sri Lanka and we already done with Thunderbird 2.x (bug id :420023) and now we would like to work on Thunderbird 3.0.
Reproducible: Always
Steps to Reproduce:
1.
2.
3.
Summary: We would like to have Thunderbird 3.0 in ta-LK - Tamil (Sri Lanka) → Thunderbird 3.0 in ta-LK - Tamil (Sri Lanka)
Updated•17 years ago
|
Status: UNCONFIRMED → NEW
Ever confirmed: true
| Assignee | ||
Comment 1•17 years ago
|
||
Hi Sarves, sorry for not answering earlier here.
Are you still interested in doing a ta-LK localization of Thunderbird 3? If yes, have you already started to work on it? How far along are you right now?
Assignee: nobody → bugzilla
Status: NEW → ASSIGNED
Hi Simon,
Its ok...
Yep, we have started on TB 3.0 and progressing on it. About 60% is done.
What should we do?
Tx, Sarves
| Assignee | ||
Comment 3•17 years ago
|
||
Great! Do you (or someone from your team) already have commit rights for hg?
Comment 4•17 years ago
|
||
The bug 420023 (https://bugzilla.mozilla.org/show_bug.cgi?id=420023) contains some relevant info. And I have attached TB3 (Alpha3) l10n files of which ~40% completed.
Sarves, you may use those files to do string-translation further and apply latest string changes to those.
Rohana, Thanks for compiling source files. Yep, we are progressing with the source files that u complied.
| Assignee | ||
Comment 7•17 years ago
|
||
Rohana, Sarves,
how far along are you at the moment with the Thunderbird 3.0 ta-LK localization? Can you please give me an update?
| Assignee | ||
Updated•17 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 17 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•