Apache OpenOffice (AOO) Bugzilla – Issue 33936
Printer font visualization
Last modified: 2004-09-17 07:54:42 UTC
Unlike Microsoft Word, OOo Writer is unable to visualize printer fonts. Example: the font Kruti Dev 010 (downloadable via link http://www.angelfire.com/pop/top4/ fonts/typing.zip). In this font, Latin letters are replaced with Devangari (Hindi) ones. MS Word both correctly visualizes and prints out texts formatted with that font. OOo replaces it with Arial when visualizing, although printing is OK. Can this be fixed?
I think, fonts "embedded in the file fornat" has to be implemented for this...
no, this is not about fonts embedded in documents but OOo being unable to display a *.ttf-Font -> changing back to defect, assigning to default owner. No problem with linux though. (see screenshot)
Created attachment 17678 [details] dummytext, formatted with "Kruti Dev 010"-font
seems to be a duplicate of issue 26332, but according to http://development.openoffice.org/releases/OOo_2_0_timetable.html CWS fontlist02 has been integrated for m48, so maybe this is another problem. Are you really using 680m51? reassigning to gsl.
cp->hdu: indeed it sounds like a dupe to 26332, please have a look
-> cloph. Yes, I use m51. I have installed it over m49. Well, may that cause problems?
The screenshot from the SRC680m51 version looks good to my untrained eye... can you give us a hint where exactly the the problem is visible in this screenshot?
The screenshot doesn't show the problem. It did it using 1.9m51 using linux. As issue 26332 has been a windows-only problem as well, I cannot tell wether these two are duplicates/related. (It was meant as a "proof" that linux is not affected) maybe the reporter can upload a windows-screenshot showing the problem. Sorry for the confusion.
-> hdu: the screenshot provided by cloph is exactly what it should be. Considering that, yesterday I've done a clean reinstall of OOo and the problem seems to have desappeared. It looks like the problem was about installing over a previous version and I've sort of false reported. I'm sorry and suggest to close the issue.
Ok. From the original bug description it really looks like a duplicate to issue 26332, which is already fixed in >=SRC68m48. So if everyone agrees I'm closing it. *** This issue has been marked as a duplicate of 26332 ***
.