Upgrade Storagenickbart
About
- Username
- nickbart
- Joined
- Roles
- Member
Comments
-
I fully agree with @bwiernik and @adamsmith, but I would like to add what I think is the most important aspect: @case is definitely not a recognized type in either biblatex or biblatex-apa, as should be sufficiently clear from the biblatex and bibla…
-
Even if BBT continues to export Zotero’s language fields to biblatex’s langid fields, and never to language, which I maintain is the only sensible way, the biblatex langid tags can still be used to selectively generate language fields that produce t…
-
I disagree. Zotero's "language" field should be exported to the biblatex field "langid" only. Both fields are supposed to contain only language tags that control formatting, e.g. capitalization of titles and hyphenation. Biblatex's "language" fie…
-
There are CSL-based solutions, but in particular for individuals known to prefer their names being sorted on the particle, or where it is customary to do so, the best solution is to enclose the string in Zotero’s "Last name" field in quotation marks…
-
Nothing in Zotero itself, AFAICS. But editor is a valid CSL variable, so there’s always the option of including it in the Extra field (using the so-called cheater syntax, supported by citeproc-js, Zotero’s processor; see https://citeproc-js.readthed…
-
Right, as is, you’d get “Smith & Jones” with apa.csl. But there’s a lua filter (https://github.com/crsh/rmdfiltr/blob/master/inst/replace_ampersands.lua) that can transform this to “Smith and Jones” (with [as of yet limited] multilingual support…
-
Actually, there’s an even simpler format for generating narrative citations in pandoc (provided the year is to appear right after the author(s)): Just write @salas_dagostino2020, without any square braces.
-
If the preferred form is indeed lower-case, you could also wrap the last name in double quotes, like this "dos Santos". This prevents the “dos” from being parsed as a particle at all.
-
I meant “command line” in a very broad sense (like, for example, the pandoc-zotxt filter, which requires a running instance of Zotero, too). And you’re right, I’m primarily curious whether it can be done at all. For merely testing whether bib(la)…
-
In case not using LaTeX is not an option here, could Zotero Better BibTeX (BBT), or some spin-off, be used to convert a CSL JSON file to a Bib(La)TeX file, possibly via the command line? As far as I know, BBT and pandoc-citeproc are the only biblio…
-
Just checked again (with an up-to-date Zotero + LO, no Propachi): an adjusted version of chicago-author-date.csl does fix the issue; the current version from the repository does not.
-
Maybe I’m missing something, but is there any reason why the official chicago-author-date.csl shouldn’t be updated accordingly?
-
@adamsmith This is different from a named volume in a multi-volume work, right? Absolutely. It’s no different from a book section actually, but because of its publication history (originally published as a book) convention demands that it be formatt…
-
@Ayerbender – You’ll have to add a string like “original-author: foo” to the “Extra” field. (So-called “cheater syntax”, specs here: https://citeproc-js.readthedocs.io/en/latest/csl-json/markup.html#cheater-syntax-for-odd-fields.) In fact, you cou…
-
One somewhat hackish solution for having titles italicized rather than wrapped in quotes would be to add a flag to such “bookinbook” items by assigning an arbitrary value to an otherwise unused variable, say original-author, and, in the CSL style fi…
-
zbib.org does not seem to accept shortDOIs (see http://shortdoi.org/). I feel shortDOIs should be treated as first class citizens, just like conventional (long) DOIs, so it would be great if zbib could be made to accept them.
-
@fbennett – With an adjusted chicago-author-date.csl and propachi-vanilla-v1.1.120-fx.xpi, the results are as expected now.
-
I tried propachi-vanilla-v1.1.120-fx.xpi together with the latest chicago-author-date.csl, but it seems there’s still no semicolon in cases where page numbers are involved: Expected: Blah (Doe 1986, 12–34; 1998, 77). Actual output: Blah (Doe 198…
-
My understanding is that (Condit et al. 2000, 1995, 1998; Connell 1971; Cortes & Hunziker 1971) actually is the correct form according to http://chicagomanualofstyle.org/book/ed17/part3/ch15/psec030.html (unchanged from CMoS, 16e, 15.29), which …
-
I find being able to have BBT auto-export saved searches very useful, too. This worked nicely with Zotero 4/BBT, and it’s a pity it’s broken with Zotero 5.
-
Well, in fact you can: Put `issued: 2018?` in the “Extra field”, and use a style like water-sa.csl to see for yourself. It’s just the CMS styles that would need to be patched.
-
A possible workaround for classical references (that does involve editing the style though) could be to tag classical works via an otherwise unused variable by entering, say, `original-author: classical` into the “Extra” field. In the style file, yo…
-
Thank you. Same style, different issue: It seems that the pandoc issue described at https://github.com/jgm/pandoc-citeproc/issues/45 can be fixed by using the macro “issue-note-join-with-space” instead of “issue-note-join-with-comma” for the item t…
-
Exact steps: Insert ZWS at the end of a first name field, leave that field, wait a few seconds, return to the field, copy the field’s content, paste into some editor with “show invisibles” enabled – the ZWS is gone. Reason for using ZWS: citeprocs …
-
> Does the problem occur if you disable the automatic shortDOI lookup preference? Yes. I also tried this with all other addons disabled (except for Zotero LibreOffice Integration), and the effect continues to occur when Zotero DOI Manager is ena…
-
Zotero DOI Manager, if enabled, seems to trigger the removal of zero-width space chars from author fields in Zotero (previously reported at https://github.com/bwiernik/zotero-shortdoi/issues/2). Disabling Zotero DOI Manager removes this effect. Not…
-
10/djhg26 (and 10.1017/S1380203807002140) work as expected for me (using plain Zotero).
-
Big improvements, again: thank you. Just a few more very minor suggestions and observations: An attempt to retrieve or check an invalid DOI sets the “_Invalid DOI” tag. Conversely, it would seem useful to clear that tag after any successful retriev…
-
The most recent version, Zotero DOI Manager 1.1.1, seems to show a lack of visible response or feedback in some cases: valid long DOI, e.g., 10.1109/5.771073: - Get shortDOIs → shortDOI appears in < 1 sec - Verify and clean DOIs → no visible res…
-
Ok, good to know. (Indeed there was a “%2F” involved, though it doesn’t show up in my post above in the view [as opposed to edit] mode.)