Closed while0pass closed 12 years ago
I'm really not sure exactly what you're asking for. If you can show me a pull request, I'll look at it, but other than that, the code example is just showing the working code. I'm not sure if anything else is needed. Thanks.
Actually I have yet no idea of how it should be laid out. I just wanted to attract your attention (though I'm sure you are well aware of it) to the fact that @font-face
rule is multipart and not all of its parts are supported by all the browsers. So It would be good to cover all of them somehow. In the specification they are called 'descriptors'. And some of them have well known properties counterparts, so there may be little need for them to be described. But at least unicode-range
descriptor is very desirable to be described separatly. Though I do not yet know how. Anyway thank you very much for your project.
I don't think I'm going to add anything on this topic, but if anyone wants further reading, here is the spec link:
It will be helpful to have all the font descriptors from
@font-face
rule as separate items. I mainly mean those descriptors that do not have counterparts among css properties, i.e.unicode-range
andsrc
vs.font-family
,font-weight
, etc.