UiPath Studio

Installing OCR Languages

The default language of an OCR engine is English. This can be changed for any of the built-in engines by accessing the Properties panel and adding the name of the language between quotation marks, as seen in the screenshots below:

Note:

For the Google OCR engine, the Language field needs to contain the language file prefix, such as “ron” for Romanian, “ita” for Italian, "jpn" for Japanese, and “fra” for French.

Note:

ABBYY FineReader Engine includes the majority of supported OCR languages by default. They can be used right after a successful installation of the engine.

The language for the Microsoft OCR engine can also be changed in a Screen Scraping activity when selecting “OCR” as the Scraping Method.

This can also be done for the Google OCR engine.

Note:

ABBYY OCR is not available in the default Screen Scraping window. You can change the language of the OCR engine by modifying the Language property.

Installing an OCR Engine and Changing the Language

Microsoft OCR

Windows 10

To add a language to your system and then use it in your workflow:

  1. Go to Start Menu > Settings, the Windows Settings window opens. Make sure to maximize the window.
  2. Access Time & Language, the Date & time window opens.
  3. On the left side menu, select Region & language. Under Languages, click Add a language.
  4. Choose your preferred language and click Next. The Install language features window opens.
  5. Uncheck the Set as my Windows display language check box. Click Install and wait for the installation to finish.
  6. Restart UiPath Studio for new languages to become available. The language can now be used in Studio by adding its name between quotation marks (“Japanese”).

Note:

If a language is simply added and not installed it cannot be used by the Microsoft OCR engine. Not all system languages are supported.

Windows 7 and Windows 8.1

The Microsoft OCR engine needs to be manually installed.

  1. Download and install Microsoft SharePoint Designer 2010 32-bit or 64-bit.
  2. Choose your Office version and language here, and follow the instructions to set up the desired language.

Google OCR

  1. Search for the desired language file on this page.
  2. Save the file in the tessdata folder of the UiPath installation directory (C:\Program Files (x86)\UiPath\Studio\tessdata).
  1. Restart UiPath Studio for the new languages to become available. The language can now be used in Studio by adding its name between quotation marks (“ron”).

ABBYY OCR

Important:

ABBYY FineReader Engine SDK is required. The engine only works with a license distributed by the UiPath sales department.

  1. Contact our sales department to obtain a functional ABBYY FineReader Engine SDK License.
    1.1. Access the Contact us page.
    1.2. Go to Technical Support & Activations.
    1.3. Request a license by filling up the form.
    1.4. Choose “Service Request” after providing a Name and Email.
  2. Press Win + S to open up Search.
  3. Type CMD and then press Ctrl + Shift + Enter. This opens Command Prompt with Administrator Privileges.
  4. Navigate to the download directory.

Note:

Use cd.. to go up one folder and cd folder_name to access a specific folder in Command Prompt.

  1. Type Setup.exe /qb /v INSTALLDIR="C:\Abbyy\FR11" SN=serialkey ARCH=x86 LICENSESRV=Yes.
    • The /qb and /v switches handle the interface and caching options.
    • INSTALLDIR is the installation path.
    • SN is the serial number obtained at step 1.
    • ARCH represents the installation architecture which needs to match that of UiPath Studio.
  2. Navigate to the Bin folder in the installation directory. It should look something like C:\abbyy\fr11\Bin.
  3. Type LicenseManager.exe /SilentActivation /SN:serialkey to activate the license key.
    • The /SilentActivation switch disables user prompts.
    • SN is the serial number obtained at step 1.
  4. Restart UiPath Studio to use ABBYY OCR.

Updated 23 days ago



Installing OCR Languages


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.