# 5.2.6. Languages and character encoding

In addition to the possibility for GeoPrism Registry user’s interface to be localized (see [section 3.4](https://github.com/terraframe/geoprism-registry-documentation/blob/main/versions/current/3-deployment-and-setup/3.4-localisation)) users have the possibility to import, store and share the information associated with each data element in the local language.

Thanks to the libraries it integrates, GeoPrism Registry is able to cover any language as long as it is based on the [Unicode](https://home.unicode.org/) character encoding system.


---

# Agent Instructions: 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:

```
GET https://docs.geoprismregistry.com/readme/current/geoprism-registry-key-components/5.2-content-related-capacities-of-geoprism-registry/5.2-content-related-capacities-of-geoprism-registry-5.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.