{"id":30147,"date":"2019-01-30T11:54:57","date_gmt":"2019-01-30T19:54:57","guid":{"rendered":"https:\/\/ephesoft.com\/docs\/?page_id=30147"},"modified":"2020-05-19T12:24:18","modified_gmt":"2020-05-19T19:24:18","slug":"etext-support-in-pdf","status":"publish","type":"docs","link":"https:\/\/ephesoft.com\/docs\/products\/transact\/release-notes\/release-notes-2019-1\/etext-support-in-pdf\/","title":{"rendered":"EText Support &#8211; Leveraging Existing Text Layer in PDF Documents"},"content":{"rendered":"<p><a href=\"#post-30147-_Toc534204320\">Introduction<\/a><\/p>\n<p><a href=\"#post-30147-_Toc534204321\">EText Functionality<\/a><\/p>\n<p style=\"padding-left: 30px\"><a href=\"#post-30147-_Toc534204322\">Page Process Module<\/a><\/p>\n<p style=\"padding-left: 30px\"><a href=\"#post-30147-_Toc534204323\">Learn File(s) \/ Test Classification \/ Test Extraction<\/a><\/p>\n<p style=\"padding-left: 30px\"><a href=\"#post-30147-_Toc534204324\">Extraction Configuration Screens<\/a><\/p>\n<p style=\"padding-left: 30px\"><a href=\"#post-30147-_Toc534204325\">Batch.xml File<\/a><\/p>\n<p style=\"padding-left: 30px\"><a href=\"#post-30147-_Toc534204326\">Export Module<\/a><\/p>\n<p style=\"padding-left: 30px\"><a href=\"#post-30147-_Toc534204327\">Web Services<\/a><\/p>\n<p><a href=\"#post-30147-_Toc534204328\">Use Cases<\/a><\/p>\n<p style=\"padding-left: 30px\"><a href=\"#post-30147-_Toc534204329\">EText Mode \u2013 Automatically<\/a><\/p>\n<p style=\"padding-left: 30px\"><a href=\"#post-30147-_Toc534204330\">EText Mode \u2013 Always<\/a><\/p>\n<p style=\"padding-left: 30px\"><a href=\"#post-30147-_Toc534204331\">EText Mode \u2013 Never<\/a><\/p>\n<h2><a id=\"post-30147-_Toc534204320\"><\/a><strong>Introduction<\/strong><\/h2>\n<p>Ephesoft Transact fully leverages the text embedded in computer generated PDFs (also referred to by RecoStar as EText). This helps to boost the accuracy of extracted text and greatly reduce the effort required for extraction on all projects that include processing of electronically generated documents.<\/p>\n<p>Rather than being OCRed as images, the documents with EText layer are processed using a special mechanism, which helps to extract data directly. As per provided configuration, the EText support feature can be used:<\/p>\n<ul>\n<li>AUTOMATICALLY<\/li>\n<li>ALWAYS<\/li>\n<li>NEVER<\/li>\n<\/ul>\n<p>This feature also allows to create the exported PDF artefact(s) from the original file rather than use an image with a text layer attached.<\/p>\n<p>The following languages are supported with EText feature:<\/p>\n<div>1. English<br \/>\n2. French<\/div>\n<div>3. German<\/div>\n<div>4. Italian<\/div>\n<div>5. Spanish<\/div>\n<div>6. Dutch<\/div>\n<h2><a id=\"post-30147-_Toc534204321\"><\/a><strong>EText Functionality <\/strong><\/h2>\n<p>The feature is implemented on the following levels:<\/p>\n<p><a href=\"#post-30147-_Page_Process_Module\"><strong>Page Process Module<\/strong><\/a><\/p>\n<ul>\n<li>RECOSTAR_HOCR plugin (Windows)<\/li>\n<li>NUANCE_HOCR plugin (Linux)<\/li>\n<\/ul>\n<p><a href=\"#post-30147-_Learn_File(s)_\/_1\"><strong>Learn File(s) \/ Test Classification \/ Test Extraction<\/strong><\/a><\/p>\n<p><a href=\"#post-30147-_Extraction_Configuration_Screens_1\"><strong>Extraction Configuration Screens<\/strong><\/a><\/p>\n<ul>\n<li>KV Extraction Rule<\/li>\n<li>Paragraph Extraction Rule<\/li>\n<li>Cross Section Extraction<\/li>\n<li>Table Extraction Rule<\/li>\n<li>KV Page Process Extraction Rule<\/li>\n<\/ul>\n<p><a href=\"#post-30147-_Batch.xml_File_1\"><strong>Batch.xml File<\/strong><\/a><\/p>\n<ul>\n<li>At root level (&lt;ETextMode&gt;)<\/li>\n<li>At page level (&lt;TreatAsEText&gt;)<\/li>\n<\/ul>\n<p><a href=\"#post-30147-_Export_Module\"><strong>Export Module<\/strong><\/a><\/p>\n<ul>\n<li>CREATEMULTIPAGE_FILES<\/li>\n<\/ul>\n<p><a href=\"#post-30147-_Web_Services\"><strong>Web Services<\/strong><\/a><\/p>\n<p>Three new web services have been added and 11 existing web services have been updated to support the new functionality.<\/p>\n<p>Feature implementation on various levels is described in detail below.<\/p>\n<p>&nbsp;<\/p>\n<h3><a id=\"post-30147-_Page_Process_Module\"><\/a><a id=\"post-30147-_Toc534204322\"><\/a><strong>Page Process Module<\/strong><\/h3>\n<h4><strong>RECOSTAR_HOCR plugin (Windows)<\/strong><\/h4>\n<p>Two fields \u201cUse EText Recostar Project File\u201d and \u201cPDF EText Recostar Project File Name\u201d have been added to the plugin. Both new fields are mandatory.<\/p>\n<p><img decoding=\"async\" width=\"1445\" height=\"579\" class=\"wp-image-30556\" src=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-56.png\" srcset=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-56.png 1445w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-56-300x120.png 300w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-56-768x308.png 768w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-56-1024x410.png 1024w\" sizes=\"(max-width: 1445px) 100vw, 1445px\" \/><\/p>\n<table>\n<tbody>\n<tr>\n<td width=\"300\">Use EText Recostar Project File<\/td>\n<td>Allows the user to select one of three available options provided for EText support:<\/p>\n<p>&#8211; Automatically<\/p>\n<p>&#8211; Always<\/p>\n<p>&#8211; Never<\/p>\n<p>The default value is Never.<\/td>\n<\/tr>\n<tr>\n<td>PDF EText Recostar Project File Name<\/td>\n<td>Is used to select the Recostar project file which will be used for EText OCRing if the option selected in the first field is either Always or Automatically.<\/p>\n<p>If needed, this rsp file can be manipulated by users for more granular control or customization.<\/p>\n<p>There are four .rsp files available in the drop-down: FPR_EText.rsp, FPR.rsp, FPR_MultiLanguage.rsp and FPR_Barcode.rsp. The FPR_EText.rsp is selected by default. In rare cases, when the user is selecting any other file, they need to make sure to change the ProcessingMode parameter in them from OcrFromImage to ExtractFromEtext for the functionality to work. This approach helps to avoid duplication of .rsp files in the fixed-form-extraction folder, yet gives the user the required flexibility.<\/p>\n<p><img decoding=\"async\" width=\"767\" height=\"439\" class=\"wp-image-30557\" src=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-57.png\" srcset=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-57.png 767w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-57-300x172.png 300w\" sizes=\"(max-width: 767px) 100vw, 767px\" \/><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>Depending on the option selected in the first field, the \u201cPDF EText Recostar Project File Name\u201d and \u201cImage OCR Recostar Project File Name\u201d fields will be disabled or enabled:<\/p>\n<table>\n<tbody>\n<tr>\n<td><strong>Use EText Recostar Project File<\/strong><\/td>\n<td><strong>PDF EText Recostar Project File Name<\/strong><\/td>\n<td><strong>Image OCR Recostar Project File Name<\/strong><\/td>\n<\/tr>\n<tr>\n<td>Automatically<\/td>\n<td>Enabled<\/td>\n<td>Enabled<\/td>\n<\/tr>\n<tr>\n<td>Always<\/td>\n<td>Enabled<\/td>\n<td>Disabled<\/td>\n<\/tr>\n<tr>\n<td>Never<\/td>\n<td>Disabled<\/td>\n<td>Enabled<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><strong>Important: <\/strong>The default OCR language for FRP_EText.rsp is English (USA). To update the language(s), this file will need to be manually changed. (SharedFolder\\&lt;Batch Class Id&gt;\\fixed-form-extraction). For that, select required language(s) in the OCR Country\/Language on the RECOSTAR_HOCR plugin screen, copy selection and paste it under the Country parameter, save the file.<\/p>\n<p><img decoding=\"async\" width=\"1089\" height=\"551\" class=\"wp-image-30558\" src=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-58.png\" srcset=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-58.png 1089w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-58-300x152.png 300w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-58-768x389.png 768w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-58-1024x518.png 1024w\" sizes=\"(max-width: 1089px) 100vw, 1089px\" \/><\/p>\n<p>&nbsp;<\/p>\n<h4><strong>NUANCE_HOCR plugin (Linux)<\/strong><\/h4>\n<p>One mandatory field \u201cProcess PDFs as EText Files\u201d has been added to the plugin. Same as in the RECOSTAR_HOCR plugin, this field allows the user to select one of three available options provided for EText support:<\/p>\n<p>&#8211; Automatically<\/p>\n<p>&#8211; Always<\/p>\n<p>&#8211; Never<\/p>\n<p>The default value is Never.<\/p>\n<p><img decoding=\"async\" width=\"1134\" height=\"482\" class=\"wp-image-30559\" src=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-59.png\" srcset=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-59.png 1134w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-59-300x128.png 300w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-59-768x326.png 768w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-59-1024x435.png 1024w\" sizes=\"(max-width: 1134px) 100vw, 1134px\" \/><\/p>\n<p>EText support functionality is implemented in the similar way both in Windows and Linux environments.<\/p>\n<p>&nbsp;<\/p>\n<h4><strong>EText Support \u2013 AUTOMATICALLY<\/strong><\/h4>\n<p>&#8211; All input PDF files are analysed and EText compatible files are identified.<\/p>\n<p>&#8211; During batch processing, the <strong>EText_Processing<\/strong> folder is created under the ephesoft-system-folder (SharedFolders\\ephesoft-system-folder\\&lt;Batch Instance Id&gt;). The folder structure along with included files for RECOSTAR_HOCR plugin is presented below.<\/p>\n<table>\n<tbody>\n<tr>\n<td colspan=\"2\"><strong>ephesoft-system-folder<\/strong><\/td>\n<\/tr>\n<tr>\n<td colspan=\"2\"><\/td>\n<\/tr>\n<tr>\n<td>Batch Instance ID<\/p>\n<p>(e.g. BI1)<\/td>\n<td>&#8211; All extracted TIFF\/PNG files except TIFF\/PNGs which correspond to EText compatible PDF pages in the EText_Processing folder<\/p>\n<p>&#8211; Rsbatch file containing TIFF\/PNG files names except TIFF\/PNGs which correspond to EText compatible PDF pages in the EText_Processing folder*<\/p>\n<p>&#8211; HOCR files for non-EText-compatible pages<\/td>\n<\/tr>\n<tr>\n<td colspan=\"2\"><\/td>\n<\/tr>\n<tr>\n<td>EText_Processing<\/td>\n<td>&#8211; All EText compatible PDF files that are resized and denormalized (later to be used for Export)<\/p>\n<p>&#8211; Rsbatch file containing each single page PDF name for EText compatible files*<\/p>\n<p>&#8211; HOCR files for all single page EText compatible PDFs<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><em>* For NUANCE_HOCR plugin, no rsbatch file is created in the <\/em><strong><em>EText_Processing<\/em><\/strong><em> folder since this file is specific to RecoStar.<\/em><\/p>\n<p>All HOCR files present in <strong>EText_Processing<\/strong> folder are also copied to the Batch Instance folder under the ephesoft-system-folder.<\/p>\n<p>&nbsp;<\/p>\n<h4><strong>EText Support \u2013 ALWAYS<\/strong><\/h4>\n<p>&#8211; All input PDF files identified during execution of RECOSTAR_HOCR \/ NUANCE_HOCR plugin are by default considered to be EText compatible.<\/p>\n<p>&#8211; During batch processing, the <strong>EText_Processing<\/strong> folder is created under the ephesoft-system-folder (SharedFolders\\ephesoft-system-folder\\&lt;Batch Instance Id&gt;). The folder structure along with included files for RECOSTAR_HOCR plugin is presented below.<\/p>\n<table>\n<tbody>\n<tr>\n<td colspan=\"2\"><strong>ephesoft-system-folder<\/strong><\/td>\n<\/tr>\n<tr>\n<td colspan=\"2\"><\/td>\n<\/tr>\n<tr>\n<td>Batch Instance ID<\/p>\n<p>(e.g. BI1)<\/td>\n<td>&#8211; All extracted TIFF\/PNG files except TIFF\/PNGs which correspond to PDF pages in the EText_Processing folder<\/p>\n<p>&#8211; Rsbatch file containing TIFF\/PNG files names except TIFF\/PNGs which correspond to PDF pages in the EText_Processing folder*<\/p>\n<p>&#8211; Blank HOCR files in case of non-PDF input files or for PDF files without the EText layer#<\/td>\n<\/tr>\n<tr>\n<td colspan=\"2\"><\/td>\n<\/tr>\n<tr>\n<td>EText_Processing<\/td>\n<td>&#8211; All extracted PDF files that are resized and denormalized (later to be used for Export)<\/p>\n<p>&#8211; Rsbatch file containing each single page PDF name*<\/p>\n<p>&#8211; HOCR files for all single page PDFs (blank HOCR files in case of non-EText-compatible pages)<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><em>* For NUANCE_HOCR plugin, no rsbatch file is created in the <\/em><strong><em>EText_Processing<\/em><\/strong><em> folder since this file is specific to RecoStar.<\/em><\/p>\n<p><em># NUANCE_HOCR plugin generates normal HOCRs for TIFF\/PNG files, as the configuration SETTINGS.sts file used for Nuance has both PDF and non-PDF properties which are used according to the file type.<\/em><\/p>\n<p>All HOCR files present in <strong>EText_Processing<\/strong> folder are also copied to the Batch Instance folder under the ephesoft-system-folder.<\/p>\n<p>&nbsp;<\/p>\n<h4><strong>EText Support \u2013 NEVER<\/strong><\/h4>\n<p>&#8211; There is no special handling of EText compatible files.<\/p>\n<p>&#8211; <strong>EText_Processing<\/strong> folder is not created for a batch instance.<\/p>\n<p>&#8211; HOCR files are generated for all TIFF\/PNGs under the ephesoft-system-folder (SharedFolders\\ephesoft-system-folder\\&lt;Batch Instance Id&gt;) as was done prior to 2019.1 release.<\/p>\n<p>&nbsp;<\/p>\n<h3><a id=\"post-30147-_Learn_File(s)_\/_1\"><\/a><a id=\"post-30147-_Toc534204323\"><\/a><strong>Learn File(s) \/ Test Classification \/ Test Extraction <\/strong><\/h3>\n<p>All these three functionalities depend on the EText Support mode (ALWAYS\/AUTOMATICALLY\/NEVER) and will generate only 1 HOCR at a time.<\/p>\n<table>\n<tbody>\n<tr>\n<td colspan=\"3\"><strong>EText Support Mode<\/strong><\/td>\n<\/tr>\n<tr>\n<td><strong><em>Automatically<\/em><\/strong><\/td>\n<td><strong><em>Always<\/em><\/strong><\/td>\n<td><strong><em>Never<\/em><\/strong><\/td>\n<\/tr>\n<tr>\n<td width=\"500\">Whenever a PDF is uploaded, each page of the PDF is verified for EText availability. If EText layer is available, individual PDF pages are considered for OCRing, else TIFF files are used.<\/td>\n<td>Whenever a PDF is uploaded, each individual PDF page is considered for OCRing.<\/p>\n<p>In case of RECOSTAR_HOCR plugin, blank HOCR files are created for non-PDF pages\/files.In case of NUANCE_HOCR plugin, normal HOCR files are created for non-PDF pages\/files.<\/td>\n<td>Only TIFF files are considered for OCRing as in the previous versions of Transact.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><strong><em>Note on the Learn Files functionality<\/em><\/strong><em>: If the EText support mode is <\/em><strong><em>Always<\/em><\/strong><em> or <\/em><strong><em>Automatically<\/em><\/strong><em> and the user deletes the HOCR files manually from the corresponding folders, these EText PDF files will need to be re-uploaded and re-learned since individual PDF pages are not saved in the backend folder. <\/em><\/p>\n<p>&nbsp;<\/p>\n<h3><a id=\"post-30147-_Extraction_Configuration_Screens_1\"><\/a><a id=\"post-30147-_Toc534204324\"><\/a><strong>Extraction Configuration Screens<\/strong><\/h3>\n<p>To implement EText support feature, a new dropdown has been added to the Extraction configuration screens like KV Extraction Rule, Paragraph Extraction Rule, Cross Section Extraction Rule, Table Extraction Rule etc. (in general wherever <strong>View OCR Data<\/strong>\u00a0functionality is provided on the screen except for Review-Validate screens). The new dropdown contains two options: <strong>EText<\/strong> and <strong>OCR<\/strong>, with OCR as default.<\/p>\n<p><img decoding=\"async\" width=\"1270\" height=\"219\" class=\"wp-image-30560\" src=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-60.png\" srcset=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-60.png 1270w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-60-300x52.png 300w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-60-768x132.png 768w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-60-1024x177.png 1024w\" sizes=\"(max-width: 1270px) 100vw, 1270px\" \/><\/p>\n<p>Whenever a PDF is uploaded on any Extraction Configuration screen, it is analysed to identify whether it is EText compatible, irrespective of EText Support mode in Recostar_HOCR \/ NUANCE_HOCR plugins (ALWAYS\/AUTOMATICALLY\/NEVER).<\/p>\n<p><strong>If the PDF page is EText compatible<\/strong>, both TIFF as well as PDF page are considered for OCRing, thus the system creates 2 HOCR files. The new dropdown will become enabled, allowing the user to select which HOCR file (EText or OCR) to use to view OCR data. The default value of the dropdown is OCR.<\/p>\n<p><img decoding=\"async\" width=\"1464\" height=\"384\" class=\"wp-image-30561\" src=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-61.png\" srcset=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-61.png 1464w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-61-300x79.png 300w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-61-768x201.png 768w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-61-1024x269.png 1024w\" sizes=\"(max-width: 1464px) 100vw, 1464px\" \/><\/p>\n<p><strong><em>Note<\/em><\/strong><em>: The EText option in the dropdown is only used to view OCR data and test extraction. The overlays to create extraction rules are still going to be generated on the image as it was done previously.<\/em><\/p>\n<p><strong>If the PDF page is not EText compatible<\/strong>, only TIFF file is used for OCRing and the new dropdown will be disabled, with OCR option selected by default.<\/p>\n<p><img decoding=\"async\" width=\"1412\" height=\"472\" class=\"wp-image-30562\" src=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-62.png\" srcset=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-62.png 1412w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-62-300x100.png 300w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-62-768x257.png 768w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-62-1024x342.png 1024w\" sizes=\"(max-width: 1412px) 100vw, 1412px\" \/><\/p>\n<p>As for the View OCR functionality on the Review-Validate screens, the system will use only the generated HOCR contained inside the ephesoft-system-folder\\&lt;Batch Instance Id&gt;.<\/p>\n<h3><a id=\"post-30147-_Batch.xml_File_1\"><\/a><a id=\"post-30147-_Toc534204325\"><\/a><strong>Batch.xml File <\/strong><\/h3>\n<p>Two new parameters have been added to the batch.xml file:<\/p>\n<p>&#8211; &lt;<strong>ETextMode<\/strong>&gt; at the root level with three possible values (Always, Automatically, Never).<\/p>\n<p>&#8211; &lt;<strong>TreatAsEText<\/strong>&gt; at the page level with two possible values (true, false).<\/p>\n<table>\n<tbody>\n<tr>\n<td>EText Support mode<\/td>\n<td>&lt;<strong>ETextMode<\/strong>&gt; element<\/p>\n<p>at the root level<\/td>\n<td>&lt;<strong>TreatAsEText<\/strong>&gt; element<\/p>\n<p>at the page level<\/td>\n<\/tr>\n<tr>\n<td><strong>AUTOMATICALLY<\/strong><\/td>\n<td>Has a value of <strong>Automatically<\/strong><\/td>\n<td>All PDF pages in the batch.xml have the attribute &lt;<strong>TreatAsEText<\/strong>&gt; with a value of <strong>true<\/strong> for EText compatible page and <strong>false<\/strong> for non-compatible pages.<\/p>\n<p><strong><em>Note<\/em><\/strong><em>: This attribute does not appear for input pages that are not PDF.<\/em><\/td>\n<\/tr>\n<tr>\n<td><strong>ALWAYS<\/strong><\/td>\n<td>Has a value of <strong>Always<\/strong><\/td>\n<td>All PDF pages (both EText compatible and non-compatible) in the batch.xml have the attribute &lt;<strong>TreatAsEText<\/strong>&gt; with a value of <strong>true<\/strong>.<\/p>\n<p><strong><em>Note<\/em><\/strong><em>: This attribute does not appear for input pages that are not PDF.<\/em><\/td>\n<\/tr>\n<tr>\n<td><strong>NEVER<\/strong><\/td>\n<td>Has a value of <strong>Never<\/strong><\/td>\n<td>The &lt;<strong>TreatAsEText<\/strong>&gt; element is not included in the batch.xml<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>&nbsp;<\/p>\n<h3><a id=\"post-30147-_Export_Module\"><\/a><a id=\"post-30147-_Toc534204326\"><\/a><strong>Export Module <\/strong><\/h3>\n<p>To implement the EText Support feature, a new switch \u201cUse EText Original Pages When Available\u201d with values of TRUE and FALSE has been added to the CREATEMULTIPAGE_FILES plugin of the Export module both in Windows and Linux environments. The default value is TRUE.<\/p>\n<p><img decoding=\"async\" width=\"1396\" height=\"480\" class=\"wp-image-30563\" src=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-63.png\" srcset=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-63.png 1396w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-63-300x103.png 300w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-63-768x264.png 768w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-63-1024x352.png 1024w\" sizes=\"(max-width: 1396px) 100vw, 1396px\" \/><\/p>\n<table>\n<tbody>\n<tr>\n<td>TRUE<\/td>\n<td>Export PDFs are generated using the input PDFs, provided ALL pages of the document in batch.xml are EText compatible (&lt;TreatAsEText&gt; element for all pages is TRUE).<\/p>\n<p>If some pages of the document are EText compatible and some are not (&lt;TreatAsEText&gt; element is FALSE or absent), export files are created after the TIFF\/PNG to PDF conversion as it was done in previous versions of Transact.<\/td>\n<\/tr>\n<tr>\n<td>FALSE<\/td>\n<td>Export files are created after the TIFF\/PNG to PDF conversion as it was done in previous versions of Transact.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>Below is a short overview of functionality in various scenarios:<\/p>\n<table>\n<tbody>\n<tr>\n<td rowspan=\"2\"><strong><em>Switch Value<\/em><\/strong><\/td>\n<td colspan=\"3\"><strong><em>EText Support mode<\/em><\/strong><\/td>\n<\/tr>\n<tr>\n<td><strong><em>Automatically<\/em><\/strong><\/td>\n<td><strong><em>Always<\/em><\/strong><\/td>\n<td><strong><em>Never<\/em><\/strong><\/td>\n<\/tr>\n<tr>\n<td><strong><em>TRUE<\/em><\/strong><\/td>\n<td colspan=\"2\">All pages of the document in the batch.xml are scanned for the &lt;TreatAsEText&gt; element value.<\/p>\n<p>&#8211; If all the values are\u00a0<strong>true<\/strong>, then these denormalized PDF pages are fetched from ephesoft-system-folder\\&lt;Batch Instance Id&gt;\\EText_Processing folder to generate the export PDF for that document. No TIFF to PDF conversion occurs.<\/p>\n<p>&#8211; If a &lt;TreatAsEText&gt; element is\u00a0<strong>false<\/strong> or <strong>absent<\/strong>\u00a0for any page of the document, then the previous functionality of the plugin will take place to generate the Export PDF for that document. TIFF to PDF conversion occurs.<\/td>\n<td>&lt;TreatAsEText&gt; element in the batch.xml is not considered, the plugin generates export PDFs as was done previously, i.e. by converting TIFF to PDF.<\/td>\n<\/tr>\n<tr>\n<td><strong><em>FALSE<\/em><\/strong><\/td>\n<td colspan=\"3\">The plugin generates export PDFs as was done previously, i.e. by converting TIFF to PDF.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>&nbsp;<\/p>\n<h3><a id=\"post-30147-_Web_Services\"><\/a><a id=\"post-30147-_Toc534204327\"><\/a><strong>Web Services<\/strong><\/h3>\n<p>The following\u00a0<strong>new<\/strong>\u00a0webservices are created to support EText:<\/p>\n<ul>\n<li>\/splitMultiPagePDFtoPDFs<\/li>\n<li>\/createMultiPagePDFFromSinglePDFs<\/li>\n<li>\/batchClass\/uploadLearnFiles<\/li>\n<\/ul>\n<p>The following\u00a0<strong>existing<\/strong>\u00a0webservices are updated to support EText:<\/p>\n<ul>\n<li>\/createOCR<\/li>\n<li>\/batchClass\/learnFile\/{batchClassIdentifier}<\/li>\n<li>\/ocrClassifyExtract<\/li>\n<li>\/ocrClassifyExtractSearchablePdf<\/li>\n<li>\/initiateOcrClassifyExtract<\/li>\n<li>\/ocrClassify<\/li>\n<li>\/v2\/ocrClassifyExtract<\/li>\n<li>\/v2\/ocrClassifyExtractBase64<\/li>\n<li>\/executeMobileUpload<\/li>\n<li>\/keywordClassification<\/li>\n<li>\/createHOCRForBatchClass<\/li>\n<\/ul>\n<p>Detailed documentation for all available web services is provided on Swagger:<\/p>\n<p>http:\/\/&lt;IP address&gt;:&lt;port&gt;\/dcma\/rest\/swagger-ui.html<\/p>\n<p>&nbsp;<\/p>\n<h2><a id=\"post-30147-_Toc534204328\"><\/a><strong>Use Cases<\/strong><\/h2>\n<h3><a id=\"post-30147-_Toc534204329\"><\/a><strong>EText Mode \u2013 Automatically <\/strong><\/h3>\n<p><strong>Pre-requisites:<\/strong><\/p>\n<p>For Windows environment, in the RECOSTAR_HOCR plugin under the Page Process Module:<\/p>\n<p>&#8211; <strong>Automatically<\/strong> option should be selected from the \u201cUse EText Recostar Project File\u201d dropdown.<\/p>\n<p>&#8211; Both dropdowns \u201cPDF EText Recostar Project File Name\u201d and \u201cImage OCR Recostar Project File Name\u201d are enabled and <strong>FPR_EText.rsp <\/strong>and<strong> Fpr.srp<\/strong> files should be selected by default.<\/p>\n<p><img decoding=\"async\" width=\"1336\" height=\"575\" class=\"wp-image-30564\" src=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-64.png\" srcset=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-64.png 1336w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-64-300x129.png 300w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-64-768x331.png 768w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-64-1024x441.png 1024w\" sizes=\"(max-width: 1336px) 100vw, 1336px\" \/><\/p>\n<p>OR<\/p>\n<p>For Linux environment, in the NUANCE_HOCR plugin under the Page Process Module:<\/p>\n<p>&#8211; <strong>Automatically<\/strong> option should be selected from the \u201cProcess PDFs as EText Files\u201d.<\/p>\n<p><strong><img decoding=\"async\" width=\"1134\" height=\"481\" class=\"wp-image-30565\" src=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-65.png\" srcset=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-65.png 1134w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-65-300x127.png 300w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-65-768x326.png 768w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-65-1024x434.png 1024w\" sizes=\"(max-width: 1134px) 100vw, 1134px\" \/><\/strong><\/p>\n<p>For both Windows and Linux OS, in the CREATEMULTIPAGE_FILES plugin under the Export Module, the value of the \u201cUse EText Original Pages When Available\u201d switch should be TRUE, if you want to export original PDF files used at input.<\/p>\n<p><strong><img decoding=\"async\" width=\"1252\" height=\"507\" class=\"wp-image-30566\" src=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-66.png\" srcset=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-66.png 1252w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-66-300x121.png 300w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-66-768x311.png 768w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-66-1024x415.png 1024w\" sizes=\"(max-width: 1252px) 100vw, 1252px\" \/> <\/strong><\/p>\n<p>Now, let us process three-page PDF document which contains both EText compatible as well as non-compatible pages (the first page is non-compatible, the second and third pages contain EText layer). For that:<\/p>\n<p>1. On the Batch Class Management screen, create a batch class.<\/p>\n<p>2. Open your batch class and create a document type.<\/p>\n<p>3. On the Document Types screen, upload a Learn File.<\/p>\n<p>4. On the same screen, upload Test Classification File to check classification results, and click Test Classification.<\/p>\n<p><img decoding=\"async\" width=\"1884\" height=\"511\" class=\"wp-image-30567\" src=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-67.png\" srcset=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-67.png 1884w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-67-300x81.png 300w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-67-768x208.png 768w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-67-1024x278.png 1024w\" sizes=\"(max-width: 1884px) 100vw, 1884px\" \/><\/p>\n<p>5. On the Test Classification screen, click Classify to see classification results. HOCR files are created both for non-EText-compatible page as well as EText compatible pages, so all three pages are classified successfully.<\/p>\n<p><img decoding=\"async\" width=\"1757\" height=\"568\" class=\"wp-image-30568\" src=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-68.png\" srcset=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-68.png 1757w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-68-300x97.png 300w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-68-768x248.png 768w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-68-1024x331.png 1024w\" sizes=\"(max-width: 1757px) 100vw, 1757px\" \/><\/p>\n<p><strong>Note<\/strong>: HOCR files will be created for all types of input files, with a separate mechanism being used for all EText compatible PDF pages.<\/p>\n<p>6. Navigate to the Index Fields screen and create index fields. In this case, two index fields are created:<\/p>\n<p><em>\u00a0&#8211; TransID<\/em> index field on the first non-EText-compatible page, and<\/p>\n<p><em>\u00a0&#8211; Product No<\/em> index field on the second Etext compatible page.<\/p>\n<p><img decoding=\"async\" width=\"1854\" height=\"479\" class=\"wp-image-30569\" src=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-69.png\" srcset=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-69.png 1854w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-69-300x78.png 300w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-69-768x198.png 768w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-69-1024x265.png 1024w\" sizes=\"(max-width: 1854px) 100vw, 1854px\" \/><\/p>\n<p>7. Create extraction rules for your index fields by expanding Index Fields menu, selecting the index field and required extraction rule. In this case, KV extraction rules will be created for pages 1 and 2.<\/p>\n<p><img decoding=\"async\" width=\"1658\" height=\"356\" class=\"wp-image-30570\" src=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-70.png\" srcset=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-70.png 1658w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-70-300x64.png 300w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-70-768x165.png 768w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-70-1024x220.png 1024w\" sizes=\"(max-width: 1658px) 100vw, 1658px\" \/><\/p>\n<p>8. On the Extraction Configuration screen, upload the file and create extraction rules.<\/p>\n<p>Since the first page of our file is not EText compatible, the drop-down menu allowing to view OCR from EText PDF is disabled.<\/p>\n<p><strong><img decoding=\"async\" width=\"1669\" height=\"538\" class=\"wp-image-30571\" src=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-71.png\" srcset=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-71.png 1669w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-71-300x97.png 300w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-71-768x248.png 768w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-71-1024x330.png 1024w\" sizes=\"(max-width: 1669px) 100vw, 1669px\" \/> <\/strong><\/p>\n<p>The second and third pages of the document do have EText layer, so the dropdown becomes enabled on all Extraction Configuration screens, allowing you to select the source to view OCR data. EText extracted data is often more accurate. You can check it by selecting EText in the dropdown menu and clicking View OCR Data.<\/p>\n<p><img decoding=\"async\" width=\"1740\" height=\"660\" class=\"wp-image-30572\" src=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-72.png\" srcset=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-72.png 1740w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-72-300x114.png 300w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-72-768x291.png 768w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-72-1024x388.png 1024w\" sizes=\"(max-width: 1740px) 100vw, 1740px\" \/><\/p>\n<p>9. Once extraction rules are created, navigate back to the Document Types screen to test extraction results. For that, upload Test Extraction file and click Test Extraction.<\/p>\n<p><img decoding=\"async\" width=\"1784\" height=\"458\" class=\"wp-image-30573\" src=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-73.png\" srcset=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-73.png 1784w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-73-300x77.png 300w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-73-768x197.png 768w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-73-1024x263.png 1024w\" sizes=\"(max-width: 1784px) 100vw, 1784px\" \/><\/p>\n<p>10. On the Test Extraction screen, click Extract to see extraction results. As you can see below, the values are extracted from all pages, both non-EText-compatible (<em>TransID<\/em>) and EText compatible page (<em>Product No<\/em>).<\/p>\n<p><img decoding=\"async\" width=\"1696\" height=\"636\" class=\"wp-image-30574\" src=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-74.png\" srcset=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-74.png 1696w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-74-300x113.png 300w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-74-768x288.png 768w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-74-1024x384.png 1024w\" sizes=\"(max-width: 1696px) 100vw, 1696px\" \/><\/p>\n<p>11. Now, let us process a batch. Navigate to the Upload Batch screen, select a batch class and priority, upload the file and click Start Batch.<\/p>\n<p><img decoding=\"async\" width=\"1610\" height=\"573\" class=\"wp-image-30575\" src=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-75.png\" srcset=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-75.png 1610w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-75-300x107.png 300w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-75-768x273.png 768w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-75-1024x364.png 1024w\" sizes=\"(max-width: 1610px) 100vw, 1610px\" \/><\/p>\n<p>As the batch is being processing, a new folder is created under the ephesoft-system-folder\\&lt;Batch Instance Id&gt;, called \u201cEText_Processing\u201d.<\/p>\n<p><img decoding=\"async\" width=\"1169\" height=\"507\" class=\"wp-image-30576\" src=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-76.png\" srcset=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-76.png 1169w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-76-300x130.png 300w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-76-768x333.png 768w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-76-1024x444.png 1024w\" sizes=\"(max-width: 1169px) 100vw, 1169px\" \/><\/p>\n<p>This folder contains all original and denormalized EText compatible PDF pages present in the batch along with HOCR files. Denormalized files are going to be used later, at the Export stage. There is also a FileList.rsbatch file, which includes the names of all single page EText compatible PDFs.<\/p>\n<p>In this case, the batch contains two EText compatible page, all details of which are saved in the EText_Processing folder.<\/p>\n<p><img decoding=\"async\" width=\"1168\" height=\"490\" class=\"wp-image-30577\" src=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-77.png\" srcset=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-77.png 1168w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-77-300x126.png 300w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-77-768x322.png 768w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-77-1024x430.png 1024w\" sizes=\"(max-width: 1168px) 100vw, 1168px\" \/><\/p>\n<p>If the PDF page is not EText compatible or there are input files of a different format, their HOCR files will be saved in the ephesoft-system-folder\\&lt;Batch Instance Id&gt; folder. The same folder will also contain a separate rsbatch file with names of these files.<\/p>\n<p>In our case, there is one non-EText-compatible PDF page. It is saved in the BIA folder under the ephesoft-system-folder and its name is included in the rsbatch file.<\/p>\n<p><strong><img decoding=\"async\" width=\"1167\" height=\"527\" class=\"wp-image-30578\" src=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-78.png\" srcset=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-78.png 1167w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-78-300x135.png 300w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-78-768x347.png 768w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-78-1024x462.png 1024w\" sizes=\"(max-width: 1167px) 100vw, 1167px\" \/><\/strong><\/p>\n<p>12. Since all the pages are classified successfully, the batch doesn\u2019t stop at the Review stage.<\/p>\n<p>If the batch stops at the Validation stage, both values will be extracted successfully \u2013 both from EText compatible as well as non-compatible pages. In this case, one of the fields was set to Force Review. Click Validate to proceed.<\/p>\n<p><img decoding=\"async\" width=\"1364\" height=\"443\" class=\"wp-image-30579\" src=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-79.png\" srcset=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-79.png 1364w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-79-300x97.png 300w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-79-768x249.png 768w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-79-1024x333.png 1024w\" sizes=\"(max-width: 1364px) 100vw, 1364px\" \/><\/p>\n<p>13. The batch processing is complete and the batch.xml along with PDF file is exported to the final-drop-folder, as configured (SharedFolders\\final-drop-folder\\&lt;Batch Instance Id&gt;).<\/p>\n<p>14. Navigate to the folder and open batch.xml.<\/p>\n<p><img decoding=\"async\" width=\"1168\" height=\"618\" class=\"wp-image-30580\" src=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-80.png\" srcset=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-80.png 1168w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-80-300x159.png 300w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-80-768x406.png 768w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-80-1024x542.png 1024w\" sizes=\"(max-width: 1168px) 100vw, 1168px\" \/><\/p>\n<p>The batch.xml file includes two new attributes:<\/p>\n<p>&#8211; At the root level, the value of the new \u201cETextMode\u201d element is AUTOMATICALLY as configured.<\/p>\n<p><img decoding=\"async\" width=\"815\" height=\"490\" class=\"wp-image-30581\" src=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-81.png\" srcset=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-81.png 815w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-81-300x180.png 300w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-81-768x462.png 768w\" sizes=\"(max-width: 815px) 100vw, 815px\" \/><\/p>\n<p>&#8211; At the page level, the new \u201cTreatAsEText\u201d element is FALSE for all non-EText-compatible PDF pages and TRUE for all EText compatible PDF pages. In this case, this element value is FALSE for the first page and TRUE for two remaining pages.<\/p>\n<p><img decoding=\"async\" width=\"1627\" height=\"540\" class=\"wp-image-30582\" src=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-82.png\" srcset=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-82.png 1627w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-82-300x100.png 300w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-82-768x255.png 768w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-82-1024x340.png 1024w\" sizes=\"(max-width: 1627px) 100vw, 1627px\" \/><\/p>\n<p><strong>Note<\/strong>: The &lt;TreatAsEText&gt; element (TRUE\/FALSE) in the batch.xml applies only to pages in PDF format. This element will be absent for all pages in other formats (TIFF, PNG, Word etc.).<\/p>\n<p>15. Check exported PDF.<\/p>\n<p>Since we configured \u201cUse EText Original Pages When Available\u201d switch as\u00a0TRUE\u00a0in the CREATEMULTIPAGE_FILES plugin,\u00a0all the pages of the document in the batch.xml file are scanned for the &lt;TreatAsEText&gt; element value.<\/p>\n<p>Since the EText Support mode is AUTOMATICALLY, the &lt;TreatAsEText&gt; element is FALSE for the first PDF page of our batch and TRUE for the second and third pages. As per the feature implementation, TIFF to PDF conversion is used for all three pages (since the value of the &lt;TreatAsEText&gt; element in the batch.xml file is not TRUE for all pages). This means that export PDF does not contain EText layer on any page, all exported pages are not EText compatible.<\/p>\n<p><strong>Note<\/strong>: If export PDFs are generated as searchable using ITEXT (see configuration below), then such output PDF files also become EText compatible. In this case, however, they are not vector based PDFs as original input files, but rather have OCRed layer attached on top of the image.<\/p>\n<p><img decoding=\"async\" width=\"1283\" height=\"478\" class=\"wp-image-30583\" src=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-83.png\" srcset=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-83.png 1283w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-83-300x112.png 300w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-83-768x286.png 768w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-83-1024x382.png 1024w\" sizes=\"(max-width: 1283px) 100vw, 1283px\" \/><\/p>\n<p>&nbsp;<\/p>\n<h3><a id=\"post-30147-_Toc534204330\"><\/a><strong>EText Mode \u2013 Always<\/strong><\/h3>\n<p><strong>Pre-requisites:<\/strong><\/p>\n<p>For Windows environment, in the RECOSTAR_HOCR plugin under the Page Process Module:<\/p>\n<p>&#8211; <strong>Always<\/strong> option should be selected from the \u201cUse EText Recostar Project File\u201d dropdown.<\/p>\n<p>&#8211; <strong>FPR_EText.rsp<\/strong> file should be selected from the \u201cPDF EText Recostar Project File Name\u201d dropdown. \u201cImage OCR Recostar Project File Name\u201d dropdown is automatically disabled.<\/p>\n<p><img decoding=\"async\" width=\"1442\" height=\"582\" class=\"wp-image-30584\" src=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-84.png\" srcset=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-84.png 1442w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-84-300x121.png 300w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-84-768x310.png 768w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-84-1024x413.png 1024w\" sizes=\"(max-width: 1442px) 100vw, 1442px\" \/><\/p>\n<p>OR<\/p>\n<p>For Linux environment, in the NUANCE_HOCR plugin under the Page Process Module:<\/p>\n<p>&#8211; <strong>Always<\/strong> option should be selected from the \u201cProcess PDFs as EText Files\u201d.<\/p>\n<p><strong><img decoding=\"async\" width=\"1134\" height=\"482\" class=\"wp-image-30585\" src=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-85.png\" srcset=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-85.png 1134w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-85-300x128.png 300w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-85-768x326.png 768w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-85-1024x435.png 1024w\" sizes=\"(max-width: 1134px) 100vw, 1134px\" \/><\/strong><\/p>\n<p>For both Windows and Linux OS, in the CREATEMULTIPAGE_FILES plugin under the Export Module, the value of the \u201cUse EText Original Pages When Available\u201d switch should be TRUE, if you want to export original PDF files used at input.<\/p>\n<p><strong><img decoding=\"async\" width=\"1252\" height=\"507\" class=\"wp-image-30586\" src=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-86.png\" srcset=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-86.png 1252w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-86-300x121.png 300w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-86-768x311.png 768w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-86-1024x415.png 1024w\" sizes=\"(max-width: 1252px) 100vw, 1252px\" \/> <\/strong><\/p>\n<p>Now, let us process three-page PDF document which contains both EText compatible as well as non-compatible pages (the first page is non-compatible, the second and third pages are EText compatible). For that:<\/p>\n<p>1. On the Batch Class Management screen, create a batch class.<\/p>\n<p>2. Open your batch class and create a document type.<\/p>\n<p>3. On the Document Types screen, upload a Learn File.<\/p>\n<p>4. On the same screen, upload Test Classification File to check classification results, and click Test Classification.<\/p>\n<p><img decoding=\"async\" width=\"1884\" height=\"511\" class=\"wp-image-30587\" src=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-87.png\" srcset=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-87.png 1884w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-87-300x81.png 300w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-87-768x208.png 768w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-87-1024x278.png 1024w\" sizes=\"(max-width: 1884px) 100vw, 1884px\" \/><\/p>\n<p>5. On the Test Classification screen, click Classify to see classification results. Since no HOCR file is created for non-EText-compatible page, the first page is not classified. In this scenario, HOCR files are created only for EText compatible pages, so the remaining two pages are classified successfully.<\/p>\n<p><img decoding=\"async\" width=\"1811\" height=\"575\" class=\"wp-image-30588\" src=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-88.png\" srcset=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-88.png 1811w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-88-300x95.png 300w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-88-768x244.png 768w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-88-1024x325.png 1024w\" sizes=\"(max-width: 1811px) 100vw, 1811px\" \/><\/p>\n<p><strong>Note<\/strong>: When the EText Support mode is ALWAYS, HOCR files are created ONLY for EText compatible PDF pages. HOCR files are not created for any other type of input files.<\/p>\n<p>6. Navigate to the Index Fields screen and create index fields. In this case, two index fields are created:<\/p>\n<p><em>\u00a0&#8211; TransID<\/em> index field on the first non-EText -compatible page, and<\/p>\n<p><em>\u00a0&#8211; Product No<\/em> index field on the second Etext compatible page.<\/p>\n<p><img decoding=\"async\" width=\"1854\" height=\"479\" class=\"wp-image-30589\" src=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-89.png\" srcset=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-89.png 1854w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-89-300x78.png 300w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-89-768x198.png 768w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-89-1024x265.png 1024w\" sizes=\"(max-width: 1854px) 100vw, 1854px\" \/><\/p>\n<p>7. Create extraction rules for your index fields by expanding Index Fields menu, selecting the index field and required extraction rule. In this case, KV extraction rules will be created for pages 1 and 2.<\/p>\n<p><img decoding=\"async\" width=\"1658\" height=\"356\" class=\"wp-image-30590\" src=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-90.png\" srcset=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-90.png 1658w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-90-300x64.png 300w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-90-768x165.png 768w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-90-1024x220.png 1024w\" sizes=\"(max-width: 1658px) 100vw, 1658px\" \/><\/p>\n<p>8. On the Extraction Configuration screen, upload the file and create extraction rules.<\/p>\n<p>Since the first page of our file is not EText compatible, the dropdown menu allowing to view OCR from EText PDF is disabled.<\/p>\n<p><strong><img decoding=\"async\" width=\"1669\" height=\"538\" class=\"wp-image-30591\" src=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-91.png\" srcset=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-91.png 1669w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-91-300x97.png 300w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-91-768x248.png 768w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-91-1024x330.png 1024w\" sizes=\"(max-width: 1669px) 100vw, 1669px\" \/> <\/strong><\/p>\n<p>The second and third pages of the document do have EText layer, so the dropdown becomes enabled on all Extraction Configuration screens, allowing you to select the source to view OCR data. EText extracted data is often more accurate. You can check it by selecting EText in the dropdown menu and clicking View OCR Data.<\/p>\n<p><img decoding=\"async\" width=\"1740\" height=\"660\" class=\"wp-image-30592\" src=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-92.png\" srcset=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-92.png 1740w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-92-300x114.png 300w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-92-768x291.png 768w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-92-1024x388.png 1024w\" sizes=\"(max-width: 1740px) 100vw, 1740px\" \/><\/p>\n<p>9. Once extraction rules are created, navigate back to the Document Types screen to test extraction results. For that, upload Test Extraction file and click Test Extraction.<\/p>\n<p><img decoding=\"async\" width=\"1784\" height=\"458\" class=\"wp-image-30593\" src=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-93.png\" srcset=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-93.png 1784w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-93-300x77.png 300w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-93-768x197.png 768w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-93-1024x263.png 1024w\" sizes=\"(max-width: 1784px) 100vw, 1784px\" \/><\/p>\n<p>10. On the Test Extraction screen, click Extract to see extraction results. As you can see below, the value is only extracted from the EText compatible page (<em>Product No<\/em>). Since the selected EText mode is ALWAYS, only EText compatible pages are processed in this case.<\/p>\n<p><img decoding=\"async\" width=\"1755\" height=\"581\" class=\"wp-image-30594\" src=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-94.png\" srcset=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-94.png 1755w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-94-300x99.png 300w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-94-768x254.png 768w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-94-1024x339.png 1024w\" sizes=\"(max-width: 1755px) 100vw, 1755px\" \/><\/p>\n<p>11. Now, let us process a batch. Navigate to the Upload Batch screen, select a batch class and priority, upload the file and click Start Batch.<\/p>\n<p><img decoding=\"async\" width=\"1610\" height=\"573\" class=\"wp-image-30595\" src=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-95.png\" srcset=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-95.png 1610w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-95-300x107.png 300w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-95-768x273.png 768w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-95-1024x364.png 1024w\" sizes=\"(max-width: 1610px) 100vw, 1610px\" \/><\/p>\n<p>As the batch is being processing, a new folder is created under the ephesoft-system-folder\\&lt;Batch Instance Id&gt;, called \u201cEText_Processing\u201d.<\/p>\n<p><img decoding=\"async\" width=\"1061\" height=\"458\" class=\"wp-image-30596\" src=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-96.png\" srcset=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-96.png 1061w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-96-300x130.png 300w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-96-768x332.png 768w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-96-1024x442.png 1024w\" sizes=\"(max-width: 1061px) 100vw, 1061px\" \/><\/p>\n<p>This folder contains all original and denormalized PDF pages present in the batch along with HOCR files. Denormalized files are going to be used later, at the Export stage. There is also a FileList.rsbatch file, which includes the names of all single page PDFs.<\/p>\n<p><img decoding=\"async\" width=\"1166\" height=\"710\" class=\"wp-image-30597\" src=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-97.png\" srcset=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-97.png 1166w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-97-300x183.png 300w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-97-768x468.png 768w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-97-1024x624.png 1024w\" sizes=\"(max-width: 1166px) 100vw, 1166px\" \/><\/p>\n<p>If the PDF page is not EText compatible, its HOCR file will be blank. In our case, the first page does not contain EText layer, so its HOCR file looks as follows:<\/p>\n<p><strong><img decoding=\"async\" width=\"1169\" height=\"713\" class=\"wp-image-30598\" src=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-98.png\" srcset=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-98.png 1169w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-98-300x183.png 300w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-98-768x468.png 768w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-98-1024x625.png 1024w\" sizes=\"(max-width: 1169px) 100vw, 1169px\" \/><\/strong><\/p>\n<p><strong>Note<\/strong>: If a batch contains any non-PDF pages, the HOCR files created for them will also be blank and will be located in the batch instance folder under the ephesoft-system-folder (SharedFolders\\ephesoft-system-folder\\&lt;Batch Instance Id&gt;).<\/p>\n<p>In case of NUANCE_HOCR plugin, HOCR files will be created as usual both for PDF and non-PDF pages.<\/p>\n<p>12. Our batch contains one page that is not EText compatible and HOCR file for this page is blank. Hence it cannot be classified, and the batch stops at the Review stage. All EText compatible pages are classified successfully.<\/p>\n<p>Select the document type from the dropdown list, if needed merge selected pages and click Review to proceed.<\/p>\n<p><img decoding=\"async\" width=\"1701\" height=\"564\" class=\"wp-image-30599\" src=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-99.png\" srcset=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-99.png 1701w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-99-300x99.png 300w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-99-768x255.png 768w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-99-1024x340.png 1024w\" sizes=\"(max-width: 1701px) 100vw, 1701px\" \/><\/p>\n<p><strong>Note<\/strong>: View OCR functionality on the Review-Validate screens for non-EText-compatible pages will not work in this case. When the View OCR button is clicked, the system will return blank page. When moving to the non-EText compatible pages, the following message is displayed:<\/p>\n<p><img decoding=\"async\" width=\"225\" height=\"87\" class=\"wp-image-30600\" src=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-100.png\" \/><\/p>\n<p>13. On the Validation screen, the values are only extracted for the EText compatible pages. In this case, only the <em>Product No<\/em> value is extracted, while <em>TransID<\/em> index field value is blank as its KV extraction rule is configured for a non-EText-compatible page.<\/p>\n<p>Since there is no HOCR file created for non-compatible page, the value cannot be specified by creating overlay on the image on the RV screen and needs to be entered manually, if required. Once done, click Validate to proceed.<\/p>\n<p><img decoding=\"async\" width=\"1718\" height=\"497\" class=\"wp-image-30601\" src=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-101.png\" srcset=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-101.png 1718w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-101-300x87.png 300w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-101-768x222.png 768w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-101-1024x296.png 1024w\" sizes=\"(max-width: 1718px) 100vw, 1718px\" \/><\/p>\n<p>14. The batch processing is complete and the batch.xml along with PDF file is exported to the final-drop-folder, as configured (SharedFolders\\final-drop-folder\\&lt;Batch Instance Id&gt;).<\/p>\n<p>Navigate to the folder and open batch.xml.<\/p>\n<p><img decoding=\"async\" width=\"1166\" height=\"712\" class=\"wp-image-30602\" src=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-102.png\" srcset=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-102.png 1166w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-102-300x183.png 300w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-102-768x469.png 768w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-102-1024x625.png 1024w\" sizes=\"(max-width: 1166px) 100vw, 1166px\" \/><\/p>\n<p>Batch.xml contains two new attributes:<\/p>\n<p>&#8211; At the root level, the value of the new \u201cETextMode\u201d element is ALWAYS as configured.<\/p>\n<p><img decoding=\"async\" width=\"783\" height=\"446\" class=\"wp-image-30603\" src=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-103.png\" srcset=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-103.png 783w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-103-300x171.png 300w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-103-768x437.png 768w\" sizes=\"(max-width: 783px) 100vw, 783px\" \/><\/p>\n<p>&#8211; At the page level, the new \u201cTreatAsEText\u201d element is TRUE for all PDF pages, both EText compatible and not (as per implementation of the ALWAYS EText Support mode).<\/p>\n<p>In this case though, the first page is not EText compatible, so no HOCR has been created for it. Hence, this page has one more attribute \u201cIsBlank\u201d, the value of which is TRUE. The second and third pages contain EText layer, HOCR files are created for them, so \u201cIsBlank\u201d element is not present for these pages.<\/p>\n<p><img decoding=\"async\" width=\"814\" height=\"540\" class=\"wp-image-30604\" src=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-104.png\" srcset=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-104.png 814w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-104-300x199.png 300w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-104-768x509.png 768w\" sizes=\"(max-width: 814px) 100vw, 814px\" \/><\/p>\n<p><strong>Note<\/strong>: The &lt;TreatAsEText&gt; element (TRUE\/FALSE) in the batch.xml applies only to pages in PDF format. This element will be absent for all pages in other formats (TIFF, PNG, Word etc.).<\/p>\n<p>15. Check exported PDF.<\/p>\n<p>Since we configured \u201cUse EText Original Pages When Available\u201d switch as\u00a0TRUE\u00a0in the CREATEMULTIPAGE_FILES plugin,\u00a0all the pages of the document in the batch.xml file are scanned for the &lt;TreatAsEText&gt; element value.<\/p>\n<p>Since the EText Support mode is ALWAYS, the &lt;TreatAsEText&gt; element is TRUE for all PDF pages, that means that PDF pages are fetched from the ephesoft-system-folder\\&lt;Batch Instance Id&gt;\\EText_Processing folder to generate the export PDF for that document. No TIFF to PDF conversion occurs in this case. Thus, our document will contain the first non-EText-compatible page and two remaining pages with EText layer, same as during input.<\/p>\n<p>&nbsp;<\/p>\n<h3><a id=\"post-30147-_Toc534204331\"><\/a><strong>EText Mode \u2013 Never <\/strong><\/h3>\n<p>In this case, the functionality works same way as it did prior to the 2019.1 release and EText Support feature implementation.<\/p>\n<p><strong>Pre-requisites:<\/strong><\/p>\n<p>For Windows environment, in the RECOSTAR_HOCR plugin under the Page Process Module:<\/p>\n<p>&#8211; <strong>Never<\/strong> option should be selected from the \u201cUse EText Recostar Project File\u201d dropdown.<\/p>\n<p>&#8211; <strong>Fpr.rsp<\/strong> file should be selected from the \u201cImage OCR Recostar Project File Name\u201d dropdown. \u201cPDF EText Recostar Project File Name\u201d dropdown is automatically disabled.<\/p>\n<p><img decoding=\"async\" width=\"1173\" height=\"528\" class=\"wp-image-30605\" src=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-105.png\" srcset=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-105.png 1173w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-105-300x135.png 300w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-105-768x346.png 768w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-105-1024x461.png 1024w\" sizes=\"(max-width: 1173px) 100vw, 1173px\" \/><\/p>\n<p>OR<\/p>\n<p>For Linux environment, in the NUANCE_HOCR plugin under the Page Process Module:<\/p>\n<p>&#8211; <strong>Never<\/strong> option should be selected from the \u201cProcess PDFs as EText Files\u201d.<\/p>\n<p><strong><img decoding=\"async\" width=\"1134\" height=\"481\" class=\"wp-image-30606\" src=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-106.png\" srcset=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-106.png 1134w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-106-300x127.png 300w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-106-768x326.png 768w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-106-1024x434.png 1024w\" sizes=\"(max-width: 1134px) 100vw, 1134px\" \/><\/strong><\/p>\n<p>Since no EText processing is done in this case, the value of the \u201cUse EText Original Pages When Available\u201d switch in the CREATEMULTIPAGE_FILES plugin under the Export Module does not matter. It can be either TRUE by default or FALSE.<\/p>\n<p><img decoding=\"async\" width=\"1324\" height=\"567\" class=\"wp-image-30607\" src=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-107.png\" srcset=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-107.png 1324w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-107-300x128.png 300w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-107-768x329.png 768w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-107-1024x439.png 1024w\" sizes=\"(max-width: 1324px) 100vw, 1324px\" \/><\/p>\n<p>Now, let us process three-page PDF document which contains both EText compatible as well as non-compatible pages (the first page is non-compatible, the second and third pages are EText compatible). For that:<\/p>\n<p>1. On the Batch Class Management screen, create a batch class.<\/p>\n<p>2. Open your batch class and create a document type.<\/p>\n<p>3. On the Document Types screen, upload a Learn File.<\/p>\n<p>4. On the same screen, upload Test Classification File to check classification results, and click Test Classification.<\/p>\n<p><img decoding=\"async\" width=\"1884\" height=\"511\" class=\"wp-image-30608\" src=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-108.png\" srcset=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-108.png 1884w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-108-300x81.png 300w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-108-768x208.png 768w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-108-1024x278.png 1024w\" sizes=\"(max-width: 1884px) 100vw, 1884px\" \/><\/p>\n<p>5. On the Test Classification screen, click Classify to see classification results. HOCR files are created for all pages as usual using PDF to TIFF conversion, so all three pages are classified successfully.<\/p>\n<p><img decoding=\"async\" width=\"1757\" height=\"568\" class=\"wp-image-30609\" src=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-109.png\" srcset=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-109.png 1757w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-109-300x97.png 300w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-109-768x248.png 768w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-109-1024x331.png 1024w\" sizes=\"(max-width: 1757px) 100vw, 1757px\" \/><\/p>\n<p>6. Navigate to the Index Fields screen and create index fields. In this case, two index fields are created:<\/p>\n<p><em>\u00a0&#8211; TransID<\/em> index field on the first non-EText-compatible page, and<\/p>\n<p><em>\u00a0&#8211; Product No<\/em> index field on the second Etext compatible page.<\/p>\n<p><img decoding=\"async\" width=\"1854\" height=\"479\" class=\"wp-image-30610\" src=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-110.png\" srcset=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-110.png 1854w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-110-300x78.png 300w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-110-768x198.png 768w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-110-1024x265.png 1024w\" sizes=\"(max-width: 1854px) 100vw, 1854px\" \/><\/p>\n<p>7. Create extraction rules for your index fields by expanding Index Fields menu, selecting the index field and required extraction rule. In this case, KV extraction rules will be created for pages 1 and 2.<\/p>\n<p><img decoding=\"async\" width=\"1658\" height=\"356\" class=\"wp-image-30611\" src=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-111.png\" srcset=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-111.png 1658w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-111-300x64.png 300w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-111-768x165.png 768w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-111-1024x220.png 1024w\" sizes=\"(max-width: 1658px) 100vw, 1658px\" \/><\/p>\n<p>8. On the Extraction Configuration screen, upload the file and create extraction rules.<\/p>\n<p>Since the first page of our file is not EText compatible, the dropdown menu allowing to view OCR from EText PDF is disabled.<\/p>\n<p><strong><img decoding=\"async\" width=\"1669\" height=\"538\" class=\"wp-image-30612\" src=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-112.png\" srcset=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-112.png 1669w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-112-300x97.png 300w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-112-768x248.png 768w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-112-1024x330.png 1024w\" sizes=\"(max-width: 1669px) 100vw, 1669px\" \/> <\/strong><\/p>\n<p>The second and third pages of the document do have EText layer, so the dropdown becomes enabled on all Extraction Configuration screens, allowing you to select the source to view OCR data. EText extracted data is often more accurate. You can check it by selecting EText in the dropdown menu and clicking View OCR Data.<\/p>\n<p><img decoding=\"async\" width=\"1740\" height=\"660\" class=\"wp-image-30613\" src=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-113.png\" srcset=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-113.png 1740w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-113-300x114.png 300w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-113-768x291.png 768w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-113-1024x388.png 1024w\" sizes=\"(max-width: 1740px) 100vw, 1740px\" \/><\/p>\n<p>9. Once extraction rules are created, navigate back to the Document Types screen to test extraction results. For that, upload Test Extraction file and click Test Extraction.<\/p>\n<p><img decoding=\"async\" width=\"1784\" height=\"458\" class=\"wp-image-30614\" src=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-114.png\" srcset=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-114.png 1784w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-114-300x77.png 300w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-114-768x197.png 768w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-114-1024x263.png 1024w\" sizes=\"(max-width: 1784px) 100vw, 1784px\" \/><\/p>\n<p>10. On the Test Extraction screen, click Extract to see extraction results. As you can see below, the values are extracted from all pages (<em>TransID<\/em> and <em>Product No<\/em>).<\/p>\n<p><img decoding=\"async\" width=\"1696\" height=\"636\" class=\"wp-image-30615\" src=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-115.png\" srcset=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-115.png 1696w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-115-300x113.png 300w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-115-768x288.png 768w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-115-1024x384.png 1024w\" sizes=\"(max-width: 1696px) 100vw, 1696px\" \/><\/p>\n<p>11. Now, let us process a batch. Navigate to the Upload Batch screen, select a batch class and priority, upload the file and click Start Batch.<\/p>\n<p><img decoding=\"async\" width=\"1610\" height=\"573\" class=\"wp-image-30616\" src=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-116.png\" srcset=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-116.png 1610w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-116-300x107.png 300w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-116-768x273.png 768w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-116-1024x364.png 1024w\" sizes=\"(max-width: 1610px) 100vw, 1610px\" \/><\/p>\n<p>As the batch is being processing, all converted TIFF\/PNG images and HOCR files are saved in the ephesoft-system-folder\\&lt;Batch Instance Id&gt; folder as in previous versions of Transact (no \u201cEText_Processing\u201d folder is created in this case).<\/p>\n<p>The same batch instance folder also contains a FileList.rsbatch file, which includes the names of all single pages of the input file.<\/p>\n<p><img decoding=\"async\" width=\"1168\" height=\"662\" class=\"wp-image-30617\" src=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-117.png\" srcset=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-117.png 1168w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-117-300x170.png 300w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-117-768x435.png 768w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-117-1024x580.png 1024w\" sizes=\"(max-width: 1168px) 100vw, 1168px\" \/><\/p>\n<p>12. Since all the pages are classified successfully, the batch doesn\u2019t stop at the Review stage.<\/p>\n<p>If the batch stops at the Validation stage, both values will be extracted successfully since HOCR files are created for all input pages. In this case, one of the fields was set to Force Review. Click Validate to proceed.<\/p>\n<p><img decoding=\"async\" width=\"1364\" height=\"443\" class=\"wp-image-30618\" src=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-118.png\" srcset=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-118.png 1364w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-118-300x97.png 300w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-118-768x249.png 768w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-118-1024x333.png 1024w\" sizes=\"(max-width: 1364px) 100vw, 1364px\" \/><\/p>\n<p>13. The batch processing is complete and the batch.xml along with PDF file is exported to the final-drop-folder, as configured (SharedFolders\\final-drop-folder\\&lt;Batch Instance Id&gt;).<\/p>\n<p>Navigate to the folder and open batch.xml.<\/p>\n<p><img decoding=\"async\" width=\"1166\" height=\"658\" class=\"wp-image-30619\" src=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-119.png\" srcset=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-119.png 1166w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-119-300x169.png 300w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-119-768x433.png 768w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-119-1024x578.png 1024w\" sizes=\"(max-width: 1166px) 100vw, 1166px\" \/><\/p>\n<p>Batch.xml contains only one new attribute:<\/p>\n<p>&#8211; At the root level, the value of the new &lt;ETextMode&gt; element is NEVER as configured.<\/p>\n<p><img decoding=\"async\" width=\"829\" height=\"514\" class=\"wp-image-30620\" src=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-120.png\" srcset=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-120.png 829w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-120-300x186.png 300w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-120-768x476.png 768w\" sizes=\"(max-width: 829px) 100vw, 829px\" \/><\/p>\n<p><strong>Note<\/strong>: At the page level, the new &lt;TreatAsEText&gt; element will not be used in this case.<\/p>\n<p>14. Check exported PDF.<\/p>\n<p>Since usual PDF to TIFF \/ TIFF to PDF conversion is used in this case and no EText processing is involved, the exported PDF will not contain pages with EText layer, even though some input pages were EText compatible.<\/p>\n<p><strong>Note<\/strong>: If export PDFs are generated as searchable using ITEXT (see configuration below), then such output PDF files also become EText compatible. In this case, however, they are not vector based PDFs as original input files, but rather have OCRed layer attached on top of the image.<\/p>\n<p><img decoding=\"async\" width=\"1283\" height=\"478\" class=\"wp-image-30621\" src=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-121.png\" srcset=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-121.png 1283w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-121-300x112.png 300w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-121-768x286.png 768w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-121-1024x382.png 1024w\" sizes=\"(max-width: 1283px) 100vw, 1283px\" \/><\/p>\n","protected":false},"featured_media":0,"parent":28466,"menu_order":3,"comment_status":"closed","ping_status":"closed","template":"","doc_tag":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO Premium plugin v19.0 (Yoast SEO v22.1) - https:\/\/yoast.com\/wordpress\/plugins\/seo\/ -->\n<title>EText Support - Leveraging Existing Text Layer in PDF Documents | Ephesoft Docs<\/title>\n<meta name=\"robots\" content=\"noindex, follow\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"EText Support - Leveraging Existing Text Layer in PDF Documents\" \/>\n<meta property=\"og:description\" content=\"Introduction EText Functionality Page Process Module Learn File(s) \/ Test Classification \/ Test Extraction Extraction Configuration Screens Batch.xml File Export [&hellip;]\" \/>\n<meta property=\"og:url\" content=\"https:\/\/ephesoft.com\/docs\/products\/transact\/release-notes\/release-notes-2019-1\/etext-support-in-pdf\/\" \/>\n<meta property=\"og:site_name\" content=\"Ephesoft Docs\" \/>\n<meta property=\"article:modified_time\" content=\"2020-05-19T19:24:18+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-56.png\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data1\" content=\"25 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/ephesoft.com\/docs\/products\/transact\/release-notes\/release-notes-2019-1\/etext-support-in-pdf\/\",\"url\":\"https:\/\/ephesoft.com\/docs\/products\/transact\/release-notes\/release-notes-2019-1\/etext-support-in-pdf\/\",\"name\":\"EText Support - Leveraging Existing Text Layer in PDF Documents | Ephesoft Docs\",\"isPartOf\":{\"@id\":\"https:\/\/ephesoft.com\/docs\/#website\"},\"datePublished\":\"2019-01-30T19:54:57+00:00\",\"dateModified\":\"2020-05-19T19:24:18+00:00\",\"breadcrumb\":{\"@id\":\"https:\/\/ephesoft.com\/docs\/products\/transact\/release-notes\/release-notes-2019-1\/etext-support-in-pdf\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/ephesoft.com\/docs\/products\/transact\/release-notes\/release-notes-2019-1\/etext-support-in-pdf\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/ephesoft.com\/docs\/products\/transact\/release-notes\/release-notes-2019-1\/etext-support-in-pdf\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/ephesoft.com\/docs\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Transact\",\"item\":\"https:\/\/ephesoft.com\/docs\/products\/transact\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Release Notes and Software Updates\",\"item\":\"https:\/\/ephesoft.com\/docs\/products\/transact\/release-notes\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"2019.1\",\"item\":\"https:\/\/ephesoft.com\/docs\/products\/transact\/release-notes\/release-notes-2019-1\/\"},{\"@type\":\"ListItem\",\"position\":5,\"name\":\"EText Support &#8211; Leveraging Existing Text Layer in PDF Documents\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/ephesoft.com\/docs\/#website\",\"url\":\"https:\/\/ephesoft.com\/docs\/\",\"name\":\"Ephesoft Docs\",\"description\":\"Intelligent Document Processing Made Easy\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/ephesoft.com\/docs\/?s={search_term_string}\"},\"query-input\":\"required name=search_term_string\"}],\"inLanguage\":\"en-US\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"EText Support - Leveraging Existing Text Layer in PDF Documents | Ephesoft Docs","robots":{"index":"noindex","follow":"follow"},"og_locale":"en_US","og_type":"article","og_title":"EText Support - Leveraging Existing Text Layer in PDF Documents","og_description":"Introduction EText Functionality Page Process Module Learn File(s) \/ Test Classification \/ Test Extraction Extraction Configuration Screens Batch.xml File Export [&hellip;]","og_url":"https:\/\/ephesoft.com\/docs\/products\/transact\/release-notes\/release-notes-2019-1\/etext-support-in-pdf\/","og_site_name":"Ephesoft Docs","article_modified_time":"2020-05-19T19:24:18+00:00","og_image":[{"url":"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/word-image-56.png"}],"twitter_card":"summary_large_image","twitter_misc":{"Est. reading time":"25 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/ephesoft.com\/docs\/products\/transact\/release-notes\/release-notes-2019-1\/etext-support-in-pdf\/","url":"https:\/\/ephesoft.com\/docs\/products\/transact\/release-notes\/release-notes-2019-1\/etext-support-in-pdf\/","name":"EText Support - Leveraging Existing Text Layer in PDF Documents | Ephesoft Docs","isPartOf":{"@id":"https:\/\/ephesoft.com\/docs\/#website"},"datePublished":"2019-01-30T19:54:57+00:00","dateModified":"2020-05-19T19:24:18+00:00","breadcrumb":{"@id":"https:\/\/ephesoft.com\/docs\/products\/transact\/release-notes\/release-notes-2019-1\/etext-support-in-pdf\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/ephesoft.com\/docs\/products\/transact\/release-notes\/release-notes-2019-1\/etext-support-in-pdf\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/ephesoft.com\/docs\/products\/transact\/release-notes\/release-notes-2019-1\/etext-support-in-pdf\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/ephesoft.com\/docs\/"},{"@type":"ListItem","position":2,"name":"Transact","item":"https:\/\/ephesoft.com\/docs\/products\/transact\/"},{"@type":"ListItem","position":3,"name":"Release Notes and Software Updates","item":"https:\/\/ephesoft.com\/docs\/products\/transact\/release-notes\/"},{"@type":"ListItem","position":4,"name":"2019.1","item":"https:\/\/ephesoft.com\/docs\/products\/transact\/release-notes\/release-notes-2019-1\/"},{"@type":"ListItem","position":5,"name":"EText Support &#8211; Leveraging Existing Text Layer in PDF Documents"}]},{"@type":"WebSite","@id":"https:\/\/ephesoft.com\/docs\/#website","url":"https:\/\/ephesoft.com\/docs\/","name":"Ephesoft Docs","description":"Intelligent Document Processing Made Easy","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/ephesoft.com\/docs\/?s={search_term_string}"},"query-input":"required name=search_term_string"}],"inLanguage":"en-US"}]}},"comment_count":0,"_links":{"self":[{"href":"https:\/\/ephesoft.com\/docs\/wp-json\/wp\/v2\/docs\/30147"}],"collection":[{"href":"https:\/\/ephesoft.com\/docs\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/ephesoft.com\/docs\/wp-json\/wp\/v2\/types\/docs"}],"replies":[{"embeddable":true,"href":"https:\/\/ephesoft.com\/docs\/wp-json\/wp\/v2\/comments?post=30147"}],"version-history":[{"count":0,"href":"https:\/\/ephesoft.com\/docs\/wp-json\/wp\/v2\/docs\/30147\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/ephesoft.com\/docs\/wp-json\/wp\/v2\/docs\/28466"}],"next":[{"title":"Ephesoft Transact Release Support","link":"https:\/\/ephesoft.com\/docs\/products\/transact\/release-notes\/release-notes-2019-1\/transact-release-support\/","href":"https:\/\/ephesoft.com\/docs\/wp-json\/wp\/v2\/docs\/28467"}],"prev":[{"title":"Expedite Export","link":"https:\/\/ephesoft.com\/docs\/products\/transact\/release-notes\/release-notes-2019-1\/expedite-export\/","href":"https:\/\/ephesoft.com\/docs\/wp-json\/wp\/v2\/docs\/30314"}],"wp:attachment":[{"href":"https:\/\/ephesoft.com\/docs\/wp-json\/wp\/v2\/media?parent=30147"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/ephesoft.com\/docs\/wp-json\/wp\/v2\/doc_tag?post=30147"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}