[news.eclipse.tools] Re: Latin1 String on Non-latin1 environment

[Silenio_Quarti@xxxxxxx (Silenio Quarti)]

The problem has been addressed and there is people
working on it. We intend to provide the following
support:

1) API will be provided to set the desired code page when looking up
(creating ) fonts. The default value will be the default code page for the 
platform. Widgets/GCs will display characters based on the code page of
the 
font they are given. That is, the unicode strings are converted based on
the 
code page specified by the font, so each widget/gc will be capable of 
displaying all of the glyphs from a particular codepage, assuming a
matching 
font is available. 

2) We are also investigating whether or not the unicode code page on
Windows 
(1200) can be used. A true Unicode font would allow us to display the full 
unicode character set.

Silenio

Masaki Wakao wrote:

> When I tried to draw A with acute (U+00C1) by GC.drawString() method on
> Windows 2000 Japanese environment, just normal "A" is drawn.

> I looked into the source code and found that Converter.wcsToMbcs() is called
> for string. Actually wcsToMbcs() calles OS.WideCharToMultiByte(). But the
> call convert "A with acute" to just "A" in Japanese environment because
> acute doesn't exist in Japanese charset (=SJIS in windows).

> How can I draw such characters ?
> I know the current Eclipse doesn't support Internationalization. But has
> this issue been addressed already?

> Thanks.