https://bugs.documentfoundation.org/show_bug.cgi?id=162306

Eyal Rozenberg <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Blocks|109530, 162305              |
           See Also|                            |https://bugs.documentfounda
                   |                            |tion.org/show_bug.cgi?id=16
                   |                            |2305

--- Comment #5 from Eyal Rozenberg <[email protected]> ---
(In reply to Heiko Tietze from comment #4)
> How do you know whether the document continues with RTL text given the
> default PS is RTL following the locale settings? It's very likely IMO.

Actually, AFAICT, it is actually not likely for a text file starting with an
LTR paragraph to be mostly-RTL.

> Or
> let's think of the 'lazy fox' and add one RTL character, maybe an Aleph as
> list indicator. And what do you expect for the opposite, LTR locale
> receiving some الثعلب البني السريع text, hope this is correct, and
> Western/Latin default PS?

This is actually a challenge I face in my Thunderbird extension for direction
auto-detection. I cooked up a certain heuristic to make the decision, which I
could elaborate if you like.

> Ultimately not a topic for UX but RTL people.

I will ask for input on the RTL Telegram channel.

> Rather a duplicate of 162305 than blocking.

There are three possibilities:

1. Use the LO locale regardless of anything.
2. Apply a heuristic to determine the direction of the first paragraph, ignore
rest-of-documents.
3. Apply a heuristic to determine the direction of _each_ paragraph in the
document, then either aggregate somehow (e.g. "any RTL paragraph -> RTL
document", or "majority", or something accounting for the LO locale) or apply
per-paragraph direction, as suggested in bug 162305.

Now, bug 162305 is a heavy "ask", which is why I separated it. Option (3.)
already takes a bit of work. But while we are undecided (or rejecting) option
(3.), it is still better to use option (2.) as a cheap and rough heuristic,
covering the most common cases better than we do now.


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=109530
[Bug 109530] [META] File opening issues
https://bugs.documentfoundation.org/show_bug.cgi?id=162305
[Bug 162305] When opening a text file with both strong-LTR and strong-RTL
characters, apply per-paragraph direction setting using a heuristic
-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to