-
-
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
No utf8 encoding while fetching from Medline #2060
Comments
Thanks for your report. I could not reproduce that issue in the latest development version. All Betas and Alphas etc are shown correctly. Database encoding is set to UTF8. |
I just installed: |
JabRef 3.7dev--snapshot--2016-09-25--master--693c705 I can confirm: β |
Okay, I have an idea. And I will release a fix soon. |
When I am right it should be now correct: You can try this snapshot: |
Works here too. 👍 |
works! Thank you for a fast correction! |
BTW where is the line for the DOI search in this snapshot? |
@bernhard-kleine DOI? I don't know to what problem you refer to. The DOI ID-Fetcher (not fulltext) already uses UTF-8. Edit// I close this issue here. If you have further problems please open a new issue. |
Fixed in #2061 |
That was quite quick. Three hours from report to fix. Great job @Siedlerchr |
There does not seem a DOI fetcher in the web seach list at the moment. Has it changed his place? |
@bernhard-kleine All ID-based fetchers have been moved to the New Entry dialog |
DOI Fetcher is now in the new entry dialog as it fetches a single id only
|
Seen and tested. Thank you |
JabRef 3.6
windows 7 6.1 amd64
Java 1.8.0_66
Steps to reproduce:
I would expect utf8 encoding for the import since the medline has really a good way to deal with the alphas and betas, as well as any other greek letters or even japanese or other languages. While the utf8 encoding does well work in jabref, it is ?ommited? in the import. Please change.
The text was updated successfully, but these errors were encountered: