28,935
edits
Changes
m
→Other questions on transifex process
Line 8:
Line 8:
−
−==== Linking your new page to the original English page. ====
−To add a link to your newly created page on the original English page, you must edit it using the '''Edit wikicode''' (not the visual editor).
−On the top of the page, search for a block that look like :
−<source>
−<!-- BEGIN origin interlang links -->
−<!-- You can edit this section but do NOT remove these comments
− Links below will be automatically replicated on translated pages by PolyglotBot -->
−[[fr:Documentation_traducteur]]
−[[es:Documentación_traductores]]
−[[zh:翻译文档]]
−<!-- END interlang links -->
−</source>
−Add your new link accordingly.
−If the block does not exist, use the template above : copy it and paste it on top of the original English page (add only your new link).
−Do not add links onto translated pages : they are managed automatically by [[User:PolyglotBot]].
<!-- END interlang links -->
<!-- END interlang links -->
−<seo metak="translation, documentation, translator, localize, localization, i18n, internationalization, language" />
+<seo metak="translation, documentation, translator, localize, localization, i18n, l18n, internationalization, language" />
=[[File:Language.png]] Translate Dolibarr Application into your language=
=[[File:Language.png]] Translate Dolibarr Application into your language=
Line 49:
Line 49:
First install TX Client.
First install TX Client.
With Debian/Ubuntu/Mint:
With Debian/Ubuntu/Mint:
−<source lang="bash">
+<syntaxhighlight lang="bash">
apt-get install python-pip
apt-get install python-pip
pip install transifex-client
pip install transifex-client
−</source>
+</syntaxhighlight>
Then you have to initialize your TX environment. This is done by running '''tx init''' into dolibarr project root directory.
Then you have to initialize your TX environment. This is done by running '''tx init''' into dolibarr project root directory.
−<source lang="bash">
+<syntaxhighlight lang="bash">
cd git/dolibarr
cd git/dolibarr
tx init
tx init
−</source>
+</syntaxhighlight>
Accept to overwrite config file. Keep default value for Transifex instance, then enter your Transifex login and password.
Accept to overwrite config file. Keep default value for Transifex instance, then enter your Transifex login and password.
Line 91:
Line 91:
That is a sample of what the config file contains:
That is a sample of what the config file contains:
−<source lang="ini">
+<syntaxhighlight lang="ini">
[main]
[main]
host = https://www.transifex.com
host = https://www.transifex.com
Line 101:
Line 101:
source_lang = en_US
source_lang = en_US
type = MOZILLAPROPERTIES
type = MOZILLAPROPERTIES
−</source>
+</syntaxhighlight>
Here is an explanation of the sections and options used in the config file:
Here is an explanation of the sections and options used in the config file:
Line 157:
Line 157:
To pull translation files, you can use:
To pull translation files, you can use:
−<source lang="bash">
+<syntaxhighlight lang="bash">
tx -d pull -l it_IT # Get italian language only
tx -d pull -l it_IT # Get italian language only
tx -d pull -a # Get all languages
tx -d pull -a # Get all languages
−</source>
+</syntaxhighlight>
To push source files, just type:
To push source files, just type:
−<source lang="bash">
+<syntaxhighlight lang="bash">
tx -d push -t -l it_IT [-r dolibarr.file] # To push only a specific translation file
tx -d push -t -l it_IT [-r dolibarr.file] # To push only a specific translation file
tx -d push -s # To push source file
tx -d push -s # To push source file
−</source>
+</syntaxhighlight>
===Other questions on transifex process===
===Other questions on transifex process===
This is short questions and answers you may also ask about transifex translation process:
This is short questions and answers you may also ask about transifex translation process:
−1) Is the sync on a regular time interval?
+1) Is the sync done on a regular time interval?
No. It is done where there is enough translation submitted. It is also done on a beta branch just before creating the final release package.
No. It is done where there is enough translation submitted. It is also done on a beta branch just before creating the final release package.
2) Are all the translations synced to git or only the reviewed translations? Do I need to review before sync is done?
+2) Are all the translations synced to git or only the reviewed translations ? Do I need to review before sync is done?
When a Sync is done, transifex files overwrites files into git, but only if there is at least on record modified for the file.
When a Sync is done, transifex files overwrites files into git, but only if there is at least on record modified for the file.
−You don't have to make a review before sync is done. Making review is above all to know which lines were manually reviewed and which one was initially translated using a robot.
+You don't have to make a review before sync is done. Making review is above all to know which lines were manually reviewed and which one was initially translated using a robot. The sync always take the last translated version, even if the new translation was not reviewed.
3) In which Dolibarr releases will translations be available? Are transifex translations also synced to maintenance releases?
+3) In which Dolibarr releases will translations be available? Are Transifex translations also synced to maintenance releases?
Sync is always done on develop and/or beta.
Sync is always done on develop and/or beta.
−So transifex changes appear in all version whose branch is created after the transifex change (a sync is always done before creating a new branch). Once a branch is created, the new changes into transifex will be available only for the next branch. The reason for this is that transifex is not able to manage branch/versions (not yet).
+So Transifex changes appear in all versions whose branch is created after the Transifex change (a sync is always done before creating a new branch). Once a branch is created, the new changes into Transifex will be available only for the next branch. The reason for this is that we do not manage branch/versions on Transifex (not yet).
==Manual Translation (not recommended)==
==Manual Translation (not recommended)==
Line 192:
Line 192:
These files have the format of key/value pairs in each line like the followings:
These files have the format of key/value pairs in each line like the followings:
−<source lang="ini">
+<syntaxhighlight lang="ini">
Code1 = translate phrase 1
Code1 = translate phrase 1
Code2 = translate phrase 2
Code2 = translate phrase 2
...
...
Coden = translate phrase n
Coden = translate phrase n
−</source>
+</syntaxhighlight>
Translate the phrases (the value portion of the key/value pairs) on the right side of the "=" as seen above, the code (the key portion) on the left side of "=" should remain unchanged. It is possible to translate the files one by one, without bringing them all at once. If a file has not been translated into the new language, Dolibarr uses English.
Translate the phrases (the value portion of the key/value pairs) on the right side of the "=" as seen above, the code (the key portion) on the left side of "=" should remain unchanged. It is possible to translate the files one by one, without bringing them all at once. If a file has not been translated into the new language, Dolibarr uses English.
Line 203:
Line 203:
To have a localised (translated) string into the PHP code, all you have to do is load the language file and use the method to get the translated value, like this:
To have a localised (translated) string into the PHP code, all you have to do is load the language file and use the method to get the translated value, like this:
−<source lang="php">
+<syntaxhighlight lang="php">
$langs->load("myfile"); // or use $langs->load("myfile@mymodule") if myfile.lang is inside directory htdocs/mymodule/langs/xx_XX
$langs->load("myfile"); // or use $langs->load("myfile@mymodule") if myfile.lang is inside directory htdocs/mymodule/langs/xx_XX
print $langs->trans("CodeX")
print $langs->trans("CodeX")
−</source>
+</syntaxhighlight>
An entry type;
An entry type;
−<source lang="ini">
+<syntaxhighlight lang="ini">
CodeX = phrase X
CodeX = phrase X
−</source>
+</syntaxhighlight>
must be present or added to the myfile.lang file.
must be present or added to the myfile.lang file.
Line 226:
Line 226:
To make or update all files of a language code, just run the script:
To make or update all files of a language code, just run the script:
−<source lang="bash">
+<syntaxhighlight lang="bash">
php autotranslator.php lang_code_source lang_code_target GOOGLEAPIKEY
php autotranslator.php lang_code_source lang_code_target GOOGLEAPIKEY
−</source>
+</syntaxhighlight>
For example :
For example :
−<source lang="bash">
+<syntaxhighlight lang="bash">
php autotranslator.php en_US pt_PT GOOGLEAPIKEY
php autotranslator.php en_US pt_PT GOOGLEAPIKEY
−</source>
+</syntaxhighlight>
to translate into Portuguese (pt_PT) using English (en_US) files.
to translate into Portuguese (pt_PT) using English (en_US) files.
Line 262:
Line 262:
<br />
<br />
−=== How to translate an existing page ? ===
+===How to translate an existing page ?===
−==== Create a new page for the translated version. ====
+====Create a new page for the translated version.====
Start by creating a new page for the translated version. To do this, you can access an non existant URL : for example [[Translator documentation|<code>https://wiki.dolibarr.org/index.php/Ma_nouvelle_page_en_français</code>]]
Start by creating a new page for the translated version. To do this, you can access an non existant URL : for example [[Translator documentation|<code>https://wiki.dolibarr.org/index.php/Ma_nouvelle_page_en_français</code>]]
The chosen title for the translated version of the page should be the translation of the title of the original English page.
The chosen title for the translated version of the page should be the translation of the title of the original English page.
−