zelo72
/
mastodon-ios
mirror of https://github.com/mastodon/mastodon-ios
2
2
Fork 1
Code Issues 19 Releases Wiki Activity
mastodon-ios/Localization
History
Nathan Mattes 38b4ab062e Add Armenian Localization (#1147) 2023-11-10 11:05:17 +01:00
..
StringsConvertor Add Armenian Localization (#1147) 2023-11-10 11:05:17 +01:00
Intents.stringsdict chore: add intents strings dict to Crowdin configuration. 2021-08-10 16:02:51 +08:00
Localizable.stringsdict IOS-69: Label this “re-blog” otherwise it sounds like “reh-blog” (#975) 2023-03-15 14:58:25 +01:00
README.md Fix typo 2022-12-19 12:06:46 +01:00
app.json Add missing piece of localization (IOS-20) 2023-10-10 14:00:32 +02:00
ios-infoPlist.json feat: add compose and search home screen quick actions 2021-07-26 17:41:00 +08:00

README.md

Localization

Crowdin

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.

  1. Add new strings in Localization/app.json and the Localizable.strings for English.
  2. Run swiftgen to generate the Strings.swift-file or have Xcode build the app (swiftgen is a Build phase, too).
  3. Use import MastodonLocalization and its (new) L10n-enum and its properties where ever you need them in the app.
  4. 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:

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