I just realized that the @STRING declarations in my bibfile are not exported to the subdatabase generated with JabRef based on an AUX file, which results in an invalid subdatabase.
The corresponding command line command is jabref --nogui --aux=report.aux,report.bib literature.bib where report.bib is a subdatabase of literature.bib Searching for this issue I discovered the JabRef bug report with ID 2357299 from 2008-11-28: http://sourceforge.net/tracker/index.php?func=detail&aid=2357299&group_id=92314&atid=600306 It seems that this old bug report has been overlooked until now, because the problem still persists with the current version 2.8 of JabRef. I would appreciate if this could be fixed, because it makes the subdatabase functionality useless when working with strings. A rapid solution would be to just copy all of the strings to the subdatabase, ignoring for the moment that not all of them might be used therein; but at least the resulting subdatabase would then be valid. Thanks a lot to the developers! Best regards, Wastl ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Jabref-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jabref-users
