Make tests work on Windows and typos

[seanyoung]

No description provided.

[bengtmartensson]

Hi Sean. Many thanks for your efforts. Comments:

1. I would like to have the spelling fixes and the test fixes in separate commits. Is that OK?
2. There is a problem with your fixes. The current program Runs/compiles on the age-old Java 8, which does not contain String.lines(), see https://docs.oracle.com/javase/8/docs/api/java/lang/String.html. There will come a day, and a reason, when I give up Java 8, but I do not consider your issue to be that reason. I ask you for a Java 8 version.

[seanyoung]

1. I would like to have the spelling fixes and the test fixes in separate commits. Is that OK?

Makes sense. I've made it into a separate commit.

2. There is a problem with your fixes. The current program Runs/compiles on the age-old Java 8, which does not contain String.lines(), see https://docs.oracle.com/javase/8/docs/api/java/lang/String.html. There will come a day, and a reason, when I give up Java 8, but I do not consider your issue to be that reason. I ask you for a Java 8 version.

I've reimplemented without .lines(), I think it should work in Java 8.

Thanks!

[bengtmartensson]

Hi Sean,
I "deep dived" yesterday and found out interesting: The basic idea is that a multi-platform Java program should generate output in the native format for the platform it currently runs on. The tests are written in that vein. The failed tests are not "false positives", they really detect a problem. The culprit is JCommander, which generates help/usage texts using "\n" for all platforms. Bugreport. For this reason, I will not use your PR (the spell-fix commit "cherry-picked" though), but will implement another, more transparent solution.

Thank you very much for your efforts. Sorry for asking you for a Java-8 version that was not used anyhow.