- From: Dave Raggett <dsr@w3.org>
- Date: Tue, 25 Apr 2006 18:41:06 +0100 (BST)
- To: Octavio Alvarez <alvarezp@alvarezp.ods.org>
- Cc: www-style@w3.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tue, 25 Apr 2006, Octavio Alvarez wrote: >> My computer might know about a font server, but it probably won't >> have the fonts used on your web site, especially fonts that have >> been developed specially for that site. To get around that, the >> web page could specify the URI for a font server. > > No, the font would be just like any other resource, even cached, so > MUAs only downloads what it needs. > > If the site wants to have fonts available the same site should > bring a font server up. How is the browser supposed to locate that server? Are you proposing that there should be a standard for how a browser asks for a font from the server that the web page was downloaded from? I presume it would have to involve the URI for the web page in question and the name of the font, but might involve other information as well. >> The next question is what glyphs to ask the font server for, as >> the whole font may be too large. > > MUAs can also examine the documents to check what glyphs are used > and auto-determine the range. That is easy enough for static documents, but much harder for dynamically generated documents that are customized for a specific request. How would you propose to handle such web pages? Dave Raggett <dsr@w3.org> W3C lead for multimodal interaction http://www.w3.org/People/Raggett +44 1225 866240 (or 867351) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFETl84b3AdEmxAsUsRApHOAJ9irNybHTBxyAbdPnXImR2WQUu0TgCdGeJi bTibnnA4WGiq45yWPKSbZ/Q= =uRIN -----END PGP SIGNATURE-----
Received on Tuesday, 25 April 2006 17:41:28 UTC