A code table defines a character set (Coded Character Set, CCS for short) and the coding of these characters in the file. A CCS is assigned a name of up to 8 characters in length via which the CCS can be addressed.
As FT administrator, you can use the ftmodo -ccs command to set a standard CCS for openFT. In addition, you are still able to set your own 8-bit CCS.
The standard CCS is used for all FT requests. However, users can set a different CCS in the ft-/ncopy request and in the openFT Editor.
The following CCSs are supplied with openFT as standard:
Name of the CCS | Meaning |
ISO88591 to ISO8859B and | for the ASCII tables ISO8859-1 to ISO8859-11 and |
ISO646 | for the international 7-bit ASCII table |
ISO646DE | for the German 7-bit ASCII reference version |
EDF041 to EDF04A, EDF04D | for the EBCDIC tables DF04-1 to DF04-10, DF04-13 and |
EDF03IRV | for the international 7-bit EBCDIC table defined by FSC |
EDF03DRV | for the German 7-bit EBCDIC table defined by FSC |
UTF16 | for Unicode with UTF-16 coding (platform-specific endian) |
UTF8 | for Unicode with UTF-8 coding |
UTFE | for Unicode with the UTF-E coding |
UTF16LE | for Unicode with UTF-16 coding (little-endian) |
UTF16BE | for Unicode with UTF-16 coding (big-endian) |
UTFEIBM | for Unicode with the UTF-EBCDIC coding defined by IBM |
IBM037 | for the US/Canada EBCDIC character set defined by IBM |
IBM273 | for the German/Austria EBCDIC character set defined by |
IBM500 | for the International EBCDIC character set defined by IBM |
IBM1047 | for the OpenExtensions EBCDIC character set defined by |
CP437 | for the English (USA) OEM character set defined by |
CP720 | for the Arabic OEM character set character set defined by |
CP737 | for the Greek OEM character set defined by Microsoft |
CP775 | for the Lettish OEM character set defined by Microsoft |
CP850 | for the Western Europe OEM character set defined by |
CP852 | for the Polish OEM character set defined by Microsoft |
CP855 | for the Serbian OEM character set defined by Microsoft |
CP857 | for the Turkish OEM character set defined by Microsoft |
CP858 | for the OEM character set CP850 with the Euro symbol |
CP862 | for the Hebrew OEM character set defined by Microsoft |
CP866 | for the Cyrillic OEM character set defined by Microsoft |
CP874 | for the Thai Windows character set defined by Microsoft |
CP1250 | for the Central Europe Windows character set defined by |
CP1251 | for the Cyrillic Windows character set defined by Microsoft |
CP1252 | for the Western Europe Windows character set with the |
CP1253 | for the Greek Windows character set defined by Microsoft |
CP1254 | for the Turkish Windows character set defined by |
CP1255 | for the Hebrew Windows character set defined by |
CP1256 | for the Arabic Windows character set defined by Microsoft |
CP1257 | for the Baltic Windows character set defined by Microsoft |
CP1258 | for the Vietnamese Windows character set defined by |
Creating a user-defined CCS
If you are an openFT administrator, you can create your own CCS (Coded Character Set). To do this, you must create a text file which is stored in the sysccs subfolder of the openFT instance. The CCS name corresponds to the name of this file.
The text file must have the following structure:
The first line starts with a '#'.
The second character is a blank. The remainder of the line contains a comment which characterizes the code contained.
In Unix systems, the file name must be written completely in lower case.The second line contains an alphabetic character which can at present only have the value 'S'. 'S' stands for single-byte code, i.e. a character is always 1 byte in length.
The third line contains three numbers.
The first number is a 4-digit hexadecimal number. This defines the substitution character to be used if a Unicode character cannot be mapped to the code.
The second number is currently always '0'.
The third number is a decimal number which defines the number of code pages that follow. It currently always has the value '1'.
The following lines define the code pages and have the following structure:
The first of these lines contains the number of the code page in the form of a twodigit hexadecimal number.
All the subsequent lines contain the mapping of the characters for the codes to be defined to UTF-16 in the form of a 4-digit hexadecimal number. The values are arranged in 16 lines, each of which contains 16 4-digit hexadecimal numbers with no spaces.
Example for ISO8859-15 (Western Europe with Euro symbol)
# Encoding file: iso8859-15, single-byte S 003F 0 1 00 0000000100020003000400050006000700080009000A000B000C000D000E000F 0010001100120013001400150016001700180019001A001B001C001D001E001F 0020002100220023002400250026002700280029002A002B002C002D002E002F 0030003100320033003400350036003700380039003A003B003C003D003E003F 0040004100420043004400450046004700480049004A004B004C004D004E004F 0050005100520053005400550056005700580059005A005B005C005D005E005F 0060006100620063006400650066006700680069006A006B006C006D006E006F 0070007100720073007400750076007700780079007A007B007C007D007E007F 0080008100820083008400850086008700880089008A008B008C008D008E008F 0090009100920093009400950096009700980099009A009B009C009D009E009F 00A000A100A200A320AC00A5016000A7016100A900AA00AB00AC00AD00AE00AF 00B000B100B200B3017D00B500B600B7017E00B900BA00BB01520153017800BF 00C000C100C200C300C400C500C600C700C800C900CA00CB00CC00CD00CE00CF 00D000D100D200D300D400D500D600D700D800D900DA00DB00DC00DD00DE00DF 00E000E100E200E300E400E500E600E700E800E900EA00EB00EC00ED00EE00EF 00F000F100F200F300F400F500F600F700F800F900FA00FB00FC00FD00FE00FF