translators VS styles

> `` tags "using the Google/Highwire key-value system" sounds prommising -- but I'm having trouble finding a list of valid keys at the documentation linked to!

They're in the Indexing section of the linked Google page, just formatted in a particularly unreadable manner:

https://scholar.google.com/intl/en/scholar/inclusion.html#in...

That will let you specify a PDF (`citation_pdf_url`) as well.

Should be mostly self-explanatory, but you can see Zotero's mappings here:

https://github.com/zotero/translators/blob/b18eeac0f770c698f...

> I wish there was a way I could provide the cite in CSL!

We're planning to support `` elements to any supported format — basically a modern replacement for unAPI, which went defunct before CSL could be listed as an option — but CSL wouldn't let you specify a PDF anyway. And most sites want the search engine indexing they get from embedded metadata.

Looks like the Zotero devs have already done that [1]. You can probably just vendor the repo in a browser extension, I'd think.

[1] https://github.com/zotero/translators

JavaScript translators created with the visual editor (although probably less reliable than translators created by an experienced JS developer) will be compatible with Zotero's translation server, and could be further refined to be posted for review to the Zotero's translators repository.

I had some trouble following this but I think what you're saying is the ` [@Bernhofer2021.02.23.432527]` tag isn't getting converted to the actual bib reference - is that right? I just copied this into my system and I could make that part work fine - using my own .bib file of course, and I used this csl which I copied locally. The one change I made to the setup was to put both the .bib and the .csl file in my working directory where the .qmd file is, and also as I commented on a different post of yours from the other day, I make sure there's no spaces in the path to my working directory (for either the folder names or the filenames). So for me, everything is in C:\Users\xxxx\workingdir - this is due to a known RStudio issue with spaces. Who knows if that's what you're running into or not.

Seems like in that case you need to use the csl export processor instead of the default basic -- see the instructions at https://ox-hugo.scripter.co/doc/org-cite-citations/. The default CSL style shipped with Org is Chicago author-date. For numbered citations you will need to use a different CSL style, for instance, ieee-with-url.

Both should. See https://citationstyles.org/

;; Currently only using csl (use-package oc-csl :after oc :init ;; make sure to download csl ;; https://citationstyles.org ;; https://github.com/citation-style-language ;; repos for styles & locales (setq org-cite-csl-styles-dir "~/path/to/csl/styles") (setq org-cite-csl-locales-dir "~/path/to/csl/locales")) ``` Make sure apa7 is part of the csl styles dir that you're setting. Then you just need this in your org document or referenced by that document:

You can use the BetterBibtex plugin to export the references to a bib or json file which can be ingested by Pandoc. There's an option to have it re-export the file every time you make a change to the library.

Citations work pretty well. You can customize the output with different CSL files [1].

[1] https://citationstyles.org/

PS: i found out this link with many medley reference styles: https://github.com/citation-style-language/styles

The bibliography.bib file is your exported bibtex file. The style.csl file is the citation style for the targeted journal (they can all be found here: https://github.com/citation-style-language/styles)

In addition, there are dozens of auxiliary features like searching & downloading citation styles from the Citation Style Repository or an "anticipatory" word count (i.e., calculating the word count a document would have when the bibliography has been added, a feature that virtually all markdown writing apps lack).