In the four examples at http://cs.sru.edu/~ddailey/svg/embedSVGfont1.html
Here are the scores by browser for what I think should be proper display (if I understand how <font> is supposed to work): IE/Adobe ASV == 4/4 Opera ==1/4 Chrome ==1/4 Safari ==1/4 Firefox ==0/4 IE9 ==0/4 The four tests are 1. Support of d attribute within glyph 2. Support of simple black path as child of glyph 3. Support of simple red path as child of glyph 4. Support of path with animated gradient in glyph Several questions of different sorts follow: A. Does anyone know when any browser is likely to take the next step (to do simple paths as children of glyphs)??? It would be important for both accessibility and for the implementation of emoji (in which color is a part of the Unicode definition of many of the characters). An emoji subset of the Symbola font from George Douros can be seen here in Opera, Safari, Chrome or ASV: http://cs.sru.edu/~ddailey/svg/SymbolaB1.svg The data is currently about 2MB for the 1500 some odd characters. It would be greatly reduced in size, as well as more semantically appropriate, and accessible, if we had access to gradients, color, pattern, and replicate for the definitions of the glyphs. B. Curiously I see that Firefox substitutes its own charset for many of the emoji. Does anyone know where I can get the source code for the symbols used in Firefox?? C. I was unhappy with the mushroom character U+1f344, so I played a bit with rebuilding it as follows: <glyph glyph-name="MUSHROOMcandidate2" unicode="p" horiz-adv-x="1940" d = "M 1550 710.5 Q 1650 840 1610.5 920.5 Q 1580 1010 1130.5 970 Q 690 930 840 810 Q 990 690 1010.5 450.5 Q 1040 220 1190 190.5 Q 1340 170 1480.5 210 Q 1630 250 1540 420 Q 1450 590 1550 710.5 M 940.5 860.5 Q 610 1100 630.5 1170 Q 660 1240 770 1250.5 Q 880 1270 1110.5 1270 Q 1350 1270 1610 1300 Q 1870 1330 1920 1250.5 Q 1970 1180 1810 1060 Q 1650 940 1460.5 780.5 Q 1280 630 940.5 860.5 z"> </glyph> The multiple Moveto commands, however result in fill-rule=evenodd being applied by default. Does anyone know if that is what is supposed to happen? It makes it rather goofy, until we get <superpath> in SVG since overlapping boundaries will have to trace one another unless we get support for <g> as a child of <glyph>. Support for iconographic script such as emoji, depends rather critically upon <replicate> -- just another use case for those keeping score. The count of distinct use cases is now 2713 - the approximate year that <replicate> and <random> will enter SVG. Cheers David [Non-text portions of this message have been removed] ------------------------------------ ----- To unsubscribe send a message to: [email protected] -or- visit http://groups.yahoo.com/group/svg-developers and click "edit my membership" ----Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/svg-developers/ <*> Your email settings: Individual Email | Traditional <*> To change settings online go to: http://groups.yahoo.com/group/svg-developers/join (Yahoo! ID required) <*> To change settings via email: [email protected] [email protected] <*> To unsubscribe from this group, send an email to: [email protected] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
