Figure out how to handle locale-specific UI exceptions

RESOLVED WONTFIX

Status

RESOLVED WONTFIX
3 years ago
10 months ago

People

(Reporter: nefzaoui, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

3 years ago
Bug 1176832 triggered the initial conversation.
(In reply to Sam Foster [:sfoster] from comment #13)
> I talked with :nefzaoui about this. So the problem is that arabic characters
> do not italicize well, and for arabic language locales we should avoid them.
> As of today as far as FxOS is concerned, its true to say that RTL==arabic,
> but these are different concepts obviously and I would rather not conflate
> them for all time in our codebase. So we have 2 not-mutually-exclusive
> options: 
> 
> 1) Use a [lang="ar"] selector to override the italic font-style where
> necessary
> 2) Develop and apply language-neutral UX that accomodates these quirks. 
> 
> I fully realize that 1. is not optimal - it begs the question what happens
> when another language comes along? In lieu of 2. I think its our best bet
> though, unless anyone else has other ideas. We should pick this up in a new
> bug though as this one is resolved.

We should be thinking about a solution for the *long term*, not only for this exception (italic text in Arabic) but for also other exceptions that we don't know about yet. Correct me if I'm wrong but ideally we would come up with a way better to handle per-locale style without being chaotic or causing code conflict for the locale-specific changes when original code changes.
(Reporter)

Updated

3 years ago
See Also: → bug 1176832

Comment 1

10 months ago
Firefox OS is not being worked on
Status: NEW → RESOLVED
Last Resolved: 10 months ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.