Fix: The report is saved without following the UTF-8 encoding #564
Conversation
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
…ally save according to utf-8
|
Mind testing if 4.0.0rc1 solves your issue? |
|
v4 seems to handle this correctly. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
HTML specifies the page charset="utf-8", but the file was not actually save according to utf-8
How to reproduce
a case
Report content
Cause analysis
This line of code declares that the HTML content is displayed in UTF-8, but in fact, the HTML file is not saved in UTF-8.
To put it simply, the encoding of the file content is unknown, but it is emphasized to display according to UTF-8
#224