[gs-bugs] [Bug 691479] cidfmap not used by FreeType

bugzilla-daemon at ghostscript.com bugzilla-daemon at ghostscript.com
Mon Jul 19 07:36:11 UTC 2010


Ken Sharp <ken.sharp at artifex.com> changed:

           What    |Removed                     |Added
             Status|NEW                         |RESOLVED
         Resolution|                            |WORKSFORME

--- Comment #1 from Ken Sharp <ken.sharp at artifex.com> 2010-07-19 07:36:10 UTC ---
FreeType makes no distinction regarding cidfmap at all. The cidfmap file is
loaded and interpreted by the PostScript interpreter without reference to the
font rendering library.

I just tested this on my setup, cidfmap entry:

 /FileType /TrueType
 /Path (/tests/690930/FreeSerif.TTF)
 /SubfontID 0
 /CSI [(Artifex) (Unicode) 0]

At the GS window, type:

/FreeSerif /CIDFont findfont

results in a correct font dictionary on the operand stack.

Also tried cidfmap entry:
/TimesNewRoman << /CSI [(Identity) 0] /Path (c:/windows/fonts/times.ttf)
/SubfontID 0 /FileType /TrueType >> ;

Then using TimesNewRoman-Identity-H to set test, this also works. So the
FreeType build of GS most certainly does use cidfmap on Windows.

I'm less sure about your point regarding the location of cidfmap. Again this is
unaffected by the choice of font rendering engine. As far as I am aware cidfmap
is supposed to be found in Resource/Init (certainly that's where mine is) I'm
not aware that it 'should' be read from the current directory.

However, if this has changed it seems more likely to be related to the recent
flurry of activity surrounding search paths than anything to do with FreeType.

Marcos, can you please tell me why you think FreeType isn't using cidfmap ? Can
you please also explain why cidfmap should be read from the current directory.
If it should, then I suggest finding out which revision broke it and
re-assigning it to whoever made the change.

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