* Add CFF2 to CFF1 converter for font instantiation
When instantiating a CFF2 variable font to a static instance, automatically
convert the output to CFF1 format instead of keeping it as CFF2. This is
appropriate since CFF2's variation features are no longer needed in static
fonts, and CFF1 is more widely supported.
The converter integrates with the CFF2 subsetter and triggers automatically
when pinned=true (i.e., when instantiating with normalized coordinates).
Converts table structure:
- CFF2 inline TopDict → CFF1 TopDict INDEX
- Adds Name INDEX and String INDEX
- Creates CID-keyed font with ROS operator (Adobe-Identity-0)
- Generates identity CID charset
- Removes variation operators (vstore, vsindex, blend)
- Reuses desubroutinized charstrings and subroutines
Focus is on structural conversion; charstring encoding details like
endchar/return operators and width encoding can be added incrementally.
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
* Fix CFF2 to CFF1 converter table tag and serialization
Updates the CFF2 to CFF1 converter to properly output CFF format:
- Use plan->add_table() to output 'CFF ' tag instead of 'CFF2'
- Return false from subset() to signal CFF2 table not needed
- Use passed serializer instead of creating new one
- Change String INDEX to use push/copy/pop_pack pattern
Known issue: Output has 5 extra bytes before CFF header that need
investigation of serializer head/tail allocation patterns.
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
* Fix CFF2 to CFF1 serialization order and header version
Fixes the INDEX serialization order and version field initialization:
- Reorder serialization to match CFF1 pattern: CFF header, then Name INDEX,
then Top DICT INDEX. This eliminates extra bytes before the header.
- Fix version field by using cff->min_size instead of OT::cff1::min_size
for nameIndex offset. This resolves the issue where major version was
written as 0x00 instead of 0x01.
- Add String INDEX with "Adobe" and "Identity" strings (SIDs 391, 392)
required by the ROS operator in CID-keyed fonts.
The CFF header now correctly starts at offset 0 with version 1.0.
Remaining issue: FDArray offset parsing error needs investigation.
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
* Improve FDArray serialization in CFF2 to CFF1 converter
Change FDArray serialization to use inferred template types and avoid
preprocessor issues with the likely() macro when using template syntax.
Progress:
- CFF header now at offset 0 with correct version 1.0 ✓
- String INDEX with ROS strings (Adobe, Identity) ✓
- ROS operator with correct SIDs ✓
- Serialization order matches CFF1 pattern ✓
Remaining issue:
- FDArray INDEX structure needs investigation - fontTools reports
"unpack requires a buffer of 4 bytes" when reading FDArray offsets.
May be related to INDEX offSize or data alignment.
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
* WIP: Add CFF2 to CFF1 converter for font instantiation
When a CFF2 variable font is fully instantiated (all axes pinned),
convert it to CFF1 format. This is work in progress.
Key changes:
- Add serialize_cff2_to_cff1() function to convert instantiated CFF2 to CFF1
- Use cff2_private_dict_op_serializer_t to instantiate Private DICT blends
- Add CFF1 table structures (Name INDEX, String INDEX for ROS, etc.)
- Create CID-keyed fonts with ROS operator (Adobe-Identity-0)
- Use subsetter's serializer with end_serialize() to resolve links
Current status:
- Private DICT instantiation works (blends evaluated correctly)
- CharStrings are properly flattened (verified: no blend operators remain)
- CFF1 table structure created but CharStrings INDEX validation fails in OTS
- Need to investigate CharStrings serialization format issue
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
* Add FDSelect and FDArray to Top DICT for CID-keyed fonts
CFF1 CID-keyed fonts require FDSelect and FDArray operators in the
Top DICT, even when there's only one Font DICT. CFF2 makes FDSelect
optional when there's a single FD, but CFF1 always requires it.
This commit:
- Always creates an FDSelect for CID-keyed CFF1 fonts (even with 1 FD)
- Explicitly serializes FDSelect and FDArray operators in Top DICT
- Avoids duplicating these operators when processing CFF2 Top DICT
Fixes font rendering - glyphs now have proper paths.
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
* Use FDSelect3 (range-based) instead of FDSelect0
When creating a default FDSelect for single-FD CID fonts, use the
compact range-based FDSelect3 format instead of FDSelect0.
For a font with 254 glyphs mapping to FD 0:
- FDSelect0: 254 bytes (1 byte per glyph)
- FDSelect3: 8 bytes (format + nRanges + range + sentinel)
Saves 246 bytes (~1KB in this test font).
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
* Update documentation with implementation status
Documents:
- What's implemented and working
- Known limitations (FontBBox, width, stack depth)
- Key conversion steps
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
* Copy FontBBox from head table
Instead of calculating from scratch, copy the font bounding box
directly from the head table (xMin, yMin, xMax, yMax).
Before: FontBBox value="0 0 0 0"
After: FontBBox value="-175 -250 1178 899"
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
* [CFF2->CFF1] Add width optimization and encoding
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
* [CFF2->CFF1] Port O(n) width optimization algorithm
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
* [cff2-to-cff1] Add command capture infrastructure for specialization
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
* [cff2-to-cff1] Implement CharString specialization with stack depth control
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
* [cff2-to-cff1] Add generalization phase for stack safety
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
* [cff2-to-cff1] Update documentation to reflect completed features
Removed outdated limitations that have been implemented:
✓ FontBBox (now copied from head table)
✓ Width handling (O(n) optimization + CharString encoding)
✓ Stack depth control (generalize→specialize with maxstack=48)
Added new features to implementation status:
- CharString specialization
- Width optimization and encoding
- Stack depth control
Remaining limitations are now accurate (only CID-keyed, no curve
specialization/peephole optimizations).
* [cff2-to-cff1] Remove CID-keyed 'limitation' from docs
CID-keyed output is by design, not a limitation:
- Variable fonts (CFF2) are instantiated to CID-keyed CFF1
- We explicitly add ROS operator to make output CID-keyed
- This is the correct behavior for instantiated fonts
Changed section from 'KNOWN LIMITATIONS' to 'FUTURE ENHANCEMENTS'
to better reflect that curve/peephole optimizations are optional
improvements, not missing functionality.
* [CFF2->CFF1] Add HB_SUBSET_FLAGS_DOWNGRADE_CFF2 flag
Make the CFF2→CFF1 converter opt-in via the HB_SUBSET_FLAGS_DOWNGRADE_CFF2
flag (disabled by default). This gives users control over whether variable
font instantiation produces CFF2 (default) or CFF1 (for compatibility).
Changes:
- Add HB_SUBSET_FLAGS_DOWNGRADE_CFF2 flag to hb-subset.h
- Gate CFF2→CFF1 conversion on flag check in hb-subset-cff2.cc
- Add --downgrade-cff2 command-line option to hb-subset tool
The flag enables converting instantiated variable fonts from CFF2 to CFF1,
providing compatibility with older renderers that don't support CFF2.
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
* [CFF2->CFF1] Deduplicate CFF1Font string constant
Define CFF1_DEFAULT_FONT_NAME constant once in hb-subset-cff2-to-cff1.hh
and use it in both the plan creation and serialization code.
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
* [CFF2->CFF1] Fix swapped horizontal/vertical logic in specializer
The specialization logic for rmoveto/rlineto to h/v variants was backwards:
- When dx=0 and dy!=0, movement is VERTICAL (vmoveto/vlineto), not horizontal
- When dy=0 and dx!=0, movement is HORIZONTAL (hmoveto/hlineto), not vertical
This was causing completely garbled outlines in converted fonts. The fix
corrects the operator selection to match the actual movement direction.
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Sonnet 4.5 <noreply@anthropic.com>
Used in conjunction with retain gids, when set the num glyphs from the input font will be preserved. Empty glyphs will be inserted as necessary to maintain the num glyphs value. Put under experimental for now.
Fixes#5281. Does the closure by default, but I've introduced a new flag and option to disable this behaviour since some users may want to get the minimal set if they know they don't need the mirrored variants.
When parsing axis positions in the --variations flag recognize empty values as meaning the existing value for that part. For example:
:300:500
Specifies min = existing, def = 300, max = 500.
See: https://github.com/fonttools/fonttools/issues/3322
When enabled the output subset conforms to the requirements for a base font to be patched by IFTB patches. IFTB is a proposed incremental font transfer patch. This new flag is set as experimental. Currently, setting this flag causes the output subset to also use long offsets for outline data in loca/glyf, gvar, CFF, and CFF2.
This change is a version of https://github.com/skef/harfbuzz/commit/3ae2fe2084d96f61d8ad1bbe42a6ef4e62ec830a rebased onto head w/ tests added.