fix(cli): force UTF-8 stdout/stderr on Windows to avoid UnicodeEncode… - #1
Open
2031814001yuyue-tech wants to merge 1 commit into
Open
Conversation
…Error Windows consoles default to GBK/cp936 which cannot encode all Unicode characters (e.g. \xa0 non-breaking spaces common in article bodies). Reading a WeChat article on a Chinese Windows terminal previously crashed with UnicodeEncodeError when printing the result. Reconfigure stdout/stderr to UTF-8 at CLI entry, matching the UTF-8 encoding used when writing files via --output.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Windows 终端默认使用 GBK/cp936 编码，无法编码所有 Unicode 字符。在中文 Windows 上读取文章时，会在打印结果时崩溃：