History

Nathan Mattes 9e912be7c4 Fix build Happened due to localization, we changed the workflow, but didn't consider another pr. so boom.		2022-11-14 23:19:53 +01:00
..
StringsConvertor	Fix build	2022-11-14 23:19:53 +01:00
Intents.stringsdict	…
Localizable.stringsdict	Add real localization keys	2022-11-08 13:50:23 -05:00
README.md	Fix typo (#539 )	2022-11-09 12:25:17 +01:00
app.json	Merge pull request #564 from ReactiveRaven/feature/validated-fields	2022-11-14 19:39:17 +01:00
ios-infoPlist.json	…

README.md

Localization

We use Crowdin for translations and some automation.

How to contribute

Help with translations

Head over Crowdin for that. To help with translations, select your language and translate :-) If your language is not in the list, please feel free to open a topic on Crowdin.

Please note: You need to have an account on Crowdin to help with translations.

Add new strings

This is mainly for developers.

Add new strings in Localization/app.json and the Localizable.strings for English.
Run swiftgen to generate the Strings.swift-file or have Xcode build the app (swiftgen is a Build phase, too).
Use import MastodonLocalization and its (new) L10n-enum and its properties where ever you need them in the app.
Once the updated Localization/app.json hits develop, it gets synced to Crowdin, where people can help with translations. Localization/app.json must be a valid json.

How to update translations

If there are new translations, Crowdin pushes new commits to a branch called l10n_develop and creates a new Pull Request. Both, the branch and the PR might be updated once an hour. The project itself uses a script to generate the various Localizable.strings-files etc. for Xcode.

To update or add new translations, the workflow is as follows:

Merge the PR with l10n_develop into develop. It's usually called New Crowdin Updates
Run update.localization.sh on your computer.
Commit the changes and push develop.