Apache OpenOffice (AOO) Bugzilla – Issue 15955
single and double opening/closing quotes mess up word order in rtl text
Last modified: 2013-08-07 15:00:39 UTC
When importing Hebrew documents from word XP, the word order gets messed up in the presents of single and double opening/closing quotes. See attached example
Created attachment 7066 [details] original word XP file
Created attachment 7067 [details] the file in word (currect word order)
Created attachment 7068 [details] the file in OO write (incorrect word order)
DL->FME: Could you please takeover?
FME->HDU: Everything looks fine with a 'regular' font. The problem seems to be that the quotation marks are not contained in the font and the glyph fallback takes over. Could you please have a look?
.
>The problem seems to be that the quotation marks are not contained in the font and the glyph fallback takes over ---- If it is a font problem, then why does MS word display this currectly using the same font on the same machine? Comparing the two screenshots, it looks like both are using the same glyph- so I dubt that word fell back to a diffrent font.
The word order problem got solved between 1.1.beta2 and 1.1.1rc3. There were still problems with bad text display seen here (internal reminder #111016#). The reason was there is no font fallback from the documents font "NarkisimMF" to the available "Narkisim" yet, so another less appropriate font got used. By the way, where does "NarkisimMF" come from? The text display problem observed will be fixed in 1.1.1 (CWS vcl7pp1r1 + CWS vcl7pp1r2 combined).
>The word order problem got solved between 1.1.beta2 and 1.1.1rc3. I hope they will fix the RC dowload page soon, so I can see for myself. http://qa.openoffice.org/servlets/ReadMsg?msgId=788833&listName=dev >where does "NarkisimMF" come from? NarkisimMF is the master font version of Narkisim: http://www.masterfont.co.il (the site right now has a notice that it is down for updates) It is NOT the same version that comes with Windows.
Reopening for reassigning and verification.
Please verify the fix in OOo 1.1.
close issue