Unicode Installations

enaio® 10.0 »

It was possible to implement first Unicode projects for new installations with version 9.10; with version 10.0, nearly complete Unicode installations are now possible, that is, installations additionally with enaio® client and all administrative components: enaio® enterprise-manager, enaio® administrator, enaio® editor, enaio® editor-for-workflow, enaio® administrator-for-workflow. In so doing, a system can be operated now completely also with the familiar enaio® client, for example, also with Russian object definition or with Greek index data. Even user names can be set up in the national language. Many new object definition languages, which you can use for country-specific naming of object types and fields, are available with this enaio® version.

enaio® capture is the major exception in a Unicode installation that remains. Other administrative limitations: Decentralized user administration and electronic signature are not available.

Only Microsoft SQL Server is supported as a database for Unicode installations.

Unicode installations are only possible as a new installation or as an update to a 9.10 Unicode installation.

enaio® editor

Database field length: Please note that the maximum size for index data fields is now not the same as the maximum column width of the database. Data is filed as UTF-16, so only half the maximum size is available.

Database types: The 'Letters' database type can contain all characters except numbers, surrogates (such as smileys), and punctuation marks. It is now also possible to use '% -*_\' and space characters, unlike in previous versions.

'Uppercase letters' can be any letter or character of the respective language. Number characters are also allowed here as an extension to the 'Letters' database type. Please note that not all languages feature case sensitivity. In this case, the normal set of characters are allowed. 'Numbers' are still only Arabic numbers. Numeric characters of other languages (such as Japanese) are not allowed here.

Internal names: We recommend using a European language such as English as the default language and storing only English texts there. When creating new object types from any number of characters, it is technically not possible to automatically create internal names.

Add-on configurations should always be made using internal names.

Regular expressions: Please note that regular expressions in the world of Unicode are more complex. The expression [a-zA-Z] will not produce any hits for Cyrillic characters/words, for example. привет does not match [a-zA-Z]{6}; however, [а-я]{6} does. There is not always a numeric sorting for the letters of all alphabets, so the letter 'ё' is not included in [а-я]. Certain languages, such as Egyptian hieroglyphs, contain characters with 4 bytes. Since such characters consist of 2 x 2 bytes, the expression '.' (check for one character) does not return a hit, but '..' (check for two characters) does. Please refer to the corresponding literature, some of which is also available online, for more details on using regular expressions.

The test feature in enaio® administrator (Extras > Tools) was changed and features a clearer design now.

Structure tree: Structure trees can be integrated; however, the catalog values can only be ANSI characters.

Catalog add-on: The axaddxmltree.dll catalog add-on cannot be used in Unicode installation. Instead, the new Treeview add-on axaddtreeview.dll is available, for which the first release featured the ability to configure simple catalogs that combine properties of hierarchy and tree catalogs. An upcoming release will integrate further functions of the catalog add-on, such that it can replace it. The new Treeview add-on can also be used in ANSI installations.

VBScript add-on: If scripts are password-protected, then it can only consist of ANSI characters.

Address add-on: The add-on cannot be used in Unicode installations. It will be replaced by a similar add-on in the future.

enaio® administrator

'Data import/export' automatic actions: It is not possible to import and export dBase in Unicode installations. This is because we have decided to deliver the Unicode clients and administration tools as 64-bit Windows applications. A corresponding dBase driver is not available.

The ASCII import/export has been renamed: Text import/export. Data – ANSI or UTF16 – can be imported and exported. For import data, if a BOM specifies the coding, then it will be automatically detected and used correctly. Field length specifications must adhere to the length difference between ASCII and Unicode characters.

Actions to verify the archiving process: The automatic actions of the axactarc.dll library are not available.

'XML TagExtraction' automatic action: Output files are UTF-16 encoded.

COLD import: The automatic action is not available.

enaio® start: Adjustments may be necessary when starting via command line parameters with Unicode characters in the path or in configuration names.

enaio® editor-for-workflow

Variables: Unicode characters cannot be used for variable names since workflow variable names occur in the programming interfaces.

Data Transfer

Data transfers are only possible without user interaction. With specifications for selection in case of multiple hits, data transfers cannot be executed.

Scanning with Kofax

Scanning with Kofax is not possible in enaio® client. Scanning is only possible via the TWAIN interface.