[mpeg-OTspec] Incorrect offset type in MATH table spec
Levantovsky, Vladimir
vladimir.levantovsky at monotype.com
Fri Jul 18 00:45:53 CEST 2014
Thank you Sergey,
I've got permission from the ISO Secretariat to make editorial changes in the spec before it is submitted for a ballot and I am going to implement the changes you suggested. To clarify - the data types for table entries listed below in your email should all be changes to "Offset" instead of "ULONG", right?
Thank you,
Vladimir
From: mpeg-OTspec at yahoogroups.com [mailto:mpeg-OTspec at yahoogroups.com] On Behalf Of Sergey Malkin sergey.malkin at yahoo.com [mpeg-OTspec]
Sent: Wednesday, July 16, 2014 5:51 PM
To: mpeg-OTspec at yahoogroups.com
Subject: RE: [mpeg-OTspec] Incorrect offset type in MATH table spec
Below is full list of fields that require update:
MathValueRecord table:DeviceTable
MathHeaderTable table:MathConstants, MathGLyphInfo, MathVariants
MathGlyphInfo table: MathITalicsCorrectionInfo, MathTopAccentAttachment, ExtendedShapeCoverage, MathKernInfo
MathItalicsCorrectionInfo table: Coverage
MathTopAccentAttachment table: TopAccentCoverage
MathKernInfo table: MathKernCoverage
MathKernInfoRecord table: TopRightMathKern, TopLeftMathKern, BottomRightMathKern, BottomLeftMathKern
MathVariants table: VertGlyphCoverage, HorizGlyphCoverage, VertGlyphConstruction, HorizGlyphConstruction
MathGlyphConstruction table: GlyphAssembly
Also there is also a type-o in the header of one table:
Math Neader Table -> Math Header Table
Thanks,
Sergey
________________________________
To: mpeg-otspec at yahoogroups.com<mailto:mpeg-otspec at yahoogroups.com>
From: mpeg-OTspec-noreply at yahoogroups.com<mailto:mpeg-OTspec-noreply at yahoogroups.com>
Date: Wed, 16 Jul 2014 10:36:02 -0700
Subject: [mpeg-OTspec] Incorrect offset type in MATH table spec
Hi,
It was brought to our attention that version of MATH table in ISO spec as well as in OpenType spec on Microsoft site has incorrect data type describing offsets inside table. It looks like all 2-byte offset data types had been replaced with ULONG across the whole spec. Names and descriptions of the fields appear unchanged, only data types should be replaced back to 'Offset'.
Given that format actually didn't change since its creation, we should be able to treat this fix as editorial change and fast-track it into specification.
Thanks,
Sergey
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.aau.at/pipermail/mpeg-otspec/attachments/20140717/4f67c542/attachment.html>
More information about the mpeg-otspec
mailing list