http://qa.mandrakesoft.com/show_bug.cgi?id=3931
------- Additional Comments From [EMAIL PROTECTED] 2003-16-09 19:18 ------- Giuseppe Ghibò wrote: > I think the patch should be also sent to the scribus authors. This is VERY important. To avoid that this bug appears again and again and to avoid that users of other Linux distros or users who compile from source have this problem, it should be solved at its roots, in the original code produced by the authors. So I ask all of you, who have contributed a fix for this problem, to send your fix to the authors of the appropriate application or library (If you did not already do so). -- 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.
