Skip to content

fix(encoding): set content encoding to UTF-8 - #140

Open
DrRataplan wants to merge 1 commit into
mainfrom
charsets
Open

fix(encoding): set content encoding to UTF-8#140
DrRataplan wants to merge 1 commit into
mainfrom
charsets

Conversation

@DrRataplan

Copy link
Copy Markdown
Contributor

This prevents endpoints serving non-latin scripts to display properly. Without the UTF-8 encoding the encoding will be interpreted as something else, resulting in so-called mojibake.

@line-o

line-o commented Aug 27, 2026

Copy link
Copy Markdown
Member

I have a hard time seeing the actual changes on my phone because the GitHub app does not have the option to ignore whitespace changes. Any chance splitting this PR up in a formatting followed by the change or the other way around? Whatever is simpler.

This prevents endpoints serving non-latin scripts to display properly. Without the UTF-8 encoding
the encoding will be interpreted as something else, resulting in so-called mojibake.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants