Lotus Multi-Byte Character Set

Created around the same time and addressing some of the same problems, LMBCS could be viewed as parallel development and possible alternative to Unicode. For maximum compatibility, later issues of LMBCS incorporate UTF-16 as a subset.

Commercially, LMBCS was first introduced as the default character set of Lotus 1-2-3 Release 3 for DOS in March 1989 and Lotus 1-2-3/G Release 1 for OS/2 in 1990 replacing the 8-bit Lotus International Character Set (LICS) and ASCII used in earlier DOS-only versions of Lotus 1-2-3 and Symphony. LMBCS is also used in IBM/Lotus SmartSuite, Notes and Domino, as well as in a number of third-party products.

LMBCS encodes the characters required for languages using the Latin, Arabic, Hebrew, Greek and Cyrillic scripts, the Thai, Chinese, Japanese and Korean writing systems, and technical symbols.

Technically, LMBCS is a lead-byte encoding where code point 00_hex as well as code points 20_hex (32) to 7F_hex (127) are identical to ASCII (as well as to LICS).

Code point 00_hex is always treated as NUL character to ensure maximum code compatibility with existing software libraries dealing with null-terminated strings in many programming languages such as C. This applies even to the UTF-16be codes, where code words with the form xx00_hex are mapped to private-use codes with the form F6xx_hex during encoding in order to avoid the use of NUL bytes, and to escaped control characters, where 20_hex is added to the C0 (but not C1) control characters following the 0F_hex lead byte.

Code points 01_hex to 1F_hex, which serve as control codes in ASCII, are used as lead bytes to switch the definition of code points above 7F_hex between several code groups (similar to code pages) and at the same time determine either a single- or multi-byte nature for the corresponding code group.

For example, code group 1 (with group byte 01_hex) is almost identical to the SBCS code page 850, whereas code group 16 (with group byte 10_hex) is similar to the Japanese MBCS code page 932. Multi-byte characters can thus occupy two or three bytes.

In canonical LMBCS, each character starts with its group byte. To reduce the length, in optimized or compressed LMBCS a default code group or optimization group code can be defined on a per application or process basis (ideally chosen according to the highest likelihood of occurrence) and must be communicated to the interpreting code in some way (f.e. by specifying the corresponding "LMBCS-n" name). Thereby, the group byte can be omitted for these characters. Lotus 1-2-3 retrieves the optimization group code from the file header of the corresponding source file, whereas for Lotus Notes the optimization group code is fixed to be always 01_hex.

Without prefix byte the code points 32 (20_hex) to 127 (7F_hex) are interpreted as follows (corresponding to LMBCS codes 32 to 127):

Group 1

LMBCS group 1 code points 128 (80_hex) to 255 (FF_hex) are identical to the corresponding code points in code page 850 (DOS Latin-1), whereas code points 1 (01_hex) to 127 (7F_hex) are defined according to the following exception list (corresponding to LMBCS codes 256 to 383):

Group 2

LMBCS group 2 code points 128 (80_hex) to 255 (FF_hex) are identical to the corresponding code points in code page 851 (DOS Greek), whereas code points 1 (01_hex) to 127 (7F_hex) are defined according to the following exception list:

Group 6

LMBCS group 6 code points 128 (80_hex) to 255 (FF_hex) are identical to the corresponding code points in code page 852 (DOS Latin-2), whereas code points 1 (01_hex) to 127 (7F_hex) are defined according to the following exception list:

• Compose key
• GB 18030
• Standard Compression Scheme for Unicode (SCSU)
• Symbol (typeface)
• Xerox Character Code Standard (XCCS)