Note, that only JabRef 3.8.2 would open always open the files, as long as the correct main file directory was set. Below I attach some screenshots of the file editor view of files with "full" and "partial" relative paths for both JabRef 5.7 (current developer version) and JabRef 3.8.2 (both use the same (!) main file directory). This new behaviour is completely different from JabRef 3.8.2, where - if the correct main file directory was set - it would not matter, whether the file had the "full relative path" or the "partial relative path". Now files from (4) will open, but files from (2) will no longer open (instead you get again the file manager) You can get around the issue of (4) if you change your main file directory to the directory that contains the file directory, e.g. The file will not open and instead the file manger of the operating system (e.g., Windows Explorer) is openedĥ. Now try to open a linked file from within JabRef that has a "partial relative path" (Literature_database/Baez2008.pdf)Ĥ. The linked file is opened (all is good!)ģ. We assume you have set the correct main file directory in your preferences (e.g., C:\Users\Literature_database)Ģ. Open a linked file from within JabRef (current developer version 5.7) that has a "full relative path" (Baez2004.pdf). Let's forget about (c) since I have not seen the issue so far appear with (c) (in fact I don't even know, whether the newer JabRef versions support absolute file paths).ġ. C:/Users/Literature_database/Baez2012.pdf you had specified the same main file directory as in (a), but the file would be shown in the "File" field of the editor with its file name the directory the file was stored in, e.g., Literature_database/Baez2008.pdf ("Literature_database" is the directory, "Baez2008.pdf" is the actual file) (b) a "partial relative path" (again, don't know the proper term), i. you had specified your main file directory in the preferences, and the file would be shown in the "File" field of the editor with just its name, e.g., Baez2004.pdf (a) a "full relative path" (don't know the proper term), i. When adding linked files to JabRef (at least this happened in the older version) you would sometimes end up with files with While using the wonderful "Copy linked files to folder." function of JabRef 5 I noticed a behaviour of linked files that differs a lot from previous versions (namely JabRef 3.8.2) and which can have serious consequences. I have tested the latest development version and the problem persists I made a backup of my libraries before testing the latest development version. # Checked with the latest development build # Details on version and operating system Don't do that.Īpart from that, thanks for the great software. (jabref:15534): Gdk-WARNING **: 12:19:24.373: XSetErrorHandler() called with a GDK error trap pushed. Probably that is not linked to this issue, but the Terminal output says while starting Jabref:ĮRROR StatusLogger Unrecognized format specifier ĮRROR StatusLogger Unrecognized conversion specifier starting at position 16 in conversion pattern.ĮRROR StatusLogger Unrecognized conversion specifier starting at position 25 in conversion pattern.ĮRROR StatusLogger Unrecognized conversion specifier starting at position 35 in conversion pattern.ĮRROR StatusLogger Unrecognized conversion specifier starting at position 47 in conversion pattern.ĮRROR StatusLogger Unrecognized conversion specifier starting at position 54 in conversion pattern.ĮRROR StatusLogger Unrecognized conversion specifier starting at position 56 in conversion pattern. In my bibliography.bib file, files are linked like `file = ,`. I tested absolute paths, they are still working. Nothing happens and _Open file_ in the right click menu is grey. Since I have installed the update, I cannot open linked files with F4, click on the file symbol or with _right click -> open file_. T … oday i received the update notification and installed the new jabref version 5.1 on my Ubuntu 20.04 via the.
0 Comments
Leave a Reply. |