Andreas/tracks
1
0
Fork 0
mirror of https://github.com/TracksApp/tracks.git synced 2026-02-16 20:28:09 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions

Updated Translating Tracks (textile)

lrbalt 2012-07-18 06:26:10 -07:00
parent 0168b30441
commit 61cdd3c863
1 changed files with 19 additions and 9 deletions
Download patch file Download diff file Expand all files Collapse all files

28
Translating-tracks.textile

@ -1,28 +1,38 @@
h1. Translating Tracks
h2. Overview
Translating Tracks is very easy and can be done from your webbrowser. Translating Tracks into another language is not very difficult and does not require you to be a developer
Translating Tracks into another language is not very difficult and does not require you to be a developer
Tracks <=2.1 uses different built-in mechanism for creating translations than Tracks 2.2.
h2. Overview
In general the steps are:
* get a copy of tracks
** either make a copy of your running tracks (to make sure you always have a working verions)
** or get it from git using @git clone git://github.com/TracksApp/tracks.git@
* create an empty locale file in @/config/locales@, i.e. touch @/path/to/copy/of/tracks/config/locales/XX.yml@
** @XX.yml@ is the locale file for your language where @XX@ is the short name for your country like the following who are allready there: en (english) or de (german) or nl (dutch).
* create a new locale for the language you want to add to Tracks
** for Tracks 2.2, this can be done from the webpage
** for Tracks 2.1, create an empty locale file in @/config/locales@, i.e. @touch /path/to/copy/of/tracks/config/locales/XX.yml@
*** @XX.yml@ is the locale file for your language where @XX@ is the short name for your country like the following who are already there: en (english) or de (german) or nl (dutch).
* run Tracks in development mode: @script/server -e development@
** this will run tracks on localhost on port 3000
** this will require you to configure a database in @config/databases.yml@ for the development environment. To be safe, use a copy of your database or make backups!
** Make sure the database is current: @rake db:migrate@
** access it by pointing your webbrowser to @http://localhost:3000@
* go to your preferences page and select your language as default
** all pages should look wrong or fail. No worry!
* point your browser to @http://localhost:3000/translate@
** this is the translate plugin that will show you all strings that need to be translated
** all pages should look wrong or fail or just display everything in English (fallback option). No worry!
* For Tracks 2.2, point your browser to @http://localhost:3000/tolk@
** Select the language you want to work on or create a new one
** When you are done, either submit the new language file to Assembla or create a pull request
*** using @rake tolk:dump_all@ will write all changes to the locale files in @/path/to/tracks/config/locale@
*** Or: download the locale file: @http://localhost:3000/tolk/locales/XX.yml@ where @XX@ is the name of your locale (for example nl or de or cz)
* For Tracks 2.1, point your browser to @http://localhost:3000/translate@
** this is the translate plug-in that will show you all strings that need to be translated
** set the filter right: set your language by choosing "Translate from EN to XX" with XX being your language and choose Display
** You can select "untranslated" to filter on untranslated strings
* The "auto translage" link uses Google to translate the string. Very handy. Be aware though that it will translate parameters like @%{count}@ too. Change this back or Tracks will fail
* When you save the translations, it will write it to @XX.yml@ in your @config/locales@ directory
** The "auto translage" link uses Google to translate the string. Very handy. Be aware though that it will translate parameters like @%{count}@ too. Change this back or Tracks will fail
** When you save the translations, it will write it to @XX.yml@ in your @config/locales@ directory
Some pages need to be translated manually: