W3C home > Mailing lists > Public > www-style@w3.org > March 2010

Re: font-specific feature handling

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Thu, 18 Mar 2010 20:09:33 -0700
Message-ID: <dd0fbad1003182009y40d97ae8lc2e0f3cbe06f9a14@mail.gmail.com>
To: Christopher Slye <cslye@adobe.com>
Cc: www-style <www-style@w3.org>
On Thu, Mar 18, 2010 at 6:00 PM, Christopher Slye <cslye@adobe.com> wrote:
> On Mar 18, 2010, at 5:19 PM, Tab Atkins Jr. wrote:
>> Otherwise, fantasai's alt-set idea seems like an interesting solution
>> to Daggett's objections.
>
> As much as I agree with John's aversion to code clutter, I do think that it's better to keep these things tied to specific fonts, one way or another. That said, I don't think John's solution would be the end of the world. We already have this problem in desktop apps like InDesign, which preserve these kinds of font-specific substitutions. I don't think it's had a big real-world impact yet. Maybe someday it will.

Still a fundamentally different set of problems, though.  If InDesign
preserves the substitutions, it's merely an annoyance when you notice
that the new font you're using has weird substitutions.  In CSS, the
weird substitutions will often/nearly always occur in a fallback font
that the author *never sees*, and thus won't have an immediate clue
that there's a problem.

~TJ
Received on Friday, 19 March 2010 03:10:25 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 17:20:25 GMT