(I cc to volker, maybe he can mention this to Hermann Zapf who is redoing the fonts). Interestingly Hermann is not mentioned in the copyright notice of his own fonts.) Hi, The optima nova fonts have pretty long copyright notices and these give problems in ghostscript /Copyright (The digitally encoded machine readable software for producing the Typefaces licensed to you is copyrighted (c) 1981, 1999, 2002 Linotype Library GmbH or its affiliated companies. All rights reserved. This software is now the property of Heidelberger Druckmaschinen AG and its licensors, and may not be reproduced, used, displayed, modified, disclosed or transferred without the express written approval of Heidelberger Druckmaschinen AG. Part of the digital encoded machine readable software for producing the Typefaces licensed to you is copyrighted (c) 1981, 1999 Adobe Systems. All rights reserved. Part of this software is the property of Adobe Systems Incorporated and its licensors, and may not be reproduced, used, displayed, modified, disclosed or transferred without the express written approval of Adobe.) readonly def /Notice (Optima is a trademark of Heidelberger Druckmaschinen AG, which may be registered in certain jurisdictions, exclusively licensed through Linotype Library GmbH, a wholly owned subsidiary of Heidelberger Druckmaschinen AG.) readonly def maybe pdftex can split too long lines into multiple /Copyright () lines Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------
"Hans" == Hans Hagen
writes:
> (I cc to volker, maybe he can mention this to Hermann Zapf who > is redoing the fonts). Interestingly Hermann is not mentioned in > the copyright notice of his own fonts.) > Hi, > The optima nova fonts have pretty long copyright notices and > these give problems in ghostscript Hi, did you try the font with other programs? It seems to be most probably a bug in ghostscript. A copyright notice in a Type 1 font is just a string. I didn't find anything about limitations in the Type 1 Reference Manual or TN 5015. The PostScript Language Reference Manual (Appendix B) describes PS interpreter requirements. According to this, any PS interpreter should be able to handle strings of least 65535 bytes. There are some restrictions for ATM compatibility but obviously they do not affect string lengths. So I think that ghostscript is the culprit and the bug should be fixed there. Can you send me a small file which shows this problem? At the moment I have 30 different versions of gs installed on my system and it shouldn't bee too difficult to find out which versions are affected (or when this bug had been introduced). > [...] > maybe pdftex can split too long lines into multiple /Copyright > () lines I think that pdftex should remove anything from a font which is not needed, but as far as the copyright notice is concerned, it's certainly best to leave it as it is. Technically, it is wrong to split it into multiple lines. For example: /Copyright (copyright by me.) def /Copyright (you are not allowed to) def /Copyright (give this font away!) def The content of /Copyright is now the string "give this font away!". Even worse, /Copyright is defined as "readonly def". A PS interpreter should complain if someone tries to overwrite the initial definition. I agree with you that the copyright notice is much too long. Nobody spends much time to read so boring stuff, anyway. Regards, Reinhard -- ---------------------------------------------------------------------------- Reinhard Kotucha Phone: +49-511-4592165 Marschnerstr. 25 D-30167 Hannover mailto:reinhard.kotucha@web.de ---------------------------------------------------------------------------- Microsoft isn't the answer. Microsoft is the question, and the answer is NO. ----------------------------------------------------------------------------
Reinhard Kotucha wrote:
Hi, did you try the font with other programs? It seems to be most probably a bug in ghostscript.
A copyright notice in a Type 1 font is just a string. I didn't find anything about limitations in the Type 1 Reference Manual or TN 5015.
hm, i found out that when for instance afm files have lines longer than 256, some programs break on it so either we have to do with fuzzy specs, or rumoured lengths, or lousy programming
The PostScript Language Reference Manual (Appendix B) describes PS interpreter requirements. According to this, any PS interpreter should be able to handle strings of least 65535 bytes.
Interesting, i wonder why gs has limitations then; what does the spec say about unknown %%comments? GS breaks on them each time adobe adds a new undocumented one.
So I think that ghostscript is the culprit and the bug should be fixed there. Can you send me a small file which shows this problem? At the moment I have 30 different versions of gs installed on my system and it shouldn't bee too difficult to find out which versions are affected (or when this bug had been introduced).
i filled in a bug report for gs; i also downloaded the 8.31 beta version which seems to work ok; this means that the official version has problems
/Copyright (copyright by me.) def /Copyright (you are not allowed to) def /Copyright (give this font away!) def
The content of /Copyright is now the string "give this font away!".
i hadn't thought of that one -)
Even worse, /Copyright is defined as "readonly def". A PS interpreter should complain if someone tries to overwrite the initial definition.
we could zip it: if length> 255 then /Copyright(zipped: ,zipped string>} -) Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------
"Hans" == Hans Hagen
writes:
> hm, i found out that when for instance afm files have lines > longer than 256, some programs break on it so either we have to > do with fuzzy specs, or rumoured lengths, or lousy programming This is described in http://partners.adobe.com/asn/developer/pdfs/tn/5004.AFM_Spec.pdf on page 10: | Comments can be present in an AFM file. They are introduced | by the keyword Comment and are terminated by the end of | line. Lines are no longer than 255 characters long. >> The PostScript Language Reference Manual (Appendix B) describes >> PS interpreter requirements. According to this, any PS >> interpreter should be able to handle strings of least 65535 >> bytes. > Interesting, i wonder why gs has limitations then; what does the > spec say about unknown %%comments? GS breaks on them each time > adobe adds a new undocumented one. From http://partners.adobe.com/asn/developer/PDFS/TN/5001.DSC_Spec.pdf page 21: | A non-conforming document is recognized by the %! header | comment. Under no circumstances should a non-conforming | document use the %!PS-Adobe-3.0 header comment. Regards, Reinhard -- ---------------------------------------------------------------------------- Reinhard Kotucha Phone: +49-511-4592165 Marschnerstr. 25 D-30167 Hannover mailto:reinhard.kotucha@web.de ---------------------------------------------------------------------------- Microsoft isn't the answer. Microsoft is the question, and the answer is NO. ----------------------------------------------------------------------------
participants (2)
-
Hans Hagen
-
Reinhard Kotucha