Re: content negotiation for language in web pages
Hi,
>>"James" == James A Treacy <treacy@debian.org> writes:
James> The big problem with this is that it all hinges on every server
James> supporting content negotiation (CN from here on in). We don't
James> control the mirrors so it's a big problem. Without content
James> negotiation, you run into a problem in deciding how to write
James> links. If you just write <foo>.html, then CN does the right
James> thing. Without CN, you can only get one language.
Pardon me for being dense, but it is not any worse than the
current situation, is it? I mean, we have the default language at the
moment. Though we can't mandate content negotiation on mirror
servers, we can suggest that they do so; don't most modern servers
support CN quite easily?
And in any case, it does seem like CN is the way to go, and
even mirror servers that do not support it yet shall gradually get to
supporting it.
manoj
--
The likelihood of anything happening is in direct proportion to the
amount of trouble it will cause if it does happen. -- Sam W. Warren
Manoj Srivastava <srivasta@acm.org> <http://www.datasync.com/%7Esrivasta/>
Key C7261095 fingerprint = CB D9 F4 12 68 07 E4 05 CC 2D 27 12 1D F5 E8 6E
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-www-request@lists.debian.org .
Trouble? e-mail to templin@bucknell.edu .
Reply to: