Localization Lab Wiki - User contributions [en]

Dutch

2021-06-15T12:29:45Z

Meteor0id: Make a start with styling, more to be done later to improve readability of the style guide

Dutch is the first language of about 24 million people, and a second language to another 5 million people, making it one of the 40 most spoken languages in the world. It is an official language in the Netherlands, Suriname and the Belgium. Dutch is closely related to English and German, and because Dutch is not a world language, most people with Dutch as their first language are also proficient in English. Never the less not all who speak Dutch are proficient in English, and localization to Dutch helps create a better understanding of the app / website or whatever resource is being translated.
The Dutch language plays a significant role in it's cultural differences: The Dutch often view themselves as more nuanced and reserved than for example Americans. The language is typically more descriptive and less figurative than English.

__TOC__

==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 [https://internetfreedomfestival.org/ International Freedom Festival] domain and is subject to their [https://www.internetfreedomfestival.org/wiki/index.php/Code_of_Conduct Code of Conduct]. Be sure to read through the [https://www.internetfreedomfestival.org/wiki/index.php/Code_of_Conduct Code of Conduct] and then [mailto:info@localizationlab.org?subject=Mattermost%20Sign-up&body=Please%20send%20me%20a%20link%20to%20sign%20up%20for%20Mattermost. 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==
Ask yourself: "If my 65 year old mother read this (who has a total of 3 apps on her phone and uses only one of them on a weekly basis), would she understand this without anyone's help?". The goal is not to translate words, the goal is to make the text understandable to people who grew up in a different country.

===Signal Messenger===
''This Style guide is a result of reviewers communicating about inconsistencies and solutions to those. 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. We will try to make this style guide easier to read in the future.''

* The most important rule to always keep in question yourself who your audience will be and whether they will fully understand it. Yes, you are doing this work on behave of the Signal developers, but your audience are Signal users. Place yourself in the frame of mind of a Signal user who doesn't really know much about Signal and is trying to understand his options. Don't just translate literary, translate in such a way that it makes sense, is accurate, and is easy to read for the end user.
* 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. 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, meaning different words and/or a different structure of the sentence.

{| class="wikitable"
|+ Example: Don't try to translate literally
|-
! English original !! Avoid !! Instead use
|-
| Signal needs location services enabled to discover and connect with your old Android device. || - || Om je oude Android apparaat te kunnen detecteren en om er verbinding mee te maken is het nodig dat locatiebepaling op je apparaat is ingeschakeld.
|-
| - || Om het in te schakelen, tik op de schuifknop zodat hij blauw wordt. || Tik op de schuifknop zodat hij blauw wordt om meekijkpreventie in te schakelen.
|}

* Avoid referencing earlier mentions with articles, instead write out the full sentence. Example: do not write "Om het in the schakelen" instead write "om meekijkpreventie in te schakelen". Also avoid "deze" "dit" and "die" wherever possible.
* 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 punctuation, end the sentence with a period. If the description does not contain any punctuation, 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 Dutch people also get it wrong. [https://www.dutchgrammar.com/en/?n=WordOrder.00] 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. An example: Don't write "Deze personen kunnen door jou niet direct worden toegevoegd aan de groep." instead write "Deze personen kunnen door jou niet direct aan de groep worden toegevoegd.".
* 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 white space: 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 …
* Make sure the subject is repeated in every new sentence, do not refer back to a previous sentence. We do this to keep texts easy to read and understand. An example: do not write "Turing this on allows you to receive emails. They will contain information about your account." instead write "Turning this on allows you to receive emails. The emails you will receive contain information about your account.".
* Avoid anglicisms, our job is to localize the content so it can be understood by as many people as possible, that includes people who don't understand even the most common of English words.
* For units we follow the Si-standards. That means we translate 20MB as 20 MB with a white space. Kilobytes as kB. Note that Signal does not use KiB, MiB etc, because Signal is following the same units as the Android operating system. The same rule applies to other units such as 10s becoming 10 s. Abbreviations for minutes, months and weeks are not si units but we agreed to translate those as "min", "mnd" and "w". Capitalization matters.
* The text strings for the app store sometimes contain wordplay. If a good wordplay in Dutch can't be found, than rather leave the word joke out and just factually describe the change.
* Use pronoun + "wie" instead of "die" wherever possible. Read [https://taaladvies.net/taal/advies/vraag/1564 Taaladvies about wie/die] about where to use "wie" and where to use "die". This is a style choice we made to make complex sentences easier to comprehend.
* Use "van wie", "bij wie", "op wie" and "voor wie" instead of "waarvan", "waarmee", "waarop" and "waarvoor" wherever possible.
* For texts on buttons in Android and Desktop use the infinitive (infinitief) grammatical mood (werkwoordswijs), do not use the imperative (gebiedende wijs) because we don't want to give the user the impression that he is recommended or required to press the button. It is not imperative you clikc the button, it is merely an option you have. This is the norm in almost all Dutch translations also outside of the Signal project. Only iOS still often uses the imperative, so for iOS we have not yet decided which form we wish to use. Examples: Do use "Aan gesprek deelnemen", "Aan Signal doneren" and "Alice toevoegen". Do not use "Voeg Alice toe" or "Deelnemen aan gesprek" or "Doneren aan Signal".
* Only capitalize the first letter. Unlike English we don't capitalize every word in Dutch.
* Try to stick to Dutch words, even if you see English words being used in other apps: "timer" becomes "tijdspanne", "admin" "beheerder", "checkbox" "selectievakje of aankruisvakje", "updaten" "bijwerken", "icon" "pictogram", "non-profit" "organisatie zonder winstoogmerk", "error" "fout", "database""databank" etc. You can find words like these listed in the Transifex Glossary for the Dutch Signal project.
* Beware of capitalization: use "QR-code" do not use "QR-Code" or "qr-code". "WiFi" is spelled different in Dutch: "wifi" all lowercase and without a dash. You can find words like these listed in the Transifex Glossary for the Dutch Signal project.
* Use [https://onzetaal.nl/taaladvies/signaalwoorden-lijst/ signal words] (words that indicate summation, contradiction etc.) wherever possible.
* Use formal verbs where their is no difference in meaning: use "je kunt" not "je kan". Howerver for "kun je" versus "kan je" there is a minor difference: "kan je" is more proposing while "kun je" is more forcefully suggestive. Therefore we use "kan je" instead of "kun je", and "zal je" instead of "zul je". [https://taalhelden.org/bericht/het-kan-je-kun-je https://taalhelden.org/bericht/het-kan-je-kun-je]
* Don't forget that although in English articles can be omitted, in Dutch it's not an accepted practice to omit the article. For example: "Playback time of audio attachment" should be localized as "Afspeellengte van HET audiobericht".
* Don't use possessive pronounce for things the user isn't possessing: Don't write "Open Signal-Desktop en gebruik de sneltoetsen om je tekstgrootte aan te passen.", instead write "Open Signal-Desktop en gebruik de sneltoetsen om de tekstgrootte aan te passen.". Users don't have font size, Signal has font size.
* We consistently use only the ‘rode werkwoordsvolgorde’, never the ‘groene werkwoordsvolgorde’. This means we never write "... vertrokken is." but instead always write "... is vertrokken.". For more information about verb order: [https://onzetaal.nl/taaladvies/rode-groene-volgorde/ https://onzetaal.nl/taaladvies/rode-groene-volgorde/]
* Do not hesitate to make use of 'old' or 'formal' words or grammer wherever it reduces ambiguity. For example the phrase "Journalist Bergman
Zag tijdens een interview met De Koning deze foto op zijn bureau staan." For most readers it wil be clear that the photo was on the Kings desk, but some may understand it in the litteral sense and understand that the photo was on the desk of journalist Berman. The solution to prevent this ambiguity is to use grammar whoch is perfectly correct, but isn't used often anymore: "Journalist Berman zag tijdens een interview met De Koning deze foto of diens bureau staan." (In case of a female person it would be "dier" instead of "diens". Don't shy away from formal language, avoiding ambiguoty is of a hogher priority. Just because some people don't oike the sound of it doesn't mean it's wrongz at least everyone understands it without confusion or misinterpretation.

Extra example:
* Don't localize "Other Signal users who are saved to your phone's contact list." as "Andere Signal-gebruikers die zijn opgeslagen in jouw telefoons contactenlijst." but instead localize it as "Andere Signal-gebruikers van wie het telefoonnummer voor komt in de systeemcontactenlijst van jouw telefoon."

===Other projects===
For other projects the style has not yet been written down, however some translators seem to hold on to [http://download.microsoft.com/download/4/7/e/47e135ad-15d7-4491-be78-369804f0d333/nld-nld-StyleGuide.pdf a style guide from Microsoft].

==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.
* ANY time you edit a translation on a project with multiple separate resources, make sure to open all the resources and check if the same string exists elsewhere to apply the exact same edit there. An example would be when you edit a string in the Android Signal messenger app, make sure to also check if the same string exists in the Desktop app, the iOS app, the website or the support center. It's not easy for other reviewers to spot the inconsistency later, so do this right away at the very moment you make an edit.
* Be extra careful with plurals in Transifex, it's easy to miss one of the plural forms when reviewing. You can check all plurals again by searching for pluralized:yes
* Found a spelling mistake, grammar mistake, word order mistake or some word which is better substituted with another word? Don't just correct it when you see it and move on, check all the strings on all the resources for the same mistake or imperfection and correct that mistake on all the strings where it occurs. The moment you noticed something is the only opportunity to come up with a consistent solution across all the strings.

==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 punctuation is accurate, the capitalization is accurate, there are no double white spaces, and no missing white spaces
* 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.
* Don't just look at untranslated string, some strings are automatically translated by Transifex but might still be wrong because the context requires a different translation. use source_updated_after:dd-mm-yyyy to find all the new strings. Also check for edits made by others, using translation_updated_after:dd-mm-yyyy .

==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.''

===Grammar and word order in sentences===
*[https://www.dutchgrammar.com/en/?n=WordOrder.00 https://www.dutchgrammar.com/en/?n=WordOrder.00] About word order in sentences. It's not just one page, keep clicking on next page in the bottom right to see more examples.
*[http://redekundig.nl/ http://redekundig.nl/] a tool to help identify the structure of a Dutch sentence. Very helpful if you're dealing with complex grammatical rules and need to understand the sentence you are reviewing.
* [https://urd2.let.rug.nl/~vannoord/bin/alpino https://urd2.let.rug.nl/~vannoord/bin/alpino] university hosted tool to identify structure of a Dutch sentence. It's the same tool as redekundig.nl but hosted elsewhere, and the interface is harder to comprehend. Would advise trying this in case redekundig.nl isn't giving you the information you need.
* [https://onzetaal.nl/taaladvies/signaalwoorden-lijst/ List of signal words], use these wherever possible, they help clarify your message and prevent ambiguity.
* Dutch article debunking myths about 'new grammar rules': https://vrttaal.net/nieuws/kranten-haal-het-nepnieuws-over-de-ans-van-jullie-site

===Style and tone===
* First follow any style guide you find here on this wiki for language and project you are working on
* If you are missing something, contact other translators
* If you search for style advise from other websites, avoid getting it from tech companies who make up their own version of Dutch language based on marketing rather than proper standard Dutch. Also avoid other wiki's which are often written by opinionated people who are not representative for the language. That doesn't mean you can't read them and learn from them, but take it with a grain of salt.

===Spelling===
*[https://taaladvies.net Taaladvies]
*[https://taal.vrt.be Taalnet]
*[https://onzetaal.nl OnzeTaal]

===Technical terminology===
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:
[https://docs.google.com/spreadsheets/d/1OPyeWDq2rtPf9fEpCLRpHl9Hn--OfFbWLbrGtZx3lYI/edit?usp=sharing Dutch Unified Localization Lab Glossary]. The document is maintained by Erin (a localization lab employee). If you wish to add comments, edits or suggest new entries, do so using the "Comment" feature in the spreadsheet.

==Language varieties==
Dutch language varieties do not have their own glossary, style guide or terminology. All of these languages varieties follow Dutch (nl). there is generally no use in setting up resources for nl_NL, nl_BE or any other nl_* region, project maintainers should simply set up nl.

===Dutch in Belgium / Flemish (nl_BE)===
Flemish people may live in a different geographical region but are in a language union with and are in the same language region as Dutch people, therefore there are usually no differences between nl_NL and nl_BE. Projects should be localized to standardized Dutch (nl)(Standaardnederlands / Algemeen Nederlands). In the rare case some translation isn't clear to Flemish speakers, they can request to phrase the translation differently, but at all times the translation should conform to standard Dutch.

There is a Wikipedia page on the differences between these language varieties, however some of the differences are being exaggerated: https://nl.wikipedia.org/wiki/Lijst_van_verschillen_tussen_het_Nederlands_in_Belgi%C3%AB,_Nederland_en_Suriname

===Other varieties===
Below you find a list of other language varieties along with their ISO 3166-1 code:
* nl_AW Dutch (Aruba)
* nl_BQ Dutch (Caribbean Netherlands (Bonaire, Saba, Sint Eustatius))
* nl_CW Dutch (Curaçao)
* nl_SR Dutch (Suriname)
* nl_SX Dutch (Sint Maarten)

==Similar languages==
If you want to localize a project to a language which has strong similarities to Dutch and if there already exist good quality translations to Dutch, than it is recommended to base your translations of Dutch rather than English or an other source language. This may make translations faster, but more importantly it also keeps the texts consistent, so that someone who lives just across the border, or someone who has family in the other region, doesn't see completely different texts for the same project. In Transifex there is an option to swap which language you are using as the source language for your translations; you will find it by clicking the setting icon in the top right of the translation interface. Any strings that have not yet been translated to Dutch will automatically still be shown as the original source language for the project (usually English).

===West Frisian (fy_NL)===
Frisian is a language of its own, but because most if Frisians actually live in the Netherlands and have Dutch as their first or second language, and because the Frisian localization community is very small, Frisian is merged with the Dutch localization community. Of course they have their own style, terminology and glossary but for most projects there are too few translators available to maintain those. Project maintainers should add Frisian (fy) to their resources to offer Frisians a chance to preserve their language and culture.

===Afrikaans (af)===
Afrikaans is a language on its own with strong similarities to Dutch. It is spoken in the southern regions of Africa and it has its own localization community unrelated to Dutch. Most Afrikaans speakers have English as their first or second language, so there usually aren't many translators who feel the need to localize a project to Afrikaans. Never the less Afrikaans has plenty of speakers who prefer Afrikaans over English, and project maintainers should add Afrikaans (af) to their resources.

Dutch

2021-05-26T18:31:58Z

Meteor0id: Fix many typos

Dutch is the first language of about 24 million people, and a second language to another 5 million people, making it one of the 40 most spoken languages in the world. It is an official language in the Netherlands, Suriname and the Belgium. Dutch is closely related to English and German, and because Dutch is not a world language, most people with Dutch as their first language are also proficient in English. Never the less not all who speak Dutch are proficient in English, and localization to Dutch helps create a better understanding of the app / website or whatever resource is being translated.
The Dutch language plays a significant role in it's cultural differences: The Dutch often view themselves as more nuanced and reserved than for example Americans. The language is typically more descriptive and less figurative than English.

__TOC__

==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 [https://internetfreedomfestival.org/ International Freedom Festival] domain and is subject to their [https://www.internetfreedomfestival.org/wiki/index.php/Code_of_Conduct Code of Conduct]. Be sure to read through the [https://www.internetfreedomfestival.org/wiki/index.php/Code_of_Conduct Code of Conduct] and then [mailto:info@localizationlab.org?subject=Mattermost%20Sign-up&body=Please%20send%20me%20a%20link%20to%20sign%20up%20for%20Mattermost. 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==
Ask yourself: "If my 65 year old mother read this (who has a total of 3 apps on her phone and uses only one of them on a weekly basis), would she understand this without anyone's help?". The goal is not to translate words, the goal is to make the text understandable to people who grew up in a different country.

===Signal Messenger===
''This Style guide is a result of reviewers communicating about inconsistencies and solutions to those. 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. We will try to make this style guide easier to read in the future.''

* The most important rule to always keep in question yourself who your audience will be and whether they will fully understand it. Yes, you are doing this work on behave of the Signal developers, but your audience are Signal users. Place yourself in the frame of mind of a Signal user who doesn't really know much about Signal and is trying to understand his options. Don't just translate literary, translate in such a way that it makes sense, is accurate, and is easy to read for the end user.
* 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. 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, meaning different words and/or a different structure of the sentence. An example: "Signal needs location services enabled to discover and connect with your old Android device." is localized as "Om je oude Android apparaat te kunnen detecteren en om er verbinding mee te maken is het nodig dat locatiebepaling op je apparaat is ingeschakeld.". Another example: don't write "Om het in te schakelen, tik op de schuifknop zodat hij blauw wordt." but instead write "Tik op de schuifknop zodat hij blauw wordt om meekijkpreventie in te schakelen."
* 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 punctuation, end the sentence with a period. If the description does not contain any punctuation, 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 Dutch people also get it wrong. [https://www.dutchgrammar.com/en/?n=WordOrder.00] 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. An example: Don't write "Deze personen kunnen door jou niet direct worden toegevoegd aan de groep." instead write "Deze personen kunnen door jou niet direct aan de groep worden toegevoegd.".
* 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 white space: 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 …
* Make sure the subject is repeated in every new sentence, do not refer back to a previous sentence. We do this to keep texts easy to read and understand. An example: do not write "Turing this on allows you to receive emails. They will contain information about your account." instead write "Turning this on allows you to receive emails. The emails you will receive contain information about your account.".
* Avoid anglicisms, our job is to localize the content so it can be understood by as many people as possible, that includes people who don't understand even the most common of English words.
* For units we follow the Si-standards. That means we translate 20MB as 20 MB with a white space. Kilobytes as kB. Note that Signal does not use KiB, MiB etc, because Signal is following the same units as the Android operating system. The same rule applies to other units such as 10s becoming 10 s. Abbreviations for minutes, months and weeks are not si units but we agreed to translate those as "min", "mnd" and "w". Capitalization matters.
* The text strings for the app store sometimes contain wordplay. If a good wordplay in Dutch can't be found, than rather leave the word joke out and just factually describe the change.
* Use pronoun + "wie" instead of "die" wherever possible. Read [https://taaladvies.net/taal/advies/vraag/1564 Taaladvies about wie/die] about where to use "wie" and where to use "die". This is a style choice we made to make complex sentences easier to comprehend.
* Use "van wie", "bij wie", "op wie" and "voor wie" instead of "waarvan", "waarmee", "waarop" and "waarvoor" wherever possible.
* For texts on buttons in Android and Desktop use the infinitive (infinitief) grammatical mood (werkwoordswijs), do not use the imperative (gebiedende wijs) because we don't want to give the user the impression that he is recommended or required to press the button. It is not imperative you clikc the button, it is merely an option you have. This is the norm in almost all Dutch translations also outside of the Signal project. Only iOS still often uses the imperative, so for iOS we have not yet decided which form we wish to use. Examples: Do use "Aan gesprek deelnemen", "Aan Signal doneren" and "Alice toevoegen". Do not use "Voeg Alice toe" or "Deelnemen aan gesprek" or "Doneren aan Signal".
* Only capitalize the first letter. Unlike English we don't capitalize every word in Dutch.
* Try to stick to Dutch words, even if you see English words being used in other apps: "timer" becomes "tijdspanne", "admin" "beheerder", "checkbox" "selectievakje of aankruisvakje", "updaten" "bijwerken", "icon" "pictogram", "non-profit" "organisatie zonder winstoogmerk", "error" "fout", "database""databank" etc. You can find words like these listed in the Transifex Glossary for the Dutch Signal project.
* Beware of capitalization: use "QR-code" do not use "QR-Code" or "qr-code". "WiFi" is spelled different in Dutch: "wifi" all lowercase and without a dash. You can find words like these listed in the Transifex Glossary for the Dutch Signal project.
* Use [https://onzetaal.nl/taaladvies/signaalwoorden-lijst/ signal words] (words that indicate summation, contradiction etc.) wherever possible.
* Use formal verbs where their is no difference in meaning: use "je kunt" not "je kan". Howerver for "kun je" versus "kan je" there is a minor difference: "kan je" is more proposing while "kun je" is more forcefully suggestive. Therefore we use "kan je" instead of "kun je", and "zal je" instead of "zul je". [https://taalhelden.org/bericht/het-kan-je-kun-je https://taalhelden.org/bericht/het-kan-je-kun-je]
* Don't forget that although in English articles can be omitted, in Dutch it's not an accepted practice to omit the article. For example: "Playback time of audio attachment" should be localized as "Afspeellengte van HET audiobericht".
* Don't use possessive pronounce for things the user isn't possessing: Don't write "Open Signal-Desktop en gebruik de sneltoetsen om je tekstgrootte aan te passen.", instead write "Open Signal-Desktop en gebruik de sneltoetsen om de tekstgrootte aan te passen.". Users don't have font size, Signal has font size.
* We consistently use only the ‘rode werkwoordsvolgorde’, never the ‘groene werkwoordsvolgorde’. This means we never write "... vertrokken is." but instead always write "... is vertrokken.". For more information about verb order: [https://onzetaal.nl/taaladvies/rode-groene-volgorde/ https://onzetaal.nl/taaladvies/rode-groene-volgorde/]
* Do not hesitate to make use of 'old' or 'formal' words or grammer wherever it reduces ambiguity. For example the phrase "Journalist Bergman
Zag tijdens een interview met De Koning deze foto op zijn bureau staan." For most readers it wil be clear that the photo was on the Kings desk, but some may understand it in the litteral sense and understand that the photo was on the desk of journalist Berman. The solution to prevent this ambiguity is to use grammar whoch is perfectly correct, but isn't used often anymore: "Journalist Berman zag tijdens een interview met De Koning deze foto of diens bureau staan." (In case of a female person it would be "dier" instead of "diens". Don't shy away from formal language, avoiding ambiguoty is of a hogher priority. Just because some people don't oike the sound of it doesn't mean it's wrongz at least everyone understands it without confusion or misinterpretation.

Extra example:
* Don't localize "Other Signal users who are saved to your phone's contact list." as "Andere Signal-gebruikers die zijn opgeslagen in jouw telefoons contactenlijst." but instead localize it as "Andere Signal-gebruikers van wie het telefoonnummer voor komt in de systeemcontactenlijst van jouw telefoon."

===Other projects===
For other projects the style has not yet been written down, however some translators seem to hold on to [http://download.microsoft.com/download/4/7/e/47e135ad-15d7-4491-be78-369804f0d333/nld-nld-StyleGuide.pdf a style guide from Microsoft].

==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.
* ANY time you edit a translation on a project with multiple separate resources, make sure to open all the resources and check if the same string exists elsewhere to apply the exact same edit there. An example would be when you edit a string in the Android Signal messenger app, make sure to also check if the same string exists in the Desktop app, the iOS app, the website or the support center. It's not easy for other reviewers to spot the inconsistency later, so do this right away at the very moment you make an edit.
* Be extra careful with plurals in Transifex, it's easy to miss one of the plural forms when reviewing. You can check all plurals again by searching for pluralized:yes
* Found a spelling mistake, grammar mistake, word order mistake or some word which is better substituted with another word? Don't just correct it when you see it and move on, check all the strings on all the resources for the same mistake or imperfection and correct that mistake on all the strings where it occurs. The moment you noticed something is the only opportunity to come up with a consistent solution across all the strings.

==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 punctuation is accurate, the capitalization is accurate, there are no double white spaces, and no missing white spaces
* 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.
* Don't just look at untranslated string, some strings are automatically translated by Transifex but might still be wrong because the context requires a different translation. use source_updated_after:dd-mm-yyyy to find all the new strings. Also check for edits made by others, using translation_updated_after:dd-mm-yyyy .

==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.''

===Grammar and word order in sentences===
*[https://www.dutchgrammar.com/en/?n=WordOrder.00 https://www.dutchgrammar.com/en/?n=WordOrder.00] About word order in sentences. It's not just one page, keep clicking on next page in the bottom right to see more examples.
*[http://redekundig.nl/ http://redekundig.nl/] a tool to help identify the structure of a Dutch sentence. Very helpful if you're dealing with complex grammatical rules and need to understand the sentence you are reviewing.
* [https://urd2.let.rug.nl/~vannoord/bin/alpino https://urd2.let.rug.nl/~vannoord/bin/alpino] university hosted tool to identify structure of a Dutch sentence. It's the same tool as redekundig.nl but hosted elsewhere, and the interface is harder to comprehend. Would advise trying this in case redekundig.nl isn't giving you the information you need.
* [https://onzetaal.nl/taaladvies/signaalwoorden-lijst/ List of signal words], use these wherever possible, they help clarify your message and prevent ambiguity.
* Dutch article debunking myths about 'new grammar rules': https://vrttaal.net/nieuws/kranten-haal-het-nepnieuws-over-de-ans-van-jullie-site

===Style and tone===
* First follow any style guide you find here on this wiki for language and project you are working on
* If you are missing something, contact other translators
* If you search for style advise from other websites, avoid getting it from tech companies who make up their own version of Dutch language based on marketing rather than proper standard Dutch. Also avoid other wiki's which are often written by opinionated people who are not representative for the language. That doesn't mean you can't read them and learn from them, but take it with a grain of salt.

===Spelling===
*[https://taaladvies.net Taaladvies]
*[https://taal.vrt.be Taalnet]
*[https://onzetaal.nl OnzeTaal]

===Technical terminology===
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:
[https://docs.google.com/spreadsheets/d/1OPyeWDq2rtPf9fEpCLRpHl9Hn--OfFbWLbrGtZx3lYI/edit?usp=sharing Dutch Unified Localization Lab Glossary]. The document is maintained by Erin (a localization lab employee). If you wish to add comments, edits or suggest new entries, do so using the "Comment" feature in the spreadsheet.

==Language varieties==
Dutch language varieties do not have their own glossary, style guide or terminology. All of these languages varieties follow Dutch (nl). there is generally no use in setting up resources for nl_NL, nl_BE or any other nl_* region, project maintainers should simply set up nl.

===Dutch in Belgium / Flemish (nl_BE)===
Flemish people may live in a different geographical region but are in a language union with and are in the same language region as Dutch people, therefore there are usually no differences between nl_NL and nl_BE. Projects should be localized to standardized Dutch (nl)(Standaardnederlands / Algemeen Nederlands). In the rare case some translation isn't clear to Flemish speakers, they can request to phrase the translation differently, but at all times the translation should conform to standard Dutch.

There is a Wikipedia page on the differences between these language varieties, however some of the differences are being exaggerated: https://nl.wikipedia.org/wiki/Lijst_van_verschillen_tussen_het_Nederlands_in_Belgi%C3%AB,_Nederland_en_Suriname

===Other varieties===
Below you find a list of other language varieties along with their ISO 3166-1 code:
* nl_AW Dutch (Aruba)
* nl_BQ Dutch (Caribbean Netherlands (Bonaire, Saba, Sint Eustatius))
* nl_CW Dutch (Curaçao)
* nl_SR Dutch (Suriname)
* nl_SX Dutch (Sint Maarten)

==Similar languages==
If you want to localize a project to a language which has strong similarities to Dutch and if there already exist good quality translations to Dutch, than it is recommended to base your translations of Dutch rather than English or an other source language. This may make translations faster, but more importantly it also keeps the texts consistent, so that someone who lives just across the border, or someone who has family in the other region, doesn't see completely different texts for the same project. In Transifex there is an option to swap which language you are using as the source language for your translations; you will find it by clicking the setting icon in the top right of the translation interface. Any strings that have not yet been translated to Dutch will automatically still be shown as the original source language for the project (usually English).

===West Frisian (fy_NL)===
Frisian is a language of its own, but because most if Frisians actually live in the Netherlands and have Dutch as their first or second language, and because the Frisian localization community is very small, Frisian is merged with the Dutch localization community. Of course they have their own style, terminology and glossary but for most projects there are too few translators available to maintain those. Project maintainers should add Frisian (fy) to their resources to offer Frisians a chance to preserve their language and culture.

===Afrikaans (af)===
Afrikaans is a language on its own with strong similarities to Dutch. It is spoken in the southern regions of Africa and it has its own localization community unrelated to Dutch. Most Afrikaans speakers have English as their first or second language, so there usually aren't many translators who feel the need to localize a project to Afrikaans. Never the less Afrikaans has plenty of speakers who prefer Afrikaans over English, and project maintainers should add Afrikaans (af) to their resources.

Dutch

2021-05-26T18:30:15Z

Meteor0id: Add short introduction to Dutch

Dutch is the first language of about 24 million people, and a second language to another 5 million people, making it one of the 40 most spoken languages in the world. It is an official language in the Netherlands, Suriname and the Belgium. Dutch is closely related to English and German, and because Dutch is not a world language, most people with Dutch as their first language are also proficient in English. Never the less not all who speak Dutch are proficient in English, and localization to Dutch helps create a better understanding of the app / website or whatever resource is being translated.
The Dutch language plays a significant role in it's culteral differnces: The Dutch often view themselfs as more nuanced and reserved than for exmaple Americans. The language is typically more descriptive and less figurative than English.

__TOC__

==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 [https://internetfreedomfestival.org/ International Freedom Festival] domain and is subject to their [https://www.internetfreedomfestival.org/wiki/index.php/Code_of_Conduct Code of Conduct]. Be sure to read through the [https://www.internetfreedomfestival.org/wiki/index.php/Code_of_Conduct Code of Conduct] and then [mailto:info@localizationlab.org?subject=Mattermost%20Sign-up&body=Please%20send%20me%20a%20link%20to%20sign%20up%20for%20Mattermost. 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==
Ask yourself: "If my 65 year old mother read this (who has a total of 3 apps on her phone and uses only one of them on a weekly basis), would she understand this without anyone's help?". The goal is not to translate words, the goal is to make the text understandable to people who grew up in a different country.

===Signal Messenger===
''This Style guide is a result of reviewers communicating about inconsistencies and solutions to those. 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. We will try to make this style guide easier to read in the future.''

* The most important rule to always keep in question yourself who your audience will be and whether they will fully understand it. Yes, you are doing this work on behave of the Signal developers, but your audience are Signal users. Place yourself in the frame of mind of a Signal user who doesn't really know much about Signal and is trying to understand his options. Don't just translate literary, translate in such a way that it makes sense, is accurate, and is easy to read for the end user.
* 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. 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, meaning different words and/or a different structure of the sentence. An example: "Signal needs location services enabled to discover and connect with your old Android device." is localized as "Om je oude Android apparaat te kunnen detecteren en om er verbinding mee te maken is het nodig dat locatiebepaling op je apparaat is ingeschakeld.". Another example: don't write "Om het in te schakelen, tik op de schuifknop zodat hij blauw wordt." but instead write "Tik op de schuifknop zodat hij blauw wordt om meekijkpreventie in te schakelen."
* 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 punctuation, end the sentence with a period. If the description does not contain any punctuation, 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 Dutch people also get it wrong. [https://www.dutchgrammar.com/en/?n=WordOrder.00] 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. An example: Don't write "Deze personen kunnen door jou niet direct worden toegevoegd aan de groep." instead write "Deze personen kunnen door jou niet direct aan de groep worden toegevoegd.".
* 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 white space: 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 …
* Make sure the subject is repeated in every new sentence, do not refer back to a previous sentence. We do this to keep texts easy to read and understand. An example: do not write "Turing this on allows you to receive emails. They will contain information about your account." instead write "Turning this on allows you to receive emails. The emails you will receive contain information about your account.".
* Avoid anglicisms, our job is to localize the content so it can be understood by as many people as possible, that includes people who don't understand even the most common of English words.
* For units we follow the Si-standards. That means we translate 20MB as 20 MB with a white space. Kilobytes as kB. Note that Signal does not use KiB, MiB etc, because Signal is following the same units as the Android operating system. The same rule applies to other units such as 10s becoming 10 s. Abbreviations for minutes, months and weeks are not si units but we agreed to translate those as "min", "mnd" and "w". Capitalization matters.
* The text strings for the app store sometimes contain wordplay. If a good wordplay in Dutch can't be found, than rather leave the word joke out and just factually describe the change.
* Use pronoun + "wie" instead of "die" wherever possible. Read [https://taaladvies.net/taal/advies/vraag/1564 Taaladvies about wie/die] about where to use "wie" and where to use "die". This is a style choice we made to make complex sentences easier to comprehend.
* Use "van wie", "bij wie", "op wie" and "voor wie" instead of "waarvan", "waarmee", "waarop" and "waarvoor" wherever possible.
* For texts on buttons in Android and Desktop use the infinitive (infinitief) grammatical mood (werkwoordswijs), do not use the imperative (gebiedende wijs) because we don't want to give the user the impression that he is recommended or required to press the button. It is not imperative you clikc the button, it is merely an option you have. This is the norm in almost all Dutch translations also outside of the Signal project. Only iOS still often uses the imperative, so for iOS we have not yet decided which form we wish to use. Examples: Do use "Aan gesprek deelnemen", "Aan Signal doneren" and "Alice toevoegen". Do not use "Voeg Alice toe" or "Deelnemen aan gesprek" or "Doneren aan Signal".
* Only capitalize the first letter. Unlike English we don't capitalize every word in Dutch.
* Try to stick to Dutch words, even if you see English words being used in other apps: "timer" becomes "tijdspanne", "admin" "beheerder", "checkbox" "selectievakje of aankruisvakje", "updaten" "bijwerken", "icon" "pictogram", "non-profit" "organisatie zonder winstoogmerk", "error" "fout", "database""databank" etc. You can find words like these listed in the Transifex Glossary for the Dutch Signal project.
* Beware of capitalization: use "QR-code" do not use "QR-Code" or "qr-code". "WiFi" is spelled different in Dutch: "wifi" all lowercase and without a dash. You can find words like these listed in the Transifex Glossary for the Dutch Signal project.
* Use [https://onzetaal.nl/taaladvies/signaalwoorden-lijst/ signal words] (words that indicate summation, contradiction etc.) wherever possible.
* Use formal verbs where their is no difference in meaning: use "je kunt" not "je kan". Howerver for "kun je" versus "kan je" there is a minor difference: "kan je" is more proposing while "kun je" is more forcefully suggestive. Therefore we use "kan je" instead of "kun je", and "zal je" instead of "zul je". [https://taalhelden.org/bericht/het-kan-je-kun-je https://taalhelden.org/bericht/het-kan-je-kun-je]
* Don't forget that although in English articles can be omitted, in Dutch it's not an accepted practice to omit the article. For example: "Playback time of audio attachment" should be localized as "Afspeellengte van HET audiobericht".
* Don't use possessive pronounce for things the user isn't possessing: Don't write "Open Signal-Desktop en gebruik de sneltoetsen om je tekstgrootte aan te passen.", instead write "Open Signal-Desktop en gebruik de sneltoetsen om de tekstgrootte aan te passen.". Users don't have font size, Signal has font size.
* We consistently use only the ‘rode werkwoordsvolgorde’, never the ‘groene werkwoordsvolgorde’. This means we never write "... vertrokken is." but instead always write "... is vertrokken.". For more information about verb order: [https://onzetaal.nl/taaladvies/rode-groene-volgorde/ https://onzetaal.nl/taaladvies/rode-groene-volgorde/]
* Do not hesitate to make use of 'old' or 'formal' words or grammer wherever it reduces ambiguity. For example the phrase "Journalist Bergman
Zag tijdens een interview met De Koning deze foto op zijn bureau staan." For most readers it wil be clear that the photo was on the Kings desk, but some may understand it in the litteral sense and understand that the photo was on the desk of journalist Berman. The solution to prevent this ambiguity is to use grammar whoch is perfectly correct, but isn't used often anymore: "Journalist Berman zag tijdens een interview met De Koning deze foto of diens bureau staan." (In case of a female person it would be "dier" instead of "diens". Don't shy away from formal language, avoiding ambiguoty is of a hogher priority. Just because some people don't oike the sound of it doesn't mean it's wrongz at least everyone understands it without confusion or misinterpretation.

Extra example:
* Don't localize "Other Signal users who are saved to your phone's contact list." as "Andere Signal-gebruikers die zijn opgeslagen in jouw telefoons contactenlijst." but instead localize it as "Andere Signal-gebruikers van wie het telefoonnummer voor komt in de systeemcontactenlijst van jouw telefoon."

===Other projects===
For other projects the style has not yet been written down, however some translators seem to hold on to [http://download.microsoft.com/download/4/7/e/47e135ad-15d7-4491-be78-369804f0d333/nld-nld-StyleGuide.pdf a style guide from Microsoft].

==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.
* ANY time you edit a translation on a project with multiple separate resources, make sure to open all the resources and check if the same string exists elsewhere to apply the exact same edit there. An example would be when you edit a string in the Android Signal messenger app, make sure to also check if the same string exists in the Desktop app, the iOS app, the website or the support center. It's not easy for other reviewers to spot the inconsistency later, so do this right away at the very moment you make an edit.
* Be extra careful with plurals in Transifex, it's easy to miss one of the plural forms when reviewing. You can check all plurals again by searching for pluralized:yes
* Found a spelling mistake, grammar mistake, word order mistake or some word which is better substituted with another word? Don't just correct it when you see it and move on, check all the strings on all the resources for the same mistake or imperfection and correct that mistake on all the strings where it occurs. The moment you noticed something is the only opportunity to come up with a consistent solution across all the strings.

==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 punctuation is accurate, the capitalization is accurate, there are no double white spaces, and no missing white spaces
* 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.
* Don't just look at untranslated string, some strings are automatically translated by Transifex but might still be wrong because the context requires a different translation. use source_updated_after:dd-mm-yyyy to find all the new strings. Also check for edits made by others, using translation_updated_after:dd-mm-yyyy .

==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.''

===Grammar and word order in sentences===
*[https://www.dutchgrammar.com/en/?n=WordOrder.00 https://www.dutchgrammar.com/en/?n=WordOrder.00] About word order in sentences. It's not just one page, keep clicking on next page in the bottom right to see more examples.
*[http://redekundig.nl/ http://redekundig.nl/] a tool to help identify the structure of a Dutch sentence. Very helpful if you're dealing with complex grammatical rules and need to understand the sentence you are reviewing.
* [https://urd2.let.rug.nl/~vannoord/bin/alpino https://urd2.let.rug.nl/~vannoord/bin/alpino] university hosted tool to identify structure of a Dutch sentence. It's the same tool as redekundig.nl but hosted elsewhere, and the interface is harder to comprehend. Would advise trying this in case redekundig.nl isn't giving you the information you need.
* [https://onzetaal.nl/taaladvies/signaalwoorden-lijst/ List of signal words], use these wherever possible, they help clarify your message and prevent ambiguity.
* Dutch article debunking myths about 'new grammer rules': https://vrttaal.net/nieuws/kranten-haal-het-nepnieuws-over-de-ans-van-jullie-site

===Style and tone===
* First follow any style guide you find here on this wiki for language and project you are working on
* If you are missing something, contact other translators
* If you search for style advise from other websites, avoid getting it from tech companies who make up their own version of Dutch language based on marketing rather than proper standard Dutch. Also avoid other wiki's which are often written by opinionated people who are not representative for the language. That doesn't mean you can't read them and learn from them, but take it with a grain of salt.

===Spelling===
*[https://taaladvies.net Taaladvies]
*[https://taal.vrt.be Taalnet]
*[https://onzetaal.nl OnzeTaal]

===Technical terminology===
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:
[https://docs.google.com/spreadsheets/d/1OPyeWDq2rtPf9fEpCLRpHl9Hn--OfFbWLbrGtZx3lYI/edit?usp=sharing Dutch Unified Localization Lab Glossary]. The document is maintained by Erin (a localization lab employee). If you wish to add comments, edits or suggest new entries, do so using the "Comment" feature in the spreadsheet.

==Language varieties==
Dutch language varieties do not have their own glossary, style guide or terminology. All of these languages varieties follow Dutch (nl). there is generally no use in setting up resources for nl_NL, nl_BE or any other nl_* region, project maintainers should simply set up nl.

===Dutch in Belgium / Flemish (nl_BE)===
Flemish people may live in a different geographical region but are in a language union with and are in the same language region as Dutch people, therefore there are usually no differences between nl_NL and nl_BE. Projects should be localized to standardized Dutch (nl)(Standaardnederlands / Algemeen Nederlands). In the rare case some translation isn't clear to Flemish speakers, they can request to phrase the translation differently, but at all times the translation should conform to standard Dutch.

There is a Wikipedia page on the differences between these language varieties, however some of the differences are being exaggerated: https://nl.wikipedia.org/wiki/Lijst_van_verschillen_tussen_het_Nederlands_in_Belgi%C3%AB,_Nederland_en_Suriname

===Other varieties===
Below you find a list of other language varieties along with their ISO 3166-1 code:
* nl_AW Dutch (Aruba)
* nl_BQ Dutch (Caribbean Netherlands (Bonaire, Saba, Sint Eustatius))
* nl_CW Dutch (Curaçao)
* nl_SR Dutch (Suriname)
* nl_SX Dutch (Sint Maarten)

==Similar languages==
If you want to localize a project to a language which has strong similarities to Dutch and if there already exist good quality translations to Dutch, than it is recommended to base your translations of Dutch rather than English or an other source language. This may make translations faster, but more importantly it also keeps the texts consistent, so that someone who lives just across the border, or someone who has family in the other region, doesn't see completely different texts for the same project. In Transifex there is an option to swap which language you are using as the source language for your translations; you will find it by clicking the setting icon in the top right of the translation interface. Any strings that have not yet been translated to Dutch will automatically still be shown as the original source language for the project (usually English).

===West Frisian (fy_NL)===
Frisian is a language of its own, but because most if Frisians actually live in the Netherlands and have Dutch as their first or second language, and because the Frisian localization community is very small, Frisian is merged with the Dutch localization community. Of course they have their own style, terminology and glossary but for most projects there are too few translators available to maintain those. Project maintainers should add Frisian (fy) to their resources to offer Frisians a chance to preserve their language and culture.

===Afrikaans (af)===
Afrikaans is a language on its own with strong similarities to Dutch. It is spoken in the southern regions of Africa and it has its own localization community unrelated to Dutch. Most Afrikaans speakers have English as their first or second language, so there usually aren't many translators who feel the need to localize a project to Afrikaans. Never the less Afrikaans has plenty of speakers who prefer Afrikaans over English, and project maintainers should add Afrikaans (af) to their resources.

Dutch

2021-05-26T17:47:53Z

Meteor0id: better explain grammatical mood

__TOC__

==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 [https://internetfreedomfestival.org/ International Freedom Festival] domain and is subject to their [https://www.internetfreedomfestival.org/wiki/index.php/Code_of_Conduct Code of Conduct]. Be sure to read through the [https://www.internetfreedomfestival.org/wiki/index.php/Code_of_Conduct Code of Conduct] and then [mailto:info@localizationlab.org?subject=Mattermost%20Sign-up&body=Please%20send%20me%20a%20link%20to%20sign%20up%20for%20Mattermost. 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==
Ask yourself: "If my 65 year old mother read this (who has a total of 3 apps on her phone and uses only one of them on a weekly basis), would she understand this without anyone's help?". The goal is not to translate words, the goal is to make the text understandable to people who grew up in a different country.

===Signal Messenger===
''This Style guide is a result of reviewers communicating about inconsistencies and solutions to those. 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. We will try to make this style guide easier to read in the future.''

* The most important rule to always keep in question yourself who your audience will be and whether they will fully understand it. Yes, you are doing this work on behave of the Signal developers, but your audience are Signal users. Place yourself in the frame of mind of a Signal user who doesn't really know much about Signal and is trying to understand his options. Don't just translate literary, translate in such a way that it makes sense, is accurate, and is easy to read for the end user.
* 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. 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, meaning different words and/or a different structure of the sentence. An example: "Signal needs location services enabled to discover and connect with your old Android device." is localized as "Om je oude Android apparaat te kunnen detecteren en om er verbinding mee te maken is het nodig dat locatiebepaling op je apparaat is ingeschakeld.". Another example: don't write "Om het in te schakelen, tik op de schuifknop zodat hij blauw wordt." but instead write "Tik op de schuifknop zodat hij blauw wordt om meekijkpreventie in te schakelen."
* 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 punctuation, end the sentence with a period. If the description does not contain any punctuation, 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 Dutch people also get it wrong. [https://www.dutchgrammar.com/en/?n=WordOrder.00] 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. An example: Don't write "Deze personen kunnen door jou niet direct worden toegevoegd aan de groep." instead write "Deze personen kunnen door jou niet direct aan de groep worden toegevoegd.".
* 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 white space: 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 …
* Make sure the subject is repeated in every new sentence, do not refer back to a previous sentence. We do this to keep texts easy to read and understand. An example: do not write "Turing this on allows you to receive emails. They will contain information about your account." instead write "Turning this on allows you to receive emails. The emails you will receive contain information about your account.".
* Avoid anglicisms, our job is to localize the content so it can be understood by as many people as possible, that includes people who don't understand even the most common of English words.
* For units we follow the Si-standards. That means we translate 20MB as 20 MB with a white space. Kilobytes as kB. Note that Signal does not use KiB, MiB etc, because Signal is following the same units as the Android operating system. The same rule applies to other units such as 10s becoming 10 s. Abbreviations for minutes, months and weeks are not si units but we agreed to translate those as "min", "mnd" and "w". Capitalization matters.
* The text strings for the app store sometimes contain wordplay. If a good wordplay in Dutch can't be found, than rather leave the word joke out and just factually describe the change.
* Use pronoun + "wie" instead of "die" wherever possible. Read [https://taaladvies.net/taal/advies/vraag/1564 Taaladvies about wie/die] about where to use "wie" and where to use "die". This is a style choice we made to make complex sentences easier to comprehend.
* Use "van wie", "bij wie", "op wie" and "voor wie" instead of "waarvan", "waarmee", "waarop" and "waarvoor" wherever possible.
* For texts on buttons in Android and Desktop use the infinitive (infinitief) grammatical mood (werkwoordswijs), do not use the imperative (gebiedende wijs) because we don't want to give the user the impression that he is recommended or required to press the button. It is not imperative you clikc the button, it is merely an option you have. This is the norm in almost all Dutch translations also outside of the Signal project. Only iOS still often uses the imperative, so for iOS we have not yet decided which form we wish to use. Examples: Do use "Aan gesprek deelnemen", "Aan Signal doneren" and "Alice toevoegen". Do not use "Voeg Alice toe" or "Deelnemen aan gesprek" or "Doneren aan Signal".
* Only capitalize the first letter. Unlike English we don't capitalize every word in Dutch.
* Try to stick to Dutch words, even if you see English words being used in other apps: "timer" becomes "tijdspanne", "admin" "beheerder", "checkbox" "selectievakje of aankruisvakje", "updaten" "bijwerken", "icon" "pictogram", "non-profit" "organisatie zonder winstoogmerk", "error" "fout", "database""databank" etc. You can find words like these listed in the Transifex Glossary for the Dutch Signal project.
* Beware of capitalization: use "QR-code" do not use "QR-Code" or "qr-code". "WiFi" is spelled different in Dutch: "wifi" all lowercase and without a dash. You can find words like these listed in the Transifex Glossary for the Dutch Signal project.
* Use [https://onzetaal.nl/taaladvies/signaalwoorden-lijst/ signal words] (words that indicate summation, contradiction etc.) wherever possible.
* Use formal verbs where their is no difference in meaning: use "je kunt" not "je kan". Howerver for "kun je" versus "kan je" there is a minor difference: "kan je" is more proposing while "kun je" is more forcefully suggestive. Therefore we use "kan je" instead of "kun je", and "zal je" instead of "zul je". [https://taalhelden.org/bericht/het-kan-je-kun-je https://taalhelden.org/bericht/het-kan-je-kun-je]
* Don't forget that although in English articles can be omitted, in Dutch it's not an accepted practice to omit the article. For example: "Playback time of audio attachment" should be localized as "Afspeellengte van HET audiobericht".
* Don't use possessive pronounce for things the user isn't possessing: Don't write "Open Signal-Desktop en gebruik de sneltoetsen om je tekstgrootte aan te passen.", instead write "Open Signal-Desktop en gebruik de sneltoetsen om de tekstgrootte aan te passen.". Users don't have font size, Signal has font size.
* We consistently use only the ‘rode werkwoordsvolgorde’, never the ‘groene werkwoordsvolgorde’. This means we never write "... vertrokken is." but instead always write "... is vertrokken.". For more information about verb order: [https://onzetaal.nl/taaladvies/rode-groene-volgorde/ https://onzetaal.nl/taaladvies/rode-groene-volgorde/]
* Do not hesitate to make use of 'old' or 'formal' words or grammer wherever it reduces ambiguity. For example the phrase "Journalist Bergman
Zag tijdens een interview met De Koning deze foto op zijn bureau staan." For most readers it wil be clear that the photo was on the Kings desk, but some may understand it in the litteral sense and understand that the photo was on the desk of journalist Berman. The solution to prevent this ambiguity is to use grammar whoch is perfectly correct, but isn't used often anymore: "Journalist Berman zag tijdens een interview met De Koning deze foto of diens bureau staan." (In case of a female person it would be "dier" instead of "diens". Don't shy away from formal language, avoiding ambiguoty is of a hogher priority. Just because some people don't oike the sound of it doesn't mean it's wrongz at least everyone understands it without confusion or misinterpretation.

Extra example:
* Don't localize "Other Signal users who are saved to your phone's contact list." as "Andere Signal-gebruikers die zijn opgeslagen in jouw telefoons contactenlijst." but instead localize it as "Andere Signal-gebruikers van wie het telefoonnummer voor komt in de systeemcontactenlijst van jouw telefoon."

===Other projects===
For other projects the style has not yet been written down, however some translators seem to hold on to [http://download.microsoft.com/download/4/7/e/47e135ad-15d7-4491-be78-369804f0d333/nld-nld-StyleGuide.pdf a style guide from Microsoft].

==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.
* ANY time you edit a translation on a project with multiple separate resources, make sure to open all the resources and check if the same string exists elsewhere to apply the exact same edit there. An example would be when you edit a string in the Android Signal messenger app, make sure to also check if the same string exists in the Desktop app, the iOS app, the website or the support center. It's not easy for other reviewers to spot the inconsistency later, so do this right away at the very moment you make an edit.
* Be extra careful with plurals in Transifex, it's easy to miss one of the plural forms when reviewing. You can check all plurals again by searching for pluralized:yes
* Found a spelling mistake, grammar mistake, word order mistake or some word which is better substituted with another word? Don't just correct it when you see it and move on, check all the strings on all the resources for the same mistake or imperfection and correct that mistake on all the strings where it occurs. The moment you noticed something is the only opportunity to come up with a consistent solution across all the strings.

==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 punctuation is accurate, the capitalization is accurate, there are no double white spaces, and no missing white spaces
* 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.
* Don't just look at untranslated string, some strings are automatically translated by Transifex but might still be wrong because the context requires a different translation. use source_updated_after:dd-mm-yyyy to find all the new strings. Also check for edits made by others, using translation_updated_after:dd-mm-yyyy .

==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.''

===Grammar and word order in sentences===
*[https://www.dutchgrammar.com/en/?n=WordOrder.00 https://www.dutchgrammar.com/en/?n=WordOrder.00] About word order in sentences. It's not just one page, keep clicking on next page in the bottom right to see more examples.
*[http://redekundig.nl/ http://redekundig.nl/] a tool to help identify the structure of a Dutch sentence. Very helpful if you're dealing with complex grammatical rules and need to understand the sentence you are reviewing.
* [https://urd2.let.rug.nl/~vannoord/bin/alpino https://urd2.let.rug.nl/~vannoord/bin/alpino] university hosted tool to identify structure of a Dutch sentence. It's the same tool as redekundig.nl but hosted elsewhere, and the interface is harder to comprehend. Would advise trying this in case redekundig.nl isn't giving you the information you need.
* [https://onzetaal.nl/taaladvies/signaalwoorden-lijst/ List of signal words], use these wherever possible, they help clarify your message and prevent ambiguity.
* Dutch article debunking myths about 'new grammer rules': https://vrttaal.net/nieuws/kranten-haal-het-nepnieuws-over-de-ans-van-jullie-site

===Style and tone===
* First follow any style guide you find here on this wiki for language and project you are working on
* If you are missing something, contact other translators
* If you search for style advise from other websites, avoid getting it from tech companies who make up their own version of Dutch language based on marketing rather than proper standard Dutch. Also avoid other wiki's which are often written by opinionated people who are not representative for the language. That doesn't mean you can't read them and learn from them, but take it with a grain of salt.

===Spelling===
*[https://taaladvies.net Taaladvies]
*[https://taal.vrt.be Taalnet]
*[https://onzetaal.nl OnzeTaal]

===Technical terminology===
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:
[https://docs.google.com/spreadsheets/d/1OPyeWDq2rtPf9fEpCLRpHl9Hn--OfFbWLbrGtZx3lYI/edit?usp=sharing Dutch Unified Localization Lab Glossary]. The document is maintained by Erin (a localization lab employee). If you wish to add comments, edits or suggest new entries, do so using the "Comment" feature in the spreadsheet.

==Language varieties==
Dutch language varieties do not have their own glossary, style guide or terminology. All of these languages varieties follow Dutch (nl). there is generally no use in setting up resources for nl_NL, nl_BE or any other nl_* region, project maintainers should simply set up nl.

===Dutch in Belgium / Flemish (nl_BE)===
Flemish people may live in a different geographical region but are in a language union with and are in the same language region as Dutch people, therefore there are usually no differences between nl_NL and nl_BE. Projects should be localized to standardized Dutch (nl)(Standaardnederlands / Algemeen Nederlands). In the rare case some translation isn't clear to Flemish speakers, they can request to phrase the translation differently, but at all times the translation should conform to standard Dutch.

There is a Wikipedia page on the differences between these language varieties, however some of the differences are being exaggerated: https://nl.wikipedia.org/wiki/Lijst_van_verschillen_tussen_het_Nederlands_in_Belgi%C3%AB,_Nederland_en_Suriname

===Other varieties===
Below you find a list of other language varieties along with their ISO 3166-1 code:
* nl_AW Dutch (Aruba)
* nl_BQ Dutch (Caribbean Netherlands (Bonaire, Saba, Sint Eustatius))
* nl_CW Dutch (Curaçao)
* nl_SR Dutch (Suriname)
* nl_SX Dutch (Sint Maarten)

==Similar languages==
If you want to localize a project to a language which has strong similarities to Dutch and if there already exist good quality translations to Dutch, than it is recommended to base your translations of Dutch rather than English or an other source language. This may make translations faster, but more importantly it also keeps the texts consistent, so that someone who lives just across the border, or someone who has family in the other region, doesn't see completely different texts for the same project. In Transifex there is an option to swap which language you are using as the source language for your translations; you will find it by clicking the setting icon in the top right of the translation interface. Any strings that have not yet been translated to Dutch will automatically still be shown as the original source language for the project (usually English).

===West Frisian (fy_NL)===
Frisian is a language of its own, but because most if Frisians actually live in the Netherlands and have Dutch as their first or second language, and because the Frisian localization community is very small, Frisian is merged with the Dutch localization community. Of course they have their own style, terminology and glossary but for most projects there are too few translators available to maintain those. Project maintainers should add Frisian (fy) to their resources to offer Frisians a chance to preserve their language and culture.

===Afrikaans (af)===
Afrikaans is a language on its own with strong similarities to Dutch. It is spoken in the southern regions of Africa and it has its own localization community unrelated to Dutch. Most Afrikaans speakers have English as their first or second language, so there usually aren't many translators who feel the need to localize a project to Afrikaans. Never the less Afrikaans has plenty of speakers who prefer Afrikaans over English, and project maintainers should add Afrikaans (af) to their resources.

Dutch

2021-05-07T20:25:48Z

Meteor0id: address that using formal and / or old language is perfectly fine

__TOC__

==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 [https://internetfreedomfestival.org/ International Freedom Festival] domain and is subject to their [https://www.internetfreedomfestival.org/wiki/index.php/Code_of_Conduct Code of Conduct]. Be sure to read through the [https://www.internetfreedomfestival.org/wiki/index.php/Code_of_Conduct Code of Conduct] and then [mailto:info@localizationlab.org?subject=Mattermost%20Sign-up&body=Please%20send%20me%20a%20link%20to%20sign%20up%20for%20Mattermost. 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==
Ask yourself: "If my 65 year old mother read this (who has a total of 3 apps on her phone and uses only one of them on a weekly basis), would she understand this without anyone's help?". The goal is not to translate words, the goal is to make the text understandable to people who grew up in a different country.

===Signal Messenger===
''This Style guide is a result of reviewers communicating about inconsistencies and solutions to those. 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. We will try to make this style guide easier to read in the future.''

* The most important rule to always keep in question yourself who your audience will be and whether they will fully understand it. Yes, you are doing this work on behave of the Signal developers, but your audience are Signal users. Place yourself in the frame of mind of a Signal user who doesn't really know much about Signal and is trying to understand his options. Don't just translate literary, translate in such a way that it makes sense, is accurate, and is easy to read for the end user.
* 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. 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, meaning different words and/or a different structure of the sentence. An example: "Signal needs location services enabled to discover and connect with your old Android device." is localized as "Om je oude Android apparaat te kunnen detecteren en om er verbinding mee te maken is het nodig dat locatiebepaling op je apparaat is ingeschakeld.". Another example: don't write "Om het in te schakelen, tik op de schuifknop zodat hij blauw wordt." but instead write "Tik op de schuifknop zodat hij blauw wordt om meekijkpreventie in te schakelen."
* 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 punctuation, end the sentence with a period. If the description does not contain any punctuation, 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 Dutch people also get it wrong. [https://www.dutchgrammar.com/en/?n=WordOrder.00] 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. An example: Don't write "Deze personen kunnen door jou niet direct worden toegevoegd aan de groep." instead write "Deze personen kunnen door jou niet direct aan de groep worden toegevoegd.".
* 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 white space: 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 …
* Make sure the subject is repeated in every new sentence, do not refer back to a previous sentence. We do this to keep texts easy to read and understand. An example: do not write "Turing this on allows you to receive emails. They will contain information about your account." instead write "Turning this on allows you to receive emails. The emails you will receive contain information about your account.".
* Avoid anglicisms, our job is to localize the content so it can be understood by as many people as possible, that includes people who don't understand even the most common of English words.
* For units we follow the Si-standards. That means we translate 20MB as 20 MB with a white space. Kilobytes as kB. Note that Signal does not use KiB, MiB etc, because Signal is following the same units as the Android operating system. The same rule applies to other units such as 10s becoming 10 s. Abbreviations for minutes, months and weeks are not si units but we agreed to translate those as "min", "mnd" and "w". Capitalization matters.
* The text strings for the app store sometimes contain wordplay. If a good wordplay in Dutch can't be found, than rather leave the word joke out and just factually describe the change.
* Use pronoun + "wie" instead of "die" wherever possible. Read [https://taaladvies.net/taal/advies/vraag/1564 Taaladvies about wie/die] about where to use "wie" and where to use "die". This is a style choice we made to make complex sentences easier to comprehend.
* Use "van wie", "bij wie", "op wie" and "voor wie" instead of "waarvan", "waarmee", "waarop" and "waarvoor" wherever possible.
* For texts on buttons in Android and Desktop: use "Aan gesprek deelnemen", "Aan Signal doneren" and "Alice toevoegen". Do not use "Voeg Alice toe" or "Deelnemen aan gesprek" or "Doneren aan Signal". reason for this is optial readability. Also capitalize the first letter. on iOS we have not yet decided on the style, because that operating system often uses 'gebiedende wijs' rather than 'infinitief'.
* Try to stick to Dutch words, even if you see English words being used in other apps: "timer" becomes "tijdspanne", "admin" "beheerder", "checkbox" "selectievakje of aankruisvakje", "updaten" "bijwerken", "icon" "pictogram", "non-profit" "organisatie zonder winstoogmerk", "error" "fout", "database""databank" etc. You can find words like these listed in the Transifex Glossary for the Dutch Signal project.
* Beware of capitalization: use "QR-code" do not use "QR-Code" or "qr-code". "WiFi" is spelled different in Dutch: "wifi" all lowercase and without a dash. You can find words like these listed in the Transifex Glossary for the Dutch Signal project.
* Use [https://onzetaal.nl/taaladvies/signaalwoorden-lijst/ signal words] (words that indicate summation, contradiction etc.) wherever possible.
* Use formal verbs where their is no difference in meaning: use "je kunt" not "je kan". Howerver for "kun je" versus "kan je" there is a minor difference: "kan je" is more proposing while "kun je" is more forcefully suggestive. Therefore we use "kan je" instead of "kun je", and "zal je" instead of "zul je". [https://taalhelden.org/bericht/het-kan-je-kun-je https://taalhelden.org/bericht/het-kan-je-kun-je]
* Don't forget that although in English articles can be omitted, in Dutch it's not an accepted practice to omit the article. For example: "Playback time of audio attachment" should be localized as "Afspeellengte van HET audiobericht".
* Don't use possessive pronounce for things the user isn't possessing: Don't write "Open Signal-Desktop en gebruik de sneltoetsen om je tekstgrootte aan te passen.", instead write "Open Signal-Desktop en gebruik de sneltoetsen om de tekstgrootte aan te passen.". Users don't have font size, Signal has font size.
* We consistently use only the ‘rode werkwoordsvolgorde’, never the ‘groene werkwoordsvolgorde’. This means we never write "... vertrokken is." but instead always write "... is vertrokken.". For more information about verb order: [https://onzetaal.nl/taaladvies/rode-groene-volgorde/ https://onzetaal.nl/taaladvies/rode-groene-volgorde/]
* Do not hesitate to make use of 'old' or 'formal' words or grammer wherever it reduces ambiguity. For example the phrase "Journalist Bergman
Zag tijdens een interview met De Koning deze foto op zijn bureau staan." For most readers it wil be clear that the photo was on the Kings desk, but some may understand it in the litteral sense and understand that the photo was on the desk of journalist Berman. The solution to prevent this ambiguity is to use grammar whoch is perfectly correct, but isn't used often anymore: "Journalist Berman zag tijdens een interview met De Koning deze foto of diens bureau staan." (In case of a female person it would be "dier" instead of "diens". Don't shy away from formal language, avoiding ambiguoty is of a hogher priority. Just because some people don't oike the sound of it doesn't mean it's wrongz at least everyone understands it without confusion or misinterpretation.

Extra example:
* Don't localize "Other Signal users who are saved to your phone's contact list." as "Andere Signal-gebruikers die zijn opgeslagen in jouw telefoons contactenlijst." but instead localize it as "Andere Signal-gebruikers van wie het telefoonnummer voor komt in de systeemcontactenlijst van jouw telefoon."

===Other projects===
For other projects the style has not yet been written down, however some translators seem to hold on to [http://download.microsoft.com/download/4/7/e/47e135ad-15d7-4491-be78-369804f0d333/nld-nld-StyleGuide.pdf a style guide from Microsoft].

==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.
* ANY time you edit a translation on a project with multiple separate resources, make sure to open all the resources and check if the same string exists elsewhere to apply the exact same edit there. An example would be when you edit a string in the Android Signal messenger app, make sure to also check if the same string exists in the Desktop app, the iOS app, the website or the support center. It's not easy for other reviewers to spot the inconsistency later, so do this right away at the very moment you make an edit.
* Be extra careful with plurals in Transifex, it's easy to miss one of the plural forms when reviewing. You can check all plurals again by searching for pluralized:yes
* Found a spelling mistake, grammar mistake, word order mistake or some word which is better substituted with another word? Don't just correct it when you see it and move on, check all the strings on all the resources for the same mistake or imperfection and correct that mistake on all the strings where it occurs. The moment you noticed something is the only opportunity to come up with a consistent solution across all the strings.

==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 punctuation is accurate, the capitalization is accurate, there are no double white spaces, and no missing white spaces
* 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.
* Don't just look at untranslated string, some strings are automatically translated by Transifex but might still be wrong because the context requires a different translation. use source_updated_after:dd-mm-yyyy to find all the new strings. Also check for edits made by others, using translation_updated_after:dd-mm-yyyy .

==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.''

===Grammar and word order in sentences===
*[https://www.dutchgrammar.com/en/?n=WordOrder.00 https://www.dutchgrammar.com/en/?n=WordOrder.00] About word order in sentences. It's not just one page, keep clicking on next page in the bottom right to see more examples.
*[http://redekundig.nl/ http://redekundig.nl/] a tool to help identify the structure of a Dutch sentence. Very helpful if you're dealing with complex grammatical rules and need to understand the sentence you are reviewing.
* [https://urd2.let.rug.nl/~vannoord/bin/alpino https://urd2.let.rug.nl/~vannoord/bin/alpino] university hosted tool to identify structure of a Dutch sentence. It's the same tool as redekundig.nl but hosted elsewhere, and the interface is harder to comprehend. Would advise trying this in case redekundig.nl isn't giving you the information you need.
* [https://onzetaal.nl/taaladvies/signaalwoorden-lijst/ List of signal words], use these wherever possible, they help clarify your message and prevent ambiguity.
* Dutch article debunking myths about 'new grammer rules': https://vrttaal.net/nieuws/kranten-haal-het-nepnieuws-over-de-ans-van-jullie-site

===Style and tone===
* First follow any style guide you find here on this wiki for language and project you are working on
* If you are missing something, contact other translators
* If you search for style advise from other websites, avoid getting it from tech companies who make up their own version of Dutch language based on marketing rather than proper standard Dutch. Also avoid other wiki's which are often written by opinionated people who are not representative for the language. That doesn't mean you can't read them and learn from them, but take it with a grain of salt.

===Spelling===
*[https://taaladvies.net Taaladvies]
*[https://taal.vrt.be Taalnet]
*[https://onzetaal.nl OnzeTaal]

===Technical terminology===
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:
[https://docs.google.com/spreadsheets/d/1OPyeWDq2rtPf9fEpCLRpHl9Hn--OfFbWLbrGtZx3lYI/edit?usp=sharing Dutch Unified Localization Lab Glossary]. The document is maintained by Erin (a localization lab employee). If you wish to add comments, edits or suggest new entries, do so using the "Comment" feature in the spreadsheet.

==Language varieties==
Dutch language varieties do not have their own glossary, style guide or terminology. All of these languages varieties follow Dutch (nl). there is generally no use in setting up resources for nl_NL, nl_BE or any other nl_* region, project maintainers should simply set up nl.

===Dutch in Belgium / Flemish (nl_BE)===
Flemish people may live in a different geographical region but are in a language union with and are in the same language region as Dutch people, therefore there are usually no differences between nl_NL and nl_BE. Projects should be localized to standardized Dutch (nl)(Standaardnederlands / Algemeen Nederlands). In the rare case some translation isn't clear to Flemish speakers, they can request to phrase the translation differently, but at all times the translation should conform to standard Dutch.

There is a Wikipedia page on the differences between these language varieties, however some of the differences are being exaggerated: https://nl.wikipedia.org/wiki/Lijst_van_verschillen_tussen_het_Nederlands_in_Belgi%C3%AB,_Nederland_en_Suriname

===Other varieties===
Below you find a list of other language varieties along with their ISO 3166-1 code:
* nl_AW Dutch (Aruba)
* nl_BQ Dutch (Caribbean Netherlands (Bonaire, Saba, Sint Eustatius))
* nl_CW Dutch (Curaçao)
* nl_SR Dutch (Suriname)
* nl_SX Dutch (Sint Maarten)

==Similar languages==
If you want to localize a project to a language which has strong similarities to Dutch and if there already exist good quality translations to Dutch, than it is recommended to base your translations of Dutch rather than English or an other source language. This may make translations faster, but more importantly it also keeps the texts consistent, so that someone who lives just across the border, or someone who has family in the other region, doesn't see completely different texts for the same project. In Transifex there is an option to swap which language you are using as the source language for your translations; you will find it by clicking the setting icon in the top right of the translation interface. Any strings that have not yet been translated to Dutch will automatically still be shown as the original source language for the project (usually English).

===West Frisian (fy_NL)===
Frisian is a language of its own, but because most if Frisians actually live in the Netherlands and have Dutch as their first or second language, and because the Frisian localization community is very small, Frisian is merged with the Dutch localization community. Of course they have their own style, terminology and glossary but for most projects there are too few translators available to maintain those. Project maintainers should add Frisian (fy) to their resources to offer Frisians a chance to preserve their language and culture.

===Afrikaans (af)===
Afrikaans is a language on its own with strong similarities to Dutch. It is spoken in the southern regions of Africa and it has its own localization community unrelated to Dutch. Most Afrikaans speakers have English as their first or second language, so there usually aren't many translators who feel the need to localize a project to Afrikaans. Never the less Afrikaans has plenty of speakers who prefer Afrikaans over English, and project maintainers should add Afrikaans (af) to their resources.

Dutch

2021-05-05T11:39:20Z

Meteor0id: /* Language Resources */

__TOC__

==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 [https://internetfreedomfestival.org/ International Freedom Festival] domain and is subject to their [https://www.internetfreedomfestival.org/wiki/index.php/Code_of_Conduct Code of Conduct]. Be sure to read through the [https://www.internetfreedomfestival.org/wiki/index.php/Code_of_Conduct Code of Conduct] and then [mailto:info@localizationlab.org?subject=Mattermost%20Sign-up&body=Please%20send%20me%20a%20link%20to%20sign%20up%20for%20Mattermost. 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==
Ask yourself: "If my 65 year old mother read this (who has a total of 3 apps on her phone and uses only one of them on a weekly basis), would she understand this without anyone's help?". The goal is not to translate words, the goal is to make the text understandable to people who grew up in a different country.

===Signal Messenger===
''This Style guide is a result of reviewers communicating about inconsistencies and solutions to those. 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. We will try to make this style guide easier to read in the future.''

* The most important rule to always keep in question yourself who your audience will be and whether they will fully understand it. Yes, you are doing this work on behave of the Signal developers, but your audience are Signal users. Place yourself in the frame of mind of a Signal user who doesn't really know much about Signal and is trying to understand his options. Don't just translate literary, translate in such a way that it makes sense, is accurate, and is easy to read for the end user.
* 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. 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, meaning different words and/or a different structure of the sentence. An example: "Signal needs location services enabled to discover and connect with your old Android device." is localized as "Om je oude Android apparaat te kunnen detecteren en om er verbinding mee te maken is het nodig dat locatiebepaling op je apparaat is ingeschakeld.". Another example: don't write "Om het in te schakelen, tik op de schuifknop zodat hij blauw wordt." but instead write "Tik op de schuifknop zodat hij blauw wordt om meekijkpreventie in te schakelen."
* 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 punctuation, end the sentence with a period. If the description does not contain any punctuation, 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 Dutch people also get it wrong. [https://www.dutchgrammar.com/en/?n=WordOrder.00] 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. An example: Don't write "Deze personen kunnen door jou niet direct worden toegevoegd aan de groep." instead write "Deze personen kunnen door jou niet direct aan de groep worden toegevoegd.".
* 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 white space: 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 …
* Make sure the subject is repeated in every new sentence, do not refer back to a previous sentence. We do this to keep texts easy to read and understand. An example: do not write "Turing this on allows you to receive emails. They will contain information about your account." instead write "Turning this on allows you to receive emails. The emails you will receive contain information about your account.".
* Avoid anglicisms, our job is to localize the content so it can be understood by as many people as possible, that includes people who don't understand even the most common of English words.
* For units we follow the Si-standards. That means we translate 20MB as 20 MB with a white space. Kilobytes as kB. Note that Signal does not use KiB, MiB etc, because Signal is following the same units as the Android operating system. The same rule applies to other units such as 10s becoming 10 s. Abbreviations for minutes, months and weeks are not si units but we agreed to translate those as "min", "mnd" and "w". Capitalization matters.
* The text strings for the app store sometimes contain wordplay. If a good wordplay in Dutch can't be found, than rather leave the word joke out and just factually describe the change.
* Use pronoun + "wie" instead of "die" wherever possible. Read [https://taaladvies.net/taal/advies/vraag/1564 Taaladvies about wie/die] about where to use "wie" and where to use "die". This is a style choice we made to make complex sentences easier to comprehend.
* Use "van wie", "bij wie", "op wie" and "voor wie" instead of "waarvan", "waarmee", "waarop" and "waarvoor" wherever possible.
* For texts on buttons in Android and Desktop: use "Aan gesprek deelnemen", "Aan Signal doneren" and "Alice toevoegen". Do not use "Voeg Alice toe" or "Deelnemen aan gesprek" or "Doneren aan Signal". reason for this is optial readability. Also capitalize the first letter. on iOS we have not yet decided on the style, because that operating system often uses 'gebiedende wijs' rather than 'infinitief'.
* Try to stick to Dutch words, even if you see English words being used in other apps: "timer" becomes "tijdspanne", "admin" "beheerder", "checkbox" "selectievakje of aankruisvakje", "updaten" "bijwerken", "icon" "pictogram", "non-profit" "organisatie zonder winstoogmerk", "error" "fout", "database""databank" etc. You can find words like these listed in the Transifex Glossary for the Dutch Signal project.
* Beware of capitalization: use "QR-code" do not use "QR-Code" or "qr-code". "WiFi" is spelled different in Dutch: "wifi" all lowercase and without a dash. You can find words like these listed in the Transifex Glossary for the Dutch Signal project.
* Use [https://onzetaal.nl/taaladvies/signaalwoorden-lijst/ signal words] (words that indicate summation, contradiction etc.) wherever possible.
* Use formal verbs where their is no difference in meaning: use "je kunt" not "je kan". Howerver for "kun je" versus "kan je" there is a minor difference: "kan je" is more proposing while "kun je" is more forcefully suggestive. Therefore we use "kan je" instead of "kun je", and "zal je" instead of "zul je". [https://taalhelden.org/bericht/het-kan-je-kun-je https://taalhelden.org/bericht/het-kan-je-kun-je]
* Don't forget that although in English articles can be omitted, in Dutch it's not an accepted practice to omit the article. For example: "Playback time of audio attachment" should be localized as "Afspeellengte van HET audiobericht".
* Don't use possessive pronounce for things the user isn't possessing: Don't write "Open Signal-Desktop en gebruik de sneltoetsen om je tekstgrootte aan te passen.", instead write "Open Signal-Desktop en gebruik de sneltoetsen om de tekstgrootte aan te passen.". Users don't have font size, Signal has font size.
* We consistently use only the ‘rode werkwoordsvolgorde’, never the ‘groene werkwoordsvolgorde’. This means we never write "... vertrokken is." but instead always write "... is vertrokken.". For more information about verb order: [https://onzetaal.nl/taaladvies/rode-groene-volgorde/ https://onzetaal.nl/taaladvies/rode-groene-volgorde/]

Extra example:
* Don't localize "Other Signal users who are saved to your phone's contact list." as "Andere Signal-gebruikers die zijn opgeslagen in jouw telefoons contactenlijst." but instead localize it as "Andere Signal-gebruikers van wie het telefoonnummer voor komt in de systeemcontactenlijst van jouw telefoon."

===Other projects===
For other projects the style has not yet been written down, however some translators seem to hold on to [http://download.microsoft.com/download/4/7/e/47e135ad-15d7-4491-be78-369804f0d333/nld-nld-StyleGuide.pdf a style guide from Microsoft].

==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.
* ANY time you edit a translation on a project with multiple separate resources, make sure to open all the resources and check if the same string exists elsewhere to apply the exact same edit there. An example would be when you edit a string in the Android Signal messenger app, make sure to also check if the same string exists in the Desktop app, the iOS app, the website or the support center. It's not easy for other reviewers to spot the inconsistency later, so do this right away at the very moment you make an edit.
* Be extra careful with plurals in Transifex, it's easy to miss one of the plural forms when reviewing. You can check all plurals again by searching for pluralized:yes
* Found a spelling mistake, grammar mistake, word order mistake or some word which is better substituted with another word? Don't just correct it when you see it and move on, check all the strings on all the resources for the same mistake or imperfection and correct that mistake on all the strings where it occurs. The moment you noticed something is the only opportunity to come up with a consistent solution across all the strings.

==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 punctuation is accurate, the capitalization is accurate, there are no double white spaces, and no missing white spaces
* 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.
* Don't just look at untranslated string, some strings are automatically translated by Transifex but might still be wrong because the context requires a different translation. use source_updated_after:dd-mm-yyyy to find all the new strings. Also check for edits made by others, using translation_updated_after:dd-mm-yyyy .

==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.''

===Grammar and word order in sentences===
*[https://www.dutchgrammar.com/en/?n=WordOrder.00 https://www.dutchgrammar.com/en/?n=WordOrder.00] About word order in sentences. It's not just one page, keep clicking on next page in the bottom right to see more examples.
*[http://redekundig.nl/ http://redekundig.nl/] a tool to help identify the structure of a Dutch sentence. Very helpful if you're dealing with complex grammatical rules and need to understand the sentence you are reviewing.
* [https://urd2.let.rug.nl/~vannoord/bin/alpino https://urd2.let.rug.nl/~vannoord/bin/alpino] university hosted tool to identify structure of a Dutch sentence. It's the same tool as redekundig.nl but hosted elsewhere, and the interface is harder to comprehend. Would advise trying this in case redekundig.nl isn't giving you the information you need.
* [https://onzetaal.nl/taaladvies/signaalwoorden-lijst/ List of signal words], use these wherever possible, they help clarify your message and prevent ambiguity.
* Dutch article debunking myths about 'new grammer rules': https://vrttaal.net/nieuws/kranten-haal-het-nepnieuws-over-de-ans-van-jullie-site

===Style and tone===
* First follow any style guide you find here on this wiki for language and project you are working on
* If you are missing something, contact other translators
* If you search for style advise from other websites, avoid getting it from tech companies who make up their own version of Dutch language based on marketing rather than proper standard Dutch. Also avoid other wiki's which are often written by opinionated people who are not representative for the language. That doesn't mean you can't read them and learn from them, but take it with a grain of salt.

===Spelling===
*[https://taaladvies.net Taaladvies]
*[https://taal.vrt.be Taalnet]
*[https://onzetaal.nl OnzeTaal]

===Technical terminology===
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:
[https://docs.google.com/spreadsheets/d/1OPyeWDq2rtPf9fEpCLRpHl9Hn--OfFbWLbrGtZx3lYI/edit?usp=sharing Dutch Unified Localization Lab Glossary]. The document is maintained by Erin (a localization lab employee). If you wish to add comments, edits or suggest new entries, do so using the "Comment" feature in the spreadsheet.

==Language varieties==
Dutch language varieties do not have their own glossary, style guide or terminology. All of these languages varieties follow Dutch (nl). there is generally no use in setting up resources for nl_NL, nl_BE or any other nl_* region, project maintainers should simply set up nl.

===Dutch in Belgium / Flemish (nl_BE)===
Flemish people may live in a different geographical region but are in a language union with and are in the same language region as Dutch people, therefore there are usually no differences between nl_NL and nl_BE. Projects should be localized to standardized Dutch (nl)(Standaardnederlands / Algemeen Nederlands). In the rare case some translation isn't clear to Flemish speakers, they can request to phrase the translation differently, but at all times the translation should conform to standard Dutch.

There is a Wikipedia page on the differences between these language varieties, however some of the differences are being exaggerated: https://nl.wikipedia.org/wiki/Lijst_van_verschillen_tussen_het_Nederlands_in_Belgi%C3%AB,_Nederland_en_Suriname

===Other varieties===
Below you find a list of other language varieties along with their ISO 3166-1 code:
* nl_AW Dutch (Aruba)
* nl_BQ Dutch (Caribbean Netherlands (Bonaire, Saba, Sint Eustatius))
* nl_CW Dutch (Curaçao)
* nl_SR Dutch (Suriname)
* nl_SX Dutch (Sint Maarten)

==Similar languages==
If you want to localize a project to a language which has strong similarities to Dutch and if there already exist good quality translations to Dutch, than it is recommended to base your translations of Dutch rather than English or an other source language. This may make translations faster, but more importantly it also keeps the texts consistent, so that someone who lives just across the border, or someone who has family in the other region, doesn't see completely different texts for the same project. In Transifex there is an option to swap which language you are using as the source language for your translations; you will find it by clicking the setting icon in the top right of the translation interface. Any strings that have not yet been translated to Dutch will automatically still be shown as the original source language for the project (usually English).

===West Frisian (fy_NL)===
Frisian is a language of its own, but because most if Frisians actually live in the Netherlands and have Dutch as their first or second language, and because the Frisian localization community is very small, Frisian is merged with the Dutch localization community. Of course they have their own style, terminology and glossary but for most projects there are too few translators available to maintain those. Project maintainers should add Frisian (fy) to their resources to offer Frisians a chance to preserve their language and culture.

===Afrikaans (af)===
Afrikaans is a language on its own with strong similarities to Dutch. It is spoken in the southern regions of Africa and it has its own localization community unrelated to Dutch. Most Afrikaans speakers have English as their first or second language, so there usually aren't many translators who feel the need to localize a project to Afrikaans. Never the less Afrikaans has plenty of speakers who prefer Afrikaans over English, and project maintainers should add Afrikaans (af) to their resources.

Dutch

2021-04-15T21:51:57Z

Meteor0id: /* Dutch in Belgium / Flemish (nl_BE) */

__TOC__

==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 [https://internetfreedomfestival.org/ International Freedom Festival] domain and is subject to their [https://www.internetfreedomfestival.org/wiki/index.php/Code_of_Conduct Code of Conduct]. Be sure to read through the [https://www.internetfreedomfestival.org/wiki/index.php/Code_of_Conduct Code of Conduct] and then [mailto:info@localizationlab.org?subject=Mattermost%20Sign-up&body=Please%20send%20me%20a%20link%20to%20sign%20up%20for%20Mattermost. 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==
Ask yourself: "If my 65 year old mother read this (who has a total of 3 apps on her phone and uses only one of them on a weekly basis), would she understand this without anyone's help?". The goal is not to translate words, the goal is to make the text understandable to people who grew up in a different country.

===Signal Messenger===
''This Style guide is a result of reviewers communicating about inconsistencies and solutions to those. 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. We will try to make this style guide easier to read in the future.''

* The most important rule to always keep in question yourself who your audience will be and whether they will fully understand it. Yes, you are doing this work on behave of the Signal developers, but your audience are Signal users. Place yourself in the frame of mind of a Signal user who doesn't really know much about Signal and is trying to understand his options. Don't just translate literary, translate in such a way that it makes sense, is accurate, and is easy to read for the end user.
* 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. 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, meaning different words and/or a different structure of the sentence. An example: "Signal needs location services enabled to discover and connect with your old Android device." is localized as "Om je oude Android apparaat te kunnen detecteren en om er verbinding mee te maken is het nodig dat locatiebepaling op je apparaat is ingeschakeld.". Another example: don't write "Om het in te schakelen, tik op de schuifknop zodat hij blauw wordt." but instead write "Tik op de schuifknop zodat hij blauw wordt om meekijkpreventie in te schakelen."
* 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 punctuation, end the sentence with a period. If the description does not contain any punctuation, 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 Dutch people also get it wrong. [https://www.dutchgrammar.com/en/?n=WordOrder.00] 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. An example: Don't write "Deze personen kunnen door jou niet direct worden toegevoegd aan de groep." instead write "Deze personen kunnen door jou niet direct aan de groep worden toegevoegd.".
* 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 white space: 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 …
* Make sure the subject is repeated in every new sentence, do not refer back to a previous sentence. We do this to keep texts easy to read and understand. An example: do not write "Turing this on allows you to receive emails. They will contain information about your account." instead write "Turning this on allows you to receive emails. The emails you will receive contain information about your account.".
* Avoid anglicisms, our job is to localize the content so it can be understood by as many people as possible, that includes people who don't understand even the most common of English words.
* For units we follow the Si-standards. That means we translate 20MB as 20 MB with a white space. Kilobytes as kB. Note that Signal does not use KiB, MiB etc, because Signal is following the same units as the Android operating system. The same rule applies to other units such as 10s becoming 10 s. Abbreviations for minutes, months and weeks are not si units but we agreed to translate those as "min", "mnd" and "w". Capitalization matters.
* The text strings for the app store sometimes contain wordplay. If a good wordplay in Dutch can't be found, than rather leave the word joke out and just factually describe the change.
* Use pronoun + "wie" instead of "die" wherever possible. Read [https://taaladvies.net/taal/advies/vraag/1564 Taaladvies about wie/die] about where to use "wie" and where to use "die". This is a style choice we made to make complex sentences easier to comprehend.
* Use "van wie", "bij wie", "op wie" and "voor wie" instead of "waarvan", "waarmee", "waarop" and "waarvoor" wherever possible.
* For texts on buttons in Android and Desktop: use "Aan gesprek deelnemen", "Aan Signal doneren" and "Alice toevoegen". Do not use "Voeg Alice toe" or "Deelnemen aan gesprek" or "Doneren aan Signal". reason for this is optial readability. Also capitalize the first letter. on iOS we have not yet decided on the style, because that operating system often uses 'gebiedende wijs' rather than 'infinitief'.
* Try to stick to Dutch words, even if you see English words being used in other apps: "timer" becomes "tijdspanne", "admin" "beheerder", "checkbox" "selectievakje of aankruisvakje", "updaten" "bijwerken", "icon" "pictogram", "non-profit" "organisatie zonder winstoogmerk", "error" "fout", "database""databank" etc. You can find words like these listed in the Transifex Glossary for the Dutch Signal project.
* Beware of capitalization: use "QR-code" do not use "QR-Code" or "qr-code". "WiFi" is spelled different in Dutch: "wifi" all lowercase and without a dash. You can find words like these listed in the Transifex Glossary for the Dutch Signal project.
* Use [https://onzetaal.nl/taaladvies/signaalwoorden-lijst/ signal words] (words that indicate summation, contradiction etc.) wherever possible.
* Use formal verbs where their is no difference in meaning: use "je kunt" not "je kan". Howerver for "kun je" versus "kan je" there is a minor difference: "kan je" is more proposing while "kun je" is more forcefully suggestive. Therefore we use "kan je" instead of "kun je", and "zal je" instead of "zul je". [https://taalhelden.org/bericht/het-kan-je-kun-je https://taalhelden.org/bericht/het-kan-je-kun-je]
* Don't forget that although in English articles can be omitted, in Dutch it's not an accepted practice to omit the article. For example: "Playback time of audio attachment" should be localized as "Afspeellengte van HET audiobericht".
* Don't use possessive pronounce for things the user isn't possessing: Don't write "Open Signal-Desktop en gebruik de sneltoetsen om je tekstgrootte aan te passen.", instead write "Open Signal-Desktop en gebruik de sneltoetsen om de tekstgrootte aan te passen.". Users don't have font size, Signal has font size.
* We consistently use only the ‘rode werkwoordsvolgorde’, never the ‘groene werkwoordsvolgorde’. This means we never write "... vertrokken is." but instead always write "... is vertrokken.". For more information about verb order: [https://onzetaal.nl/taaladvies/rode-groene-volgorde/ https://onzetaal.nl/taaladvies/rode-groene-volgorde/]

Extra example:
* Don't localize "Other Signal users who are saved to your phone's contact list." as "Andere Signal-gebruikers die zijn opgeslagen in jouw telefoons contactenlijst." but instead localize it as "Andere Signal-gebruikers van wie het telefoonnummer voor komt in de systeemcontactenlijst van jouw telefoon."

===Other projects===
For other projects the style has not yet been written down, however some translators seem to hold on to [http://download.microsoft.com/download/4/7/e/47e135ad-15d7-4491-be78-369804f0d333/nld-nld-StyleGuide.pdf a style guide from Microsoft].

==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.
* ANY time you edit a translation on a project with multiple separate resources, make sure to open all the resources and check if the same string exists elsewhere to apply the exact same edit there. An example would be when you edit a string in the Android Signal messenger app, make sure to also check if the same string exists in the Desktop app, the iOS app, the website or the support center. It's not easy for other reviewers to spot the inconsistency later, so do this right away at the very moment you make an edit.
* Be extra careful with plurals in Transifex, it's easy to miss one of the plural forms when reviewing. You can check all plurals again by searching for pluralized:yes
* Found a spelling mistake, grammar mistake, word order mistake or some word which is better substituted with another word? Don't just correct it when you see it and move on, check all the strings on all the resources for the same mistake or imperfection and correct that mistake on all the strings where it occurs. The moment you noticed something is the only opportunity to come up with a consistent solution across all the strings.

==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 punctuation is accurate, the capitalization is accurate, there are no double white spaces, and no missing white spaces
* 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.
* Don't just look at untranslated string, some strings are automatically translated by Transifex but might still be wrong because the context requires a different translation. use source_updated_after:dd-mm-yyyy to find all the new strings. Also check for edits made by others, using translation_updated_after:dd-mm-yyyy .

==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.''

===Grammar and word order in sentences===
*[https://www.dutchgrammar.com/en/?n=WordOrder.00 https://www.dutchgrammar.com/en/?n=WordOrder.00] About word order in sentences. It's not just one page, keep clicking on next page in the bottom right to see more examples.
*[http://redekundig.nl/ http://redekundig.nl/] a tool to help identify the structure of a Dutch sentence. Very helpful if you're dealing with complex grammatical rules and need to understand the sentence you are reviewing.
* [https://urd2.let.rug.nl/~vannoord/bin/alpino https://urd2.let.rug.nl/~vannoord/bin/alpino] university hosted tool to identify structure of a Dutch sentence. It's the same tool as redekundig.nl but hosted elsewhere, and the interface is harder to comprehend. Would advise trying this in case redekundig.nl isn't giving you the information you need.
* [https://onzetaal.nl/taaladvies/signaalwoorden-lijst/ List of signal words], use these wherever possible, they help clarify your message and prevent ambiguity.

===Style and tone===
* First follow any style guide you find here on this wiki for language and project you are working on
* If you are missing something, contact other translators
* If you search for style advise from other websites, avoid getting it from tech companies who make up their own version of Dutch language based on marketing rather than proper standard Dutch. Also avoid other wiki's which are often written by opinionated people who are not representative for the language. That doesn't mean you can't read them and learn from them, but take it with a grain of salt.

===Spelling===
*[https://taaladvies.net Taaladvies]
*[https://taal.vrt.be Taalnet]
*[https://onzetaal.nl OnzeTaal]

===Technical terminology===
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:
[https://docs.google.com/spreadsheets/d/1OPyeWDq2rtPf9fEpCLRpHl9Hn--OfFbWLbrGtZx3lYI/edit?usp=sharing Dutch Unified Localization Lab Glossary]. The document is maintained by Erin (a localization lab employee). If you wish to add comments, edits or suggest new entries, do so using the "Comment" feature in the spreadsheet.

==Language varieties==
Dutch language varieties do not have their own glossary, style guide or terminology. All of these languages varieties follow Dutch (nl). there is generally no use in setting up resources for nl_NL, nl_BE or any other nl_* region, project maintainers should simply set up nl.

===Dutch in Belgium / Flemish (nl_BE)===
Flemish people may live in a different geographical region but are in a language union with and are in the same language region as Dutch people, therefore there are usually no differences between nl_NL and nl_BE. Projects should be localized to standardized Dutch (nl)(Standaardnederlands / Algemeen Nederlands). In the rare case some translation isn't clear to Flemish speakers, they can request to phrase the translation differently, but at all times the translation should conform to standard Dutch.

There is a Wikipedia page on the differences between these language varieties, however some of the differences are being exaggerated: https://nl.wikipedia.org/wiki/Lijst_van_verschillen_tussen_het_Nederlands_in_Belgi%C3%AB,_Nederland_en_Suriname

===Other varieties===
Below you find a list of other language varieties along with their ISO 3166-1 code:
* nl_AW Dutch (Aruba)
* nl_BQ Dutch (Caribbean Netherlands (Bonaire, Saba, Sint Eustatius))
* nl_CW Dutch (Curaçao)
* nl_SR Dutch (Suriname)
* nl_SX Dutch (Sint Maarten)

==Similar languages==
If you want to localize a project to a language which has strong similarities to Dutch and if there already exist good quality translations to Dutch, than it is recommended to base your translations of Dutch rather than English or an other source language. This may make translations faster, but more importantly it also keeps the texts consistent, so that someone who lives just across the border, or someone who has family in the other region, doesn't see completely different texts for the same project. In Transifex there is an option to swap which language you are using as the source language for your translations; you will find it by clicking the setting icon in the top right of the translation interface. Any strings that have not yet been translated to Dutch will automatically still be shown as the original source language for the project (usually English).

===West Frisian (fy_NL)===
Frisian is a language of its own, but because most if Frisians actually live in the Netherlands and have Dutch as their first or second language, and because the Frisian localization community is very small, Frisian is merged with the Dutch localization community. Of course they have their own style, terminology and glossary but for most projects there are too few translators available to maintain those. Project maintainers should add Frisian (fy) to their resources to offer Frisians a chance to preserve their language and culture.

===Afrikaans (af)===
Afrikaans is a language on its own with strong similarities to Dutch. It is spoken in the southern regions of Africa and it has its own localization community unrelated to Dutch. Most Afrikaans speakers have English as their first or second language, so there usually aren't many translators who feel the need to localize a project to Afrikaans. Never the less Afrikaans has plenty of speakers who prefer Afrikaans over English, and project maintainers should add Afrikaans (af) to their resources.

Portuguese (Brazilian)

2021-04-15T18:25:25Z

Meteor0id: add unified Portuguese resources

Afrikaans

2021-04-15T18:19:36Z

Meteor0id:

Dutch

2021-04-15T18:17:45Z

Meteor0id: /* Afrikaans (af) */

__TOC__

==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 [https://internetfreedomfestival.org/ International Freedom Festival] domain and is subject to their [https://www.internetfreedomfestival.org/wiki/index.php/Code_of_Conduct Code of Conduct]. Be sure to read through the [https://www.internetfreedomfestival.org/wiki/index.php/Code_of_Conduct Code of Conduct] and then [mailto:info@localizationlab.org?subject=Mattermost%20Sign-up&body=Please%20send%20me%20a%20link%20to%20sign%20up%20for%20Mattermost. 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==
Ask yourself: "If my 65 year old mother read this (who has a total of 3 apps on her phone and uses only one of them on a weekly basis), would she understand this without anyone's help?". The goal is not to translate words, the goal is to make the text understandable to people who grew up in a different country.

===Signal Messenger===
''This Style guide is a result of reviewers communicating about inconsistencies and solutions to those. 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. We will try to make this style guide easier to read in the future.''

* The most important rule to always keep in question yourself who your audience will be and whether they will fully understand it. Yes, you are doing this work on behave of the Signal developers, but your audience are Signal users. Place yourself in the frame of mind of a Signal user who doesn't really know much about Signal and is trying to understand his options. Don't just translate literary, translate in such a way that it makes sense, is accurate, and is easy to read for the end user.
* 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. 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, meaning different words and/or a different structure of the sentence. An example: "Signal needs location services enabled to discover and connect with your old Android device." is localized as "Om je oude Android apparaat te kunnen detecteren en om er verbinding mee te maken is het nodig dat locatiebepaling op je apparaat is ingeschakeld.". Another example: don't write "Om het in te schakelen, tik op de schuifknop zodat hij blauw wordt." but instead write "Tik op de schuifknop zodat hij blauw wordt om meekijkpreventie in te schakelen."
* 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 punctuation, end the sentence with a period. If the description does not contain any punctuation, 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 Dutch people also get it wrong. [https://www.dutchgrammar.com/en/?n=WordOrder.00] 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. An example: Don't write "Deze personen kunnen door jou niet direct worden toegevoegd aan de groep." instead write "Deze personen kunnen door jou niet direct aan de groep worden toegevoegd.".
* 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 white space: 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 …
* Make sure the subject is repeated in every new sentence, do not refer back to a previous sentence. We do this to keep texts easy to read and understand. An example: do not write "Turing this on allows you to receive emails. They will contain information about your account." instead write "Turning this on allows you to receive emails. The emails you will receive contain information about your account.".
* Avoid anglicisms, our job is to localize the content so it can be understood by as many people as possible, that includes people who don't understand even the most common of English words.
* For units we follow the Si-standards. That means we translate 20MB as 20 MB with a white space. Kilobytes as kB. Note that Signal does not use KiB, MiB etc, because Signal is following the same units as the Android operating system. The same rule applies to other units such as 10s becoming 10 s. Abbreviations for minutes, months and weeks are not si units but we agreed to translate those as "min", "mnd" and "w". Capitalization matters.
* The text strings for the app store sometimes contain wordplay. If a good wordplay in Dutch can't be found, than rather leave the word joke out and just factually describe the change.
* Use pronoun + "wie" instead of "die" wherever possible. Read [https://taaladvies.net/taal/advies/vraag/1564 Taaladvies about wie/die] about where to use "wie" and where to use "die". This is a style choice we made to make complex sentences easier to comprehend.
* Use "van wie", "bij wie", "op wie" and "voor wie" instead of "waarvan", "waarmee", "waarop" and "waarvoor" wherever possible.
* For texts on buttons in Android and Desktop: use "Aan gesprek deelnemen", "Aan Signal doneren" and "Alice toevoegen". Do not use "Voeg Alice toe" or "Deelnemen aan gesprek" or "Doneren aan Signal". reason for this is optial readability. Also capitalize the first letter. on iOS we have not yet decided on the style, because that operating system often uses 'gebiedende wijs' rather than 'infinitief'.
* Try to stick to Dutch words, even if you see English words being used in other apps: "timer" becomes "tijdspanne", "admin" "beheerder", "checkbox" "selectievakje of aankruisvakje", "updaten" "bijwerken", "icon" "pictogram", "non-profit" "organisatie zonder winstoogmerk", "error" "fout", "database""databank" etc. You can find words like these listed in the Transifex Glossary for the Dutch Signal project.
* Beware of capitalization: use "QR-code" do not use "QR-Code" or "qr-code". "WiFi" is spelled different in Dutch: "wifi" all lowercase and without a dash. You can find words like these listed in the Transifex Glossary for the Dutch Signal project.
* Use [https://onzetaal.nl/taaladvies/signaalwoorden-lijst/ signal words] (words that indicate summation, contradiction etc.) wherever possible.
* Use formal verbs where their is no difference in meaning: use "je kunt" not "je kan". Howerver for "kun je" versus "kan je" there is a minor difference: "kan je" is more proposing while "kun je" is more forcefully suggestive. Therefore we use "kan je" instead of "kun je", and "zal je" instead of "zul je". [https://taalhelden.org/bericht/het-kan-je-kun-je https://taalhelden.org/bericht/het-kan-je-kun-je]
* Don't forget that although in English articles can be omitted, in Dutch it's not an accepted practice to omit the article. For example: "Playback time of audio attachment" should be localized as "Afspeellengte van HET audiobericht".
* Don't use possessive pronounce for things the user isn't possessing: Don't write "Open Signal-Desktop en gebruik de sneltoetsen om je tekstgrootte aan te passen.", instead write "Open Signal-Desktop en gebruik de sneltoetsen om de tekstgrootte aan te passen.". Users don't have font size, Signal has font size.
* We consistently use only the ‘rode werkwoordsvolgorde’, never the ‘groene werkwoordsvolgorde’. This means we never write "... vertrokken is." but instead always write "... is vertrokken.". For more information about verb order: [https://onzetaal.nl/taaladvies/rode-groene-volgorde/ https://onzetaal.nl/taaladvies/rode-groene-volgorde/]

Extra example:
* Don't localize "Other Signal users who are saved to your phone's contact list." as "Andere Signal-gebruikers die zijn opgeslagen in jouw telefoons contactenlijst." but instead localize it as "Andere Signal-gebruikers van wie het telefoonnummer voor komt in de systeemcontactenlijst van jouw telefoon."

===Other projects===
For other projects the style has not yet been written down, however some translators seem to hold on to [http://download.microsoft.com/download/4/7/e/47e135ad-15d7-4491-be78-369804f0d333/nld-nld-StyleGuide.pdf a style guide from Microsoft].

==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.
* ANY time you edit a translation on a project with multiple separate resources, make sure to open all the resources and check if the same string exists elsewhere to apply the exact same edit there. An example would be when you edit a string in the Android Signal messenger app, make sure to also check if the same string exists in the Desktop app, the iOS app, the website or the support center. It's not easy for other reviewers to spot the inconsistency later, so do this right away at the very moment you make an edit.
* Be extra careful with plurals in Transifex, it's easy to miss one of the plural forms when reviewing. You can check all plurals again by searching for pluralized:yes
* Found a spelling mistake, grammar mistake, word order mistake or some word which is better substituted with another word? Don't just correct it when you see it and move on, check all the strings on all the resources for the same mistake or imperfection and correct that mistake on all the strings where it occurs. The moment you noticed something is the only opportunity to come up with a consistent solution across all the strings.

==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 punctuation is accurate, the capitalization is accurate, there are no double white spaces, and no missing white spaces
* 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.
* Don't just look at untranslated string, some strings are automatically translated by Transifex but might still be wrong because the context requires a different translation. use source_updated_after:dd-mm-yyyy to find all the new strings. Also check for edits made by others, using translation_updated_after:dd-mm-yyyy .

==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.''

===Grammar and word order in sentences===
*[https://www.dutchgrammar.com/en/?n=WordOrder.00 https://www.dutchgrammar.com/en/?n=WordOrder.00] About word order in sentences. It's not just one page, keep clicking on next page in the bottom right to see more examples.
*[http://redekundig.nl/ http://redekundig.nl/] a tool to help identify the structure of a Dutch sentence. Very helpful if you're dealing with complex grammatical rules and need to understand the sentence you are reviewing.
* [https://urd2.let.rug.nl/~vannoord/bin/alpino https://urd2.let.rug.nl/~vannoord/bin/alpino] university hosted tool to identify structure of a Dutch sentence. It's the same tool as redekundig.nl but hosted elsewhere, and the interface is harder to comprehend. Would advise trying this in case redekundig.nl isn't giving you the information you need.
* [https://onzetaal.nl/taaladvies/signaalwoorden-lijst/ List of signal words], use these wherever possible, they help clarify your message and prevent ambiguity.

===Style and tone===
* First follow any style guide you find here on this wiki for language and project you are working on
* If you are missing something, contact other translators
* If you search for style advise from other websites, avoid getting it from tech companies who make up their own version of Dutch language based on marketing rather than proper standard Dutch. Also avoid other wiki's which are often written by opinionated people who are not representative for the language. That doesn't mean you can't read them and learn from them, but take it with a grain of salt.

===Spelling===
*[https://taaladvies.net Taaladvies]
*[https://taal.vrt.be Taalnet]
*[https://onzetaal.nl OnzeTaal]

===Technical terminology===
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:
[https://docs.google.com/spreadsheets/d/1OPyeWDq2rtPf9fEpCLRpHl9Hn--OfFbWLbrGtZx3lYI/edit?usp=sharing Dutch Unified Localization Lab Glossary]. The document is maintained by Erin (a localization lab employee). If you wish to add comments, edits or suggest new entries, do so using the "Comment" feature in the spreadsheet.

==Language varieties==
Dutch language varieties do not have their own glossary, style guide or terminology. All of these languages varieties follow Dutch (nl). there is generally no use in setting up resources for nl_NL, nl_BE or any other nl_* region, project maintainers should simply set up nl.

===Dutch in Belgium / Flemish (nl_BE)===
Flemish people may live in a different geographical region but are in a language union with and are in the same language region as Dutch people, therefore there are usually no differences between nl_NL and nl_BE. Projects should simply be localized to Dutch (nl). In the rare case some translation isn't clear to Flemish speakers, they can request to phrase the translation differently, but at all times the rules of standard Dutch should be followed.

===Other varieties===
Below you find a list of other language varieties along with their ISO 3166-1 code:
* nl_AW Dutch (Aruba)
* nl_BQ Dutch (Caribbean Netherlands (Bonaire, Saba, Sint Eustatius))
* nl_CW Dutch (Curaçao)
* nl_SR Dutch (Suriname)
* nl_SX Dutch (Sint Maarten)

==Similar languages==
If you want to localize a project to a language which has strong similarities to Dutch and if there already exist good quality translations to Dutch, than it is recommended to base your translations of Dutch rather than English or an other source language. This may make translations faster, but more importantly it also keeps the texts consistent, so that someone who lives just across the border, or someone who has family in the other region, doesn't see completely different texts for the same project. In Transifex there is an option to swap which language you are using as the source language for your translations; you will find it by clicking the setting icon in the top right of the translation interface. Any strings that have not yet been translated to Dutch will automatically still be shown as the original source language for the project (usually English).

===West Frisian (fy_NL)===
Frisian is a language of its own, but because most if Frisians actually live in the Netherlands and have Dutch as their first or second language, and because the Frisian localization community is very small, Frisian is merged with the Dutch localization community. Of course they have their own style, terminology and glossary but for most projects there are too few translators available to maintain those. Project maintainers should add Frisian (fy) to their resources to offer Frisians a chance to preserve their language and culture.

===Afrikaans (af)===
Afrikaans is a language on its own with strong similarities to Dutch. It is spoken in the southern regions of Africa and it has its own localization community unrelated to Dutch. Most Afrikaans speakers have English as their first or second language, so there usually aren't many translators who feel the need to localize a project to Afrikaans. Never the less Afrikaans has plenty of speakers who prefer Afrikaans over English, and project maintainers should add Afrikaans (af) to their resources.

Dutch

2021-04-15T18:11:40Z

Meteor0id: /* West Frisian (fy_NL) */

__TOC__

==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 [https://internetfreedomfestival.org/ International Freedom Festival] domain and is subject to their [https://www.internetfreedomfestival.org/wiki/index.php/Code_of_Conduct Code of Conduct]. Be sure to read through the [https://www.internetfreedomfestival.org/wiki/index.php/Code_of_Conduct Code of Conduct] and then [mailto:info@localizationlab.org?subject=Mattermost%20Sign-up&body=Please%20send%20me%20a%20link%20to%20sign%20up%20for%20Mattermost. 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==
Ask yourself: "If my 65 year old mother read this (who has a total of 3 apps on her phone and uses only one of them on a weekly basis), would she understand this without anyone's help?". The goal is not to translate words, the goal is to make the text understandable to people who grew up in a different country.

===Signal Messenger===
''This Style guide is a result of reviewers communicating about inconsistencies and solutions to those. 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. We will try to make this style guide easier to read in the future.''

* The most important rule to always keep in question yourself who your audience will be and whether they will fully understand it. Yes, you are doing this work on behave of the Signal developers, but your audience are Signal users. Place yourself in the frame of mind of a Signal user who doesn't really know much about Signal and is trying to understand his options. Don't just translate literary, translate in such a way that it makes sense, is accurate, and is easy to read for the end user.
* 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. 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, meaning different words and/or a different structure of the sentence. An example: "Signal needs location services enabled to discover and connect with your old Android device." is localized as "Om je oude Android apparaat te kunnen detecteren en om er verbinding mee te maken is het nodig dat locatiebepaling op je apparaat is ingeschakeld.". Another example: don't write "Om het in te schakelen, tik op de schuifknop zodat hij blauw wordt." but instead write "Tik op de schuifknop zodat hij blauw wordt om meekijkpreventie in te schakelen."
* 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 punctuation, end the sentence with a period. If the description does not contain any punctuation, 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 Dutch people also get it wrong. [https://www.dutchgrammar.com/en/?n=WordOrder.00] 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. An example: Don't write "Deze personen kunnen door jou niet direct worden toegevoegd aan de groep." instead write "Deze personen kunnen door jou niet direct aan de groep worden toegevoegd.".
* 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 white space: 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 …
* Make sure the subject is repeated in every new sentence, do not refer back to a previous sentence. We do this to keep texts easy to read and understand. An example: do not write "Turing this on allows you to receive emails. They will contain information about your account." instead write "Turning this on allows you to receive emails. The emails you will receive contain information about your account.".
* Avoid anglicisms, our job is to localize the content so it can be understood by as many people as possible, that includes people who don't understand even the most common of English words.
* For units we follow the Si-standards. That means we translate 20MB as 20 MB with a white space. Kilobytes as kB. Note that Signal does not use KiB, MiB etc, because Signal is following the same units as the Android operating system. The same rule applies to other units such as 10s becoming 10 s. Abbreviations for minutes, months and weeks are not si units but we agreed to translate those as "min", "mnd" and "w". Capitalization matters.
* The text strings for the app store sometimes contain wordplay. If a good wordplay in Dutch can't be found, than rather leave the word joke out and just factually describe the change.
* Use pronoun + "wie" instead of "die" wherever possible. Read [https://taaladvies.net/taal/advies/vraag/1564 Taaladvies about wie/die] about where to use "wie" and where to use "die". This is a style choice we made to make complex sentences easier to comprehend.
* Use "van wie", "bij wie", "op wie" and "voor wie" instead of "waarvan", "waarmee", "waarop" and "waarvoor" wherever possible.
* For texts on buttons in Android and Desktop: use "Aan gesprek deelnemen", "Aan Signal doneren" and "Alice toevoegen". Do not use "Voeg Alice toe" or "Deelnemen aan gesprek" or "Doneren aan Signal". reason for this is optial readability. Also capitalize the first letter. on iOS we have not yet decided on the style, because that operating system often uses 'gebiedende wijs' rather than 'infinitief'.
* Try to stick to Dutch words, even if you see English words being used in other apps: "timer" becomes "tijdspanne", "admin" "beheerder", "checkbox" "selectievakje of aankruisvakje", "updaten" "bijwerken", "icon" "pictogram", "non-profit" "organisatie zonder winstoogmerk", "error" "fout", "database""databank" etc. You can find words like these listed in the Transifex Glossary for the Dutch Signal project.
* Beware of capitalization: use "QR-code" do not use "QR-Code" or "qr-code". "WiFi" is spelled different in Dutch: "wifi" all lowercase and without a dash. You can find words like these listed in the Transifex Glossary for the Dutch Signal project.
* Use [https://onzetaal.nl/taaladvies/signaalwoorden-lijst/ signal words] (words that indicate summation, contradiction etc.) wherever possible.
* Use formal verbs where their is no difference in meaning: use "je kunt" not "je kan". Howerver for "kun je" versus "kan je" there is a minor difference: "kan je" is more proposing while "kun je" is more forcefully suggestive. Therefore we use "kan je" instead of "kun je", and "zal je" instead of "zul je". [https://taalhelden.org/bericht/het-kan-je-kun-je https://taalhelden.org/bericht/het-kan-je-kun-je]
* Don't forget that although in English articles can be omitted, in Dutch it's not an accepted practice to omit the article. For example: "Playback time of audio attachment" should be localized as "Afspeellengte van HET audiobericht".
* Don't use possessive pronounce for things the user isn't possessing: Don't write "Open Signal-Desktop en gebruik de sneltoetsen om je tekstgrootte aan te passen.", instead write "Open Signal-Desktop en gebruik de sneltoetsen om de tekstgrootte aan te passen.". Users don't have font size, Signal has font size.
* We consistently use only the ‘rode werkwoordsvolgorde’, never the ‘groene werkwoordsvolgorde’. This means we never write "... vertrokken is." but instead always write "... is vertrokken.". For more information about verb order: [https://onzetaal.nl/taaladvies/rode-groene-volgorde/ https://onzetaal.nl/taaladvies/rode-groene-volgorde/]

Extra example:
* Don't localize "Other Signal users who are saved to your phone's contact list." as "Andere Signal-gebruikers die zijn opgeslagen in jouw telefoons contactenlijst." but instead localize it as "Andere Signal-gebruikers van wie het telefoonnummer voor komt in de systeemcontactenlijst van jouw telefoon."

===Other projects===
For other projects the style has not yet been written down, however some translators seem to hold on to [http://download.microsoft.com/download/4/7/e/47e135ad-15d7-4491-be78-369804f0d333/nld-nld-StyleGuide.pdf a style guide from Microsoft].

==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.
* ANY time you edit a translation on a project with multiple separate resources, make sure to open all the resources and check if the same string exists elsewhere to apply the exact same edit there. An example would be when you edit a string in the Android Signal messenger app, make sure to also check if the same string exists in the Desktop app, the iOS app, the website or the support center. It's not easy for other reviewers to spot the inconsistency later, so do this right away at the very moment you make an edit.
* Be extra careful with plurals in Transifex, it's easy to miss one of the plural forms when reviewing. You can check all plurals again by searching for pluralized:yes
* Found a spelling mistake, grammar mistake, word order mistake or some word which is better substituted with another word? Don't just correct it when you see it and move on, check all the strings on all the resources for the same mistake or imperfection and correct that mistake on all the strings where it occurs. The moment you noticed something is the only opportunity to come up with a consistent solution across all the strings.

==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 punctuation is accurate, the capitalization is accurate, there are no double white spaces, and no missing white spaces
* 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.
* Don't just look at untranslated string, some strings are automatically translated by Transifex but might still be wrong because the context requires a different translation. use source_updated_after:dd-mm-yyyy to find all the new strings. Also check for edits made by others, using translation_updated_after:dd-mm-yyyy .

==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.''

===Grammar and word order in sentences===
*[https://www.dutchgrammar.com/en/?n=WordOrder.00 https://www.dutchgrammar.com/en/?n=WordOrder.00] About word order in sentences. It's not just one page, keep clicking on next page in the bottom right to see more examples.
*[http://redekundig.nl/ http://redekundig.nl/] a tool to help identify the structure of a Dutch sentence. Very helpful if you're dealing with complex grammatical rules and need to understand the sentence you are reviewing.
* [https://urd2.let.rug.nl/~vannoord/bin/alpino https://urd2.let.rug.nl/~vannoord/bin/alpino] university hosted tool to identify structure of a Dutch sentence. It's the same tool as redekundig.nl but hosted elsewhere, and the interface is harder to comprehend. Would advise trying this in case redekundig.nl isn't giving you the information you need.
* [https://onzetaal.nl/taaladvies/signaalwoorden-lijst/ List of signal words], use these wherever possible, they help clarify your message and prevent ambiguity.

===Style and tone===
* First follow any style guide you find here on this wiki for language and project you are working on
* If you are missing something, contact other translators
* If you search for style advise from other websites, avoid getting it from tech companies who make up their own version of Dutch language based on marketing rather than proper standard Dutch. Also avoid other wiki's which are often written by opinionated people who are not representative for the language. That doesn't mean you can't read them and learn from them, but take it with a grain of salt.

===Spelling===
*[https://taaladvies.net Taaladvies]
*[https://taal.vrt.be Taalnet]
*[https://onzetaal.nl OnzeTaal]

===Technical terminology===
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:
[https://docs.google.com/spreadsheets/d/1OPyeWDq2rtPf9fEpCLRpHl9Hn--OfFbWLbrGtZx3lYI/edit?usp=sharing Dutch Unified Localization Lab Glossary]. The document is maintained by Erin (a localization lab employee). If you wish to add comments, edits or suggest new entries, do so using the "Comment" feature in the spreadsheet.

==Language varieties==
Dutch language varieties do not have their own glossary, style guide or terminology. All of these languages varieties follow Dutch (nl). there is generally no use in setting up resources for nl_NL, nl_BE or any other nl_* region, project maintainers should simply set up nl.

===Dutch in Belgium / Flemish (nl_BE)===
Flemish people may live in a different geographical region but are in a language union with and are in the same language region as Dutch people, therefore there are usually no differences between nl_NL and nl_BE. Projects should simply be localized to Dutch (nl). In the rare case some translation isn't clear to Flemish speakers, they can request to phrase the translation differently, but at all times the rules of standard Dutch should be followed.

===Other varieties===
Below you find a list of other language varieties along with their ISO 3166-1 code:
* nl_AW Dutch (Aruba)
* nl_BQ Dutch (Caribbean Netherlands (Bonaire, Saba, Sint Eustatius))
* nl_CW Dutch (Curaçao)
* nl_SR Dutch (Suriname)
* nl_SX Dutch (Sint Maarten)

==Similar languages==
If you want to localize a project to a language which has strong similarities to Dutch and if there already exist good quality translations to Dutch, than it is recommended to base your translations of Dutch rather than English or an other source language. This may make translations faster, but more importantly it also keeps the texts consistent, so that someone who lives just across the border, or someone who has family in the other region, doesn't see completely different texts for the same project. In Transifex there is an option to swap which language you are using as the source language for your translations; you will find it by clicking the setting icon in the top right of the translation interface. Any strings that have not yet been translated to Dutch will automatically still be shown as the original source language for the project (usually English).

===West Frisian (fy_NL)===
Frisian is a language of its own, but because most if Frisians actually live in the Netherlands and have Dutch as their first or second language, and because the Frisian localization community is very small, Frisian is merged with the Dutch localization community. Of course they have their own style, terminology and glossary but for most projects there are too few translators available to maintain those. Project maintainers should add Frisian (fy) to their resources to offer Frisians a chance to preserve their language and culture.

===Afrikaans (af)===
Afrikaans is a language on its own and because it is spoken in a different region and has plenty of speakers, it has its own localization community.

Dutch

2021-04-15T18:07:39Z

Meteor0id: changing topic order

__TOC__

==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 [https://internetfreedomfestival.org/ International Freedom Festival] domain and is subject to their [https://www.internetfreedomfestival.org/wiki/index.php/Code_of_Conduct Code of Conduct]. Be sure to read through the [https://www.internetfreedomfestival.org/wiki/index.php/Code_of_Conduct Code of Conduct] and then [mailto:info@localizationlab.org?subject=Mattermost%20Sign-up&body=Please%20send%20me%20a%20link%20to%20sign%20up%20for%20Mattermost. 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==
Ask yourself: "If my 65 year old mother read this (who has a total of 3 apps on her phone and uses only one of them on a weekly basis), would she understand this without anyone's help?". The goal is not to translate words, the goal is to make the text understandable to people who grew up in a different country.

===Signal Messenger===
''This Style guide is a result of reviewers communicating about inconsistencies and solutions to those. 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. We will try to make this style guide easier to read in the future.''

* The most important rule to always keep in question yourself who your audience will be and whether they will fully understand it. Yes, you are doing this work on behave of the Signal developers, but your audience are Signal users. Place yourself in the frame of mind of a Signal user who doesn't really know much about Signal and is trying to understand his options. Don't just translate literary, translate in such a way that it makes sense, is accurate, and is easy to read for the end user.
* 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. 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, meaning different words and/or a different structure of the sentence. An example: "Signal needs location services enabled to discover and connect with your old Android device." is localized as "Om je oude Android apparaat te kunnen detecteren en om er verbinding mee te maken is het nodig dat locatiebepaling op je apparaat is ingeschakeld.". Another example: don't write "Om het in te schakelen, tik op de schuifknop zodat hij blauw wordt." but instead write "Tik op de schuifknop zodat hij blauw wordt om meekijkpreventie in te schakelen."
* 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 punctuation, end the sentence with a period. If the description does not contain any punctuation, 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 Dutch people also get it wrong. [https://www.dutchgrammar.com/en/?n=WordOrder.00] 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. An example: Don't write "Deze personen kunnen door jou niet direct worden toegevoegd aan de groep." instead write "Deze personen kunnen door jou niet direct aan de groep worden toegevoegd.".
* 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 white space: 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 …
* Make sure the subject is repeated in every new sentence, do not refer back to a previous sentence. We do this to keep texts easy to read and understand. An example: do not write "Turing this on allows you to receive emails. They will contain information about your account." instead write "Turning this on allows you to receive emails. The emails you will receive contain information about your account.".
* Avoid anglicisms, our job is to localize the content so it can be understood by as many people as possible, that includes people who don't understand even the most common of English words.
* For units we follow the Si-standards. That means we translate 20MB as 20 MB with a white space. Kilobytes as kB. Note that Signal does not use KiB, MiB etc, because Signal is following the same units as the Android operating system. The same rule applies to other units such as 10s becoming 10 s. Abbreviations for minutes, months and weeks are not si units but we agreed to translate those as "min", "mnd" and "w". Capitalization matters.
* The text strings for the app store sometimes contain wordplay. If a good wordplay in Dutch can't be found, than rather leave the word joke out and just factually describe the change.
* Use pronoun + "wie" instead of "die" wherever possible. Read [https://taaladvies.net/taal/advies/vraag/1564 Taaladvies about wie/die] about where to use "wie" and where to use "die". This is a style choice we made to make complex sentences easier to comprehend.
* Use "van wie", "bij wie", "op wie" and "voor wie" instead of "waarvan", "waarmee", "waarop" and "waarvoor" wherever possible.
* For texts on buttons in Android and Desktop: use "Aan gesprek deelnemen", "Aan Signal doneren" and "Alice toevoegen". Do not use "Voeg Alice toe" or "Deelnemen aan gesprek" or "Doneren aan Signal". reason for this is optial readability. Also capitalize the first letter. on iOS we have not yet decided on the style, because that operating system often uses 'gebiedende wijs' rather than 'infinitief'.
* Try to stick to Dutch words, even if you see English words being used in other apps: "timer" becomes "tijdspanne", "admin" "beheerder", "checkbox" "selectievakje of aankruisvakje", "updaten" "bijwerken", "icon" "pictogram", "non-profit" "organisatie zonder winstoogmerk", "error" "fout", "database""databank" etc. You can find words like these listed in the Transifex Glossary for the Dutch Signal project.
* Beware of capitalization: use "QR-code" do not use "QR-Code" or "qr-code". "WiFi" is spelled different in Dutch: "wifi" all lowercase and without a dash. You can find words like these listed in the Transifex Glossary for the Dutch Signal project.
* Use [https://onzetaal.nl/taaladvies/signaalwoorden-lijst/ signal words] (words that indicate summation, contradiction etc.) wherever possible.
* Use formal verbs where their is no difference in meaning: use "je kunt" not "je kan". Howerver for "kun je" versus "kan je" there is a minor difference: "kan je" is more proposing while "kun je" is more forcefully suggestive. Therefore we use "kan je" instead of "kun je", and "zal je" instead of "zul je". [https://taalhelden.org/bericht/het-kan-je-kun-je https://taalhelden.org/bericht/het-kan-je-kun-je]
* Don't forget that although in English articles can be omitted, in Dutch it's not an accepted practice to omit the article. For example: "Playback time of audio attachment" should be localized as "Afspeellengte van HET audiobericht".
* Don't use possessive pronounce for things the user isn't possessing: Don't write "Open Signal-Desktop en gebruik de sneltoetsen om je tekstgrootte aan te passen.", instead write "Open Signal-Desktop en gebruik de sneltoetsen om de tekstgrootte aan te passen.". Users don't have font size, Signal has font size.
* We consistently use only the ‘rode werkwoordsvolgorde’, never the ‘groene werkwoordsvolgorde’. This means we never write "... vertrokken is." but instead always write "... is vertrokken.". For more information about verb order: [https://onzetaal.nl/taaladvies/rode-groene-volgorde/ https://onzetaal.nl/taaladvies/rode-groene-volgorde/]

Extra example:
* Don't localize "Other Signal users who are saved to your phone's contact list." as "Andere Signal-gebruikers die zijn opgeslagen in jouw telefoons contactenlijst." but instead localize it as "Andere Signal-gebruikers van wie het telefoonnummer voor komt in de systeemcontactenlijst van jouw telefoon."

===Other projects===
For other projects the style has not yet been written down, however some translators seem to hold on to [http://download.microsoft.com/download/4/7/e/47e135ad-15d7-4491-be78-369804f0d333/nld-nld-StyleGuide.pdf a style guide from Microsoft].

==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.
* ANY time you edit a translation on a project with multiple separate resources, make sure to open all the resources and check if the same string exists elsewhere to apply the exact same edit there. An example would be when you edit a string in the Android Signal messenger app, make sure to also check if the same string exists in the Desktop app, the iOS app, the website or the support center. It's not easy for other reviewers to spot the inconsistency later, so do this right away at the very moment you make an edit.
* Be extra careful with plurals in Transifex, it's easy to miss one of the plural forms when reviewing. You can check all plurals again by searching for pluralized:yes
* Found a spelling mistake, grammar mistake, word order mistake or some word which is better substituted with another word? Don't just correct it when you see it and move on, check all the strings on all the resources for the same mistake or imperfection and correct that mistake on all the strings where it occurs. The moment you noticed something is the only opportunity to come up with a consistent solution across all the strings.

==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 punctuation is accurate, the capitalization is accurate, there are no double white spaces, and no missing white spaces
* 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.
* Don't just look at untranslated string, some strings are automatically translated by Transifex but might still be wrong because the context requires a different translation. use source_updated_after:dd-mm-yyyy to find all the new strings. Also check for edits made by others, using translation_updated_after:dd-mm-yyyy .

==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.''

===Grammar and word order in sentences===
*[https://www.dutchgrammar.com/en/?n=WordOrder.00 https://www.dutchgrammar.com/en/?n=WordOrder.00] About word order in sentences. It's not just one page, keep clicking on next page in the bottom right to see more examples.
*[http://redekundig.nl/ http://redekundig.nl/] a tool to help identify the structure of a Dutch sentence. Very helpful if you're dealing with complex grammatical rules and need to understand the sentence you are reviewing.
* [https://urd2.let.rug.nl/~vannoord/bin/alpino https://urd2.let.rug.nl/~vannoord/bin/alpino] university hosted tool to identify structure of a Dutch sentence. It's the same tool as redekundig.nl but hosted elsewhere, and the interface is harder to comprehend. Would advise trying this in case redekundig.nl isn't giving you the information you need.
* [https://onzetaal.nl/taaladvies/signaalwoorden-lijst/ List of signal words], use these wherever possible, they help clarify your message and prevent ambiguity.

===Style and tone===
* First follow any style guide you find here on this wiki for language and project you are working on
* If you are missing something, contact other translators
* If you search for style advise from other websites, avoid getting it from tech companies who make up their own version of Dutch language based on marketing rather than proper standard Dutch. Also avoid other wiki's which are often written by opinionated people who are not representative for the language. That doesn't mean you can't read them and learn from them, but take it with a grain of salt.

===Spelling===
*[https://taaladvies.net Taaladvies]
*[https://taal.vrt.be Taalnet]
*[https://onzetaal.nl OnzeTaal]

===Technical terminology===
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:
[https://docs.google.com/spreadsheets/d/1OPyeWDq2rtPf9fEpCLRpHl9Hn--OfFbWLbrGtZx3lYI/edit?usp=sharing Dutch Unified Localization Lab Glossary]. The document is maintained by Erin (a localization lab employee). If you wish to add comments, edits or suggest new entries, do so using the "Comment" feature in the spreadsheet.

==Language varieties==
Dutch language varieties do not have their own glossary, style guide or terminology. All of these languages varieties follow Dutch (nl). there is generally no use in setting up resources for nl_NL, nl_BE or any other nl_* region, project maintainers should simply set up nl.

===Dutch in Belgium / Flemish (nl_BE)===
Flemish people may live in a different geographical region but are in a language union with and are in the same language region as Dutch people, therefore there are usually no differences between nl_NL and nl_BE. Projects should simply be localized to Dutch (nl). In the rare case some translation isn't clear to Flemish speakers, they can request to phrase the translation differently, but at all times the rules of standard Dutch should be followed.

===Other varieties===
Below you find a list of other language varieties along with their ISO 3166-1 code:
* nl_AW Dutch (Aruba)
* nl_BQ Dutch (Caribbean Netherlands (Bonaire, Saba, Sint Eustatius))
* nl_CW Dutch (Curaçao)
* nl_SR Dutch (Suriname)
* nl_SX Dutch (Sint Maarten)

==Similar languages==
If you want to localize a project to a language which has strong similarities to Dutch and if there already exist good quality translations to Dutch, than it is recommended to base your translations of Dutch rather than English or an other source language. This may make translations faster, but more importantly it also keeps the texts consistent, so that someone who lives just across the border, or someone who has family in the other region, doesn't see completely different texts for the same project. In Transifex there is an option to swap which language you are using as the source language for your translations; you will find it by clicking the setting icon in the top right of the translation interface. Any strings that have not yet been translated to Dutch will automatically still be shown as the original source language for the project (usually English).

===West Frisian (fy_NL)===
Frisian is a language of its own, but because most if Frisians actually live in the Netherlands and have Dutch as their first or second language, and because the Frisian community is very small, Frisian is merged with the Dutch community. Of course they have their own style, terminology and glossary but these have not yet been determined.

===Afrikaans (af)===
Afrikaans is a language on its own and because it is spoken in a different region and has plenty of speakers, it has its own localization community.

Dutch

2021-04-15T18:06:42Z

Meteor0id: Significant corrections to "language varieties"

__TOC__

==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 [https://internetfreedomfestival.org/ International Freedom Festival] domain and is subject to their [https://www.internetfreedomfestival.org/wiki/index.php/Code_of_Conduct Code of Conduct]. Be sure to read through the [https://www.internetfreedomfestival.org/wiki/index.php/Code_of_Conduct Code of Conduct] and then [mailto:info@localizationlab.org?subject=Mattermost%20Sign-up&body=Please%20send%20me%20a%20link%20to%20sign%20up%20for%20Mattermost. 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==
Ask yourself: "If my 65 year old mother read this (who has a total of 3 apps on her phone and uses only one of them on a weekly basis), would she understand this without anyone's help?". The goal is not to translate words, the goal is to make the text understandable to people who grew up in a different country.

===Signal Messenger===
''This Style guide is a result of reviewers communicating about inconsistencies and solutions to those. 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. We will try to make this style guide easier to read in the future.''

* The most important rule to always keep in question yourself who your audience will be and whether they will fully understand it. Yes, you are doing this work on behave of the Signal developers, but your audience are Signal users. Place yourself in the frame of mind of a Signal user who doesn't really know much about Signal and is trying to understand his options. Don't just translate literary, translate in such a way that it makes sense, is accurate, and is easy to read for the end user.
* 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. 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, meaning different words and/or a different structure of the sentence. An example: "Signal needs location services enabled to discover and connect with your old Android device." is localized as "Om je oude Android apparaat te kunnen detecteren en om er verbinding mee te maken is het nodig dat locatiebepaling op je apparaat is ingeschakeld.". Another example: don't write "Om het in te schakelen, tik op de schuifknop zodat hij blauw wordt." but instead write "Tik op de schuifknop zodat hij blauw wordt om meekijkpreventie in te schakelen."
* 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 punctuation, end the sentence with a period. If the description does not contain any punctuation, 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 Dutch people also get it wrong. [https://www.dutchgrammar.com/en/?n=WordOrder.00] 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. An example: Don't write "Deze personen kunnen door jou niet direct worden toegevoegd aan de groep." instead write "Deze personen kunnen door jou niet direct aan de groep worden toegevoegd.".
* 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 white space: 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 …
* Make sure the subject is repeated in every new sentence, do not refer back to a previous sentence. We do this to keep texts easy to read and understand. An example: do not write "Turing this on allows you to receive emails. They will contain information about your account." instead write "Turning this on allows you to receive emails. The emails you will receive contain information about your account.".
* Avoid anglicisms, our job is to localize the content so it can be understood by as many people as possible, that includes people who don't understand even the most common of English words.
* For units we follow the Si-standards. That means we translate 20MB as 20 MB with a white space. Kilobytes as kB. Note that Signal does not use KiB, MiB etc, because Signal is following the same units as the Android operating system. The same rule applies to other units such as 10s becoming 10 s. Abbreviations for minutes, months and weeks are not si units but we agreed to translate those as "min", "mnd" and "w". Capitalization matters.
* The text strings for the app store sometimes contain wordplay. If a good wordplay in Dutch can't be found, than rather leave the word joke out and just factually describe the change.
* Use pronoun + "wie" instead of "die" wherever possible. Read [https://taaladvies.net/taal/advies/vraag/1564 Taaladvies about wie/die] about where to use "wie" and where to use "die". This is a style choice we made to make complex sentences easier to comprehend.
* Use "van wie", "bij wie", "op wie" and "voor wie" instead of "waarvan", "waarmee", "waarop" and "waarvoor" wherever possible.
* For texts on buttons in Android and Desktop: use "Aan gesprek deelnemen", "Aan Signal doneren" and "Alice toevoegen". Do not use "Voeg Alice toe" or "Deelnemen aan gesprek" or "Doneren aan Signal". reason for this is optial readability. Also capitalize the first letter. on iOS we have not yet decided on the style, because that operating system often uses 'gebiedende wijs' rather than 'infinitief'.
* Try to stick to Dutch words, even if you see English words being used in other apps: "timer" becomes "tijdspanne", "admin" "beheerder", "checkbox" "selectievakje of aankruisvakje", "updaten" "bijwerken", "icon" "pictogram", "non-profit" "organisatie zonder winstoogmerk", "error" "fout", "database""databank" etc. You can find words like these listed in the Transifex Glossary for the Dutch Signal project.
* Beware of capitalization: use "QR-code" do not use "QR-Code" or "qr-code". "WiFi" is spelled different in Dutch: "wifi" all lowercase and without a dash. You can find words like these listed in the Transifex Glossary for the Dutch Signal project.
* Use [https://onzetaal.nl/taaladvies/signaalwoorden-lijst/ signal words] (words that indicate summation, contradiction etc.) wherever possible.
* Use formal verbs where their is no difference in meaning: use "je kunt" not "je kan". Howerver for "kun je" versus "kan je" there is a minor difference: "kan je" is more proposing while "kun je" is more forcefully suggestive. Therefore we use "kan je" instead of "kun je", and "zal je" instead of "zul je". [https://taalhelden.org/bericht/het-kan-je-kun-je https://taalhelden.org/bericht/het-kan-je-kun-je]
* Don't forget that although in English articles can be omitted, in Dutch it's not an accepted practice to omit the article. For example: "Playback time of audio attachment" should be localized as "Afspeellengte van HET audiobericht".
* Don't use possessive pronounce for things the user isn't possessing: Don't write "Open Signal-Desktop en gebruik de sneltoetsen om je tekstgrootte aan te passen.", instead write "Open Signal-Desktop en gebruik de sneltoetsen om de tekstgrootte aan te passen.". Users don't have font size, Signal has font size.
* We consistently use only the ‘rode werkwoordsvolgorde’, never the ‘groene werkwoordsvolgorde’. This means we never write "... vertrokken is." but instead always write "... is vertrokken.". For more information about verb order: [https://onzetaal.nl/taaladvies/rode-groene-volgorde/ https://onzetaal.nl/taaladvies/rode-groene-volgorde/]

Extra example:
* Don't localize "Other Signal users who are saved to your phone's contact list." as "Andere Signal-gebruikers die zijn opgeslagen in jouw telefoons contactenlijst." but instead localize it as "Andere Signal-gebruikers van wie het telefoonnummer voor komt in de systeemcontactenlijst van jouw telefoon."

===Other projects===
For other projects the style has not yet been written down, however some translators seem to hold on to [http://download.microsoft.com/download/4/7/e/47e135ad-15d7-4491-be78-369804f0d333/nld-nld-StyleGuide.pdf a style guide from Microsoft].

==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.
* ANY time you edit a translation on a project with multiple separate resources, make sure to open all the resources and check if the same string exists elsewhere to apply the exact same edit there. An example would be when you edit a string in the Android Signal messenger app, make sure to also check if the same string exists in the Desktop app, the iOS app, the website or the support center. It's not easy for other reviewers to spot the inconsistency later, so do this right away at the very moment you make an edit.
* Be extra careful with plurals in Transifex, it's easy to miss one of the plural forms when reviewing. You can check all plurals again by searching for pluralized:yes
* Found a spelling mistake, grammar mistake, word order mistake or some word which is better substituted with another word? Don't just correct it when you see it and move on, check all the strings on all the resources for the same mistake or imperfection and correct that mistake on all the strings where it occurs. The moment you noticed something is the only opportunity to come up with a consistent solution across all the strings.

==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 punctuation is accurate, the capitalization is accurate, there are no double white spaces, and no missing white spaces
* 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.
* Don't just look at untranslated string, some strings are automatically translated by Transifex but might still be wrong because the context requires a different translation. use source_updated_after:dd-mm-yyyy to find all the new strings. Also check for edits made by others, using translation_updated_after:dd-mm-yyyy .

==Language varieties==
Dutch language varieties do not have their own glossary, style guide or terminology. All of these languages varieties follow Dutch (nl). there is generally no use in setting up resources for nl_NL, nl_BE or any other nl_* region, project maintainers should simply set up nl.

===Dutch in Belgium / Flemish (nl_BE)===
Flemish people may live in a different geographical region but are in a language union with and are in the same language region as Dutch people, therefore there are usually no differences between nl_NL and nl_BE. Projects should simply be localized to Dutch (nl). In the rare case some translation isn't clear to Flemish speakers, they can request to phrase the translation differently, but at all times the rules of standard Dutch should be followed.

===Other varieties===
Below you find a list of other language varieties along with their ISO 3166-1 code:
* nl_AW Dutch (Aruba)
* nl_BQ Dutch (Caribbean Netherlands (Bonaire, Saba, Sint Eustatius))
* nl_CW Dutch (Curaçao)
* nl_SR Dutch (Suriname)
* nl_SX Dutch (Sint Maarten)

==Similar languages==
If you want to localize a project to a language which has strong similarities to Dutch and if there already exist good quality translations to Dutch, than it is recommended to base your translations of Dutch rather than English or an other source language. This may make translations faster, but more importantly it also keeps the texts consistent, so that someone who lives just across the border, or someone who has family in the other region, doesn't see completely different texts for the same project. In Transifex there is an option to swap which language you are using as the source language for your translations; you will find it by clicking the setting icon in the top right of the translation interface. Any strings that have not yet been translated to Dutch will automatically still be shown as the original source language for the project (usually English).

===West Frisian (fy_NL)===
Frisian is a language of its own, but because most if Frisians actually live in the Netherlands and have Dutch as their first or second language, and because the Frisian community is very small, Frisian is merged with the Dutch community. Of course they have their own style, terminology and glossary but these have not yet been determined.

===Afrikaans (af)===
Afrikaans is a language on its own and because it is spoken in a different region and has plenty of speakers, it has its own localization community.

==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.''

===Grammar and word order in sentences===
*[https://www.dutchgrammar.com/en/?n=WordOrder.00 https://www.dutchgrammar.com/en/?n=WordOrder.00] About word order in sentences. It's not just one page, keep clicking on next page in the bottom right to see more examples.
*[http://redekundig.nl/ http://redekundig.nl/] a tool to help identify the structure of a Dutch sentence. Very helpful if you're dealing with complex grammatical rules and need to understand the sentence you are reviewing.
* [https://urd2.let.rug.nl/~vannoord/bin/alpino https://urd2.let.rug.nl/~vannoord/bin/alpino] university hosted tool to identify structure of a Dutch sentence. It's the same tool as redekundig.nl but hosted elsewhere, and the interface is harder to comprehend. Would advise trying this in case redekundig.nl isn't giving you the information you need.
* [https://onzetaal.nl/taaladvies/signaalwoorden-lijst/ List of signal words], use these wherever possible, they help clarify your message and prevent ambiguity.

===Style and tone===
* First follow any style guide you find here on this wiki for language and project you are working on
* If you are missing something, contact other translators
* If you search for style advise from other websites, avoid getting it from tech companies who make up their own version of Dutch language based on marketing rather than proper standard Dutch. Also avoid other wiki's which are often written by opinionated people who are not representative for the language. That doesn't mean you can't read them and learn from them, but take it with a grain of salt.

===Spelling===
*[https://taaladvies.net Taaladvies]
*[https://taal.vrt.be Taalnet]
*[https://onzetaal.nl OnzeTaal]

===Technical terminology===
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:
[https://docs.google.com/spreadsheets/d/1OPyeWDq2rtPf9fEpCLRpHl9Hn--OfFbWLbrGtZx3lYI/edit?usp=sharing Dutch Unified Localization Lab Glossary]. The document is maintained by Erin (a localization lab employee). If you wish to add comments, edits or suggest new entries, do so using the "Comment" feature in the spreadsheet.

Dutch

2021-04-15T16:22:01Z

Meteor0id: /* Language varieties */

__TOC__

==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 [https://internetfreedomfestival.org/ International Freedom Festival] domain and is subject to their [https://www.internetfreedomfestival.org/wiki/index.php/Code_of_Conduct Code of Conduct]. Be sure to read through the [https://www.internetfreedomfestival.org/wiki/index.php/Code_of_Conduct Code of Conduct] and then [mailto:info@localizationlab.org?subject=Mattermost%20Sign-up&body=Please%20send%20me%20a%20link%20to%20sign%20up%20for%20Mattermost. 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==
Ask yourself: "If my 65 year old mother read this (who has a total of 3 apps on her phone and uses only one of them on a weekly basis), would she understand this without anyone's help?". The goal is not to translate words, the goal is to make the text understandable to people who grew up in a different country.

===Signal Messenger===
''This Style guide is a result of reviewers communicating about inconsistencies and solutions to those. 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. We will try to make this style guide easier to read in the future.''

* The most important rule to always keep in question yourself who your audience will be and whether they will fully understand it. Yes, you are doing this work on behave of the Signal developers, but your audience are Signal users. Place yourself in the frame of mind of a Signal user who doesn't really know much about Signal and is trying to understand his options. Don't just translate literary, translate in such a way that it makes sense, is accurate, and is easy to read for the end user.
* 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. 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, meaning different words and/or a different structure of the sentence. An example: "Signal needs location services enabled to discover and connect with your old Android device." is localized as "Om je oude Android apparaat te kunnen detecteren en om er verbinding mee te maken is het nodig dat locatiebepaling op je apparaat is ingeschakeld.". Another example: don't write "Om het in te schakelen, tik op de schuifknop zodat hij blauw wordt." but instead write "Tik op de schuifknop zodat hij blauw wordt om meekijkpreventie in te schakelen."
* 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 punctuation, end the sentence with a period. If the description does not contain any punctuation, 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 Dutch people also get it wrong. [https://www.dutchgrammar.com/en/?n=WordOrder.00] 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. An example: Don't write "Deze personen kunnen door jou niet direct worden toegevoegd aan de groep." instead write "Deze personen kunnen door jou niet direct aan de groep worden toegevoegd.".
* 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 white space: 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 …
* Make sure the subject is repeated in every new sentence, do not refer back to a previous sentence. We do this to keep texts easy to read and understand. An example: do not write "Turing this on allows you to receive emails. They will contain information about your account." instead write "Turning this on allows you to receive emails. The emails you will receive contain information about your account.".
* Avoid anglicisms, our job is to localize the content so it can be understood by as many people as possible, that includes people who don't understand even the most common of English words.
* For units we follow the Si-standards. That means we translate 20MB as 20 MB with a white space. Kilobytes as kB. Note that Signal does not use KiB, MiB etc, because Signal is following the same units as the Android operating system. The same rule applies to other units such as 10s becoming 10 s. Abbreviations for minutes, months and weeks are not si units but we agreed to translate those as "min", "mnd" and "w". Capitalization matters.
* The text strings for the app store sometimes contain wordplay. If a good wordplay in Dutch can't be found, than rather leave the word joke out and just factually describe the change.
* Use pronoun + "wie" instead of "die" wherever possible. Read [https://taaladvies.net/taal/advies/vraag/1564 Taaladvies about wie/die] about where to use "wie" and where to use "die". This is a style choice we made to make complex sentences easier to comprehend.
* Use "van wie", "bij wie", "op wie" and "voor wie" instead of "waarvan", "waarmee", "waarop" and "waarvoor" wherever possible.
* For texts on buttons in Android and Desktop: use "Aan gesprek deelnemen", "Aan Signal doneren" and "Alice toevoegen". Do not use "Voeg Alice toe" or "Deelnemen aan gesprek" or "Doneren aan Signal". reason for this is optial readability. Also capitalize the first letter. on iOS we have not yet decided on the style, because that operating system often uses 'gebiedende wijs' rather than 'infinitief'.
* Try to stick to Dutch words, even if you see English words being used in other apps: "timer" becomes "tijdspanne", "admin" "beheerder", "checkbox" "selectievakje of aankruisvakje", "updaten" "bijwerken", "icon" "pictogram", "non-profit" "organisatie zonder winstoogmerk", "error" "fout", "database""databank" etc. You can find words like these listed in the Transifex Glossary for the Dutch Signal project.
* Beware of capitalization: use "QR-code" do not use "QR-Code" or "qr-code". "WiFi" is spelled different in Dutch: "wifi" all lowercase and without a dash. You can find words like these listed in the Transifex Glossary for the Dutch Signal project.
* Use [https://onzetaal.nl/taaladvies/signaalwoorden-lijst/ signal words] (words that indicate summation, contradiction etc.) wherever possible.
* Use formal verbs where their is no difference in meaning: use "je kunt" not "je kan". Howerver for "kun je" versus "kan je" there is a minor difference: "kan je" is more proposing while "kun je" is more forcefully suggestive. Therefore we use "kan je" instead of "kun je", and "zal je" instead of "zul je". [https://taalhelden.org/bericht/het-kan-je-kun-je https://taalhelden.org/bericht/het-kan-je-kun-je]
* Don't forget that although in English articles can be omitted, in Dutch it's not an accepted practice to omit the article. For example: "Playback time of audio attachment" should be localized as "Afspeellengte van HET audiobericht".
* Don't use possessive pronounce for things the user isn't possessing: Don't write "Open Signal-Desktop en gebruik de sneltoetsen om je tekstgrootte aan te passen.", instead write "Open Signal-Desktop en gebruik de sneltoetsen om de tekstgrootte aan te passen.". Users don't have font size, Signal has font size.
* We consistently use only the ‘rode werkwoordsvolgorde’, never the ‘groene werkwoordsvolgorde’. This means we never write "... vertrokken is." but instead always write "... is vertrokken.". For more information about verb order: [https://onzetaal.nl/taaladvies/rode-groene-volgorde/ https://onzetaal.nl/taaladvies/rode-groene-volgorde/]

Extra example:
* Don't localize "Other Signal users who are saved to your phone's contact list." as "Andere Signal-gebruikers die zijn opgeslagen in jouw telefoons contactenlijst." but instead localize it as "Andere Signal-gebruikers van wie het telefoonnummer voor komt in de systeemcontactenlijst van jouw telefoon."

===Other projects===
For other projects the style has not yet been written down, however some translators seem to hold on to [http://download.microsoft.com/download/4/7/e/47e135ad-15d7-4491-be78-369804f0d333/nld-nld-StyleGuide.pdf a style guide from Microsoft].

==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.
* ANY time you edit a translation on a project with multiple separate resources, make sure to open all the resources and check if the same string exists elsewhere to apply the exact same edit there. An example would be when you edit a string in the Android Signal messenger app, make sure to also check if the same string exists in the Desktop app, the iOS app, the website or the support center. It's not easy for other reviewers to spot the inconsistency later, so do this right away at the very moment you make an edit.
* Be extra careful with plurals in Transifex, it's easy to miss one of the plural forms when reviewing. You can check all plurals again by searching for pluralized:yes
* Found a spelling mistake, grammar mistake, word order mistake or some word which is better substituted with another word? Don't just correct it when you see it and move on, check all the strings on all the resources for the same mistake or imperfection and correct that mistake on all the strings where it occurs. The moment you noticed something is the only opportunity to come up with a consistent solution across all the strings.

==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 punctuation is accurate, the capitalization is accurate, there are no double white spaces, and no missing white spaces
* 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.
* Don't just look at untranslated string, some strings are automatically translated by Transifex but might still be wrong because the context requires a different translation. use source_updated_after:dd-mm-yyyy to find all the new strings. Also check for edits made by others, using translation_updated_after:dd-mm-yyyy .

==Language varieties==
If you want to localize a project to a language variety which has strong similarities to Dutch and if there already exist good quality translations to Dutch, than it is recommended to base your translations of Dutch rather than English or an other source language. This may make translations faster, but more importantly it also keeps the texts consistent, so that someone who lives just across the border doesn't see completely different texts for the same project. In Transifex there is an option to swap which language you are using as the source language for your translations; you will find it by clicking the setting icon in the top right of the translation interface. Any string that have not yet been translated to Dutch will automatically still be shown as the original source language for the project (usually English).

===Flemish (nl_BE)===
If a project does not accept translations for nl_BE than unfortunately for Flanders, the languages nl and nl_NL will still follow Dutch standard language (Nederlandse standaardtaal). It is not acceptable to deliberately choose words and sentence structure which are understood by both language varieties, as that would reduce quality for both language varieties. If Flemish translators want to work on a project, they should contact a project maintainer and ask to add a nl_BE project. International Dutch (nl) is exactly the same as Dutch spoken in the Netherlands (nl_NL).

===Frisian (fy_NL)===
Frisian is a language of its own, but because most if Frisians actually live in the Netherlands and have Dutch as their first or second language, and because the Frisian community is very small, Frisian is merged with the Dutch community. Of course they have their own style, terminology and glossary but these have not yet been determined.

===Afrikaans (af)===
Afrikaans is a language on its own and because it is spoken in a different region and has plenty of speakers, it has its own community.

===Other varieties===
Other varieties do not have their own glossary, style guide or terminology because their communities are too small to maintain translations. These languages follow International Dutch. Below you find a list of these language varieties:
* nl_AW Dutch (Aruba)
* nl_BQ Dutch (Caribbean Netherlands)
* nl_CW Dutch (Curaçao)
* nl_SR Dutch (Suriname)
* nl_SX Dutch (Sint Maarten)

==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.''

===Grammar and word order in sentences===
*[https://www.dutchgrammar.com/en/?n=WordOrder.00 https://www.dutchgrammar.com/en/?n=WordOrder.00] About word order in sentences. It's not just one page, keep clicking on next page in the bottom right to see more examples.
*[http://redekundig.nl/ http://redekundig.nl/] a tool to help identify the structure of a Dutch sentence. Very helpful if you're dealing with complex grammatical rules and need to understand the sentence you are reviewing.
* [https://urd2.let.rug.nl/~vannoord/bin/alpino https://urd2.let.rug.nl/~vannoord/bin/alpino] university hosted tool to identify structure of a Dutch sentence. It's the same tool as redekundig.nl but hosted elsewhere, and the interface is harder to comprehend. Would advise trying this in case redekundig.nl isn't giving you the information you need.
* [https://onzetaal.nl/taaladvies/signaalwoorden-lijst/ List of signal words], use these wherever possible, they help clarify your message and prevent ambiguity.

===Style and tone===
* First follow any style guide you find here on this wiki for language and project you are working on
* If you are missing something, contact other translators
* If you search for style advise from other websites, avoid getting it from tech companies who make up their own version of Dutch language based on marketing rather than proper standard Dutch. Also avoid other wiki's which are often written by opinionated people who are not representative for the language. That doesn't mean you can't read them and learn from them, but take it with a grain of salt.

===Spelling===
*[https://taaladvies.net Taaladvies]
*[https://taal.vrt.be Taalnet]
*[https://onzetaal.nl OnzeTaal]

===Technical terminology===
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:
[https://docs.google.com/spreadsheets/d/1OPyeWDq2rtPf9fEpCLRpHl9Hn--OfFbWLbrGtZx3lYI/edit?usp=sharing Dutch Unified Localization Lab Glossary]. The document is maintained by Erin (a localization lab employee). If you wish to add comments, edits or suggest new entries, do so using the "Comment" feature in the spreadsheet.

Language Resources

2021-04-15T16:14:30Z

Meteor0id: /* Language Team Pages */

Want to add a language team page? You can use and customize the [[Language Team Template]] to get started.
<div style="float:right; margin-left:2.5em">__TOC__</div>
==Language Team Pages==

{| class="wikitable sortable"
|-
! Language Team
! [https://en.wikipedia.org/wiki/List_of_ISO_639-1_codes ISO 639-1] Codes
|-
| [[Afrikaans]]
| af
|-
| [[Amharic]]
| am
|-
| [[Arabic]]
| ar
|-
| [[Burmese]]
| my
|-
| [[Catalan]]
| ca
|-
| [[Chinese (simplified)]]
| zh, zh_CH, zh-Hans
|-
| [[Chinese (traditional)]]
| zh, zh_TW, zh-Hant
|-
| [[Dutch]] & Frisian
| nl, nl_BE, fy
|-
| [[French]]
| fr
|-
| [[German]]
| de
|-
| [[Greek]]
| el
|-
| [[Indonesian (Bahasa)]]
| id
|-
| [[Kannada]]
| kn
|-
| [[Khmer]]
| km
|-
| [[Kurdish (Kurmanji)]]
| kmr
|-
| [[Kurdish (Sorani)]]
| ckb
|-
| [[Luganda]]
| lg
|-
| [[Malayalam]]
| ml
|-
| [[Oromo]]
| om
|-
| [[Persian]]
| fa
|-
| [[Portuguese (Portugal)]]
| pt, pt_PT
|-
| [[Portuguese (Brazilian)]]
| pt_BR
|-
| [[Serbian]]
| sr
|-
| [[Shona]]
| sn
|-
| [[Spanish]]
| es
|-
| [[Swahili]]
| sw
|-
| [[Tigrinya]]
| ti
|-
| [[Thai]]
| th
|-
| [[Turkish]]
| tr
|-
| [[Turkmen]]
| tk
|-
| [[Ukrainian]]
| uk
|}

==Multi-Lingual Glossaries==
* [https://www.wikipedia.org/ Wikipedia] *Search for a term in English and refer to the "Languages" section in the sidebar to see if a page for that term exists in your language. You can also add terms yourself: "[https://en.wikipedia.org/wiki/Wikipedia:Translation#How_to_translate How to Translate]"

* [https://www.microsoft.com/Language/en-US/Search.aspx Microsoft Language Portal Searchable Terminologies]

* [http://www.it46.se/glossmaster/ African Network for Localization FOSS Glossaries] *Glossaries are downloadable as CSV and are available for Akan, Arabic, Amharic, French, Kinyarwanda, Lingala, Luganda, Songhay, Yoruba, and Zulu.

* Electronic Frontier Foundation's [https://ssd.eff.org/en/glossary Security Self-Defense Glossary] *Available in: Amharic, Arabic, French, Russian, Spanish, Thai, Turkish, Vietnamese, Urdu

==Multi-Lingual Style Guides==
* [https://www.microsoft.com/en-US/Language/StyleGuides Microsoft Language Portal Downloadable Style Guides] 
* [https://wiki.mozilla.org/Category:L10n_Teams Mozilla Language Team Resources] *Find your language by its [https://www.loc.gov/standards/iso639-2/php/code_list.php ISO 639-1/2 code]

==Terminology & Glossary Planning==
===Term Planning===
[http://www.terminfo.fi/sisalto/term-planning-for-irish--and-other-languages-85.html Term planning for Irish – and other languages]

Projects

2021-04-15T16:07:15Z

Meteor0id: update Signal

__TOC__

=Projects actively supported by Localization Lab=

{| class="wikitable sortable" style="font-size:75%"
|-
! Logo
! Project
! Organization
! Summary
! Project Site
! Project Type
! Project Status
|-
| [[File:Apple_Censorship_Logo.jpg|75px|center|Apple Censorship Logo]]
| [[Apple Censorship]]
| [https://en.greatfire.org/ GreatFire]
| 
| [https://applecensorship.com/ applecensorship.com]
| Censorship
| Active
|-
| [[File:Bitmask.png|75px|center|Bitmask Logo]]
| [[Bitmask]]
| [https://leap.se/ LEAP]
| Bitmask is an open source application to provide easy and secure encrypted communication. You can choose among several different service providers or start your own. Currently, Bitmask supports encrypted internet (VPN) and encrypted email.
| [https://bitmask.net/ bitmask.net]
| Circumvention, VPN, Email Encryption
| Active
|-
| [[File:Briar_Logo.png|75px|center|Briar Project Logo]]
| [[Briar]]
| Briar Project
| Briar offers peer-to-peer encrypted messaging and forums, storing data securely on your device and not in the cloud. Briar also allows you to connect directly with nearby contacts without Internet access, making messaging possible with low-bandwidth or when Internet access is blocked.
| [https://briarproject.org/ briarproject.org]
| Secure Messaging
| Active
|-
| [[File:BypassCensorship.png|100px|center|Bypass Censorship Website Logo]]
| [[Bypass Censorship Website]]
|
| The Bypass Censorship website aims to connect individuals worldwide with effective tools to circumvent censorship.
| [https://bypasscensorship.org bypasscensorship.org]
| Circumvention
| Active
|-
| [[File:BIFSO_Logo.png|75px|center|CGIProxy Logo]]
| [[CGIProxy]]
| [https://freespeechonline.net/ Berkeley Institute for Free Speech Online]
| CGIProxy is a client-less circumvention tool that allows individuals to access blocked content on their web browser by proxying it through a server running CGIProxy outside of the region of the censoring filter.
| [https://freespeechonline.net/download/ freespeechonline.net/download]
| Circumvention
| Pending
|-
| [[File:Commotion.png|75px|center|Commotion Logo]]
| [[Commotion]]
| Formerly hosted by the [https://www.newamerica.org/oti/ Open Technology Institute]
| "Commotion is an open-source communication tool that uses wireless devices to create decentralized mesh networks."
| [https://www.commotionwireless.net/ www.commotionwireless.net]
| Mesh Networking
| Active
|-
| [[File:Courier.png|75px|center|Courier Logo]]
| [[Courier]]
| [https://guardianproject.info/ Guardian Project]
| Courier is a mobile news reader with enhanced security features, offline reading and device-to-device sharing capability. We’ve designed it to be fast and light on slow networks and secured from device and network monitoring.
| [https://guardianproject.info/apps/courier/ guardianproject.info]
| Secure RSS Feeds
| Active
|-
| [[File:Cupcake_Logo.png|100px|center|Cupcake Logo]]
| [[Cupcake]]
| Cupcake
| "Cupcake empowers you to assist censored internet users all over the world by turning your web browser into a pathway to the Tor network."
| [https://chrome.google.com/webstore/detail/cupcake/dajjbehmbnbppjkcnpdkaniapgdppdnc Cupcake Chome Extension]
|
| Active
|-
| [[File:Deflect.png|75px|center|Deflect Logo]]
| [[Deflect]]
| [https://equalit.ie/ Equalit.ie]
| "Deflect is a robust and innovative website protection service designed to withstand distributed denial of service (DDoS) attacks."
| [https://deflect.ca/ deflect.ca]
| Website Security and Hosting
| Active
|-
| [[File:Enigmail.png|100px|center|Enigmail Logo]]
| [[Enigmail]]
| [https://www.enigmail.net/index.php/en/ The Enigmail Project]
| Enigmail is a Mozilla Thunderbird add-on that allows you to use OpenPGP to encrypt and digitally sign your emails and to decrypt and verify messages you receive.
| [https://www.enigmail.net/index.php/en/ enigmail.net]
| Email Encryption
| Active
|-
| [[File:F-Droid_Logo.png|75px|center|F-Droid Logo]]
| [[F-Droid]]
| [https://f-droid.org/en/about/ F-Droid Limited]
| F-Droid is an installable catalogue of FOSS (Free and Open Source Software) applications for the Android platform. The client makes it easy to browse, install, and keep track of updates on your device.
| [https://f-droid.org/ f-droid.org]
| App Store
| Active
|-
| [[File:FreedomBox-logo-standard.svg|100px|center|FreedomBox Logo]]
| [[FreedomBox]]
| [https://freedomboxfoundation.org/ FreedomBox Foundation]
| FreedomBox is a simple private server, wireless internet router, and multi-purpose tool designed to create internet freedom with only free software and inexpensive hardware. FreedomBox is a Debian-based system designed to protect against data-mining, surveillance, and censorship.
| [https://freedombox.org/ freedombox.org]
| Personal Server
| Active
|-
| [[File:freebooks.png|100px|center|FreeBooks Logo]]
| [[FreeBooks]]
| [https://greatfire.org GreatFire]
| '''Note: FreeBrowser is a closed source project.''' FreeBooks is a free Android app that provides access to censored books, primarily in Mainland China and Iran.
|
| Circumvention
| Active
|-
| [[File:freebrowser.png|100px|center|FreeBrowser Logo]]
| [[FreeBrowser]]
| [https://greatfire.org GreatFire]
| '''Note: FreeBrowser is a closed source project.''' FreeBrowser is a free Android app that provides access to an uncensored internet.
| [https://freebrowser.org freebrowser.org]
| Circumvention
| Active
|-
| [[File:Freenet.png|100px|center|Freenet Logo]]
| [[Freenet]]
| [https://freenetproject.org/ The Freenet Project Inc.]
| Freenet is free software which lets you anonymously share files, browse and publish "freesites" (web sites accessible only through Freenet) and chat on forums, without fear of censorship.
| [https://freenetproject.org/ freenetproject.org]
|
| Active
|-
| [[File:GlobaLeaks.svg|75px|center|Globaleaks Logo]]
| [[Globaleaks]]
| [https://www.hermescenter.org/ Hermes Center for Transparency and Digital Human Rights]
| GlobaLeaks is an open source project aimed at creating a worldwide, anonymous, censorship-resistant, distributed whistleblowing platform.
| [https://www.globaleaks.org/ globaleaks.org]
|
| Active
|-
| [[File:I2P_Logo.jpg|75px|center|I2P Logo]]
| [[I2P]] (Invisible Internet Project)
|
| "I2P is an anonymous network built on top of the internet. It allows netizens to create and access content and build online communities on a network that is both distributed and dynamic. It is intended to protect communication and resist monitoring by third parties such as ISPs."
| [https://geti2p.net/en/ geti2p.net]
|
| Active
|-
| [[File:CJFE.png|75px|center|CJFE Logo]]
| [[Journalists in Distress]]
| [https://www.cjfe.org Canadian Journalists for Free Expression]
| Journalists in Distress is a a digital security guide targeting journalists working in hostile environments.
| [https://www.cjfe.org/journalists_in_distress_securing_your_digital_life www.cjfe.org]
|
| Active
|-
|
| [[keys.openpgp.org]]
| keys.openpgp.org
| "The keys.openpgp.org server is a public service for the distribution and discovery of OpenPGP-compatible keys, commonly referred to as a 'keyserver'."
| [https://keys.openpgp.org/ keys.openpgp.org]
|
| Active
|-
| [[File:Lantern.png|75px|center|Lantern Logo]]
| [[Lantern]]
| [http://www.bravenewsoftware.org/ Brave New Software]
| Lantern is an Internet proxy tool that lets you access blocked sites.
| [https://getlantern.org/ getlantern.org]
|
| Active
|-
| [[File:Mailpile_Vertical_Logo.svg|75px|center|Mailpile App Logo]]
| [[Mailpile]]
| Mailpile
| 
| [https://www.mailpile.is/ mailpile.is]
|
| Active
|-
| [[File:Mailvelope_Logo.png|75px|center|Mailvelope Logo]]
| [[Mailvelope]]
| Mailvelope
| Mailvelope is an easy-to-use browser extension for Chrome and Firefox that enables the exchange of encrypted emails following the OpenPGP encryption standard.
| [https://www.mailvelope.com/ mailvelope.com]
| Email Encryption
| Active
|-
| [[File:MassBrowser.png|75px|center|MassBrowser Logo]]
| [[MassBrowser]]
| [https://people.cs.umass.edu/~amir/Research.html The Secure, Private Internet Research Group (SPIN)]
| "MassBrowser is a state-of-the-art system designed to circumvent Internet censorship. MassBrowser is open-source and free-to-use. It has been designed and developed by the Secure, Private Internet (SPIN) Research Group at the University of Massachusetts Amherst. MassBrowser operates with the help of normal Internet users with open access to the Internet who volunteer to help censored Internet users."
| [https://massbrowser.cs.umass.edu/ massbrowser.cs.umass.edu]
|
| Pending
|-
| [[File:NoScript.png|75px|center|NoScript Logo]]
| [[NoScript]]
|
| NoScript is a Firefox extension that provides extra protection for Firefox, Seamonkey and other mozilla-based browsers. It is a free, open source add-on that allows JavaScript, Java, Flash and other plugins to be executed only by trusted web sites of your choice.
| [https://noscript.net/ noscript.net]
|
| Active
|-
| [[File:ObscuraCam.png|100px|center|ObscuraCam Logo]]
| [[ObscuraCam]]
| [https://guardianproject.info/ Guardian Project]
| "In a world of viral videos and facial recognition, ObscuraCam helps you share photos and videos while protecting the privacy of you and those you care about. With ObscuraCam you can blur and disguise faces in your photos and videos. Information that could identify you as the cameraperson is removed from the files for added security."
| [https://guardianproject.info/apps/obscuracam/ guardianproject.info]
| Photo, Video
| Active
|-
| [[File:OnionBrowser.png|100px|center|Onion Browser Logo]]
| [[Onion Browser]]
|
| "Onion Browser is a free and open-source web browser for iPhone and iPad that encrypts and tunnels web traffic through the Tor network, with extra features to help you browse the internet privately."
| [https://mike.tig.as/onionbrowser/ mike.tig.as/onionbrowser]
| Circumvention, Anonymous and Secure Browsing
| Active
|-
| [[File:OnionShare.png|75px|center|OnionShare Logo]]
| [[OnionShare]]
|
| OnionShare is an open source tool that lets you securely and anonymously share a file of any size.
| [https://onionshare.org/ onionshare.org]
| Anonymous and Secure Filesharing
| Active
|-
| [[File:OONI.png|75px|center|OONIprobe Logo]]
| [[OONI Probe]]
| Open Observatory of Network Interference (OONI)
| OONI Probe is an open source tool for detecting censorship, surveillance and traffic manipulation on the Internet.
| [https://ooni.torproject.org/ ooni.torproject.org]
|
| Active
|-
| [[File:Openkeychain.png|75px|center|OpenKeychain Logo]]
| [[OpenKeychain]]
|
| OpenKeychain is an app for Android that helps you communicate more privately and securely. It is based on the well established OpenPGP standard making encryption compatible across your devices and operating systems.
| [https://www.openkeychain.org openkeychain.org]
| Key Management, Encryption
| Active
|-
| [[File:orbot.png|75px|center|Orbot Logo]]
| [[Orbot]]
| [https://guardianproject.info/ Guardian Project]
| "Orbot is a free proxy app that empowers other apps to use the internet more securely. Orbot uses Tor to encrypt your Internet traffic and then hides it by bouncing through a series of computers around the world. Tor is free software and an open network that helps you defend against a form of network surveillance that threatens personal freedom and privacy, confidential business activities and relationships, and state security known as traffic analysis. Orbot creates a truly private mobile internet connection."
| [https://guardianproject.info/apps/orbot/ guardianproject.info]
| Circumvention
| Active
|-
| [[File:pixelknot.png|75px|center|Pixelknot Logo]]
| [[Pixelknot]]
| [https://guardianproject.info/ Guardian Project]
| Pixelknot is an Android application that allows users to hide short text-based messages in photographs and share them across trusted channels.
| [https://guardianproject.info/apps/pixelknot/ guardianproject.info]
|
| Active
|-
| [[File:psiphon.png|75px|center|Psiphon Logo]]
| [[Psiphon]]
| Psiphon
| Psiphon is an open-source Internet censorship circumvention tool that uses a combination of secure communication and obfuscation technologies (VPN, SSH, and HTTP Proxy).
| [https://psiphon.ca psiphon.ca]
| Circumvention, VPN
| Active
|-
| [[File:RippleApp.png|75px|center|Ripple Logo]]
| [[Ripple]]
| [https://guardianproject.info/ Guardian Project]
| Ripple is a "panic button" that can send it's trigger message to any app that is a "panic responder". Such apps can do things like lock, disguise themselves, delete private data, send an emergency message, and more. It is meant for situations where there is time to react, but where users need to be sure it is not mistakenly set off.
| [https://guardianproject.info/2016/01/12/panickit-making-your-whole-phone-respond-to-a-panic-button/ guardianproject.info]
|
| Active
|-
| [[File:Qubes_OS_Logo.svg|75px|center|Qubes OS Logo]]
| [[Qubes OS]]
| Qubes OS
| Qubes OS is a "relatively secure operating system" that secures your digital life by compartmentalizing your data and online activities.
| [https://www.qubes-os.org qubes-os.org]
|
| Active
|-
| [[File:SecureDrop_logo.png|75px|center|SecureDrop Logo]]
| [[SecureDrop]]
| [https://freedom.press/ Freedom of the Press Foundation]
| SecureDrop is an open-source whistleblower submission system that media organizations can use to securely accept documents from and communicate with anonymous sources.
| [https://securedrop.org/ securedrop.org]
|
| Active
|-
| [[File:SAFETAG.png|75px|center|SAFETAG Logo]]
| [[SAFETAG]]
| [https://www.internews.org/ Internews]
| "Security Auditing Framework and Evaluation Template for Advocacy Groups
SAFETAG is a professional audit framework that adapts traditional penetration testing and risk assessment methodologies to be relevant to smaller non-profit organizations based or operating in the developing world."
| [https://safetag.org/ safetag.org]
|
| Active
|-
| [[File:SAVE.png|75px|center|SAVE by OpenArchive Logo]]
| [[Save]] by OpenArchive
| [open-archive.org OpenArchive]
| "Save is a mobile app designed to help users preserve, protect, and amplify audio/visual media. It is a project of OpenArchive and is free, open-source, and currently available for Android (iOS coming soon!). Functionalities include privacy, mobile archiving, preservation, circumvention, adding metadata and Creative Commons licensing to audio/visual mobile media and sending it to the Internet Archive and other archives over the privacy-focused Tor network."
| [https://open-archive.org/save/ open-archive.org/save]
|
| Active
|-
| [[File:signal.png|75px|center|Signal Logo]]
| [[Signal]]
| Signal Foundation (previously Open Whisper Systems)
| Signal is an open source secure messaging application that uses end-to-end encryption on everything. Very little to no metadata is accessible to the developers, making it an excellent tool to communicate when in fear of government surveillance. Signal is very a feature rish and user friendly messenger, making it suitable for every day use by any user as their main messenger app. Signal is available for iOS, Android and desktop computers and allows users to send one-to-one messages, group messages, self destructing messages, voice messages but also make (group) voice and video calls and share files, photo's and video. Recently Signal is experimenting with letting users make payments to each other using cryptocurrency, turning this messenger app into a multi-purpose app.
| [https://signal.org/ signal.org]
| Secure Messaging, secure crypto-payments
| Active
|-
| [[File:Tella_Logo.png|75px|center|Tella Logo]]
| [[Tella]]
| [https://hzontal.org Horizontal]
| Tella is a documentation app for Android. In challenging environments--with limited or no internet connectivity or in the face of repression--Tella makes it easier and safer to document events, whether that’s violence, human rights violations, corruption, or electoral fraud
| [https://hzontal.org/tella/ hzontal.org/tella]
|
| Active
|-
| [[File:PhishDetect.png|75px|center|PhishDetect Logo]]
| [[PhishDetect]]
|
| PhishDetect is a tool to help at-risk users to identify potential phishing attacks. It allows to distribute up-to-date blocklists, to easily detect and report suspicious emails and links, and to scan unknown pages.
| [https://phishdetect.io/ phishdetect.io]
|
| Active
|-
| [[File:Tails-logo-flat-inverted.svg|100px|center|Tails Logo]]
| [[Tails]]
| Tails
| Tails is a complete operating system that aims to preserve your privacy and anonymity. It helps you to use the Internet anonymously and circumvent censorship almost anywhere you go and on any computer but leaving no trace unless you ask it to explicitly. It is Free Software and based on Debian GNU/Linux.
| [https://tails.boum.org/ tails.boum.org]
|
| Active
|-
| [[File:tor.png|100px|center|Tor Logo]]
| [[Tor]]
| Tor Project
| "Tor protects you by bouncing your communications around a distributed network of relays run by volunteers all around the world: it prevents somebody watching your Internet connection from learning what sites you visit, and it prevents the sites you visit from learning your physical location."
| [https://torproject.org/ torproject.org]
|
| Active
|-
| [[File:UmbrellaApp.jpg|75px|center|Umbrella App Logo]]
| [[Umbrella App]]
| [https://secfirst.org/ Security First]
| Umbrella is a one-stop-shop for all the latest tools and information needed to operate safely in a hostile environment.
| [https://secfirst.org/ secfirst.org]
|
| Active
|-
| [[File:VeraCrypt_Logo.svg|100px|center|VeraCrypt Logo]]
| [[VeraCrypt]]
| [https://www.idrix.fr/Root/ IDRIX]
| Full disk encryption software for Windows, Mac OSX and Linux
| [https://www.veracrypt.fr/en/Home.html www.veracrypt.fr]
| Full-Disk Encryption
| Active
|-
|}

=Other projects supported by Localization Lab=

{| class="wikitable sortable" style="font-size:75%"
|-
! Logo
! Project
! Organization
! Summary
! Project Site
! Project Type
! Project Status
|-
| [[File:Calyx_Logo.png|75px|center|Calyx Institute Logo]]
| [[CalyxOS]]
| [https://calyxinstitute.org/ Calyx Institute]
| 
| [https://calyxos.org/ calyxos.org]
|
| Active
|-
| [[File:Check.jpg|75px|center|Check Logo]]
| [[Check]]
| [https://meedan.com/en/ Meedan]
| 
| [http://checkmedia.org checkmedia.org] [https://www.transifex.com/meedan/check-2/dashboard/ Check on Transifex]
|
| Active
|-
| [[File:Delta-Chat_Logo.png|75px|center|Delta Chat Logo]]
| [[Delta Chat]]
|
| Delta Chat is like Telegram or Whatsapp but without the tracking or central control. Delta Chat does not need your phone number.
| [https://delta.chat/en/ Delta Chat website] [https://www.transifex.com/otf/delta-chat/dashboard/ Delta Chat on Transifex]
|
| Active
|-
| [[File:Haven.png|75px|center|Haven Logo]]
| [[Haven]]
| [https://guardianproject.info/ Guardian Project]
| 
| [https://guardianproject.github.io/haven/ guardianproject.github.io/haven/] [https://www.transifex.com/guardianproject/public/ Haven on Transifex]
|
| Active
|-
|
| [[OpenCircle]]
| [https://guardianproject.info/ Guardian Project]
| 
| [https://github.com/guardianproject/OpenCircle github.com/guardianproject/OpenCircle] [https://www.transifex.com/guardianproject/public/ OpenCircle on Transifex]
|
| Active
|-
|
| [[Outline]]
| [https://jigsaw.google.com/ Jigsaw]
| 
| [https://getoutline.org/en/home getoutline.org]
|
| Active
|-
| [[File:ProofMode.jpeg|75px|center|ProofMode Logo]]
| [[ProofMode]]
| [https://guardianproject.info/ Guardian Project]
| 
| [https://guardianproject.info/2017/02/24/combating-fake-news-with-a-smartphone-proof-mode/ guardianproject.info] [https://www.transifex.com/guardianproject/public/ ProofMode on Transifex]
|
| Active
|-
|
| [[Zom]]
| [https://guardianproject.info/ Guardian Project]
| 
| [https://www.transifex.com/guardianproject/zom/ Zom on Transifex]
|
| Active
|-
|}

=Inactive projects formerly supported by Localization Lab=

{| class="wikitable sortable" style="font-size:75%"
|-
! Logo
! Project
! Organization
! Summary
! Project Site
! Project Type
! Project Status
|-
| [[File:Camerav.png|75px|center|CameraV Logo]]
| [[CameraV]]
| [https://guardianproject.info/ Guardian Project]
| "CameraV is the easiest way to capture and share verifiable photos and video proof on a smartphone or tablet, all the while keeping it entirely secure and private."
| [https://guardianproject.info/apps/camerav/ guardianproject.info]
|
| Inactive - See [[ProofMode]]
|-
| [[File:Firetweet.png|75px|center|Firetweet Logo]]
| [[Firetweet]]
| [http://www.bravenewsoftware.org/ Brave New Software]
| "FireTweet is an Android app powered by Lantern that gives direct unblocked access to Twitter from anywhere in the world."
| [https://firetweet.io/ firetweet.io]
|
| Inactive
|-
| [[File:Gnuprivacyguard.png|75px|center|Gnu Privacy Guard Logo]]
| [[Gnu Privacy Guard]]
| [https://guardianproject.info/ Guardian Project]
| Gnu Privacy Guard (GnuPG) for Android brings the widespread standard in OpenPGP encryption to Android. GnuPG provides solid encryption for keeping emails and files private, and for verifying that emails and files are who you think they are.
| [https://guardianproject.info/code/gnupg/ guardianproject.info]
|
| Inactive - See [[OpenKeychain]]
|-
| [[File:Martus.png|75px|center|Martus Logo]]
| [[Martus]]
| [https://benetech.org/ Benetech]
| Martus is an open source software application that allows users anywhere in the world to securely gather and organize information about human rights violations.
| [https://martus.org/ martus.org]
|
| Inactive
|-
| [[File:netaidkit.png|75px|center|NetAidKit Logo]]
| [[NetAidKit]]
| [https://www.freepressunlimited.org/en Free Press Unlimited]
| The NetAidKit is a pocket size, USB powered router that connects everything to everything, designed specifically for non-technical users. The easy to use web interface will allow you to connect the NetAidKit to a wireless or wired network and share that connection with your other devices, such as a phone, laptop or tablet. 
| [https://netaidkit.net/ netaidkit.net]
|
| Inactive
|-
| [[File:orfox.jpeg|75px|center|Orfox Logo]]
| [[Orfox]]
| [https://guardianproject.info/ Guardian Project]
| "Orfox is built from the same source code as Tor Browser (which is built upon Firefox), but with a few minor modifications to the privacy enhancing features to make them compatible with Firefox for Android and the Android operating system"
| [https://guardianproject.info/apps/orfox/ guardianproject.info]
|
| Inactive - See [[Tor]]
|-
| [[File:Orweb.png|75px|center|Orweb Logo]]
| [[Orweb]]
| [https://guardianproject.info/ Guardian Project]
| 
| [https://guardianproject.info/apps/orweb/ guardianproject.info]
|
| Inactive - See [[Tor]]
|-
| [[File:peerio.jpg|75px|center|Peerio Logo]]
| [[Peerio]]
| Peerio
| Peerio is a cloud-based encrypted communications suite, available for Android, Apple iOS, Windows, Mac, Linux, and as a Google Chrome extension.
| [https://peerio.com peerio.com]
| Secure Messaging, Encryption
| Inactive [https://support.peerio.com/hc/en-us/articles/360021688172-Peerio-Service-Closure-FAQs Peerio Service Closure FAQ]
|-
| [[File:SecureApp.PNG|75px|center|secureApp Generator Logo]]
| [[secureApp Generator]]
| [https://benetech.org/ Benetech]
| The secureApp Generator by Benetech will provide a public system for the creation of secure, multi-lingual, and open source data collection apps that will improve information management and reduce the risk of exposure for reporters, researchers, and activists. By lowering the barrier to strong, open source encryption, this app will democratize technology and empower citizens.
| [https://martus.org/ martus.org]
|
| Inactive
|-
| [[File:Storymaker.png|75px|center|Storymaker Logo]]
| [[Storymaker]]
| [http://smallworldnews.com/ Small World News]
| StoryMaker is an Android app that enables aspiring journalists all over the world to safely produce and publish professional-grade news with their phone.
| [https://storymaker.org/ storymaker.org]
|
| Inactive
|-
|}

Language Resources

2021-04-15T15:48:47Z

Meteor0id: repair links

Want to add a language team page? You can use and customize the [[Language Team Template]] to get started.
<div style="float:right; margin-left:2.5em">__TOC__</div>
==Language Team Pages==

{| class="wikitable sortable"
|-
! Language Team
! [https://en.wikipedia.org/wiki/List_of_ISO_639-1_codes ISO 639-1] Codes
|-
| [[Afrikaans]]
| af
|-
| [[Amharic]]
| am
|-
| [[Arabic]]
| ar
|-
| [[Burmese]]
| my
|-
| [[Catalan]]
| ca
|-
| [[Chinese (simplified)]]
| zh, zh_CH, zh-Hans
|-
| [[Chinese (traditional)]]
| zh, zh_TW, zh-Hant
|-
| [[Dutch]] & Frysk
| nl, nl_BE, fy
|-
| [[French]]
| fr
|-
| [[German]]
| de
|-
| [[Greek]]
| el
|-
| [[Indonesian (Bahasa)]]
| id
|-
| [[Kannada]]
| kn
|-
| [[Khmer]]
| km
|-
| [[Kurdish (Kurmanji)]]
| kmr
|-
| [[Kurdish (Sorani)]]
| ckb
|-
| [[Luganda]]
| lg
|-
| [[Malayalam]]
| ml
|-
| [[Oromo]]
| om
|-
| [[Persian]]
| fa
|-
| [[Portuguese (Portugal)]]
| pt, pt_PT
|-
| [[Portuguese (Brazilian)]]
| pt_BR
|-
| [[Serbian]]
| sr
|-
| [[Shona]]
| sn
|-
| [[Spanish]]
| es
|-
| [[Swahili]]
| sw
|-
| [[Tigrinya]]
| ti
|-
| [[Thai]]
| th
|-
| [[Turkish]]
| tr
|-
| [[Turkmen]]
| tk
|-
| [[Ukrainian]]
| uk
|}

==Multi-Lingual Glossaries==
* [https://www.wikipedia.org/ Wikipedia] *Search for a term in English and refer to the "Languages" section in the sidebar to see if a page for that term exists in your language. You can also add terms yourself: "[https://en.wikipedia.org/wiki/Wikipedia:Translation#How_to_translate How to Translate]"

* [https://www.microsoft.com/Language/en-US/Search.aspx Microsoft Language Portal Searchable Terminologies]

* [http://www.it46.se/glossmaster/ African Network for Localization FOSS Glossaries] *Glossaries are downloadable as CSV and are available for Akan, Arabic, Amharic, French, Kinyarwanda, Lingala, Luganda, Songhay, Yoruba, and Zulu.

* Electronic Frontier Foundation's [https://ssd.eff.org/en/glossary Security Self-Defense Glossary] *Available in: Amharic, Arabic, French, Russian, Spanish, Thai, Turkish, Vietnamese, Urdu

==Multi-Lingual Style Guides==
* [https://www.microsoft.com/en-US/Language/StyleGuides Microsoft Language Portal Downloadable Style Guides] 
* [https://wiki.mozilla.org/Category:L10n_Teams Mozilla Language Team Resources] *Find your language by its [https://www.loc.gov/standards/iso639-2/php/code_list.php ISO 639-1/2 code]

==Terminology & Glossary Planning==
===Term Planning===
[http://www.terminfo.fi/sisalto/term-planning-for-irish--and-other-languages-85.html Term planning for Irish – and other languages]

Bahasa Indonesia

2021-04-15T15:48:10Z

Meteor0id: Meteor0id moved page Bahasa Indonesia to Indonesian (Bahasa): Use English name for language

#REDIRECT [[Indonesian (Bahasa)]]

Indonesian (Bahasa)

2021-04-15T15:48:09Z

Meteor0id: Meteor0id moved page Bahasa Indonesia to Indonesian (Bahasa): Use English name for language

__TOC__

==Communication Platforms==

The Localization Lab Mattermost channel and Localization Lab language-focused channels are hosted on the [https://internetfreedomfestival.org/ International Freedom Festival] Mattermost instance and are subject to their [https://www.internetfreedomfestival.org/wiki/index.php/Code_of_Conduct Code of Conduct]. Be sure to read through the [https://www.internetfreedomfestival.org/wiki/index.php/Code_of_Conduct Code of Conduct] and then [mailto:info@localizationlab.org?subject=Mattermost%20Sign-up&body=Please%20send%20me%20a%20link%20to%20sign%20up%20for%20Mattermost. contact us] and we will send you a link to sign up for the channel.
[https://about.mattermost.com/ Mattermost]: [https://community.internetfreedomfestival.org/community/channels/localization-id''Bahasa Indonesia Channel'']

==Translation References==

===Glossaries===
[https://docs.google.com/spreadsheets/d/19vRoWRzx_BcAR0r8yBPl-3x8h_oK1ENtfXuwW4fPK6o/edit?usp=sharing Localization Lab Unified Glossary]
Feel free to add comments to the glossary if you have suggestions or disagree with translations.

===Style Guides===

==Project Resources==

Traditional Chinese

2021-04-15T15:46:32Z

Meteor0id: Meteor0id moved page Traditional Chinese to Chinese (traditional)

#REDIRECT [[Chinese (traditional)]]

Chinese (traditional)

2021-04-15T15:46:31Z

Meteor0id: Meteor0id moved page Traditional Chinese to Chinese (traditional)

==Communication Platforms　交流平台==
The Localization Lab Mattermost channel and Localization Lab language-focused channels are hosted on the [https://internetfreedomfestival.org/ International Freedom Festival] Mattermost instance and are subject to their [https://www.internetfreedomfestival.org/wiki/index.php/Code_of_Conduct Code of Conduct]. Be sure to read through the [https://www.internetfreedomfestival.org/wiki/index.php/Code_of_Conduct Code of Conduct] and then [mailto:info@localizationlab.org?subject=Mattermost%20Sign-up&body=Please%20send%20me%20a%20link%20to%20sign%20up%20for%20Mattermost. contact us] and we will send you a link to sign up for the channel.
[https://about.mattermost.com/ Mattermost]: [https://community.internetfreedomfestival.org/community/channels/localization-zh-hans''Simplified & Traditional Chinese Channel'']

==Project Resources 專案資源==

==Peoples/ Communities 其它相關社群==
[[Other Chinese Localization Groups]]
他山之石，其它類似的中文在地化社群整理列表

[[Internet Freedom Groups in Taiwan]]
關注網路資訊安全的組織、研究單位或個人

[[Internet Freedom Resources in Chinese]]
有關網際網路自由、網路治理與人權的中文資源

==Works 各項工作開展==

[[現在進行中 doing]]
歡迎加入各項進行中的在地專案，

[[待辦事項 to do]]
值得進行中文化的網路自由工具或相關資訊推薦建議　

[[已完畢 (almost) done]]
中文小組歷來工作成果滙總　

==Tools　中文化實用工具==
[http://jjhou.boolan.com/terms.htm 英中繁簡編程術語對照]

[http://glossary.pank.org/ 中文化辭彙搜尋]

[https://byvoid.github.io/OpenCC/　開放中文轉換] : 一個簡繁中文自動轉換（含二地習慣用語置換）的工具

[https://github.com/sparanoid/chinese-copywriting-guidelines 中文文案排版指北]: 統一中文文案、排版的相關用法

[https://github.com/bluebat/msgchi msgchi]: 一個不知道要做什麼以及如何使用的翻譯工具

====
Map 本頁草圖(draft) 在地化中文小組維基頁架構建議，歁迎成員添加修改，並一起來豐富此維基頁

The following image file [https://coggle.it/diagram/WYqueEX7ngABUMQR is made by coggle], all members are welcome to add/edit/comment it.

[[File:Wiki-Chinese.png]]

Simplified Chinese

2021-04-15T15:45:37Z

Meteor0id: Meteor0id moved page Simplified Chinese to Chinese (simplified)

#REDIRECT [[Chinese (simplified)]]

Chinese (simplified)

2021-04-15T15:45:35Z

Meteor0id: Meteor0id moved page Simplified Chinese to Chinese (simplified)

__TOC__

==Communication Platforms==
The Localization Lab Mattermost channel and Localization Lab language-focused channels are hosted on the [https://internetfreedomfestival.org/ International Freedom Festival] Mattermost instance and are subject to their [https://www.internetfreedomfestival.org/wiki/index.php/Code_of_Conduct Code of Conduct]. Be sure to read through the [https://www.internetfreedomfestival.org/wiki/index.php/Code_of_Conduct Code of Conduct] and then [mailto:info@localizationlab.org?subject=Mattermost%20Sign-up&body=Please%20send%20me%20a%20link%20to%20sign%20up%20for%20Mattermost. contact us] and we will send you a link to sign up for the channel.
[https://about.mattermost.com/ Mattermost]: [https://community.internetfreedomfestival.org/community/channels/localization-zh-hans''Simplified & Traditional Chinese Channel'']

==Project Resources==

===Psiphon===
[[Chinese translation style guide]]

Brazilian Portuguese

2021-04-15T15:44:16Z

Meteor0id: Meteor0id moved page Brazilian Portuguese to Portuguese (Brazilian)

#REDIRECT [[Portuguese (Brazilian)]]

Portuguese (Brazilian)

2021-04-15T15:44:16Z

Meteor0id: Meteor0id moved page Brazilian Portuguese to Portuguese (Brazilian)

Portuguese

2021-04-15T15:40:20Z

Meteor0id: Meteor0id moved page Portuguese to Portuguese (Portugal): Splitting Portugese into Brazil and Protugal varieties

#REDIRECT [[Portuguese (Portugal)]]

Portuguese (Portugal)

2021-04-15T15:40:20Z

Meteor0id: Meteor0id moved page Portuguese to Portuguese (Portugal): Splitting Portugese into Brazil and Protugal varieties

__TOC__

==Communication Platforms==
The Localization Lab Mattermost channel and Localization Lab language-focused channels are hosted on the [https://internetfreedomfestival.org/ International Freedom Festival] Mattermost instance and are subject to their [https://www.internetfreedomfestival.org/wiki/index.php/Code_of_Conduct Code of Conduct]. Be sure to read through the [https://www.internetfreedomfestival.org/wiki/index.php/Code_of_Conduct Code of Conduct] and then [mailto:info@localizationlab.org?subject=Mattermost%20Sign-up&body=Please%20send%20me%20a%20link%20to%20sign%20up%20for%20Mattermost. contact us] and we will send you a link to sign up for the channel.
[https://about.mattermost.com/ Mattermost]: [https://community.internetfreedomfestival.org/community/channels/localization-pt''Portuguese Channel'']

==Translation References==
===Glossaries===
[https://docs.google.com/spreadsheets/d/1L7H21w2eEcdvnIlmnIretQD7O3lNuGZT2dkPT69zJY0/edit?usp=sharing Portuguese (Portugal) Unified Localization Lab Glossary]

===Style Guides===

==Project Resources==

Language Resources

2021-04-15T15:37:05Z

Meteor0id: /* Language Team Pages */

Want to add a language team page? You can use and customize the [[Language Team Template]] to get started.
<div style="float:right; margin-left:2.5em">__TOC__</div>
==Language Team Pages==

{| class="wikitable sortable"
|-
! Language Team
! [https://en.wikipedia.org/wiki/List_of_ISO_639-1_codes ISO 639-1] Codes
|-
| [[Afrikaans]]
| af
|-
| [[Amharic]]
| am
|-
| [[Arabic]]
| ar
|-
| [[Burmese]]
| my
|-
| [[Catalan]]
| ca
|-
| [[Chinese (simplified)]]
| zh, zh_CH, zh-Hans
|-
| [[Chinese (traditional]]
| zh, zh_TW, zh-Hant
|-
| [[Dutch]] & Frysk
| nl, nl_BE, fy
|-
| [[French]]
| fr
|-
| [[German]]
| de
|-
| [[Greek]]
| el
|-
| [[Indonesian (Bahasa)]]
| id
|-
| [[Kannada]]
| kn
|-
| [[Khmer]]
| km
|-
| [[Kurdish (Kurmanji)]]
| kmr
|-
| [[Kurdish (Sorani)]]
| ckb
|-
| [[Luganda]]
| lg
|-
| [[Malayalam]]
| ml
|-
| [[Oromo]]
| om
|-
| [[Persian]]
| fa
|-
| [[Portuguese (Portugal)]]
| pt, pt_PT
|-
| [[Portuguese (Brazilian)]]
| pt_BR
|-
| [[Serbian]]
| sr
|-
| [[Shona]]
| sn
|-
| [[Spanish]]
| es
|-
| [[Swahili]]
| sw
|-
| [[Tigrinya]]
| ti
|-
| [[Thai]]
| th
|-
| [[Turkish]]
| tr
|-
| [[Turkmen]]
| tk
|-
| [[Ukrainian]]
| uk
|}

==Multi-Lingual Glossaries==
* [https://www.wikipedia.org/ Wikipedia] *Search for a term in English and refer to the "Languages" section in the sidebar to see if a page for that term exists in your language. You can also add terms yourself: "[https://en.wikipedia.org/wiki/Wikipedia:Translation#How_to_translate How to Translate]"

* [https://www.microsoft.com/Language/en-US/Search.aspx Microsoft Language Portal Searchable Terminologies]

* [http://www.it46.se/glossmaster/ African Network for Localization FOSS Glossaries] *Glossaries are downloadable as CSV and are available for Akan, Arabic, Amharic, French, Kinyarwanda, Lingala, Luganda, Songhay, Yoruba, and Zulu.

* Electronic Frontier Foundation's [https://ssd.eff.org/en/glossary Security Self-Defense Glossary] *Available in: Amharic, Arabic, French, Russian, Spanish, Thai, Turkish, Vietnamese, Urdu

==Multi-Lingual Style Guides==
* [https://www.microsoft.com/en-US/Language/StyleGuides Microsoft Language Portal Downloadable Style Guides] 
* [https://wiki.mozilla.org/Category:L10n_Teams Mozilla Language Team Resources] *Find your language by its [https://www.loc.gov/standards/iso639-2/php/code_list.php ISO 639-1/2 code]

==Terminology & Glossary Planning==
===Term Planning===
[http://www.terminfo.fi/sisalto/term-planning-for-irish--and-other-languages-85.html Term planning for Irish – and other languages]

Language Resources

2021-04-15T15:33:20Z

Meteor0id: readability improvement

Want to add a language team page? You can use and customize the [[Language Team Template]] to get started.
<div style="float:right; margin-left:2.5em">__TOC__</div>
==Language Team Pages==

{| class="wikitable sortable"
|-
! Language Team
! [https://en.wikipedia.org/wiki/List_of_ISO_639-1_codes ISO 639-1] Codes
|-
| [[Afrikaans]]
| af
|-
| [[Amharic]]
| am
|-
| [[Arabic]]
| ar
|-
| [[Burmese]]
| my
|-
| [[Catalan]]
| ca
|-
| [[Chinese (simplified)]]
| zh, zh_CH, zh-Hans
|-
| [[Chinese (traditional]]
| zh, zh_TW, zh-Hant
|-
| [[Dutch]] & Frysk
| nl, nl_BE, fy
|-
| [[French]]
| fr
|-
| [[German]]
| de
|-
| [[Greek]]
| el
|-
| [[Indonesian (Bahasa)]]
| id
|-
| [[Kannada]]
| kn
|-
| [[Khmer]]
| km
|-
| [[Kurdish (Kurmanji)]]
| kmr
|-
| [[Kurdish (Sorani)]]
| ckb
|-
| [[Luganda]]
| lg
|-
| [[Malayalam]]
| ml
|-
| [[Oromoo (Afaan)]]
| om
|-
| [[Persian]]
| fa
|-
| [[Portuguese (Portugal]]
| pt, pt_PT
|-
| [[Portuguese (Brazilian)]]
| pt_BR
|-
| [[Serbian]]
| sr
|-
| [[Shona]]
| sn
|-
| [[Spanish]]
| es
|-
| [[Swahili]]
| sw
|-
| [[Tigrinya]]
| ti
|-
| [[Thai]]
| th
|-
| [[Turkish]]
| tr
|-
| [[Turkmen]]
| tk
|-
| [[Ukrainian]]
| uk
|}

==Multi-Lingual Glossaries==
* [https://www.wikipedia.org/ Wikipedia] *Search for a term in English and refer to the "Languages" section in the sidebar to see if a page for that term exists in your language. You can also add terms yourself: "[https://en.wikipedia.org/wiki/Wikipedia:Translation#How_to_translate How to Translate]"

* [https://www.microsoft.com/Language/en-US/Search.aspx Microsoft Language Portal Searchable Terminologies]

* [http://www.it46.se/glossmaster/ African Network for Localization FOSS Glossaries] *Glossaries are downloadable as CSV and are available for Akan, Arabic, Amharic, French, Kinyarwanda, Lingala, Luganda, Songhay, Yoruba, and Zulu.

* Electronic Frontier Foundation's [https://ssd.eff.org/en/glossary Security Self-Defense Glossary] *Available in: Amharic, Arabic, French, Russian, Spanish, Thai, Turkish, Vietnamese, Urdu

==Multi-Lingual Style Guides==
* [https://www.microsoft.com/en-US/Language/StyleGuides Microsoft Language Portal Downloadable Style Guides] 
* [https://wiki.mozilla.org/Category:L10n_Teams Mozilla Language Team Resources] *Find your language by its [https://www.loc.gov/standards/iso639-2/php/code_list.php ISO 639-1/2 code]

==Terminology & Glossary Planning==
===Term Planning===
[http://www.terminfo.fi/sisalto/term-planning-for-irish--and-other-languages-85.html Term planning for Irish – and other languages]

Dutch

2021-04-15T15:29:24Z

Meteor0id:

__TOC__

==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 [https://internetfreedomfestival.org/ International Freedom Festival] domain and is subject to their [https://www.internetfreedomfestival.org/wiki/index.php/Code_of_Conduct Code of Conduct]. Be sure to read through the [https://www.internetfreedomfestival.org/wiki/index.php/Code_of_Conduct Code of Conduct] and then [mailto:info@localizationlab.org?subject=Mattermost%20Sign-up&body=Please%20send%20me%20a%20link%20to%20sign%20up%20for%20Mattermost. 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==
Ask yourself: "If my 65 year old mother read this (who has a total of 3 apps on her phone and uses only one of them on a weekly basis), would she understand this without anyone's help?". The goal is not to translate words, the goal is to make the text understandable to people who grew up in a different country.

===Signal Messenger===
''This Style guide is a result of reviewers communicating about inconsistencies and solutions to those. 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. We will try to make this style guide easier to read in the future.''

* The most important rule to always keep in question yourself who your audience will be and whether they will fully understand it. Yes, you are doing this work on behave of the Signal developers, but your audience are Signal users. Place yourself in the frame of mind of a Signal user who doesn't really know much about Signal and is trying to understand his options. Don't just translate literary, translate in such a way that it makes sense, is accurate, and is easy to read for the end user.
* 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. 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, meaning different words and/or a different structure of the sentence. An example: "Signal needs location services enabled to discover and connect with your old Android device." is localized as "Om je oude Android apparaat te kunnen detecteren en om er verbinding mee te maken is het nodig dat locatiebepaling op je apparaat is ingeschakeld.". Another example: don't write "Om het in te schakelen, tik op de schuifknop zodat hij blauw wordt." but instead write "Tik op de schuifknop zodat hij blauw wordt om meekijkpreventie in te schakelen."
* 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 punctuation, end the sentence with a period. If the description does not contain any punctuation, 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 Dutch people also get it wrong. [https://www.dutchgrammar.com/en/?n=WordOrder.00] 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. An example: Don't write "Deze personen kunnen door jou niet direct worden toegevoegd aan de groep." instead write "Deze personen kunnen door jou niet direct aan de groep worden toegevoegd.".
* 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 white space: 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 …
* Make sure the subject is repeated in every new sentence, do not refer back to a previous sentence. We do this to keep texts easy to read and understand. An example: do not write "Turing this on allows you to receive emails. They will contain information about your account." instead write "Turning this on allows you to receive emails. The emails you will receive contain information about your account.".
* Avoid anglicisms, our job is to localize the content so it can be understood by as many people as possible, that includes people who don't understand even the most common of English words.
* For units we follow the Si-standards. That means we translate 20MB as 20 MB with a white space. Kilobytes as kB. Note that Signal does not use KiB, MiB etc, because Signal is following the same units as the Android operating system. The same rule applies to other units such as 10s becoming 10 s. Abbreviations for minutes, months and weeks are not si units but we agreed to translate those as "min", "mnd" and "w". Capitalization matters.
* The text strings for the app store sometimes contain wordplay. If a good wordplay in Dutch can't be found, than rather leave the word joke out and just factually describe the change.
* Use pronoun + "wie" instead of "die" wherever possible. Read [https://taaladvies.net/taal/advies/vraag/1564 Taaladvies about wie/die] about where to use "wie" and where to use "die". This is a style choice we made to make complex sentences easier to comprehend.
* Use "van wie", "bij wie", "op wie" and "voor wie" instead of "waarvan", "waarmee", "waarop" and "waarvoor" wherever possible.
* For texts on buttons in Android and Desktop: use "Aan gesprek deelnemen", "Aan Signal doneren" and "Alice toevoegen". Do not use "Voeg Alice toe" or "Deelnemen aan gesprek" or "Doneren aan Signal". reason for this is optial readability. Also capitalize the first letter. on iOS we have not yet decided on the style, because that operating system often uses 'gebiedende wijs' rather than 'infinitief'.
* Try to stick to Dutch words, even if you see English words being used in other apps: "timer" becomes "tijdspanne", "admin" "beheerder", "checkbox" "selectievakje of aankruisvakje", "updaten" "bijwerken", "icon" "pictogram", "non-profit" "organisatie zonder winstoogmerk", "error" "fout", "database""databank" etc. You can find words like these listed in the Transifex Glossary for the Dutch Signal project.
* Beware of capitalization: use "QR-code" do not use "QR-Code" or "qr-code". "WiFi" is spelled different in Dutch: "wifi" all lowercase and without a dash. You can find words like these listed in the Transifex Glossary for the Dutch Signal project.
* Use [https://onzetaal.nl/taaladvies/signaalwoorden-lijst/ signal words] (words that indicate summation, contradiction etc.) wherever possible.
* Use formal verbs where their is no difference in meaning: use "je kunt" not "je kan". Howerver for "kun je" versus "kan je" there is a minor difference: "kan je" is more proposing while "kun je" is more forcefully suggestive. Therefore we use "kan je" instead of "kun je", and "zal je" instead of "zul je". [https://taalhelden.org/bericht/het-kan-je-kun-je https://taalhelden.org/bericht/het-kan-je-kun-je]
* Don't forget that although in English articles can be omitted, in Dutch it's not an accepted practice to omit the article. For example: "Playback time of audio attachment" should be localized as "Afspeellengte van HET audiobericht".
* Don't use possessive pronounce for things the user isn't possessing: Don't write "Open Signal-Desktop en gebruik de sneltoetsen om je tekstgrootte aan te passen.", instead write "Open Signal-Desktop en gebruik de sneltoetsen om de tekstgrootte aan te passen.". Users don't have font size, Signal has font size.
* We consistently use only the ‘rode werkwoordsvolgorde’, never the ‘groene werkwoordsvolgorde’. This means we never write "... vertrokken is." but instead always write "... is vertrokken.". For more information about verb order: [https://onzetaal.nl/taaladvies/rode-groene-volgorde/ https://onzetaal.nl/taaladvies/rode-groene-volgorde/]

Extra example:
* Don't localize "Other Signal users who are saved to your phone's contact list." as "Andere Signal-gebruikers die zijn opgeslagen in jouw telefoons contactenlijst." but instead localize it as "Andere Signal-gebruikers van wie het telefoonnummer voor komt in de systeemcontactenlijst van jouw telefoon."

===Other projects===
For other projects the style has not yet been written down, however some translators seem to hold on to [http://download.microsoft.com/download/4/7/e/47e135ad-15d7-4491-be78-369804f0d333/nld-nld-StyleGuide.pdf a style guide from Microsoft].

==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.
* ANY time you edit a translation on a project with multiple separate resources, make sure to open all the resources and check if the same string exists elsewhere to apply the exact same edit there. An example would be when you edit a string in the Android Signal messenger app, make sure to also check if the same string exists in the Desktop app, the iOS app, the website or the support center. It's not easy for other reviewers to spot the inconsistency later, so do this right away at the very moment you make an edit.
* Be extra careful with plurals in Transifex, it's easy to miss one of the plural forms when reviewing. You can check all plurals again by searching for pluralized:yes
* Found a spelling mistake, grammar mistake, word order mistake or some word which is better substituted with another word? Don't just correct it when you see it and move on, check all the strings on all the resources for the same mistake or imperfection and correct that mistake on all the strings where it occurs. The moment you noticed something is the only opportunity to come up with a consistent solution across all the strings.

==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 punctuation is accurate, the capitalization is accurate, there are no double white spaces, and no missing white spaces
* 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.
* Don't just look at untranslated string, some strings are automatically translated by Transifex but might still be wrong because the context requires a different translation. use source_updated_after:dd-mm-yyyy to find all the new strings. Also check for edits made by others, using translation_updated_after:dd-mm-yyyy .

==Language varieties==
If you want to localize a project to a language variety which has strong similarities to Dutch and if there already exist good quality translations to Dutch, than it is recommended to base your translations of Dutch rather than English or an other source language. This may make translations faster, but more importantly it also keeps the texts consistent, so that someone who lives just across the border doesn't see completely different texts for the same project. In Transifex there is an option to swap which language you are using as the source language for your translations; you will find it by clicking the setting icon in the top right of the translation interface. Any string that have not yet been translated to Dutch will automatically still be shown as the original source language for the project (usually English).

===Flemish (nl_BE)===
If a project does not accept translations for nl_BE than unfortunately for Flanders, the languages nl and nl_NL will still follow Dutch standard language (Nederlandse standaardtaal). It is not acceptable to deliberately choose words and sentence structure which are understood by both language varieties, as that would reduce quality for both language varieties. If Flemish translators want to work on a project, they should contact a project maintainer and ask to add a nl_BE project. International Dutch (nl) is exactly the same as Dutch spoken in the Netherlands (nl_NL).

===Other varieties===
Other varieties are
* nl_AW Dutch (Aruba)
* nl_BQ Dutch (Caribbean Netherlands)
* nl_CW Dutch (Curaçao)
* nl_SR Dutch (Suriname)
* nl_SX Dutch (Sint Maarten)
* af (Afrikaans)
* fy_NL (Frisian)

==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.''

===Grammar and word order in sentences===
*[https://www.dutchgrammar.com/en/?n=WordOrder.00 https://www.dutchgrammar.com/en/?n=WordOrder.00] About word order in sentences. It's not just one page, keep clicking on next page in the bottom right to see more examples.
*[http://redekundig.nl/ http://redekundig.nl/] a tool to help identify the structure of a Dutch sentence. Very helpful if you're dealing with complex grammatical rules and need to understand the sentence you are reviewing.
* [https://urd2.let.rug.nl/~vannoord/bin/alpino https://urd2.let.rug.nl/~vannoord/bin/alpino] university hosted tool to identify structure of a Dutch sentence. It's the same tool as redekundig.nl but hosted elsewhere, and the interface is harder to comprehend. Would advise trying this in case redekundig.nl isn't giving you the information you need.
* [https://onzetaal.nl/taaladvies/signaalwoorden-lijst/ List of signal words], use these wherever possible, they help clarify your message and prevent ambiguity.

===Style and tone===
* First follow any style guide you find here on this wiki for language and project you are working on
* If you are missing something, contact other translators
* If you search for style advise from other websites, avoid getting it from tech companies who make up their own version of Dutch language based on marketing rather than proper standard Dutch. Also avoid other wiki's which are often written by opinionated people who are not representative for the language. That doesn't mean you can't read them and learn from them, but take it with a grain of salt.

===Spelling===
*[https://taaladvies.net Taaladvies]
*[https://taal.vrt.be Taalnet]
*[https://onzetaal.nl OnzeTaal]

===Technical terminology===
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:
[https://docs.google.com/spreadsheets/d/1OPyeWDq2rtPf9fEpCLRpHl9Hn--OfFbWLbrGtZx3lYI/edit?usp=sharing Dutch Unified Localization Lab Glossary]. The document is maintained by Erin (a localization lab employee). If you wish to add comments, edits or suggest new entries, do so using the "Comment" feature in the spreadsheet.

Afrikaans

2021-04-15T15:28:40Z

Meteor0id: /* Grammar and word order in sentences */

Language Resources

2021-04-15T15:26:30Z

Meteor0id: split out some languages which are not varieties but are a language on their own

Want to add a language team page? You can use and customize the [[Language Team Template]] to get started.
<div style="float:right; margin-left:2.5em">__TOC__</div>
==Language Team Pages==

{| class="wikitable sortable"
|-
! Language Team
! [https://en.wikipedia.org/wiki/List_of_ISO_639-1_codes ISO 639-1] Codes
|-
| [[Afrikaans]]
| af
|-
| [[Amharic]]
| am
|-
| [[Arabic]]
| ar
|-
| [[Bahasa Indonesia]]
| id
|-
| [[Burmese]]
| my
|-
| [[Catalan]]
| ca
|-
| [[Simplified Chinese]]
| zh, zh_CH, zh-Hans
|-
| [[Traditional Chinese]]
| zh, zh_TW, zh-Hant
|-
| [[Dutch]] & Frysk
| nl, nl_BE, fy
|-
| [[French]]
| fr
|-
| [[German]]
| de
|-
| [[Greek]]
| el
|-
| [[Kannada]]
| kn
|-
| [[Khmer]]
| km
|-
| [[Kurdish (Kurmanji)]]
| kmr
|-
| [[Kurdish (Sorani)]]
| ckb
|-
| [[Luganda]]
| lg
|-
| [[Malayalam]]
| ml
|-
| [[Afaan Oromoo]]
| om
|-
| [[Persian]]
| fa
|-
| [[Portuguese]]
| pt, pt_PT
|-
| [[Brazilian Portuguese]]
| pt_BR
|-
| [[Serbian]]
| sr
|-
| [[Shona]]
| sn
|-
| [[Spanish]]
| es
|-
| [[Swahili]]
| sw
|-
| [[Tigrinya]]
| ti
|-
| [[Thai]]
| th
|-
| [[Turkish]]
| tr
|-
| [[Turkmen]]
| tk
|-
| [[Ukrainian]]
| uk
|}

==Multi-Lingual Glossaries==
* [https://www.wikipedia.org/ Wikipedia] *Search for a term in English and refer to the "Languages" section in the sidebar to see if a page for that term exists in your language. You can also add terms yourself: "[https://en.wikipedia.org/wiki/Wikipedia:Translation#How_to_translate How to Translate]"

* [https://www.microsoft.com/Language/en-US/Search.aspx Microsoft Language Portal Searchable Terminologies]

* [http://www.it46.se/glossmaster/ African Network for Localization FOSS Glossaries] *Glossaries are downloadable as CSV and are available for Akan, Arabic, Amharic, French, Kinyarwanda, Lingala, Luganda, Songhay, Yoruba, and Zulu.

* Electronic Frontier Foundation's [https://ssd.eff.org/en/glossary Security Self-Defense Glossary] *Available in: Amharic, Arabic, French, Russian, Spanish, Thai, Turkish, Vietnamese, Urdu

==Multi-Lingual Style Guides==
* [https://www.microsoft.com/en-US/Language/StyleGuides Microsoft Language Portal Downloadable Style Guides] 
* [https://wiki.mozilla.org/Category:L10n_Teams Mozilla Language Team Resources] *Find your language by its [https://www.loc.gov/standards/iso639-2/php/code_list.php ISO 639-1/2 code]

==Terminology & Glossary Planning==
===Term Planning===
[http://www.terminfo.fi/sisalto/term-planning-for-irish--and-other-languages-85.html Term planning for Irish – and other languages]

Portuguese (Brazilian)

2021-04-15T15:26:24Z

Meteor0id: Create page, template based on Dutch localization page

Afrikaans

2021-04-15T15:25:13Z

Meteor0id: Created page, template based on Dutch localization page

Dutch

2021-04-01T20:31:14Z

Meteor0id: /* Signal Messenger */

__TOC__

==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 [https://internetfreedomfestival.org/ International Freedom Festival] domain and is subject to their [https://www.internetfreedomfestival.org/wiki/index.php/Code_of_Conduct Code of Conduct]. Be sure to read through the [https://www.internetfreedomfestival.org/wiki/index.php/Code_of_Conduct Code of Conduct] and then [mailto:info@localizationlab.org?subject=Mattermost%20Sign-up&body=Please%20send%20me%20a%20link%20to%20sign%20up%20for%20Mattermost. 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==
Ask yourself: "If my 65 year old mother read this (who has a total of 3 apps on her phone and uses only one of them on a weekly basis), would she understand this without anyone's help?". The goal is not to translate words, the goal is to make the text understandable to people who grew up in a different country.

===Signal Messenger===
''This Style guide is a result of reviewers communicating about inconsistencies and solutions to those. 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. We will try to make this style guide easier to read in the future.''

* The most important rule to always keep in question yourself who your audience will be and whether they will fully understand it. Yes, you are doing this work on behave of the Signal developers, but your audience are Signal users. Place yourself in the frame of mind of a Signal user who doesn't really know much about Signal and is trying to understand his options. Don't just translate literary, translate in such a way that it makes sense, is accurate, and is easy to read for the end user.
* 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. 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, meaning different words and/or a different structure of the sentence. An example: "Signal needs location services enabled to discover and connect with your old Android device." is localized as "Om je oude Android apparaat te kunnen detecteren en om er verbinding mee te maken is het nodig dat locatiebepaling op je apparaat is ingeschakeld.". Another example: don't write "Om het in te schakelen, tik op de schuifknop zodat hij blauw wordt." but instead write "Tik op de schuifknop zodat hij blauw wordt om meekijkpreventie in te schakelen."
* 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 punctuation, end the sentence with a period. If the description does not contain any punctuation, 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 Dutch people also get it wrong. [https://www.dutchgrammar.com/en/?n=WordOrder.00] 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. An example: Don't write "Deze personen kunnen door jou niet direct worden toegevoegd aan de groep." instead write "Deze personen kunnen door jou niet direct aan de groep worden toegevoegd.".
* 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 white space: 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 …
* Make sure the subject is repeated in every new sentence, do not refer back to a previous sentence. We do this to keep texts easy to read and understand. An example: do not write "Turing this on allows you to receive emails. They will contain information about your account." instead write "Turning this on allows you to receive emails. The emails you will receive contain information about your account.".
* Avoid anglicisms, our job is to localize the content so it can be understood by as many people as possible, that includes people who don't understand even the most common of English words.
* For units we follow the Si-standards. That means we translate 20MB as 20 MB with a white space. Kilobytes as kB. Note that Signal does not use KiB, MiB etc, because Signal is following the same units as the Android operating system. The same rule applies to other units such as 10s becoming 10 s. Abbreviations for minutes, months and weeks are not si units but we agreed to translate those as "min", "mnd" and "w". Capitalization matters.
* The text strings for the app store sometimes contain wordplay. If a good wordplay in Dutch can't be found, than rather leave the word joke out and just factually describe the change.
* Use pronoun + "wie" instead of "die" wherever possible. Read [https://taaladvies.net/taal/advies/vraag/1564 Taaladvies about wie/die] about where to use "wie" and where to use "die". This is a style choice we made to make complex sentences easier to comprehend.
* Use "van wie", "bij wie", "op wie" and "voor wie" instead of "waarvan", "waarmee", "waarop" and "waarvoor" wherever possible.
* For texts on buttons in Android and Desktop: use "Aan gesprek deelnemen", "Aan Signal doneren" and "Alice toevoegen". Do not use "Voeg Alice toe" or "Deelnemen aan gesprek" or "Doneren aan Signal". reason for this is optial readability. Also capitalize the first letter. on iOS we have not yet decided on the style, because that operating system often uses 'gebiedende wijs' rather than 'infinitief'.
* Try to stick to Dutch words, even if you see English words being used in other apps: "timer" becomes "tijdspanne", "admin" "beheerder", "checkbox" "selectievakje of aankruisvakje", "updaten" "bijwerken", "icon" "pictogram", "non-profit" "organisatie zonder winstoogmerk", "error" "fout", "database""databank" etc. You can find words like these listed in the Transifex Glossary for the Dutch Signal project.
* Beware of capitalization: use "QR-code" do not use "QR-Code" or "qr-code". "WiFi" is spelled different in Dutch: "wifi" all lowercase and without a dash. You can find words like these listed in the Transifex Glossary for the Dutch Signal project.
* Use [https://onzetaal.nl/taaladvies/signaalwoorden-lijst/ signal words] (words that indicate summation, contradiction etc.) wherever possible.
* Use formal verbs where their is no difference in meaning: use "je kunt" not "je kan". Howerver for "kun je" versus "kan je" there is a minor difference: "kan je" is more proposing while "kun je" is more forcefully suggestive. Therefore we use "kan je" instead of "kun je", and "zal je" instead of "zul je". [https://taalhelden.org/bericht/het-kan-je-kun-je https://taalhelden.org/bericht/het-kan-je-kun-je]
* Don't forget that although in English articles can be omitted, in Dutch it's not an accepted practice to omit the article. For example: "Playback time of audio attachment" should be localized as "Afspeellengte van HET audiobericht".
* Don't use possessive pronounce for things the user isn't possessing: Don't write "Open Signal-Desktop en gebruik de sneltoetsen om je tekstgrootte aan te passen.", instead write "Open Signal-Desktop en gebruik de sneltoetsen om de tekstgrootte aan te passen.". Users don't have font size, Signal has font size.
* We consistently use only the ‘rode werkwoordsvolgorde’, never the ‘groene werkwoordsvolgorde’. This means we never write "... vertrokken is." but instead always write "... is vertrokken.". For more information about verb order: [https://onzetaal.nl/taaladvies/rode-groene-volgorde/ https://onzetaal.nl/taaladvies/rode-groene-volgorde/]

Extra example:
* Don't localize "Other Signal users who are saved to your phone's contact list." as "Andere Signal-gebruikers die zijn opgeslagen in jouw telefoons contactenlijst." but instead localize it as "Andere Signal-gebruikers van wie het telefoonnummer voor komt in de systeemcontactenlijst van jouw telefoon."

===Other projects===
For other projects the style has not yet been written down, however some translators seem to hold on to [http://download.microsoft.com/download/4/7/e/47e135ad-15d7-4491-be78-369804f0d333/nld-nld-StyleGuide.pdf a style guide from Microsoft].

==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.
* ANY time you edit a translation on a project with multiple separate resources, make sure to open all the resources and check if the same string exists elsewhere to apply the exact same edit there. An example would be when you edit a string in the Android Signal messenger app, make sure to also check if the same string exists in the Desktop app, the iOS app, the website or the support center. It's not easy for other reviewers to spot the inconsistency later, so do this right away at the very moment you make an edit.
* Be extra careful with plurals in Transifex, it's easy to miss one of the plural forms when reviewing. You can check all plurals again by searching for pluralized:yes
* Found a spelling mistake, grammar mistake, word order mistake or some word which is better substituted with another word? Don't just correct it when you see it and move on, check all the strings on all the resources for the same mistake or imperfection and correct that mistake on all the strings where it occurs. the moment you noticed something is the only opportunity to come up with a consistent solution across all the strings.

==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 punctuation is accurate, the capitalization is accurate, there are no double white spaces, and no missing white spaces
* 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.
* Don't just look at untranslated string, some strings are automatically translated by Transifex but might still be wrong because the context requires a different translation. use source_updated_after:dd-mm-yyyy to find all the new strings. Also check for edits made by others, using translation_updated_after:dd-mm-yyyy .

==Language varieties==
If you want to localize a project to a language variety which has strong similarities to Dutch and if there already exist good quality translations to Dutch, than it is recommended to base your translations of Dutch rather than English or an other source language. This may make translations faster, but more importantly it also keeps the texts consistent, so that someone who lives just across the border doesn't see completely different texts for the same project. In Transifex there is an option to swap which language you are using as the source language for your translations; you will find it by clicking the setting icon in the top right of the translation interface. Any string that have not yet been translated to Dutch will automatically still be shown as the original source language for the project (usually English).

===Flemish (nl_BE)===
If a project does not accept translations for nl_BE than unfortunately for Flanders, the languages nl and nl_NL will still follow Dutch standard language (Nederlandse standaardtaal). It is not acceptable to deliberately choose words and sentence structure which are understood by both language varieties, as that would reduce quality for both language varieties. If Flemish translators want to work on a project, they should contact a project maintainer and ask to add a nl_BE project. International Dutch (nl) is exactly the same as Dutch spoken in the Netherlands (nl_NL).

===Other varieties===
Other varieties are
* nl_AW Dutch (Aruba)
* nl_BQ Dutch (Caribbean Netherlands)
* nl_CW Dutch (Curaçao)
* nl_SR Dutch (Suriname)
* nl_SX Dutch (Sint Maarten)
* af (Afrikaans)
* fy_NL (Frisian)

==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.''

===Grammer and word order in sentences===
*[https://www.dutchgrammar.com/en/?n=WordOrder.00 https://www.dutchgrammar.com/en/?n=WordOrder.00] About word order in sentences. It's not just one page, keep clicking on next page in the bottom right to see more examples.
*[http://redekundig.nl/ http://redekundig.nl/] a tool to help identify the structure of a Dutch sentence. Very helpful if you're dealing with complex grammatical rules and need to understand the sentence you are reviewing.
* [https://urd2.let.rug.nl/~vannoord/bin/alpino https://urd2.let.rug.nl/~vannoord/bin/alpino] university hosted tool to identify structure of a Dutch sentence. It's the same tool as redekundig.nl but hosted elsewhere, and the interface is harder to comprehend. Would advise trying this in case redekundig.nl isn't giving you the information you need.
* [https://onzetaal.nl/taaladvies/signaalwoorden-lijst/ List of signal words], use these wherever possible, they help clarify your message and prevent ambiguity.

===Style and tone===
* First follow any style guide you find here on this wiki for language and project you are working on
* If you are missing something, contact other translators
* If you search for style advise from other websites, avoid getting it from tech companies who make up their own version of Dutch language based on marketing rather than proper standard Dutch. Also avoid other wiki's which are often written by opinionated people who are not representative for the language. That doesn't mean you can't read them and learn from them, but take it with a grain of salt.

===Spelling===
*[https://taaladvies.net Taaladvies]
*[https://taal.vrt.be Taalnet]
*[https://onzetaal.nl OnzeTaal]

===Technical terminology===
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:
[https://docs.google.com/spreadsheets/d/1OPyeWDq2rtPf9fEpCLRpHl9Hn--OfFbWLbrGtZx3lYI/edit?usp=sharing Dutch Unified Localization Lab Glossary]. The document is maintained by Erin (a localization lab employee). If you wish to add comments, edits or suggest new entries, do so using the "Comment" feature in the spreadsheet.

Dutch

2021-03-24T19:57:39Z

Meteor0id: /* Signal Messenger */

__TOC__

==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 [https://internetfreedomfestival.org/ International Freedom Festival] domain and is subject to their [https://www.internetfreedomfestival.org/wiki/index.php/Code_of_Conduct Code of Conduct]. Be sure to read through the [https://www.internetfreedomfestival.org/wiki/index.php/Code_of_Conduct Code of Conduct] and then [mailto:info@localizationlab.org?subject=Mattermost%20Sign-up&body=Please%20send%20me%20a%20link%20to%20sign%20up%20for%20Mattermost. 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==
Ask yourself: "If my 65 year old mother read this (who has a total of 3 apps on her phone and uses only one of them on a weekly basis), would she understand this without anyone's help?". The goal is not to translate words, the goal is to make the text understandable to people who grew up in a different country.

===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. We will try to make this styleguide easier to read in the future.''

* 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. 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, meaning different words and/or a different structure of the sentence. An example: "Signal needs location services enabled to discover and connect with your old Android device." is localized as "Om je oude Android apparaat te kunnen detecteren en om er verbinding mee te maken is het nodig dat locatiebepaling op je apparaat is ingeschakeld.". Another example: don't write "Om het in te schakelen, tik op de schuifknop zodat hij blauw wordt." but instead write "Tik op de schuifknop zodat hij blauw wordt om meekijkpreventie in te schakelen."
* 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 punctuation, end the sentence with a period. If the description does not contain any punctuation, 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 Dutch people also get it wrong. [https://www.dutchgrammar.com/en/?n=WordOrder.00] 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. An example: Don't write "Deze personen kunnen door jou niet direct worden toegevoegd aan de groep." instead write "Deze personen kunnen door jou niet direct aan de groep worden toegevoegd.".
* 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 white space: 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 …
* Make sure the subject is repeated in every new sentence, do not refer back to a previous sentence. We do this to keep texts easy to read and understand. An example: do not write "Turing this on allows you to receive emails. They will contain information about your account." instead write "Turning this on allows you to receive emails. The emails you will receive contain information about your account.".
* Avoid anglicisms, our job is to localize the content so it can be understood by as many people as possible, that includes people who don't understand even the most common of English words.
* For units we follow the Si-standards. That means we translate 20MB as 20 MB with a white space. Kilobytes as kB. Note that Signal does not use KiB, MiB etc, because Signal is following the same units as the Android operating system. The same rule applies to other units such as 10s becoming 10 s. Abbreviations for minutes, months and weeks are not si units but we agreed to translate those as "min", "mnd" and "w". Capitalization matters.
* The text strings for the app store sometimes contain wordplay. If a good wordplay in Dutch can't be found, than rather leave the word joke out and just factually describe the change.
* Use pronoun + "wie" instead of "die" wherever possible. Read [https://taaladvies.net/taal/advies/vraag/1564 Taaladvies about wie/die] about where to use "wie" and where to use "die". This is a style choice we made to make complex sentences easier to comprehend.
* Use "van wie", "bij wie", "op wie" and "voor wie" instead of "waarvan", "waarmee", "waarop" and "waarvoor" wherever possible.
* For texts on buttons in Android and Desktop: use "Aan gesprek deelnemen", "Aan Signal doneren" and "Alice toevoegen". Do not use "Voeg Alice toe" or "Deelnemen aan gesprek" or "Doneren aan Signal". reason for this is optial readability. Also capitalize the first letter. on iOS we have not yet decided on the style, because that operating system often uses 'gebiedende wijs' rather than 'infinitief'.
* Try to stick to Dutch words, even if you see English words being used in other apps: "timer" becomes "tijdspanne", "admin" "beheerder", "checkbox" "selectievakje of aankruisvakje", "updaten" "bijwerken", "icon" "pictogram", "non-profit" "organisatie zonder winstoogmerk", "error" "fout", "database""databank" etc. You can find words like these listed in the Transifex Glossary for the Dutch Signal project.
* Beware of capitalization: use "QR-code" do not use "QR-Code" or "qr-code". "WiFi" is spelled different in Dutch: "wifi" all lowercase and without a dash. You can find words like these listed in the Transifex Glossary for the Dutch Signal project.
* Use [https://onzetaal.nl/taaladvies/signaalwoorden-lijst/ signal words] (words that indicate summation, contradiction etc.) wherever possible.
* Use formal verbs where their is no difference in meaning: use "je kunt" not "je kan". Howerver for "kun je" versus "kan je" there is a minor difference: "kan je" is more proposing while "kun je" is more forcefully suggestive. Therefore we use "kan je" instead of "kun je", and "zal je" instead of "zul je". [https://taalhelden.org/bericht/het-kan-je-kun-je https://taalhelden.org/bericht/het-kan-je-kun-je]
* Don't forget that although in English articles can be omitted, in Dutch it's not an accepted practice to omit the article. For example: "Playback time of audio attachment" should be localized as "Afspeellengte van HET audiobericht".
* Don't use possessive pronounce for things the user isn't possessing: Don't write "Open Signal-Desktop en gebruik de sneltoetsen om je tekstgrootte aan te passen.", instead write "Open Signal-Desktop en gebruik de sneltoetsen om de tekstgrootte aan te passen.". Users don't have font size, Signal has font size.
* We consistently use only the ‘rode werkwoordsvolgorde’, never the ‘groene werkwoordsvolgorde’. This means we never write "... vertrokken is." but instead always write "... is vertrokken.". For more information about verb order: [https://onzetaal.nl/taaladvies/rode-groene-volgorde/ https://onzetaal.nl/taaladvies/rode-groene-volgorde/]

Extra example:
* Don't localize "Other Signal users who are saved to your phone's contact list." as "Andere Signal-gebruikers die zijn opgeslagen in jouw telefoons contactenlijst." but instead localize it as "Andere Signal-gebruikers van wie het telefoonnummer voor komt in de systeemcontactenlijst van jouw telefoon."

===Other projects===
For other projects the style has not yet been written down, however some translators seem to hold on to [http://download.microsoft.com/download/4/7/e/47e135ad-15d7-4491-be78-369804f0d333/nld-nld-StyleGuide.pdf a style guide from Microsoft].

==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.
* ANY time you edit a translation on a project with multiple separate resources, make sure to open all the resources and check if the same string exists elsewhere to apply the exact same edit there. An example would be when you edit a string in the Android Signal messenger app, make sure to also check if the same string exists in the Desktop app, the iOS app, the website or the support center. It's not easy for other reviewers to spot the inconsistency later, so do this right away at the very moment you make an edit.
* Be extra careful with plurals in Transifex, it's easy to miss one of the plural forms when reviewing. You can check all plurals again by searching for pluralized:yes
* Found a spelling mistake, grammar mistake, word order mistake or some word which is better substituted with another word? Don't just correct it when you see it and move on, check all the strings on all the resources for the same mistake or imperfection and correct that mistake on all the strings where it occurs. the moment you noticed something is the only opportunity to come up with a consistent solution across all the strings.

==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 punctuation is accurate, the capitalization is accurate, there are no double white spaces, and no missing white spaces
* 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.
* Don't just look at untranslated string, some strings are automatically translated by Transifex but might still be wrong because the context requires a different translation. use source_updated_after:dd-mm-yyyy to find all the new strings. Also check for edits made by others, using translation_updated_after:dd-mm-yyyy .

==Language varieties==
If you want to localize a project to a language variety which has strong similarities to Dutch and if there already exist good quality translations to Dutch, than it is recommended to base your translations of Dutch rather than English or an other source language. This may make translations faster, but more importantly it also keeps the texts consistent, so that someone who lives just across the border doesn't see completely different texts for the same project. In Transifex there is an option to swap which language you are using as the source language for your translations; you will find it by clicking the setting icon in the top right of the translation interface. Any string that have not yet been translated to Dutch will automatically still be shown as the original source language for the project (usually English).

===Flemish (nl_BE)===
If a project does not accept translations for nl_BE than unfortunately for Flanders, the languages nl and nl_NL will still follow Dutch standard language (Nederlandse standaardtaal). It is not acceptable to deliberately choose words and sentence structure which are understood by both language varieties, as that would reduce quality for both language varieties. If Flemish translators want to work on a project, they should contact a project maintainer and ask to add a nl_BE project. International Dutch (nl) is exactly the same as Dutch spoken in the Netherlands (nl_NL).

===Other varieties===
Other varieties are
* nl_AW Dutch (Aruba)
* nl_BQ Dutch (Caribbean Netherlands)
* nl_CW Dutch (Curaçao)
* nl_SR Dutch (Suriname)
* nl_SX Dutch (Sint Maarten)
* af (Afrikaans)
* fy_NL (Frisian)

==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.''

===Grammer and word order in sentences===
*[https://www.dutchgrammar.com/en/?n=WordOrder.00 https://www.dutchgrammar.com/en/?n=WordOrder.00] About word order in sentences. It's not just one page, keep clicking on next page in the bottom right to see more examples.
*[http://redekundig.nl/ http://redekundig.nl/] a tool to help identify the structure of a Dutch sentence. Very helpful if you're dealing with complex grammatical rules and need to understand the sentence you are reviewing.
* [https://urd2.let.rug.nl/~vannoord/bin/alpino https://urd2.let.rug.nl/~vannoord/bin/alpino] university hosted tool to identify structure of a Dutch sentence. It's the same tool as redekundig.nl but hosted elsewhere, and the interface is harder to comprehend. Would advise trying this in case redekundig.nl isn't giving you the information you need.
* [https://onzetaal.nl/taaladvies/signaalwoorden-lijst/ List of signal words], use these wherever possible, they help clarify your message and prevent ambiguity.

===Style and tone===
* First follow any style guide you find here on this wiki for language and project you are working on
* If you are missing something, contact other translators
* If you search for style advise from other websites, avoid getting it from tech companies who make up their own version of Dutch language based on marketing rather than proper standard Dutch. Also avoid other wiki's which are often written by opinionated people who are not representative for the language. That doesn't mean you can't read them and learn from them, but take it with a grain of salt.

===Spelling===
*[https://taaladvies.net Taaladvies]
*[https://taal.vrt.be Taalnet]
*[https://onzetaal.nl OnzeTaal]

===Technical terminology===
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:
[https://docs.google.com/spreadsheets/d/1OPyeWDq2rtPf9fEpCLRpHl9Hn--OfFbWLbrGtZx3lYI/edit?usp=sharing Dutch Unified Localization Lab Glossary]. The document is maintained by Erin (a localization lab employee). If you wish to add comments, edits or suggest new entries, do so using the "Comment" feature in the spreadsheet.

Dutch

2021-03-24T19:57:16Z

Meteor0id: /* Signal Messenger */

__TOC__

==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 [https://internetfreedomfestival.org/ International Freedom Festival] domain and is subject to their [https://www.internetfreedomfestival.org/wiki/index.php/Code_of_Conduct Code of Conduct]. Be sure to read through the [https://www.internetfreedomfestival.org/wiki/index.php/Code_of_Conduct Code of Conduct] and then [mailto:info@localizationlab.org?subject=Mattermost%20Sign-up&body=Please%20send%20me%20a%20link%20to%20sign%20up%20for%20Mattermost. 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==
Ask yourself: "If my 65 year old mother read this (who has a total of 3 apps on her phone and uses only one of them on a weekly basis), would she understand this without anyone's help?". The goal is not to translate words, the goal is to make the text understandable to people who grew up in a different country.

===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. We will try to make this styleguide easier to read in the future.''

* 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. 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, meaning different words and/or a different structure of the sentence. An example: "Signal needs location services enabled to discover and connect with your old Android device." is localized as "Om je oude Android apparaat te kunnen detecteren en om er verbinding mee te maken is het nodig dat locatiebepaling op je apparaat is ingeschakeld.". Another example: don't write "Om het in te schakelen, tik op de schuifknop zodat hij blauw wordt." but instead write "Tik op de schuifknop zodat hij blauw wordt om meekijkpreventie in te schakelen."
* 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 punctuation, end the sentence with a period. If the description does not contain any punctuation, 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 Dutch people also get it wrong. [https://www.dutchgrammar.com/en/?n=WordOrder.00] 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. An example: Don't write "Deze personen kunnen door jou niet direct worden toegevoegd aan de groep." instead write "Deze personen kunnen door jou niet direct aan de groep worden toegevoegd.".
* 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 white space: 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 …
* Make sure the subject is repeated in every new sentence, do not refer back to a previous sentence. We do this to keep texts easy to read and understand. An example: do not write "Turing this on allows you to receive emails. They will contain information about your account." instead write "Turning this on allows you to receive emails. The emails you will receive contain information about your account.".
* Avoid anglicisms, our job is to localize the content so it can be understood by as many people as possible, that includes people who don't understand even the most common of English words.
* For units we follow the Si-standards. That means we translate 20MB as 20 MB with a white space. Kilobytes as kB. Note that Signal does not use KiB, MiB etc, because Signal is following the same units as the Android operating system. The same rule applies to other units such as 10s becoming 10 s. Abbreviations for minutes, months and weeks are not si units but we agreed to translate those as "min", "mnd" and "w". Capitalization matters.
* The text strings for the app store sometimes contain wordplay. If a good wordplay in Dutch can't be found, than rather leave the word joke out and just factually describe the change.
* Use pronoun + "wie" instead of "die" wherever possible. Read [https://taaladvies.net/taal/advies/vraag/1564 Taaladvies about wie/die] about where to use "wie" and where to use "die". This is a style choice we made to make complex sentences easier to comprehend.
* Use "van wie", "bij wie", "op wie" and "voor wie" instead of "waarvan", "waarmee", "waarop" and "waarvoor" wherever possible.
* For texts on buttons in Android and Desktop: use "Aan gesprek deelnemen", "Aan Signal doneren" and "Alice toevoegen". Do not use "Voeg Alice toe" or "Deelnemen aan gesprek" or "Doneren aan Signal". reason for this is optial readability. Also capitalize the first letter. on iOS we have not yet decided on the style, because that operating system often uses 'gebiedende wijs' rather than 'infinitief'.
* Try to stick to Dutch words, even if you see English words being used in other apps: "timer" becomes "tijdspanne", "admin" "beheerder", "checkbox" "selectievakje of aankruisvakje", "updaten" "bijwerken", "icon" "pictogram", "non-profit" "organisatie zonder winstoogmerk", "error" "fout", "database""databank" etc. You can find words like these listed in the Transifex Glossary for the Dutch Signal project.
* Beware of capitalization: use "QR-code" do not use "QR-Code" or "qr-code". "WiFi" is spelled different in Dutch: "wifi" all lowercase and without a dash. You can find words like these listed in the Transifex Glossary for the Dutch Signal project.
* Use [https://onzetaal.nl/taaladvies/signaalwoorden-lijst/ signal words] (words that indicate summation, contradiction etc.) wherever possible.
* Use formal verbs where their is no difference in meaning: use "je kunt" not "je kan". Howerver for "kun je" versus "kan je" there is a minor difference: "kan je" is more proposing while "kun je" is more forcefully suggestive. Therefore we use "kan je" instead of "kun je", and "zal je" instead of "zul je". [https://taalhelden.org/bericht/het-kan-je-kun-je https://taalhelden.org/bericht/het-kan-je-kun-je]
* Don't forget that although in English articles can be omitted, in Dutch it's not an accepted practice to omit the article. For example: "Playback time of audio attachment" should be localized as "Afspeellengte van HET audiobericht".
* Don't use possessive pronounce for things the user isn't possessing: Don't write "Open Signal-Desktop en gebruik de sneltoetsen om je tekstgrootte aan te
passen.", instead write "Open Signal-Desktop en gebruik de sneltoetsen om de tekstgrootte aan te passen.". Users don't have font size, Signal has font size.
* We consistently use only the ‘rode werkwoordsvolgorde’, never the ‘groene werkwoordsvolgorde’. This means we never write "... vertrokken is." but instead always write "... is vertrokken.". For more information about verb order: [https://onzetaal.nl/taaladvies/rode-groene-volgorde/ https://onzetaal.nl/taaladvies/rode-groene-volgorde/]

Extra example:
* Don't localize "Other Signal users who are saved to your phone's contact list." as "Andere Signal-gebruikers die zijn opgeslagen in jouw telefoons contactenlijst." but instead localize it as "Andere Signal-gebruikers van wie het telefoonnummer voor komt in de systeemcontactenlijst van jouw telefoon."

===Other projects===
For other projects the style has not yet been written down, however some translators seem to hold on to [http://download.microsoft.com/download/4/7/e/47e135ad-15d7-4491-be78-369804f0d333/nld-nld-StyleGuide.pdf a style guide from Microsoft].

==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.
* ANY time you edit a translation on a project with multiple separate resources, make sure to open all the resources and check if the same string exists elsewhere to apply the exact same edit there. An example would be when you edit a string in the Android Signal messenger app, make sure to also check if the same string exists in the Desktop app, the iOS app, the website or the support center. It's not easy for other reviewers to spot the inconsistency later, so do this right away at the very moment you make an edit.
* Be extra careful with plurals in Transifex, it's easy to miss one of the plural forms when reviewing. You can check all plurals again by searching for pluralized:yes
* Found a spelling mistake, grammar mistake, word order mistake or some word which is better substituted with another word? Don't just correct it when you see it and move on, check all the strings on all the resources for the same mistake or imperfection and correct that mistake on all the strings where it occurs. the moment you noticed something is the only opportunity to come up with a consistent solution across all the strings.

==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 punctuation is accurate, the capitalization is accurate, there are no double white spaces, and no missing white spaces
* 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.
* Don't just look at untranslated string, some strings are automatically translated by Transifex but might still be wrong because the context requires a different translation. use source_updated_after:dd-mm-yyyy to find all the new strings. Also check for edits made by others, using translation_updated_after:dd-mm-yyyy .

==Language varieties==
If you want to localize a project to a language variety which has strong similarities to Dutch and if there already exist good quality translations to Dutch, than it is recommended to base your translations of Dutch rather than English or an other source language. This may make translations faster, but more importantly it also keeps the texts consistent, so that someone who lives just across the border doesn't see completely different texts for the same project. In Transifex there is an option to swap which language you are using as the source language for your translations; you will find it by clicking the setting icon in the top right of the translation interface. Any string that have not yet been translated to Dutch will automatically still be shown as the original source language for the project (usually English).

===Flemish (nl_BE)===
If a project does not accept translations for nl_BE than unfortunately for Flanders, the languages nl and nl_NL will still follow Dutch standard language (Nederlandse standaardtaal). It is not acceptable to deliberately choose words and sentence structure which are understood by both language varieties, as that would reduce quality for both language varieties. If Flemish translators want to work on a project, they should contact a project maintainer and ask to add a nl_BE project. International Dutch (nl) is exactly the same as Dutch spoken in the Netherlands (nl_NL).

===Other varieties===
Other varieties are
* nl_AW Dutch (Aruba)
* nl_BQ Dutch (Caribbean Netherlands)
* nl_CW Dutch (Curaçao)
* nl_SR Dutch (Suriname)
* nl_SX Dutch (Sint Maarten)
* af (Afrikaans)
* fy_NL (Frisian)

==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.''

===Grammer and word order in sentences===
*[https://www.dutchgrammar.com/en/?n=WordOrder.00 https://www.dutchgrammar.com/en/?n=WordOrder.00] About word order in sentences. It's not just one page, keep clicking on next page in the bottom right to see more examples.
*[http://redekundig.nl/ http://redekundig.nl/] a tool to help identify the structure of a Dutch sentence. Very helpful if you're dealing with complex grammatical rules and need to understand the sentence you are reviewing.
* [https://urd2.let.rug.nl/~vannoord/bin/alpino https://urd2.let.rug.nl/~vannoord/bin/alpino] university hosted tool to identify structure of a Dutch sentence. It's the same tool as redekundig.nl but hosted elsewhere, and the interface is harder to comprehend. Would advise trying this in case redekundig.nl isn't giving you the information you need.
* [https://onzetaal.nl/taaladvies/signaalwoorden-lijst/ List of signal words], use these wherever possible, they help clarify your message and prevent ambiguity.

===Style and tone===
* First follow any style guide you find here on this wiki for language and project you are working on
* If you are missing something, contact other translators
* If you search for style advise from other websites, avoid getting it from tech companies who make up their own version of Dutch language based on marketing rather than proper standard Dutch. Also avoid other wiki's which are often written by opinionated people who are not representative for the language. That doesn't mean you can't read them and learn from them, but take it with a grain of salt.

===Spelling===
*[https://taaladvies.net Taaladvies]
*[https://taal.vrt.be Taalnet]
*[https://onzetaal.nl OnzeTaal]

===Technical terminology===
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:
[https://docs.google.com/spreadsheets/d/1OPyeWDq2rtPf9fEpCLRpHl9Hn--OfFbWLbrGtZx3lYI/edit?usp=sharing Dutch Unified Localization Lab Glossary]. The document is maintained by Erin (a localization lab employee). If you wish to add comments, edits or suggest new entries, do so using the "Comment" feature in the spreadsheet.

Dutch

2021-03-24T17:20:03Z

Meteor0id: /* Signal Messenger */

__TOC__

==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 [https://internetfreedomfestival.org/ International Freedom Festival] domain and is subject to their [https://www.internetfreedomfestival.org/wiki/index.php/Code_of_Conduct Code of Conduct]. Be sure to read through the [https://www.internetfreedomfestival.org/wiki/index.php/Code_of_Conduct Code of Conduct] and then [mailto:info@localizationlab.org?subject=Mattermost%20Sign-up&body=Please%20send%20me%20a%20link%20to%20sign%20up%20for%20Mattermost. 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==
Ask yourself: "If my 65 year old mother read this (who has a total of 3 apps on her phone and uses only one of them on a weekly basis), would she understand this without anyone's help?". The goal is not to translate words, the goal is to make the text understandable to people who grew up in a different country.

===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. We will try to make this styleguide easier to read in the future.''

* 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. 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, meaning different words and/or a different structure of the sentence. An example: "Signal needs location services enabled to discover and connect with your old Android device." is localized as "Om je oude Android apparaat te kunnen detecteren en om er verbinding mee te maken is het nodig dat locatiebepaling op je apparaat is ingeschakeld.". Another example: don't write "Om het in te schakelen, tik op de schuifknop zodat hij blauw wordt." but instead write "Tik op de schuifknop zodat hij blauw wordt om meekijkpreventie in te schakelen."
* 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 punctuation, end the sentence with a period. If the description does not contain any punctuation, 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 Dutch people also get it wrong. [https://www.dutchgrammar.com/en/?n=WordOrder.00] 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. An example: Don't write "Deze personen kunnen door jou niet direct worden toegevoegd aan de groep." instead write "Deze personen kunnen door jou niet direct aan de groep worden toegevoegd.".
* 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 white space: 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 …
* Make sure the subject is repeated in every new sentence, do not refer back to a previous sentence. We do this to keep texts easy to read and understand. An example: do not write "Turing this on allows you to receive emails. They will contain information about your account." instead write "Turning this on allows you to receive emails. The emails you will receive contain information about your account.".
* Avoid anglicisms, our job is to localize the content so it can be understood by as many people as possible, that includes people who don't understand even the most common of English words.
* For units we follow the Si-standards. That means we translate 20MB as 20 MB with a white space. Kilobytes as kB. Note that Signal does not use KiB, MiB etc, because Signal is following the same units as the Android operating system. The same rule applies to other units such as 10s becoming 10 s. Abbreviations for minutes, months and weeks are not si units but we agreed to translate those as "min", "mnd" and "w". Capitalization matters.
* The text strings for the app store sometimes contain wordplay. If a good wordplay in Dutch can't be found, than rather leave the word joke out and just factually describe the change.
* Use pronoun + "wie" instead of "die" wherever possible. Read [https://taaladvies.net/taal/advies/vraag/1564 Taaladvies about wie/die] about where to use "wie" and where to use "die". This is a style choice we made to make complex sentences easier to comprehend.
* Use "van wie", "bij wie", "op wie" and "voor wie" instead of "waarvan", "waarmee", "waarop" and "waarvoor" wherever possible.
* For texts on buttons in Android and Desktop: use "Aan gesprek deelnemen", "Aan Signal doneren" and "Alice toevoegen". Do not use "Voeg Alice toe" or "Deelnemen aan gesprek" or "Doneren aan Signal". reason for this is optial readability. Also capitalize the first letter. on iOS we have not yet decided on the style, because that operating system often uses 'gebiedende wijs' rather than 'infinitief'.
* Try to stick to Dutch words, even if you see English words being used in other apps: "timer" becomes "tijdspanne", "admin" "beheerder", "checkbox" "selectievakje of aankruisvakje", "updaten" "bijwerken", "icon" "pictogram", "non-profit" "organisatie zonder winstoogmerk", "error" "fout", "database""databank" etc. You can find words like these listed in the Transifex Glossary for the Dutch Signal project.
* Beware of capitalization: use "QR-code" do not use "QR-Code" or "qr-code". "WiFi" is spelled different in Dutch: "wifi" all lowercase and without a dash. You can find words like these listed in the Transifex Glossary for the Dutch Signal project.
* Use [https://onzetaal.nl/taaladvies/signaalwoorden-lijst/ signal words] (words that indicate summation, contradiction etc.) wherever possible.
* Use formal verbs where their is no difference in meaning: use "je kunt" not "je kan". Howerver for "kun je" versus "kan je" there is a minor difference: "kan je" is more proposing while "kun je" is more forcefully suggestive. Therefore we use "kan je" instead of "kun je", and "zal je" instead of "zul je". [https://taalhelden.org/bericht/het-kan-je-kun-je https://taalhelden.org/bericht/het-kan-je-kun-je]
* Don't forget that although in English articles can be omitted, in Dutch it's not an accepted practice to omit the article. For example: "Playback time of audio attachment" should be localized as "Afspeellengte van HET audiobericht".
* Don't use possessive pronounce for things the user isn't possessing: Don't write "Open Signal-Desktop en gebruik de sneltoetsen om je tekstgrootte aan te passen.", instead write "Open Signal-Desktop en gebruik de sneltoetsen om de tekstgrootte aan te passen.". Users don't have font size, Signal has font size.

Extra example:
* Don't localize "Other Signal users who are saved to your phone's contact list." as "Andere Signal-gebruikers die zijn opgeslagen in jouw telefoons contactenlijst." but instead localize it as "Andere Signal-gebruikers van wie het telefoonnummer voor komt in de systeemcontactenlijst van jouw telefoon."

===Other projects===
For other projects the style has not yet been written down, however some translators seem to hold on to [http://download.microsoft.com/download/4/7/e/47e135ad-15d7-4491-be78-369804f0d333/nld-nld-StyleGuide.pdf a style guide from Microsoft].

==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.
* ANY time you edit a translation on a project with multiple separate resources, make sure to open all the resources and check if the same string exists elsewhere to apply the exact same edit there. An example would be when you edit a string in the Android Signal messenger app, make sure to also check if the same string exists in the Desktop app, the iOS app, the website or the support center. It's not easy for other reviewers to spot the inconsistency later, so do this right away at the very moment you make an edit.
* Be extra careful with plurals in Transifex, it's easy to miss one of the plural forms when reviewing. You can check all plurals again by searching for pluralized:yes
* Found a spelling mistake, grammar mistake, word order mistake or some word which is better substituted with another word? Don't just correct it when you see it and move on, check all the strings on all the resources for the same mistake or imperfection and correct that mistake on all the strings where it occurs. the moment you noticed something is the only opportunity to come up with a consistent solution across all the strings.

==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 punctuation is accurate, the capitalization is accurate, there are no double white spaces, and no missing white spaces
* 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.
* Don't just look at untranslated string, some strings are automatically translated by Transifex but might still be wrong because the context requires a different translation. use source_updated_after:dd-mm-yyyy to find all the new strings. Also check for edits made by others, using translation_updated_after:dd-mm-yyyy .

==Language varieties==
If you want to localize a project to a language variety which has strong similarities to Dutch and if there already exist good quality translations to Dutch, than it is recommended to base your translations of Dutch rather than English or an other source language. This may make translations faster, but more importantly it also keeps the texts consistent, so that someone who lives just across the border doesn't see completely different texts for the same project. In Transifex there is an option to swap which language you are using as the source language for your translations; you will find it by clicking the setting icon in the top right of the translation interface. Any string that have not yet been translated to Dutch will automatically still be shown as the original source language for the project (usually English).

===Flemish (nl_BE)===
If a project does not accept translations for nl_BE than unfortunately for Flanders, the languages nl and nl_NL will still follow Dutch standard language (Nederlandse standaardtaal). It is not acceptable to deliberately choose words and sentence structure which are understood by both language varieties, as that would reduce quality for both language varieties. If Flemish translators want to work on a project, they should contact a project maintainer and ask to add a nl_BE project. International Dutch (nl) is exactly the same as Dutch spoken in the Netherlands (nl_NL).

===Other varieties===
Other varieties are
* nl_AW Dutch (Aruba)
* nl_BQ Dutch (Caribbean Netherlands)
* nl_CW Dutch (Curaçao)
* nl_SR Dutch (Suriname)
* nl_SX Dutch (Sint Maarten)
* af (Afrikaans)
* fy_NL (Frisian)

==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.''

===Grammer and word order in sentences===
*[https://www.dutchgrammar.com/en/?n=WordOrder.00 https://www.dutchgrammar.com/en/?n=WordOrder.00] About word order in sentences. It's not just one page, keep clicking on next page in the bottom right to see more examples.
*[http://redekundig.nl/ http://redekundig.nl/] a tool to help identify the structure of a Dutch sentence. Very helpful if you're dealing with complex grammatical rules and need to understand the sentence you are reviewing.
* [https://urd2.let.rug.nl/~vannoord/bin/alpino https://urd2.let.rug.nl/~vannoord/bin/alpino] university hosted tool to identify structure of a Dutch sentence. It's the same tool as redekundig.nl but hosted elsewhere, and the interface is harder to comprehend. Would advise trying this in case redekundig.nl isn't giving you the information you need.
* [https://onzetaal.nl/taaladvies/signaalwoorden-lijst/ List of signal words], use these wherever possible, they help clarify your message and prevent ambiguity.

===Style and tone===
* First follow any style guide you find here on this wiki for language and project you are working on
* If you are missing something, contact other translators
* If you search for style advise from other websites, avoid getting it from tech companies who make up their own version of Dutch language based on marketing rather than proper standard Dutch. Also avoid other wiki's which are often written by opinionated people who are not representative for the language. That doesn't mean you can't read them and learn from them, but take it with a grain of salt.

===Spelling===
*[https://taaladvies.net Taaladvies]
*[https://taal.vrt.be Taalnet]
*[https://onzetaal.nl OnzeTaal]

===Technical terminology===
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:
[https://docs.google.com/spreadsheets/d/1OPyeWDq2rtPf9fEpCLRpHl9Hn--OfFbWLbrGtZx3lYI/edit?usp=sharing Dutch Unified Localization Lab Glossary]. The document is maintained by Erin (a localization lab employee). If you wish to add comments, edits or suggest new entries, do so using the "Comment" feature in the spreadsheet.

Dutch

2021-03-23T15:35:03Z

Meteor0id: /* Flemish (nl_BE) */

__TOC__

==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 [https://internetfreedomfestival.org/ International Freedom Festival] domain and is subject to their [https://www.internetfreedomfestival.org/wiki/index.php/Code_of_Conduct Code of Conduct]. Be sure to read through the [https://www.internetfreedomfestival.org/wiki/index.php/Code_of_Conduct Code of Conduct] and then [mailto:info@localizationlab.org?subject=Mattermost%20Sign-up&body=Please%20send%20me%20a%20link%20to%20sign%20up%20for%20Mattermost. 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==
Ask yourself: "If my 65 year old mother read this (who has a total of 3 apps on her phone and uses only one of them on a weekly basis), would she understand this without anyone's help?". The goal is not to translate words, the goal is to make the text understandable to people who grew up in a different country.

===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. We will try to make this styleguide easier to read in the future.''

* 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. 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, meaning different words and/or a different structure of the sentence. An example: "Signal needs location services enabled to discover and connect with your old Android device." is localized as "Om je oude Android apparaat te kunnen detecteren en om er verbinding mee te maken is het nodig dat locatiebepaling op je apparaat is ingeschakeld.". Another example: don't write "Om het in te schakelen, tik op de schuifknop zodat hij blauw wordt." but instead write "Tik op de schuifknop zodat hij blauw wordt om meekijkpreventie in te schakelen."
* 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 punctuation, end the sentence with a period. If the description does not contain any punctuation, 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 Dutch people also get it wrong. [https://www.dutchgrammar.com/en/?n=WordOrder.00] 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. An example: Don't write "Deze personen kunnen door jou niet direct worden toegevoegd aan de groep." instead write "Deze personen kunnen door jou niet direct aan de groep worden toegevoegd.".
* 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 white space: 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 …
* Make sure the subject is repeated in every new sentence, do not refer back to a previous sentence. We do this to keep texts easy to read and understand. An example: do not write "Turing this on allows you to receive emails. They will contain information about your account." instead write "Turning this on allows you to receive emails. The emails you will receive contain information about your account.".
* Avoid anglicisms, our job is to localize the content so it can be understood by as many people as possible, that includes people who don't understand even the most common of English words.
* For units we follow the Si-standards. That means we translate 20MB as 20 MB with a white space. Kilobytes as kB. Note that Signal does not use KiB, MiB etc, because Signal is following the same units as the Android operating system. The same rule applies to other units such as 10s becoming 10 s. Abbreviations for minutes, months and weeks are not si units but we agreed to translate those as "min", "mnd" and "w". Capitalization matters.
* The text strings for the app store sometimes contain wordplay. If a good wordplay in Dutch can't be found, than rather leave the word joke out and just factually describe the change.
* Use pronoun + "wie" instead of "die" wherever possible. Read [https://taaladvies.net/taal/advies/vraag/1564 Taaladvies about wie/die] about where to use "wie" and where to use "die". This is a style choice we made to make complex sentences easier to comprehend.
* Use "van wie", "bij wie", "op wie" and "voor wie" instead of "waarvan", "waarmee", "waarop" and "waarvoor" wherever possible.
* For texts on buttons in Android and Desktop: use "Aan gesprek deelnemen", "Aan Signal doneren" and "Alice toevoegen". Do not use "Voeg Alice toe" or "Deelnemen aan gesprek" or "Doneren aan Signal". reason for this is optial readability. Also capitalize the first letter. on iOS we have not yet decided on the style, because that operating system often uses 'gebiedende wijs' rather than 'infinitief'.
* Try to stick to Dutch words, even if you see English words being used in other apps: "timer" becomes "tijdspanne", "admin" "beheerder", "checkbox" "selectievakje of aankruisvakje", "updaten" "bijwerken", "icon" "pictogram", "non-profit" "organisatie zonder winstoogmerk", "error" "fout", "database""databank" etc. You can find words like these listed in the Transifex Glossary for the Dutch Signal project.
* Beware of capitalization: use "QR-code" do not use "QR-Code" or "qr-code". "WiFi" is spelled different in Dutch: "wifi" all lowercase and without a dash. You can find words like these listed in the Transifex Glossary for the Dutch Signal project.
* Use [https://onzetaal.nl/taaladvies/signaalwoorden-lijst/ signal words] (words that indicate summation, contradiction etc.) wherever possible.
* Use formal verbs where their is no difference in meaning: use "je kunt" not "je kan". Howerver for "kun je" versus "kan je" there is a minor difference: "kan je" is more proposing while "kun je" is more forcefully suggestive. Therefore we use "kan je" instead of "kun je", and "zal je" instead of "zul je". [https://taalhelden.org/bericht/het-kan-je-kun-je https://taalhelden.org/bericht/het-kan-je-kun-je]
* Don't forget that although in English articles can be omitted, in Dutch it's not an accepted practice to omit the article. For example: "Playback time of audio attachment" should be localized as "Afspeellengte van HET audiobericht".

Extra example:
* Don't localize "Other Signal users who are saved to your phone's contact list." as "Andere Signal-gebruikers die zijn opgeslagen in jouw telefoons contactenlijst." but instead localize it as "Andere Signal-gebruikers van wie het telefoonnummer voor komt in de systeemcontactenlijst van jouw telefoon."

===Other projects===
For other projects the style has not yet been written down, however some translators seem to hold on to [http://download.microsoft.com/download/4/7/e/47e135ad-15d7-4491-be78-369804f0d333/nld-nld-StyleGuide.pdf a style guide from Microsoft].

==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.
* ANY time you edit a translation on a project with multiple separate resources, make sure to open all the resources and check if the same string exists elsewhere to apply the exact same edit there. An example would be when you edit a string in the Android Signal messenger app, make sure to also check if the same string exists in the Desktop app, the iOS app, the website or the support center. It's not easy for other reviewers to spot the inconsistency later, so do this right away at the very moment you make an edit.
* Be extra careful with plurals in Transifex, it's easy to miss one of the plural forms when reviewing. You can check all plurals again by searching for pluralized:yes
* Found a spelling mistake, grammar mistake, word order mistake or some word which is better substituted with another word? Don't just correct it when you see it and move on, check all the strings on all the resources for the same mistake or imperfection and correct that mistake on all the strings where it occurs. the moment you noticed something is the only opportunity to come up with a consistent solution across all the strings.

==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 punctuation is accurate, the capitalization is accurate, there are no double white spaces, and no missing white spaces
* 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.
* Don't just look at untranslated string, some strings are automatically translated by Transifex but might still be wrong because the context requires a different translation. use source_updated_after:dd-mm-yyyy to find all the new strings. Also check for edits made by others, using translation_updated_after:dd-mm-yyyy .

==Language varieties==
If you want to localize a project to a language variety which has strong similarities to Dutch and if there already exist good quality translations to Dutch, than it is recommended to base your translations of Dutch rather than English or an other source language. This may make translations faster, but more importantly it also keeps the texts consistent, so that someone who lives just across the border doesn't see completely different texts for the same project. In Transifex there is an option to swap which language you are using as the source language for your translations; you will find it by clicking the setting icon in the top right of the translation interface. Any string that have not yet been translated to Dutch will automatically still be shown as the original source language for the project (usually English).

===Flemish (nl_BE)===
If a project does not accept translations for nl_BE than unfortunately for Flanders, the languages nl and nl_NL will still follow Dutch standard language (Nederlandse standaardtaal). It is not acceptable to deliberately choose words and sentence structure which are understood by both language varieties, as that would reduce quality for both language varieties. If Flemish translators want to work on a project, they should contact a project maintainer and ask to add a nl_BE project. International Dutch (nl) is exactly the same as Dutch spoken in the Netherlands (nl_NL).

===Other varieties===
Other varieties are
* nl_AW Dutch (Aruba)
* nl_BQ Dutch (Caribbean Netherlands)
* nl_CW Dutch (Curaçao)
* nl_SR Dutch (Suriname)
* nl_SX Dutch (Sint Maarten)
* af (Afrikaans)
* fy_NL (Frisian)

==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.''

===Grammer and word order in sentences===
*[https://www.dutchgrammar.com/en/?n=WordOrder.00 https://www.dutchgrammar.com/en/?n=WordOrder.00] About word order in sentences. It's not just one page, keep clicking on next page in the bottom right to see more examples.
*[http://redekundig.nl/ http://redekundig.nl/] a tool to help identify the structure of a Dutch sentence. Very helpful if you're dealing with complex grammatical rules and need to understand the sentence you are reviewing.
* [https://urd2.let.rug.nl/~vannoord/bin/alpino https://urd2.let.rug.nl/~vannoord/bin/alpino] university hosted tool to identify structure of a Dutch sentence. It's the same tool as redekundig.nl but hosted elsewhere, and the interface is harder to comprehend. Would advise trying this in case redekundig.nl isn't giving you the information you need.
* [https://onzetaal.nl/taaladvies/signaalwoorden-lijst/ List of signal words], use these wherever possible, they help clarify your message and prevent ambiguity.

===Style and tone===
* First follow any style guide you find here on this wiki for language and project you are working on
* If you are missing something, contact other translators
* If you search for style advise from other websites, avoid getting it from tech companies who make up their own version of Dutch language based on marketing rather than proper standard Dutch. Also avoid other wiki's which are often written by opinionated people who are not representative for the language. That doesn't mean you can't read them and learn from them, but take it with a grain of salt.

===Spelling===
*[https://taaladvies.net Taaladvies]
*[https://taal.vrt.be Taalnet]
*[https://onzetaal.nl OnzeTaal]

===Technical terminology===
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:
[https://docs.google.com/spreadsheets/d/1OPyeWDq2rtPf9fEpCLRpHl9Hn--OfFbWLbrGtZx3lYI/edit?usp=sharing Dutch Unified Localization Lab Glossary]. The document is maintained by Erin (a localization lab employee). If you wish to add comments, edits or suggest new entries, do so using the "Comment" feature in the spreadsheet.

Dutch

2021-03-23T15:30:23Z

Meteor0id: /* Language varieties */

__TOC__

==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 [https://internetfreedomfestival.org/ International Freedom Festival] domain and is subject to their [https://www.internetfreedomfestival.org/wiki/index.php/Code_of_Conduct Code of Conduct]. Be sure to read through the [https://www.internetfreedomfestival.org/wiki/index.php/Code_of_Conduct Code of Conduct] and then [mailto:info@localizationlab.org?subject=Mattermost%20Sign-up&body=Please%20send%20me%20a%20link%20to%20sign%20up%20for%20Mattermost. 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==
Ask yourself: "If my 65 year old mother read this (who has a total of 3 apps on her phone and uses only one of them on a weekly basis), would she understand this without anyone's help?". The goal is not to translate words, the goal is to make the text understandable to people who grew up in a different country.

===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. We will try to make this styleguide easier to read in the future.''

* 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. 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, meaning different words and/or a different structure of the sentence. An example: "Signal needs location services enabled to discover and connect with your old Android device." is localized as "Om je oude Android apparaat te kunnen detecteren en om er verbinding mee te maken is het nodig dat locatiebepaling op je apparaat is ingeschakeld.". Another example: don't write "Om het in te schakelen, tik op de schuifknop zodat hij blauw wordt." but instead write "Tik op de schuifknop zodat hij blauw wordt om meekijkpreventie in te schakelen."
* 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 punctuation, end the sentence with a period. If the description does not contain any punctuation, 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 Dutch people also get it wrong. [https://www.dutchgrammar.com/en/?n=WordOrder.00] 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. An example: Don't write "Deze personen kunnen door jou niet direct worden toegevoegd aan de groep." instead write "Deze personen kunnen door jou niet direct aan de groep worden toegevoegd.".
* 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 white space: 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 …
* Make sure the subject is repeated in every new sentence, do not refer back to a previous sentence. We do this to keep texts easy to read and understand. An example: do not write "Turing this on allows you to receive emails. They will contain information about your account." instead write "Turning this on allows you to receive emails. The emails you will receive contain information about your account.".
* Avoid anglicisms, our job is to localize the content so it can be understood by as many people as possible, that includes people who don't understand even the most common of English words.
* For units we follow the Si-standards. That means we translate 20MB as 20 MB with a white space. Kilobytes as kB. Note that Signal does not use KiB, MiB etc, because Signal is following the same units as the Android operating system. The same rule applies to other units such as 10s becoming 10 s. Abbreviations for minutes, months and weeks are not si units but we agreed to translate those as "min", "mnd" and "w". Capitalization matters.
* The text strings for the app store sometimes contain wordplay. If a good wordplay in Dutch can't be found, than rather leave the word joke out and just factually describe the change.
* Use pronoun + "wie" instead of "die" wherever possible. Read [https://taaladvies.net/taal/advies/vraag/1564 Taaladvies about wie/die] about where to use "wie" and where to use "die". This is a style choice we made to make complex sentences easier to comprehend.
* Use "van wie", "bij wie", "op wie" and "voor wie" instead of "waarvan", "waarmee", "waarop" and "waarvoor" wherever possible.
* For texts on buttons in Android and Desktop: use "Aan gesprek deelnemen", "Aan Signal doneren" and "Alice toevoegen". Do not use "Voeg Alice toe" or "Deelnemen aan gesprek" or "Doneren aan Signal". reason for this is optial readability. Also capitalize the first letter. on iOS we have not yet decided on the style, because that operating system often uses 'gebiedende wijs' rather than 'infinitief'.
* Try to stick to Dutch words, even if you see English words being used in other apps: "timer" becomes "tijdspanne", "admin" "beheerder", "checkbox" "selectievakje of aankruisvakje", "updaten" "bijwerken", "icon" "pictogram", "non-profit" "organisatie zonder winstoogmerk", "error" "fout", "database""databank" etc. You can find words like these listed in the Transifex Glossary for the Dutch Signal project.
* Beware of capitalization: use "QR-code" do not use "QR-Code" or "qr-code". "WiFi" is spelled different in Dutch: "wifi" all lowercase and without a dash. You can find words like these listed in the Transifex Glossary for the Dutch Signal project.
* Use [https://onzetaal.nl/taaladvies/signaalwoorden-lijst/ signal words] (words that indicate summation, contradiction etc.) wherever possible.
* Use formal verbs where their is no difference in meaning: use "je kunt" not "je kan". Howerver for "kun je" versus "kan je" there is a minor difference: "kan je" is more proposing while "kun je" is more forcefully suggestive. Therefore we use "kan je" instead of "kun je", and "zal je" instead of "zul je". [https://taalhelden.org/bericht/het-kan-je-kun-je https://taalhelden.org/bericht/het-kan-je-kun-je]
* Don't forget that although in English articles can be omitted, in Dutch it's not an accepted practice to omit the article. For example: "Playback time of audio attachment" should be localized as "Afspeellengte van HET audiobericht".

Extra example:
* Don't localize "Other Signal users who are saved to your phone's contact list." as "Andere Signal-gebruikers die zijn opgeslagen in jouw telefoons contactenlijst." but instead localize it as "Andere Signal-gebruikers van wie het telefoonnummer voor komt in de systeemcontactenlijst van jouw telefoon."

===Other projects===
For other projects the style has not yet been written down, however some translators seem to hold on to [http://download.microsoft.com/download/4/7/e/47e135ad-15d7-4491-be78-369804f0d333/nld-nld-StyleGuide.pdf a style guide from Microsoft].

==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.
* ANY time you edit a translation on a project with multiple separate resources, make sure to open all the resources and check if the same string exists elsewhere to apply the exact same edit there. An example would be when you edit a string in the Android Signal messenger app, make sure to also check if the same string exists in the Desktop app, the iOS app, the website or the support center. It's not easy for other reviewers to spot the inconsistency later, so do this right away at the very moment you make an edit.
* Be extra careful with plurals in Transifex, it's easy to miss one of the plural forms when reviewing. You can check all plurals again by searching for pluralized:yes
* Found a spelling mistake, grammar mistake, word order mistake or some word which is better substituted with another word? Don't just correct it when you see it and move on, check all the strings on all the resources for the same mistake or imperfection and correct that mistake on all the strings where it occurs. the moment you noticed something is the only opportunity to come up with a consistent solution across all the strings.

==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 punctuation is accurate, the capitalization is accurate, there are no double white spaces, and no missing white spaces
* 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.
* Don't just look at untranslated string, some strings are automatically translated by Transifex but might still be wrong because the context requires a different translation. use source_updated_after:dd-mm-yyyy to find all the new strings. Also check for edits made by others, using translation_updated_after:dd-mm-yyyy .

==Language varieties==
If you want to localize a project to a language variety which has strong similarities to Dutch and if there already exist good quality translations to Dutch, than it is recommended to base your translations of Dutch rather than English or an other source language. This may make translations faster, but more importantly it also keeps the texts consistent, so that someone who lives just across the border doesn't see completely different texts for the same project. In Transifex there is an option to swap which language you are using as the source language for your translations; you will find it by clicking the setting icon in the top right of the translation interface. Any string that have not yet been translated to Dutch will automatically still be shown as the original source language for the project (usually English).

===Flemish (nl_BE)===
* It is not ok to try and compromise between Flemish and Dutch, as that would reduce quality for both language varieties. If a project does not accept translations for nl_BE than unfortunately for Flanders, the languages nl and nl_NL will still follow Dutch standard language (Nederlandse standaardtaal). It is not possible to make nl into a mix or compromise between both language varieties to satisfy both language varieties. If Flemish translators want to work on a project, they should contact a project maintainer and ask to add a nl_BE project.

===Other varieties===
Other varieties are
* nl_AW Dutch (Aruba)
* nl_BQ Dutch (Caribbean Netherlands)
* nl_CW Dutch (Curaçao)
* nl_SR Dutch (Suriname)
* nl_SX Dutch (Sint Maarten)
* af (Afrikaans)
* fy_NL (Frisian)

==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.''

===Grammer and word order in sentences===
*[https://www.dutchgrammar.com/en/?n=WordOrder.00 https://www.dutchgrammar.com/en/?n=WordOrder.00] About word order in sentences. It's not just one page, keep clicking on next page in the bottom right to see more examples.
*[http://redekundig.nl/ http://redekundig.nl/] a tool to help identify the structure of a Dutch sentence. Very helpful if you're dealing with complex grammatical rules and need to understand the sentence you are reviewing.
* [https://urd2.let.rug.nl/~vannoord/bin/alpino https://urd2.let.rug.nl/~vannoord/bin/alpino] university hosted tool to identify structure of a Dutch sentence. It's the same tool as redekundig.nl but hosted elsewhere, and the interface is harder to comprehend. Would advise trying this in case redekundig.nl isn't giving you the information you need.
* [https://onzetaal.nl/taaladvies/signaalwoorden-lijst/ List of signal words], use these wherever possible, they help clarify your message and prevent ambiguity.

===Style and tone===
* First follow any style guide you find here on this wiki for language and project you are working on
* If you are missing something, contact other translators
* If you search for style advise from other websites, avoid getting it from tech companies who make up their own version of Dutch language based on marketing rather than proper standard Dutch. Also avoid other wiki's which are often written by opinionated people who are not representative for the language. That doesn't mean you can't read them and learn from them, but take it with a grain of salt.

===Spelling===
*[https://taaladvies.net Taaladvies]
*[https://taal.vrt.be Taalnet]
*[https://onzetaal.nl OnzeTaal]

===Technical terminology===
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:
[https://docs.google.com/spreadsheets/d/1OPyeWDq2rtPf9fEpCLRpHl9Hn--OfFbWLbrGtZx3lYI/edit?usp=sharing Dutch Unified Localization Lab Glossary]. The document is maintained by Erin (a localization lab employee). If you wish to add comments, edits or suggest new entries, do so using the "Comment" feature in the spreadsheet.

Dutch

2021-03-23T15:29:13Z

Meteor0id: /* Other varieties */

__TOC__

==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 [https://internetfreedomfestival.org/ International Freedom Festival] domain and is subject to their [https://www.internetfreedomfestival.org/wiki/index.php/Code_of_Conduct Code of Conduct]. Be sure to read through the [https://www.internetfreedomfestival.org/wiki/index.php/Code_of_Conduct Code of Conduct] and then [mailto:info@localizationlab.org?subject=Mattermost%20Sign-up&body=Please%20send%20me%20a%20link%20to%20sign%20up%20for%20Mattermost. 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==
Ask yourself: "If my 65 year old mother read this (who has a total of 3 apps on her phone and uses only one of them on a weekly basis), would she understand this without anyone's help?". The goal is not to translate words, the goal is to make the text understandable to people who grew up in a different country.

===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. We will try to make this styleguide easier to read in the future.''

* 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. 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, meaning different words and/or a different structure of the sentence. An example: "Signal needs location services enabled to discover and connect with your old Android device." is localized as "Om je oude Android apparaat te kunnen detecteren en om er verbinding mee te maken is het nodig dat locatiebepaling op je apparaat is ingeschakeld.". Another example: don't write "Om het in te schakelen, tik op de schuifknop zodat hij blauw wordt." but instead write "Tik op de schuifknop zodat hij blauw wordt om meekijkpreventie in te schakelen."
* 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 punctuation, end the sentence with a period. If the description does not contain any punctuation, 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 Dutch people also get it wrong. [https://www.dutchgrammar.com/en/?n=WordOrder.00] 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. An example: Don't write "Deze personen kunnen door jou niet direct worden toegevoegd aan de groep." instead write "Deze personen kunnen door jou niet direct aan de groep worden toegevoegd.".
* 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 white space: 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 …
* Make sure the subject is repeated in every new sentence, do not refer back to a previous sentence. We do this to keep texts easy to read and understand. An example: do not write "Turing this on allows you to receive emails. They will contain information about your account." instead write "Turning this on allows you to receive emails. The emails you will receive contain information about your account.".
* Avoid anglicisms, our job is to localize the content so it can be understood by as many people as possible, that includes people who don't understand even the most common of English words.
* For units we follow the Si-standards. That means we translate 20MB as 20 MB with a white space. Kilobytes as kB. Note that Signal does not use KiB, MiB etc, because Signal is following the same units as the Android operating system. The same rule applies to other units such as 10s becoming 10 s. Abbreviations for minutes, months and weeks are not si units but we agreed to translate those as "min", "mnd" and "w". Capitalization matters.
* The text strings for the app store sometimes contain wordplay. If a good wordplay in Dutch can't be found, than rather leave the word joke out and just factually describe the change.
* Use pronoun + "wie" instead of "die" wherever possible. Read [https://taaladvies.net/taal/advies/vraag/1564 Taaladvies about wie/die] about where to use "wie" and where to use "die". This is a style choice we made to make complex sentences easier to comprehend.
* Use "van wie", "bij wie", "op wie" and "voor wie" instead of "waarvan", "waarmee", "waarop" and "waarvoor" wherever possible.
* For texts on buttons in Android and Desktop: use "Aan gesprek deelnemen", "Aan Signal doneren" and "Alice toevoegen". Do not use "Voeg Alice toe" or "Deelnemen aan gesprek" or "Doneren aan Signal". reason for this is optial readability. Also capitalize the first letter. on iOS we have not yet decided on the style, because that operating system often uses 'gebiedende wijs' rather than 'infinitief'.
* Try to stick to Dutch words, even if you see English words being used in other apps: "timer" becomes "tijdspanne", "admin" "beheerder", "checkbox" "selectievakje of aankruisvakje", "updaten" "bijwerken", "icon" "pictogram", "non-profit" "organisatie zonder winstoogmerk", "error" "fout", "database""databank" etc. You can find words like these listed in the Transifex Glossary for the Dutch Signal project.
* Beware of capitalization: use "QR-code" do not use "QR-Code" or "qr-code". "WiFi" is spelled different in Dutch: "wifi" all lowercase and without a dash. You can find words like these listed in the Transifex Glossary for the Dutch Signal project.
* Use [https://onzetaal.nl/taaladvies/signaalwoorden-lijst/ signal words] (words that indicate summation, contradiction etc.) wherever possible.
* Use formal verbs where their is no difference in meaning: use "je kunt" not "je kan". Howerver for "kun je" versus "kan je" there is a minor difference: "kan je" is more proposing while "kun je" is more forcefully suggestive. Therefore we use "kan je" instead of "kun je", and "zal je" instead of "zul je". [https://taalhelden.org/bericht/het-kan-je-kun-je https://taalhelden.org/bericht/het-kan-je-kun-je]
* Don't forget that although in English articles can be omitted, in Dutch it's not an accepted practice to omit the article. For example: "Playback time of audio attachment" should be localized as "Afspeellengte van HET audiobericht".

Extra example:
* Don't localize "Other Signal users who are saved to your phone's contact list." as "Andere Signal-gebruikers die zijn opgeslagen in jouw telefoons contactenlijst." but instead localize it as "Andere Signal-gebruikers van wie het telefoonnummer voor komt in de systeemcontactenlijst van jouw telefoon."

===Other projects===
For other projects the style has not yet been written down, however some translators seem to hold on to [http://download.microsoft.com/download/4/7/e/47e135ad-15d7-4491-be78-369804f0d333/nld-nld-StyleGuide.pdf a style guide from Microsoft].

==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.
* ANY time you edit a translation on a project with multiple separate resources, make sure to open all the resources and check if the same string exists elsewhere to apply the exact same edit there. An example would be when you edit a string in the Android Signal messenger app, make sure to also check if the same string exists in the Desktop app, the iOS app, the website or the support center. It's not easy for other reviewers to spot the inconsistency later, so do this right away at the very moment you make an edit.
* Be extra careful with plurals in Transifex, it's easy to miss one of the plural forms when reviewing. You can check all plurals again by searching for pluralized:yes
* Found a spelling mistake, grammar mistake, word order mistake or some word which is better substituted with another word? Don't just correct it when you see it and move on, check all the strings on all the resources for the same mistake or imperfection and correct that mistake on all the strings where it occurs. the moment you noticed something is the only opportunity to come up with a consistent solution across all the strings.

==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 punctuation is accurate, the capitalization is accurate, there are no double white spaces, and no missing white spaces
* 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.
* Don't just look at untranslated string, some strings are automatically translated by Transifex but might still be wrong because the context requires a different translation. use source_updated_after:dd-mm-yyyy to find all the new strings. Also check for edits made by others, using translation_updated_after:dd-mm-yyyy .

==Language varieties==
If you want to localize a project to a language variety which has strong similarities to Dutch and if there already exist good quality translations to Dutch, than it is recommended to base your translations of Dutch rather than English or an other source language. This may make translations faster, but more importantly it also keeps the texts consistent, so that someone who lives just across the border doesn't see completely different texts for the same project. In Transifex there is an option to swap which language you are using as the source language for your translations; you will find it by clicking the setting icon in the top right of the translation interface. Any string that have not yet been translated to Dutch will automatically still be shown as the original source language for the project (usually English).

===Compromising between nl, nl_NL and Flemish (nl_BE)===
* It is not ok to try and compromise between Flemish and Dutch, as that would reduce quality for both language varieties. If a project does not accept translations for nl_BE than unfortunately for Flanders, the languages nl and nl_NL will still follow Dutch standard language (Nederlandse standaardtaal). It is not possible to make nl into a mix or compromise between both language varieties to satisfy both language varieties. If Flemish translators want to work on a project, they should contact a project maintainer and ask to add a nl_BE project.

===Other varieties===
Other varieties are
* nl_AW Dutch (Aruba)
* nl_BE Dutch (Belgium)
* nl_BQ Dutch (Caribbean Netherlands)
* nl_CW Dutch (Curaçao)
* nl_SR Dutch (Suriname)
* nl_SX Dutch (Sint Maarten)
* af (Afrikaans)
* fy_NL (Frisian)

==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.''

===Grammer and word order in sentences===
*[https://www.dutchgrammar.com/en/?n=WordOrder.00 https://www.dutchgrammar.com/en/?n=WordOrder.00] About word order in sentences. It's not just one page, keep clicking on next page in the bottom right to see more examples.
*[http://redekundig.nl/ http://redekundig.nl/] a tool to help identify the structure of a Dutch sentence. Very helpful if you're dealing with complex grammatical rules and need to understand the sentence you are reviewing.
* [https://urd2.let.rug.nl/~vannoord/bin/alpino https://urd2.let.rug.nl/~vannoord/bin/alpino] university hosted tool to identify structure of a Dutch sentence. It's the same tool as redekundig.nl but hosted elsewhere, and the interface is harder to comprehend. Would advise trying this in case redekundig.nl isn't giving you the information you need.
* [https://onzetaal.nl/taaladvies/signaalwoorden-lijst/ List of signal words], use these wherever possible, they help clarify your message and prevent ambiguity.

===Style and tone===
* First follow any style guide you find here on this wiki for language and project you are working on
* If you are missing something, contact other translators
* If you search for style advise from other websites, avoid getting it from tech companies who make up their own version of Dutch language based on marketing rather than proper standard Dutch. Also avoid other wiki's which are often written by opinionated people who are not representative for the language. That doesn't mean you can't read them and learn from them, but take it with a grain of salt.

===Spelling===
*[https://taaladvies.net Taaladvies]
*[https://taal.vrt.be Taalnet]
*[https://onzetaal.nl OnzeTaal]

===Technical terminology===
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:
[https://docs.google.com/spreadsheets/d/1OPyeWDq2rtPf9fEpCLRpHl9Hn--OfFbWLbrGtZx3lYI/edit?usp=sharing Dutch Unified Localization Lab Glossary]. The document is maintained by Erin (a localization lab employee). If you wish to add comments, edits or suggest new entries, do so using the "Comment" feature in the spreadsheet.

Dutch

2021-03-23T15:27:47Z

Meteor0id: /* using nl or nl_NL for Flemish (nl_BE) */

__TOC__

==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 [https://internetfreedomfestival.org/ International Freedom Festival] domain and is subject to their [https://www.internetfreedomfestival.org/wiki/index.php/Code_of_Conduct Code of Conduct]. Be sure to read through the [https://www.internetfreedomfestival.org/wiki/index.php/Code_of_Conduct Code of Conduct] and then [mailto:info@localizationlab.org?subject=Mattermost%20Sign-up&body=Please%20send%20me%20a%20link%20to%20sign%20up%20for%20Mattermost. 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==
Ask yourself: "If my 65 year old mother read this (who has a total of 3 apps on her phone and uses only one of them on a weekly basis), would she understand this without anyone's help?". The goal is not to translate words, the goal is to make the text understandable to people who grew up in a different country.

===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. We will try to make this styleguide easier to read in the future.''

* 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. 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, meaning different words and/or a different structure of the sentence. An example: "Signal needs location services enabled to discover and connect with your old Android device." is localized as "Om je oude Android apparaat te kunnen detecteren en om er verbinding mee te maken is het nodig dat locatiebepaling op je apparaat is ingeschakeld.". Another example: don't write "Om het in te schakelen, tik op de schuifknop zodat hij blauw wordt." but instead write "Tik op de schuifknop zodat hij blauw wordt om meekijkpreventie in te schakelen."
* 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 punctuation, end the sentence with a period. If the description does not contain any punctuation, 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 Dutch people also get it wrong. [https://www.dutchgrammar.com/en/?n=WordOrder.00] 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. An example: Don't write "Deze personen kunnen door jou niet direct worden toegevoegd aan de groep." instead write "Deze personen kunnen door jou niet direct aan de groep worden toegevoegd.".
* 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 white space: 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 …
* Make sure the subject is repeated in every new sentence, do not refer back to a previous sentence. We do this to keep texts easy to read and understand. An example: do not write "Turing this on allows you to receive emails. They will contain information about your account." instead write "Turning this on allows you to receive emails. The emails you will receive contain information about your account.".
* Avoid anglicisms, our job is to localize the content so it can be understood by as many people as possible, that includes people who don't understand even the most common of English words.
* For units we follow the Si-standards. That means we translate 20MB as 20 MB with a white space. Kilobytes as kB. Note that Signal does not use KiB, MiB etc, because Signal is following the same units as the Android operating system. The same rule applies to other units such as 10s becoming 10 s. Abbreviations for minutes, months and weeks are not si units but we agreed to translate those as "min", "mnd" and "w". Capitalization matters.
* The text strings for the app store sometimes contain wordplay. If a good wordplay in Dutch can't be found, than rather leave the word joke out and just factually describe the change.
* Use pronoun + "wie" instead of "die" wherever possible. Read [https://taaladvies.net/taal/advies/vraag/1564 Taaladvies about wie/die] about where to use "wie" and where to use "die". This is a style choice we made to make complex sentences easier to comprehend.
* Use "van wie", "bij wie", "op wie" and "voor wie" instead of "waarvan", "waarmee", "waarop" and "waarvoor" wherever possible.
* For texts on buttons in Android and Desktop: use "Aan gesprek deelnemen", "Aan Signal doneren" and "Alice toevoegen". Do not use "Voeg Alice toe" or "Deelnemen aan gesprek" or "Doneren aan Signal". reason for this is optial readability. Also capitalize the first letter. on iOS we have not yet decided on the style, because that operating system often uses 'gebiedende wijs' rather than 'infinitief'.
* Try to stick to Dutch words, even if you see English words being used in other apps: "timer" becomes "tijdspanne", "admin" "beheerder", "checkbox" "selectievakje of aankruisvakje", "updaten" "bijwerken", "icon" "pictogram", "non-profit" "organisatie zonder winstoogmerk", "error" "fout", "database""databank" etc. You can find words like these listed in the Transifex Glossary for the Dutch Signal project.
* Beware of capitalization: use "QR-code" do not use "QR-Code" or "qr-code". "WiFi" is spelled different in Dutch: "wifi" all lowercase and without a dash. You can find words like these listed in the Transifex Glossary for the Dutch Signal project.
* Use [https://onzetaal.nl/taaladvies/signaalwoorden-lijst/ signal words] (words that indicate summation, contradiction etc.) wherever possible.
* Use formal verbs where their is no difference in meaning: use "je kunt" not "je kan". Howerver for "kun je" versus "kan je" there is a minor difference: "kan je" is more proposing while "kun je" is more forcefully suggestive. Therefore we use "kan je" instead of "kun je", and "zal je" instead of "zul je". [https://taalhelden.org/bericht/het-kan-je-kun-je https://taalhelden.org/bericht/het-kan-je-kun-je]
* Don't forget that although in English articles can be omitted, in Dutch it's not an accepted practice to omit the article. For example: "Playback time of audio attachment" should be localized as "Afspeellengte van HET audiobericht".

Extra example:
* Don't localize "Other Signal users who are saved to your phone's contact list." as "Andere Signal-gebruikers die zijn opgeslagen in jouw telefoons contactenlijst." but instead localize it as "Andere Signal-gebruikers van wie het telefoonnummer voor komt in de systeemcontactenlijst van jouw telefoon."

===Other projects===
For other projects the style has not yet been written down, however some translators seem to hold on to [http://download.microsoft.com/download/4/7/e/47e135ad-15d7-4491-be78-369804f0d333/nld-nld-StyleGuide.pdf a style guide from Microsoft].

==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.
* ANY time you edit a translation on a project with multiple separate resources, make sure to open all the resources and check if the same string exists elsewhere to apply the exact same edit there. An example would be when you edit a string in the Android Signal messenger app, make sure to also check if the same string exists in the Desktop app, the iOS app, the website or the support center. It's not easy for other reviewers to spot the inconsistency later, so do this right away at the very moment you make an edit.
* Be extra careful with plurals in Transifex, it's easy to miss one of the plural forms when reviewing. You can check all plurals again by searching for pluralized:yes
* Found a spelling mistake, grammar mistake, word order mistake or some word which is better substituted with another word? Don't just correct it when you see it and move on, check all the strings on all the resources for the same mistake or imperfection and correct that mistake on all the strings where it occurs. the moment you noticed something is the only opportunity to come up with a consistent solution across all the strings.

==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 punctuation is accurate, the capitalization is accurate, there are no double white spaces, and no missing white spaces
* 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.
* Don't just look at untranslated string, some strings are automatically translated by Transifex but might still be wrong because the context requires a different translation. use source_updated_after:dd-mm-yyyy to find all the new strings. Also check for edits made by others, using translation_updated_after:dd-mm-yyyy .

==Language varieties==
If you want to localize a project to a language variety which has strong similarities to Dutch and if there already exist good quality translations to Dutch, than it is recommended to base your translations of Dutch rather than English or an other source language. This may make translations faster, but more importantly it also keeps the texts consistent, so that someone who lives just across the border doesn't see completely different texts for the same project. In Transifex there is an option to swap which language you are using as the source language for your translations; you will find it by clicking the setting icon in the top right of the translation interface. Any string that have not yet been translated to Dutch will automatically still be shown as the original source language for the project (usually English).

===Compromising between nl, nl_NL and Flemish (nl_BE)===
* It is not ok to try and compromise between Flemish and Dutch, as that would reduce quality for both language varieties. If a project does not accept translations for nl_BE than unfortunately for Flanders, the languages nl and nl_NL will still follow Dutch standard language (Nederlandse standaardtaal). It is not possible to make nl into a mix or compromise between both language varieties to satisfy both language varieties. If Flemish translators want to work on a project, they should contact a project maintainer and ask to add a nl_BE project.

===Other varieties===
Other varieties are
* nl-AW Dutch (Aruba)
* nl-BE Dutch (Belgium)
* nl-BQ Dutch (Caribbean Netherlands)
* nl-CW Dutch (Curaçao)
* nl-SR Dutch (Suriname)
* nl-SX Dutch (Sint Maarten)
* af (Afrikaans)

==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.''

===Grammer and word order in sentences===
*[https://www.dutchgrammar.com/en/?n=WordOrder.00 https://www.dutchgrammar.com/en/?n=WordOrder.00] About word order in sentences. It's not just one page, keep clicking on next page in the bottom right to see more examples.
*[http://redekundig.nl/ http://redekundig.nl/] a tool to help identify the structure of a Dutch sentence. Very helpful if you're dealing with complex grammatical rules and need to understand the sentence you are reviewing.
* [https://urd2.let.rug.nl/~vannoord/bin/alpino https://urd2.let.rug.nl/~vannoord/bin/alpino] university hosted tool to identify structure of a Dutch sentence. It's the same tool as redekundig.nl but hosted elsewhere, and the interface is harder to comprehend. Would advise trying this in case redekundig.nl isn't giving you the information you need.
* [https://onzetaal.nl/taaladvies/signaalwoorden-lijst/ List of signal words], use these wherever possible, they help clarify your message and prevent ambiguity.

===Style and tone===
* First follow any style guide you find here on this wiki for language and project you are working on
* If you are missing something, contact other translators
* If you search for style advise from other websites, avoid getting it from tech companies who make up their own version of Dutch language based on marketing rather than proper standard Dutch. Also avoid other wiki's which are often written by opinionated people who are not representative for the language. That doesn't mean you can't read them and learn from them, but take it with a grain of salt.

===Spelling===
*[https://taaladvies.net Taaladvies]
*[https://taal.vrt.be Taalnet]
*[https://onzetaal.nl OnzeTaal]

===Technical terminology===
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:
[https://docs.google.com/spreadsheets/d/1OPyeWDq2rtPf9fEpCLRpHl9Hn--OfFbWLbrGtZx3lYI/edit?usp=sharing Dutch Unified Localization Lab Glossary]. The document is maintained by Erin (a localization lab employee). If you wish to add comments, edits or suggest new entries, do so using the "Comment" feature in the spreadsheet.

Dutch

2021-03-23T15:26:00Z

Meteor0id: /* (Flemish nl_BE) and Frisian (fy_NL) */

__TOC__

==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 [https://internetfreedomfestival.org/ International Freedom Festival] domain and is subject to their [https://www.internetfreedomfestival.org/wiki/index.php/Code_of_Conduct Code of Conduct]. Be sure to read through the [https://www.internetfreedomfestival.org/wiki/index.php/Code_of_Conduct Code of Conduct] and then [mailto:info@localizationlab.org?subject=Mattermost%20Sign-up&body=Please%20send%20me%20a%20link%20to%20sign%20up%20for%20Mattermost. 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==
Ask yourself: "If my 65 year old mother read this (who has a total of 3 apps on her phone and uses only one of them on a weekly basis), would she understand this without anyone's help?". The goal is not to translate words, the goal is to make the text understandable to people who grew up in a different country.

===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. We will try to make this styleguide easier to read in the future.''

* 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. 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, meaning different words and/or a different structure of the sentence. An example: "Signal needs location services enabled to discover and connect with your old Android device." is localized as "Om je oude Android apparaat te kunnen detecteren en om er verbinding mee te maken is het nodig dat locatiebepaling op je apparaat is ingeschakeld.". Another example: don't write "Om het in te schakelen, tik op de schuifknop zodat hij blauw wordt." but instead write "Tik op de schuifknop zodat hij blauw wordt om meekijkpreventie in te schakelen."
* 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 punctuation, end the sentence with a period. If the description does not contain any punctuation, 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 Dutch people also get it wrong. [https://www.dutchgrammar.com/en/?n=WordOrder.00] 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. An example: Don't write "Deze personen kunnen door jou niet direct worden toegevoegd aan de groep." instead write "Deze personen kunnen door jou niet direct aan de groep worden toegevoegd.".
* 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 white space: 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 …
* Make sure the subject is repeated in every new sentence, do not refer back to a previous sentence. We do this to keep texts easy to read and understand. An example: do not write "Turing this on allows you to receive emails. They will contain information about your account." instead write "Turning this on allows you to receive emails. The emails you will receive contain information about your account.".
* Avoid anglicisms, our job is to localize the content so it can be understood by as many people as possible, that includes people who don't understand even the most common of English words.
* For units we follow the Si-standards. That means we translate 20MB as 20 MB with a white space. Kilobytes as kB. Note that Signal does not use KiB, MiB etc, because Signal is following the same units as the Android operating system. The same rule applies to other units such as 10s becoming 10 s. Abbreviations for minutes, months and weeks are not si units but we agreed to translate those as "min", "mnd" and "w". Capitalization matters.
* The text strings for the app store sometimes contain wordplay. If a good wordplay in Dutch can't be found, than rather leave the word joke out and just factually describe the change.
* Use pronoun + "wie" instead of "die" wherever possible. Read [https://taaladvies.net/taal/advies/vraag/1564 Taaladvies about wie/die] about where to use "wie" and where to use "die". This is a style choice we made to make complex sentences easier to comprehend.
* Use "van wie", "bij wie", "op wie" and "voor wie" instead of "waarvan", "waarmee", "waarop" and "waarvoor" wherever possible.
* For texts on buttons in Android and Desktop: use "Aan gesprek deelnemen", "Aan Signal doneren" and "Alice toevoegen". Do not use "Voeg Alice toe" or "Deelnemen aan gesprek" or "Doneren aan Signal". reason for this is optial readability. Also capitalize the first letter. on iOS we have not yet decided on the style, because that operating system often uses 'gebiedende wijs' rather than 'infinitief'.
* Try to stick to Dutch words, even if you see English words being used in other apps: "timer" becomes "tijdspanne", "admin" "beheerder", "checkbox" "selectievakje of aankruisvakje", "updaten" "bijwerken", "icon" "pictogram", "non-profit" "organisatie zonder winstoogmerk", "error" "fout", "database""databank" etc. You can find words like these listed in the Transifex Glossary for the Dutch Signal project.
* Beware of capitalization: use "QR-code" do not use "QR-Code" or "qr-code". "WiFi" is spelled different in Dutch: "wifi" all lowercase and without a dash. You can find words like these listed in the Transifex Glossary for the Dutch Signal project.
* Use [https://onzetaal.nl/taaladvies/signaalwoorden-lijst/ signal words] (words that indicate summation, contradiction etc.) wherever possible.
* Use formal verbs where their is no difference in meaning: use "je kunt" not "je kan". Howerver for "kun je" versus "kan je" there is a minor difference: "kan je" is more proposing while "kun je" is more forcefully suggestive. Therefore we use "kan je" instead of "kun je", and "zal je" instead of "zul je". [https://taalhelden.org/bericht/het-kan-je-kun-je https://taalhelden.org/bericht/het-kan-je-kun-je]
* Don't forget that although in English articles can be omitted, in Dutch it's not an accepted practice to omit the article. For example: "Playback time of audio attachment" should be localized as "Afspeellengte van HET audiobericht".

Extra example:
* Don't localize "Other Signal users who are saved to your phone's contact list." as "Andere Signal-gebruikers die zijn opgeslagen in jouw telefoons contactenlijst." but instead localize it as "Andere Signal-gebruikers van wie het telefoonnummer voor komt in de systeemcontactenlijst van jouw telefoon."

===Other projects===
For other projects the style has not yet been written down, however some translators seem to hold on to [http://download.microsoft.com/download/4/7/e/47e135ad-15d7-4491-be78-369804f0d333/nld-nld-StyleGuide.pdf a style guide from Microsoft].

==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.
* ANY time you edit a translation on a project with multiple separate resources, make sure to open all the resources and check if the same string exists elsewhere to apply the exact same edit there. An example would be when you edit a string in the Android Signal messenger app, make sure to also check if the same string exists in the Desktop app, the iOS app, the website or the support center. It's not easy for other reviewers to spot the inconsistency later, so do this right away at the very moment you make an edit.
* Be extra careful with plurals in Transifex, it's easy to miss one of the plural forms when reviewing. You can check all plurals again by searching for pluralized:yes
* Found a spelling mistake, grammar mistake, word order mistake or some word which is better substituted with another word? Don't just correct it when you see it and move on, check all the strings on all the resources for the same mistake or imperfection and correct that mistake on all the strings where it occurs. the moment you noticed something is the only opportunity to come up with a consistent solution across all the strings.

==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 punctuation is accurate, the capitalization is accurate, there are no double white spaces, and no missing white spaces
* 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.
* Don't just look at untranslated string, some strings are automatically translated by Transifex but might still be wrong because the context requires a different translation. use source_updated_after:dd-mm-yyyy to find all the new strings. Also check for edits made by others, using translation_updated_after:dd-mm-yyyy .

==Language varieties==
If you want to localize a project to a language variety which has strong similarities to Dutch and if there already exist good quality translations to Dutch, than it is recommended to base your translations of Dutch rather than English or an other source language. This may make translations faster, but more importantly it also keeps the texts consistent, so that someone who lives just across the border doesn't see completely different texts for the same project. In Transifex there is an option to swap which language you are using as the source language for your translations; you will find it by clicking the setting icon in the top right of the translation interface. Any string that have not yet been translated to Dutch will automatically still be shown as the original source language for the project (usually English).

===using nl or nl_NL for Flemish (nl_BE)===
* About compromising between Flemish and Dutch: If a project does not accept translations for nl_BE than unfortunately for Flanders, the languages nl and nl_NL will still follow Dutch standard language (Nederlandse standaardtaal). It is not possible to make nl into a mix or compromise between both languages to satisfy both languages. If Flemish translators want to work on a project, they should contact a project maintainer and ask to add a nl_BE project.

===Other varieties===
Other varieties are
* nl-AW Dutch (Aruba)
* nl-BE Dutch (Belgium)
* nl-BQ Dutch (Caribbean Netherlands)
* nl-CW Dutch (Curaçao)
* nl-SR Dutch (Suriname)
* nl-SX Dutch (Sint Maarten)
* af (Afrikaans)

==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.''

===Grammer and word order in sentences===
*[https://www.dutchgrammar.com/en/?n=WordOrder.00 https://www.dutchgrammar.com/en/?n=WordOrder.00] About word order in sentences. It's not just one page, keep clicking on next page in the bottom right to see more examples.
*[http://redekundig.nl/ http://redekundig.nl/] a tool to help identify the structure of a Dutch sentence. Very helpful if you're dealing with complex grammatical rules and need to understand the sentence you are reviewing.
* [https://urd2.let.rug.nl/~vannoord/bin/alpino https://urd2.let.rug.nl/~vannoord/bin/alpino] university hosted tool to identify structure of a Dutch sentence. It's the same tool as redekundig.nl but hosted elsewhere, and the interface is harder to comprehend. Would advise trying this in case redekundig.nl isn't giving you the information you need.
* [https://onzetaal.nl/taaladvies/signaalwoorden-lijst/ List of signal words], use these wherever possible, they help clarify your message and prevent ambiguity.

===Style and tone===
* First follow any style guide you find here on this wiki for language and project you are working on
* If you are missing something, contact other translators
* If you search for style advise from other websites, avoid getting it from tech companies who make up their own version of Dutch language based on marketing rather than proper standard Dutch. Also avoid other wiki's which are often written by opinionated people who are not representative for the language. That doesn't mean you can't read them and learn from them, but take it with a grain of salt.

===Spelling===
*[https://taaladvies.net Taaladvies]
*[https://taal.vrt.be Taalnet]
*[https://onzetaal.nl OnzeTaal]

===Technical terminology===
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:
[https://docs.google.com/spreadsheets/d/1OPyeWDq2rtPf9fEpCLRpHl9Hn--OfFbWLbrGtZx3lYI/edit?usp=sharing Dutch Unified Localization Lab Glossary]. The document is maintained by Erin (a localization lab employee). If you wish to add comments, edits or suggest new entries, do so using the "Comment" feature in the spreadsheet.

Language Resources

2021-03-23T15:21:35Z

Meteor0id:

Want to add a language team page? You can use and customize the [[Language Team Template]] to get started.
<div style="float:right; margin-left:2.5em">__TOC__</div>
==Language Team Pages==

{| class="wikitable sortable"
|-
! Language Team
! [https://en.wikipedia.org/wiki/List_of_ISO_639-1_codes ISO 639-1] Codes
|-
| [[Amharic]]
| am
|-
| [[Arabic]]
| ar
|-
| [[Bahasa Indonesia]]
| id
|-
| [[Burmese]]
| my
|-
| [[Catalan]]
| ca
|-
| [[Simplified Chinese]]
| zh, zh_CH, zh-Hans
|-
| [[Traditional Chinese]]
| zh, zh_TW, zh-Hant
|-
| [[Dutch]]
| nl, nl_BE, fy, af
|-
| [[French]]
| fr
|-
| [[German]]
| de
|-
| [[Greek]]
| el
|-
| [[Kannada]]
| kn
|-
| [[Khmer]]
| km
|-
| [[Kurdish (Kurmanji)]]
| kmr
|-
| [[Kurdish (Sorani)]]
| ckb
|-
| [[Luganda]]
| lg
|-
| [[Malayalam]]
| ml
|-
| [[Afaan Oromoo]]
| om
|-
| [[Persian]]
| fa
|-
| [[Portuguese]]
| pt, pt_PT, pt_BR
|-
| [[Serbian]]
| sr
|-
| [[Shona]]
| sn
|-
| [[Spanish]]
| es
|-
| [[Swahili]]
| sw
|-
| [[Tigrinya]]
| ti
|-
| [[Thai]]
| th
|-
| [[Turkish]]
| tr
|-
| [[Turkmen]]
| tk
|-
| [[Ukrainian]]
| uk
|}

==Multi-Lingual Glossaries==
* [https://www.wikipedia.org/ Wikipedia] *Search for a term in English and refer to the "Languages" section in the sidebar to see if a page for that term exists in your language. You can also add terms yourself: "[https://en.wikipedia.org/wiki/Wikipedia:Translation#How_to_translate How to Translate]"

* [https://www.microsoft.com/Language/en-US/Search.aspx Microsoft Language Portal Searchable Terminologies]

* [http://www.it46.se/glossmaster/ African Network for Localization FOSS Glossaries] *Glossaries are downloadable as CSV and are available for Akan, Arabic, Amharic, French, Kinyarwanda, Lingala, Luganda, Songhay, Yoruba, and Zulu.

* Electronic Frontier Foundation's [https://ssd.eff.org/en/glossary Security Self-Defense Glossary] *Available in: Amharic, Arabic, French, Russian, Spanish, Thai, Turkish, Vietnamese, Urdu

==Multi-Lingual Style Guides==
* [https://www.microsoft.com/en-US/Language/StyleGuides Microsoft Language Portal Downloadable Style Guides] 
* [https://wiki.mozilla.org/Category:L10n_Teams Mozilla Language Team Resources] *Find your language by its [https://www.loc.gov/standards/iso639-2/php/code_list.php ISO 639-1/2 code]

==Terminology & Glossary Planning==
===Term Planning===
[http://www.terminfo.fi/sisalto/term-planning-for-irish--and-other-languages-85.html Term planning for Irish – and other languages]

Language Resources

2021-03-23T15:19:53Z

Meteor0id: For now, consider Afrikaans as part of Dutch

Want to add a language team page? You can use and customize the [[Language Team Template]] to get started.
<div style="float:right; margin-left:2.5em">__TOC__</div>
==Language Team Pages==

{| class="wikitable sortable"
|-
! Language Team
! [https://en.wikipedia.org/wiki/List_of_ISO_639-1_codes ISO 639-1] Codes
|-
| [[Amharic]]
| am
|-
| [[Arabic]]
| ar
|-
| [[Bahasa Indonesia]]
| id
|-
| [[Burmese]]
| my
|-
| [[Catalan]]
| ca
|-
| [[Simplified Chinese]]
| zh, zh_CH, zh-Hans
|-
| [[Traditional Chinese]]
| zh, zh_TW, zh-Hant
|-
| [[Dutch]]
| nl, nl_NL, nl_BE, fy, af
|-
| [[French]]
| fr
|-
| [[German]]
| de
|-
| [[Greek]]
| el
|-
| [[Kannada]]
| kn
|-
| [[Khmer]]
| km
|-
| [[Kurdish (Kurmanji)]]
| kmr
|-
| [[Kurdish (Sorani)]]
| ckb
|-
| [[Luganda]]
| lg
|-
| [[Malayalam]]
| ml
|-
| [[Afaan Oromoo]]
| om
|-
| [[Persian]]
| fa
|-
| [[Portuguese]]
| pt, pt_PT, pt_BR
|-
| [[Serbian]]
| sr
|-
| [[Shona]]
| sn
|-
| [[Spanish]]
| es
|-
| [[Swahili]]
| sw
|-
| [[Tigrinya]]
| ti
|-
| [[Thai]]
| th
|-
| [[Turkish]]
| tr
|-
| [[Turkmen]]
| tk
|-
| [[Ukrainian]]
| uk
|}

==Multi-Lingual Glossaries==
* [https://www.wikipedia.org/ Wikipedia] *Search for a term in English and refer to the "Languages" section in the sidebar to see if a page for that term exists in your language. You can also add terms yourself: "[https://en.wikipedia.org/wiki/Wikipedia:Translation#How_to_translate How to Translate]"

* [https://www.microsoft.com/Language/en-US/Search.aspx Microsoft Language Portal Searchable Terminologies]

* [http://www.it46.se/glossmaster/ African Network for Localization FOSS Glossaries] *Glossaries are downloadable as CSV and are available for Akan, Arabic, Amharic, French, Kinyarwanda, Lingala, Luganda, Songhay, Yoruba, and Zulu.

* Electronic Frontier Foundation's [https://ssd.eff.org/en/glossary Security Self-Defense Glossary] *Available in: Amharic, Arabic, French, Russian, Spanish, Thai, Turkish, Vietnamese, Urdu

==Multi-Lingual Style Guides==
* [https://www.microsoft.com/en-US/Language/StyleGuides Microsoft Language Portal Downloadable Style Guides] 
* [https://wiki.mozilla.org/Category:L10n_Teams Mozilla Language Team Resources] *Find your language by its [https://www.loc.gov/standards/iso639-2/php/code_list.php ISO 639-1/2 code]

==Terminology & Glossary Planning==
===Term Planning===
[http://www.terminfo.fi/sisalto/term-planning-for-irish--and-other-languages-85.html Term planning for Irish – and other languages]

Translation and Review Guidelines

2021-03-23T15:14:32Z

Meteor0id: correction to header formatting

__TOC__

'''Please review the tips and guidelines below prior to localizing projects. The following information will help you navigate the Transifex interface and more effectively and accurately translate and review projects.'''

{|class="wikitable" style="margin-right: auto; margin-left: 0px; width: Auto; background-color:#ffcccc;"
|
===Do not Machine Translate===
:Machine translation tools like Google Translate and Microsoft Translator Hub are useful resources, however they should never be used as the foundation of your translation, particularly long-form text which is less and less likely to be accurate the longer it is.

:Keep in mind that even if you heavily post-edit machine translations, the grammar, style, tone and terminology used in the machine translation can still greatly affect your translation.
|}

{|class="wikitable" style="margin-right: auto; margin-left: 0px; width: Auto; background-color:#ffcccc;"
|
===Communicate===
:'''''Leave '''[https://docs.transifex.com/translation/tools-in-the-editor#comments Comments]''' for other translators'''''
::Localization in the Localization Lab community is a group effort! If you are simply fixing a typo or grammatical error, feel free to make the changes necessary without leaving a comment. If you are changing key terminology or significantly changing the structure of a translation, leave a comment for the previous translator to briefly explain the change. Be sure the ''mention'' them by including @ followed by their username in your comment.
::Leaving comments ensures that other contributors understand why you have made changes, can learn from them, and can make sure to apply the changes to future translations.
:'''''Leave '''[https://docs.transifex.com/translation/tools-in-the-editor#issues Issues]''' for project maintainers'''''
::If you don't understand what a string means, need more context or there is a typo or fundamental issue with the source text, let the project maintainer know! You can do this by creating an ''Issue''. Developers and project maintainers are notified of issues so that they can be addressed efficiently.

::There are several priority levels to chose from when creating an issue:
::*'''Low:''' Minor and cosmetic changes to a source string.
::* '''Normal:''' Typos, questions or changes affecting the meaning of a source string that may hinder translation.
::* '''High:''' Significant issues with the localizability or coherence of the source string.
::* '''Critical:''' Issues with the source string that might break the software.
|}

{|class="wikitable" style="margin-right: auto; margin-left: 0px; width: Auto; background-color:#ffcccc;"
|
===Read the ''Developer Notes'' and ''Translation Instructions'' in Transifex===
:The ''Developer Notes'' and ''Instructions'' are located in the Web Editor in between the source text and the translation text field. Make sure to read and follow any available instructions for the string you are translating.

[[File:Developer notes.png|500px|center|Example of ''Developer Notes''.]]
 
|}

{|class="wikitable" style="margin-right: auto; margin-left: 0px; width: Auto; background-color:#ffcccc;"
|
===Do not translate or transliterate application or project names.===
:Do not translate or transliterate project, company or application names that do not have an official or widely adopted regional variation.

:Some projects have widely used and accepted translations or transliterations of their names. If this is the case in your language, feel free to use the localized version.
::'''Example:''' تويتر (''Transliteration of Twitter in Arabic'')

|}

{|class="wikitable" style="margin-right: auto; margin-left: 0px; width: Auto; background-color:#ffcccc;"
|
===Focus on Consistency===
In addition to recurring terminology, you will often encounter strings that are duplicate or directly reference other strings. It is important to ensure these translations are consistent across the entirety of a project.
::'''Example:''' If "Create Account" appears in a string in a project, use the [https://docs.transifex.com/translation/translating-with-the-web-editor#searching-and-filtering-for-strings filters] in the Web Editor to see where else "Create Account" appears in the rest of the project resources and make sure the translation is consistent.

[[File:Reference_to_another_string_1.png|500px|center|Reference to "Create Account" in a string.]] 
[[File:Reference_to_another_string_2.png|500px|center|Original "Create Account" string.]] 

:Transifex has several features to help you manage consistency across translations:
:* The '''[https://docs.transifex.com/translation/using-translation-memory-and-concordance-search#concordance-search Concordance Search]''' allows you to search for words and phrases across multiple resources within the same project and across different projects within the same organization. You can use it to see how something is translated in different strings and contexts.
:* The '''[https://docs.transifex.com/projects/search-strings Search Strings]''' feature in Transifex allows you to search words and phrases across all Localization Lab projects using more filters than are available in the simple Concordance Search. You can filter matches by project, resource, target language, source language, tag, date etc.
:* Web Editor '''[https://docs.transifex.com/translation/translating-with-the-web-editor#searching-and-filtering-for-strings Filters]''' allow you to filter and search strings across one or multiple resources in a project. Among many options, you can filter by word or phrase in the source text or in the translation text.
:* The '''[https://docs.transifex.com/translation/using-translation-memory-and-concordance-search#understanding-translation-memory-suggestions Suggestions tab]''' in the web editor lets you view translations from the Localization Lab Translation Memory from other strings and resources in related projects. Translations of strings which are up to 60% the same will appear in this tab. Referencing these suggestions can help you maintain consistency across projects.
:* The Localization Lab '''[https://docs.transifex.com/translation/using-the-glossary Glossary]''' is very robust in English, however not all languages have translations for each term. Use the ''Glossary'' tab to double check translation of a term. If the term is not there, select ''View Glossary'' to [https://docs.transifex.com/setup/glossary/adding-terms add the translation to the glossary].
:::Key project terms will have the label "[project name]" in the ''Comments'' field for the term.
|}

{|class="wikitable" style="margin-right: auto; margin-left: 0px; width: Auto; background-color:#ffcccc;"
|

===Watch out for Placeholders, HTML and Unicode Character Entities, and Markup Language.===
====Placeholders and Variables====
::Many project strings contain '''placeholders''' which may replace [https://www.quackit.com/html/tags/ HTML], [https://www.quackit.com/xml/tutorial/about_xml.cfm XML] or words and numbers that change within the application's interface. '''It is important to keep these placeholders unchanged in the translation'''. You can move the placeholders depending on where they grammatically make the most sense in your language. 
::Hover your mouse over the variable in the English source text to see what the placeholder is replacing.
[[File:variable.png|500px|center|Variables in Transifex]] 
::Sometimes a variable will not be recognized by Transifex and will be editable in the web editor. If you see an element within curly brackets, you can assume that in most cases you should '''not translate''' anything inside the brackets. Double check the ''Developer Notes'' to see if there are any special notes about how to treat the content in brackets. If you are still unsure, create an "Issue" for the string so that a project maintainer can clarify.
[[File:Curly bracket variable.png|500px|center|Curly bracket variables in Transifex]] 
::Placeholders will often provide hints as to what they replace in the app's user interface. If you cannot determine what the placeholder will replace in the app and as a result, don't know how to translate the surrounding content, '''create an issue''' and ask the project maintainer.
::Below, the placeholder '''"{language}"''' will be replaced by the name of a language.
[[File:Language Variable Check.png|500px|center|Language Variable in Transifex]] 
::Below you can see how the variables '''"{author}"''', '''"{title}"''' and '''"{status}"''' are replaced by different text in the [[Check]] user interface.
[[File:Status Variable Check.png|300px|center|Status and Author Variables in Check]] [[File:Author_Title_Variables.png|300px|center|Author and Title Variables in Check]] 
[[File:Context for Check Variables.png|300px|center|Context for Check Variables]] 
::Review the [https://docs.transifex.com/translation/html-files#in-the-new-editor Transifex documentation] to learn how to manage placeholders in the translation editor. 

====HTML and Unicode Character Entities & Mark Down Language====
::Sometimes an HTML character entity will not be recognized and replaced by Transifex. In these cases, you can either copy the exact character entity or you can replace it with what it corresponds to. 
::You can look up HTML entities on the [https://www.w3schools.com/charsets/ref_html_entities_4.asp W3 website].

::'''Examples:'''
::* '''&nbsp;''' is a non-breaking space
::* '''&lt;''' is equivalent to <
::* '''&gt;''' is equivalent to >
[[File:HTML character entity 2.png|500px|center|HTML variable in Transifex]] 
[[File:HTML character entity 1.png|500px|center|HTML variable in Transifex]] 

====New lines====
::The little blue arrows in the source text are equivalent to a new line (''/n''). Make sure to input new lines where indicated in the source text. Do so by simply selecting the ''Enter'' or ''Return'' key on your keyboard. The number of new lines in the translation should be the exact same as the number in the English source text. 
|}

{|class="wikitable" style="margin-right: auto; margin-left: 0px; width: Auto; background-color:#ffcccc;"
|
===Pay Attention to the "notranslate" Tag===
:Some strings will be assigned the "notranslate" tag and you will find a special message at the bottom of the translation input field. These strings should be copied ''exactly'' using the copy icon in the web editor. If you do not copy these strings exactly, Transifex will give you an error warning.

::''The translation in the example below is '''incorrect''' because this string should be an exact copy of the English source text.''

[[File:Notranslate.png|500px|center|Notranslate tag in Transifex]] 
|}

{|class="wikitable" style="margin-right: auto; margin-left: 0px; width: Auto; background-color:#ffcccc;"
|
===Punctuation, Capitalization, Double Spaces and Typos===
The small details make a big difference in the end product. Individuals are less likely to trust a tool whose interface is messy or has inconsistent punctuation and capitalization, even if the translation itself is correct.

:'''While you are translating and reviewing, make sure that you:'''
:*Use the correct and consistent punctuation;
:*Use correct and consistent capitalization. If there are individual terms that are capitalized in the English source, they are most likely capitalized for a reason. Double check to see if you should also capitalize in the target language translation;
:*Add the correct number of brackets, parentheses and curly brackets in your translation; and
:*Do not add double spaces unless they are present in the original source content. You can turn on "Display Spaces" in your [https://docs.transifex.com/translation/translating-with-the-web-editor#editor-settings Transifex Editor Settings] which will help you visualize spaces in the source text and your translation.

::[[File:Display_Spaces.png|500px|center|Display Spaces Transifex]]
|}

{|class="wikitable" style="margin-right: auto; margin-left: 0px; width: Auto; background-color:#ffcccc;"
|
===Reference other Languages===
If you are multi-lingual, you can view both the English source text and current translations in another language that you speak. This can be helpful when trying to understand the context and meaning of the English source text.

You can add an additional source language through the [https://docs.transifex.com/translation/translating-with-the-web-editor#editor-settings Transifex Editor Settings] in the web editor.

'''Please remember''' that the current translations in another language may or may not be reviewed by a trusted contributor, and you should ultimately defer to the English source text.
|}

{|class="wikitable" style="margin-right: auto; margin-left: 0px; width: Auto; background-color:#ffcccc;"
|
===Always keep the end-user in mind===
Ask yourself: "If my 65 year old mother read this (who has a total of 3 apps on her phone and uses only one of them on a weekly basis), would she understand this without anyone's help?". The goal is not to translate words or sentences, the goal is to make the text understandable to people who grew up in a different country.
|}

{|class="wikitable" style="margin-right: auto; margin-left: 0px; width: Auto; background-color:#ffcccc;"
|
===Know the Style Guide===
Check to see if there is a style guide for [https://wiki.localizationlab.org/index.php/Language_Resources your language] on this wiki.

No style guide on the Localization Lab wiki for your language team? Refer to [https://wiki.localizationlab.org/index.php/Language_Resources#Multi-Lingual_Style_Guides style guides for other technical projects].
|}

Translation and Review Guidelines

2021-03-23T15:12:50Z

Meteor0id: Add the end-user philosophy

__TOC__

'''Please review the tips and guidelines below prior to localizing projects. The following information will help you navigate the Transifex interface and more effectively and accurately translate and review projects.'''

{|class="wikitable" style="margin-right: auto; margin-left: 0px; width: Auto; background-color:#ffcccc;"
|
===Do not Machine Translate===
:Machine translation tools like Google Translate and Microsoft Translator Hub are useful resources, however they should never be used as the foundation of your translation, particularly long-form text which is less and less likely to be accurate the longer it is.

:Keep in mind that even if you heavily post-edit machine translations, the grammar, style, tone and terminology used in the machine translation can still greatly affect your translation.
|}

{|class="wikitable" style="margin-right: auto; margin-left: 0px; width: Auto; background-color:#ffcccc;"
|
===Communicate===
:'''''Leave '''[https://docs.transifex.com/translation/tools-in-the-editor#comments Comments]''' for other translators'''''
::Localization in the Localization Lab community is a group effort! If you are simply fixing a typo or grammatical error, feel free to make the changes necessary without leaving a comment. If you are changing key terminology or significantly changing the structure of a translation, leave a comment for the previous translator to briefly explain the change. Be sure the ''mention'' them by including @ followed by their username in your comment.
::Leaving comments ensures that other contributors understand why you have made changes, can learn from them, and can make sure to apply the changes to future translations.
:'''''Leave '''[https://docs.transifex.com/translation/tools-in-the-editor#issues Issues]''' for project maintainers'''''
::If you don't understand what a string means, need more context or there is a typo or fundamental issue with the source text, let the project maintainer know! You can do this by creating an ''Issue''. Developers and project maintainers are notified of issues so that they can be addressed efficiently.

::There are several priority levels to chose from when creating an issue:
::*'''Low:''' Minor and cosmetic changes to a source string.
::* '''Normal:''' Typos, questions or changes affecting the meaning of a source string that may hinder translation.
::* '''High:''' Significant issues with the localizability or coherence of the source string.
::* '''Critical:''' Issues with the source string that might break the software.
|}

{|class="wikitable" style="margin-right: auto; margin-left: 0px; width: Auto; background-color:#ffcccc;"
|
===Read the ''Developer Notes'' and ''Translation Instructions'' in Transifex===
:The ''Developer Notes'' and ''Instructions'' are located in the Web Editor in between the source text and the translation text field. Make sure to read and follow any available instructions for the string you are translating.

[[File:Developer notes.png|500px|center|Example of ''Developer Notes''.]]
 
|}

{|class="wikitable" style="margin-right: auto; margin-left: 0px; width: Auto; background-color:#ffcccc;"
|
===Do not translate or transliterate application or project names.===
:Do not translate or transliterate project, company or application names that do not have an official or widely adopted regional variation.

:Some projects have widely used and accepted translations or transliterations of their names. If this is the case in your language, feel free to use the localized version.
::'''Example:''' تويتر (''Transliteration of Twitter in Arabic'')

|}

{|class="wikitable" style="margin-right: auto; margin-left: 0px; width: Auto; background-color:#ffcccc;"
|
===Focus on Consistency===
In addition to recurring terminology, you will often encounter strings that are duplicate or directly reference other strings. It is important to ensure these translations are consistent across the entirety of a project.
::'''Example:''' If "Create Account" appears in a string in a project, use the [https://docs.transifex.com/translation/translating-with-the-web-editor#searching-and-filtering-for-strings filters] in the Web Editor to see where else "Create Account" appears in the rest of the project resources and make sure the translation is consistent.

[[File:Reference_to_another_string_1.png|500px|center|Reference to "Create Account" in a string.]] 
[[File:Reference_to_another_string_2.png|500px|center|Original "Create Account" string.]] 

:Transifex has several features to help you manage consistency across translations:
:* The '''[https://docs.transifex.com/translation/using-translation-memory-and-concordance-search#concordance-search Concordance Search]''' allows you to search for words and phrases across multiple resources within the same project and across different projects within the same organization. You can use it to see how something is translated in different strings and contexts.
:* The '''[https://docs.transifex.com/projects/search-strings Search Strings]''' feature in Transifex allows you to search words and phrases across all Localization Lab projects using more filters than are available in the simple Concordance Search. You can filter matches by project, resource, target language, source language, tag, date etc.
:* Web Editor '''[https://docs.transifex.com/translation/translating-with-the-web-editor#searching-and-filtering-for-strings Filters]''' allow you to filter and search strings across one or multiple resources in a project. Among many options, you can filter by word or phrase in the source text or in the translation text.
:* The '''[https://docs.transifex.com/translation/using-translation-memory-and-concordance-search#understanding-translation-memory-suggestions Suggestions tab]''' in the web editor lets you view translations from the Localization Lab Translation Memory from other strings and resources in related projects. Translations of strings which are up to 60% the same will appear in this tab. Referencing these suggestions can help you maintain consistency across projects.
:* The Localization Lab '''[https://docs.transifex.com/translation/using-the-glossary Glossary]''' is very robust in English, however not all languages have translations for each term. Use the ''Glossary'' tab to double check translation of a term. If the term is not there, select ''View Glossary'' to [https://docs.transifex.com/setup/glossary/adding-terms add the translation to the glossary].
:::Key project terms will have the label "[project name]" in the ''Comments'' field for the term.
|}

{|class="wikitable" style="margin-right: auto; margin-left: 0px; width: Auto; background-color:#ffcccc;"
|

===Watch out for Placeholders, HTML and Unicode Character Entities, and Markup Language.===
====Placeholders and Variables====
::Many project strings contain '''placeholders''' which may replace [https://www.quackit.com/html/tags/ HTML], [https://www.quackit.com/xml/tutorial/about_xml.cfm XML] or words and numbers that change within the application's interface. '''It is important to keep these placeholders unchanged in the translation'''. You can move the placeholders depending on where they grammatically make the most sense in your language. 
::Hover your mouse over the variable in the English source text to see what the placeholder is replacing.
[[File:variable.png|500px|center|Variables in Transifex]] 
::Sometimes a variable will not be recognized by Transifex and will be editable in the web editor. If you see an element within curly brackets, you can assume that in most cases you should '''not translate''' anything inside the brackets. Double check the ''Developer Notes'' to see if there are any special notes about how to treat the content in brackets. If you are still unsure, create an "Issue" for the string so that a project maintainer can clarify.
[[File:Curly bracket variable.png|500px|center|Curly bracket variables in Transifex]] 
::Placeholders will often provide hints as to what they replace in the app's user interface. If you cannot determine what the placeholder will replace in the app and as a result, don't know how to translate the surrounding content, '''create an issue''' and ask the project maintainer.
::Below, the placeholder '''"{language}"''' will be replaced by the name of a language.
[[File:Language Variable Check.png|500px|center|Language Variable in Transifex]] 
::Below you can see how the variables '''"{author}"''', '''"{title}"''' and '''"{status}"''' are replaced by different text in the [[Check]] user interface.
[[File:Status Variable Check.png|300px|center|Status and Author Variables in Check]] [[File:Author_Title_Variables.png|300px|center|Author and Title Variables in Check]] 
[[File:Context for Check Variables.png|300px|center|Context for Check Variables]] 
::Review the [https://docs.transifex.com/translation/html-files#in-the-new-editor Transifex documentation] to learn how to manage placeholders in the translation editor. 

====HTML and Unicode Character Entities & Mark Down Language====
::Sometimes an HTML character entity will not be recognized and replaced by Transifex. In these cases, you can either copy the exact character entity or you can replace it with what it corresponds to. 
::You can look up HTML entities on the [https://www.w3schools.com/charsets/ref_html_entities_4.asp W3 website].

::'''Examples:'''
::* '''&nbsp;''' is a non-breaking space
::* '''&lt;''' is equivalent to <
::* '''&gt;''' is equivalent to >
[[File:HTML character entity 2.png|500px|center|HTML variable in Transifex]] 
[[File:HTML character entity 1.png|500px|center|HTML variable in Transifex]] 

====New lines====
::The little blue arrows in the source text are equivalent to a new line (''/n''). Make sure to input new lines where indicated in the source text. Do so by simply selecting the ''Enter'' or ''Return'' key on your keyboard. The number of new lines in the translation should be the exact same as the number in the English source text. 
|}

{|class="wikitable" style="margin-right: auto; margin-left: 0px; width: Auto; background-color:#ffcccc;"
|
===Pay Attention to the "notranslate" Tag===
:Some strings will be assigned the "notranslate" tag and you will find a special message at the bottom of the translation input field. These strings should be copied ''exactly'' using the copy icon in the web editor. If you do not copy these strings exactly, Transifex will give you an error warning.

::''The translation in the example below is '''incorrect''' because this string should be an exact copy of the English source text.''

[[File:Notranslate.png|500px|center|Notranslate tag in Transifex]] 
|}

{|class="wikitable" style="margin-right: auto; margin-left: 0px; width: Auto; background-color:#ffcccc;"
|
===Punctuation, Capitalization, Double Spaces and Typos===
The small details make a big difference in the end product. Individuals are less likely to trust a tool whose interface is messy or has inconsistent punctuation and capitalization, even if the translation itself is correct.

:'''While you are translating and reviewing, make sure that you:'''
:*Use the correct and consistent punctuation;
:*Use correct and consistent capitalization. If there are individual terms that are capitalized in the English source, they are most likely capitalized for a reason. Double check to see if you should also capitalize in the target language translation;
:*Add the correct number of brackets, parentheses and curly brackets in your translation; and
:*Do not add double spaces unless they are present in the original source content. You can turn on "Display Spaces" in your [https://docs.transifex.com/translation/translating-with-the-web-editor#editor-settings Transifex Editor Settings] which will help you visualize spaces in the source text and your translation.

::[[File:Display_Spaces.png|500px|center|Display Spaces Transifex]]
|}

{|class="wikitable" style="margin-right: auto; margin-left: 0px; width: Auto; background-color:#ffcccc;"
|
===Reference other Languages===
If you are multi-lingual, you can view both the English source text and current translations in another language that you speak. This can be helpful when trying to understand the context and meaning of the English source text.

You can add an additional source language through the [https://docs.transifex.com/translation/translating-with-the-web-editor#editor-settings Transifex Editor Settings] in the web editor.

'''Please remember''' that the current translations in another language may or may not be reviewed by a trusted contributor, and you should ultimately defer to the English source text.
|}

{|class="wikitable" style="margin-right: auto; margin-left: 0px; width: Auto; background-color:#ffcccc;"
|
==Always keep the end-user in mind==
Ask yourself: "If my 65 year old mother read this (who has a total of 3 apps on her phone and uses only one of them on a weekly basis), would she understand this without anyone's help?". The goal is not to translate words or sentences, the goal is to make the text understandable to people who grew up in a different country.
|}

{|class="wikitable" style="margin-right: auto; margin-left: 0px; width: Auto; background-color:#ffcccc;"
|
===Know the Style Guide===
Check to see if there is a style guide for [https://wiki.localizationlab.org/index.php/Language_Resources your language] on this wiki.

No style guide on the Localization Lab wiki for your language team? Refer to [https://wiki.localizationlab.org/index.php/Language_Resources#Multi-Lingual_Style_Guides style guides for other technical projects].
|}

Dutch

2021-03-23T15:08:03Z

Meteor0id: add philosophy of localization

__TOC__

==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 [https://internetfreedomfestival.org/ International Freedom Festival] domain and is subject to their [https://www.internetfreedomfestival.org/wiki/index.php/Code_of_Conduct Code of Conduct]. Be sure to read through the [https://www.internetfreedomfestival.org/wiki/index.php/Code_of_Conduct Code of Conduct] and then [mailto:info@localizationlab.org?subject=Mattermost%20Sign-up&body=Please%20send%20me%20a%20link%20to%20sign%20up%20for%20Mattermost. 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==
Ask yourself: "If my 65 year old mother read this (who has a total of 3 apps on her phone and uses only one of them on a weekly basis), would she understand this without anyone's help?". The goal is not to translate words, the goal is to make the text understandable to people who grew up in a different country.

===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. We will try to make this styleguide easier to read in the future.''

* 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. 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, meaning different words and/or a different structure of the sentence. An example: "Signal needs location services enabled to discover and connect with your old Android device." is localized as "Om je oude Android apparaat te kunnen detecteren en om er verbinding mee te maken is het nodig dat locatiebepaling op je apparaat is ingeschakeld.". Another example: don't write "Om het in te schakelen, tik op de schuifknop zodat hij blauw wordt." but instead write "Tik op de schuifknop zodat hij blauw wordt om meekijkpreventie in te schakelen."
* 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 punctuation, end the sentence with a period. If the description does not contain any punctuation, 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 Dutch people also get it wrong. [https://www.dutchgrammar.com/en/?n=WordOrder.00] 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. An example: Don't write "Deze personen kunnen door jou niet direct worden toegevoegd aan de groep." instead write "Deze personen kunnen door jou niet direct aan de groep worden toegevoegd.".
* 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 white space: 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 …
* Make sure the subject is repeated in every new sentence, do not refer back to a previous sentence. We do this to keep texts easy to read and understand. An example: do not write "Turing this on allows you to receive emails. They will contain information about your account." instead write "Turning this on allows you to receive emails. The emails you will receive contain information about your account.".
* Avoid anglicisms, our job is to localize the content so it can be understood by as many people as possible, that includes people who don't understand even the most common of English words.
* For units we follow the Si-standards. That means we translate 20MB as 20 MB with a white space. Kilobytes as kB. Note that Signal does not use KiB, MiB etc, because Signal is following the same units as the Android operating system. The same rule applies to other units such as 10s becoming 10 s. Abbreviations for minutes, months and weeks are not si units but we agreed to translate those as "min", "mnd" and "w". Capitalization matters.
* The text strings for the app store sometimes contain wordplay. If a good wordplay in Dutch can't be found, than rather leave the word joke out and just factually describe the change.
* Use pronoun + "wie" instead of "die" wherever possible. Read [https://taaladvies.net/taal/advies/vraag/1564 Taaladvies about wie/die] about where to use "wie" and where to use "die". This is a style choice we made to make complex sentences easier to comprehend.
* Use "van wie", "bij wie", "op wie" and "voor wie" instead of "waarvan", "waarmee", "waarop" and "waarvoor" wherever possible.
* For texts on buttons in Android and Desktop: use "Aan gesprek deelnemen", "Aan Signal doneren" and "Alice toevoegen". Do not use "Voeg Alice toe" or "Deelnemen aan gesprek" or "Doneren aan Signal". reason for this is optial readability. Also capitalize the first letter. on iOS we have not yet decided on the style, because that operating system often uses 'gebiedende wijs' rather than 'infinitief'.
* Try to stick to Dutch words, even if you see English words being used in other apps: "timer" becomes "tijdspanne", "admin" "beheerder", "checkbox" "selectievakje of aankruisvakje", "updaten" "bijwerken", "icon" "pictogram", "non-profit" "organisatie zonder winstoogmerk", "error" "fout", "database""databank" etc. You can find words like these listed in the Transifex Glossary for the Dutch Signal project.
* Beware of capitalization: use "QR-code" do not use "QR-Code" or "qr-code". "WiFi" is spelled different in Dutch: "wifi" all lowercase and without a dash. You can find words like these listed in the Transifex Glossary for the Dutch Signal project.
* Use [https://onzetaal.nl/taaladvies/signaalwoorden-lijst/ signal words] (words that indicate summation, contradiction etc.) wherever possible.
* Use formal verbs where their is no difference in meaning: use "je kunt" not "je kan". Howerver for "kun je" versus "kan je" there is a minor difference: "kan je" is more proposing while "kun je" is more forcefully suggestive. Therefore we use "kan je" instead of "kun je", and "zal je" instead of "zul je". [https://taalhelden.org/bericht/het-kan-je-kun-je https://taalhelden.org/bericht/het-kan-je-kun-je]
* Don't forget that although in English articles can be omitted, in Dutch it's not an accepted practice to omit the article. For example: "Playback time of audio attachment" should be localized as "Afspeellengte van HET audiobericht".

Extra example:
* Don't localize "Other Signal users who are saved to your phone's contact list." as "Andere Signal-gebruikers die zijn opgeslagen in jouw telefoons contactenlijst." but instead localize it as "Andere Signal-gebruikers van wie het telefoonnummer voor komt in de systeemcontactenlijst van jouw telefoon."

===Other projects===
For other projects the style has not yet been written down, however some translators seem to hold on to [http://download.microsoft.com/download/4/7/e/47e135ad-15d7-4491-be78-369804f0d333/nld-nld-StyleGuide.pdf a style guide from Microsoft].

==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.
* ANY time you edit a translation on a project with multiple separate resources, make sure to open all the resources and check if the same string exists elsewhere to apply the exact same edit there. An example would be when you edit a string in the Android Signal messenger app, make sure to also check if the same string exists in the Desktop app, the iOS app, the website or the support center. It's not easy for other reviewers to spot the inconsistency later, so do this right away at the very moment you make an edit.
* Be extra careful with plurals in Transifex, it's easy to miss one of the plural forms when reviewing. You can check all plurals again by searching for pluralized:yes
* Found a spelling mistake, grammar mistake, word order mistake or some word which is better substituted with another word? Don't just correct it when you see it and move on, check all the strings on all the resources for the same mistake or imperfection and correct that mistake on all the strings where it occurs. the moment you noticed something is the only opportunity to come up with a consistent solution across all the strings.

==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 punctuation is accurate, the capitalization is accurate, there are no double white spaces, and no missing white spaces
* 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.
* Don't just look at untranslated string, some strings are automatically translated by Transifex but might still be wrong because the context requires a different translation. use source_updated_after:dd-mm-yyyy to find all the new strings. Also check for edits made by others, using translation_updated_after:dd-mm-yyyy .

==Language varieties==
If you want to localize a project to a language variety which has strong similarities to Dutch and if there already exist good quality translations to Dutch, than it is recommended to base your translations of Dutch rather than English or an other source language. This may make translations faster, but more importantly it also keeps the texts consistent, so that someone who lives just across the border doesn't see completely different texts for the same project. In Transifex there is an option to swap which language you are using as the source language for your translations; you will find it by clicking the setting icon in the top right of the translation interface. Any string that have not yet been translated to Dutch will automatically still be shown as the original source language for the project (usually English).

===(Flemish nl_BE) and Frisian (fy_NL)===
* About compromising between Flemish and Dutch: If a project does not accept translations for nl_BE than unfortunately for Flanders, the languages nl and nl_NL will still follow Dutch standard language (Nederlandse standaardtaal). It is not possible to make nl into a mix or compromise between both languages to satisfy both languages. Flemish translators can contact a project maintainer and ask to add a nl_BE project.

===Other varieties===
Other varieties are
* nl-AW Dutch (Aruba)
* nl-BE Dutch (Belgium)
* nl-BQ Dutch (Caribbean Netherlands)
* nl-CW Dutch (Curaçao)
* nl-SR Dutch (Suriname)
* nl-SX Dutch (Sint Maarten)
* af (Afrikaans)

==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.''

===Grammer and word order in sentences===
*[https://www.dutchgrammar.com/en/?n=WordOrder.00 https://www.dutchgrammar.com/en/?n=WordOrder.00] About word order in sentences. It's not just one page, keep clicking on next page in the bottom right to see more examples.
*[http://redekundig.nl/ http://redekundig.nl/] a tool to help identify the structure of a Dutch sentence. Very helpful if you're dealing with complex grammatical rules and need to understand the sentence you are reviewing.
* [https://urd2.let.rug.nl/~vannoord/bin/alpino https://urd2.let.rug.nl/~vannoord/bin/alpino] university hosted tool to identify structure of a Dutch sentence. It's the same tool as redekundig.nl but hosted elsewhere, and the interface is harder to comprehend. Would advise trying this in case redekundig.nl isn't giving you the information you need.
* [https://onzetaal.nl/taaladvies/signaalwoorden-lijst/ List of signal words], use these wherever possible, they help clarify your message and prevent ambiguity.

===Style and tone===
* First follow any style guide you find here on this wiki for language and project you are working on
* If you are missing something, contact other translators
* If you search for style advise from other websites, avoid getting it from tech companies who make up their own version of Dutch language based on marketing rather than proper standard Dutch. Also avoid other wiki's which are often written by opinionated people who are not representative for the language. That doesn't mean you can't read them and learn from them, but take it with a grain of salt.

===Spelling===
*[https://taaladvies.net Taaladvies]
*[https://taal.vrt.be Taalnet]
*[https://onzetaal.nl OnzeTaal]

===Technical terminology===
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:
[https://docs.google.com/spreadsheets/d/1OPyeWDq2rtPf9fEpCLRpHl9Hn--OfFbWLbrGtZx3lYI/edit?usp=sharing Dutch Unified Localization Lab Glossary]. The document is maintained by Erin (a localization lab employee). If you wish to add comments, edits or suggest new entries, do so using the "Comment" feature in the spreadsheet.

Dutch

2021-03-23T14:58:45Z

Meteor0id: /* Tips for consistency */

__TOC__

==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 [https://internetfreedomfestival.org/ International Freedom Festival] domain and is subject to their [https://www.internetfreedomfestival.org/wiki/index.php/Code_of_Conduct Code of Conduct]. Be sure to read through the [https://www.internetfreedomfestival.org/wiki/index.php/Code_of_Conduct Code of Conduct] and then [mailto:info@localizationlab.org?subject=Mattermost%20Sign-up&body=Please%20send%20me%20a%20link%20to%20sign%20up%20for%20Mattermost. 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==
===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. We will try to make this styleguide easier to read in the future.''

* 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. 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, meaning different words and/or a different structure of the sentence. An example: "Signal needs location services enabled to discover and connect with your old Android device." is localized as "Om je oude Android apparaat te kunnen detecteren en om er verbinding mee te maken is het nodig dat locatiebepaling op je apparaat is ingeschakeld.". Another example: don't write "Om het in te schakelen, tik op de schuifknop zodat hij blauw wordt." but instead write "Tik op de schuifknop zodat hij blauw wordt om meekijkpreventie in te schakelen."
* 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 punctuation, end the sentence with a period. If the description does not contain any punctuation, 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 Dutch people also get it wrong. [https://www.dutchgrammar.com/en/?n=WordOrder.00] 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. An example: Don't write "Deze personen kunnen door jou niet direct worden toegevoegd aan de groep." instead write "Deze personen kunnen door jou niet direct aan de groep worden toegevoegd.".
* 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 white space: 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 …
* Make sure the subject is repeated in every new sentence, do not refer back to a previous sentence. We do this to keep texts easy to read and understand. An example: do not write "Turing this on allows you to receive emails. They will contain information about your account." instead write "Turning this on allows you to receive emails. The emails you will receive contain information about your account.".
* Avoid anglicisms, our job is to localize the content so it can be understood by as many people as possible, that includes people who don't understand even the most common of English words.
* For units we follow the Si-standards. That means we translate 20MB as 20 MB with a white space. Kilobytes as kB. Note that Signal does not use KiB, MiB etc, because Signal is following the same units as the Android operating system. The same rule applies to other units such as 10s becoming 10 s. Abbreviations for minutes, months and weeks are not si units but we agreed to translate those as "min", "mnd" and "w". Capitalization matters.
* The text strings for the app store sometimes contain wordplay. If a good wordplay in Dutch can't be found, than rather leave the word joke out and just factually describe the change.
* Use pronoun + "wie" instead of "die" wherever possible. Read [https://taaladvies.net/taal/advies/vraag/1564 Taaladvies about wie/die] about where to use "wie" and where to use "die". This is a style choice we made to make complex sentences easier to comprehend.
* Use "van wie", "bij wie", "op wie" and "voor wie" instead of "waarvan", "waarmee", "waarop" and "waarvoor" wherever possible.
* For texts on buttons in Android and Desktop: use "Aan gesprek deelnemen", "Aan Signal doneren" and "Alice toevoegen". Do not use "Voeg Alice toe" or "Deelnemen aan gesprek" or "Doneren aan Signal". reason for this is optial readability. Also capitalize the first letter. on iOS we have not yet decided on the style, because that operating system often uses 'gebiedende wijs' rather than 'infinitief'.
* Try to stick to Dutch words, even if you see English words being used in other apps: "timer" becomes "tijdspanne", "admin" "beheerder", "checkbox" "selectievakje of aankruisvakje", "updaten" "bijwerken", "icon" "pictogram", "non-profit" "organisatie zonder winstoogmerk", "error" "fout", "database""databank" etc. You can find words like these listed in the Transifex Glossary for the Dutch Signal project.
* Beware of capitalization: use "QR-code" do not use "QR-Code" or "qr-code". "WiFi" is spelled different in Dutch: "wifi" all lowercase and without a dash. You can find words like these listed in the Transifex Glossary for the Dutch Signal project.
* Use [https://onzetaal.nl/taaladvies/signaalwoorden-lijst/ signal words] (words that indicate summation, contradiction etc.) wherever possible.
* Use formal verbs where their is no difference in meaning: use "je kunt" not "je kan". Howerver for "kun je" versus "kan je" there is a minor difference: "kan je" is more proposing while "kun je" is more forcefully suggestive. Therefore we use "kan je" instead of "kun je", and "zal je" instead of "zul je". [https://taalhelden.org/bericht/het-kan-je-kun-je https://taalhelden.org/bericht/het-kan-je-kun-je]
* Don't forget that although in English articles can be omitted, in Dutch it's not an accepted practice to omit the article. For example: "Playback time of audio attachment" should be localized as "Afspeellengte van HET audiobericht".

Extra example:
* Don't localize "Other Signal users who are saved to your phone's contact list." as "Andere Signal-gebruikers die zijn opgeslagen in jouw telefoons contactenlijst." but instead localize it as "Andere Signal-gebruikers van wie het telefoonnummer voor komt in de systeemcontactenlijst van jouw telefoon."

===Other projects===
For other projects the style has not yet been written down, however some translators seem to hold on to [http://download.microsoft.com/download/4/7/e/47e135ad-15d7-4491-be78-369804f0d333/nld-nld-StyleGuide.pdf a style guide from Microsoft].

==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.
* ANY time you edit a translation on a project with multiple separate resources, make sure to open all the resources and check if the same string exists elsewhere to apply the exact same edit there. An example would be when you edit a string in the Android Signal messenger app, make sure to also check if the same string exists in the Desktop app, the iOS app, the website or the support center. It's not easy for other reviewers to spot the inconsistency later, so do this right away at the very moment you make an edit.
* Be extra careful with plurals in Transifex, it's easy to miss one of the plural forms when reviewing. You can check all plurals again by searching for pluralized:yes
* Found a spelling mistake, grammar mistake, word order mistake or some word which is better substituted with another word? Don't just correct it when you see it and move on, check all the strings on all the resources for the same mistake or imperfection and correct that mistake on all the strings where it occurs. the moment you noticed something is the only opportunity to come up with a consistent solution across all the strings.

==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 punctuation is accurate, the capitalization is accurate, there are no double white spaces, and no missing white spaces
* 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.
* Don't just look at untranslated string, some strings are automatically translated by Transifex but might still be wrong because the context requires a different translation. use source_updated_after:dd-mm-yyyy to find all the new strings. Also check for edits made by others, using translation_updated_after:dd-mm-yyyy .

==Language varieties==
If you want to localize a project to a language variety which has strong similarities to Dutch and if there already exist good quality translations to Dutch, than it is recommended to base your translations of Dutch rather than English or an other source language. This may make translations faster, but more importantly it also keeps the texts consistent, so that someone who lives just across the border doesn't see completely different texts for the same project. In Transifex there is an option to swap which language you are using as the source language for your translations; you will find it by clicking the setting icon in the top right of the translation interface. Any string that have not yet been translated to Dutch will automatically still be shown as the original source language for the project (usually English).

===(Flemish nl_BE) and Frisian (fy_NL)===
* About compromising between Flemish and Dutch: If a project does not accept translations for nl_BE than unfortunately for Flanders, the languages nl and nl_NL will still follow Dutch standard language (Nederlandse standaardtaal). It is not possible to make nl into a mix or compromise between both languages to satisfy both languages. Flemish translators can contact a project maintainer and ask to add a nl_BE project.

===Other varieties===
Other varieties are
* nl-AW Dutch (Aruba)
* nl-BE Dutch (Belgium)
* nl-BQ Dutch (Caribbean Netherlands)
* nl-CW Dutch (Curaçao)
* nl-SR Dutch (Suriname)
* nl-SX Dutch (Sint Maarten)
* af (Afrikaans)

==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.''

===Grammer and word order in sentences===
*[https://www.dutchgrammar.com/en/?n=WordOrder.00 https://www.dutchgrammar.com/en/?n=WordOrder.00] About word order in sentences. It's not just one page, keep clicking on next page in the bottom right to see more examples.
*[http://redekundig.nl/ http://redekundig.nl/] a tool to help identify the structure of a Dutch sentence. Very helpful if you're dealing with complex grammatical rules and need to understand the sentence you are reviewing.
* [https://urd2.let.rug.nl/~vannoord/bin/alpino https://urd2.let.rug.nl/~vannoord/bin/alpino] university hosted tool to identify structure of a Dutch sentence. It's the same tool as redekundig.nl but hosted elsewhere, and the interface is harder to comprehend. Would advise trying this in case redekundig.nl isn't giving you the information you need.
* [https://onzetaal.nl/taaladvies/signaalwoorden-lijst/ List of signal words], use these wherever possible, they help clarify your message and prevent ambiguity.

===Style and tone===
* First follow any style guide you find here on this wiki for language and project you are working on
* If you are missing something, contact other translators
* If you search for style advise from other websites, avoid getting it from tech companies who make up their own version of Dutch language based on marketing rather than proper standard Dutch. Also avoid other wiki's which are often written by opinionated people who are not representative for the language. That doesn't mean you can't read them and learn from them, but take it with a grain of salt.

===Spelling===
*[https://taaladvies.net Taaladvies]
*[https://taal.vrt.be Taalnet]
*[https://onzetaal.nl OnzeTaal]

===Technical terminology===
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:
[https://docs.google.com/spreadsheets/d/1OPyeWDq2rtPf9fEpCLRpHl9Hn--OfFbWLbrGtZx3lYI/edit?usp=sharing Dutch Unified Localization Lab Glossary]. The document is maintained by Erin (a localization lab employee). If you wish to add comments, edits or suggest new entries, do so using the "Comment" feature in the spreadsheet.

Dutch

2021-03-22T18:13:10Z

Meteor0id: add classic example of think before you localize, don't just translate.

__TOC__

==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 [https://internetfreedomfestival.org/ International Freedom Festival] domain and is subject to their [https://www.internetfreedomfestival.org/wiki/index.php/Code_of_Conduct Code of Conduct]. Be sure to read through the [https://www.internetfreedomfestival.org/wiki/index.php/Code_of_Conduct Code of Conduct] and then [mailto:info@localizationlab.org?subject=Mattermost%20Sign-up&body=Please%20send%20me%20a%20link%20to%20sign%20up%20for%20Mattermost. 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==
===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. We will try to make this styleguide easier to read in the future.''

* 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. 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, meaning different words and/or a different structure of the sentence. An example: "Signal needs location services enabled to discover and connect with your old Android device." is localized as "Om je oude Android apparaat te kunnen detecteren en om er verbinding mee te maken is het nodig dat locatiebepaling op je apparaat is ingeschakeld.". Another example: don't write "Om het in te schakelen, tik op de schuifknop zodat hij blauw wordt." but instead write "Tik op de schuifknop zodat hij blauw wordt om meekijkpreventie in te schakelen."
* 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 punctuation, end the sentence with a period. If the description does not contain any punctuation, 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 Dutch people also get it wrong. [https://www.dutchgrammar.com/en/?n=WordOrder.00] 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. An example: Don't write "Deze personen kunnen door jou niet direct worden toegevoegd aan de groep." instead write "Deze personen kunnen door jou niet direct aan de groep worden toegevoegd.".
* 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 white space: 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 …
* Make sure the subject is repeated in every new sentence, do not refer back to a previous sentence. We do this to keep texts easy to read and understand. An example: do not write "Turing this on allows you to receive emails. They will contain information about your account." instead write "Turning this on allows you to receive emails. The emails you will receive contain information about your account.".
* Avoid anglicisms, our job is to localize the content so it can be understood by as many people as possible, that includes people who don't understand even the most common of English words.
* For units we follow the Si-standards. That means we translate 20MB as 20 MB with a white space. Kilobytes as kB. Note that Signal does not use KiB, MiB etc, because Signal is following the same units as the Android operating system. The same rule applies to other units such as 10s becoming 10 s. Abbreviations for minutes, months and weeks are not si units but we agreed to translate those as "min", "mnd" and "w". Capitalization matters.
* The text strings for the app store sometimes contain wordplay. If a good wordplay in Dutch can't be found, than rather leave the word joke out and just factually describe the change.
* Use pronoun + "wie" instead of "die" wherever possible. Read [https://taaladvies.net/taal/advies/vraag/1564 Taaladvies about wie/die] about where to use "wie" and where to use "die". This is a style choice we made to make complex sentences easier to comprehend.
* Use "van wie", "bij wie", "op wie" and "voor wie" instead of "waarvan", "waarmee", "waarop" and "waarvoor" wherever possible.
* For texts on buttons in Android and Desktop: use "Aan gesprek deelnemen", "Aan Signal doneren" and "Alice toevoegen". Do not use "Voeg Alice toe" or "Deelnemen aan gesprek" or "Doneren aan Signal". reason for this is optial readability. Also capitalize the first letter. on iOS we have not yet decided on the style, because that operating system often uses 'gebiedende wijs' rather than 'infinitief'.
* Try to stick to Dutch words, even if you see English words being used in other apps: "timer" becomes "tijdspanne", "admin" "beheerder", "checkbox" "selectievakje of aankruisvakje", "updaten" "bijwerken", "icon" "pictogram", "non-profit" "organisatie zonder winstoogmerk", "error" "fout", "database""databank" etc. You can find words like these listed in the Transifex Glossary for the Dutch Signal project.
* Beware of capitalization: use "QR-code" do not use "QR-Code" or "qr-code". "WiFi" is spelled different in Dutch: "wifi" all lowercase and without a dash. You can find words like these listed in the Transifex Glossary for the Dutch Signal project.
* Use [https://onzetaal.nl/taaladvies/signaalwoorden-lijst/ signal words] (words that indicate summation, contradiction etc.) wherever possible.
* Use formal verbs where their is no difference in meaning: use "je kunt" not "je kan". Howerver for "kun je" versus "kan je" there is a minor difference: "kan je" is more proposing while "kun je" is more forcefully suggestive. Therefore we use "kan je" instead of "kun je", and "zal je" instead of "zul je". [https://taalhelden.org/bericht/het-kan-je-kun-je https://taalhelden.org/bericht/het-kan-je-kun-je]
* Don't forget that although in English articles can be omitted, in Dutch it's not an accepted practice to omit the article. For example: "Playback time of audio attachment" should be localized as "Afspeellengte van HET audiobericht".

Extra example:
* Don't localize "Other Signal users who are saved to your phone's contact list." as "Andere Signal-gebruikers die zijn opgeslagen in jouw telefoons contactenlijst." but instead localize it as "Andere Signal-gebruikers van wie het telefoonnummer voor komt in de systeemcontactenlijst van jouw telefoon."

===Other projects===
For other projects the style has not yet been written down, however some translators seem to hold on to [http://download.microsoft.com/download/4/7/e/47e135ad-15d7-4491-be78-369804f0d333/nld-nld-StyleGuide.pdf a style guide from Microsoft].

==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.
* ANY time you edit a translation on a project with multiple separate resources, make sure to open all the resources and check if the same string exists elsewhere to apply the exact same edit there. An example would be when you edit a string in the Android Signal messenger app, make sure to also check if the same string exists in the Desktop app, the iOS app, the website or the support center. It's not easy for other reviewers to spot the inconsistency later, so do this right away at the very moment you make an edit.
* Be extra careful with plurals in Transifex, it's easy to miss one of the plural forms when reviewing. You can check all plurals again by searching for pluralized:yes

==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 punctuation is accurate, the capitalization is accurate, there are no double white spaces, and no missing white spaces
* 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.
* Don't just look at untranslated string, some strings are automatically translated by Transifex but might still be wrong because the context requires a different translation. use source_updated_after:dd-mm-yyyy to find all the new strings. Also check for edits made by others, using translation_updated_after:dd-mm-yyyy .

==Language varieties==
If you want to localize a project to a language variety which has strong similarities to Dutch and if there already exist good quality translations to Dutch, than it is recommended to base your translations of Dutch rather than English or an other source language. This may make translations faster, but more importantly it also keeps the texts consistent, so that someone who lives just across the border doesn't see completely different texts for the same project. In Transifex there is an option to swap which language you are using as the source language for your translations; you will find it by clicking the setting icon in the top right of the translation interface. Any string that have not yet been translated to Dutch will automatically still be shown as the original source language for the project (usually English).

===(Flemish nl_BE) and Frisian (fy_NL)===
* About compromising between Flemish and Dutch: If a project does not accept translations for nl_BE than unfortunately for Flanders, the languages nl and nl_NL will still follow Dutch standard language (Nederlandse standaardtaal). It is not possible to make nl into a mix or compromise between both languages to satisfy both languages. Flemish translators can contact a project maintainer and ask to add a nl_BE project.

===Other varieties===
Other varieties are
* nl-AW Dutch (Aruba)
* nl-BE Dutch (Belgium)
* nl-BQ Dutch (Caribbean Netherlands)
* nl-CW Dutch (Curaçao)
* nl-SR Dutch (Suriname)
* nl-SX Dutch (Sint Maarten)
* af (Afrikaans)

==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.''

===Grammer and word order in sentences===
*[https://www.dutchgrammar.com/en/?n=WordOrder.00 https://www.dutchgrammar.com/en/?n=WordOrder.00] About word order in sentences. It's not just one page, keep clicking on next page in the bottom right to see more examples.
*[http://redekundig.nl/ http://redekundig.nl/] a tool to help identify the structure of a Dutch sentence. Very helpful if you're dealing with complex grammatical rules and need to understand the sentence you are reviewing.
* [https://urd2.let.rug.nl/~vannoord/bin/alpino https://urd2.let.rug.nl/~vannoord/bin/alpino] university hosted tool to identify structure of a Dutch sentence. It's the same tool as redekundig.nl but hosted elsewhere, and the interface is harder to comprehend. Would advise trying this in case redekundig.nl isn't giving you the information you need.
* [https://onzetaal.nl/taaladvies/signaalwoorden-lijst/ List of signal words], use these wherever possible, they help clarify your message and prevent ambiguity.

===Style and tone===
* First follow any style guide you find here on this wiki for language and project you are working on
* If you are missing something, contact other translators
* If you search for style advise from other websites, avoid getting it from tech companies who make up their own version of Dutch language based on marketing rather than proper standard Dutch. Also avoid other wiki's which are often written by opinionated people who are not representative for the language. That doesn't mean you can't read them and learn from them, but take it with a grain of salt.

===Spelling===
*[https://taaladvies.net Taaladvies]
*[https://taal.vrt.be Taalnet]
*[https://onzetaal.nl OnzeTaal]

===Technical terminology===
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:
[https://docs.google.com/spreadsheets/d/1OPyeWDq2rtPf9fEpCLRpHl9Hn--OfFbWLbrGtZx3lYI/edit?usp=sharing Dutch Unified Localization Lab Glossary]. The document is maintained by Erin (a localization lab employee). If you wish to add comments, edits or suggest new entries, do so using the "Comment" feature in the spreadsheet.