> For the complete documentation index, see [llms.txt](https://help.jurisphere.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.jurisphere.ai/translation/overview-of-the-translation-tool.md).

# Overview of the Translation tool

Jurisphere is capable of translating documents into over **200** global languages, including 22 Indian regional languages. The translations from 22 Indian languages to English have been rigorously vetted by professional translators, achieving an accuracy rate of <mark style="color:green;">**93.6%**</mark>.

Documents can also be translated *to* 20 different regional languages.

<details>

<summary>Input languages</summary>

<table><thead><tr><th>Language</th><th>Accuracy</th><th data-type="checkbox">Handwritten content</th></tr></thead><tbody><tr><td>Hindi</td><td>98.4%</td><td>true</td></tr><tr><td>Marathi</td><td>94.3%</td><td>true</td></tr><tr><td>Punjabi</td><td>92.6%</td><td>false</td></tr><tr><td>Kannada</td><td>91.6%</td><td>true</td></tr><tr><td>Gujarati</td><td>84.2%</td><td>false</td></tr><tr><td>Tamil</td><td>86.3%</td><td>false</td></tr><tr><td>Telugu</td><td>85.2%</td><td>false</td></tr><tr><td>Bengali</td><td>93.2%</td><td>false</td></tr><tr><td>Malayalam</td><td>91.2%</td><td>false</td></tr><tr><td>Urdu</td><td>90.8%</td><td>false</td></tr><tr><td>English </td><td></td><td>true</td></tr></tbody></table>

</details>

<details>

<summary>Output languages</summary>

English, Hindi, Assamese, Bengali, Kannada, Malayalam, Marathi, Odia, Punjabi, Telugu, Tamil, Gujarati, Chinese, Japanese, Thai, Arabic, French, German, Spanish, Italian.&#x20;

</details>

Some key features of our Translation tool are:

## Format and Document Integrity

1. **Formatting Preservation**: Jurisphere prioritizes retention of:

a. Original formatting - headings, paragraphs, indentation, simple tables, etc.

b. Pagination - contents flowing over to another page are demarcated as per original.

2. **Benefits for Legal Workflows**:

a. Enables side-by-side comparison for legal analysis.

b. Maintains document integrity for accurate interpretation.

## Limitations and Considerations

1. **Handwriting Variability**: Handwritten notes and numerals are supported, but:

a. Individual handwriting styles may impact recognition accuracy.

b. Proper nouns may occasionally be misinterpreted.

{% hint style="warning" %}
**High Quality OCR = Accurate Translation!**

Jurisphere uses an in-house [OCR](/file-upload-and-management/your-files-and-documents/ocr.md) (Optical Character Recognition) system. If the document has been OCRed properly, the translated output maintains high fidelity to the original content.
{% endhint %}

## Use Cases

1. **Non-Admissible Legal Copy**: Translations and transcriptions are **not court-admissible**.

a. Ideal for internal analysis and quick comprehension of large document batches.

b. Useful when immediate translation is needed and official translators are unavailable.

2. **Large Data Dumps**: Quickly convert and make sense of scanned or handwritten documents without waiting for manual translation workflows.
3. **Typed copies**: For poorly legible or handwritten English / Hindi documents, [choose the appropriate target](/translation/translating-a-document-on-jurisphere.md) language to obtain clear typed copies.


---

# 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://help.jurisphere.ai/translation/overview-of-the-translation-tool.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.