W3C home > Mailing lists > Public > www-validator@w3.org > March 2001

RE: Content negotiation: GIF v. PNG

From: Jon Haworth <JHaworth@witanjardine.co.uk>
Date: Tue, 6 Mar 2001 11:01:18 -0000
Message-ID: <67DF9B67CEFAD4119E4200D0B720FA3F13B386@BOOTROS>
To: "'www-validator@w3.org'" <www-validator@w3.org>
You know about the licensing issues with .gif files, right?

http://www.unisys.com/unisys/lzw/

The consensus seems to be that if you're using GIFs you should think about
moving them over to PNG, however at the moment, as Terje wrote, not all
clients can support PNG - the choice of when to change is up to you. I think
W3C are doing their best to support as many people as possible and have used
this as a half-way house. 

Cheers
Jon


-----Original Message-----
From: Peter Foti (PeterF) [mailto:PeterF@SystolicNetworks.com]
Sent: 05 March 2001 20:34
To: 'www-validator@w3.org'
Subject: RE: Content negotiation: GIF v. PNG


I question why this is done at all?  Why is PNG the preferred format?
It seems that if the validator was just changed to always offer the GIF
file, then no one would have this problem, and the world would be a
better place! :)  There would be no additional server configuration
required, plus you wouldn't have to worry about supporting both a PNG
version and a GIF version of the file.  It would seem logical to rely on
the method that is most portable and requires the least amount of
configuring.

-Peter


-----Original Message-----
From: www-validator-request@w3.org
[mailto:www-validator-request@w3.org]On Behalf Of Brian Gilkison
Sent: Monday, March 05, 2001 3:14 PM
To: www-validator@w3.org
Subject: Content negotiation: GIF v. PNG


Some time ago (late '99), Terje gave the following explanation as to why
there was no ".gif" or ".png" extension on the validator <img> tags,
i.e., those generated for validated pages, ala:

  <p>
    <a href="http://validator.w3.org/check/referer"><img border="0"
        src="http://www.w3.org/Icons/valid-html401"
        alt="Valid HTML 4.01!" height="31" width="88"></a>
  </p>

Terje wrote:
> The filename extension is left out to let the server negotiate with
the
> client whether to return a GIF file or a PNG file. PNG is the
preferred
> format but not all clients can handle it so there has to be a fallback
> to the GIF files. This will of course fail if the server running the
> validator does not have content negotiation enabled.

Although more an Apache question, exactly what directives are required
for
this to happen?  The above code works unchanged on my ISP's server,
presuming I have an .htaccess file with an "Options MultiViews" entry,
but
on my personal server it doesn't...  What other directives besides
"Options Multiviews' might be required?

Brian

>  Brian Gilkison           | http://w3.one.net/~gilkison/ <
>  gilkison@one.net         | finger for PGP Public key    <
>                                                          <
>    Don't steal. The government hates the competition.    <



**********************************************************************
'The information included in this Email is of a confidential nature and is 
intended only for the addressee. If you are not the intended addressee, 
any disclosure, copying or distribution by you is prohibited and may be 
unlawful. Disclosure to any party other than the addressee, whether 
inadvertent or otherwise is not intended to waive privilege or confidentiality'

**********************************************************************
Received on Tuesday, 6 March 2001 06:03:54 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 25 April 2012 12:13:55 GMT