https://bugs.documentfoundation.org/show_bug.cgi?id=163082
--- Comment #6 from Mike Kaganski <[email protected]> --- (In reply to V Stuart Foote from comment #4) > We'd have to recognize it and probably apply Explicit bidi bracketing (i.e. > LRE/RLE or LRO/RLO) with or without termination (PDF). In any case requiring > additional i18n logic in the editengine(s). It is important, that OOXML markup gives the clear borders where this automatic direction change happens. As Eyal mentioned in comment 2, the markup in the document is <w:r><w:t>LTR text</w:t></w:r> <w:r><w:rPr><w:rtl/><w:lang w:bidi="he-IL"/></w:rPr><w:t>RTL text</w:t></w:r> <w:r><w:t>LTR text</w:t></w:r> And editing the XML, dropping either one of <w:rtl/> or <w:lang w:bidi="he-IL"/> (but keeping the other) keeps the look in Word as expected (e- = 5); while dropping both makes Word show the same thing as Writer and Notepad: e5 = - So this may be seen as import filter problem - then we need to check if the next run changes direction explicitly, then put the respective marks (and then, likely, these marks become the document content, which we will export); or we could consider this as more fundamental lack of functionality, where we can't explicitly mark various text runs as having wanted language/direction, e.g. when the run consists of neutral characters (bug 148257). However, that would still require to fix this interoperability problem, if the new feature would take long; then the explicit direction change marks would still be a valid temporary fix. -- You are receiving this mail because: You are the assignee for the bug.
