iNaturalistMobile
Translations for iNaturalist apps for Android and iOS
See https://github.com/inaturalist/INaturalistIOS/ and https://github.com/inaturalist/iNaturalistAndroid for our code.
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
For Android (strings.xml), we try to upload new strings twice a month, and integrate translations into our code at the beginning of the month. The app is not on a regular release schedule, so we can't guarantee translations will be released by a given date. App release is driven by the current overall stability of the build, so we might have multiple releases in a month, or we might not release at all in a given month.
For iPhone (the rest of the files), we try to follow a similar schedule, but app releases are less frequent due to the fact that our iPhone developer divides his time between the app and computer vision work, and due to the more onerous review process of the App Store.
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.
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/
See https://github.com/inaturalist/INaturalistIOS/ and https://github.com/inaturalist/iNaturalistAndroid for our code.
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
For Android (strings.xml), we try to upload new strings twice a month, and integrate translations into our code at the beginning of the month. The app is not on a regular release schedule, so we can't guarantee translations will be released by a given date. App release is driven by the current overall stability of the build, so we might have multiple releases in a month, or we might not release at all in a given month.
For iPhone (the rest of the files), we try to follow a similar schedule, but app releases are less frequent due to the fact that our iPhone developer divides his time between the app and computer vision work, and due to the more onerous review process of the App Store.
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.
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/