[OSM-dev] REST API encoding

Dean Earley dean at earlsoft.co.uk
Wed Jul 12 14:27:21 BST 2006


> Found it !
> This is a server inconsistency in charset use.
>
> Server use ISO-8859-1 for segment and way request, but a mix of
> ISO-8859-1 and UTF-8 for map request.
>
> If someone has the time to look at this... The server should only use
> UTF-8 (as it does actually for ways in the map request) so we could
> update clients and close trac tickets #28 and #29.
>
>
> Here is the reply for single segment :
>>     <tag k="name" v="t&#xE9;st"/>
<SNIP>
>
> For single way :
>>     <tag k="name" v="t&#xE9;st"/>
<SNIP>
>
> A9 is the hex code for é in ISO-8859-1
> C3A9 is the hex code for é UTF-8

Technically, these are neither.
It happens to be hex encoded representation of the aforementioned encoding
formats. Saying "it is 8859-1" or "it is utf-8" means it will be that
format raw (not hex encoded).

-- 
Dean Earley, Dee (dean at earlsoft.co.uk)

irc:    irc://irc.blitzed.org/
web:    http://personal.earlsoft.co.uk
phone:  +44 (0)780 8369596






More information about the dev mailing list