From: Nicolas Goaziou <firstname.lastname@example.org> To: Denis Maier <email@example.com> Cc: org-mode-email <firstname.lastname@example.org>, Bruce D'Arcus <email@example.com> Subject: Re: [wip-cite-new] Initial implementation of `biblatex' citation processor Date: Wed, 19 May 2021 17:23:50 +0200 [thread overview] Message-ID: <firstname.lastname@example.org> (raw) In-Reply-To: <email@example.com> (Denis Maier's message of "Wed, 19 May 2021 16:31:02 +0200") Denis Maier <firstname.lastname@example.org> writes: > In that case, I'd think that note/bare => footcitecite isn't > a particular good fit. Footcitetext puts the citation in a footnote, > just that it doesn't print a footnote mark in a running text. > (This is useful in cases where the regular footnote mechanism in LaTeX > doesn't work, e.g. in headings or tables. In these cases you' can > place the mark manually with \footnotemark, and later you specify the > text with \footnotetext, or in that case with \footcitetext.) OK, I'll remove it. What about also removing \footcite altogether? We could simply automatically wrap the citation in a inline footnote before exporting the document. No need for a special command. Org already handles footnotes in headings and tables, so there may be no need to footcitetext either… > Regarding: >> | locators | bare | notecite | >> | locators | caps | Pnotecite | >> | locators | bare-caps | Notecite | >> | locators | | pnotecite | > > fnotecite should be added. Under what style/variant combination? >> One problem is there is no "\cite", or "\parencite". I though they would >> make a good fit for the default style, "\cite" being the "bare" variant >> of "\parencite", and "\autocite" could be moved to a "auto" style. I'm >> not sure where to put \cite, then. > > Why not just add a cite/parens style? OK. > \cite could be [cite/bare: ...] This would be confusing. So far, "bare" is a style variant. Your suggestion promotes it exceptionally to a full-fledged style. It hurts my logic. :) Could "\cite" be [cite/parens/bare:...] instead? > Regarding \autocite being the default: > I think one strong argument in favor of this is that people may want > to switch between different citation export processors. So if you > typeset your article with latex you may want to use biblatex. But if > the journal accepts submissions only as docx files you'll have to > switch to a CSL-based citeproc. Here, the default is to wrap the > citation either in a footnote or in parentheses, depending on the > style. > So, to ensure portability of documents across export systems [cite: > @doe] should give similar results with different systems, and I think > \autocite would be the best choice. (By the way, it's also the way > pandoc implements this.) Users can disregard any default style chosen by the processor. If I write: #+cite_export: biblatex whatever text all [cite:...] objects will create \textcite commands, no matter what the processor thinks about it. So, an hypothetical #+cite_export: biblatex foo auto could also turn all [cite:...] into \autocite commands and the document would be portable. The default processor style for citations is to be understood as a fall-back style, not necessarily as "the style associated to [cite:...]". Anyway, I don't have a strong opinion about autocite being the default. If it makes sense and we can put \cite elsewhere, let's use that. Regards,
next prev parent reply other threads:[~2021-05-19 15:24 UTC|newest] Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-05-18 15:13 Nicolas Goaziou 2021-05-18 18:40 ` Bruce D'Arcus 2021-05-20 7:22 ` Rudolf Adamkovič 2021-05-20 10:38 ` Bruce D'Arcus 2021-05-19 10:03 ` Denis Maier 2021-05-19 10:43 ` Bruce D'Arcus 2021-05-19 12:33 ` Denis Maier 2021-05-19 13:44 ` Nicolas Goaziou 2021-05-19 13:50 ` Bruce D'Arcus 2021-05-19 14:31 ` Denis Maier 2021-05-19 14:46 ` Bruce D'Arcus 2021-05-19 15:23 ` Nicolas Goaziou [this message] 2021-05-20 8:04 ` Denis Maier 2021-05-20 10:36 ` Bruce D'Arcus 2021-05-20 11:56 ` Bruce D'Arcus 2021-05-20 11:59 ` Bruce D'Arcus 2021-05-20 13:24 ` Denis Maier 2021-05-20 13:07 ` Denis Maier 2021-05-20 13:22 ` Bruce D'Arcus 2021-05-20 13:56 ` Denis Maier 2021-05-20 14:11 ` Bruce D'Arcus 2021-05-20 14:29 ` Denis Maier 2021-05-20 15:14 ` Bruce D'Arcus 2021-05-20 17:06 ` Nicolas Goaziou 2021-05-20 21:51 ` Denis Maier 2021-05-20 22:37 ` Thomas S. Dye 2021-05-20 22:51 ` Bruce D'Arcus 2021-05-21 0:07 ` Thomas S. Dye 2021-05-21 13:38 ` Nicolas Goaziou 2021-05-20 13:08 ` Denis Maier 2021-05-20 17:15 ` Nicolas Goaziou 2021-05-20 21:54 ` Denis Maier 2021-05-21 13:29 ` Nicolas Goaziou 2021-05-20 14:32 ` Denis Maier 2021-05-19 13:00 ` Denis Maier 2021-05-21 11:49 ` Bruce D'Arcus 2021-05-21 13:13 ` Nicolas Goaziou 2021-05-21 13:25 ` Bruce D'Arcus 2021-05-25 14:30 ` Bruce D'Arcus 2021-05-26 20:04 ` Nicolas Goaziou 2021-05-29 14:44 ` [org-cite, oc-csl] print_bibliography options Bruce D'Arcus 2021-05-29 15:15 ` Nicolas Goaziou 2021-05-29 16:03 ` Bruce D'Arcus 2021-05-29 16:30 ` Nicolas Goaziou 2021-05-31 18:10 ` András Simonyi 2021-05-31 21:54 ` Bruce D'Arcus
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style List information: https://www.orgmode.org/ * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: [wip-cite-new] Initial implementation of `biblatex'\'' citation processor' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
Code repositories for project(s) associated with this inbox: https://git.savannah.gnu.org/cgit/emacs/org-mode.git This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).