🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Thread View: comp.protocols.iso
2 messages
2 total messages Started by Markku Savela Mon, 28 Jan 1991 13:12
CCITT T.51 (ISO2022?) and multiple-byte codes designated to GR/GL?
#1061
Author: Markku Savela
Date: Mon, 28 Jan 1991 13:12
21 lines
1449 bytes
  Have I understood the standard right? Assuming the following in
8-bit environment:

   1) I have designated single byte code set (like normal "ASCII")
      into G0 and invoked it into GL with LS0.
   2) I have designated multi-byte code set (like JISC 6226 (kanji))
      into G1 and invoked it into GR with LS1R. 

  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.

  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?
--
Markku Savela (savela@tel.vtt.fi), Technical Research Centre of Finland
Telecommunications Laboratory, Otakaari 7 B, SF-02150 ESPOO, Finland
Re: CCITT T.51 (ISO2022?) and multiple-byte codes designated to GR/GL?
#1070
Author: Kiyo Inaba
Date: Tue, 29 Jan 1991 15:54
31 lines
1865 bytes
In article <5356@hemuli.tik.vtt.fi> savela@tel.vtt.fi (Markku Savela) writes:
#
#  Have I understood the standard right? Assuming the following in
#8-bit environment:
#
#   1) I have designated single byte code set (like normal "ASCII")
#      into G0 and invoked it into GL with LS0.
#   2) I have designated multi-byte code set (like JISC 6226 (kanji))
#      into G1 and invoked it into GR with LS1R. 
#
#  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.

Unfortunately, I don't have 2022 in hand, refering JIS X0202 (which
is Japanese translation of 2022), this interpretation is correct.

#  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?

According to the JIS X0202, 'Error recovery for transmitting incorrect
multi byte character set is not defined in this standard'.
But I usually, just get two byte even if the next byte's MSB is set to
0. 

BTW, JISC 6226 became JIS X0208 several years ago.

Kiyo Inaba
Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads