Kanji mangling

[Jamtex]

Why is it that using Japanese (esp Kanji) sometimes works and other times creates situations where it turns into lines of garbage? Sometimes editing text that has Kanji, even if you don't edit the text, creates extra Kanji and garbage...

[Paulo]

You mean on the forum?

[Jamtex]

Er yes. Example $B?4(B$BNn(B$B<v(B$B;&(B$B;U(B$BB@(B$BO:(B$B4](B is a famous game by Time Warner on the Saturn.

[Jamtex]

The third kanji $B<v(B has turned into .... and the second to last kanji $BO:(B turns into [left arrow] $BO:

$B?4(B$BNn(B$B<v(B$B;&(B$B;U(B$BB@(B$BO:(B$B4](B

[Jamtex]

Depending on browser and using encoding (auto or ISO-2022-JP) the above Kanji does turn into complete garbage and all I posted was the name of a Japanese game... if there was an edit button, clicking the text and saving it a few times would spawn several lines of garbage. :)

[GaijinPunch]

問題ない

[GaijinPunch]

I did that one w/ my browser encoding set to ISO-8859-1
Give it a shot.

[Yakumo]

My PC is set to West Europe ISO Windows encoding and have no problem with Kanji or any japanese sites. In fact I'm sure this is the standard default setting for Japanese PCs for some reason.

Yakumo

[cez]

I had the same problem Jamtex described some months ago. The problem disappeared after a browser upgrade I guess (now on Firefox 3.5.3).

I just noticed that when I click on the main window with posts the encoding is recognized as Western ISO-8859-1 and in the Quick Reply text box it is UTF-8. Try to manually set the encoding to Unicode when you write and it should be fine.

[ave]

I discovered that I can't write any Kanji that were copied out of my JPNtext program or from any webpage. I use to copy the text to any of the browser's several textfield (adress bar, google search bar) prior to copying them again and them into the message field - works.

I use Firefox 3.0.14 btw, Unicode UTF-8.

[Jamtex]

$B?4(B$BNn(B$B<v(B$B;&(B$B;U(B$BB@(B$BO:(B$B4](B

[Jamtex]

Hmm have encoding set to UTF-8 and it's still mangled :S

[GaijinPunch]

Hmm have encoding set to UTF-8 and it's still mangled :S

It's BECAUSE you have it set to UTF-8 that it's still mangled. The Server's config (most likely MySQL) doesn't support it. Set it to the aforementioned ones and you should have no issue.