RE: RE: Proposing new arrow characters with Bidi_Mirrored=Yes

Nitai Sasson wrote:

>> But specifically a left-to-right arrow, such as U+2192 as currently
>> defined, correct? If they had intended a right-to-left arrow (such as
>> U+2190) because the surrounding text is RTL, they would have typed
>> “<--”, correct?
>
> Close, but the actual intention is specifically an arrow pointing in
> the same direction as the ASCII approximation of an arrow points. When
> the character sequence "-->" appears within RTL text, this means a
> right-to-left arrow: א --> ב. This is the crux of the issue.

OK, so just to be clear, you’re talking about a mechanism where the user enters:

U+05D0 HEBREW LETTER ALEF
U+0020 SPACE
U+002D HYPHEN-MINUS
U+002D HYPHEN-MINUS
U+003E GREATER-THAN SIGN
U+05D1 HEBREW LETTER BET

(where the entire sequence --> is mirrored to look like <-- when surrounded by strong RTL characters) and have it replaced by:

U+2192 RIGHTWARDS ARROW

except that the arrow is visually mirrored depending on the directionality of the surrounding characters.

From my casual reading, it feels like two separate topics are being discussed — glyph mirroring, and replacement of Basic Latin fallback input with true arrow characters — and I want to make sure I understand the use case.

--
Doug Ewell, CC, ALB | Lakewood, CO, US | ewellic.org