> Please see my responses to Lars.  I think if you read carefully, you will 
> agree that the prefix rule is one way, and it doesn't allow the server to 
> return "en" for a client that requests "en-us".  I'm not going to argue that 
> this is what makes the most intuitive sense.  However, we do need to stick 
> with what the standard says.

We can always insert workarounds and overrides for buggy browsers.
All of content negotiation is, by nature, optional.

The spec was written with the expectation that browser developers would
eventually learn to read.  Instead, they prefer to be bugward-compatible.

....Roy

Reply via email to