- From: Levantovsky, Vladimir <Vladimir.Levantovsky@monotype.com>
- Date: Thu, 3 Dec 2015 22:44:49 +0000
- To: WebFonts Working Group <public-webfonts-wg@w3.org>
Folks, Following up on our telcon discussion yesterday - mandating the use of known table tags requires new conformance test cases. I have added the "MUST" requirement for encoder to use known table tags but I am somewhat reluctant to do the same on the UA side and would like to explore and hear your opinion on the following: - Does it make sense to allow decoders to process an input font even if known tables are encoded *without transform* using custom table flag with the known tag that follows? Seems like this would be harmless and easy way to preserve backward compatibility. - Similarly, does it make sense to mandate that only those tables that have transform defined be encoded using known table tags? This would likely be a safer way to deal with transformed tables but, hypothetically, would limit our ability to introduce new transforms for new font tables yet to be defined in the future. - Should we simply replicate the "MUST use known table tags" for the UA without any regard for transform flags value? Thank you, Vlad -----Original Message----- From: WebFonts Working Group Issue Tracker [mailto:sysbot+tracker@w3.org] Sent: Thursday, December 03, 2015 5:19 PM To: public-webfonts-wg@w3.org Subject: WOFF-ACTION-193: Known tags must use known tag format WOFF-ACTION-193: Known tags must use known tag format http://www.w3.org/Fonts/WG/track/actions/193 Assigned to: Vladimir Levantovsky Known tags must use known tag format
Received on Thursday, 3 December 2015 22:45:20 UTC