| 1 |
Systemtap Internationalization: |
| 2 |
|
| 3 |
The internationalization data will not be generated by default unless systemtap |
| 4 |
is configured with maintainer-mode. However, one can manually regenerate all |
| 5 |
files, including the source-filename-list po/POTFILES.in by executing |
| 6 |
'make update-po' from the top-level source directory. |
| 7 |
|
| 8 |
In order to generate a specific language, run the command: |
| 9 |
'make -C po language.gmo' where 'language' is the language you would like to |
| 10 |
have generated. |
| 11 |
|
| 12 |
Systemtap has a translation page located at |
| 13 |
http://www.transifex.net/projects/p/systemtap/ which is automatically updated |
| 14 |
to host the most up-to-date pot files. |
| 15 |
|
| 16 |
To begin a new translation of systemtap, simply copy the systemtap.pot file |
| 17 |
to a new language.po file, fill in: |
| 18 |
- PO-Revision-Date |
| 19 |
- Last-Translator |
| 20 |
- Language-Team |
| 21 |
- CHARSET |
| 22 |
- Plural-Forms |
| 23 |
- Strings to Translate |
| 24 |
|
| 25 |
If you're unsure of the specific plural forms of the language, they can be |
| 26 |
found in the gnu gettext online manual located at |
| 27 |
http://www.gnu.org/software/gettext/manual/gettext.html#Plural-forms |
| 28 |
Once all translatable strings have been completed, generate the necessary |
| 29 |
files by running 'make -C po language.gmo' where 'language' is the |
| 30 |
language you would like to generate from the po file. |
| 31 |
|
| 32 |
If there are any ambiguities or clarifications needed from the source, the |
| 33 |
comment code '//TRANSLATORS: ' one line above a gettext string will be passed |
| 34 |
through to the systemtap.pot file for translators to view. Feel free to ask |
| 35 |
for any further clarifications either on the systemtap mailing list or on |
| 36 |
the oftc.net #systemtap IRC channel. |
| 37 |
|
| 38 |
In the most general case, adding a translatable string can be done by simply |
| 39 |
wrapping the string with the _() macro, ie. _("string to translate here"). |
| 40 |
The macro _F() has been used for autosprintf, _N() for ngettext, and _NF() |
| 41 |
for a combination of autosprintf and ngettext. For more information on how to |
| 42 |
use gnu gettext please consult the online manual at |
| 43 |
http://www.gnu.org/software/gettext/ |