Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!eu.feeder.erje.net!news.swapon.de!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: Helge Blischke Newsgroups: comp.lang.postscript Subject: Re: resourceforall fails Followup-To: comp.lang.postscript Date: Mon, 25 Nov 2013 12:43:26 +0100 Lines: 17 Message-ID: References: <2039b9b4-5def-4c13-b0ed-2f6fc36e691d@googlegroups.com> <9456c32b-9bb8-44ca-8760-4fab362c5035@googlegroups.com> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8Bit X-Trace: individual.net MOFoq65qQfKUhII4/yriQAm3HisX89OyBxJnH61gZ7/v+eKRUI Cancel-Lock: sha1:pY2GRRmKZOaDI12haJXQirhWfA8= User-Agent: KNode/0.99.01 Xref: csiph.com comp.lang.postscript:1738 jdaw1 wrote: > There appear to be non-ASCII characters in the log output, so I’ve > uploaded some files. > http://www.jdawiseman.com/papers/bugs/20131125_resourceforall.ps > http://www.jdawiseman.com/papers/bugs/20131125_resourceforall.log > Obviously the first file made the second. Maybe it is an implementation bug in Acrobat 11. At least it seems uncommen to me that the resourceforall operator inernally calls findresource (maybe it is a Windows specific hack to get the names from the fonts folder?). And, CID fonts are a separate resosurce category (at least a of PLRM 3rd ed), so why is a CID font treated when listing "ordinary" fonts? Helge