We've just added another style customization option: "commas". When present, replaces semicolons with commas, and "and" with "&", e.g.,

Graham, R. L., Knuth, D. E., & Patashnik, O.

instead of

Graham, R. L.; Knuth, D. E.; and Patashnik, O.

Hi Carol,

I think this is indeed a matter of style and taste, but I agree that the option should at least exist. So we've gone ahead and added a new customization option to do just that. You can now add "&commas=true" to your bibbase url. It will then use commas instead of semicolons, and ampersands instead of the "and".

Thanks for the suggestion!

Hm, I get a "Page not found" when opening that link. Is it public?

Sorry, DJ, I can't quite parse the images. Could you point me to the page where this is happening? It will be easier for me to see there what might be going on.

No, sorry, that's not yet supported. Perhaps the closest would be to use full names using &fullnames=1.

This is a known issue for some people. There is probably a conflict between some of the libraries bibbase uses and the ones you are already using on your page. It's best in those cases to just hide those dropdowns using CSS:

#bibbase_header {
     display: none;
}

That one is easy. You can just add "&authorFirst=1" to the bibbase url. For more details see the customization options described in our documentation.

Actually nevermind, @strings are supported but were only working for lower-case string names. We've just pushed a fix for that to make them work for upper-case names as well. Your bib is now rendering fine.

Hi Marcus!

@string expressions are not currently supported, but I think it would be a valuable feature to add. I'll investigate how much work that would be.

See below.

Carol, I'm no longer sure what you are asking.

 accent acute, quotes, etc, that are coded in this manner: {\textopenbullet}. None read correctly.

Accent acute and quotes in latex are not created using `\textopenbullet` -- I don't even know that command, so of course that won't produce quotes or accent acute in bibbase either. But most special characters do work if that's your question.

@conference works on some, but not all of these.

That tag is not valid bibtex and is not supported by BibBase, I don't think. But inbook is. 

Perhaps I could help better if you pointed me at your web site. Then maybe I can see what the issue is.