-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Error while parsing changed file #8895
Comments
Thanks for the report. The error message looks similar to #8870 Can you open the bib file in an application like Notepad++ and check the encoding? JabRef always tries to Write and Read in UTF-8. |
Thanks a lot for the files. I could reproduce this on my machine as well. |
Cause could maybe be: JabRef#75 (comment) |
* Fix charset detection with utf16 and others Fixes #8895 Fixes #8870 * checkstyöe * Fix typo in method names * change newlines * get bytes * Set newline character to LF * Revert "get bytes" This reverts commit 1082f8a. * progress * switch line sep to LF * Please work * Try jitpack * Add manual build of icu4j * Check if we have ascii in the list of charsets * fix checkstyle * Update external-libraries.md * Enocde with UTF-16BE * Fix umlaut * Hack to get test running * Also compare meta data * Add enforced ignorance of malformed characters Source: http://biercoff.com/malformedinputexception-input-length-1-exception-solution-for-scala-and-java/ Co-authored-by: Christoph <siedlerkiller@gmail.com> * checkstyle * IntelliJ now also renders the file correctly * Add test Additionally - Replace unknown characters - Remove obsolete wrapping classes in test * Refine CHANGELOG.md * Remove non-working jpackage reference Co-authored-by: Oliver Kopp <kopp.dev@gmail.com> Co-authored-by: Houssem Nasri <housi.housi2015@gmail.com>
JabRef version
5.6 (latest release)
Operating system
Windows
Details on version and operating system
WIndows 10 Pro 21H2
Checked with the latest development build
Steps to reproduce the behaviour
Appendix
...
Log File
The text was updated successfully, but these errors were encountered: