Here is the 3rd revision.
https://gitlab.freedesktop.org/mpsuzuki/ft2demos-mps-wip/-/compare/8a4879f6...228f50f0
The execution "ftdump -c" for OpenType/CFF fonts with "holes" in
the implemented CIDs, like Hiragino fonts on macOS, generates
the output ending with:
--------------------------------------------------
(...Charmap printout...),2f9de,2f9df,2f9f4
/CIDSystemInfo dictionary
Registry: Adobe
Ordering: Japan1
Supplement: 7
Implemented CIDs:
0-20316,21072-21074,21371,21558,21722,21933,22920,23058,23059
--------------------------------------------------
The execution for real CID-keyed font generates the output ending
with:
--------------------------------------------------
(font type entries...)
underline_thickness: 0
/CIDSystemInfo dictionary
Registry: Adobe
Ordering: Japan1
Supplement: 1
Implemented CIDs:
0-8359
--------------------------------------------------
Is this what you expected?
Regards,
mpsuzuki
On 2023/04/17 23:07, Alexei Podtelezhnikov wrote:
Here is the 2nd revision,
https://gitlab.freedesktop.org/mpsuzuki/ft2demos-mps-wip/-/compare/8a4879f6...c0267c89
To dump the ROS info, it needs "-n" option, as it is needed to dump /FontInfo
dictionary.
For the similarity with /FontInfo dumping, the syntax of the output is changed.
You certainly have a lot more experience with CID-keyed fonts. From my quick
reading, they do not have CMap, which is provided separately. CIDinfo gives a
clue which CMap is to be used. Therefore, it seems best to show this under
Print_Charmaps. You might even consider verbose (-c) output with added
FT_Get_CID_From_Glyph_Index output dump.
Alexei
