co-maps/docs/TRANSLATIONS.md

Translations

Translations are managed through Codeberg Translate, which is based on Weblate. Please contribute translations via the Codeberg Translate, and the system and maintainers will handle the rest.

Components

The project consists of multiple components, each with its own translation files.

Weblate Component	Description	Translation Files
Android	UI strings	android/app/src/main/res/values*/strings.xml (en)
Android feature types	Map feature types	android/sdk/src/main/res/values*/type_strings.xml (en)
Android SDK	UI strings (system-level)	android/sdk/src/main/res/values*/strings.xml (en)
iOS	UI strings	iphone/Maps/LocalizedStrings/*.lproj/Localizable.strings (en)
iOS Type Strings	OpenStreetMap Types	iphone/Maps/LocalizedStrings/*.lproj/LocalizableTypes.strings (en)
iOS Plurals	UI strings (plurals)	iphone/Maps/LocalizedStrings/*.lproj/Localizable.stringsdict (en)
iOS Plist	UI strings (system-level)	iphone/Maps/LocalizedStrings/*.lproj/InfoPlist.strings (en)
TTS	Voice announcement strings for navigation directions (TTS)	data/sound-strings/*.json (en)
Countries	Country names for downloader	data/countries-strings/*.json (en)
Search keywords	Search keywords/aliases/synonyms	data/categories-strings/
Search keywords (cuisines)	Search keywords for cuisine types	data/categories_cuisines.txt
AppStore Descriptions	AppStore descriptions	iphone/metadata (en)
Android Stores Descriptions	Google, Huawei store descriptions	android/app/src/google/play/listings (en)
F-Droid Descriptions	F-Droid descriptions	android/app/src/fdroid/play/listings (en)
Website	Website content	comaps/website (see details)

Components without links haven't been integrated into Weblate and must be translated directly via Codeberg Pull Requests.

Translating

Workflow

Translations are managed through Codeberg Translate. Direct submissions to this repository are not recommended but possible in specific cases (like batch-changes). Please prefer using the Weblate for translations whenever possible. Weblate periodically creates pull requests, which @comaps/mergers review and merge as usual.

Cross-Component Synchronization

Android and iOS share most of the strings. Codeberg Translate automatically syncs translations between components (e.g., from Android to iOS and vice versa), so updating a string in one place is usually sufficient.

Categories strings

Search categories synonyms/aliases usually shouldn't be just direct translations from English, but rather adaptations - e.g. some specific terms could be used in your language to search for a certain feature and they might not have English equivalents.

Some translations are borrowed from the common category (@ in the key). Please do not duplicate translations if a category in the key already includes it.

Syntax:

• | - used to separate synonyms.
• 1-9 - digits in front of a synonym indicate the number of symbols that need to be typed in a search query to make this synonym appear in the list of suggestions. Located immediately at the start of a synonym. At most one digit per synonym is allowed. It's possible to use emoji codes as search synonyms, e.g. U+1F6B0 for potable water.

For all languages with nominative and gentive cases (e.g. Slavic languagues like Russian, Ukrainian, Belarus, Serbian), state short nouns in nominative and genitive case, e.g. Вино|вина, so that both (e.g. Russian) searches for "вино" and "магазин вина" returns wine shops.

For longer nouns (6 letters or longer) this is not necessary, because error correction can fix 1 or 2 letters, e.g Мебель

Searcing for "магазин мебели" will also match the category name (1 letter difference).

Exact treshold may be different for different languages. For Serbian, error correction kicks in only for 8-letter or longer words.

Machine Translation

Codeberg Translate is configured to generate machine translations using the best available tools. Auto-translated entries are added as suggestions.

Failing checks

Please review any issues flagged by automated checks, such as missing placeholders, inconsistencies, and other potential errors. Use the filter has:check AND state:>=translated language:de, replacing de with your target language.

Developing

Workflow

Translations are handled by the translation team via Codeberg Translate, with no direct developer involvement required. Developers are only responsible for adding English base strings to the source file (see Components). Codeberg Translate manages the rest. If you're confident in a language, feel free to contribute translations, but please avoid adding machine translations or translating languages you are not familiar with.

Tools

Android developers can utilize the built-in features of Android Studio to add and modify strings efficiently. iOS developers are advised to edit Localizable.strings as a text file, as Xcode’s interface only supports "String Catalog," which is not currently in use. JSON files can be modified using any text editor. To ensure consistency, always follow the established structure and include a comment when adding new strings.

Cross-Component Synchronization

When adding new strings, first check the base file of the component for existing ones. If no relevant strings are found, look for them on the corresponding platform (e.g., iOS when adding Android strings or vice versa). To maintain consistency across platforms, always reuse the existing string key from the other platform with the same English base string.

Maintaining

Under the Hood

Codeberg Translate maintains an internal copy of the Git repository. The repository URL can be found under Manage → Repository Maintenance → Weblate Repository. All components, except for the website, share the same internal Weblate repository.

Translations are extracted from the repository and stored in an internal database, which is used by the Weblate UI. Every 24 hours, this internal database is synchronized back to the internal repository. This process can also be triggered manually via Manage → Repository Maintenance → Commit.

Codeberg Translate has its own Git repository fork of both the website and the main Git repository for pushing translation commits and then creating pull requests (PRs) on Codeberg. After committing changes from the internal database to the internal repository, Codeberg Translate pushes all updates to the weblate-comaps-<component> branch (e.g. weblate-comaps-android for Android UI strings) of its forked repository and creates or updates a PR to main branch of the main repository. This operation can be manually triggered via Manage → Repository Maintenance → Push.

Reviewing PRs

Translations are intended to be reviewed by the community on Codeberg Translate. However, if it's a user's first contribution or if there is any doubt, a quick scan and comparison with the English source can be useful.

It is recommended to add comments directly on Codeberg Translate, as translators primarily work within that platform. Since Codeberg Translate requires a Codeberg account, you may tag contributors in the pull request, but there is no guarantee that they will respond.

Resolving Conflicts

The recommended approach for resolving conflicts is as follows:

1. Make sure the translations on Weblate are actually locked, this ensures that no more changes are done on Weblate while the conflict is being fixed. You will need to have the right Weblate permissions to do this.
2. Commit all changes from the Weblate internal database to the Weblate-internal Git repository, the steps in the UI are: Manage → Repository Maintenance → Commit (button). This ensures that all existing translations are in the Weblate-internal Git repo. (this also requires the right Weblate permissions)
3. Now you can add the weblate-internal Git repo as a remote for your local repo: git remote add weblate https://translate.codeberg.org/git/comaps/android/. This step only needs to be done the first time you have to resolve a conflict
4. Make sure that your local main branch is at the latest remote state, e.g. by running git checkout main; git pull
5. Now you can fetch the current state of the Weblate remote: git fetch weblate
6. To be able to rebase the Codeberg main into the Weblate one, you need to have an editable branch. You can create it using git checkout -b resolve_translate weblate/main. This creates a branch called resolve_translate off the Weblate remote, and also switches you to this newly created branch.
7. You can now run git rebase main, to rebase the branch and resolve any conflicts that are between the two. (Note: Make sure to run this command from your resolve_translate branch)
8. Once you have resolved the conflicts, you can push the resolve_translate branch to Codeberg: git push
9. Make a PR for merging your conflict-resolution-branch into main on Codeberg, and get it reviewed as usual
10. Once the PR is merged into main on Codeberg and the merge conflict is gone, you can now unlock the translations on Weblate again.
11. Optionally if necessary: If the conflict hasn't resolved through the steps, you can optionally reset the Weblate from the admin backend for the website component, this forces the current state from the Codeberg git repo into Weblate: Manage → Repository Maintenance → Reset (button).

Using these steps all existing translations can still be kept and rebased into the repo, without losing work. The important bit is that you need to ensure that all translations are in the Weblate-internal git repository before you rebase, so that they get into the actual Codeberg repo.