Basics | |
|
How to create a new translation resource for a new Tiki release | |
For every major Tiki release a resource should be added (eg: https://www.transifex.com/tiki/tiki-translation/tiki-15/), for minor releases (eg: Tiki 15.1) there is no need for this 1. Open "Resources" screen for the project
Resource settings "SLUG" is a short, unique name for the resource. Please follow naming convention: tiki-majorreleasenumber (eg: tiki-15).
"YOUR TRANSLATORS CAN TRANSLATE RESOURCE STRINGS": make sure it is checked so that the resource can be translated. "CATEGORIES": optional, you can add eg: "php" and the Tiki release number
|
How to enable automated resource translation from translation memory in a project | |
It is possible to automate the translation among resources inside a Transifex project, automated update of source strings can ensure that translation is done automatically. Currently it is turned ON Automated translation is currently turned on for the project (it is a project level setting, can not be set for each resource). Transifex is being tested for the Tiki 15 release, if the automation has no side-effects, it stays on, otherwise it will be switched off.
Automated translation You can configure the Translation Memory of a project to automatically populate translations for source strings that have 100% similarity match with already translated source strings in another resource. If enabled, this action is triggered on every time you upload a resource, no matter if this is done through the UI or by using the Transifex client. That way, the translators' workload is reduced and translations that should be consistent across your resources are guaranteed to be identical."
Read more here: http://docs.transifex.com/features/tm/
Read more about how it works (really!) There are some trade-offs coming with automation, see here: http://docs.transifex.com/tutorials/content/#transifex-tips |