[ZNC 1.6.5] Client encoding settings aren't copied over from the user to a new network [CygWin] #759

New Issue

2026-10-05T04:43:05+02:00

adam commented

2026-10-05 04:43:05 +02:00

OS: Windows Server 2012 R2
ZNC version: ZNC 1.6.5+cygwin1 - http://znc.in
IPv6: yes, SSL: yes, DNS: threads, charset: yes
CygWin version: CYGWIN_NT-6.3 Server 2.7.0(0.306/5/3) 2017-02-12 13:18 x86_64 Cygwin

When adding a new network the Client encoding settings from the user aren't copied over to the new network properly in the Web-interface.

For example, the user has Client encoding under ZNC Behavior set to:
Try to parse as UTF-8 and as ISO-8859-15 , send as UTF-8 (recommended)
But when adding a new network it says:
Try to parse as UTF-8 and as UTF-8 , send as UTF-8 (recommended)

**OS:** Windows Server 2012 R2 **ZNC version:** ZNC 1.6.5+cygwin1 - http://znc.in IPv6: yes, SSL: yes, DNS: threads, charset: yes **CygWin version:** CYGWIN_NT-6.3 Server 2.7.0(0.306/5/3) 2017-02-12 13:18 x86_64 Cygwin When adding a new network the **Client encoding** settings from the user aren't copied over to the new network properly in the Web-interface. For example, the user has Client encoding under _ZNC Behavior_ set to: _Try to parse as UTF-8 and as **ISO-8859-15** , send as UTF-8 (recommended)_ But when adding a new network it says: _Try to parse as UTF-8 and as **UTF-8** , send as UTF-8 (recommended)_

adam closed this issue

2026-10-05 04:43:05 +02:00

adam commented

2026-10-05 04:43:06 +02:00

There are no server encodings in User. User has client encoding - the one used between IRC client and ZNC.

There are no server encodings in User. User has client encoding - the one used between IRC client and ZNC.

adam commented

2026-10-05 04:43:07 +02:00

I updated the Title and the comment. I meant the Client encoding setting that you can find under ZNC Behavior

I updated the Title and the comment. I meant the **Client encoding setting** that you can find under **ZNC Behavior**

adam commented

2026-10-05 04:43:07 +02:00

That doesn't change anything.
There's no client encoding in Network.
Client connects to a user, using client encoding configured in the user; network connects to server using server encoding configured in network. There's no problem having client to use UTF-8 only for all networks, because ZNC handles reencodings per-network internally.

In other words, client encoding is independent from server encoding. Encoding in user settings is independent from encoding in network settings.

That doesn't change anything. There's no client encoding in Network. Client connects to a user, using client encoding configured in the user; network connects to server using server encoding configured in network. There's no problem having client to use UTF-8 only for all networks, because ZNC handles reencodings per-network internally. In other words, client encoding is independent from server encoding. Encoding in user settings is independent from encoding in network settings.

adam commented

2026-10-05 04:43:08 +02:00

My mistake, I didn't read carefully enough. Thought initially they were the same, I see now they are two completely different settings.

My mistake, I didn't read carefully enough. Thought initially they were the same, I see now they are two completely different settings.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: adam/znc#759