Guidance on switching to Bookends
Posted: Fri May 03, 2019 6:50 pm
Hi all,
I've had a license for Bookends for some years (including v. 13), but a couple of years back switched over to Zotero. There were a bunch of reasons:
I've had a license for Bookends for some years (including v. 13), but a couple of years back switched over to Zotero. There were a bunch of reasons:
- the Better BibTeX addon. I generally have to use SBL citations, and there are some technicalities that only BibLaTeX-SBL handles correctly. These matter a great deal for my DPhil thesis, so I've switched to using Pandoc to write, BibLaTeX for citation processing. Better BibTeX has a very flexible .bib export including support for the custom item types I need for SBL, and also can be persuaded to deal well with different languages - even to the extent of giving the correct output for a JSON export vs a Bib export.
- the Zotfile addon is great.
- the Zutilo addon tidies up a few other things.
- the web page importer is awesome.
- because of the Zotfile options for naming PDFs well, I index them in DevonThink Pro and tend to access them there.
- having the PDFs named by Author, Date, and Title. Any thoughts on how I can do that?
- I use BetterBibTex's "extra" field quite a bit, to add in or override the default BibTeX export. For example, SBL style supports a Series abbreviation. By including I can get the correct BibTeX data for the SBL style, which automatically gets added to an index (i.e., this is very worthwhile for me). Any way to do something similar with Bookends' BibTeX export?
Code: Select all
bibtex { shortseries: "VTSupp"}
- does Bookends deal with other languages well? In Zotero, I can use a subset of HTML markup, e.g. with a language code to mark the language, and this gets transformed to appropriate TeX in a BibTeX export (while being retained for a JSON export). Some examples:
Code: Select all
<span class="nocase">a-na 1/2 GÍN-šú GAL-bi</span>
Code: Select all
<i>meʾat</i>
Code: Select all
Genesis = <span lang="he">ברשית</span>: the traditional Hebrew text with the new JPS translation
The last one is the only real language-specific one, and by hardcoding the BibTeX output I get the correct output in my LaTeX typesetting. The span generates the correct output for Pandoc's cite-proc on a JSON file. But for my field, preserving italics for transliterated terms (in this case, Akkadian) does matter.Code: Select all
bibtex{ title: "Genesis = \\texthebrew{ברשית}: the traditional {{H}}ebrew text with the new {{JPS}} translation" }