Carlos,

>I was unhappy when I wrote font. Really I wanted to write Charset.
>In XbpCrt() I use Courier New. Its default charset is OEM.

The Character Set (CharSet) setting is a thread-local setting, and the 
default setting for a thread depends on several things. On Windows, the 
default setting (for the Main thread) is ANSI for GUI (and Hybrid) 
applications and OEM for Console (VIO) applications. Additional threads 
inherit the current CharSet setting of the thread from which they are 
started. You can change that setting at any time, though!

Xbase++ does automatic (implicit) OEM to ANSI and ANSI to OEM conversions, 
depending on the thread's current CharSet setting and the input source and 
output target. Additionally, you can manually (explicitly) convert from OEM 
to ANSI using the ConvToAnsiCP() function and from ANSI to OEM using the 
ConvToOemCP() function.

Besides the above, you can use any (available) Windows font for any of the 
XbaseParts, including XbpCRT() dialogs. If you select an OEM font, you can 
usually only show OEM characters. If you select an ANSI font, you can often 
show OEM characters besides ANSI characters, if you select the correct Code 
Page. Which characters (glyphs/symbols) can be displayed depends on the 
selected font (and the selected Code Page of the selected font).

All this can be found in the docs under "SET CHARSET", "XbpFont:codePage",
and related topics.

Please see also the attached demo program that shows the effects of changing 
a Font's Code Page as well as switching the current CharSet setting.

I hope that clarifies it sufficiently.

Andreas

Andreas Gehrs-Pahl
Absolute Software, LLC

phone: (989) 723-9927
email: Andreas@AbsoluteSoftwareLLC.com
web:   http://www.AbsoluteSoftwareLLC.com
[F]:   https://www.facebook.com/AbsoluteSoftwareLLC