Skip to content

Update translations guidelines #1135

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Mar 18, 2021
Merged

Update translations guidelines #1135

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion TRANSLATIONS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,6 +3,8 @@ Thank you for taking the time to contribute to DuckDuckGo! :sparkles:

If you know any of the following languages and would like to help us improve the translations for them, please follow the instructions below.

⚠️ We only accept translations tweaks that fix actual issues (typos, grammatical errors) and won't accept minor changes that are only focused on tweaking the wording.

## List of languages
1. Bulgarian (bg)
1. Croatian (hr)
Expand Down Expand Up @@ -34,7 +36,7 @@ If you know any of the following languages and would like to help us improve the
1. Each language has a [`values`](https://github.com/duckduckgo/Android/tree/develop/app/src/main/res) directory containing the language code, and the `strings.xml` file contains the translations. Examples:
- Italian translation files are located within `app/src/main/res/values-it/strings.xml`
- Spanish translation files are located within `app/src/main/res/values-es/strings.xml`
1. If you notice anything which could be improved, you should create a PR containing the improved language suggestions.
1. If you notice anything which should be fixed, you should create a PR containing the improved language suggestions.
1. Make the changes to the relevant `strings.xml` file
1. Test the app in the language you've improved, and ensure the changed strings look good
1. Create a PR. As well as the changes themselves, explaining _why_ the changes are an improvement helps a lot.
Expand Down