Abbreviation in footnote leads to suppression of semicolon

I have the following problem: in my footnote, I want my source to look like this "first source, p. 27 f.; next source" - the "f." stands for "following pages".
Unfortunately, if I put "f." as a suffix to the page, the semicolon between the two sources will disappear. If I put "f.;" as a suffix to the page, there will be two semicolons between two sources.
Can anyone tell me how I can fix this?
  • edited February 26, 2019
    I can't easily reproduce that in the test suite (I tried with the page and locator variables in a simple snippet of CSL). I'll need more detail.
  • edited February 26, 2019
    @fbennett Thank you so much for trying! What details do you need?
    This is how part of my CSL-thing (I am sorry for the amateur-language, I am definitely not a pro at this) looks:

    citation
    layout delimiter="; " suffix="."
    choose
    ...
    else-if type="book"
    group delimiter=", "
    text macro="autor-editor-note"/
    text variable="title" form="short"/
    text macro="locator-with-label"/
    /group
    /else-if

    Please imagine the "<"/">"-signs, because the page will not post my comment, if I put the code in.

    If I use the Zotero-Add-In for Microsoft Word, then I can choose my (multiple) source(s) and a mask will open, where I can put in the page-number and an individual prefix/suffix. If I put "f." as a suffix to my first source, but also have additional sources, then it should look like this in the citation (footnote): "author, title, p. 27 f.; author, title, p. 23 f.; author, title,... ." - unfortunately it looks like this: "author, title, p. 27 f. author, title, p. 23 f. author, title,... ."

    Does this help? Thank you in advance!
  • We would need to have the full style file to say anything definite. Before that, though, have you validated the style?

    https://validator.citationstyles.org/
  • edited February 26, 2019
    @fbennet Yes, I have just now and corrected a few small things.

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.