Fix windows utf-8 issues #256
Merged
Conversation
This file contains 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
angerman
requested review from
paweljakubas,
Anviking,
HeinrichApfelmus,
jonathanknowles and
Unisay
as code owners
hamishmack
force-pushed
the
angerman/fix-win
branch
from
1330a07
to
4942a2b
Compare
|
This has fixed the cross compiled Windows issue. It does not fix the windows ghc 9.6.5 issue in the GitHub action (so we have left that disabled for now). |
hamishmack
approved these changes
Jun 12, 2024
This ensure we force the rigth codepages on windows to support utf8 caracters in the haskell source for the tests.
angerman
force-pushed
the
angerman/fix-win
branch
from
4942a2b
to
7c6f28e
Compare
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 ensure we force the rigth codepages on windows to support utf8 caracters in the haskell source for the tests.