Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!ccut!wnoc-tyo-news!astemgw!icspub!newmars!youki From: youki@newmars.ics.osaka-u.ac.jp (Youki Kadobayashi) Newsgroups: comp.sys.next Subject: Japanese NeXTstep (was Re: Nemacs and NeXT) Message-ID: Date: 28 Jun 91 18:02:20 GMT References: <1991Jun25.084107.15985@agate.berkeley.edu> <1991Jun25.142851.24895@m.cs.uiuc.edu> <1991Jun28.095629.29527@agate.berkeley.edu> Sender: news@icspub.ics.osaka-u.ac.jp Organization: Dept. of Info. and Comp. Sci., Osaka Univ., Japan Lines: 62 In-reply-to: izumi@mindseye.berkeley.edu's message of 28 Jun 91 09:56:29 GMT >>>>> On 28 Jun 91 09:56:29 GMT, izumi@mindseye.berkeley.edu (Izumi Ohzawa) said: > Is 2.1J actually shipping in Japan now? If not, are > you speaking of experiences with a pre-release copy? I'm speaking of both 2.0J beta and 2.1J beta. FYI, some review articles are also available on Japanese magazine "Super ASCII" (all articles are written in Japanese). "Super ASCII" is targeted toward high-end PC and personal workstation users. >> BuildDisk (file system is incompatible) >> >>The incompatibility of file system is serious problem if you have both >>SR 2.1 and SR 2.1J and they are net-less; you can't mount 2.1J's OD on >>2.1. > This is very bad. > Why did they have to mess with the filesystem format? I don't know. Please ask Canon; FAX +81-44-549-5462 for NeXT SE. My guess is that they modified file system to make it 8-bit clean so that users can use Kanji filename. (I never used this feature, but someone from DOSsy world actually did..) > Please elaborate on this. Does it go backward? That is, > can you mount 2.1 OD/floppy on 2.1J system and do read/write? Yes. In other words, 2.1J file system is upward compatible to 2.1. > If so, is the disk written on 2.1J (but initialized on 2.1) > still mountable on 2.1 system? Yes. I've tried this between 1.0 and 2.0J; it worked fine. > How about the compatibility of NetInfo config server/clients. > Can 2.1 NetInfo config server serve 2.1J clients? I can't say anything about this; since we don't have standard 2.1. When we were upgrading cubes to 2.0J, we had mixed configuration (i.e. 1.0 and 2.0J); it seemed to work. From my experience so far, Canon has made no local modification on NetInfo, I think. And some more important topic: 1. Canon should make their Japanese-OS specific documents available via FTP. There are many international-minded guys who wants to support Japanese in their Apps. Of course they must be written in English. 2. All programs which interact with data streams (e.g. files, network streams) should provide a hook for filter; because Japanese standard kanji code is JIS, and alas, Canon adopted EUC as *their* standard. As a result, Japanese NeXTmail converts EUC to JIS each time it sents out mail, and converts JIS to EUC each time it gets incoming mail. More generic mechanism (i.e. NXGetDefaultValue, popen, and NXOpenStream. sample code will be posted soon) would be better, I think. -- Youki Kadobayashi Information Network Architecture Lab. Dept. of Info. and Comp. Sci, Osaka University, Japan