> 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/uwp/viewer/localization.md).

# Localization: Updating languages in viewer UI

Discover the supported languages in Apryse SDK, including English, French, Portuguese, Chinese, Japanese, Korean, Dutch, Spanish, and Italian. Explore our open-source tools for translations. The Aprys

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

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

* English
* French (Français)
* Portuguese (Português)
* Chinese-Simplified (中文)
* Japanese (日本語)
* Korean (한국어)
* Dutch/German (Deutsch)
* Spanish (Español)
* Italian (Italiano)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

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

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.