Opened 11 years ago

Closed 8 years ago

#165 closed Bug / Defect (fixed)

GUI: broken log encoding on non-english Windows

Reported by: svimik Owned by:
Priority: minor Milestone:
Component: Generic / unclassified Version: OpenVPN 2.2.0 (Community Ed)
Severity: Not set (select this one, unless your'e a OpenVPN developer) Keywords: GUI log encoding windows
Cc: Heiko Hund


Some events (like route add) may produce error message.
On non-english Windows this message will be also non-english.
And the encoding will be broken.
See my screenshot:

Change History (5)

comment:1 Changed 11 years ago by svimik

  1. if adapter's name contains non-english characters, the encoding in CLI is wrong. in GUI it appears correctly though. I suppose the windows CLI and openvpn GUI are using different encoding to display text
  1. but "route add" errors vice versa are not readable in openvpn GUI

So I suppose there are encoding problems both in openvpn and its GUI

comment:2 Changed 10 years ago by David Sommerseth

Can you please try the OpenVPN 2.3-alpha3 releases? The 2.3 release contains a lot of code changes to the UTF-8 and Windows charset handling in general.

comment:3 Changed 9 years ago by Samuli Seppänen

Keywords: windows added

comment:4 Changed 9 years ago by Gert Döring

Cc: Heiko Hund added

I can't look at the original error message, but I'd second what dazo has asked for: please check how 2.3.2 and git master behave regarding unicode on windows - I think d12fk has done fairly good work there in fixing UCS-16, UTF-8, codepage, etc. problems, but some might still be left.

If we don't hear from you, we consider this to be fixed, and will close the ticket on Feb 15.

comment:5 Changed 8 years ago by Gert Döring

Resolution: fixed
Status: newclosed

Closing this ticket now, barely 8 months later than announced.

If the problem still exists in 2.3.6, please reopen.

Note: See TracTickets for help on using tickets.