For the most part, RTL orientation of the controls works as expected and provides RTL users with the experience that they expect. To support Arabic and Hebrew, both of which are RTL languages, there is an RTL orientation for the controls in each form, so that an RTL reader can interact with the form in a natural reading manner. Therefore, this behavior would be considered only for special conditions. Keeping track of character orientation in a financial program that might record billions of transactions and multi-billions of characters would produce significant transnational and spatial overhead if we stored contextual information for each character. Therefore, the character is given the behavioral aspects of that language. There, you will see that Word tracks (and stores together with the run of characters) the keyboard that is used to enter each character, and that it treats each character as a member of the language that is associated with the keyboard. To understand how Word “gets it right” and provides a great experience, you can inspect the XML of a Word document. Additionally, there's no attempt to provide the interactive experience that the user actually requires.
THE HEBREW WORD FOR RIGHT SOFTWARE
The problem is that most software just implements the Unicode standard to display bidirectional data, without evaluating how that data is actually used. If you're trying to understand the correct behavior of mixed language presentation, you can use Word for validation. One example of a program that implements this functionality correctly is Microsoft Word. In the area of right-to-left (RTL) language support, one consideration is the combination of RTL text and left-to-right (LTR) text in the same string. A great example of right-to-left language support: Microsoft Word This topic discusses the issue of bidirectional text and how it's handled.