- From: Rafael Otake <rafaelotake@hotmail.com>
- Date: Tue, 04 Feb 2003 10:29:42 -0600
- To: www-style@w3.org
Some features that could be usable in @font-face are anti-alias settings, or specific panose-1 descriptors, to "make" the font instead of writing a name. It could be an "hexadecimal" alternative to font-weight, font-stretch, font-face. Maybe in the future the user agent could "generate" the font with a vector engine or something like that. The Generic-Families clasification could me a little more specific, maybe for print-media or visual-media, like "Slab-serif" for Egyptian, "Serif-Modern" for Bodoni, "Semi-Grotesque" (or Semi-Sans Serif), for Optima, "Hand-Writing" and so on. Could the support for Graphite be via mime-type id?, or plug-in?, or the PARM element?... These are just some ideas, if some one use them... please give me some credit. Rafael Otake. >>We're in the middle of a project to provide support for Graphite in the >>Mozilla browser. And to do that we want to make sure that there is >>adequate markup in XHTML to handle the equivalent of the behavior of our >>Graphite-based text editor. With regard to features, you may have data >>that needs to be marked up with a specific bunch of feature settings, so >>that it is sure to be displayed the way the author intended. >Sounds to me as if you were looking for CSS's @font-face construct and its >children: <http://www.w3.org/TR/CSS2/fonts.html#font-selection>. >If you want to do the world a favor, show us that it's usable by adding @font-face support to Gecko. _________________________________________________________________ MSN Fotos: la forma más fácil de compartir e imprimir fotos. http://photos.msn.es/support/worldwide.aspx
Received on Tuesday, 4 February 2003 11:35:05 UTC