-
-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ANSI Encoding with Umlauts leads to compile errors and javadoc errors #108
Comments
Hey @HoffmannTom, |
hm... I updated to the same java version and also used git clone instead of downloading the zip file. |
Btw... the same problem occurs at compiling the java sources:
Using the -encoding parameter would also help to get platform independent: |
Hello @derTobsch Currently there is UTF-8 configured. Thanks! |
Intellij says that everything is UTF-8 encoded. By builds are fine. This is also the preferred way to configure it, see https://maven.apache.org/plugins/maven-resources-plugin/examples/encoding.html. Need some time to look at it. Maybe you can take a look at your IDE? Maybe there is something wrong? Or do you build it on a shell? @HoffmannTom can you check your git encoding? Maybe there is something configured. I also provided two branches. Please clone the repo for each branch again and try to build #112 and #111 |
Hello @derTobsch , |
I think I got it
This worked for me. |
That sounds good. If you want to provide a pr, please feel welcome to provide one. I would be happy to see the first pr from another person |
Describe the bug
When compiling with Java 17 I get errors due to encoding issues, e.g.:
The problems are the used Umlauts within the Java files.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Compile shouldn't fail.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Additional context
Similar problems occur when generating the javadocs. The Umlauts also causes errors.
Maybe converting everything to UTF-8 would be a good solution for the future or omit special characters.
The text was updated successfully, but these errors were encountered: