Re: Mule autodetection is crap

KY> Only Japanese people might be receiving a benefit from the KY> autodetection. It's worse than that. There are several verified ways that 21.4-style autodetection can destroy data. GNU Emacs fixed many of those problems with "safe-charsets", but by the time that happened Ben's rewrite was well underway. And also the GNU Emacs safe-charset implementation is not very satisfactory in some ways. KY> I cannot bear the thought of being lost the feature. Well, as I suppose you know, what Ben has is mind is a statistical detector that (eg) can distinguish EUC-JP from EUC-TW or EUC-KR (although the really important case is the ISO-8859-X mess and the various non-conforming sets like KOI8 and the Windows 12xx sets). But the design is completely new, so we need to retune it. Also there seem to be some bugs in coding priorities. KY> I heard it also before. I can believe all the other work of KY> him is extremely important for the future of XEmacs. But I KY> wish he don't leave Japanese XEmacs fan in the lurch. Well, what we really need to do is find a way to get more participation from others. Right now it's very hard because "new Mule" is hardly documented and very incomplete, but we appreciate efforts from you and Ueno-san and Ikiuo-san. Also there are some discussions with Morioka-san; I don't think we can "unify" XEmacs with UTF-2000 yet[1], but perhaps we can bring them a lot closer. Pretty soon XEmacs 21.4 will be stable, Vin will take care of it, and I'll be able to work more on 21.5 and on "infrastructure" (== helping people who don't have time to be "core team" to contribute), too. Footnotes: [1] And also I think Morioka-san still hopes for UTF-2000 for GNU Emacs. -- Institute of Policy and Planning Sciences http://turnbull.sk.tsukuba.ac.jp University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN Ask not how you can "do" free software business; ask what your business can "do for" free software.