aboutsummaryrefslogtreecommitdiff
path: root/Lib/fontTools/ttLib/tables/_c_i_d_g.py
diff options
context:
space:
mode:
Diffstat (limited to 'Lib/fontTools/ttLib/tables/_c_i_d_g.py')
-rw-r--r--Lib/fontTools/ttLib/tables/_c_i_d_g.py20
1 files changed, 10 insertions, 10 deletions
diff --git a/Lib/fontTools/ttLib/tables/_c_i_d_g.py b/Lib/fontTools/ttLib/tables/_c_i_d_g.py
index 2517e785..f11901ba 100644
--- a/Lib/fontTools/ttLib/tables/_c_i_d_g.py
+++ b/Lib/fontTools/ttLib/tables/_c_i_d_g.py
@@ -4,16 +4,16 @@ from .otBase import BaseTTXConverter
class table__c_i_d_g(BaseTTXConverter):
"""The AAT ``cidg`` table has almost the same structure as ``gidc``,
-just mapping CIDs to GlyphIDs instead of the reverse direction.
+ just mapping CIDs to GlyphIDs instead of the reverse direction.
-It is useful for fonts that may be used by a PDF renderer in lieu of
-a font reference with a known glyph collection but no subsetted
-glyphs. For instance, a PDF can say “please use a font conforming
-to Adobe-Japan-1”; the ``cidg`` mapping is necessary if the font is,
-say, a TrueType font. ``gidc`` is lossy for this purpose and is
-obsoleted by ``cidg``.
+ It is useful for fonts that may be used by a PDF renderer in lieu of
+ a font reference with a known glyph collection but no subsetted
+ glyphs. For instance, a PDF can say “please use a font conforming
+ to Adobe-Japan-1”; the ``cidg`` mapping is necessary if the font is,
+ say, a TrueType font. ``gidc`` is lossy for this purpose and is
+ obsoleted by ``cidg``.
+
+ For example, the first font in ``/System/Library/Fonts/PingFang.ttc``
+ (which Apple ships pre-installed on MacOS 10.12.6) has a ``cidg`` table."""
-For example, the first font in ``/System/Library/Fonts/PingFang.ttc``
-(which Apple ships pre-installed on MacOS 10.12.6) has a ``cidg`` table.
-"""
pass