From: ogawa@sm.sony.co.jp (Masato Ogawa)
Newsgroups: comp.sys.mac.comm
Subject: Re: KanjiTalk / NIFTY-Serve question
Date: 1 Sep 92 10:50:43 GMT
	<OGAWA.92Aug28181020@actor.sm.sony.co.jp>
	<1992Aug28.163721.11854@leland.Stanford.EDU>
Organization: Super-Micro Group, Sony Corporation, Tokyo, Japan

In article <1992Aug28.163721.11854@leland.Stanford.EDU> sigmond@leland.Stanford.EDU (Steve Sigmond) writes:
   In article <OGAWA.92Aug28181020@actor.sm.sony.co.jp> ogawa@sm.sony.co.jp (Masato Ogawa) writes:
   >In article <1992Aug27.002237.13903@leland.Stanford.EDU> sigmond@leland.Stanford.EDU (Steve Sigmond) writes:
   >>    1. When I run NinjaTerm in 8 bit, no parity mode with a generic 2400
   >>    modem, I can usually* get the modem to echo correct Kanji.
   >>    For example, if 
   >>    I type "ryo", convert to kanji, and hit return, the terminal window
   >>    echoes the correct character. However, this does not work for all
   >>    characters. 
   >>    If I type "a", and then hit return, the character echoed back
   >>    is not the 
   >>    hiragana for "a". The errors seem sensitive to settings such
   >>    as number of 
   >>    stop bits, local echo, etc. I am using Shift-JIS mode in both
   >>    NinjaTerm 
   >>    and the KanjiTalk control panel (I think!)
   >
   >completely out of my imagination... But give us the information about
   >to what, do you connect this NinajTerm&Macintosh? The echoed
   >characters are sent "BACK" by the "HOST", not your Macintosh. So the
   >problem often resides on the HOST setting. From my experiences, such
   >phenomena are caused by the "parity" setting of somewhere in the
   >communication path.  As you said, your Mac & NinjaTerm must be OK. How
   >about your "HOST"? It must be set as 7bit even parity ? (in the case of
   >accidentally matches a parity bit for lower 7 bit of a character in
   >SJIS and MSB of that character, you get the right echo back. Unlacky
   >case causes bargabe echo back for a character, as you see). You should
   >have the HOST set as 8-N-1, too.
   >

   I was referring to the interaction between the modem and the computer
   acting strangely. Before I was able to connect to NIFTY, I tried entering
   some Japanese characters and then sending them out the serial port while
   offline. What appeared in the NinjaTerm window did not always match what
   I sent out. But this isn't too surprising. When connected to NIFTY
   via CIS (8 bit no parity, as suggested), everything seems to work.


 >>    stop bits, local echo, etc. I am using Shift-JIS mode in both

local echo usually violates the Kanji, because a Kanji character
consists of 2 byte (or more). the inputed character itself which should be
displayed on the screen and the echoed character are mixed in bytes in
the order of arrival.
I can reproduce this phenomenon on my system (using NinjaTerm). But I
couldn't reproduce it by changing "stop bits". Usually, typing in /
pasting in a Kanji (Japanese) character at the same time when displaying
a character from HOST (modem) causes garbages because of mixed bytes.
But this is only on display side. Typed characters are sent correctly.
But in most cases, "logged" file has the garbage as displayed. Except for
displaying garbage, this "disorder of byte (character)" can be
happened for Roman characters as the same manner.


--
==========================================================================
Masato Ogawa					Sony corp.

ogawa@sm.sony.co.jp				Tokyo, Japan
==========================================================================