geotoad-devel

[gtoad-devel] German characters in gpx output

[Peter J. <Pet...@we...>]

Hello,
I am using geotoad together with gpxsonar (http://gpxsonar.homeip.net) and found that the special German characters (Umlaute) are not shown correctly. I discussed that already with the author of Gpxsonar, and he told me that those characters are handled right, when a GPX file from GC is used which was fetched by Pocket Query. 

I assume that geotoad translates the original characters into unicode characters (&#xxx;) which cannot be read by gpxsonar.
If this is right, it would be nice if geotoad could code the special characters in the same way as a original Pocket Query would do.

Regards,
 Peter
__________________________________________________________
Mit WEB.DE FreePhone mit hoechster Qualitaet ab 0 Ct./Min.
weltweit telefonieren! http://freephone.web.de/?mc=021201

Re: [gtoad-devel] German characters in gpx output

[Thomas S. <th...@st...>]

On 2004-10-05, at 05.24, Peter Jonas wrote:

> I assume that geotoad translates the original characters into unicode 
> characters (&#xxx;) which cannot be read by gpxsonar.
> If this is right, it would be nice if geotoad could code the special 
> characters in the same way as a original Pocket Query would do.

I'm not currently an active member (haven't done much geocaching 
lately). If someone could post what a GPX file should look like that 
has umlauts, that would help immensely. I'm pretty sure this worked in 
previous versions. I presume you are using GT 3.7.5. If so, this commit 
to geocache/search.rb may have broken it:

----
r459 | tstrombe | 2004-09-20 19:25:21 -0500 (Mon, 20 Sep 2004) | 1 line

Fix for the new geocaching search page layout. CGI.unescapeHTML the 
geocache name to prevent " names from showing up. This may break 
international characters, but hopefully not.
----

I don't know what query you were trying to run, but I think changing 
this line in geocache/search.rb from:

                     name = CGI.unescapeHTML(name);

to:

                     name.gsub!(""", "\"");

Should fix the problem. Let me know if it does, and I'll be sure to get 
this into 3.7.6.


/ Thomas

Re: [gtoad-devel] German characters in gpx output

[Russell T. <mtn...@gm...>]

On Tue, 5 Oct 2004 08:03:01 -0500, Thomas Stromberg
<th...@st...> wrote:
> 
> I don't know what query you were trying to run, but I think changing
> this line in geocache/search.rb from:
> 
>                      name = CGI.unescapeHTML(name);
> to:
>                      name.gsub!("&quot;", "\"");
> 
> Should fix the problem. Let me know if it does, and I'll be sure to get
> this into 3.7.6.
> 

The replacement line was not working with double quotes so I tried
single quotes.  Subbing the double quote character caused other issues
so I just dropped the quote all together.

     name.gsub!('&quot;', '');

Still having trouble with the other &#xxxx; characters as shown below.
 The first is a single quote, the second is a dash.

GPX Description field:
Scott&#8217;s Mill Puzzle &#8211; Apex Triple Threat by GeoCyclist
(adopted by horsegeeks), Unknown Cache (3.0/1.5)

I'm now trying to find out where the &#xxxx characters are first translated.

-R

Russell Teague
http://mtnbike.org
If you don't see the battle, you are not in the fight.

Re: [gtoad-devel] German characters in gpx output

[Thomas S. <th...@st...>]

Russell Teague wrote:

> Still having trouble with the other &#xxxx; characters as shown below.
>  The first is a single quote, the second is a dash.
> 
> GPX Description field:
> Scott’s Mill Puzzle – Apex Triple Threat by GeoCyclist
> (adopted by horsegeeks), Unknown Cache (3.0/1.5)
> 
> I'm now trying to find out where the &#xxxx characters are first translated.

There is some awful code to generate the &#xxxx characters within 
output.rb, named makeXML(). In order for the document to be XML valid, 
and for processors to handle it, I needed to convert the high ascii 
characters to this form.

The question that I haven't seen answered yet (should be easy enough) is 
  what do we have to do to take the umlauts from the page format and 
translate them into the way the GPX files from GC.com do. I'm working 
long hours on a project at work this week, so I don't have a chance to 
examine the issue any closer.

Good luck!

/ Thomas