+caderoux Posted January 29, 2006 Share Posted January 29, 2006 http://www.geocaching.com/track/details.as...a9-ba6a39fbd7ab Link to comment
+ZackJones Posted January 29, 2006 Share Posted January 29, 2006 There's an invalid character in one of the logs. Downlaod the KML file to your computer and then open it up with a text editor such as notepad. Scroll down to the 1/22/2005 log entry for the Workerofwood's Cito Event entry and look for the word "bugs" (without the quotes). Change it to read bug's, save the file and then you should be able to view the KML file on GE. Link to comment
+caderoux Posted January 29, 2006 Author Share Posted January 29, 2006 I know - I was reporting it so that this example can be used to fix this broken feature to properly escape its output. Link to comment
+NilsK Posted January 29, 2006 Share Posted January 29, 2006 (edited) http://www.geocaching.com/track/details.as...a9-ba6a39fbd7ab I see that quite often with TBs now. Being in germany, where we use a lot of Umlauts (äöü): I want to offer a wild guess: Could there be a problem with diacritics? Nils Edited January 29, 2006 by nilsk Link to comment
+Lil Devil Posted January 29, 2006 Share Posted January 29, 2006 (edited) Actually I think it's a problem with Google Earth. The kml file is correctly marked: <?xml version="1.0" encoding="UTF-8"?> so that should allow the diacritics to be there. If Google Earth is barfing on them then Google Earth needs to be fixed. Edited January 29, 2006 by Lil Devil Link to comment
+caderoux Posted January 30, 2006 Author Share Posted January 30, 2006 Actually I think it's a problem with Google Earth. The kml file is correctly marked: <?xml version="1.0" encoding="UTF-8"?> so that should allow the diacritics to be there. If Google Earth is barfing on them then Google Earth needs to be fixed. My example may or may not be a problem with Google Earth - it is those stupid "other" quote marks - which should be substituted or escaped. Link to comment
Recommended Posts