On Aug 13, 6:57 pm, Rossko <[email protected]> wrote:
> > The Atom geoxml I use, choosing the most important error need a front
> > or back fix, is classifiedsmarket.appspot.com/georss
>
> Tip : use 'view source' in your browser to see what data gets
> delivered.
> Another tip : put some line breaks in your 'atom' output so that you
> can read it yourself.
>
> I see something like
> <?xml version="1.0" encoding="UTF-8"?>
> <feed xmlns:dc="http://purl.org/dc/elements/1.1/";
> xmlns:georss="http://www.georss.org/georss"; xmlns="http://www.w3.org/
> 2005/Atom">
> <title>classifiedsmarket.appspot.com 52</title>
> <link href="http://classifiedsmarket.appspot.com"; rel="self"/>
> <id>http://classifiedsmarket.appspot.com/</id>
> <updated>2009-08-13T18:38:46.694749Z</updated>
> <generator uri="http://
> classifiedsmarket.appspot.com/">classifiedsmarket.appspot.com</
> generator>
> <entry>
> <title><![CDATA[nighties]]></title>
> <link href="http://classifiedsmarket.appspot.com/117426"/>
> <id>http://classifiedsmarket.appspot.com/117426</id>
> <updated>2009-08-13T16:54:26.388618Z</updated>
> <author><name>annainighties</name></author>
> <georss:point>11 78</georss:point>
> <published>2009-08-13T16:54:26.388481Z</published>
> <summary type="xhtml">
> <div xmlns="http://www.w3.org/1999/xhtml";>HOME BASED JOB - NIGHTIES
> SALES ....
> etc.
>
> This doesn't look very convincing -
>      <georss:point>11 78</georss:point>
> is your generator losing the part after the decimal point?
>
> I'll repeat that GGeoXml doesn't support all the possible features of
> GeoRSS, in particular I'd expect it to totally ignore your tags
> <summary> and <div>.  Is that what your problem is?
Thank you I'm even lost about which end, javascript or python to
handle
Worst problem:
The ' turns out &#39;
same problem is & turns out junk too
backend django app engine
front end javascipt
atom feed title tag
My problem is that opostrophe, ampersand and more turn out &#39;
I got backend very readable
<georss:point>%d %d</georss:point>
...
ad.geopt.lat,ad.geopt.lon
Though unsure standard order for geopoints, there should be iso
standard anyway testing this too for most important
<title><![CDATA[%s]]></title>
viewedsource
<title><![CDATA[announcement subject]]></title>
still junk view and true can't search semantic meaning of %s or %d
along the same idea that these are escape chars and what the third
should be for decimal or float when I understand %s is word, %d is
integer and a third one should be used here instead:
<georss:point>%d %d</georss:point>
%d I understand is integer can use %s instead still looking for
maximum standard compliance with minimal source.

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Google Maps API" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/Google-Maps-API?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to