[Tilesathome] setting up the api was: [OSM-dev] t at h API still turn off...

[Florian Lohoff]

On Tue, Sep 02, 2008 at 12:09:51PM +0200, Martijn van Oosterhout wrote:
> On Tue, Sep 2, 2008 at 10:52 AM, Florian Lohoff <flo at rfc822.org> wrote:
> > The (un)escaping of UTF-8 characters still doesnt work and i have
> > no clue how this works so need help here ... xmllint complains about
> > the resulting osm files with >128 ascii chars are in there - And most likely
> > some &>< escaping might be missing.
> 
> Half the point of UTF-8 is that you don't need to escape anything. As
> long as you spit out exactly what was in the OSM data you should be
> fine.

I do that and it fails -  the t at h clients complains loud
about non utf-8 compliance ...

<node id="50553449" lat="51.7439626" lon="8.3798345">
 <tag k="is_in" v="Northrine-Westfalia,Germany"/>
 <tag k="name" v="Mastholte-S<FC>d"/>
 <tag k="place" v="village"/>
 <tag k="created_by" v="JOSM"/>
</node>

This is a node which fails It should be "Süd" and 0xFC followed
by a "d" is not valid utf-8.

http://tiles-one.lab.rfc822.org/api/0.5/map?bbox=8.305664,51.717779,8.481445,51.790685

Requesting from www.openstreetmap.org returns a correct entry:

  <node id="50553449" lat="51.7439626" lon="8.3798345" user="seufer_wolle" visible="true" timestamp="2007-09-13T12:27:46+01:00">
    <tag k="created_by" v="JOSM"/>
    <tag k="name" v="Mastholte-Süd"/>
    <tag k="is_in" v="Northrine-Westfalia,Germany"/>
    <tag k="place" v="village"/>
  </node>

So some recoding is going on somewhere (i'll not exclude intelligent perl)

Flo
-- 
Florian Lohoff                  flo at rfc822.org             +49-171-2280134
	Those who would give up a little freedom to get a little 
          security shall soon have neither - Benjamin Franklin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
URL: <http://lists.openstreetmap.org/pipermail/tilesathome/attachments/20080902/60d8a8f9/attachment.pgp>