Apache OpenOffice (AOO) Bugzilla – Issue 38999
Problem with CTL Arabic fonts
Last modified: 2013-07-30 02:46:59 UTC
Dear developers of the OOO Community, I am using OOO 1.1.3 to format an arabic document in Windows 2000. I am trying to replace the MS Office application with OpenOffice. I have noticed that the CTL presentation of arabic characters in OOO differs from the CTL presentation of arabic characters in MS Word 2000. The font I am using is the same, but the actual drawn glyphs are different. What could be wrong? I will post a follow up with an http link to submit some samples. Thank you in advance, Panayiotis Fafakos.
set prio P1 -> P3
US: thanks Max! @submitter: why not attach the document in question and a screenshot that shows the difference to this issue?
Corrected Component and CC-ing HDU.
please attach the offending document to this issue, so that we can reproduce and fix the problem here. You can also send the document directly (mru@openoffice.org) for the case it contains confidential data. Feel free to re-open the issue when you've done. Thanks for supporting us!
Created attachment 20556 [details] Problem with justification and display
Submited files for examination.
By the way, I have tried to use print screen to do the screen captures, and then paste the clipboard image into OOO 1.1.3 but the image would not be pasted. I used MS Word to create the file with the screens captured by pasting them from the clipboard. Then I opened OOO to save it as .sxw. Should I open another issue for not pasting from the clipboard?
MRU->US: THe import looks quite ok, but the glyphs are drawn slightly incorrect. They are partly painted over the right page border.
Setting Target.
HDU->FME: As far as I see Writer does latin justification instead of kashida justification. IMHO we really should do kashida justification not only when the language is correctly set to Arabic but also when the script suggest is Arabic. It is easily recognizable from the unicodes used if this is the case Another issue seems to be with the import filter which doesn't import the text's language attribute.
FME->HDU: There are a couple of features that rely on a correct language attribute. We should fix this in the filter. FME->FR: As discussed, the language attribute is lost during import. Please have a look.
Currently no resources available -> later
Reset assignee on issues not touched by assignee in more than 1000 days.