Craig Cavanaugh

I see that bundling a JVM negates some of the benefits of launch4j when it comes to cross platform builds for an application when using Maven, Gradle, etc.. I too see the benefit of JAVA_HOME as a viable fallback to not finding registry entries.

Updates in Polish translation

Thanks! I've made the changes and localization corrections for the next release. Missing resource keys for all buttons on few ‘Select something’ screens inthe Tools area (Default Currency, Date format and Locale). is cause by no localization withing JavaFx. I've add it to the TODO list to correct soon.

please, could you add the jar file again ?

The build system has changed significantly make use a jar file difficult. Within the bin directoy is a .bat file for windows that may make things easier. Use of the .exe file still allows passing the portable options as before, so either way, jGnash is still usable as a portable application

Update of the Polish translation

Commited for the next relase. Sorry for not making into the latest. I missed the patch request. In the future, use of Github pull requests for Issues would help. Thanks, Craig

The bug form indicates version 1.x of jGnash which is no longer maintained. Is the bug actually the latest 2.x release of jGnash? If so, can you create a small sample file that demonstrates this issue please and attach it to the bug report?