With AQT v7 we have added Unicode support to AQT. This allows AQT to display text from non-European languages such as Chinese, Japanese, Korean, Arabic, Maori etc.
AQT v7 can not be run on Windows 95/98/ME as those versions of Windows do not support Unicode.
This support has been enabled by the following changes to AQT:
By default, Unicode support is enabled within AQT. If you do not use Unicode data in your databases it is recommended that you switch this option off for two reasons:
Unicode support can be enabled / disabled with Unicode Options > Enable Unicode Support.
In addition to Enabling Unicode Support, display of many unicode characters is possible only if the font you are using can display these characters. By default, AQT uses MS Sans Serif font, which displays only some Unicode characters. Courier New displays a wider range of unicode characters; to display a wider range of unicode characters you may need a specialised font.
To use a differerent font, select it in Options > Unicode Options > Font used for Unicode controls. This setting applies to the Text boxes, Combo boxes and List boxes that are used to display values from the database.
In addition to this you may need to change other fonts:
When Enable Unicode Support is selected, AQT will use different set of methods for interfacing to the database:
So far, all databases we have tested against support this unicode interface method (even if the databases themselves don't support unicode). However if you are having trouble accessing your database, disabling unicode support might provide a more reliable interface to the database.
When Enable Unicode Support is selected, all files saved by AQT are scanned for unicode characters. If any unicode characters are found, AQT will save the file in unicode format.
Files saved in unicode format can be read only by external editors that support unicode (such as Notepad). Unicode files are in double-byte format with the first two characters being x'FFFE'.
The Audit files are not saved in unicode format.
If you select append when exporting data, AQT will ignore the Export Data in Unicode format setting and will maintain the existing file format. For instance, if the existing file is non-unicode, all subsequent data will be appended to the file in non-unicode format, even if the data contains unicode characters. It is not possible to mix the character encoding within a file.
When Unicode support is enabled, CLOBs written to files (using the Options > LOB Options > Send to files option) will be written as unicode files.
In the demo database AQTDEMO is a table unicode_table containining Unicode data. Displaying this table is a good test of whether unicode display is working on your PC.
Unless you have a specialised keyboard, unicode characters can be created with:
Current limitations are:
Not all databases support Unicode data, and the degree to which they support unicode varies from one database to another. In the following topics we describe how particular databases support unicode.