OpenType 1.8.3 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.8.3 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.
|26 August 2018||glyf — Glyph Data||The Simple Glyph Description section incorrectly stated that simple glyph descriptions apply for numberOfContours “greater than zero”. (The description for the numberOfContours field correctly states “greater than or equal to zero”.)||Corrected in 1.8.3 (2018-8-26)|
|26 August 2018||The TrueType Instruction Set||When content was ported from Microsoft Word, changes made in OpenType 1.8.1 were not retained, and some text was inadvertently removed.||Corrected in 1.8.3 (2018-8-26)|
|26 August 2018||The TrueType Instruction Set||In the description of GET VARIATIONS, two examples are provided of using an IDEF for the GET VARIATIONS op code. In OpenType 1.8, the examples incorrectly used NPUSHB instead of NPUSHW. In OpenType 1.8.1, this was corrected in one example, but the error in the other example was missed.||Corrected in 1.8.3 (2018-8-26)|
|26 August 2018||OpenType Specification Change Log||Change made to ttinst1.doc in OpenType 1.5 was not listed.||Corrected in 1.8.3 (2018-8-26)|
Would you like to provide feedback?
Our feedback system is built on GitHub Issues. Read more on our blog.