You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 28, 2021. It is now read-only.
"Always save history as UTF-8" introduced in 1.7.0 is a good idea but it created a new problem. Sometimes messages are received in the unexpected encodings. Before 1.7.0 messages can be read by changing the encoding in message window but it is impossible now. Original (expected) encoding can be recorded to history for decoding by hands may be ?
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
"Always save history as UTF-8" introduced in 1.7.0 is a good idea but it created a new problem. Sometimes messages are received in the unexpected encodings. Before 1.7.0 messages can be read by changing the encoding in message window but it is impossible now. Original (expected) encoding can be recorded to history for decoding by hands may be ?
The text was updated successfully, but these errors were encountered: