Apache OpenOffice (AOO) Bugzilla – Issue 61929
PDF Export: some fonts are not exported correctly
Last modified: 2006-05-30 09:29:06 UTC
The document attached has a font (Nimbus Sans L Condensed) that is no longer exported correctly in m156_9004. It was exported correctly in 2.0.1. I thought it was somehow related to issue 58366, but the document presented there is exported correctly. The second attached document is the resulting PDF.
Created attachment 34064 [details] the document used to check the issue
Created attachment 34065 [details] the generated PDF file
reassign
I received a mail from a user (Göran Bondeson), on which he stated that on 2.0.1 he had error 129 from Acro Reader while opening the PDF document produced by the odt document reported here as buggy. So I did another test. On Windows XP Home I installed m156 pristine, than Nimbus Type 1 font from ghostscript 8.53. It worked just right. So it seems that the defect is confined to Linux FC4, current. In the first report I didn't mention that I had 2.0.1 pristine, m156 pristine both installed an the same PC when I ran the first test, so they worked with the same font stock: 2.0.1 was ok, m156 was not. I'm not a font expert, but if you need more info, I'll try to provide it. I have a working ooo build tree based on m150 (that btw has the same behaviour as m156), gcc is 4.0.2.
From the PDF file one can see that NimbusMono got embedded, but that most of its glyph metrics are 0. This probably means that the actual problem occured long before, possibly when parsing the corresponding .afm file. I'll investigate. It would help though, to have the font file and its accompanying afm file. You say this is straight from ghostscript 8.53 ?
beppec56->pl. gs fonts worked well in XP. I checked in my FC4 system, it appears that I have multiple copies of the same fonts in different parts, among them gs 8.53 as well, installed locally not part of the distro. As I said I don't know much of fonts metrics, so I tar+bzip2 all of them (I don't know how to isolate Nimbus quickly), so the resulting file is some 14 Mb, I'll put it somewhere else on the net and notify back when done.
Since windows does not use the afm files, this may indeed be another indicator that there is something with either the afm file or our parsing it. I downloaded the standard fonts for ghostscript and could easily reproduce the behaviour, so no further download is necessary. Thanks for the offer, though.
It seems that there is the problem with all Type1 fonts. We reproduced it also with another Type1 font "Bitstream Charter".
confirm, all type1 fonts are concerned, if you did not by chance use them to print before pdf export set target, add regression keyword
SBA: Added this issue as blocker of issue 61850 (that one is to track 2.02 stopper issues)
please verify in CWS fix61929
fixed
Verified with cws fix61929 = ok
Also ok in OOB680m5_9011
I had a similar problem with font "Century Schoolbook L" from URW: Specifically the pairs "ön" and "ti" were mis-spaced in PDF output (while OK in the application). The version being used was that of SuSE Linux 10.0 (OpenOffice_org-2.0.0-1.2). Have a look at https://bugzilla.novell.com/show_bug.cgi?id=179549 for details.