-
Notifications
You must be signed in to change notification settings - Fork 44
Encoding issue when displaying error messages (F@h 7.6.x) #76
Comments
Just want to put my observations on this issue. This hex encoding for localized characters is not only in the log messages transmitted by the FAHClient, which is not expected to be valid Pyon/Json, but can also be found in other messages, like info. For example:
Note the \xe9 in the value. Perhaps this is valid Pyon, I don't know, but it is not valid Json. |
This is a problem in C!. I may have been fixed recently. CauldronDevelopmentLLC/cbang@641d0cc JSON allows for |
Any further progress on this? Changes made in the latest 7.6 betas? |
Hello, I also spotted a similar issue, not sure if it has also been fixed in your commit @jcoffland?
|
Hello,
There seems to be an issue with F@H / FahControl 7.6.x when handling "exotic" characters (i.e. french ones ;) ) in error messages (mainly network-related ones)
(message should read : "Une connexion existante a dû être fermée par l’hôte distant.")
The easiest way to reproduce this is to launch the Viewer and close it (to receive the "usual" networking error msg)
It is OK with F@H / FahControl 7.5.1
Logfile for v7.6.9 appears OK in Notepad2 (or Notepad++) with the correct UTF8 encoding.
My computer is running Windows 10 Family Edition 1909 :
I am available if you need more information, or if you want me to test a fix/beta version.
Thanks !
JY.
The text was updated successfully, but these errors were encountered: