fbpx
This site uses cookies to offer you a better browsing experience. Find out more on how we use cookies and how you can opt out. Accept
PACE Suite - Application Packaging & Virtualization Software
Request a trial Get a quote Become a partner
Request a demo of PACE Suite now We will get in touch with you right away to schedule a convenient time for your 1-on-1 demo with one of our experts.
I have read and agree to the Privacy Policy
Request a quote Please fill in this quick form and we will send you a free quote shortly.
License *
 Freelancer Enterprise Service Provider
I have read and agree to the Privacy Policy
Request a quote Please fill in this quick form and we will send you a free quote shortly.
License *
 Freelancer Enterprise Service Provider
I have read and agree to the Privacy Policy
Request a call Please fill in this quick form and we will call you back shortly.
I have read and agree to the Privacy Policy
Contact Support Please fill in this quick form to contact our support.
I have read and agree to the Privacy Policy
Subscribe to our Newsletter Be among the first to receive our updates! Fill in this quick form to join the list of subscribers.
Send an email to Tetiana Botanevych Please fill in this quick form to contact our expert directly.
I have read and agree to the Privacy Policy

Special and non-latin characters support comes to PACE Suite

Most of the application packaging community is well aware that Windows Installers store names of files, registry entries and other resources to the database tables as string values. The Code Page of a database defines how to encode these string values.

If you manually set the right Code Page prior to adding any localization information, everything works fine. However, if you create a multi-language package and try to put, for instance, two files with extended characters of different languages into a single package, you will run into a problem. Neither neutral nor language specific like 1256 (ANSI – Arabic) Code Page cannot be used in this case, giving headaches to packagers working in countries were languages have non-latin characters (in other words, most of the world!)

The latest PACE Suite 5.3.2 solves this issue and builds and saves all MSI packages with the UTF-8 code page of a database. A package with this encoding is capable of installing resources with extended characters of different languages in the titles. You no longer need to set the right Code Page for every package manually.

Please note that UTF-7 and UTF-8 are not officially supported in MSI, because sometimes issues occur in the user interface during installation and de-installation. It all depends on the font you are going to use.