The bibtex export ist broken.
It is necessary to print the month.
The following code fragment needs to be put into biblio.import.export.inc:
if ($pub->biblio_date) {
$month=split("/",$pub->biblio_date);
if(count($month)!=2 && count($month)!=3) {
$month=$pub->biblio_date;
} else {
if(count($month)==2) {
$month=$month[0];
}else if (count($month)==3){
$month=$month[1];
}
// this is probably a bad hack to convert to int
$month=$month*1;
$month2str=array(1=>'jan',2=>'feb',3=>'mar',4=>'apr',5=>'may',6=>'jun',7=>'jul',8=>'aug',9=>'sep',10=>'oct',11=>'nov',12=>'dec');
$month=$month2str[$month];
}
$bibtex .= "\tmonth = {" . $month . "},\n";
}
Comments
Comment #1
Kounan commentedI seem to see the same issues. When exporting a biblio entry with a month, there's no month entry in the exported bibtex file.
On a related note, biblio has been having issues parsing the "month" field from bibtex entries and has been ignoring it. If more information is needed, please let me know. I don't know that much about Drupal so I don't know what kind of information you need.
EDIT: I'm using Biblio 6.x-2.0-beta3. Will try updating and see if it fixes things.
Thanks!
Comment #2
rjerome commentedCould you post a bibtex entry that you are having issues with so I can use it to test.
Comment #3
Kounan commentedAttached is the file with the bibtex entries. I've been fiddling with the first entry for the results, but biblio seems to be ignoring it. I've been using the import functionality and also have advanced import installed.
Comment #4
Kounan commentedActually, that's the result of using scons to compile everything into one file. The actual one with the entries I've been fiddling around is this one.
Comment #5
rjerome commentedI just tried importing that second file you attached and it seems to work fine for me (with the latest 6.x-2.x-dev).
Here are a couple of screen shots...
Comment #6
Kounan commentedThanks for the quick reply!
I'll try to update my module, and get back to you by the end of next week. If it's not an issue with Biblio I'll close the issue (cannot reproduce).
Comment #7
Kounan commentedTurns out my issue is not the same as the OP. There was some tinkering done in the module by my predecessor and she accidentally changed some variable names in the module, causing my issue. Don't think the OP's issue is fully resolved though so not closing this.
Comment #8
Kounan commentedTurns out my issue is not the same as the OP. There was some tinkering done in the module by my predecessor and she accidentally changed some variable names in the module, causing my issue. Don't think the OP's issue is fully resolved though so not closing this.
Comment #9
liam morlandThis version is no longer maintained. If this issue is still relevant to the Drupal 7 version, please re-open and provide details.