4 ms·
This is nothing unique to maps. It has to do with Unicode bidi algorithm mixing RTL and LTR text in various contexts. Note that in RTL languages you have things
by tgma 3y ago
This is nothing unique to maps. It has to do with Unicode bidi algorithm mixing RTL and LTR text in various contexts. Note that in RTL languages you have things like numbers that are rendered in LTR and mixing them introduces complexity.
https://unicode.org/reports/tr9/ https://unicode.org/reports/tr9/
- mapmeld 3y agoI did a write-up because it was an example of broken text "in the wild" rather than in technical references. Also it takes me a minute to think of () as open/close parens instead of left/right parens.
- tgma 3y agoYeah. Nothing against your article. As someone whose native language is RTL I can tell you this is not an isolated case at all. If you're used to operating a computer in RTL languages like Arabic script you'd see this stuff every single day. Not exaggerating at all. ;) Unicode is such a complex beast this is just one aspect of it.
- dotancohen 3y agoYou might be interested in a page I wrote about mixed RTL and LTR text and getting them to render properly: https://dotancohen.com/howto/rtl_right_to_left.html https://dotancohen.com/howto/rtl_right_to_left.html I suspect that your user entered the street name correctly at first, then played around with the wrong parenthesis in the wrong locations until he settled upon something that looked like it visually rendered as he expects, on his system in the input box.
- deleted 3y ago[deleted]