Return to BSD News archive
Received: by minnie.vk1xwt.ampr.org with NNTP id AA6218 ; Wed, 06 Jan 93 03:10:15 EST Path: sserve!manuel.anu.edu.au!munnari.oz.au!uunet!zaphod.mps.ohio-state.edu!darwin.sura.net!sgiblab!nec-gw!nec-tyo!wnoc-tyo-news!cs.titech!titccy.cc.titech!necom830!mohta From: mohta@necom830.cc.titech.ac.jp (Masataka Ohta) Newsgroups: comp.unix.bsd Subject: Constructive discussion (was Re: Dumb Terry) Keywords: Han Kanji Katakana Hirugana ISO10646 Unicode Codepages Message-ID: <2655@titccy.cc.titech.ac.jp> Date: 8 Jan 93 15:33:22 GMT References: <2628@titccy.cc.titech.ac.jp> <1993Jan7.045612.13244@fcom.cc.utah.edu> <2637@titccy.cc.titech.ac.jp> <1993Jan7.122941.29218@ulrik.uio.no> Sender: news@titccy.cc.titech.ac.jp Organization: Tokyo Institute of Technology Lines: 29 In article <1993Jan7.122941.29218@ulrik.uio.no> toreh@bootes.sds.no (Tore Haraldsen) writes: >... a bunch of bullshit far above the average for this news group. It is >quite interesting to see someone so intent on attacking and with such a >lack of constructive comments ... What? To be construtive, could you show me an way to give files attributes better than Terry? I'd rather be destructive on Vogon suggestions. As for internationalization, I already wrote that ISO 2022 and EUC are better than 10646. Isn't it constructive enough? >Dear Mr. Masataka Ohta, stop this persecution and show us how YOU would >solve the questions rised! Or, if you do not want anything solved at >all, please tell us why! Though ISO 2022 is not a solution, to deny 10646, ISO 2022 is enough. BTW, I have several real solutions at hand. But as the details are not fixed yet and as I can't yet determine what is the best solution, describing them to deny 10646 will make the current chaos (I don't think it discussion) worse. Internationalization is a really difficult problem. Be careful not to jump to "the solution", lest you should create another useless solution like 10646/Unicode. Masataka Ohta