I consider the use cases describe incomplete because they haven’t made completely clear the contexts in which text is appearing.
Peter From: Nitai Sasson <unicode....@sl.neatnit.net> Sent: April 13, 2025 4:10 AM To: Peter Constable <pgc...@msn.com> Cc: Mark E. Shoulson <m...@kli.org>; unicode@corp.unicode.org Subject: Re: RE: Proposing new arrow characters with Bidi_Mirrored=Yes On 12/04/2025 9:57, Peter Constable via Unicode wrote: > > We're being presented with actual use-cases > > Actually, I’d say we’re being presented with incomplete use cases. I'm sorry you think so. Why do you think these use cases are incomplete? https://meta.discourse.org/t/wrong-arrow-direction-in-rtl-text-contexts/360760 - an actual use case with no viable solution at this time. https://github.com/deevroman/better-osm-org/commit/ebb92a89aff109b2cf123e0b1c20f72a05b66ff6#diff-c40e4bdcda333a75ea7518bed17ef1054abd4d999e4d18f017d469a3d4210829R6306 - a use case where the lack of a Unicode solution forces the developer to implement more complex conditional logic. Note that if they had chosen a different character like U+22B6 Original Of, then the extra logic would not have been needed. https://util.unicode.org/UnicodeJsps/character.jsp?a=22B6 There is no good reason why arrow characters, when used as operators, should require more code than other operators. - Nitai
