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
I have been receiving emails that have headers with the defined character encoding GB2312. However, it appears as though these headers require the GB18030 character encoding to properly display the decoded headers. Is there a way I can force the header decoder to use GB18030 instead of GB2312?
I have been receiving emails that have headers with the defined character encoding GB2312. However, it appears as though these headers require the GB18030 character encoding to properly display the decoded headers. Is there a way I can force the header decoder to use GB18030 instead of GB2312?
What I did:
What I expected:
법원에 애플·HTC 특허합의문 공개
What I got:
�0�0�3�9�2�3 �2�1�5�3·HTC �5�8�6�1�6�6�3�5�0�1 �7�0�7�3
Release or branch I am using:
v1.2.0
The text was updated successfully, but these errors were encountered: