Use UTF-8 encoding during compilation #186
Open
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
|
Is there a reason to include a if statement? Both formulations work on Linux. |
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.
Force use of UTF-8 encoding during compilation in
build-jar.sh. Couldn't compile without that because my system uses windows-1250 encoding and there were some unmappable characters.javacby default uses system encoding and windows doesn't use UTF-8 as default.I also added UTF-8 encoding in
test.shfor consistency. Also editedjavaccommand intest.shto work in MinGW and Cygwin - windows uses;for seperating classpaths instead of:.