User-Agent: Mozilla/5.0 (X11; U; Linux i686; ar-JO; rv:1.7.5) Gecko/20041107 Firefox/1.0 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; ar-JO; rv:1.7.5) Gecko/20041107 Firefox/1.0 Hi, I'd like to register for the Arabic l10n of Firefox, I've already applied for CVS (bug <a href=" https://bugzilla.mozilla.org/show_bug.cgi?id=278651">#278651</a>). Product: Firefox Language: Arabic Locale: ar-JO Name: Ayman Hourieh Email: firstname.lastname@example.org Web page: http://www.arabeyes.org/project.php?proj=Mozilla I'm already registered for Thunderbird by the way. Thanks. - Ayman Hourieh Reproducible: Always
Hmm, I see Bugzilla doesn't like HTML, how do you create bug links then? (Sorry for being off topic)
I added these information about Arabic l10n team into our wiki page - http://wiki.mozilla.org/L10n:Localization_Teams Since Ayman has already CVS access and there are no other obstacles, I would consider this bug as resolved.
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Linux → All
Hardware: PC → All
http://mozdev.org/pipermail/project_owners/2005-June/004966.html claims that "and the written form is pretty invariant" wrt to different arabic locales. Would it make sense to just go for ar as locale, as suggested on http://wiki.mozilla.org/L10n:Simple_locale_names?
It would be great if we can go for "ar" only as the locale, I had to choose ar-JO when I filed the bug because the simple locale names doc wasn't there yet or I wasn't aware of it. Yeah the differences are minor, and one locale would be sufficient I guess. I finished an initial translation for Firefox 1.1.x today, I was going to import it to "ar", now that the locales are extended.
Registration completed. Ayman, there is a huge list of things to fix, according to compare-locales. You want to update that until Friday, 8th, as can be seen in bsmedbergs post to .l10n.
Status: NEW → RESOLVED
Last Resolved: 14 years ago
Resolution: --- → FIXED
OK, I'll make sure it's all fixed before the deadline. I took a snapshot of the files like 2 months and translated them, now it's time to update. Any updates on the status of 1.0.x by the way? Thanks.
You need to log in before you can comment on or make changes to this bug.