Hi

> On 6. May 2022, at 17:44, Lauren P <drurowin at gmail.com> wrote:
> 
> On Fri, May 6, 2022, 01:20 Tobias Pape <Das.Linux at gmx.de> wrote:
> But if we are not careful, that get complex quickly.
> Mhmm. That's a problem with Unicode, though. I'm waiting for a selector #♯. Is that a legacy selector, a unary selector, or a binary selector? (In case it doesn't render in Inbox Talk, that's [MUSIC_SHARP_SIGN].)
> 
> Is אוסף2 ok? should the 2 go after the token?
> I would say the 2 is the last character of the token, but I don't speak or write Hebrew, so I don't know how you mix Arabic numbers and Hebrew letters. Assuming it had markers, that doesn't break the rule.
> 
> This is even worse: אוסף: 2. It's a keyword selector, the 2 is the argument, and the entire sequence is printed backwards. At least during writing. Assuming it had markers, that breaks the rule.
> 
> (note that these hebrew characters do not even contain RTL/LTR markers)
> That's funny. They were certainly RTL in the message body editor. I had the most difficult time imaginable trying to add a line break for the comment, and writing the backwards message send for this one.
> 

Yeah, they _render_ RTL, but there are no _markers_ in the text.
-t