- From: Levantovsky, Vladimir <Vladimir.Levantovsky@monotype.com>
- Date: Wed, 20 May 2015 21:46:24 +0000
- To: WebFonts Working Group <public-webfonts-wg@w3.org>
I think there may be an easy way to signal the pre-processing of the 'hmtx' table. Since we are only considering two corner cases (either _all_ lsb data is removed or none at all) we can easily determine this case by analyzing the table directory entry for 'hmtx' - comparing the actual decompressed table size against the 'original' size will tell us all we need to know. If the original size is larger than decompressed size(and it will be, by exactly 2*numGlyphs bytes) - the decoder will know when the lsb array needs to be reconstructed. Vlad -----Original Message----- From: WebFonts Working Group Issue Tracker [mailto:sysbot+tracker@w3.org] Sent: Wednesday, May 20, 2015 4:46 PM To: public-webfonts-wg@w3.org Subject: WOFF-ACTION-176: Test hmtx transformation over google fonts corpus (how many lsb == x-min for all glyfs, what savings) WOFF-ACTION-176: Test hmtx transformation over google fonts corpus (how many lsb == x-min for all glyfs, what savings) http://www.w3.org/Fonts/WG/track/actions/176 Assigned to: Roderick Sheeter
Received on Wednesday, 20 May 2015 21:47:50 UTC