GpsPrune is available to download from the downloads page, with the latest released version being version 13.3. This page describes some of the features which are new with this version.
For information about the forthcoming version 14, see the development page.
Apart from fixing the single text which somehow managed to escape the clutches of the translation tools for version 13, there are also a few little changes which got bundled into an intermediate release:
Functions requiring new texts will come with version 14.
The most important change to come with version 13 is the name change. I was reluctant to change the name, but more and more Debian and Ubuntu users are joining and for their own reasons, their package is called "gpsprune", not prune. Now both names are being used and that's confusing, so the easiest solution is to change the name of the application for everybody, from Prune to GpsPrune. I hope that doesn't upset too many users!
geonames.org has been having severe problems with their wikipedia services, so a small change is required for a new username field to be passed. We're still getting timeouts and errors even with this field and the new servers, but there's not a lot we can do about this for now. In another minor change (suggested on the sourceforge forums), the <description> tags in gpx and kml files are now being handled, so you can load and edit and save these fields too (also to/from text files).
There's also a new compression algorithm available to add to the others - if you want you can now apply the Douglas-Peucker algorithm to the points, which uses the angles subtended between points rather than distances between them. Using this algorithm, if you have a series of points on a dead straight line, they will be considered superfluous and will be deleted. In the parts of the track where the heading changes, points are more likely to be kept and so the shape of the track is retained. Depending on your data, this might be a useful additional option.
There's a minor bugfix for when tile caching is enabled but the cache directory has been deleted. In version 12.1 Prune tries to write to the cache and fails, thus no map tiles are shown. Now the caching is simply disabled and so the tiles are retrieved as if tile caching was off.
There's also now an option for autosaving the settings file, so you don't have to remember to save your settings each time. If this option is enabled, the settings will get saved each time you exit GpsPrune.
Prune has been able to load KMZ files (and zipped GPX files) since version 7, but until now it has ignored any photos which might also be within the archive. Unfortunately that includes the photo thumbnails which Prune itself is able to write. Now that shortcoming is fixed, and GpsPrune can now asynchronously load the photos (or audio files) from inside zip archives. Of course they'll be attached to the appropriate points too. As a bonus, this works if a kml or gpx file includes a http:// URL to images (or audio) on the web too.
Thanks to a user suggestion we've also now got the ability to import data files through GPSBabel, so just on the off-chance that you're dealing with files which aren't text or gpx or kml or kmz or nmea, then you no longer have to call GPSBabel separately to convert the file and then open it in GpsPrune, you can do it one step. The screenshot here shows the import of an osm file from openstreetmap, where the file type in the dropdown is suggested automatically based on the filename.
After many requests, the GPX export dialog now has an option to specify UTF-8 encoding for the export. Up until now Prune has just used the system default encoding when writing files, just to make sure that other programs on the same machine can read it properly. So for systems set up for UTF-8, everything has always been written in UTF-8, but for other systems, other encoding schemes are used such as ISO-8859-* or windows-1252. With this new pair of radio buttons, you can choose whether to write your gpx file using the system encoding, or explicitly specify UTF-8. This should make it easier for other programs and web services to read the files properly if they only support UTF-8.
There's a new cache management feature, so you can see how much space is being taken up by your tiles and which backgrounds use which directories. This is shown in the screenshot to the right. Then you can choose to delete whole tilesets or to delete files older than a chosen age. This lets you clear out the cache to remove unneeded files, or to force a complete refresh of a particular tileset.
Two additional features managed to squeeze in before the freeze - firstly a menu of recently-used files, so you can reload them with a click. The default is to remember the last 6 files opened, maybe in future this can be made configurable to allow larger or smaller lists. And secondly there's now a display field to show the compass bearing at which photos were taken - of course only if this information is stored in the exif data. There's no facility to edit or resave this field though. But it might still be useful if you're using photos for mapping etc.
Another small change which you may not even notice - up till now, the transparency slider at the top of the map has only controlled the transparency of the background maps. With version 13, you can now reduce the visibility of the track too, so that you can get a clearer view of the map below (for example, to see if the map has a hiking path marked there or not). Now the slider is by default in the middle (both track and map at full visibility), and you can slide it either to left (to see the map better) or to the right (to see the track better).
See the development page for details on what's coming with version 14.