- This page describes the process of translating CATS tests and user interface to a new language. Since the process is quite different for the tests (the questions and answers) and the user interface (all those menues and other things) they are handled in two different chapters.
The status of translations is recorded at the https://bugs.cacert.org. Project is "CATS.cacert.org" and use the filter "CATS translations". Consider creating an account on the bugtracker, so you may add comments there yourself.
User Interface Translation
- This is the easier job of both, since the user interface contains fewer texts, and the texts are of a more standard type of language as compared to the tests.
CATS uses one file for each language to get its user interface texts. You can see what files are already present in the CATS repository at GitHub. If you want to start translation to a new language just download english.php, rename it to your language and start translating the texts.
- To continue an already started translation or to fix bugs get the corresponding file, note the revision number shown at the top and start editing.
If you think you're done, send a mail to the Education mailing list and ask how you can get the translation file included in the repository and activated on the testsystem1. Alternatively you may create a GitHub pull request in the GitHub repository, if you know how to work with GitHub.
- Every translation has to be reviewed by two other persons. They have to assure that the translation is OK, that is, it is not misleading or inapropriate. Of course suggestions for improvements should be considered.
- Once the review is complete the new language file will be installed and activated on the production system.
To translate a test you first of all have to create an account on the CATS Testsystem, which is currently at https://cats.test.cacert.org:14843/. Log in with one of your client certificates and write a mail to the Education mailing list including your certificate's serial number. The Education Officer (EdO) will then give you additional access so you can edit existing tests.
- To add a new language you'll have to ask EdO to create a new test for your language. It will be initialized to the english version and you can now start to translate using the admin interface of CATS.
When you've finished, EdO once again has to step in. S/he'll create some HTML file of your translation which can be used for reviewing2, then two reviewers have to be found.
Since the tests are quite more sensitive, as compared to the user interface, at least you or one of the reviewers have to be a CAcert Assurer and give a "reliable statement" that the translation corresponds to the english test to the best of his/her knowledge. The most simple way to give such a reliable statement is to send an S/MIME signed mail stating the facts3 to the mailing list firstname.lastname@example.org.
- Of course reviews of non-Assurers are also very welcome, just one of the involved persons has to be an Assurer. You may use the same procedure as an Assurer (just don't state that you are an Assurer!), but a note in the bugtracker will also suffice.
- After review is finished the new test can be installed on the production system.
We are still looking for a simpler process, especially for the reviews, so this may change in the future. Hopefully in the near future!
- Software - Data upload to main database - Database content
see Systems - CATS
Currently the Education mailing list allows only very small attachments, so transferring the file in a list message may not work. (1)
The wording of the reliable statement should be something like "I am a CAcert Assurer, I reviewed the french/russian/... CATS test from <the source web address> at <date of the download/review> and assure that it corresponds to the english version from <source web address of the english version>. This is a reliable statement." (3)
Inputs & Thoughts
Text / Your Statements, thoughts and e-mail snippets, Please