Closed ju-sh closed 2 years ago
Found an example here that says:
Memory: he said "<RLI>I NEED WATER!<PDI>", and expired.
Display: he said "!RETAW DEEN I", and expired.
But does it work differently in the early-return example?
This is a great point -- the RLI character behaves strangely. The example that you reference comes from the de facto source of truth for a correct Unicode implementation, but that's not the behavior that I observe in practice.
Unicode Bidi implementations differ by application & OS, but rendering "
I NEED WATER!
Experimentally, it appears to me that (at least in Chromium-based software) RLI affects neutral characters but not strong characters; or, rather, at least affects neutral and strong characters differently.
It's not immediately clear to me whether this behavior is in the Unicode Bidi spec, or whether this is a bug/undefined behavior in specific Bidi implementations.
Thanks. I think in the example from the page for the bidi algorithm, they also use upper case characters as a kind of notation to represent a script written from right to left (or something like that, right?).
And do you know how is bidi pronounced? Is it 'bye-dye' or 'bee-dee'?
I've heard it pronounced many different ways; I'm not sure that there's a consensus. Although it's a different "Bidirectional" there's a related thread about it here.
In the early-return.py example, I had thought
would end up being rendered as
where every character from the end of line (there's an implicit
<PDI>
at end of line, right? Or doesn't this end of line not count as an end of paragraph?) to the<RLI>
are displayed one by one.But I suppose that's not how it works since it gets displayed as
Could someone help me understand this?