Eliminate UTF-8 warnings while formatting test output #186
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
ehuelsmann
force-pushed
the
better-utf8
branch
2 times, most recently
from
1103695 to
fada0ef
Compare
This solves a long-standing warning in the LedgerSMB project where test output includes a checkmark (utf8 character U+2713). While perfectly valid UTF-8 and the data never leaves the application memory space, the error has been puzzling thusfar. With help from @ylavoie, it's now sorted that this fix solves the warning.
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.
This solves a long-standing warning in the LedgerSMB project where
test output includes a checkmark (utf8 character U+2713). While
perfectly valid UTF-8 and the data never leaves the application
memory space, the error has been puzzling thusfar. With help from
@ylavioe, it's now sorted that this fix solves the warning.