> For the complete documentation index, see [llms.txt](https://help.screena.ai/resources/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.screena.ai/resources/faq/name-matching/how-does-screena-handle-different-scripts-diacritics-and-transliteration.md).

# How does Screena handle different scripts, diacritics, and transliteration?

## **Does Screena support different scripts and diacritics?**

Yes, Screena handles a wide range of scripts and accommodates the specific characteristics of each, including diacritics that are prevalent in some languages but not in others.

For instance, while both English and French are part of the Roman script family, French often uses accents such as é and è, which are less common in English.

Our system is proficient in processing these features to ensure high accuracy in name matching.

## **What about transliteration and original scripts?**

Screena supports transliteration between scripts, allowing for the accurate matching of names across different writing systems.

For instance, our system can transliterate names from Roman to Hebrew and vice versa.

This feature is crucial for global operations where names may be presented in various scripts, including Cyrillic and others.


---

# 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://help.screena.ai/resources/faq/name-matching/how-does-screena-handle-different-scripts-diacritics-and-transliteration.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.