Best Practices for Translation

1. Take a look at the glossary

Before you start translating documents, please make sure the glossary is translated first, and find the correct terms in your language. The glossary is a dictionary for important words that should have a consistent translation throughout all the S3 resources. We added all the pattern names, and the names of important concepts like “pattern”, “driver”, “domain”, “value” etc. Contact us if you have any questions about terms in the glossary, and we will try to help as best we can.

2. Be consistent with terms from the glossary

When translating documents, please make sure to provide an identical translation for each occurrence of a term from the glossary. Be especially careful when translating value and values, as they might have two different translations in your language.

3. Use what’s there already

If a phrase is already in the translation memory, consider using that instead of creating a different translation.

4. If you’re stuck…

If something seems hard to translate, sometimes it’s a good idea to skip that text until later, progressing through the document will give you a clearer picture, and it’s easy to find and fill in the missing translations later.

5. Stick to the text…

Please DO NOT translate text inside curly brackets (e.g. {{policy-life-cycle.md}}). these are file names and need to remain as they are.

Also, please DO NOT translate anything marked as “hidden texts” (like “inline, fit”), this is used for positioning and sizing images.


Take a look at our brief tutorial to assist you with your first steps in Crowdin, or go back to the Translation Project page.