Christer wrote on May 20th, 2008 at 1:07pm:Anyone out there who understands gibberish?
Heh, that's not gibberish - it's just the PostScript debug stack. PostScript is actually quite a nice programming language in many ways, especially for the era when it was devised; although it grew as an evolution of Forth, it was a pretty big evolution and when Level 2 added garbage collection it was basically better as a compilation target than the JVM which came years later.
Digression:
What you are using (Acrobat Distiller) is an evolution of
this program, the PostScript Distillery, which is a work of genius. When Glenn Reid released this, it blew my mind (especially since at the time I hadn't moved on to Scheme).
Essentially it's a simple, readable example of a
partial evaluator built on using the language's own reflective capabilities. The regular PostScript system evaluates the program to "optimize" just as it normally would, but the Distillery redefined the drawing words to capture the final output commands and recreate the PostScript source text to just call them again. Hey presto - the output is a optimized, restricted subset of PostScript.
PDF was the result of commercializing this; Type 1 fonts were already a compressed, tokenized subset of drawing words, so the evolution to do the same to the output documents from the Distillery was natural. PDF is compressed PostScript bytecode, which has been preprocessed by one pass through interpreting the source PostScript program.
In fact, this is really responsible for the disaster that is Java and its' VM: they were designed based on experience Gosling had with the NEWS windowing system, which like many of the best windowing environments of the time - those from SGI's and NeXT as well - was based on Display PostScript.
End Digression
Anyway, "endcidrange" refers to a thing called
CID fonts. The installation of IE7 will have resulted in some changes to the fonts on your system, and this may have caused the Windows printing system (or possibly Adobe Type Manager, if that's still always installed alongside Distiller) to have made some different choices when mapping the fonts in the source program to the fonts sent to the printer driver (in this case the Distiller).
Presumably one of the CID fonts you have doesn't contain one of the symbol characters that appear on that run-time stack, and one of the things that IE7 has changes is causing this particular CID font to be used when it wasn't before.
Figuring out how to resolve it will be the tricky part; really what you want is the right version of the CID font that has those symbol characters so you don't need to deal with diagnosing the (rather opaque) font substitution path, since the substitution choices can be made all over the place (the application, Windows, ATM, the postscript driver, and Distiller).