On 04/02/14 17:32, Axel Hecht wrote:
On 2/4/14 5:17 PM, Fabien Cazenave wrote:
Dear all,
TL;DR: the RTL support and Arabic locale are broken at the moment, but
we could fix it rather quickly — and it would be nice to do so.
We used to be RTL-proof in the very early ages of this project and the
Arabic locale was in quite good shape. But as we focused on the
“official” 1.x locales, we lost traction on Arabic and RTL — most apps
don’t display well at all in RTL mode now.
Here’s the wiki page and tracking bug for the RTL support:
https://wiki.mozilla.org/L10n:B2G/RTL
https://bugzilla.mozilla.org/show_bug.cgi?id=906270
Ahmed Nefzaoui (Tunisian contributor) has started working on RTL patches
and he’s done a very good work so far.
https://bugzilla.mozilla.org/show_bug.cgi?id=883673
https://bugzilla.mozilla.org/show_bug.cgi?id=833401
My opinion about that is that’s it’s a bit of a chicken-and-egg problem:
we won’t get proper RTL support without supporting Arabic (or Hebrew)
officially, and vice-versa.
Suggestion: what about promoting Arabic to an “officially supported
locale” status, include it in our test builds, and get some help from
the Arabic-speaking community to report RTL issues and propose fixes?
Ahmed suggested to organize a localization sprint for Firefox OS during
the next Arabic Mozilla meet-up. I think it would be a great opportunity
for a couple Gaia developers and UX engineers to meet the Arabic
community and land the most important RTL fixes while the translation is
being done.
Thoughts?
:kazé
I'm happy to see motion on both Arabic and RTL.
Regarding the localization status, though, there's no such thing as
mozilla-supported builds to begin with. As for other status indications,
Arabic has and had all branch repositories, it's included in all
language files, so builds like those for the Keon do include Arabic.
Not sure what we can do more on the localization front.
It does make a difference when a locale is a 1.x-target or not. No
RTL-specific bug will be addressed properly if it’s not a blocker, and
it will only become a blocker if we have an RTL locale in the, say, 1.4
targeted locale list.
I understand it’s a product decision. CC’ing Chris Lee.
It should make a difference to commit to RTL support on the engineering
front, though. Adding a pseudo-localization for RTL on top of
https://bugzilla.mozilla.org/show_bug.cgi?id=900182 would help, and get
us out of the chicken and egg between coders not having a complete RTL
locale available, and not being able to interact with it.
Axel
FWIW, we’ve started to add an RTL checkbox to the building blocks, in
order to test them in “RTL-English” mode. I’d prefer to rely on a real
Arabic locale to have a better user feedback, but having an
“RTL-English” locale would help too!
:kazé
_______________________________________________
dev-b2g mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-b2g
