Project

General

Profile

Translating » History » Version 30

Dominic Cleal, 04/25/2013 04:02 AM
formatting

1 6 Lukas Zapletal
h1. Translating for contributors
2 1 Lukas Zapletal
3 7 Lukas Zapletal
h2. General tips
4
5
It is important not to change punctuation and whitespace. For example if the English string is "blah." it must be translated as "xyz." with the dot at the end. The same for an extra space - e.g. "blah " must be "xyz ". Although we try to eliminate all the extra spaces, there are rare cases where we need them. There is a checker (pofilter) which is executed regularly by developers to catch and fix all these types of mistakes. 
6
7
There are model names in the translation strings, you can get the full list here: https://github.com/lzap/foreman/blob/develop/locale/model_attributes.rb
8
9
These model names are in two formats: "Model name" (name of the database table) and "Modelname|Column name" for column name. Here are few examples how to translate them:
10
11
 _('Compute resource') -> "Compute Resource"
12
13
 _('ComputeResource|Description') -> "Description"
14
15
Several models have prefixes in the form something/ or Something:: - you can ignore these. Example:
16
17
 _('Audited/adapters/active record/audit') -> "Audit"
18
19
 _('Audited::Adapters::ActiveRecord::Audit|Associated name') -> "Associated Name"
20
21 6 Lukas Zapletal
h2. Using Transifex
22
23
Go to https://www.transifex.com/projects/p/foreman and register/login. Then you can use the Transifex interface to do all translations. The project on Transifex automatically updates when we add new strings into git. Foreman team regularly downloads new translations to the develop branch in git as well, therefore there is no action needed when you finish with translations. It will be pulled eventually (e.g. before the next release).
24
25
Read the tips bellow if you want to start translating now.
26 1 Lukas Zapletal
27 2 Lukas Zapletal
h2. Manually
28
29
If you prefer, you can edit PO files directly using your preferred editor. Please make sure the encoding of the files is UTF-8. It is also recommended to test your translations before submitting a Pull Request on the github using either:
30
31 28 Lukas Zapletal
  foreman# rake locale:pack
32 1 Lukas Zapletal
33 2 Lukas Zapletal
or
34 1 Lukas Zapletal
35 7 Lukas Zapletal
  foreman# make -C locale check all-mo
36 2 Lukas Zapletal
37 29 Lukas Zapletal
Note that locale:pack is an alias for gettext:pack which is only avaiable in the development environment.
38
39 1 Lukas Zapletal
The above command should not print any error message. Also you should start Foreman UI and see if your translations do fit (sometimes longer strings can wrap or even break the UI). If you start Foreman in the production mode, you need to do one of the above commands every time you change your translation. In the development mode, you only need to restart Foreman to see the changes.
40
41
More info about contributing your translation directly is on our [[Contribute]] wiki page. 
42
43 6 Lukas Zapletal
h1. Translating for developers
44 1 Lukas Zapletal
45 15 Lukas Zapletal
h2. Extracting strings
46
47
There are several rules to follow when marking strings for translations with _("") and similar functions:
48
49 30 Dominic Cleal
 * To translate a string use @_("My string")@
50
 * To translate string with a parameter use @_("String with param: %25s") %25 param@
51
 * To translate string with more than one parameters do not use @_("Params: %25s and %25s") %25 [param1, param2]@ which is translator-unfriendly
52
 * Therefore for more than one parameters use @_("Params: %25{a} and %25{b}") %25 {:a => foo, :b => bar}@
53
 * To mark something for translation (but not translate) use @N_("String")@
54
 * To use plural form use @n_("One", "Two", number)@ - note this function always accepts three parameters as the base language is usually English but translators are able to define as many plural forms as they need.
55
 * Plural forms are usually used with one parameter, do not forget to add trailing parameter to it: @n_("%25s minute", "%25s minutes", @param) %25 @param@
56
57
h3. Models and columns
58
59
 * To render name from model use @s_("Modelname|Fieldname")@ - check @./locale/model_attributes.rb@ for all models/fields which are accepted.
60
 * All our form helpers have been enriched and understand model and column names - if the field is in the model_attribute.rb (above), it does not need to be translated explicitly (e.g. text_f f, :name is enough and will be translated to "Modelname|Name")
61
62
h3. Helping translators
63
64 1 Lukas Zapletal
 * Do not break strings with newlines because then the strings have many whitespace and it looks confusing for translators like "blah    \\n     blah". If you must separate string on several lines, you can use HEREDOC or you can contatenate strings like "line1" + "line2" because Ruby Gettext detects them both.
65 30 Dominic Cleal
 * If you want to leave a note to the translator, just drop a comment before the string in the format of @# TRANSLATORS: your comment here@
66 15 Lukas Zapletal
 * Note that all HEREDOC strings are automatically extracted, when adding API documentation descriptions via HEREDOC, leave a message to translators not to translate these (API documentation will not be translated at the moment).
67 30 Dominic Cleal
68
h3. Storing strings
69
70 25 Lukas Zapletal
 * Strings get extracted into ./locale/foreman.pot file, model and column names are in ./locale/model_attributes.rb
71 15 Lukas Zapletal
 * Additional Rails strings are in ./config/locale - there is a script to update those from Rails I18N git (branch 3-x).
72
 * For more info go here: http://www.yotabanana.com/hiki/ruby-gettext-howto.html
73
74
From time to time it is good to extract strings and update translations with incoming strings, so translators are able to work on them. We usually do this before releases, but it is good idea to do this on a weekly/monthly basis. For string extractions, please *do not* use rake gettext:find but use
75
76
  foreman# rake locale:find
77
78 21 Lukas Zapletal
because it also extracts model names and columns and filters them plus it adds some notes to translators (see locale:find_model rake task). Although locale:find does some checks for malformed strings, it is good idea to run additional pofilter check which is able to find many mistakes like trailing whitespace and others:
79
80
  foreman# make -C locale check -j4
81
  foreman# make -C locale clean
82 15 Lukas Zapletal
83
h2. Generating gettext translate tables
84
85
For production environment, you need to compile PO files into binary translate tables (MO files). This is *not needed* for development or test environments as in these modes Foreman reads PO files directly.
86
87
To generate gettext MO files, you can do either
88
89
  foreman# rake gettext:pack
90
91
or
92
93
  foreman# make -C locale
94
95
Both tools generate the same result, the latter is a bit faster and allows additional checks (see locale/Makefile targets). If you install from distribution packages, you do not need to run this because everything has been pre-compiled already.
96
97 8 Lukas Zapletal
h2. Adding new language
98 6 Lukas Zapletal
99 2 Lukas Zapletal
Adding new language into Foreman is easy. You need to take two steps - first of all create new gettext PO file as a copy from POT and edit the header (at least set plural configuration):
100 12 Lukas Zapletal
101 3 Lukas Zapletal
  # cp locale/foreman.pot locale/xx/foreman.po
102 6 Lukas Zapletal
  # vim locale/xx/foreman.po
103
104 12 Lukas Zapletal
Then pull Rails translation strings from upstream 3-x branch:
105
106 26 Lukas Zapletal
  # touch config/locale/xx.yml
107
  # script/update-rails-locales.sh
108 12 Lukas Zapletal
109
And add the language to Transifex and Zanata using their web interfaces.
110 2 Lukas Zapletal
111 6 Lukas Zapletal
h2. How to pull translations
112 1 Lukas Zapletal
113 4 Lukas Zapletal
To get updated translations from Transifex you will need account there (https://www.transifex.com) and the tx cli tool.
114
115
On Fedora:
116
117
  # yum -y install transifex-client gettext make intltool
118
119
On Debian:
120
121
  # apt-get install transifex-client gettext make intltool-debian
122
123
Then configure your account:
124
125
  $ cat ~/.transifexrc
126
  [https://www.transifex.net]
127
  hostname = https://www.transifex.net
128
  username = <your_username>
129
  password = <your_password>
130
  token = <should be empty>
131
132
And then prepare new topic branch (because the following command will make new commits to your git repo):
133
134
  git checkout -b update-translations
135
136
Finally do the translation pull
137
138
  make -C locale tx-update
139
140
And then you can push changes.
141
142
  git push ...
143 9 Lukas Zapletal
144
h2. Not translated
145
146
Some parts are (yet) not translated. These include:
147
148 27 Dominic Cleal
 * all JavaScript resources (components etc), #2420
149 9 Lukas Zapletal
 * permission names
150
 * predefined role names
151
 * predefined user names
152 20 Dominic Cleal
 * names of settings?
153 11 Dominic Cleal
 * default bookmark names (active, disabled etc)
154
 * INTERNAL auth method
155 13 Lukas Zapletal
 * audit entries
156 14 Dominic Cleal
 * will_paginate (Dom working on this)
157 16 Dominic Cleal
 * reorder the More submenus alphabetically?
158 18 Dominic Cleal
 * predefined install media names ("mirror")
159
 * predefined partition table names
160 19 Dominic Cleal
 * template types/kinds
161 1 Lukas Zapletal
 * predefined template names
162 20 Dominic Cleal
 * "Clear" tooltip in scoped_search
163 22 Dominic Cleal
 * any external assert gems, e.g. SPICE HTML 5 console, noVNC?
164 23 Dominic Cleal
 * Puppet log messages, log levels
165
 * column names used in scoped_search
166 10 Lukas Zapletal
167
Some items from the list above will never be translated due to technical reasons or to avoid confusion.