- From: Orion Adrian <orion.adrian@gmail.com>
- Date: Mon, 4 Jul 2005 23:11:45 -0400
- To: www-style@w3.org
On 7/4/05, Devin Bayer <devin.bayer@rochester.edu> wrote: > > On Jul 4, 2005, at 17:27, Orion Adrian wrote: > > > > > On 7/4/05, David Woolley <david@djwhome.demon.co.uk> wrote: > > > >> > >>> Ok, rather than uncompressed, use PNG. But content negotiation > >>> should > >>> be something done by a server, not a user. A person's time is far > >>> more > >> > >> It can be rather difficult when the server is a CD-ROM containing > >> an offline copy. > > > > It's a rather simplistic system that could be added to web browsers. > > I'm not advocating it. I'm advocating that material designed to be > > presented on a server use the advantages of a server solution. > > What about when the material is used in ways it wasn't designed for. > I designed websites before using content negotiation for alternative > image formats. But it becomes a problem when one wants to recursivly > download the site. References of the form <img src="images/dog" /> > create two problems. The OS will not recognize the file type, and > the web browser will not recognize the file type. Maybe five years > down the read we can expect files without extensions to be correctly > handled, but for now being explicit is more convenient. This is due to the lack of a type attribute which exists everywhere else. A type attribute which does exist on the object element which is surplanting the img element. Again this is something that is being solved in the server environment and will be solved in the OS environment shortly. Microsoft has slowly but surely been reducing the importance of extensions and Mac OSX never had them. Orion Adrian Orion Adrian
Received on Tuesday, 5 July 2005 03:11:48 UTC