Dutch

Communication Platforms

The most important thing to do is to stay connected with fellow translators and reviewers. The Localization Lab Mattermost is hosted on the International Freedom Festival domain and is subject to their Code of Conduct. Be sure to read through the Code of Conduct and then contact us and we will send you a link to sign up for the channel. You can also comment on strings in Transifex, but please tag a reviewer for your language, because Transifex comments can otherwise easily go unnoticed.

Dutch style guide for Signal Messenger

This Style guide is a result of reviewers communicating about inconsistencies and solutions. As the result of previous discussions we have come up with the following style guide for Dutch localization of Signal messenger. The style may deviate from other Localization Lab project, because no two projects are the same.

• Any translator or reviewer should be using the Signal Beta app, so you can see the new strings as soon as possible and know where they occur in the app.

We do not welcome translators who are not using the Signal app. If you don't know the context, you can't write good localizations.

• What we are doing is localization, not just translation. That means translations do not have to match precisely to the same words in English; sometimes the cultural differences are a reason to write a different text in Dutch.
• For quotation marks we use opening and closing quotation marks as such: “ ” . Note that these are not the same quotation marks we see in the English text strings. There is no key for these on your keyboard, so you might want to learn a shortcut to type them, or you can copy paste them wherever you need them.
• Follow proper Dutch spelling, for example don't write "log bestand" but instead write "logbestand".
• Dutch people like clear no bullshit language. Avoid figure of speech, try to be direct and factual.
• Try to write strings in such a way that your grandfather and grandmother will also understand Signal, prefer Dutch words over English terminology. If a word is unfamiliar to someone, it helps if it's a Dutch word and sound similar to other Dutch words which they do know the meaning of.
• On preference / setting descriptions: If the sentence contains any interpunction, end the sentence with a period. If the description does not contain any interpuction, don't end the sentence with a period.
• About the structure of sentences: we highly recommend you read this lesson about word order in Dutch language, even if Dutch is your first language. MAny Duthc people also get it wrong. [1] Note that it's not just one page, there is a next page button on the bottom right and there are quite a lot of examples of different cases on that site.
• About "je, jij, jou, jouw, u and uw" because Signal is a messenger you use day to day we think it's most fitting to use informal pronouns, so we don't use "u and uw". We use "je" wherever there is no ambiguity / possible confusion about the meaning of the text. We use "jij, jou or jouw" if the string does not occur in a sentence or if there is any ambiguity.
• Use the ellipsis symbol instead of three lose dots: … . If it is breaking of a word use no whitspace: Ben je me nu al verge… If it breaks of a sentence use a whitespace between the last word and the ellipsis: Ik heb het potje vet al op tafel …

Tips for consistency

• Use the suggestions tab in Transifex to see if a similar string has already been translated before
• Use the glossary tab to see if a particular word has a suggestion
• Always read the comments on the string
• Look at the string key, to see what it is called in the code
• If you want, you could take a look at the source code in GitHub. Just reading the titles of recent commits could already give you a helpful clue.
• If you are not sure about the context, ask other translators in the comments, leave the string untranslated or give it your best guess and come back later to review it.

How to review

• If there is a Beta version of the website or app you are translating, you should probably be using it so you have early knowledge of where the string will occur , in what context, and how much space is available
• See if the string provides clear information, and that users don't have to guess about its meaning.
• Make sure all the interpunction is accurate, the capitalization is accurate, there are no double whitespaces, and no missing whitespaces
• Make sure all symbols and next line match with the original string
• Make sure the vocabulary matches that of other strings
• Make sure the structure of the sentence matches that of other strings
• Make sure the exact same phrase, with the same vocabulary and same sentence structure is used across various projects of the same organization, for example in the case of Signal messenger, across the iOS app, Desktop app, Android app, Support Center, Website and App store.
• Make sure the string fits in the available space. However if you feel the available space is insufficient, do not come up with some unreadable string, but instead contact the developer about creating additional space for translated strings.

Dutch vs Flemish

If a resource for nl_BE exists, Flemish style and vocabulary can be used for that project. If it does not, nl and nl_NL will still follow Dutch standard language (Nederlandse standaardtaal). It is not possible to make a mix out of the two which satisfies both language regions. Flemish translators can contact a project maintainer and ask to add a nl_BE project.

Language Resources

Please use the following resources to guide the style, tone and terminology you use across Localization Lab supported projects. Note: These resources are not are not final. If you disagree with terminology or grammar choices, please escalate the issue to the Localization Lab team for further discussion with other Dutch language team contributors.

• https://www.dutchgrammar.com/en/?n=WordOrder.00 Over woordvolgorde in zinnen, klik steeds rechts onderin op volgende pagina
• Taaladvies
• Taalnet
• OnzeTaal

If you search for other websites, avoid following style advise of tech companies who make up their own version of Dutch language based on marketing rather than proper Dutch. Also avoid other wiki's which were often written by opinionated people. That doesn't mean you can't read them and learn from them, but take it with a grain of salt.

We prefer to use the glossary in Transifex. Localization lab also has a general Glossary, although we don't really use it much at this time: Dutch Unified Localization Lab Glossary

Add comments, edits and suggest new entries by using the "Comment" feature in the spreadsheet.