addition of language metadata

[Daniel Morissette]

Kralidis,Tom [Burlington] wrote:
> 
> OK, so what about agreeing on hardcoding OWS Common XML ExceptionReport
> messages with "en-US", and "ows_language" for the language for things
> like stuff like DataIdentification (which msOWSGetLanguage would be
> applied)?
> 

Sure. That sounds like the best compromise for now.


>> Will clients get confused if they get the capabilities in one 
>> language and the exceptions in another language?
>>
> 
> They *shouldn't*, seeing that they should check the @language attribute
> of the XML response for ExceptionReport and DataIdentification.
> 
> HTTP headers would get more complex, since the client may ask for a
> specific language (i.e. Accept-Language=en-US,en;q=0.5), and the server
> would respond with Content-Language=ows_language).
> 
> What is MapServer's current stance on HTTP header responses for
> outputting language?  It looks like this isn't implemented yet (mind
> you, it would need more discussion).
> 

MapServer doesn't deal with those headers right now.

Daniel
-- 
Daniel Morissette
http://www.mapgears.com/