When I upgraded ZNC from 1.6.5 to 1.7.0, strange thing starts to happen. When I connected to my ZNC with AdiIRC, the buffer is garbled, looking like UTF-8 text interpreted as UTF-7. Real-time chat, query, backlog module, etc. seems like working as expected. Of course my server and client set to use only UTF-8 to communicate.
I'm not sure which one is to blame, but this problem disappears when I downgrade ZNC to 1.6.5. So it was my first choice to report this problem here.
When I upgraded ZNC from 1.6.5 to 1.7.0, strange thing starts to happen. When I connected to my ZNC with AdiIRC, the buffer is garbled, looking like UTF-8 text interpreted as UTF-**7**. Real-time chat, query, backlog module, etc. seems like working as expected. Of course my server and client set to use only UTF-8 to communicate.
I'm not sure which one is to blame, but this problem disappears when I downgrade ZNC to 1.6.5. So it was my first choice to report this problem here.
<!-- github-sync-id:320562186 -->
Show exact output of znc --version. What modules are loaded? What encodings did you select for user and network in ZNC?
Show exact output of `znc --version`. What modules are loaded? What encodings did you select for user and network in ZNC?
<!-- github-comment-id:386866826 -->
This is a screenshot from my PC running AdiIRC. The texts in quotes are intended to be exactly same, saying "안녕하세요", whitten in Korean alphabet.

This is a screenshot from my PC running AdiIRC. The texts in quotes are intended to be exactly same, saying "안녕하세요", whitten in Korean alphabet.
<!-- github-comment-id:386868116 -->
Nothing but bunch of PRIVMSGs. Strangely, other clients(I've tried HexChat and AndroIRC) don't seem to have charset problem with buffer. As far as I can see from the console, the buffer data itself seems to be correct UTF-8.
I've tried saving bunch of text as UTF-8 file and opening it as UTF-7. I got similar result with one from AdiIRC; for example, "안녕하세요" becomes "ìë íì¸ì", just like you can see from the screenshot.
So it can be a bug of only AdiIRC, not of ZNC. What I want to know is what makes AdiIRC behave like that, as it never happened before I installed ZNC 1.7.0.
Nothing but bunch of PRIVMSGs. Strangely, other clients(I've tried HexChat and AndroIRC) don't seem to have charset problem with buffer. As far as I can see from the console, the buffer data itself seems to be correct UTF-8.
I've tried saving bunch of text as UTF-8 file and opening it as UTF-7. I got similar result with one from AdiIRC; for example, "안녕하세요" becomes "ìë íì¸ì", just like you can see from the screenshot.
So it can be a bug of only AdiIRC, not of ZNC. What I want to know is what makes AdiIRC behave like that, as it never happened before I installed ZNC 1.7.0.
<!-- github-comment-id:387323302 -->
Packet from 1.7.0 have "batch" in message(which doesn't appear in one from old version...it's IRCv3 implementation, right?). This is something changed in 1.7.0, and which I wanted to know. IT was something that AdiIRC handles wrong. To tell the truth, the bug seems to be already fixed in beta version of AdiIRC(which I never tried).
I'm sorry for making you spend some time for me.
Aargh, Wireshark gave me answer...
Packet from 1.7.0 have "batch" in message(which doesn't appear in one from old version...it's IRCv3 implementation, right?). This is something changed in 1.7.0, and which I wanted to know. IT was something that AdiIRC handles wrong. To tell the truth, the bug seems to be already fixed in beta version of AdiIRC(which I never tried).
I'm sorry for making you spend some time for me.
<!-- github-comment-id:387491564 -->
Packet from 1.7.0 have "batch" in message(which doesn't appear in one from
old version...it's IRCv3 implementation, right?). This is something changed
in 1.7.0, and which I wanted to know. IT was something that AdiIRC handles
wrong. To tell the truth, the bug seems to be already fixed in beta version
of AdiIRC(which I never tried).
How does batch cause UTF-7 though?
"batch" is implemented now, but it's not sent unless client requests it...
which it does.
2018-05-08 19:07 GMT+01:00 IRTC1015 <notifications@github.com>:
> Aargh, Wireshark gave me answer...
>
> Packet from 1.7.0 have "batch" in message(which doesn't appear in one from
> old version...it's IRCv3 implementation, right?). This is something changed
> in 1.7.0, and which I wanted to know. IT was something that AdiIRC handles
> wrong. To tell the truth, the bug seems to be already fixed in beta version
> of AdiIRC(which I never tried).
>
> I'm sorry for making you spend some time for me.
>
> —
> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub
> <https://github.com/znc/znc/issues/1526#issuecomment-387491564>, or mute
> the thread
> <https://github.com/notifications/unsubscribe-auth/AAT15CP4Fx7kF1B-e4Gl07ah1QW8KsNvks5twd7WgaJpZM4Tz5E->
> .
>
<!-- github-comment-id:387504199 -->
I have no idea. They just marked it as resolved without further explanation. Who on earth uses UTF-7 anyway?
I have no idea. They just marked it as resolved [without further explanation](https://dev.adiirc.com/issues/3846). Who on earth uses UTF-7 anyway?
<!-- github-comment-id:387508753 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
When I upgraded ZNC from 1.6.5 to 1.7.0, strange thing starts to happen. When I connected to my ZNC with AdiIRC, the buffer is garbled, looking like UTF-8 text interpreted as UTF-7. Real-time chat, query, backlog module, etc. seems like working as expected. Of course my server and client set to use only UTF-8 to communicate.
I'm not sure which one is to blame, but this problem disappears when I downgrade ZNC to 1.6.5. So it was my first choice to report this problem here.
Show exact output of
znc --version. What modules are loaded? What encodings did you select for user and network in ZNC?I've compiled znc from tarball, on my Raspberry Pi running Debian buster. The output of $ znc --version is:
Part of my znc.conf follows:
This is a screenshot from my PC running AdiIRC. The texts in quotes are intended to be exactly same, saying "안녕하세요", whitten in Korean alphabet.
How did you detect this as UTF-7?
Does
znc -Dshow anything interesting during playback or before?Nothing but bunch of PRIVMSGs. Strangely, other clients(I've tried HexChat and AndroIRC) don't seem to have charset problem with buffer. As far as I can see from the console, the buffer data itself seems to be correct UTF-8.
I've tried saving bunch of text as UTF-8 file and opening it as UTF-7. I got similar result with one from AdiIRC; for example, "안녕하세요" becomes "ìë íì¸ì", just like you can see from the screenshot.
So it can be a bug of only AdiIRC, not of ZNC. What I want to know is what makes AdiIRC behave like that, as it never happened before I installed ZNC 1.7.0.
No idea... Try to use wireshark or tcpdump to see what encoding it sends during buffer playback.
Aargh, Wireshark gave me answer...
Packet from 1.7.0 have "batch" in message(which doesn't appear in one from old version...it's IRCv3 implementation, right?). This is something changed in 1.7.0, and which I wanted to know. IT was something that AdiIRC handles wrong. To tell the truth, the bug seems to be already fixed in beta version of AdiIRC(which I never tried).
I'm sorry for making you spend some time for me.
How does batch cause UTF-7 though?
"batch" is implemented now, but it's not sent unless client requests it...
which it does.
2018-05-08 19:07 GMT+01:00 IRTC1015 notifications@github.com:
I have no idea. They just marked it as resolved without further explanation. Who on earth uses UTF-7 anyway?
Well, good that it's resolved.
Btw, batch would be visible in
znc -Dtoo.