https://bugs.documentfoundation.org/show_bug.cgi?id=161258
--- Comment #4 from Eyal Rozenberg ---
(In reply to Stéphane Guillou (stragu) from comment #3)
I'm not suggesting that support for RTL-CTL and CJK be _always on_; I suggest
that the _default_ be on. That is, instead of applying a heuristic for
verifying it needs to be turned _on_, the heuristic will check whether we need
to turn it _off_. And only if we're sure it can safely be turned off - it will.
In other words, the "gray area" will be decided in favor of enabling support.
> I don't think all language support settings should be turned on by default
> for all locales
Stephane, you're making the assumption that the choice on/off for language
support is, or should be, simply a function of locale. I reject this
assumption. But even if it were true - there are locales which certainly need
RTL-CTL support on, locales which certainly don't, and locales in which it may
be necessary. And for those where it may be necessary, it should be turned on -
that's my point regarding the default. If we improve our heuristics, we can
move more situations from the "maybe" to the "certainly off" and "certainly on"
groups.
>, and would prefer if efforts were directed towards improving
> the automatic use of relevant settings depending on locale (if they don't
> work as expected currently, as in e.g. bug 161255), and clarifying/improving
> language support options, as in e.g. bug 104318 and bug 39935.
that would complement my suggestion.
> Of course, I understand the historical western-centric default is not ideal
> for many.
I will assume you meant to say "is not ideal, period".
> For example, it is not desirable to have something as prevalent as the Font
> tab of the Character dialog be split in two halves when that's not going to
> be useful to the user, ever.
... ah, perhaps you actually did mean that a western-centric default is ideal,
after all?
Nearly half the people of the world live their lives using more than one kind
of written language, typically their native one, and some West-European
language - English, French or Castillian mostly. That's true for most of Africa
and Asia (including Russia, although Cyrillic can't currently benefit from the
dialog being split.)
For those users, a split is desirable (or some other future arrangement if we
switch to more complex font choice schemes as per bug 151215). If we can't say
for sure whether the user only uses Western languages or not - we should split
the dialog, rather than requiring the user, especially the newbie user, to have
to locate the appropriate LO language option to be able to work.
To reiterate: Minor inconvenience for westerners must not trump major
inconvenience to non-westerners.
> (Wondering in passing how feasible it would be to add a tick box to "turn
> off" Western/LTR support so it isn't the default anymore...)
Filed bug 161523 (although ability-to-turn-off and being the default are two
different things.)
--
You are receiving this mail because:
You are the assignee for the bug.