428622 - Registration of Burmese Language Team (my_MM)

Status: RESOLVED INCOMPLETE

(Mozilla Localizations :: Registration & Management, defect)

Description

[Wunna Ko Ko]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.13) Gecko/20080313 SeaMonkey/1.1.9
Build Identifier: 

1. ISO code: my
2. Language name : Burmese
3. Language Users : People mainly in Myanmar, Some in (Singapore,
Thai, United States, Australia)
4. Script info.:
4.1 Script name: Burmese/Myanmar
4,2 Writing direction: Left to right in horizontal lines.
4.3 Additional details: can also be found by visting
 http://en.wikipedia.org/wiki/Burmese_language
 http://en.wikipedia.org/wiki/Burmese_alphabet

Reproducible: Always

Steps to Reproduce:
1.
2.
3.

Comment 2

[Rimas Kudelis [use needinfo to ping]]

Welcome to the community!

Please read this http://developer.mozilla.org/en/docs/Create_a_new_localization. It explains what needs to be done to start (or rather, to register) a new localization. One of the things you'll have to do is to actually localize one of the Mozilla applications. I think, currently it would be Firefox 3, or Thunderbird 2, or SeaMonkey (not sure about the version).

By the way, if there are no different dialects (variants, like in case of Spanish, or English) of Burmese, I think you can omit "-MM" from your locale name, leaving only "my".

Comment 3

[Mic Berman]

per comment #2, versions for Firefox is correct, you should start with Firefox 3.0. Also we use IRC channel #l10n for questions. i am a driver and my nick is "mic" on IRC if you have any questions :)
and that link in comment #2 is the right place to start. You can also get some other good information here: http://wiki.mozilla.org/L10n

Comment 4

[Ngwe Tun]

thanks for accepting Burmese Language Team in Mozzila. We will start according to Comment #2. Cheers.

Comment 5

[Axel Hecht [:Pike]]

Please don't use the MDC page.

That's an old page which we haven't gotten to kill yet.

http://wiki.mozilla.org/L10n:Localization_Process is the newer page, but that pageset as well hasn't been updated for Firefox 3 yet.

Sorry for that, but we're currently stuck in shipping the thing and didn't get around to documenting the new things.

As a side remark, we're only registring teams once we have work reviewed, so until we see an attachment of a localization source, a registration doesn't happen.

I want to second Rimas' question about the locale code, your initial comment sounds like just using 'my' should be fine.

Comment 6

[Axel Hecht [:Pike]]

Un-duping the SeaMonkey bug. There is a lot of shared code, so it'd be good to see Ngwe Tun and Wunna Ko Ko join forces, at least on the toolkit parts. But the two requests are not the same thing.

Comment 7

[Ngwe Tun]

(In reply to comment #5)
> As a side remark, we're only registring teams once we have work reviewed, so
> until we see an attachment of a localization source, a registration doesn't
> happen.
let me know detail explanation of your mentioned a localization source. I'm very new to make Language Pack. We have un-organized localization sources. But I do not know well how to pack and sent it to community.

Cheers. Thanks for valuable input.

Comment 8

[Rimas Kudelis [use needinfo to ping]]

Ngwe,
The detailed information is provided in the following pages:
http://wiki.mozilla.org/L10n:Localization_Process ,
http://wiki.mozilla.org/L10n:Starting_a_localization ,
and especially in http://developer.mozilla.org/en/docs/Creating_en-X-dude (substitute 'my' for 'en-X-dude' here). Also, in pages linked from these. This is easier to do on Linux than on Windows though.
Also, don't forget to join #l10n on irc.mozilla.org for more interactive help. :)

Comment 9

[Wunna Ko Ko]

It is a little bit complicated. In order to join our forces, Ngwe Tun & me and I hope there are many others, I think we need to setup a project and build the team first.

I think Ngwe Tun already prepared http://wiki.mozilla.org/L10n:Teams:my. We need a mailing list to discuss the efforts. Else different people will be working on the same issue. Like Ngwe Tun will be working on SeaMonkey (for example) and if others can know it, they will work on different issue, firefox (for example).

So, I think it is better to have registered first before submitting a patch.

Comment 10

[Axel Hecht [:Pike]]

(In reply to comment #9)
> It is a little bit complicated. In order to join our forces, Ngwe Tun & me and
> I hope there are many others, I think we need to setup a project and build the
> team first.

Right.

> I think Ngwe Tun already prepared http://wiki.mozilla.org/L10n:Teams:my. We
> need a mailing list to discuss the efforts. Else different people will be
> working on the same issue. Like Ngwe Tun will be working on SeaMonkey (for
> example) and if others can know it, they will work on different issue, firefox
> (for example).

It's a little unfortunate that the initial commenters here didn't point you at the right docs right away (and that I didn't jump on this earlier, no idea where that bugmail went).

The things to know about your team should be on above wiki page, the "registration" part of things is really just taking that one team up into a release process for an official version of Firefox. Registration of a localization team doesn't come with a mailing list, either.

There are many choices out there that you can choose from to open up a discussion forum: There's mozdev.org, google code, too. There are a few localization teams with mailing lists in our setup, which have newsgroup/mailing-list/google group mirroring, the downside of those is that they usually have a bit of back and forth until they are up and mirroring.

Which of those you choose really depends on what features you want, and where you feel comfortable.

http://groups.google.com/group/mozilla-ro is one on google proper, http://www.mozilla.org/community/developer-forums.html#dev-l10n-cs shows the examples in our setup.

> So, I think it is better to have registered first before submitting a patch.

I really think you're expecting registration to do things that it doesn't do, I hope my previous comments cleared that up.

Comment 11

[Wunna Ko Ko]

Thanks  Axel Hecht,

I got a bit clear. In order to confirm my understanding, the following is what we should do:

- Create a project at somewhere (google code or mozdev or sourceforge). They will provide mailing list as well as CVS host.

- Once the localization is prepared, create a patch and submit to mozilla by filling an issue.

- The informations on us can be put on http://wiki.mozilla.org/L10n:Teams:my.

If any of above is wrong, pls correct it.

Comment 12

[Axel Hecht [:Pike]]

That covers it, yeah. Just that the initial source for review should go into this bug, as a tar.gz without dictionaries (extensions/myspell), as that's the smallest in size.

Comment 13

[Ngwe Tun]

AFAIK, Mozilla set Burmese Language Team (my). I've created wiki page. http://wiki.mozilla.org/L10n:Teams:my.

And I'm waiting approval by Admin of mozdev.org. Here is my project detail.
PROJECT DETAILS
projectName: Burmese
projectDescription: Burmese Language Pack
ownerName: Ngwe Tun
ownerEmail: [e-mail]
bugzillaComponents: L10n

After approval of mozdev, I will organize contributers and keep going further implementations in Burmese Language Pack.

We are going to localize Firefox 3 first, and Thunderbird and SeaMonkey sencond, Other Units should be last prior.

I'm learning other neighbour Language pack and their route in Firefox. Here is one example. http://www.isriya.com/node/300

Cheers. Thanks for valuable input.

Comment 14

[Seth Bindernagel]

Hi Wunna and Ngwe:

Hope you are doing well.  I am not sure where you are in your localization effort at this time.  Have progressed with your translation work on FF3?  If so, thank you for all of your work at localizing.  We're at the unique point of determining if you should localize for Firefox 3 or move onto localizing for Firefox 3.1, depending on your availability and interest.

If you are interested in working on *something* that is stable, you can continue to focus on localizing Firefox 3.  We can get stable builds going for you.  However, we will eventually ship your work in Firefox 3.1 and you will need to update the effort you are putting into Firefox 3 right now.  The good news is that the string changes from Fx 3 --> Fx 3.1 are presently small in number (~30), so the update should not be too much too handle.  

However, if you are interested in moving your effort toward localizing Firefox 3.1, then you can read the following documentation on working with Mercurial and getting a local environment set up on your machine.

http://developer.mozilla.org/en/L10n_on_Mercurial

or learn the basics about Mercurial here:

http://developer.mozilla.org/en/Mercurial

Thanks so much for your hard work.  As always, ping us with any questions, we are ready to help.

Kind regards,
Sethb

Comment 15

[Axel Hecht [:Pike]]

I don't see a lot of activity in this project lately, so I'm resolving this INCOMPLETE.

If there is activity again, please feel free to reopen or file a new bug. Thanks.