Opened an issue on GitHub for this: https://github.com/apache/incubator-baremaps/issues/679

Thank you for reporting this problem, I created an issue on GitHub to track it. The root cause is probably located in our tileset or style (not in the renderer). Right now, we use the OpenStreetMap name attribute in our tiles and most of our tests are performed in central europe.

Thanks. Just verified, and OSM is correctly rendering RTL (at least Hebrew).

> "How do these issues even exists in 2023?"

Have actually tried writing something that handles languages running in different directions? It might be 2023, but the libraries... aren't great...

From my experience (not on the web), frameworks that take their Unicode support seriously fare quite well by now (nothing is perfect), while frameworks that make silly assumptions that everything is ASCII do not.

> How do these issues even exists in 2023?

As long as the core developpers of the new platform live and work on the US west coast, any issue non relevant to the US will be a second class citizen, mostly dealt with after the product is deemed stable.

The same way OpenAI operates in english first and other language systems will be improved "later".

It's not a jab on the devs, I realistically can't see any other approach. Just another angle where there's no free lunch and more investment is needed building systems that aren't US first if we care about non-US needs being met in a timely manner.

The main developer is based in Switzerland.

Point taken. Western Europe is already a pretty big difference in many respects (I guess that also explains Lausanne as the default position)