-
Bug
-
Resolution: Unresolved
-
None
-
None
-
Medium
-
Emptyshow more show less
problem
The browsers bidi algorithm to show a mixture of LTR and RTL languages may lead to a wrong visualization of tags (wrong order) - although the tag order is correct.
See screenshot.
In the concrete case the reviewer tried to fix the tag order, but instead the tag order was wrong after that.
possible solution - probably not working
The bidi alorithm could be disabled with the bdo tag or via CSS on the whole segment, which would fix the tag ordering, but then the number is displayed wrongly. In XLF there was 50, which is in arabic 50 too (https://www.quora.com/Why-are-numerals-written-left-to-right-in-Arabic) but with bidi disabled it is shown as 05 then.
In Addition RLM and LRM markers could be used:
https://stackoverflow.com/questions/48487642/are-there-right-to-left-versions-of-unicode-characters-for-period-exclamation-m
Not tested so far!
References:
https://www.w3.org/International/articles/inline-bidi-markup/
https://www.w3.org/International/questions/qa-html-dir
https://openui5.hana.ondemand.com/1.28.0/docs/guide/91f2c24b6f4d1014b6dd926db0e91070.html
- relates to
-
TRANSLATE-3206 Protect and auto-convert numbers and general patterns during translation
- Done
Finally: there is no solution, since that the browser flip the content is basically correct. So the users must be trained here on the one hand side.
What we can implement on the other hand side, is a flag (similar to the disable track changes button in the tag view drop down menu) to disable the bidi alorithm via CSS. So the user can check the content without any flipping of tags.