Carl Christian Snethlage

In fact we are in a long term refactoring progress of the prefs service, but as jabref is only a project for our free time, we can only work on...

Thanks for your interest in JabRef programming. As this issue is merly a code quality suggestion but a real issue and code quality is always been worked on, I will...

There seem to be several special conditions with the files our parser cannot read yet: - Cannot find a definition for the namespace http://ns.adobe.com/pdfx/1.3/ - No type defined for {http://ns.adobe.com/xap/1.0/mm/}subject...

To make this issue a lot more annoying: Try to paste the timestamp a second time, after it gets truncated... Argh.... 😕

Any update here?

any update here?

Closing this issue due to inactivity :zzz: Maybe someone eventually will continue your good work already and push it forward.

maybe fixed in #8506 ?

2-2.5 minutes is definitely way too long. Starting jabref takes my machine 2-2.5 seconds.

We are planning to reimplement database loading on jabcon in September. This maybe won't speed up the process at first, but should make it more responsive.