🚀 go-pugleaf

In article <5356@hemuli.tik.vtt.fi>, Markku.Savela@tel.vtt.fi (Markku Savela) writes...
>  With this setup ASCII and Kanji can be mixed without any additional
>escape sequences? Every single code that does not have the 8th bit
>set will be normal ascii, and each consecutive pair of bytes that
>have 8th bit set will be single kanji character.

Yes. You have interpreted the standard correctly.

>  What is the correct procedure to handle error cases, like when
>there is only one byte with 8th bit set? Do I blindly take the
>next byte regardless of the 8th bit setting or ignore this single
>byte?

ISO 2022 (nor T.51, when I last looked) cover error cases.  Usually there's
text such as "this is outside the scope of the standard". 

All of the implementations that I have seen take the next byte and treat the
1xxxxxxx 0xxxxxxx unit as a character and do *something*. Some vendors,
including one with which I'm familiar, actually hide a private character set in
this virtual coded space, therefore the 1xxxxxxx 0xxxxxxx combination is a
valid graphic character.

For general information: There have been proposals to extend ISO 2022 to make
the 1xxxxxxx 0xxxxxxx space a new graphic set into which two-byte character
sets may be designated, validating certain existing implementation, but this
hasn't been approved yet.  ISO JTC1/SC2 will be considering extensions to ISO
2022 at their Plenary this October.  ECMA TC1 is already considering various
proposals to recommend to the ISO subcommittee. 

Tim Lasko, Digital Equipment Corporation, Westford MA  (lasko@regent.dec.com)
Disclaimer: My opinions are my own; the facts can speak for themselves.