... | ... | @@ -153,24 +153,17 @@ mv po/pt/civicrm.mo ../../svn/l10n/pt_PT |
|
|
# (we can’t do this for the above four, as pt would overwrite pt_BR rather than pt_PT):
|
|
|
for i in po/??/civicrm.mo; do mv $i ../../svn/l10n/`echo $i | cut -d/ -f2`*; done
|
|
|
]]></script>
|
|
|
</div></div><p>After the above the MO files should be committed to the Subversion repository.</p><h1 id="PushingnewstringstoTransifex-Syncingtranslations">Syncing translations</h1><p>When a string is not translated (or translated with a ‘fuzzy’ – i.e., tentative – flag set) it doesn’t get compiled to the MO file and the original English string is used instead. For some language pairs it makes sense to use the other language’s translation in such case – with the idea being that for, e.g., Canadian French is better to fall back to French rather than English.</p><p>This situation is handed by the <code>sync-translated.sh</code> script, which – given two locales – copies over the strings translated in one but not translated in the other (both ways). Note that there are language pairs (like de and de_CH, i.e. German and Swiss German) which explicitly asked to not do the syncing for them. We currently sync en_CA with en_GB, es with es_MX and fr with fr_CA:</p><div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
|
|
|
<script type="syntaxhighlighter" class="theme: Confluence; brush: java; gutter: false"><![CDATA[bin/sync-translated.sh en_CA en_GB
|
|
|
bin/sync-translated.sh es es_MX
|
|
|
bin/sync-translated.sh fr fr_CA
|
|
|
git add po
|
|
|
git commit -m 'sync en_CA with en_GB, es with es_MX and fr with fr_CA'
|
|
|
git push
|
|
|
]]></script>
|
|
|
</div></div><p>Such translations need also to be pushed to Transifex:</p><div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
|
|
|
<script type="syntaxhighlighter" class="theme: Confluence; brush: java; gutter: false"><![CDATA[for lang in en_CA en_GB es es_MX fr fr_CA; do tx push -t -l $lang; done
|
|
|
]]></script>
|
|
|
</div></div><h1 id="PushingnewstringstoTransifex-CaringfortheTransifexcommunity">Caring for the Transifex community</h1><p>Currently our policy is that the first person willing to translate CiviCRM into a given language creates a Transifex team and becomes the team coordinator; future translators need to be approved by the coordinator.</p><p>This makes it possible to guard from spammers and keep a given localisation coherent (e.g. with regards to how different terms, like ‘househould’, should be translated), but it also means that new translators who are not quickly accepted (or denied) by the team coordinator are in limbo and wait for the decision.</p><p>Thus we should periodically check whether new translators for existing teams are handled pronto and are not discouraged/blocked when the team coordinator is inactive (or on a leave, etc.); we should poke the coordinators, elect additional ones or, in the worst cases, accept the new translators ourselves.</p><p>http://help.transifex.net/features/client/index.html#auto-local</p>
|
|
|
|
|
|
</div>
|
|
|
</td>
|
|
|
</tr>
|
|
|
</table>
|
|
|
</div></div><p>After the above the MO files should be committed to the Subversion repository.</p>
|
|
|
|
|
|
# Caring for the Transifex community
|
|
|
|
|
|
Currently our policy is that the first person willing to translate CiviCRM into a given language creates a Transifex team and becomes the team coordinator; future translators need to be approved by the coordinator.
|
|
|
|
|
|
This makes it possible to guard from spammers and keep a given localisation coherent (e.g. with regards to how different terms, like ‘househould’, should be translated), but it also means that new translators who are not quickly accepted (or denied) by the team coordinator are in limbo and wait for the decision.
|
|
|
|
|
|
Thus we should periodically check whether new translators for existing teams are handled pronto and are not discouraged/blocked when the team coordinator is inactive (or on a leave, etc.); we should poke the coordinators, elect additional ones or, in the worst cases, accept the new translators ourselves.
|
|
|
|
|
|
http://help.transifex.net/features/client/index.html#auto-local
|
|
|
|
|
|
# Historical notes
|
|
|
|
... | ... | |