Character Set Conversion

Top  Previous  Next

Overview

For many reasons Xbase++ programs must deal with different character sets. DBF tables usually contain Oem data. Old programs were written for Dos using the Oem character set. Windows requires parameters to its functions to be either in Ansi or Unicode character set. COM technology supports only Unicode character sets.

 

The effective Cockpit application character set is either Oem or Ansi (depending on the SetCX setting).

The available character set conversion functions are

SetCX

GetECX

SetOemConversion (obsolete)

ConvTextIn

ConvTextOut

ConvWTextIn

ConvWTextOut

Ansi2Unicode

Unicode2Ansi