Try this:

geo-gid -H. GC10D4Q
geo-html2gpx -b GC10D4Q.html > GC10D4Q.gpx

In the output gpx file at least I get things like &
And things like å
Which should have been & and å
That is, the ampersand is converted to &

If I postprocess with the following, the gpx files turn out right:

sed -e 's/ / /g' -e 's/&/\&/g' -e 's/"/\"/g' -e 's/&\#/\&\#/g'

After it I do a
cmconvert -BCdDLOSt -N 50 $1.gpx
and transfer to my Palm, where I look at it with CacheMate

I am not sure exactly where the problem is.


I think there is another problem with geo-html2gpx. In the same output can be found:
<url>http://www.geocaching.com/seek/cache_details.aspx?id=ab393053-d14e-4cf3-8a66-9909ec1e5946</url>;
Which is a non-working URL, and I think it should say ?guid= instead of ?id=

/Karro

1. No idea. Live with it.

2.

2009-07-13 Rick Richardson <rick.richardson@comcast.net>
* geo-html2gpx
# alternate URL... tagtext(2, "url", BaseURL "?wp=" gcid)
# alternate URL... tagtext(2, "url", BaseURL "?id=" gid)
tagtext(2, "url", BaseURL "?wp=" gcid)

This "feature" unfortunately isn't limited to the ampersand character but shows up for each encoded entity (for example, umlaut characters like in GC1RBBE).
It's most disturbing when cache or owner names are affected.

Leave it or patch it, that's the question.