> For the complete documentation index, see [llms.txt](https://docs.apryse.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.apryse.com/android/viewer/localization.md).

# Localization: updating languages in viewer UI

Discover how to add multiple language translations to your Android app with Apryse. Explore supported languages and learn how to customize string resources effectively. Find all resources in the Aprys

Apryse ships with many languages built-in as listed below.

You can add additional translations by putting them into the `res/values-xx` directory of your app (i.e. `values-fr`) . Android will automatically merge all string resources at build time. You can also override existing string translations by putting them into the respective string folders.

For reference, all string and translation resources can be found in our open-source Apryse Tools and Demo packages.

{% hint style="warning" %}
**Important: Translations in the SDK are provided AS-IS and are not guaranteed to cover 100% of the strings in the user interface. There may be untranslated strings present.**
{% endhint %}

## Supported Languages

* Arabic (ar)
* Catalan (ca)
* Chinese Simplified (zh-rCN)
* Chinese Traditional (zh-rTW)
* Chinese Traditional (zh-rHK)
* Czech (cs)
* Danish (da)
* Dutch (nl)
* French(fr)
* German (de)
* Hindi (hi)
* Hungarian (hu)
* Indonesian (id)
* Irish (ga-rIE)
* Italian (it)
* Japanese (ja)
* Korean (ko)
* Persian (fa)
* Polish (pl)
* Portuguese, Brazilian (pt-rBR)
* Russian (ru)
* Spanish (es-rES)
* Turkish (tr)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.apryse.com/android/viewer/localization.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.