Ah, ok that makes sense. Guessing encodings can be a real pain. Thanks for looking into this.
Alan
Sent: Friday, September 06, 2024 at 8:39 AM
From: "Christiaan Hofman" <[email protected]>
To: "BibDesk users list" <[email protected]>
Subject: Re: [Bibdesk-users] Spurious characters from DOI import
From: "Christiaan Hofman" <[email protected]>
To: "BibDesk users list" <[email protected]>
Subject: Re: [Bibdesk-users] Spurious characters from DOI import
The problem seems to be that the DOI server does not tell us which incoming it is returning its data. And we seem to guess the wrong encoding. This will be improved in the next release.
Christiaan
_______________________________________________ Bibdesk-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bibdesk-usersOn 6 Sep 2024, at 11:18, Christiaan Hofman <[email protected]> wrote:The problem is with the DOI site, which provides us with the bibtex record.ChristiaanOn 6 Sep 2024, at 01:18, Alan Munn via Bibdesk-users <[email protected]> wrote:Hi, when I paste the following DOI into BibDesk,the resulting record looks like this:
@article{Miller_2012,
author = {Miller, Karen L. and Schmitt, Cristina},
date-added = {2024-09-05 16:26:28 -0400},
date-modified = {2024-09-05 16:26:28 -0400},
doi = {10.1080/10489223.2012.685026},
issn = {1532-7817},
journal = {Language Acquisition},
month = jun,
number = {3},
pages = {223�261},
publisher = {Informa UK Limited},
title = {Variable Input and the Acquisition of Plural Morphology},
url = "" href="http://dx.doi.org/10.1080/10489223.2012.685026" target="_blank">http://dx.doi.org/10.1080/10489223.2012.685026},
volume = {19},
year = {2012},
bdsk-url-1 = {http://dx.doi.org/10.1080/10489223.2012.685026}}As you can see, the pages field contains an odd character, but the problem is worse than that, it also contains two invisible characters, so the what ends up in the .bib entry is 226 (latin small a circumflex), 128 (PAD), 147 (STS = set transmit state). This causes various problems when doing other things with the bibiliography (in my case using pandoc to generate an html bibliography; see https://github.com/jgm/pandoc/discussions/10151#discussioncomment-10548191 for some discussion on the pandoc repo).Is this a problem with BibDesk's use of the scraped DOI data or is it coming directly from the DOI server itself?ThanksAlan
_______________________________________________ Bibdesk-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bibdesk-users
