Customize Translation Checks for Your Files

Customize Translation Checks for Your Files
Table of contents
November 15, 2013
3 min read

Transifexians, we have good news for you! From now on, you’re going to have even more power in our editor to manage your translations the way you wish. Now, you are able to choose the validation checks that will be run against your translations, such as whether a URL is entered correctly by the translators. So, let me introduce you to our new feature.

How did it work?

We have been doing that for you by setting what checks are necessary for the new translations. These checks can be errors or warnings. When an error check for a translation fails, then the translation is rejected, but when a warning check fails, the translation is saved. In both cases translators see an appropriate message.

But isn’t it better for oneself to decide on the rules that will have an impact on his life? We believe so and that’s why we now let you decide in which occasions your translators will be just warned or not be able to save a translation at all, if it doesn’t match the rules you set.

To be more precise, each organization can now set its own translation checks for each type of file that it uses under the Manage Tab of its dashboard. Take a look below:


Example case is the following:

Let’s say I have PO and YAML files: I can choose what checks  I want to be run for each file type whenever a translator translates my content.

So for the .po file, initially I see the default checks for errors, warnings along with the disabled ones. Now I can easily change them and switch a warning check to be an error check, and vice versa. I can even turn one check off. So if I switch a check to “Error” then the  translation that does not pass the corresponding check will  be rejected but if I switch it to “Warning” then the translation will be accepted and saved. If I turn off a check then it will have no effect at all.

Let’s try it live.

Case 1: I set the validation check “Email addresses found on source string are preserved in the translation” as  Warning.


Then, if I try to translate a string that has an email and I don’t preserve the email in the translation, I get a warning but the translation is saved.


Case 2: I set the same validation check  as Error.

Then, if I try to do the same in the editor, I get an error mesage and the translation is rejected.


And that’s all!

Isn’t it cool? And it’ s available for all. Let me know your opinion!

We’d also love to have feedback on our validation checks. Which ones are the most valuable in general, or the most valuable for a specific file type and so on. We could also have suggestions for new ones!

Happy localization people!


Subscribe to
Becoming Global

Get localization news and best practices delivered to your inbox each month.

FacebookgithubGoogle+Fill 88Twitter