Closing ACTION-2887: Look at patd's inadvertent-svg-font tests to add woff fallback

Hello,

ACTION-2887: Look at patd's inadvertent-svg-font tests to add woff fallback

From http://lists.w3.org/Archives/Public/public-svg-wg/2010OctDec/0075.html


> The following test cases include SVG Fonts, which either is not integral to the tests, or should be renamed/categorized as fonts-
> text-text-04-t.svg
> text-text-05-t.svg
> text-text-06-t.svg
> masking-mask-01-b.svg
> pservers-grad-08-b.svg
> render-elems-06-t.svg
> render-elems-07-t.svg
> render-elems-08-t.svg
> text-align-08-b.svg

These all now have WOFF fallback as well as SVG Fonts. In some cases i had to regenerate the SVG fonts so that they remained the same as the WOFF ones.

I have also duplicated text-fonts-203-t.svg (which uses SVG fonts) as text-fonts-204-t.svg (which uses WOFF). Since this tests loading multiple fonts from a family, I didn't want to confuse the test in the case where an implementation supports both formats.

text-fonts-204-t.svg needs a reviewer. Its much the same as 203 except for using @font-face syntax rather than <font-face>.

Both text-fonts-203-t.svg and text-fonts-204-t.svg have had the font names obfuscated (e.g. ZSB rather than Zalamander-SemiBold) because apparently on MacOs the system libraries can try to guess the weights from the filenames (!) on the assumption that the weights in the fonts are wrong. And apparently they often are deliberately wrong, to work around a font weight/faux-bold bug in GDI+. Joy. Anyway the tests try to avoid tripping over that as its not the point of the test.


-- 
 Chris Lilley   Technical Director, Interaction Domain                 
 W3C Graphics Activity Lead, Fonts Activity Lead
 Co-Chair, W3C Hypertext CG
 Member, CSS, WebFonts, SVG Working Groups

Received on Friday, 25 February 2011 05:19:23 UTC