On 29 February 2012 16:04, Lester Ingber <[email protected]> wrote: > Hi. When my .bib file is opened, some entries are flagged as problematic > (but I don;t know why; they are OK in Bibliography Manager). A duplicate is > flagged, as I expected it to be. However, the other entries are "Skipped" > and not entered into the fields.
Ok, I see. This message comes because these entries are malformed. As the warning message indicates, it is caused by a missing comma. If you open the bib file in a text editor and look at the two line numbers that are given, you'll see the problem. Each field is terminated by a comma at the end of its line, but in two (I think) cases the comma is missing. It might be possible to make the parser read these entries despite these errors, but I'm not sure if that's the way to go - we want to encourage correctly formatted files, after all. Was this file produced by Bibliography Manager, or has it been edited by hand at some point? -- Morten ------------------------------------------------------------------------------ Virtualization & Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ _______________________________________________ Jabref-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jabref-users
