PACKAGE SEARCH contribute translations

If you'd like to help make PACKAGE SEARCH available in your language, the language files are publicly available on the PACKAGE SEARCH tracker.

Translations are maintained under the following directory:

• PACKAGE SEARCH Translations

If you’d like to contribute a new language or update an existing translation, please:

1. Fork the repository.
2. Navigate to (or create) the appropriate language folder.
3. Update the XML file (using the template below as a reference).
4. Submit a Pull Request (PR) to the repository for review.

Here’s a template you can follow when contributing. Be mindful of the comments, as there are restrictions on some strings:

Default strings.xml (aligns to en-GB)

Android follows the BCP 47 standard for naming language and region codes when defining different string resources in an app. Each language or locale gets its own folder under the res directory, and the folder name is structured based on the language and sometimes the region or script.

The general format for Android resource folders is:

res/values-<language>-<region>

• English (default): res/values/strings.xml
• French: res/values-fr/strings.xml
• Spanish (Spain): res/values-es/strings.xml
• Spanish (Mexico): res/values-es-rMX/strings.xml
• Chinese (Simplified): res/values-zh/strings.xml
• Chinese (Traditional, Taiwan): res/values-zh-rTW/strings.xml

1. Language code (<language>):

   • Two lowercase letters, e.g., en for English, fr for French.

2. Region code (<region>):

   • Two uppercase letters following r, e.g., rUS for the United States, rGB for Great Britain, rMX for Mexico.

3. Script code (optional):

   • For certain scripts, you may use a script code like Latn (Latin) or Cyrl (Cyrillic), e.g., values-bn-Latn.

The official Android documentation provides a complete guide for localization and the proper naming conventions for these folders. It explains how to structure res/values directories to target specific languages, regions, and even scripts.

Additionally, you can refer to the IANA Language Subtag Registry to explore all the possible language, script, and region subtags available.

When submitting a PR for code changes, ensure you:

• Define the language the translation is for.
• Include clear commit messages.
• Ensure you’ve updated the correct language file.
• Ensure strings remain consistent with other translations (only the text changes, not the structure).

Please include a name you wish to be credited against, as names of contributors are listed in the application.

Translations submitted via PR will be reviewed and merged into the codebase. Once merged, they will appear in the next release of PACKAGE SEARCH, which is updated periodically based on changes, bug fixes, and new features.