Zotero-better-bibtex: Book chapter citation using p. instead of pp.

[alvinyxz]

Hi Better Bibtex developer,

Thanks for your great work on improving Zotero's bib tex experience. I have a minor issue with the current citation style though.

According to APA 6th/7th, when citing a book chapter, the page number should be formatted as "pp. XX-XX." But currently when I am using Better BibTex and apacite as the LaTex citation style, the produced reference list uses "p. XX-XX".

So, instead of showing:
Faraj, S., & Azad, B. (2012). The materiality of technology: An affordance perspective. In P. M. Leonardi, B. A. Nardi, & J. Kallinikos (Eds.), Materiality and organizing: Social interaction in a technological world (pp. 237-258). Oxford University Press.

It is currently showing:
Faraj, S., & Azad, B. (2012). The materiality of technology: An affordance perspective. In P. M. Leonardi, B. A. Nardi, & J. Kallinikos (Eds.), Materiality and organizing: Social interaction in a technological world (p. 237-258). Oxford University Press.

Is there a simple way that I can change this?

[label-gun[bot]]

It looks like you did not upload an debug report. The debug report is important; it gives @retorquere your current BBT settings and a copy of the problematic reference as a test case so he can best replicate your problem. Without it, @retorquere is effectively blind. Debug reports are useful for both bug analysis and enhancement requests; in the case of export enhancements, I need the copy of the references you have in mind.

• If your issue relates to how BBT behaves around a specific reference(s), such as citekey generation or export, select at least one of the problematic reference(s), right-click it, and submit an BBT debug report from that popup menu. If the problem is with export, please do include a sample of what you see exported, and what you expected to see exported for these references.

• If the issue does not relate to references and is of a more general nature, generate an debug report by restarting Zotero with debugging enabled (Help -> Debug Output Logging -> Restart with logging enabled), reproducing your problem, and selecting "Send Better BibTeX debug report..." from the help menu.

Once done, you will see a debug ID in red. Please post that debug id in the issue here.

Thank you!

[retorquere]

BBT doesn't really deal with styles. Rendering of bibliography is done outside Zotero for bibtex references.

[alvinyxz]

Thanks for the reply. So I compared the bib file exported by Zotero (which shows "pp." in Latex) and the bib file exported by Better Bibtex (which shows "p." in Latex), and got this:

I suppose it's the difference between "269--286" and "269-286" that is causing the problem.

Is it possible to export items using two hyphens with Better Bibtex?

[retorquere]

Can you right-click that reference and send a debug log (see instructions from label-gun above)?

[alvinyxz]

Sure, the report ID is 98NJVCJX-euc

It is not only this specific reference. All items exported by Better Bibtex use "pages = {XXX-XXX}" while all items exported by Zotero use "pages = {XXX--XXX}"

[retorquere]

That's not unexpected, but this gives me a specific sample to look at (and if a fix is needed, a testcase to prevent regression)

[blip-bloop]

:robot: this is your friendly neighborhood build bot announcing test build 5.1.176.5496 ("fixes #1375")

Install in Zotero by downloading test build 5.1.176.5496, opening the Zotero "Tools" menu, selecting "Add-ons", open the gear menu in the top right, and select "Install Add-on From File...".

[blip-bloop]

:robot: this is your friendly neighborhood build bot announcing test build 5.1.176.5499 ("update test case")

Install in Zotero by downloading test build 5.1.176.5499, opening the Zotero "Tools" menu, selecting "Add-ons", open the gear menu in the top right, and select "Install Add-on From File...".

[retorquere]

Can you try 5499?

[alvinyxz]

I tried, and it works now! Thank you.

[github-actions[bot]]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.