- From: Octavio Alvarez Piza <alvarezp@alvarezp.ods.org>
- Date: Tue, 25 Apr 2006 09:28:59 -0700
- To: Philip TAYLOR <P.Taylor@Rhul.Ac.Uk>
- Cc: www-style@w3.org
On Tue, 25 Apr 2006 16:57:13 +0100
Philip TAYLOR <P.Taylor@Rhul.Ac.Uk> wrote:
>
>
> Octavio Alvarez Piza wrote:
>
> >>would this not be more likely to be
> >>
> >> > font-family: "TSCu_Comic", url(TSCu_Comic.ttf), sans-serif;
> >>
> >>with the semantics "First look for a resident copy of "TSCu_Comic",
> >>then try to download one if there is no resident copy, and finally
> >>fall back on the browser sans font if the download fails or is not
> >>supported ? I cannot see why one might want your ordering in
> >>99.9% of cases.
> >
> >
> > Being CSS information about a web page, it should *never* tell a
> > browser how to behave: that is up to the standard. That should be
> > simply
> >
> > font-family: "TSCu_Comic", url(TSCu_Comic.ttf), sans-serif;
>
> I do not understand the difference between what you and I have
> written : are you not saying exactly the same as me (up to this
> point) ? Or is your objection to the fact that I sought to make
> the semantics explicit, whereas you would prefer to leave them
> unstated and rely on the readers' familiarity with CSS ?
No, I meant what I said, but the example I wrote was dork. If I
had a nickle for each time...
The example I meant was:
font-family: "TSCu_Comic", sans-serif; /* without the url() part */
[quote]
and have a global definition of the fonts, say:
@font_url('TSCu_Comic', 'b', url(TSCu_Comic-b.ttf)); /* Where to find bold */
@font_url('TSCu_Comic', 'n', url(TSCu_Comic-n.ttf)); /* Where to find normal */
@font_url('TSCu_Comic', 'o', url(TSCu_Comic-o.ttf)); /* Where to find obliques */
[/quote]
or even
@font_url('TSCu_Comic', url(TSCu_Comic-o.ttf)); /* The whole font */
I prefer font servers though, because of downloading of ALL glyphs, instead of
the ones just needed.
Received on Tuesday, 25 April 2006 16:31:42 UTC