Hi Andreas

Andreas Martens wrote:
unfortunately your problem will not be solved by fixing this issue and by inserting these Unicode control characters.
Why not?
Because these control characters will not change the order of RTL characters. It will only change the order of text portions in BiDi paragraphs.
An example, lowercase means LTR, uppercase RTL characters:
If you type(or import) “abcDEFghi”, you'll get in OOo: “abcFEDghi”.
If you put the LTR control character at the beginning of this paragraphs, nothing changes, because the default for OOo is already LTR. If you put the RTL control character at the beginning, you'll get “ghiFEDabc”.

OK, I do not know all the theory that is behind it, but the empirical test with the WP6 Arabic (13).odt attached to issue 51400 are giving me following:

1) If I remove the control (whether there is space or not between the characters, it means whether their are in the same word or not), they are rendered naturally, RTL for all except characters 48-57 that are numbers which are normally rendered LTR even in Arabic.

2) When I put the control back, ALL characters are rendered LTR. Again, being inside the same word or not does not matter.

There are three types of LR/RL unicode controls:
a) Left-to-Right Mark (U+200E) and Right-to-Left Mark (U+200F);
b) Left-to-Right Embedding (U+202A) and Right-to-Left Embedding (U+202B)
c) Left-to-Right Override (U+202D) and Right-to-Left Override (U+202E)

Empirically the group (c) seems to be doing exactly what I needed.

I don't see a solution for your problem without reordering the characters inside the filter :-(

I hope that what I wrote above is true, since this solution would be much more difficult ;-)

Please correct me if I'm wrong, Frank.
Regards
    Andreas

Cheers

Fridrich
--
Please avoid sending me Word, Excel or PowerPoint attachments.
See http://www.gnu.org/philosophy/no-word-attachments.html

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to