From keld@dkuug.dk Sat Feb 29 18:08:44 1992 Received: by dkuug.dk (5.64+/8+bit/IDA-1.2.8) id AA00805; Sat, 29 Feb 92 18:08:44 +0100 Date: Sat, 29 Feb 92 18:08:44 +0100 From: Keld J|rn Simonsen Message-Id: <9202291708.AA00805@dkuug.dk> To: wg15rin@dkuug.dk Subject: SC22 resolution on 10646 X-Charset: ASCII X-Char-Esc: 29 The ISO/IEC JTC1/SC22 resolution 200 is contained in document ISO/IEC JTC1/SC22 N1053, page 15. It was adopted unaminously at the SC22 plenary meeting 1991-09-23/27 in Wien, Austria. Resolution 200: SC22 Liaison Report to SC2 ISO/IEC JTC1/SC22 directs the SC22 secretariat to forward the following liaison statement to SC2. Liaison report from SC22 to SC2. ISO/IEC JTC1/SC22 appreciates the work by SC2 in producing the multi-octet character set standard: ISO/IEC 10646. This standard is considered to become one of the fundamental base standards on which the Programming Language standards should be based. It is with concern that SC22 has noted recent extensive changes to the proposed standard that will affect several Programming Language standards. - SC22 notes that several standards developed in SC22, for example ISO/IEC 9899:1990 (Programming Language C) and ISO/IEC 9945:1990 (POSIX), indicate the end of a multi-byte character string with a NUL octet; and informs SC2 that existing systems based upon the above standards cannot make direct use of a system containing NUL octets. - SC22 brings to the attention of SC2 that it should not be assumed that a single coded character set will be used for coding all character sequences. For the foreseeable future, it is likely that many character sequences will be in IS 646, or conforming to IS 8859. It is essential that future character sets provide an escape sequence to announce the character set used to express the data that follows, IS 2022 for example.