GPX to HTML Converter
version 1.71 now will allow abbreviations of long-name cache series for use in your GPS.
version 1.60 now will add notes from Watcher to the cache pages. It also allows a distance limit for caches sorted from reference locations.
version 1.50 uses a different date/time engine, and can now handle dates before the Unix epoch. So it will work with benchmark GPX files from bmgpx.
Version 1.30 has some big changes. First, the decoded hints are now at the bottom of the cache pages, so there is no separate hints file. Second, this version now writes out a .loc file named Caches.loc that contains the caches in a format easily read by EasyGPS or ExpertGPS. The caches in this new file have been processed through gpx2html, so corrected caches and ignored caches are the same as your HTML version.
Version 1.20 has been upgraded to use the new groundspeak:exported field (added by ClayJar, who wrote Watcher) to correctly record date each cache description was exported from geocaching.com. The version also includes a new index page of unfound caches, and improved cache sorting that will work with the new geocaching ID-naming scheme due in a month or so.
Version 1.19 fixes an issue some people had with the use of the File::Slurp package. The GPX cleaner now does not use File::Slurp, so it should be more compatible.
Version 1.18 now tracks travel bugs, and generates a new index page of caches with travel bugs, sorted by date the cache was last found. The caches with travel bugs that were most recently logged appear at the top of this index page.
Version 1.17 fixes an issue with Plucker, in which Plucker refuses to load HTML files with illegal HTML in them. Plucker is very picky about HTML, so even if a page looks good in a browser it might contain bad HTML from Plucker's point of view. This is normally not a big problem; a few cache pages might not load, but that's life. However, if the illegal HTML was in a hint, then Plucker would refuse to load the entire hints file! So all but the most basic HTML is being stripped from hints.
I have written a little Perl script that will clean GPX files to eliminate illegal XML characters, which appear to be present in some cache descriptions. I don't have it as an exe file, so you'll need Perl to run it for now. It's gpxclean.pl. If you use gpx2html, the cleaning is now built in to the application, so you won't need it.