in reply to Once again, Kakasi

Oh for [deity of choice]'s sake. You ignore all the suggestions in the previous thread, start a new thread, then in the new thread tell us exactly zero about how the code is now failing, what output it produces, what output you expect, what results you had from trying people's previous suggestions, etc etc.

Dave.

Replies are listed 'Best First'.
Re^2: Once again, Kakasi
by GaijinPunch (Pilgrim) on Aug 01, 2005 at 01:15 UTC
    Did you read my whole post?

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

    In other words, the output is the exact same as the input. I needed people to see the thread, hence I didn't reply to the old one. Doesn't push it to the top AFAIK. Sorry if that got your panties all in a bunch.
      "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
      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.

        "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.
Re^2: Once again, Kakasi
by Anonymous Monk on Nov 09, 2009 at 04:54 UTC
    I'm using Kakasi in conjunction with JMdict from (sorry) PHP here: http://kotoba.tremicom.com/