On Thu, Jan 10, 2002 at 10:57:59AM +0900, Dan Kogai wrote: > Hi jhi, > > My name is Dan Kogai. I am a writer of Jcode.pm, which converts from
Yes, I've heard of you :-) (I'm CCing Nick Ing-Simmons, the original author of Encode, and SADAHIRO Tomoyuki, who has worked on it a little bit, and who might also know some Japanese :-) > various Japanese charset to others. With the advent of Encode module > that comes with Perl 5.7.2 and up, I finally though that the role of > Jcode, Jcode to r.i.p. When I tested the module however, I found it was > far from it. Rather, I believe I can help in great deal with the > current implementation. First off, I'm really thankful that you took a careful look the current state of Encode as per Japanese encodings. I won't (can't) comment on much the Encode details, since I'm pretty unfamiliar the design or the implementation, all I've done is to add some (eight-bit) encodings many moons ago. I'm hoping Nick and Sadahiro will join in and comment. > #4; Conclusion > > I think I have grokked both in fullness to implement > Encode::Japanese. I know you don't grok Japanese very well (which you How about "not at all"? :-) > don't have to; I don't grok Finnish either :). It takes more than a > simple table lookup to handle Japanese well enough to make native > grokkers happy. It has to automatically detect which of many charsets > are used, it has to be robust, and most of all, it must be documented in > Japanese :) I can do all that. Excellent. > I believe Jcode must someday cease to exist as Camel starts to grok > Japanese. With Encode module the day is sooner than I expected and I > want to help you make my day. > If I submit Encode::Japanese, are you going to merge it standard > module? Definitely, yes. Implementation-wise you'll have to discuss with Nick since whatever we use should work with the Tcl/Tk scheme (hence the name Encode::Tcl, as you no doubt guessed.) Sadahiro can comment on both Encode and Japanese. > Dan the Man with Too Many Charsets to Deal With Sounds good :-) One nit, though: the sooner you can start *and* finish the task, the better. For delivery dates, I would prefer "yesterday"... Why? I want to release a 5.7.3 really, REALLY soon now, so that module authors and users can test their stuff against it, so that 5.8.0 can be released in a few months. So I hope you haven't got any previous commitmentents, like a day job or a family :-) -- $jhi++; # http://www.iki.fi/jhi/ # There is this special biologist word we use for 'stable'. # It is 'dead'. -- Jack Cohen
