[OpenFontLibrary] What's the big deal about @font-face anyway?
Simos Xenitellis
simos.lists at googlemail.com
Fri May 29 16:32:09 PDT 2009
On Fri, May 29, 2009 at 5:43 PM, Jeremy Dunck <jdunck at gmail.com> wrote:
> On Fri, May 29, 2009 at 11:35 AM, Simos Xenitellis
> <simos.lists at googlemail.com> wrote:
>> On Fri, May 29, 2009 at 4:35 PM, Jeremy Dunck <jdunck at gmail.com> wrote:
>>> On Fri, May 29, 2009 at 9:30 AM, Behdad Esfahbod <behdad at behdad.org> wrote:
>>>> So, please tell me, how is
>>>> making it easier for website designers to enforce their type on me a good
>>>> thing?
>>>
>>> Right now, people use sIFR or image replacement. This is hard for a
>>> viewer to change. By moving to @font-face, the viewer can still win
>>> because they can have an !important user stylesheet. I'd argue that
>>> @font-face ubiquity means the viewer haves more, not less, control.
>>>
>>
>> Or cufón.
>
> Yeah, I should have mentioned, but I think the viewer still doesn't
> have control over cufón, right?
It would be up to the website to offer the functionality for the
visitor to select
an alternative font as the preferred font. Would require a fast server
with many autogenerated fonts.
This would be easier if it was possible to negotiate between the browser and
website as to which fonts are desired, sort of 'Accept-Font' (similar
to Accept-Encoding and Accept-Language).
Can the browser negotiate with the web server which font it would prefer to see?
Simos
More information about the OpenFontLibrary
mailing list