User-Agent: Mozilla/5.0 (Windows; U; Win98; ml-IN; rv:1.7.6) Gecko/20050317 Firefox/1.0.2
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; ml-IN; rv:1.7.6) Gecko/20050317 Firefox/1.0.2
CVS account request for Joyce K. Babu, member of the Malayalam localization team
for Firefox(versions 1.0.2 and 1.1)
Steps to Reproduce:
Need a CVS form to start the proces - www.mozilla.org/hacking/form.html. You
will need a voucher as well as an SSH key.
Joyce: are you going to be an owner of ml-IN team?
> Joyce: are you going to be an owner of ml-IN team?
I am the team leader
Created attachment 188750 [details]
SSH public key
I haven't received any response to my request all these days.. is this delay
usual ? or is it b'coz of some fault from our part ? plz reply...
Joyce: someone needs to vouch for you in this bug before I can activate your account.
Yeah,I know that. But how do I get someone to vouch for me ?
Joyce: Once gandalf, bsmedberg or someone in l10n reviews your code, they should
be able to evaluate your code and give me the approval to activate your account.
Joyce: please, attach zipped localization directories to this bug so I can
review them. (directory structure for trunk. Like -
Created attachment 191721 [details] [diff] [review]
Attaching the localized files
I have attached the localized files as instructed. I hope the files will be
reviewed. Hope I'll get an early reply.
Is this the correct directory structure? it has been downloaded from
cvs-mirror.mozilla.org:/l10n co l10n/pl..
The new localization files are uploaded at
http://prokerala.com/mozilla/ml-IN.zip . Please review the files. The base files
were downloaded from :pserver:email@example.com:/l10n co l10n/en-GB
I have localized about a thousand strings. Plz review. The files are uploaded at http://prokerala.com/mozilla/ml-IN.zip
I have completed localizing. Please review.
I'm on it
Can I know whether the review process is still on?
Hellooo! Can I know what is making the delay?
Joyce: This still has a voucher needed in the status whiteboard, need someone to bless it before I create your account.
We are terribly disappointed to see that no one has vouched for us even after such a long period. We started localizing Mozilla with the great expectation and hope that some day we will be able to dedicate the Malayalam Firefox browser and at the same time be a part (atleast a very small) of this(Mozilla) great foundation. But this delay and avoidance is downing our spirits. Is this delay because no new localizations are accepeted?? We started this project almost a year back.
I'd like to know which version this localization is for, checking against the
MOZILLA_1_8_0_BRANCH gives lots of errors, which is the branch that firefox 1.5
I see quite a few english strings glancing over the files, too.
bookmarks.html is empty, search engines are not localized, please take a
look at http://wiki.mozilla.org/L10n:Firefox_Extras for more information on the
Do you use Mozilla Translator or a descent tool/editor? I'm asking because of the
encoding of properties files, those can (and should) be just plain utf-8, not
the \u0000 foo anymore.
>I'd like to know which version this localization is for
Deer Park Alpha 2. I downloaded the original files from :pserver:firstname.lastname@example.org:/l10n co l10n/en-GB on october 20. I used the locale en-GB b'coz i had trouble downloading en-US files.
>I see quite a few english strings glancing over the files, too.
Due to lack of proper unicode support, some english strings when translated are difficult to read. We will do our best to find an alternative.
>bookmarks.html is empty, search engines are not localized
I am sorry. We will translate and upload the latest files at the earliest.
>Do you use Mozilla Translator or a descent tool/editor?
I use Mozilla Translator 5.04. Some of the files exported from MT when compared (with compare-locales.pl) with the original en-GB files gave many errors. Hence I manually edited those files using my text editor. Could you plz tell me if there is any other tool that I should use.
Joyce, I hacked MT to generate utf-8 encoded property files, you can find the
test build at
If you upload another version, please make something up to par with the
cvs -d:pserver:email@example.com:/l10n co -r MOZILLA_1_8_0_BRANCH l10n/en-GB
gives you a tree to compare to.
Thankyou for the reply and the tool. I am having my exams now. It will be over in 2 weeks. Once over I will translate the entire files once again and upload them at the earliest.
Joyce: Do we have a status update on this bug? Looks as if your last comment was back in February.
I am sorry that I couldn't inform. Soon after my exams, I was out of station for 3 month. On returning I got little busy with another project and I almost forgot about completing this. It is almost finished and just needs a few final touches. I terribly sorry for this mistake and will surely complete and upload the files within a week.
An additional comment/warning. We're closing out on Firefox 1.5 in terms of new locales, as 2.0 is just around the corner. For the purpose of this review, I'm not that picky which you submit, but I just want to tell you beforehand that there is virtually no route for further new locales on the 1.5.0.x release cycle.
Then shall I stop working on version 1.5 and start translating version 2.0 ? Will I be able to download the localization files from MOZILLA_1_8_0_BRANCH ? If not can you plz tell me where to download it?
I suggest working on 2.0, yes. You can get the sources from the MOZILLA_1_8_BRANCH. You may find bug 339000 useful, too, which should give you a bootstrap on what needs to be changed overall.
Created attachment 230270 [details]
Uploading the localized files for Malayalam Firefox(Bon Echo). Please review it.
Comment on attachment 230270 [details]
There are a bunch of untranslated strings in there, but the general structure is ok.
Marcia, I think this is ready to go.
Joyce, once this is up, you should land on the trunk first, and make sure that your line endings etc are right.
I'll double check then and then we should branch to the 1.8 branch. I'm not sure if this will be in time for 2.0, I expect this to take 'til a minor release, as a heads up.
Thanks a lot for vouching. I am sorry, I forgot the password I used for creating the SSH Key. Can I attach another key?
Comment on attachment 188750 [details]
SSH public key
marking old key obsolete, and please attach a new key
Created attachment 230596 [details]
New SSH Key
Attaching the new SSH Key.
Looks like everything is in place for this one. Over to server-ops for account creation.
Your CVS account has been created. Your CVSROOT should be:
Don't forget to set your CVS_RSH environment variable to 'ssh'.
If you have any problems connecting, let me know.
(In reply to comment #39)
Wrong repository. He needs access to /l10n on cvs, not /cvsroot.
(In reply to comment #40)
> (In reply to comment #39)
> > firstname.lastname@example.org:/cvsroot
> Wrong repository. He needs access to /l10n on cvs, not /cvsroot.
My bad - should be fixed now.
I'm sorry that i got deviated from this project. I didn't know what to do next. I tried to contact others at the l10n IRC but i was unable to get proper guidence as to how to proceed. I don't know how to connect to CVS repository using my cvs client (cvs tortoise). I tried to get help from IRC, but all users i contacted were using linux, so they couldn't help me. I sent a mail to Marcia requesting guidance, but i received no reply and very i'm sorry i got diverted from this project. I am very much interested in the completion of this project. It will be of great help if someone could advise me as to how i can revive and complete this project.
I have joined the team and would like to get cvs access (Joyce seems to have difficulty in getting cvs to work for him).
I'm attaching my ssh public key.
Created attachment 253575 [details]
My SSH public key (rsa)
My (Praveen) ssh key
Praveen: You can't use this bug to get access. If you want to get CVS access, you'll have to follow the same steps everybody else has to follow. Check out http://www.mozilla.org/hacking/getting-cvs-write-access.html for more information.
I have finally sorted everything out. Now I will be committing the localization to the repository soon.
Joyce, good to hear.
Praveen, if Joyce and you think it'll be good for the Malayalam localization for you to have cvs access, please file a CVS account bug. CC both me and Joyce and get Joyce to vouch. You need to fill out the CVS form, too, but the vouching is a little bit adapted for l10n accounts.
I'll back up the vouching by Joyce, though I may wait for the initial commit for Joyce to be locale owner in practice.
As discussed with Joyce, we're going for 'ml' as locale name, the '-IN' is not needed for Malayalam.