400928 - [tt, crh] Tatar localizations: Firefox, Thunderbird, Mozilla, SeaMonkey, SunBird, Minimo

Status: RESOLVED INCOMPLETE

(Mozilla Localizations :: Registration & Management, defect)

Description

[Reşat SABIQ (Reshat)]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.7) Gecko/20070914 Firefox/2.0.0.7
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.7) Gecko/20070914 Firefox/2.0.0.7

This is for localization of the following:
Firefox, Thunderbird, Mozilla, SeaMonkey, SunBird, Minimo.

Name: Reshat (Reşat) Sabiq
email: tatar.iqtelif. i18n  @  gmail.com


Reproducible: Always




I've been busy lately, so sorry for not following up in time on the previous entries. As long as there is the mozilla project, and these languages, there will be interest in localization.

Comment 1

[Gervase Markham [:gerv]]

Reshat: If you want to get involved here, you need to read this wiki page:
http://wiki.mozilla.org/L10n:Starting_a_localization

Create yourself a wiki page for your localisation, which registers you as the
team for that language. Then, follow the instructions on the wiki to produce a
language pack you can distribute through addons.mozilla.org. Once you have
reached that stage, we can consider your pack for official status - although I
should warn you that this is a separate process with its own complexities.
Still, the community will still be able to get your pack from
addons.mozilla.org in the meantime.

If you have read carefully and find the documentation isn't good enough in any
way, please let us know and we will improve it.

Gerv

Comment 2

[Reşat SABIQ (Reshat)]

Thanks for your feedback. 
Yes, i'm roughly aware of the steps involved, and started off by using that or a similar page's instructions. I have 1 add-on listed so far.

Comment 3

[Seth Bindernagel]

Hi Reshat:

Hope you are doing well.  I am not sure where you are in your localization effort at this time.  Have you decided to move to Firefox 3?  I hope so because we have started our "major update" for all users from Firefox 2 to Firefox 3.

If you have begun work on FF3, 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 4

[Axel Hecht [:Pike]]

I haven't seen a lot of activity here lately, thus I'm going to resolve this INCOMPLETE.

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

Comment 5

[Reşat SABIQ (Reshat)]

Hi,

Sorry it took a while to follow up. I've been working on other projects for a while, and this has been on my TODO list. One of the reasons why this dropped on my priorities list is bug
55366 (or 464414). I'd be a lot more motivated if i knew that bug was on its way to being fixed. My lang-pack extension ensures better privacy for users than they are going to have with a native build until this bug is fixed. If you can throw any weight towards fixing that bug, i'd highly appreciate it.
Nonetheless, mozilla i18n will be one of my highest priorities for the rest of the year.

Let's start by setting up the following locale for firefox:
crh
OR
crh-UA.

I've checked out mozilla-1.9.1 (which if i understand correctly includes xulrunner and firefox, as in Ubuntu packages), and tr locale as an example to look at. I guess i just need to structure the folders to match, say, tr locale, which i'm guessing my language pack probably already does for the most part (minus pending 3.0->3.5 conversion), and once crh or crh-UA locale is set up i'll need to check it in (push). Hopefully we can get a tentative native build done in the near future, and take it from there. 

I would hope that bug 55366 is fixed before a fully localized native build for Crimean Tatar (Crimean Turkish) is released, but even if it's not fixed, i guess i have little choice but to work towards a fully localized native build by the end of this year.

P.S. Please let me know what's needed for hg access. 
I now use the following email address, if one is needed:
tilde . birlik at gmail dot com
I can also upload a public key, if needed.
P.P.S. Not sure if UNCONFIRMED is the right status for this bug. Please let me know if you'd rather have me log a new one.

Thanks.

Comment 6

[Seth Bindernagel]

It's my personal guess that Bug 55366 is not going to get resolved any time soon.  If that is continues to block progress on this bug, then we'll resolve this as incomplete for now.

Ideally, the choice would be up to the user, if they want to use an eventual  Tartar version (language pack or official build) or not.  If you are willing to work on the version to get us *something*, we can move forward, but it is really up to you at this point.

Let us know how you would like to proceed.