OpenType 1.9.1 errata

This page documents errors in the OpenType specification that have technical significance and could lead to incorrect implementations. The scope is limited to issues in which the OpenType 1.9.1 specification as originally published implies technical details that are contrary to the intended design. Corrections may include corrections to incorrect values related to certain table fields, incorrect formulas for computing certain values, or similar issues. Corrections will not include any changes to data structures. If the textual change required for the correction is minor, the correction will be made in the specification and also listed here. If larger textual changes are required, the issue may be described here, but actual changes may be left to a future version. In either case, the status will be indicated in the table below.

Certain minor, editorial errors such as mis-spelling of words with no technical impact may on occasion be corrected silently, without notice or version update.

Date	Page	Description	Status
9 October 2024	CFF2 — Compact Font Format (CFF) Version 2	The description of StemSnapH and StemSnapV included a statement suggesting that, if the values are blended in a variable font and the derived instance values are not in increasing order, then behavior is not defined. That is incorrect: the values are still valid. Similarly, the discussion of blended stem and end hints included a statement suggesting that, if derived instance values for stems are not in order, then behavior is not defined. That is incorrect: the values are still valid, and the bit flag operands for cntrmask and hintmask operators reference stems in their encoded order.	Corrected in 1.9.1 (2024-10-9).
6 July 2024	OpenType™ Layout Common Table Formats	In the description for the SequenceRuleSet table, the size for the seqRuleOffsets[] array incorrectly referred to a field name “posRuleCount” instead of the “seqRuleCount” field.	Corrected in 1.9.1 (2024-7-6).