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

# Localization for Xamarin viewer tools

Learn how to localize Xamarin.Android and Xamarin.iOS Tools for different languages. Follow step-by-step instructions to add translations and create C# NuGet packages for your applications. The Apryse

Localization for Tools library follows each platform's convention.

## Xamarin.Android Tools localization

You can put your translation `strings.xml` into `Resources/values-xx` directory of your application, i.e. `values-fr` for French.

See available languages here: [Localization on Android](/android/viewer/localization.md).

## Xamarin.iOS Tools localization

1. [Download the the native SDK](/ios/get-started/download.md).
2. Navigate into `./Lib/Tools/src/PDFViewCtrlTools/Tools/en.lproj` to find the example `Localizable.strings` file that contains translation information for the Tools source code. Rename this file to `PTLocalizable.strings`
3. Create a directory called `<language code>.lproj` within your project resources directory and place the `PTLocalizable.strings` file from Step 2 in the directory. For a list of language codes supported by Apple, please refer to the [Apple documentation](https://developer.apple.com/library/archive/MacOSX/Conceptual/BPInternational/LanguageandLocaleIDs/LanguageandLocaleIDs.html).
4. Add the translations into the `PTLocalizable.strings` file.

### Localization when compiling Tools from source (deprecated)

{% hint style="warning" %}
**Warning**

This method only applies to versions of the SDK prior to v6.10.2.

This method is not recommended as it involves editing the `Tools.framework` strings file directly which will create a requirement to manually merge strings files when updating to new versions of `Tools.framework`.
{% endhint %}

1. Follow the [native localization guide](/ios/viewer/localization.md#localization-when-compiling-tools-from-source).
2. Follow the [Tools binding guide](/xamarin/learn-more/objc-ios.md) to create the C# NuGet packages.


---

# 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/xamarin/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.