🚀 go-pugleaf

In many cases it may be "good enough" to convert Unicode to MBCS and let the 
VCL control display the text. It all depends on how internalional you need 
to make your application. But keep the following in mind:

1. Converting from Unicode to MBCS requires a codepage. Codepages are 
normally set by your locale/regional settings in Windows. If your codepage 
does not support the Unicode characters in a given string, things will not 
work right.
2. Only Unicode controls can display characters from multiple codepages at 
the same time (like Japanese and Korean in the same text string)
3. The font your using must be contain the characters your trying to 
display. WinXP makes this easier with its builtin font substitution.

This is only the tip of the iceberg when dealing with internationalization.

For the VCL, you may want to check out the Tnt Unicode controls.

HTH,
Mark Finkle

"Peter Van Hove" <Will_Bounce_So_Use_My_First_Name@Smart-Projects.net> wrote 
in message news:422f1b8f$1@newsgroups.borland.com...
> Hi,
>
> My app internally stores unicode strings that it reads directly from CD.
> To display it, the widechar strings are handed to VCL controls that 
> convert it to MBCS
> (E.g. ListView, TreeView controls)
> I suppose this is the best method for Win95, Win98 etc.
> However I wonder if this is the best approach for modern OS like WinXP ?
> Fact of the matter is that if I use a (e.g.) US Windows and want to 
> display Arabic texts like that I am running into problems UNLESS the 
> proper Arabic support is installed on the OS.
>
> How can one work around that ?
> Are there VCL controls that use unicode and interface with the unicode 
> stuff on XP ?
>