Fix some text-incoding inconsistencies #77
Merged
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.
This is a very minor thing, but I came across it while investigating packaging
lestfor Fedora:example/16-trompeloeil-runtime.cppis the only non-ASCII source file (because of theöin Björn Fahller’s name), and its encoding is ISO-8869-1. I think that in 2025, UTF-8 would make more sense.Furthermore,
CHANGES.txtis valid UTF-8, but some characters were munged during transcoding at some point, leading to the replacement character U+FFFD (UTF-8 byte sequence EF BF BD) appearing at several points. I reconstructed the original intended characters.