- From: Alan J. Flavell <flavell@a5.ph.gla.ac.uk>
- Date: Wed, 8 Nov 2000 14:23:23 +0000 (GMT)
- To: Lisa Seeman <seeman@netvision.net.il>
- cc: "WAI (E-mail)" <w3c-wai-gl@w3.org>
On Wed, 8 Nov 2000, Lisa Seeman wrote: > Firstly the link itself would have to be in the logical architecture to be > accessible, in which case it will come out backwards to everyone else! The properly-engineered solution for that is the "Accept-charset:" header from the client to express its capabilities, with the server sending out the proper document variant by content-negotiation. You'll say, of course, that many available clients don't support it. True enough, and so that's the problem that needs solving. Seems to me that just as a personal proxy like WebWasher or Junkbuster can filter _out_ HTTP headers, presumably one could "front-end" a browser with a proxy that would put desired HTTP headers _in_, if the browser implementers couldn't be bothered to implement this part of the published protocols. BTW, you'll presumably be familiar with the discussion at http://www.nirdagan.com/hebrew/ best regards
Received on Wednesday, 8 November 2000 09:23:31 UTC