On Jun 26, 2011, at 5:13 PM, Cyril Georgy wrote: > > Le 26 juin 2011 à 23:08, Christiaan Hofman a écrit : > >> >> On Jun 26, 2011, at 22:28, Cyril Georgy wrote: >> >>> >>> Le 26 juin 2011 à 22:17, Christiaan Hofman a écrit : >>> >>>> >>>> On Jun 26, 2011, at 21:54, Cyril Georgy wrote: >>>> >>>>> Hello ! >>>>> >>>>> I have problem when I want to import paper from journals containing the >>>>> symbol "&" (e.g. astronomy & astrophyiscs). I try to import them from the >>>>> ADS web page, listing the paper in bibtex format. >>>>> All the paper appears and can be directly imported except those >>>>> containing this symbol, which do not appear. >>>>> >>>>> I recently re-install my whole system. I know that I did an operation in >>>>> my old installation fixing this problem, but don't remember what, and I'm >>>>> unluckily unable to re-find the information on the web.
...snip....
>
>> However, these characters can be parsed by our parser, so we could allow
>> these. Please test this out with tomorrow's nightly build.
>
> Ok, I will test that tomorrow !
>
>> BTW, there are more bibtex bugs in these items. Many use comma and "\&" to
>> separate author names, which is really wrong in bibtex, they should always
>> be separated with "and".
Should there be some kind of warning that the records to not conform to the
BibTeX format?
There is another similar issue I have encountered. Importing from the Library
of Congress, characters not in ASCII form are sometimes brought in. Then the
database cannot be saved. The error log usually will say what the problems are.
If there is more than one, the process of fixing records goes on, as each new
problem record is identified during the saving process.
I wonder, is there any way to create an alert when non-ASCII characters are in
a record, the alert coming up as the record is imported? And to provide a
little more feedback, for instance, giving the cite key of the problem record?
Waiting until the database is saved to find out that there is a problem is a
problem because I often save when I done working, but then don't have time to
troubleshoot, because I have to get on with what I intended to do when I
stopped working with the database.
>
> Of course, but I'm not responsible for these formats...
I really do have to say that I find it so astonishing that major producers of
BibTeX records like JSTOR cannot get these formats right. Rarely does a record
come into the database without my having to tinker with it. Something is always
missing or else wrong. I don't think the basic structure of a BT record is that
complicated.
\end{rant}
------------------
Adam M. Goldstein PhD, MSLIS
--
[email protected]
http://www.shiftingbalance.org
http://www.twitter.com/shiftingbalance
--
http://www.itis.gov/servlet/SingleRpt/SingleRpt?search_topic=TSN&search_value=180621
--
Associate Editor
Reviews Editor
Evolution: Education & Outreach
http://www.springer.com/life+sci/journal/12052
--
Spellman 205
(914) 637-2717 (msg)
--
Dept of Philosophy
Iona College
715 North Avenue
New Rochelle NY 10801
http://www.iona.edu/faculty/agoldstein
smime.p7s
Description: S/MIME cryptographic signature
------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2
_______________________________________________ Bibdesk-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bibdesk-users
