NLS Support in UD6 XML files

If you are using Uniface with 'national language characters', like Hebrew, Central European, or Western European, UD6 is the only solution to getting your national text into XML files.

The UD6/CMtool Driver provides the best place to keep your source code. Because it is a database, it is fast and simple to use with Uniface. Because this database stores the Uniface source code as discreet text files, it allows you to use any version control tool, configuration management tool or editor.

But Uniface stores national characters encoded?

Whilst Uniface can store national character sets, it stores them in an unreadable format. When you look at your source code for Hebrew messages stored in Oracle or Solid, or export it using Uniface 7.2.05/6 XML format, then the resulsts are of little use:

The UD6/CMtool Driver understands the Uniface encoding and stores your source code in the character set you intended: your own.

And since the March Hare UD6/CMtool Driver is standards compliant then you can even view your Hebrew or other national language source code in Internet Explorer:


The Advantage

This makes your life easier since you can get genuine difference reports between versions of messages or form components that includes your message and screen text in an understandable format - your own langauge.

You can even edit your source code in your own editor.

Unicode and UTF-8

UD6 does not currently support storing UTF-8 Unicode characters in XML files. Uniface 10 can generate UTF-8 however UD6 will translate these to the specified codepage to maintain compatibility with Uniface 7/8/9.

You can use

.gitattributes files
to configure Git and GitHub Desktop to recognise these files.

A future version of UD6 may provide native support for UTF-8 XML files.

Read more about Uniface Version Control

Further Reading

How to: Set up National Language Support with UD6

$Revision$ $Date$[go to top]