mIRC Homepage
Posted By: Bishibashi Degraded Japanese cahacter handling - 09/11/07 04:20 AM
Compared with 6.16, 6.31 seems to have some bugs at handling Japanese or multibytes characters.

When the message is divided to plural lines, the first letter at the 2nd, 3rd... lines always display wrong character.
It may lose to display the first byte of the character.

I hope this issue soon fixed.

Thanks.
Posted By: Wallmit Re: Degraded Japanese cahacter handling - 09/11/07 04:51 PM
I can confirm this. In most cases (excluding when you try to copy what's already 文字化け'd) one can copy text normally, but not read it, though, but it's kind of annoying, like when you are on such networks like freenode, where people just tend to conduct "smart" conversations saying long sentences.
Posted By: 7teen Re: Degraded Japanese cahacter handling - 09/11/07 05:11 PM
I've seen this too! But it does not bother me :P Though it'd be cool if someone fixed it. I think smile
Posted By: cartaeon Re: Degraded Japanese cahacter handling - 22/02/08 01:52 AM
I would just like to call attention to this bug report, as this issue remains as of 6.31, and at least for me is a show-stopper which significantly impacts my ability to use mIRC on a daily basis.

The basic issue on my end is that when using Japanese WITHOUT UTF8 enabled, as is the usual method on Japanese channels and networks, the character at the intersection of a line split becomes incorrectly decoded and split into two garbage ASCII characters. An example of this behavior can be seen here:


The point of attention here is the small 't' which can be seen on the third line down, which is being displayed instead of the correct Japanese character as seen further down on the UTF8 line. Occasionally this garbage text is more troublesome ASCII characters which can negatively affect all of the characters that follow.

I would be extremely pleased to see this fixed.
Posted By: argv0 Re: Degraded Japanese cahacter handling - 22/02/08 01:55 AM
Err,

It works with UTF8 on, yes? Can you not keep UTF8 on? If so, where's the problem / how is it a "show stopper"?
Posted By: cartaeon Re: Degraded Japanese cahacter handling - 22/02/08 05:31 AM
UTF8 is not supported by most Japanese IRC clients, and thus networks and channels usually do not use that encoding. I cannot use UTF8 in this case.

I understand this may appear to be a small, minor problem, and I'm sure the number of people affected is small, but having nearly every single line of text partially messed up becomes ridiculously annoying after a while. It would just be nice not to have to use an outdated version to chat properly.
Posted By: argv0 Re: Degraded Japanese cahacter handling - 22/02/08 06:20 AM
There are multiple UTF8 settings in mIRC. There is a display only mode as well as a display and encode mode. I imagine that setting it to display only will render your local window properly while still sending non-utf8 to your japanese friends across the wire.

This should be an easy fix and can be done through the font dialog (View -> Font)
Posted By: cartaeon Re: Degraded Japanese cahacter handling - 22/02/08 06:42 PM
I appreciate the help, but Display Only is what the "non unicode" text is using in that screenshot, and it certainly does not display properly. UTF8 Display and Encode is what is used in the Unicode enabled example. The problem lies with the display of SJIS text (I believe that is what mIRC displays natively in the window)

And just to save extra hassle I will say now that none of the Message settings in mIRC options (SJIS/JIS conversion, etc) are acceptable for solving the issue. It simply appears to be degraded font/text/encoding handling introduced by some change in the engine over the past couple versions.

Thanks again for any help!
Posted By: Riamus2 Re: Degraded Japanese cahacter handling - 22/02/08 10:03 PM
Strange. I thought there was a fix that handled issues with where lines wrapped. Maybe that fix only affected UTF8 and nothing else...
Posted By: Khaled Re: Degraded Japanese cahacter handling - 19/04/08 09:08 AM
Thanks this issue has been fixed for the next version.
© mIRC Discussion Forums