The issue is that not everything has to be flipped. Numbers are an example but think about LTR words embedded in a RTL language (some may be urls or email addresses or untranslatable texts).
Designing an HTML page with RTL content is basically a nightmare because the tags are still in English.
Actually some programmers do exactly as you say and flip the view completely, including tags, when they work in a mixed document. I have seen this flow with programmers who use vim in the terminal.
But not, the cost is really not enormous nowadays. It's really a matter of really easy fixes and some testing. Similarly to many other accessibility features the issue is most often ignored completely, however.
Re:Right-to-Left Styling 101
by kingcharles on Sunday December 12, 2021 @12:53PM
(#29531775)
There are other problems with big apps. Look at the comments under a YouTube video. YouTube is one of the biggest sites in the world, but it was written and designed by LtR natives. The comments have to support both LtR and RtL languages, but the comment viewing can only support one layout, so the experience is sub-par for RtL. For instance, RtL comments will start at the right and span towards the left where the user's avatar is, whereas Latin comments will sit nicely next to the user's avatar.
Tl;dr: There is no perfect solution when your site has to support both LtR and RtL in the same page at the same time. Someone is going to suffer.
I worked on a game where we shipped that solution. We flipped everything post render but also built some tech to be able to tag certain individual elements that we didn’t want RTL (essentially just flipping those individual elements again).
Isn't there a simpler solution for supporting RTL? Why not render everything LTR and then flip horizontally? Could it work?