I wanted to see if I could code the Cited Pages from the Edit&Manage citation option into a Vancouver numbered style, but I ran into a few issues. For it to properly show the brackets around the numbers and automatically choose between p or pp, it needed an extra space at the end. But somehow this disabled the grouped citation (eg 1-3) option when not Cited Pages were used.
Is this normal? I tried any other way, but the closing bracket just somehow ended up around the last citation number otherwise, and not behind the page number until I used the link operator.
For the Author (Year) option (that displays like Name superscript number), it was less important to have the display as it’s hardly used.
I know a way to bypass this is just putting the page number example written as (p2-4) into the suffix, but I was wondering what Cited Pages is otherwise for if I can’t use it for the template.
It is highly unusual to use cited pages with a superscripted bibliography number. Is that what you are trying to do?
Also I remember having issues with parentheses and cited pages in citations alot, particularly in numbered styles, but even in author year styles. (see Numbered references in alphabetical order thread for example). It probably has something to do with punctuation handling rules and developers not testing some scenarios. Also, that citations can be groups of citations, and not always stand alone. All in all, I think there is still an inherent glitch. I really think your “bypass” option is the best way forward. Since you have to manually enter cited pages anyway. As to “why” - it seems to work within parentheses when using the Author(Year) type of citations, but with numbers or leaving them alone in parentheses, there is some unsolvable glitch.
Hi Leanne, yes that’s what we were trying to do as it’s an exception we wrote into our citation style guide that in certain circumstances you can mention the page number if you wanted to specifically highlight the info.
It does seem to be a glitch. I guess the bypass suffix option works best in that circumstance then. Thanks for your reply
