I use JabRef on Windows 7 64 bit. The option for the .bib-file is set to UTF8. When I use the DOI to BibTeX feature in Jabref and import any DOI that leads to a source with special characters in its properties, say this one ...
... I get this result on Windows (version 2.9):
... it's the same with 2.10 beta3 on Windows:
... and the same for the final release for 2.10 for the doi
Here is a screenshot of the saved file opened in Notepad++:
It is working on Linux (Xubuntu 13.10 with version 2.10 beta):
Here are my options, which are equal for both installations (imported the options file into the other installation):
However I'd like to stay with utf-8-encoded files and try not to rework the faulty entries. Is there some way to have the .bib-file in utf-8 and still use the DOI to BibTeX feature? It's a bit odd JabRef can load the .bib-file which is already encoded in utf-8 but when I add something, it produces the faulty parts.
The thing is, whether I open a .bib-file saved by JabRef on either Windows or Linux, Notepad++ says (in the lower right) it is encoded Ansi as UTF-8 so I'm quite confused what is actually causing this if there aren't any encoding issues.