If you'd like to help translate GPSLog Labs into your language I'd love to hear from you, please contact me at email@example.com.
Once you've been granted translator permissions, you will see the Translate link at the bottom of each page on GPSLog Labs:
This will take you to Rosetta, an online tool for editing translations. Select your language from the list:
The main translation screen is pretty simple. The first column shows the original English version of the text, and you enter the translated version for your language in the second column.
Any blank strings will be left in English, so you can fill in what makes sense and leave the rest for later.
There are a lot of strings, and the order of the translations is unfortunately not very useful, so I'd suggest initially you skip anything you don't recognize from one of the main pages.
Try to find and do all the short generic strings first that appear in lots of areas of the site (e.g. tab and column headings) as they will have the most benefit with the least effort.
The Occurrences column lists the places in the source code where the strings appear. This will be of limited use when you're not familiar with the code, but hopefully the filenames will give you hint as to what area of the site the string appears in and strings with lots of occurrences probably should be done before strings with only one occurrence.
There's a suggest link under each textbox which will use Google Translate to provide an initial translation. This may or may not speed things up depending on how good Google's translation is.
Note: Unfortunately, this feature is no longer supported and now returns an error message from Google.
Some strings will contain "printf" style placeholders (%s, %d, %f and so on, highlighted in red), they will be expanded into data from the database and need to appear in the translated string too.
Some have only a %s, some have a keyword in brackets, such as %(file)s. The word in brackets must be in English and not be translated. If there is more than one placeholder, it's ok to swap them around if you need to.
Be careful as the Google Suggest link will mess those up.
Wherever possible I will try to avoid including HTML markup in the strings, but you will find some and it needs to be left in the translated string for the site to work properly.
Generally anything between angle brackets < and > needs to be left alone. Be particularly careful if using the Google Suggest link as it will break the HTML and you'll need to fix it up to match the English original.
Some strings require a different translation depending on the number of items being referred to:
Enter the singular case in the top textbox (0) and the plural case in the bottom textbox (1). For some languages, there may be a third textbox (2), which is usually for special cases such as numbers ending in 1, 2, 3, 4. Some more (technical) information can be found in the GNU gettext documentation.
Translations you've already made may be marked as fuzzy when I change something in the original text. It means that the translation may no longer be accurate and needs to be checked again.
You can also use the fuzzy flag to remind yourself to come back to an entry for some reason.
NOTE: Fuzzy entries will not be displayed on the site and need to be marked "not fuzzy" as soon as possible.
Use the search function to find the things you can see on the screens you use, don't worry about the other strings as much. If you haven't seen them, most users probably won't see them either.
If you can't find a string that appears on the site, let me know as there are some areas of the site that haven't been marked up for translation yet.
You can filter the list to show only untranslated or fuzzy strings by clicking the buttons on the top right of the page.
As I make changes to the site, the translations will need to be updated too. Your existing translated strings get marked as fuzzy if I change the original English version.
Please contact me if you have any questions at all, I want to make this as easy as possible for you as you're helping me and the other GPSLog Labs users.
If you get a "File is read-only" error then let me know and I'll fix it, this happens sometimes after an update to the site.