Each application file which contains text in some form (.inf, .pbk and .fmt files), is encoded in a specific character set, although the average computer user is normally not aware of this. The character set determines which characters can be used in the text, and implicitly determines the compatibility of the file with all kinds of software. If your application files still have a DOS or ISO-Latin encoding and you'd like to start using special characters from Unicode (UTF8) in text properties of these files, then you can use the Application character set conversion tool for this conversion.

Change the encoding of your application structure and settings files

The Encoding property of application structure and settings files, displays the type of character set used to encode texts that you provide for properties of the object/file. Different files may have a different encoding, but to prevent confusion about what characters can be used where, it is of course best if all structure and settings files use the same character set. You can change the setting for an individual file manually, if desired.

You can change the encoding of database structures (.inf files), application structures (.pbk files) and screens (.fmt files) also simultaneously, with the Application character set conversion tool in Axiell Designer. (The currently used character set of a .pbk, .inf or .fmt file is displayed on the Properties tab under Encoding when you select such a file in the Application browser.)
Start the Application character set conversion tool by choosing Tools > Application character set conversion in the main Axiell Designer window. With this tool you can convert your application files (only .pbk, .inf, and .fmt files) to any of three character sets. But probably you will only use it to convert a DOS (OEM) application to either an ISO-Latin (ANSI) or Unicode (UTF8) one, or to convert an ISO-Latin application to Unicode. Note that this tool only converts the application and database structure files, not your SQL database tables and data.

You only need to consider using this tool if your language has accented or other special characters and you need to use those in for instance the labels of fields, or in title bars, while the current encoding doesn't allow you to do that. Once converted to another (expanded) character set, you'll be able to use its characters in your application setup.

Before converting, make sure you select the proper work folder. Since you probably want the change to affect all your Collections files, you must select your main (copy of an) Axiell folder, and mark the Convert subfolders option in this tool window.