Bug 223992 - incremental loading for CIDFontType 2 and TrueType fonts
incremental loading for CIDFontType 2 and TrueType fonts
Product: Ghostscript
Classification: Unclassified
Component: PS Interpreter
All All
: P2 normal
Assigned To: Ray Johnston
Bug traffic
Depends on:
  Show dependency treegraph
Reported: 2000-11-30 16:13 PST by Jack Moffitt
Modified: 2007-12-13 12:55 PST (History)
0 users

See Also:
Word Size: ---


Note You need to log in before you can comment on or make changes to this bug.
Description Jack Moffitt 2000-11-30 16:13:14 PST
Originally reported by: hideyuki@users.sourceforge.net
Entire TrueType outline data in CIDFontType 2 and TrueType fonts are loaded into memory at once.  Incremental loading of the outline data is indispensable for practical use of Asian fonts.
Comment 1 L. Peter Deutsch 2000-11-30 19:26:14 PST
Comment originally by lpd@users.sourceforge.net
I suggest that anyone who would like to work on this project start by looking at how CIDFontType 0 fonts do incremental loading (lib/gs_cidfn.ps and src/zfcid0.c). I suspect that much of this code can be also be used with CIDFontType 2 and TrueType fonts.
Comment 2 L. Peter Deutsch 2000-11-30 22:09:59 PST
Comment originally by lpd@users.sourceforge.net
There is one other type of CID-keyed font that should also be loaded incrementally: CFF CIDFontType0, i.e., a CIDFontType 0 font represented using the compact binary CFF format. This is important because this is one of the two variants of Asian OpenType fonts (the other is essentially the same as TrueType). Ghostscript already supports both of these OpenType variants, but not with incremental loading.
Comment 3 L. Peter Deutsch 2000-12-31 12:00:47 PST
Comment originally by lpd@users.sourceforge.net
This topic is being discussed on the gs-devel mailing list. Anyone interested in participating is welcome to go to http://www.ghostscript.com and join the list.
Comment 4 Ray Johnston 2001-04-02 16:15:26 PDT
Comment originally by rayjj@users.sourceforge.net
Logged In: YES 

We acknowledge that this is a valid issue, but we do not have
resources available to address this at this time.

This problem report has been moved to doc/Issues.htm where it
may remain open for some time. Relevant comments are
captured there along with the ID# of this report.

By moving this issue to the widely distributed Ghostscript
documentation, we wish to make this issue well known and
solicit help in improving Ghostscript in this area.

Thanks for your input!