皆さんへ、
松木＠東京家政大です。以下はTurnerの返事です。Aliasの部分を書き直す
努力をするみたいです。
------- Forwarded Message
Date: Mon, 10 Apr 2000 15:43:42 +0100 (BST)
From: Stephen Turner <S.R.E.Turner@statslab.cam.ac.uk>
Reply-To: Stephen Turner <sret1@cam.ac.uk>
To: Takayuki Matsuki <matsuki@tokyo-kasei.ac.jp>
Subject: Re: Analog 4.04
In-Reply-To: <200004081511.AAA14740@pegasus.tokyo-kasei.ac.jp>
Message-ID: <Pine.LNX.3.96.1000410154210.503F-100000@gamma.statslab.cam.ac.uk>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Content-Length: 1482
X-atmail-flags: Unseen
On Sun, 9 Apr 2000, Takayuki Matsuki wrote:
> Dear Dr. Turner,
>
> Would you mind to answer the following questions?
>
> I understand why I get an error if I use ISO-2022-JIS code since
>
> 1) The words in the section "In the section "Some special phrases for
> particular reports", you need to change (single byte) $ to $$" are
> treated specially using confline() function.
>
> 2) It goes to configalias() and then to aliastocount() function to
> analyze op->outopts.lngstr[unresolved_], etc.
>
> 3) The function aliastocount() recovers only $$[1-9] to $[1-9]. However
> ISO-2022-JIS code includes, e.g., $B as a character in this section.
>
> Why do you treat these terms specially using confline() function?
> Why can't you use these terms as it is?
>
A good question. It's basically just for speed. But I'll look at it again.
Maybe these shouldn't be special.
> In Japanese Analog ML, there are many discussions on the problem in
> analog. We have concluded temporarily that as long as we use EUC-JP code,
> there is no serious problem and hence we support only EUC code for a
> while.
OK, no problem. Thank you very much for trying. I'm sorry to waste your time
with it. I'll have another look at it myself too.
Thank you again.
Yours,
--
Stephen Turner http://www.statslab.cam.ac.uk/~sret1/
Statistical Laboratory, 16 Mill Lane, Cambridge CB2 1SB, England
"8th March 2000. National No Smoking Day. Ash Wednesday." (On a calendar)
------- End of Forwarded Message