Apache OpenOffice (AOO) Bugzilla – Issue 6968
compilation to postscript fails due to fields in fonts
Last modified: 2003-03-13 11:13:52 UTC
For some fonts, the compilation to postscript fails because of fonts with irregular characters or spaces in internal fields (ttf's). As a result, printing fails without any warning. [cocaine:~] cat uhm | gs -sDEVICE=pbmraw -sPAPERSIZE=a4 -q -dNOPAUSE -r600 -sOutputFile=uhm.processed - Error: /undefined in StempelkastenHSet1 Operand stack: FontName Alexandras Execution stack: %interp_exit .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push --nostringval-- --nostringval-- --nostringval-- false 1 %stopped_push 1 3 %oparray_pop .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push --nostringval-- --nostringval-- --nostringval-- Dictionary stack: --dict:918/1241(G)-- --dict:0/20(G)-- --dict:61/200(L)-- --dict:3/30(L)-- Current allocation mode is local Current file position is 668549 GNU Ghostscript: Unrecoverable error, exit code 1 [cocaine:~] _ This is only an openoffice bug by proxy, but I think it's important enough to mention (there are lots of invalid ttf fonts out there). If this issue wasn't known (hard to see how it couldn't have been), it might solve some 'nothing happens when trying to print'-issues.
Created attachment 3199 [details] desription of the problem with the generated postscript (from a ghostscript-developer)
Moving to gsl, since postscript generation seems to be their responsability. Testcases with faulty postscript (and the TTF's that cause it) are available on request.
assigning to real project lead
will fix
Wouter, please provide a testcase (ttf font)
Created attachment 4324 [details] This font makes ps 'FontName' fail
Created attachment 4325 [details] This font makes ps 'FontName' fail
'black.ttf' makes the generated postscript compilation fail because of a space in the field, and 'blaiHand.ttf' because of the colon or slashes (it's an url, for some reason). It can be argued that most of these ttf fonts have invalid fields in them that should be fixed. However, we're talking about many of them, so it's probably better and definitely more feasable to escape or rename the fieldnames in the generated postscript. Perhaps solving this will also solve some other bug reports related to 'OO not printing', at least on a *nix platform. I have more examples, if needed.
thanks for the bugdoc, will be fixed in 1.1beta, psprint/printergfx/common_gfx.cxx 1.10.6.1 psprint/printergfx/glyphset.cxx 1.15.6.1 psprint/fontsubset/sft.c 1.18.6.1
fixed in CWS vcl03
fixed
verified in cws vcl-03.
As mentioned on the qa dev list on March 5th I will close all resolved <wontfix/duplicate/worksforme/invalid> issues. Please see this posting for details.