Prefer utf-8 over latin-1

[GoogleCodeExporter]

What steps will reproduce the problem?

1. call, e.g., 
http://incf-dev.crbs.ucsd.edu:8080/atlas-whs?service=WPS&version=1.0.0&request=E
xecute&Identifier=ListSRSs 
(any service will I guess)

2. Look at the response headers

What is the expected output? What do you see instead?

I would expect the app to use utf-8 as encoding but according
to the response headers it seems to be latin-1
('content-type': 'application/xml;charset=ISO-8859-1')

I consider that limiting for no good reason.

Note that I'm not saying that the response header is wrong. Rather I'd like to 
point out that the app should use a different encoding entirely.

Original issue reported on code.google.com by raphael....@gmail.com on 21 Sep 2010 at 10:47

[GoogleCodeExporter]

Hi Dave,

I assume the issue is with regards to the XML schema. Could you please look 
into Raphael's note? 

Thanks,
Asif Memon

Original comment by amemon.u...@gmail.com on 6 Oct 2010 at 8:12

[GoogleCodeExporter]

No, you will need to set the character encoding of the output in the restlet, I 
believe

Original comment by david.va...@gmail.com on 6 Oct 2010 at 9:20

[GoogleCodeExporter]

Thanks for getting back to this and sorry for my late response.

AFAICS the XML returned indicates utf-8 as encoding - which is good assuming it 
is also used. I have not seen any non-ascii characters in any response so I 
can't tell yet ;-)

What I mean here are the HTTP response headers which are usually not directly 
exposed but browsers and other apps "look at" them. If you have the web 
developer toolbar installed in Firefox you can easily see them, though. 

Original comment by raphael....@gmail.com on 11 Oct 2010 at 8:56

[GoogleCodeExporter]

Seems like this is fixed by the move to the Degree-based implementation. 
Closing therefore. 

Original comment by raphael....@gmail.com on 3 Mar 2011 at 10:05

• Changed state: Fixed