A quick overview on that has changed in TrailRunner 3.0:

Reworked UI and wording
To better meet the vocabulary being used in other applications, TrailRunner will no longer speak about workouts but activities.
Also activities, routes and your network of tracks are displayed in a better UI.



All application modes now come with their own dedicated toolbar at the bottom end of the window making the UI much more clearer.

New Network of tracks editor
The new editor makes managing your network of tracks much easier. Drag selection and shift click extent selection lets you select more than one element
Operations on the action toolbar give you the toolset to effectively remove duplicate tracks and waypoints.
A list of modified tracks on the left helps you in finding out what was newly added to your network and may contain duplications to be merged into your network of tracks.



WayPoint Perimeters
As you know, tracks can be spitted by a waypoint nearby. In previous versions of TrailRunner the maximum distance from a way-point to track to make this happen was a fixed value of 10 meters.
In the new network of tracks editor, you now see this perimeter range around selected waypoints and you can drag the border to extend the range.
This is especially useful when you have locations where great chaos lies within because many routes start and end somewhere around this spot. Now you can just increase the perimeter of one representative for this location and TrailRunner will then be able to better consolidate new elements within this area.

Better OpenStreetMap Source
Changed the Background Map to CloudMade openStreetMap Fine Line with a contour overlay.
To effectively reload all map tiles, remove the Library/Caches/TrailRunner/GeoTiles/openstreetmap.org folder

Improved Integration with EveryTrail

The community routes browser and importer now supports an improved API version for finding routes nearby on everytrail.com. Additionally TrailRunner hilights not only the location of routes nearby but also displays the tracks. So you now easily can view what courses the routes have.

Improved Diary
The diary window now displays a map and more statistical information on the selected activity.



Simplified process of localization
Over the years, the number of strings requiring localization grew to a huge number. A new database based application now helps localizers manage and update the localizations with a very easy interface that also contains a ToDo list and automatic pre-translation provided by translate.google.com
If you would like to help out with an updated or even new localization, please contact me.



QuickGuide for TrailRunner 3.0
The QuickGuide shows you all main features of the application. Great for testing everything out:
> QuickGuide

Tags: import, Maps, GoogleEarth, routes, diary, routing, Localizations, Merge, openstreetmap

With the fabulous help of many users, TrailRunner is localized to German, Swedish, Italian, traditional Chinese (Taiwan), French, Dutch and Japanese. To everyone who had completed the original translations or improved them by their comments, thank you very much!

[Updated] Japanese: Takashi, Toshimi, Norihisa
Czech: Marek
Français: Raphael, Xavier, Olivier, David
Italiano: Cesare, Oskar, Pierino
Español: Oscar, Juan, Javier
Taiwanese: Nitoc
Dutch: Steven, Bart
Swedish: Henrik
Simplified Chinese: Myckel

If you like to translate TrailRunner to your language or if you would like to supplement an existing translation, please contact me and use the following application I wrote:

1. Download the Localizer Application: http://dl.dropbox.com/u/1963886/Localizer.zip
2. Drag the TrailRunner.binary Database onto the application icon.
3. In the top search bar, select Language and search for you target language, e.g. fr for French
   
4. The table below now shows all strings known to TrailRunner with the original language in english and a localization below each entry.
   
5. In the button bar below the table, click on the button Next (Command-1) to go to the next untranslated entry.
6. To translate the original text in english to a common word being used by standard Apple Apps (like File, Copy, Delete, Clipboard, etc) use the Lookup button. It may not produce any result as I may already have done that. If the lookup was unsuccessful, choose the next step:
7. Either click on Translate (Command-3) to translate the whole string using translate.google.com or select a fragment in the Localized String edit field and click on Translate Selection (lower right button) to translate only the selection. You may also select a word and click on Suggestions to view previous translations of that word.
8. Accept removes the marker NEW or CHANGED. These are set if the original had changed or was added. Accept if the translation is still ok. The marker is used for the Next button to jump to the next location were work is being required.
9. Update resets the translation to the original for that you can redo your work.
10. Please never edit the refactoring fields for Key or the Table.
11. The buttons Import and Export are exclusive to me, you do not require them.
12. When you feel like enough work has been put into the translation by your side, save the document and send me the TrailRunner.binary file.
13. Please note that for TrailRunner mini and RaceBunny a second Database with the name TrailRunnerMini_RaceBunny.binary exists. For updating that one the same as above applies.

Please let me know how it goes, free registration waiting as an award ;-)

Tags: Localizations