- From: Henrik Frystyk Nielsen <frystyk@ptsun00.cern.ch>
- Date: Thu, 15 Dec 94 18:51:33 +0100
- To: gtn@ebt.com
- Cc: http-wg%cuckoo.hpl.hp.com@hplb.hpl.hp.com
> The language parameter should not be part of the spec. This assumes > that a single document will contain a single language. No it doesn't. The Content-Language header has explicitly been defined so that multiple natural languages can be specified. The Accept-Language header can also contain a list of languages which also covers multi-linguistic documents. > In addition, I > tend to think that any information that is available in multiple > languages, will probably be stored as seperate files (or "documents"), > and hence, would have different URI's. This is exactly what we want to avoid ;-) > I do not think decisions can > reasonably be made automatically at the protocol level. They are > rather, a navigational problem (and this might also be better handled > at the markup level via the LANG element). If you already have the document and actually parsed it in order to find the <LANG> element, then there is no idea in the language negotiation at all. It must be done at the protocol layer. -- cheers -- Henrik
Received on Thursday, 15 December 1994 10:32:35 UTC