- From: Khaled Hosny <khaledhosny@eglug.org>
- Date: Mon, 22 Jun 2015 21:40:21 +0200
- To: WebFonts WG <public-webfonts-wg@w3.org>
The test plan[1] suggests creating a glyph containing the invalid UintBase128-encoded values, but UintBase128 is only used in the origLength and transformLength of the table directory, so I’m not sure how this be done. Implementing the case of value with leading zero in the table lengths is possible, but I’m not sure if it is possible to make an otherwise valid font for the other two cases, so it will likely be rejected for other reasons, WDYT? 1. https://www.w3.org/Fonts/WG/wiki/TestPlan20-UserAgent#mustRejectInvalidBase128
Received on Monday, 22 June 2015 19:47:14 UTC