Text that only looks readable
Some Arabic PDFs carry a text layer that copies out as nonsense because of legacy fonts. Each page's text is checked before it is trusted, and read again from the page image when it fails.
Document Intelligence reads Arabic and English documents, separates combined files, classifies each document and prepares both the document and its data for your archive and the workflows that use it.
Arabic and English. Built in Kuwait.
Scanned file
scan_0412.pdf · 12 pages, Arabic and English
Documents found
Ready
Four files, named by type and date, with their key fields indexed for the archive
Printed Arabic and English text is recognised, including pages that mix both.
A combined scan is split into the individual documents inside it.
Each document is labelled by type: a policy, an ID, a report, an invoice.
The document and its data are named, indexed and passed to your archive or the next step in the workflow.
Some Arabic PDFs carry a text layer that copies out as nonsense because of legacy fonts. Each page's text is checked before it is trusted, and read again from the page image when it fails.
Bilingual pages are read block by block, so an Arabic column and its English translation both come out intact.
A misreading that repeats through a document can pass for a real word. Checks look for known error patterns, not only for unusual words.
No. It prepares documents and their data for the archive or document management system you already use.
Arabic and English, including bilingual documents.
Yes. That is what separation is for: one scanned batch is split into the documents inside it, and each is classified on its own.
Into your archive and the workflows that use them, for example a claim case opened by Intimation & Workflow Automation.
What arrives, in which languages, and where it needs to end up. We will show you how Document Intelligence would read, split and file it.