[gs-bugs] [Bug 691316] { /ISOLatin2Encoding findencoding } fails

bugzilla-daemon at ghostscript.com bugzilla-daemon at ghostscript.com
Fri May 21 11:14:34 UTC 2010


--- Comment #21 from Christopher Yeleighton <giecrilj at stegny.2a.pl> 2010-05-21 11:14:31 UTC ---
(In reply to comment #20)
> (In reply to comment #19)
> > Your assumptions here are against the logic behind the invention of resources
> > in PostScript.
> "Your understanding" of the invention. As I wrote before and write again now:
> you have your own local needs which go contrary to others', and we won't spend
> time on it; what little advice we did offer was offered on a
> take-it-or-leave-it basis on good-will.

There are many more fonts and objects of other categories than can possibly re-
side in VM at any given time. These objects originate from a source external to
the PostScript interpreter. They are introduced into VM in two ways:

• The application or print spooler embeds the objects’ definitions directly in
the job stream.

• During execution, the PostScript program requests the objects by name. *The
interpreter loads them into VM automatically from an external source*, such as
a disk file, a ROM cartridge, or a network file server.

The notion of named resources (LanguageLevel 2) supports *the second method*. A
resource is a collection of named objects that either reside in VM or can be
located and *brought into VM on demand*. There are separate categories of
resources with independent name spaces; for example, fonts and forms are
distinct resource categories. Within each category, there is a collection of
named resource instances.

(Original Adobe text, only the emphasis is mine.)

Forced preloading of all existing Encoding resources at startup time is
incompatible with this text.  And trying to load them from ./Encoding/* at
startup is insane, especially when a failure to do so causes the VM to
completely fail.

Configure bugmail: http://bugs.ghostscript.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

More information about the gs-bugs mailing list