http://qa.mandrakesoft.com/show_bug.cgi?id=3931
------- Additional Comments From [EMAIL PROTECTED] 2003-27-08 18:34 ------- this is the excerpt of the output I get from ftdump on stylus.ttf (which BTW is attachment#685) concerning the fontname: ===========CUT============ [...] font name entries family: Stylus style: Regular postscript: Stylus Regular [...] ===========CUT============ When I try to change "Stylus Regular" to "Stylus\ Regular" in attachment#687 as you suggested, ghostscript is still not happy with it: ===========CUT============ % gs stylus.ps Error: /undefined in RegularHSet1 Operand stack: FontName Stylus\ Execution stack: [...] ===========CUT============ However, I compared the output of ftdump for stylus.ttf with the output for some other font, that renders ok and the difference is obvious: excerpt of ftpdump for working aadvark.ttf: ===========CUT============ [...] font name entries family: Aardvark style: Bold postscript: AardvarkBold [...] ===========CUT============ If you compare it with the one from stylus.ttf, you see that this time the postscript-name is set up by "$FAMILY$STYLE" for aardvark.ttf, whereas for stylus.ttf it is "$FAMILY $STYLE". Instead of using hyphens (as I did previously) I then tried to remove the whitespace between $FAMILY and $STYLE - and got a working postscript file! So maybe the problem is in fontname creation? -- 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: UNCONFIRMED 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.