Updated Translating tracks (textile)

Reinier Balt 2013-05-27 06:36:24 -07:00
parent 44b645e67c
commit 2ec2ee2cc2

@ -1,6 +1,6 @@
h1. Translating Tracks
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, does not require you to be a developer and can be done from your webbrowser.
Tracks <=2.1 uses different built-in mechanism for creating translations than Tracks 2.2.
@ -15,7 +15,8 @@ In general the steps are:
** 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).
* Make sure the database is current: @bundle exec rake db:migrate@
** 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!
** this will require you to configure a database in @config/databases.yml@ for the development environment. To be safe, do not use your production database, but use a copy of your database or make backups!
** Furthermore for languages that require special character sets like hebrew, configure the correct character set both in @config/database.yml@ and for your database (i.e. in @/etc/my.cfg@ for mysql). Mysql uses @latin1@ by default and that won't work for hebrew.
* launch the built-in Tracks server in development mode:
** for Tracks 2.2: @bundle exec rails s@
** for Tracks 2.1: @script/server -e development@
@ -49,6 +50,7 @@ h2. Help and troubleshooting
** http://localhost:3000?locale=nl will switch to dutch.
** if your page gives errors, first check with @locale=en@ if the error is caused by your language changes. Remember that auto translate can mess up parameters, sometimes putting a space between @$@ and @{param}@ and sometimes translating the name of the parameter!
** see the i18n documentation for rails for more technical details http://guides.rubyonrails.org/i18n.html
* if you see a question mark (?) instead of a special language character, there is most likely a wrong encoding setting somewhere. I had @latin1@ for my character set in mysql preventing special characters to be imported correctly by Tolk
h2. Getting your changes into the next release