in reply to Re^2: Once again, Kakasi
in thread Once again, Kakasi

"FYI $str holds an EUC encoded kanji. Coincidentally, so does $jpn and $nstr."

Yes... "is that good or is it whack?" :-) What, exactly is the problem: i.e. what do you expect, and in what way does the problemgram fail to fulfill your expectations? I note that you are explicitly asking for euc input AND output.

Please also use [id://XXXXX] notations to make a link to your previous question, which appears to have some useful answers already, so it would also help if you explained why those answers don't work for you.

update: By the way, by the description in your previous node, I would guess you want something equivalent to 

> kakasi -w -JH -i euc -o euc

[download]
which does all kinds of funny things to your input $str, but since I run a unicode terminal and don't know japanese, that's about as far as I can help you with the specific options. Running kakasi directly from the commandline seems to be a quicker way of trying out the options, though.

"What should it profit a man, if he should win a flame war, yet lose his cool?"

Replies are listed 'Best First'.
Re^4: Once again, Kakasi
by GaijinPunch (Pilgrim) on Aug 01, 2005 at 04:01 UTC
    "Yes... "is that good or is it whack?" :-) What, exactly is the problem: "

    Obviously, it is whack. As stated in the other thread the main objective of the program is to take a kanji and break it down phonetically into hiragana or katakana, inputting an EUC-encoded kanji and receiving the exact same EUC-encoded kanji in the output is (I falsely assumed obviously) not good. I understand now though that if you're browser isn't set to EUC encoding you might not see what the character holds.

    "which appears to have some useful answers already"
    Not really. I understand that I miss encoded the post so after my initial post, it might've been hard to understand that kakasi was returning the exact same thing it was given... even though I typed it in there. I think I did a fairly good job of explaining that in my reply.

    The only other reply was given by lestrrat, which didn't tell me much. I guess I need to go out of my way to point out what strings are encoded in what.

    And BTW - I used Text::Chasen and solved my issue completely. Thanks for everyone's time.
[reply]
      I guess I need to go out of my way to point out...

      Exactly. (Funny thing, I didn't get anything that looked like Japanese Kanji on that previous OP until I set my browser to Shift-JIS -- and of course, I had no way of knowing whether I was looking at the intended Japanese characters.)

      Then there's the sad but unavoidable fact that, in this international community of Perl programmers, relatively few understand what it means to convert from Kanji to Katakana or Hiragana. So you would need to go out of your way a bit on that as well, to explain what the expected output should have been.

      Text::Kakasi looks like it might be useful (notice that I used [cpan://Text::Kakasi] in my post to make that link), and I'll remember it the next time I need to do something with Japanese (I hope it'll work for me better than it did for you); but I think I can speak for a lot of monks when I say I never heard of it before your post.

      Now, you say your problem is solved, but I'm still puzzled. What is "Text::Chasen"? I looked for it on CPAN but found nothing by that name.

[reply]

In Section Seekers of Perl Wisdom