SBL style error

NickaMeyer
SBL citation style produces footnotes with editor and translator information like this (ignore missing italics):

Walther Zimmerli, Ezekiel: A Commentary on the Book of the Prophet Ezekiel (ed by. Paul D. Hanson and Leonard Jay Greenspoon; trans by. James D. Martin; Minneapolis: Fortress Press, 1983), 1:124

Note "ed by. ..." and "trans by. ...".

Is someone able to fix this and update the style?

Thanks!
  • NickaMeyer
    I should note the correct format

    "(ed. Paul D. Hanson...)" and the same for translator.
  • NickaMeyer
    fixed! thanks!
  • adamsmith
    you mean you managed to fix this yourself or it's fixed for the style on the repository. Bc I don't think the latter is true.
  • NickaMeyer
    i didn't fix it myself. i'm not sure what happened. i thought i was working with the latest version, because I tried to reinstall it earlier and nothing changed, but perhaps not for after the last reinstall it works. and yet the date on the style in the repository does not indicate that it was changed today. probably then my first attempt at updating didn't work.
  • dstark
    In the v. 5.0.7, the current SBL style seems to have lost the ability to convert the same editor(s) and translator(s) to an "ed. and trans." notation . Thus:
    Hans-Georg Gadamer, Philosophical Hermeneutics, ed. David E. Ligne, trans. David E. Ligne, 1st paperback ed. (Berkeley: University of California Press, 1977).
    Hans-Georg Gadamer, Truth and Method, ed. Joel Weinsheimer and Donald G. Marshall, trans. Joel Weinsheimer and Donald G. Marshall, 2nd ed., Bloomsbury Revelations (London: Bloomsbury Academic, 2013).
    But, the notes should read:
    Hans-Georg Gadamer, Philosophical Hermeneutics, ed. and trans. David E. Ligne, 1st paperback ed. (Berkeley: University of California Press, 1977).
    Hans-Georg Gadamer, Truth and Method, ed. and trans. Joel Weinsheimer and Donald G. Marshall, 2nd ed., Bloomsbury Revelations (London: Bloomsbury Academic, 2013).
    Would it be possible to add the fix for this change back to the citation processor?

    Thanks so much!
  • damnation
    What style is this?
  • dstark
    SBL: https://www.zotero.org/styles/society-of-biblical-literature-fullnote-bibliography.
  • adamsmith
    (I won't be able to test this for a while, but given dstark's description, I'd be pretty sure this is an issue for @fbennett rather than a style issue)
  • bwiernik
    Yes, the style is correct, so it appears to be a citeproc-js issue.
  • fbennett
    edited August 1, 2017
    In the examples above, the editor and translator are rendered by the container-contributors-node macro, at lines 85-94:

    <macro name="container-contributors-note">
    <choose>
    <if type="bill book chapter graphic legal_case legislation motion_picture paper-conference report song" match="any">
    <names variable="editor translator container-author" delimiter=", ">
    <label form="verb-short" suffix=" "/>
    <name and="text" delimiter=", "/>
    </names>
    </if>
    </choose>
    </macro>

    Editor and translator will collapse only if exactly editor and translator are called via cs:names—at least that is my reading of the relevant portion of the CSL Specification. In this case, there is a third variable in the call, container-author. That's a valid CSL variable (although not linked to any Zotero variable as far as I know), but as a third variable in the call, it will break the editor-translator collapse.

    If this worked before, that would have been a bug that was somehow being masked. Removing container-author should restore collapsing. If you need to call the container-author variable, it should be called in a separate cs:names element.
  • bwiernik
    (container-author is what the Zotero bookAuthor variable is mapped to.)
  • fbennett
    Good to know -- my mapping tables must be out of date. But in either case, it needs to be removed from that construct for collapsing to work.

This is an old discussion that has not been active in a long time. Before commenting here, you should strongly consider starting a new discussion instead. If you think the content of this discussion is still relevant, you can link to it from your new discussion.

Sign In or Register to comment.