🚀 go-pugleaf

A. wrote:

> Is there any reason for having difficulty with this language (Korean)
> only?

That depends exactly what the problem is.

The 'normal' issue that people run into when translating strings is
character availability and codepages. Most applications only work with
8-bit characters and this means that they can only choose from 256
characters at a time. 256 is way too few to cater for all languages and
so when you configure Windows you tell it what language you want to
work in so that it can select a codepage that contains just those
characters you need.

As an example, my machine in it's normal configuration is incapable of
displaying Korean using 'normal' string and display functions. This is
because it's set up for Western European usage and there are far better
things to put into the codepage (from my POV) than Korean characters :)

The only way to display Korean on my machine at the moment is to use
the Unicode (also known as widestring) output functions. Because these
use 16-bit characters they have a far wide range of characters to
choose from cover most languages in common use today.

Using Unicode is not in itself a guarantee of getting all the
characters you want. It also depends on the font you are using.
Creating a font for 65536 characters takes a lot of time and resources
so most font makers don't bother. They just provide for a few codepages
(usually those based around Latin or Cyrillic) and call it a day. If
you are using a recent or updated version of Windows then you will
probably have the Arial Unicode font installed and this includes a very
wide range of characters.

However...

Normally this entire problem manifests itself as either '?'s appearing
in the string or else '|'s. IOW you don't get the string you want but
you do get /a/ string. We have played with this whole area extensively
over the last year or so and are now proficient at dealing with
codepage issues.

In all that name we never encountered a situation where the VCL failed
to respond to a caption change. The resulting caption might consist
mostly of '?'s or '|'s but it did change.

If you were using a third party tool or library to make the caption
change then I'd suspect that tool or library was spotting that the
codepage didn't support Korean and was choosing to do nothing rather
than return a string full of '?'s or '|'s.

-- 
Andrue Cope [TeamB]
[Bicester, Uk]
http://info.borland.com/newsgroups/guide.html