-
-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
2.11b4. Journal abbreviation duplicate detection #173
Comments
What behavior would you expect JabRef to have? |
I expect that JabRef wouldn't output the error message about a duplicate abbreviation if there is no real duplicate in the personal abbreviation list (see the last two lines of the first output above). |
Ok, so you say that the duplicate check should only be done per file -> only check for duplicates in the personal abbreviation list. Replacing a default abbreviation with a personal one should not result in a duplicate warning. Is this what you mean? |
Not exactly. I find that if you create a new abbreviation, not present in the default list, the program warns about a duplicate.
As you can see OLD and NEW are identical, so no real duplicate. The second part of the original post, about the "IEEE LaTeX abbreviations", may not be relevant: the original abbreviations are actually replaced by different abbreviations. So, in that case the warnings make sense. |
I have implemented a fix for the first part of the issue. For the second part, I do not know what to do. Maybe we should change the log statements to debug so that they are not shown to the user? |
An option might be to extract the IEEE journals abbreviations from journalList.txt and creating a third list with the "plain" IEEE journals abbreviations. Then if USE_IEEE_ABRV is not set the "plain" list is loaded, otherwise the "LaTeX abbreviations" in IEEEJournalList.txt is loaded (and a single line warning is sent to output). |
Good thinking. This might be an easy way to solve these issues while speeding up startup time. Especially not having all this console output will speed up the start as this is an expensive IO action. The check itself should be very fast and not that problematic. |
Any comments from your side, @ambro2 ? Otherwise I will close this issue. |
I haven't had any chance to test the branch. I'll trust you, @simonharrer, so I vote for closing. Thanks. |
Suggestion: turn it completely off. Jabref works fine with duplicates (even switching), and I happen to use that particular feature, but the slow dump of all "errors" in jabref4 makes the tool almost unstartable. |
Journal abbreviations in personal or external list are always detected as duplicate.
In an account that never used JabRef (no admin privileges) I started JabRef from the command line. I created a new journal abbreviation and closed. Starting again from the command line I get the following output:
See the last two lines
Same behaviour in Linux (Fedora 21).
Further, if "Use IEEE LaTeX abbreviations" is checked in preferences, then the output contains also lines like the following:
The system is Windows 7 Professional 64 bit. Java 1.8.0.60
Hope it helps.
The text was updated successfully, but these errors were encountered: