-
-
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 Input byte array has wrong 4-byte ending unit #11117
Comments
Please send the bib file to me |
Can you please send the file to web@jabref.org
Can you check the file encoding in another editor? Seems like an issue with
Byte Order Mark (bom)
Ingmar Lippert ***@***.***> schrieb am So., 31. März 2024,
15:59:
… JabRef version
Other (please describe below)
Operating system
Other (please describe below)
Details on version and operating system
JabRef 5.13--2024-03-31--0d97382 Linux 6.7.9-200.fc39.x86_64 amd64 Java
21.0.2 JavaFX 22+30
Checked with the latest development build (copy version output from About
dialog)
- I made a backup of my libraries before testing the latest
development version.
- I have tested the latest development version and the problem persists
Steps to reproduce the behaviour
1. open my library file, provided upon request ;)
suggestion: provide more intelligible error message
Appendix
...
Log File
java.lang.IllegalArgumentException: Input byte array has wrong 4-byte ending unit
at java.base/java.util.Base64$Decoder.decode0(Unknown Source)
at java.base/java.util.Base64$Decoder.decode(Unknown Source)
at java.base/java.util.Base64$Decoder.decode(Unknown Source)
at ***@***.***/org.jabref.logic.importer.fileformat.BibtexParser.parseField(Unknown Source)
at ***@***.***/org.jabref.logic.importer.fileformat.BibtexParser.parseEntry(Unknown Source)
at ***@***.***/org.jabref.logic.importer.fileformat.BibtexParser.parseAndAddEntry(Unknown Source)
at ***@***.***/org.jabref.logic.importer.fileformat.BibtexParser.parseFileContent(Unknown Source)
at ***@***.***/org.jabref.logic.importer.fileformat.BibtexParser.parse(Unknown Source)
at ***@***.***/org.jabref.logic.importer.fileformat.BibtexImporter.importDatabase(Unknown Source)
at ***@***.***/org.jabref.logic.importer.fileformat.BibtexImporter.importDatabase(Unknown Source)
at ***@***.***/org.jabref.logic.importer.OpenDatabase.loadDatabase(Unknown Source)
at ***@***.***/org.jabref.gui.importer.actions.OpenDatabaseAction.loadDatabase(Unknown Source)
at ***@***.***/org.jabref.gui.importer.actions.OpenDatabaseAction.lambda$openTheFile$1(Unknown Source)
at ***@***.***/org.jabref.gui.util.BackgroundTask$1.call(Unknown Source)
at ***@***.***/org.jabref.gui.util.DefaultTaskExecutor$1.call(Unknown Source)
at ***@***.***/javafx.concurrent.Task$TaskCallable.call(Unknown Source)
at java.base/java.util.concurrent.FutureTask.run(Unknown Source)
at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.base/java.util.concurrent.FutureTask.run(Unknown Source)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.base/java.lang.Thread.run(Unknown Source)
—
Reply to this email directly, view it on GitHub
<#11117>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AACOFZFJMCTHLT2GOUH63MLY3AJE7AVCNFSM6AAAAABFQOFZICVHI2DSMVQWIX3LMV43ASLTON2WKOZSGIYTMOJZGQ2TAMY>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Possible error could be related to the check for a bibdesk file field. Do you have a field starting with jabref/src/main/java/org/jabref/logic/importer/fileformat/BibtexParser.java Lines 745 to 749 in 61120e4
|
indeed, one of the entries that seems to create problems includes
gosh, the legacy of the era of using bibdesk a decade ago. |
Yes, JabRef is now able to parse BibDesk files and group(s) |
Sorry if I misuse the ticket for this. Does this BibDesk reading by the way extend to Skim's skim note files? |
Hah, as wiki might say it, once upon a time, Skim was a PDF reader, that featured non-pdf compliant annotations :(
Skim was/is developed by the BibDesk team and together it worked very well.
<https://en.m.wikipedia.org/wiki/Skim_(software)>
…--
Sent from my LineageOS device with K-9 Mail. Please excuse my brevity.
On 31 March 2024 18:01:47 CEST, Christoph ***@***.***> wrote:
> Sorry if I misuse the ticket for this. Does this BibDesk reading by the way extend to Skim's skim note files?
Never heard of this program before, I have no idea how this work, but if it's creating annotations (e.g highlighting text or comments) in pdf files, JabRef can read these (Tab File Annotations)
<img width="1347" alt="grafik" src="https://github.com/JabRef/jabref/assets/320228/1846ee12-8e10-4e52-9311-1993640efe09">
MacOS Preview pdf:
<img width="638" alt="grafik" src="https://github.com/JabRef/jabref/assets/320228/275fc331-09e5-4b2d-a171-67871445db63">
--
Reply to this email directly or view it on GitHub:
#11117 (comment)
You are receiving this because you authored the thread.
Message ID: ***@***.***>
|
According to their FAQ they save the notes in the extended file attributes on the file system (crazy), so even transferring them to a different computer would lose the info... However, seems like you can export it somehow https://sourceforge.net/p/skim-app/wiki/FAQ/
|
Thanks, yeah. Was never able to automate that. And transitioned away from osx a decade ago.
Maybe relevant as a usecase story: I keep the `bdsk` file references in the entry just as an indicator that I know there might be old notes left. And if these promise a nice secret, I power on my legacy Mac to access these files. But otherwise the `bdsk` file references are quite nonfunctional for me.
Am so happy I switched to JabRef and plain text annotations.
--
Sent from my LineageOS device with K-9 Mail. Please excuse my brevity.
…On 31 March 2024 18:15:47 CEST, Christoph ***@***.***> wrote:
According to their FAQ they save the notes in the extended file attributes on the file system (crazy), so even transferring them to a different computer would lose the info... However, seems like you can export it somehow
https://sourceforge.net/p/skim-app/wiki/FAQ/
> How can I save the PDF so that notes are visible in other viewers, such as Preview and Acrobat?
> Save a copy of the file with the notes included in the PDF. Choose Export... from the File menu and select PDF from the File Format popup button and select the With Embedded Notes option. Notes and highlights are now visible in other viewers, such as Preview and Acrobat Reader. Alternatively, you can Print to a file. Go to the print dialog window (command+P) and choose Print to PDF. However with both techniques, you won't be able to edit the notes and highlights in the exported copy.
--
Reply to this email directly or view it on GitHub:
#11117 (comment)
You are receiving this because you authored the thread.
Message ID: ***@***.***>
|
Here is another line that causes an error
and this one
|
You can use this version https://builds.jabref.org/pull/11118/merge It will print out all more warnings/errors |
Several things "wrong" with my data in this version JabRef 5.13-PullRequest11118.330--2024-03-31--0c344a9
this seems to be caused by the
|
In fact, no, it does not print out more warnings/info. I tried to copy into an empty library my round 7k entries, and only round 0.5k are imported; without any notice, the other 6.5k entries are seemingly ignored. |
However, the original file does generate these messages
|
the seemingly final culprit
thanks Christoph for the build with the warnings. helped a lot. |
I consider this closed with the #11118 fix as it helps the user to locate the error |
Thanks for your feedback. We will check the annote field parsing as well. I guess JabRef expects the at belongs to a cite key but the field should be parsed as verbatim probably. Will need to check the spec as well. We will check the copy pasting as well. Seems like there is a different parsing logic/error handling involved A bit of background, the bibdesk file fields are base64 encoded plist-files |
JabRef version
Other (please describe below)
Operating system
Other (please describe below)
Details on version and operating system
JabRef 5.13--2024-03-31--0d97382 Linux 6.7.9-200.fc39.x86_64 amd64 Java 21.0.2 JavaFX 22+30
Checked with the latest development build (copy version output from About dialog)
Steps to reproduce the behaviour
suggestion: provide more intelligible error message
Appendix
...
Log File
The text was updated successfully, but these errors were encountered: