INaturalistWeb
Translations for the website https://www.inaturalist.org. Our code can be found at https://github.com/inaturalist/inaturalist. To help with translations for iNaturalist's mobile apps, check out https://crowdin.com/project/inaturalistios.
To learn how to use Crowdin, see https://support.crowdin.com/crowdin-intro/
Note that English regions only need translations when there is a regional difference with the source text (which is en-US). For example, if the source text uses the word "color" but it should be "colour" in New Zealand, that should be translated, but text that would be identical doesn't need to be.
SCHEDULE
We will update translations on the website on at least a monthly basis, usually around the start of the month. If there's new functionality with a lot of new text to translate, we may update sooner. We usually deploy translations to the live site on the same day we pull them into the code and run our QA process.
APPROVAL / PROOFREADING
Those of us on staff don't speak every language on Earth, so approval is mostly a matter of spot checking a few contributions by a given translator using Google Translate, and if they don't look like spam, just approving the rest of that person's contributions. We do review for code and formatting problems, though.
We will assign proofreaders on request (DM us on crowdin or iNat, or use help@inaturalist.org), but usually only if that person has already added a significant number of contributions in a given language. It also helps if we know that person is an iNat user. So if you want to be a proofreader, a) add a bunch of translations, and b) contact us, and include your iNat username.
For some locales (es-MX and fr-CA) we leave all proofreading to iNaturalist Network partners, who may be operating on a different schedule.
NEW LOCALES
Please contact a manager like @kueda if you want to add a new locale. Crowdin supports a lot of them (even Klingon!), but we need to turn them on before people can add translations.
Note that we will only start showing a locale in the language chooser when we have some translations, so just because a locale is available for translation in Crowdin doesn't mean it will show up on the site.
PLURAL FORMS
Please be sure to translate *all* plural forms of a string that are offered. Crowdin will not export any translations of that string unless all the plural forms of that string are translated. If you're confused by the "OTHER" form, I believe it refers to a plural form for fractions in most languages. Note that some languages, like Russian, use the "one" form for numerous numbers, e.g. 51, 81, etc., so make sure to include the %{count} variable even if the English translation does not.
TRANSLATING BRAND / TRADEMARKED NAMES
Please do not translate the names "California Academy of Sciences" or "National Geographic." In general, it's probably best to assume brand names and trademarked names should not be translated unless a translated form is commonly used alongside the native form, e.g. "Medecins Sans Frontiers / Doctors Without Borders"
GENDER
For languages with genders, we support a @gender inflection so that strings with variables can be translated differently based on the gender of the variable. For example, if the English text is "a %{resource}", you might translate that as "@gender{m:un|f:une|n:un(e) %{resource}" in French to support male, female, and neuter forms of the article. For this to work properly, you will also need to translate all the strings with "gender" in their description (https://crowdin.com/translate/inaturalistweb/38/en-fr#q=gender). Inflections are tricky to do in code and we try to avoid them, so if it's not working, please comment on the translation and let us know something is wrong.
Keep in mind that we do *not* know the gender of our users, so gendered pronouns should always be in a gender-neutral form.
FORMALITY OF TONE
The tone of English text on iNaturalist is generally casual. We hope translators can convey that sensibility in their translations so iNaturalist can remain a friendly and inviting place for speakers of all languages, but we understand that may not always be appropriate. If there's doubt or conflict, please ask, but generally we prefer to err on the side of being casual. This means for languages that support different levels of formality, we prefer casual forms like "tus" instead of "vos" in Spanish.
REPORTING PROBLEMS / CONTACT
The best way to report a problem with a specific translation is to leave a comment on that translation and mark it as an issue. Note that project managers do *not* get notifications about comments unless they are issues or you @ mention a manager by name. You can also message managers directly. If you have a complicated issue and it would help to include screenshots, please post at https://forum.inaturalist.org/
To learn how to use Crowdin, see https://support.crowdin.com/crowdin-intro/
Note that English regions only need translations when there is a regional difference with the source text (which is en-US). For example, if the source text uses the word "color" but it should be "colour" in New Zealand, that should be translated, but text that would be identical doesn't need to be.
SCHEDULE
We will update translations on the website on at least a monthly basis, usually around the start of the month. If there's new functionality with a lot of new text to translate, we may update sooner. We usually deploy translations to the live site on the same day we pull them into the code and run our QA process.
APPROVAL / PROOFREADING
Those of us on staff don't speak every language on Earth, so approval is mostly a matter of spot checking a few contributions by a given translator using Google Translate, and if they don't look like spam, just approving the rest of that person's contributions. We do review for code and formatting problems, though.
We will assign proofreaders on request (DM us on crowdin or iNat, or use help@inaturalist.org), but usually only if that person has already added a significant number of contributions in a given language. It also helps if we know that person is an iNat user. So if you want to be a proofreader, a) add a bunch of translations, and b) contact us, and include your iNat username.
For some locales (es-MX and fr-CA) we leave all proofreading to iNaturalist Network partners, who may be operating on a different schedule.
NEW LOCALES
Please contact a manager like @kueda if you want to add a new locale. Crowdin supports a lot of them (even Klingon!), but we need to turn them on before people can add translations.
Note that we will only start showing a locale in the language chooser when we have some translations, so just because a locale is available for translation in Crowdin doesn't mean it will show up on the site.
PLURAL FORMS
Please be sure to translate *all* plural forms of a string that are offered. Crowdin will not export any translations of that string unless all the plural forms of that string are translated. If you're confused by the "OTHER" form, I believe it refers to a plural form for fractions in most languages. Note that some languages, like Russian, use the "one" form for numerous numbers, e.g. 51, 81, etc., so make sure to include the %{count} variable even if the English translation does not.
TRANSLATING BRAND / TRADEMARKED NAMES
Please do not translate the names "California Academy of Sciences" or "National Geographic." In general, it's probably best to assume brand names and trademarked names should not be translated unless a translated form is commonly used alongside the native form, e.g. "Medecins Sans Frontiers / Doctors Without Borders"
GENDER
For languages with genders, we support a @gender inflection so that strings with variables can be translated differently based on the gender of the variable. For example, if the English text is "a %{resource}", you might translate that as "@gender{m:un|f:une|n:un(e) %{resource}" in French to support male, female, and neuter forms of the article. For this to work properly, you will also need to translate all the strings with "gender" in their description (https://crowdin.com/translate/inaturalistweb/38/en-fr#q=gender). Inflections are tricky to do in code and we try to avoid them, so if it's not working, please comment on the translation and let us know something is wrong.
Keep in mind that we do *not* know the gender of our users, so gendered pronouns should always be in a gender-neutral form.
FORMALITY OF TONE
The tone of English text on iNaturalist is generally casual. We hope translators can convey that sensibility in their translations so iNaturalist can remain a friendly and inviting place for speakers of all languages, but we understand that may not always be appropriate. If there's doubt or conflict, please ask, but generally we prefer to err on the side of being casual. This means for languages that support different levels of formality, we prefer casual forms like "tus" instead of "vos" in Spanish.
REPORTING PROBLEMS / CONTACT
The best way to report a problem with a specific translation is to leave a comment on that translation and mark it as an issue. Note that project managers do *not* get notifications about comments unless they are issues or you @ mention a manager by name. You can also message managers directly. If you have a complicated issue and it would help to include screenshots, please post at https://forum.inaturalist.org/