studio
2023.4
false
- Release Notes
- Getting Started
- Setup and Configuration
- Automation Projects
- Dependencies
- Types of Workflows
- File Comparison
- Automation Best Practices
- Source Control Integration
- Debugging
- Workflow Analyzer
- About Workflow Analyzer
- ST-NMG-001 - Variables Naming Convention
- ST-NMG-002 - Arguments Naming Convention
- ST-NMG-004 - Display Name Duplication
- ST-NMG-005 - Variable Overrides Variable
- ST-NMG-006 - Variable Overrides Argument
- ST-NMG-008 - Variable Length Exceeded
- ST-NMG-009 - Prefix Datatable Variables
- ST-NMG-011 - Prefix Datatable Arguments
- ST-NMG-012 - Argument Default Values
- ST-NMG-016 - Argument Length Exceeded
- ST-DBP-002 - High Arguments Count
- ST-DBP-003 - Empty Catch Block
- ST-DBP-007 - Multiple Flowchart Layers
- ST-DBP-020 - Undefined Output Properties
- ST-DBP-023 - Empty Workflow
- ST-DBP-024 - Persistence Activity Check
- ST-DBP-025 - Variables Serialization Prerequisite
- ST-DBP-026 - Delay Activity Usage
- ST-DBP-027 - Persistence Best Practice
- ST-DBP-028 - Arguments Serialization Prerequisite
- ST-USG-005 - Hardcoded Activity Arguments
- ST-USG-009 - Unused Variables
- ST-USG-010 - Unused Dependencies
- ST-USG-014 - Package Restrictions
- ST-USG-020 - Minimum Log Messages
- ST-USG-024 - Unused Saved for Later
- ST-USG-025 - Saved Value Misuse
- ST-USG-026 - Activity Restrictions
- ST-USG-027 - Required Packages
- ST-USG-028 - Restrict Invoke File Templates
- ST-USG-032 - Required Tags
- ST-USG-034 - Automation Hub URL
- Variables
- Arguments
- Imported Namespaces
- Trigger-based Attended Automation
- Recording
- UI Elements
- Control Flow
- Selectors
- Object Repository
- Data Scraping
- Image and Text Automation
- Citrix Technologies Automation
- RDP Automation
- Salesforce Automation
- SAP Automation
- VMware Horizon Automation
- Logging
- The ScreenScrapeJavaSupport Tool
- The WebDriver Protocol
- Test Suite - Studio
- Extensions
- Troubleshooting
- About troubleshooting
- Microsoft App-V support and limitations
- Internet Explorer X64 troubleshooting
- Microsoft Office issues
- Identifying UI elements in PDF with Accessibility options
- Repairing Active Accessibility support
- Automating Applications Running Under a Different Windows User
- Validation of large Windows-legacy projects takes longer than expected
Installing an OCR Engine and Changing the Language
Studio User Guide
Last updated Dec 4, 2024
Installing an OCR Engine and Changing the Language
To add a language to your system and then use it in your workflow:
- Go to Start Menu > Settings, the Windows Settings window opens. Make sure to maximize the window.
- Access Time & Language, the Date & time window opens.
- On the left side menu, select Region & language. Under Languages, click Add a language.
- Choose your preferred language and click Next. The Install language features window opens.
- Uncheck the Set as my Windows display language check box. Click Install and wait for the installation to finish.
-
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.
- Search for the desired language file on this page.
-
Save the file in the tessdata folder of the UiPath installation directory (
C:\Program Files\UiPath\Studio\tessdata
). -
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”).
Important: ABBYY FineReader Engine SDK is required. The engine only works with a license distributed by the UiPath sales department.
-
Contact our sales department to obtain a functional ABBYY FineReader Engine SDK License.
- Access the Contact us page.
- Go to Technical Support & Activations.
- Request a license by filling up the form.
- Choose “Service Request” after providing a Name and Email.
- Press Win + S to open up Search.
- Type CMD and then press Ctrl + Shift + Enter. This opens Command Prompt with Administrator Privileges.
-
Navigate to the download directory.
Note: Usecd..
to go up one folder andcd folder_name
to access a specific folder in Command Prompt. -
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.
- The
- Navigate to the Bin folder in the installation directory. It should look something like
C:\abbyy\fr11\Bin
. -
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.
- The
- Restart UiPath Studio to use ABBYY OCR.