Reference | Help | Introduction | Slide Show | Class Hierarchy | InterClient
PREV | NEXT | FRAMES | NO FRAMES |  |

### InterClient Character Set Support

The following character set encodings may be specified using the `charSet` connection property when obtaining connections from the driver. Also see CharacterEncodings and ConnectionProperties.setCharacterEncoding in the InterClient Reference.

IANA Encoding (`charSet`) | InterBase Character Set Name
8859_1 | ISO8859_1
Big5 | BIG_5
Cp1250 | WIN1250
Cp1251 | WIN1251
Cp1252 | WIN1252
Cp1253 | WIN1253
Cp1254 | WIN1254
Cp437 | DOS437
Cp850 | DOS850
Cp852 | DOS852
Cp857 | DOS857
Cp860 | DOS860
Cp861 | DOS861
Cp863 | DOS863
Cp865 | DOS865
EUCJIS | EUCJ_0208
GB2312 | GB_2312
KSC5601 | KSC_5601
SJIS | SJIS_0208
UTF8 | UNICODE_FSS

If an encoding is not specified using the `charSet` connection property, an attachment will use the InterBase default `NONE` character set. The `NONE` character set attachment specifies that data is processed as is with no conversions. The default encoding for your locale is not used. Because conversions are not performed and no particular encoding is enforced, all SQL and SQL data is interpreted byte-wise as the low order byte of a Java Unicode 2-byte character. Therefore, all SQL and character data should be restricted to ASCII when connecting to an InterBase server using the default `NONE` character set.

À bientôt.

Reference | Help | Introduction | Slide Show | Class Hierarchy | InterClient
PREV | NEXT | FRAMES | NO FRAMES |  |

Send comments or suggestions to interclient@interbase.com