Pretty crazy that we're closer to 2030, than we are 2005. Where did the time go!
0 Members and 1 Guest are viewing this topic.
I'd personally do as Joe suggests
You might be right about that, Joe.
And on top of that, none of us have any clue what Korean is supposed to look like. Well, maybe Ergot knows.
Quote from: Joe on February 14, 2008, 01:40:02 pmAnd on top of that, none of us have any clue what Korean is supposed to look like. Well, maybe Ergot knows.If you open the link that the poster supplied, you will see some Korean.
Quote from: igimo on February 14, 2008, 06:00:21 pmQuote from: Joe on February 14, 2008, 01:40:02 pmAnd on top of that, none of us have any clue what Korean is supposed to look like. Well, maybe Ergot knows.If you open the link that the poster supplied, you will see some Korean.Are you sure? I gathered from what the guy said that that's a picture of what Korean -doesn't- look like.
Five characters is hardly enough to take on such a large endeavor.
Looks like a UTF8 encoding issue.Dealing with encoding in Java sucks a lot. It tries to auto-convert in the new String(byte[]) constructor, but it won't take a hint as to what it's encoded as, which makes it very difficult to work around.