Closed Bug 1142264 Opened 11 years ago Closed 10 years ago

[mozilla.org][ar]: localization needed for FFOS related pages

Categories

(Mozilla Localizations :: ar / Arabic, defect)

x86
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: CocoMo, Unassigned)

References

Details

You do need an account on Pootle to access the pages. **To Access files: http://mozilla.locamotion.org/ar/mozilla_lang/ 1) main.lang: http://mozilla.locamotion.org/ar/mozilla_lang/main.lang.po 2) mozorg/home/index.lang: http://mozilla.locamotion.org/ar/mozilla_lang/mozorg/home/ 3) firefox/os/index.lang: http://mozilla.locamotion.org/ar/mozilla_lang/firefox/os/index.lang.po 4) firefox/os/devices.lang: http://mozilla.locamotion.org/ar/mozilla_lang/firefox/os/devices.lang.po: 5) firefox/os/faq.lang: http://mozilla.locamotion.org/ar/mozilla_lang/firefox/os/faq.lang.po 6) firefox/partners/index.lang: http://mozilla.locamotion.org/ar/mozilla_lang/firefox/partners/ 7) legal/index.lang: http://mozilla.locamotion.org/ar/mozilla_lang/legal/ 8) tabzilla/tabzilla.lang: http://mozilla.locamotion.org/ar/mozilla_lang/tabzilla/ - As soon as the content is being pushed, the pages would be updated at least daily. ***To Test: - Pages will be available on the dev server in the meantime, e.g. https://www-dev.allizom.org/ar/firefox/os/ - the home page at: https://www-dev.allizom.org/b/ar/
Blocks: 1141927
Arabic is not working on Pootle, is working directly on SVN. I just need to add these page.
Files added in r139019, they should be available on the dashboard in a few minutes.
Flod, is projects/mozilla.com/trunk/locales/ar/firefox/os/index.lang (the older version) is still needed?
Unfortunately we can't remove the old file until we have moved all existing locales to the new one. Obsolete files like firefox/os/index.lang are hidden on the webdashboard though.
Flod, what happened to Arabic. I don't see it here: http://mozilla.locamotion.org/ar/.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.