Re: [ft-devel] CFF in OpenType is SID to CID mapping correct?

[Werner LEMBERG]

Boris,


thanks for the font.

> [...] these does not "work" (shows undefined character instead).

What exactly do you mean with `not work'?  How do you access the font?

> Unicode -> correct CID - this is also in this CMAP
> 0xFA40 -> 20317
> 0xFA20 -> 20318
> 0x8B7F -> 20319
> 0x5906 -> 20320
> 0x609E -> 20321
> 0x66B5 -> 20322
> 0x7152 -> 20323
> 0x9A42 -> 20324

Using

  ftview -e unic

I see these glyphs correctly.  ttx gives the following for the last
eight glyphs in the font:

    <GlyphID id="20317" name="cid21072"/>
    <GlyphID id="20318" name="cid21073"/>
    <GlyphID id="20319" name="cid21074"/>
    <GlyphID id="20320" name="cid21371"/>
    <GlyphID id="20321" name="cid21558"/>
    <GlyphID id="20322" name="cid21722"/>
    <GlyphID id="20323" name="cid21933"/>
    <GlyphID id="20324" name="cid22920"/>

As you can see, this is not the identity mapping.

> Unfortunately in Windows it works correctly,

Hmm.  AFAIK, Windows always use the `cmap' table if present.

> I tried to check it in ftstring (git master version), but I was not
> able to enter Unicode characters on command line.

Using the attached file (encoded in UTF-8) you can say

  ftstring -m `cat ftstring.input` <size> <font>

It works just fine for me.

> (Unrelated problem: Also ftstring unlike ftview display bitmap looks
> like switched order of 4 bytes like big/little endian problem (I am
> using jam and MSVC2005 for compilation))

Please elaborate.  I don't understand what you want to say.

Note that there seems to be a bug in either FreeType or in the demo
programs: I can't make ftview or ftstring display any bitmap strikes.
HiraMinProN-W3 doesn't contain any, but HiraMinPro-W3 does, for
example.  Will investigate soon.


    Werner

ftstring.input
Description: Binary data