http://qa.mandrakesoft.com/show_bug.cgi?id=3931
------- Additional Comments From [EMAIL PROTECTED] 2003-01-09 14:10 ------- -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 [udo] wrote: a problem The OO.o maintainer said so, and the release manager said it would be in RC2. 9.2, so it to the Current OO.o RPMs haven't compiled on cooker since just after 9.1 release, the maintainer wasn't prepared to waste time that could be spent on 1.1 making them build on cooker. Have you tried with a binary build of OO.o 1.1rc from OpenOffice.org? Regards, Buchan - -- |--------------Another happy Mandrake Club member--------------| Buchan Milne Mechanical Engineer, Network Manager Cellphone * Work +27 82 472 2231 * +27 21 8828820x202 Stellenbosch Automotive Engineering http://www.cae.co.za GPG Key http://ranger.dnsalias.com/bgmilne.asc 1024D/60D204A7 2919 E232 5610 A038 87B1 72D6 AC92 BA50 60D2 04A7 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQE/UzccrJK6UGDSBKcRAlEgAJ4uiXE48Wgc2vYD2j1iqe/MSayciwCgkQ7X q3TL98fgP9zXbAvKAA2OThI= =zMzr -----END PGP SIGNATURE----- ***************************************************************** Please click on http://www.cae.co.za/disclaimer.htm to read our e-mail disclaimer or send an e-mail to [EMAIL PROTECTED] for a copy. ***************************************************************** -- Configure bugmail: http://qa.mandrakesoft.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is. ------- Reminder: ------- assigned_to: [EMAIL PROTECTED] status: NEW creation_date: description: preface 1: my knowledge of the applications involved in printing is limited, so I am just assuming that this error is (only) ghostscript-related ... preface 2: bugzilla shows 7.05-8mdk as the current version, which is strange. The newest version I get from the mirrors is 7.05-53mdk, so this is maybe a bug in bugzilla ;-)) certain ttf-fonts installed via drakfont and/or spadmin just can't get printed. The errors I get in /var/log/cups/error_log always look like this: ---------CUT----------- [...] D [13/May/2003:23:59:15 +0200] [Job 177] Error: /undefined in Regular D [13/May/2003:23:59:15 +0200] [Job 177] Operand stack: D [13/May/2003:23:59:15 +0200] [Job 177] FontName Stylus D [13/May/2003:23:59:15 +0200] [Job 177] Execution stack: D [13/May/2003:23:59:15 +0200] [Job 177] %interp_exit .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push --nostringval-- --nostringval-- --nostringval-- false 1 %stopped_push 1 3 %oparray_pop 1 3 %oparray_pop 1 3 %oparray_pop .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push --nostringval-- --nostringval-- --nostringval-- D [13/May/2003:23:59:15 +0200] [Job 177] Dictionary stack: D [13/May/2003:23:59:15 +0200] [Job 177] --dict:1058/1123(ro)(G)-- --dict:0/20(G)-- --dict:98/200(L)-- --dict:0/11(L)-- D [13/May/2003:23:59:15 +0200] [Job 177] Current allocation mode is local [...] ---------CUT----------- I traced the problem down and found the reason in the generated (temporary) postscript file: In the postscript file the ttf-font named "Stylus" is mapped as: ---------CUT----------- %%Title: Stylus Regular ---------CUT----------- ... which is WRONG. CORRECT is: ---------CUT----------- %%Title: Stylus-Regular ---------CUT----------- If all occurances of the wrong "Stylus Regular" have been replaced, printing is successful. As I said, I have no idea if ghostscript is the real bad boy here ... This happens for many ttf-fonts, so at least for me this is a major problem. The reason are always the missing dashes in the font-names. Upon request I can also post Stylus.ttf as an attachment.
