-
-
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
key generator fails to parse colon #3359
Comments
Could you please re-check the behavior with the most recent development version available here: http://builds.jabref.org/master/ and report what you find? Since the release of 4.0 there have been changes in the key generation, which might also have affected this. |
Sorry, on my mac it says things like file damaged and should be moved to trash. Your FAQ says I can avoid this by changing the security setting to allow apps from 'anywhere', but I don't have this option on my OS (Sierra, 10.12.6). |
I can verify that this happens in the latest 11-13 build on Windows:
Not only the special characters like colon or '`' are kept in the key phrase, I also think it is not necessary to keep the curly brackets in the file name when the PDF file is downloaded from the fetcher automatically based on the bibtex information (the curly brackets are from the title entry in the bibtex code). But this could be a separate issue. |
This should be fixed in the latest development version. Could you please check the build from http://builds.jabref.org/master/. Thanks! |
It seems that in 4.0 (Mac version), when I customize the key generator to [author][year][veryshorttitle], the generated keys will include the trailing colon if there is one in the title. It also includes other special characters like (`).
I remember this wasn't the case in 3.6.
The text was updated successfully, but these errors were encountered: