https://bugs.documentfoundation.org/show_bug.cgi?id=141663
Eric Bright <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |UNCONFIRMED Resolution|INVALID |--- --- Comment #12 from Eric Bright <[email protected]> --- (In reply to Eyal Rozenberg from comment #11) > (In reply to Eric Bright from comment #0) > > Description: > > When writing a sentence that is left-to-right (LTR) inside a right-to-left > > (RTL) paragraph, any punctuation mark at the end of the LTR sentence jumps > > to the beginning of that LTR sentence, instead of staying at the end of the > > LTR sentence. > > This is intended behavior. If the paragraph is RTL, it is assumed that a > punctuation mark is part of the paragraph's flow, with the LTR text so far > having come to an end. A punctuation mark is direction-neutral, and there is > no way to know for certain whether you wanted it to be in the LTR run or > not. Once you write additional characters, LO can infer the direction with > more certainty. But if you _don't_ write any more characters, then your > punctuation mark (typically a period) should indeed be assumed to be RTL > again - since it's reasonable for you to want to finish your RTL sentence > with a punctuation mark. > > You can "force" the direction of the punctuation mark, by inserting a > Unicode control character, such as an RLM: > > https://en.wikipedia.org/wiki/Right-to-left_mark > > at the link, you'll notice how it is used for doing just this. > > > Everything I've said applies similarly to RTL text within LTR paragraphs > (with RLM marks). Thank you for the reply. Even if that behaviour is the default, which seems to be the case, that default behaviour is incorrect and must be corrected. As you can clearly see in the attached images/documents, MS Word does it correctly. An English sentence (LTR within a Persian sentence (RTL) must still retain its correct arrangement. MS Word keeps the correct arrangement. LO Writer does not. Fixing this incorrect behaviour should not be that difficult since MS Word has already figured it out and it is already known how that would work in HTML with proper tags. LO Writer must, at least, produce a document as correctly as a simple HTML page would do. As such, I am changing the status of the bug to 'unconfirmed' since you saw and verified that behaviour. This is a bug that is both annoying and unreasonable and must be looked into. The simple question is how MS Word and all browsers can correctly do what I just described but LO Writer believes it to be natural to scramble everything and think of it as normal. As I showed in the attached documents, this behaviour is not a feature; it is a bug. If one believes this bug is the intended behaviour and no one wants to fix it, then please change the status to " VERIFIES" and "WONTFIX." -- You are receiving this mail because: You are the assignee for the bug.
