281838 - SeaMonkey: Arabic (ar-JO) project registration/change

Status: RESOLVED FIXED

(Mozilla Localizations :: Registration & Management, defect)

Description

[Robert Kaiser]

Name: Ayman Hourieh
Email: [e-mail]
Website: http://www.arabeyes.org/project.php?proj=Mozilla

We will keep using the same locale: ar-JO.

-------------

As for SeaMonkey, we have actually tried to contact Ahmad Twaijry
(which is registered in that page), he used to be the previous
coordinator, but the current email bounced, and the website was down.

More info in Arabeyes mailing lists:
http://lists.arabeyes.org/archives/general/2004/October/msg00043.html
http://lists.arabeyes.org/archives/general/2004/October/msg00046.html

Comment 1

[Robert Kaiser]

One question is open for me:
Should we use ar-JO like you do for FF/TB, or keep the previously used ar-SA?
Along with that, should we move the ar-SA project to the new maintainer or file
a new one?

Comment 2

[Ayman Hourieh]

As for the locale, the only reason I'm aware of for having more than one Arabic
locale is month names, other than that, it's all the same, Gnome for example
uses two Arabic locales, ar-LB and ar-EG.

Lebanon (LB), Syria (SY), Jordan (JO), and Palestine (PS) use one set of month
names, while the rest of the Arab world use another set.

I decided to stick with the previously used locale to not complicate things and
having one locale (ar-JO which is basically the same as ar-LB) is preferable for
me right now.

For the current situation, I prefer we start a new project for Seamonkey, most
likely I'll make use of Firefox/Thunderbird translation database to keep things
consistent instead of continuing the old translation. Firefox translation was
done from scratch.

Comment 3

[Robert Kaiser]

Changed project list at http://www.mozilla.org/projects/l10n/mlp_status.html
accordingly.
I hope in the future we once can allow locale names without a region part, so
that issue might dissolve then. Until then, I remarked that ar-JO was ar-SA
previously.