From: "Bruce D'Arcus" <bdarcus@gmail.com>
To: "Bruce D'Arcus" <bdarcus@gmail.com>,
"Org Mode List" <emacs-orgmode@gnu.org>,
"András Simonyi" <andras.simonyi@gmail.com>
Subject: Re: [org-cite, oc-csl] print_bibliography options
Date: Sat, 29 May 2021 12:03:51 -0400 [thread overview]
Message-ID: <CAF-FPGNmRVHNHRbSteU+pOc9m-ovwjAu4YRCw_fDL_SecEvEqA@mail.gmail.com> (raw)
In-Reply-To: <87wnrhzi3o.fsf@nicolasgoaziou.fr>
On Sat, May 29, 2021 at 11:15 AM Nicolas Goaziou <mail@nicolasgoaziou.fr> wrote:
>
> Hello,
>
> "Bruce D'Arcus" <bdarcus@gmail.com> writes:
>
> >> Bibliography is printed using "\printbibliography" command. Additional
> >> options may be passed to it through a property list attached to the
> >> "print_bibliography" keyword. E.g.,
> >>
> >> #+print_bibliography: :section 2 :heading subbibliography
>
> > I don't believe citeproc-el currently supports any of these features,
> > and it looks like the citeproc-el API doesn't even have an optional
> > parameter to put details like these.
> >
> > As a consequence, if one adds an example like the above, so that one
> > has two print_bibliography lines, one will get two, duplicate
> > bibliography lists outside of oc-biblatex.
>
> I don't understand how you reach that consequence… If the citation
> processor does not understand the properties, it simply ignores them,
> but obeys to "print_bibliography" directive anyhow.
>
> Have you tried it? I'm not sure to understand your concern.
Yes.
I think we're saying the same thing, but maybe I need to clarify the
implications better?
See below.
Let me illustrate with a full example, where the @einstein entry has a
"keyword" field of "primary."
The use case is a user wanting a bibliography with two sections, which
is a common case for this feature.
Note that I am unsure of the exact invocation to achieve this with
biblatex (as in, it's probably wrong), but I don't think that matters
to illustrate the point.
>>>>>
#+language: en
#+bibliography: test.bib
#+cite_export: csl
1. simple: [cite:@latexcompanion]
2. primary source: [cite:@einstein]
3. affixes: [cite/text:see @latexcompanion chapter 2 p.23]
4. quote, punctuation: “my quote” [cite/text/caps:@latexcompanion].
* Bibliography
** Primary Sources
#+print_bibliography: :keyword primary :title "Primary Sources"
** Secondary Sources
#+print_bibliography: :title "Secondary Source"
<<<<<
Here's the output from oc-csl:
>>>>>
1. simple: (Goossens, Mittelbach, and Samarin 1993)
2. primary source: (Einstein 1905)
3. affixes: (see Goossens, Mittelbach, and Samarin 1993, chaps. 2 p.23)
4. quote, punctuation: “my quote” (Goossens, Mittelbach, and Samarin
1993).
1 Bibliography
══════════════
1.1 Primary Sources
───────────────────
Einstein, Albert. 1905. “Zur Elektrodynamik Bewegter Körper. (German)
[on the Electrodynamics of Moving Bodies].” /Annalen Der Physik/ 322
(10):891–921.
Goossens, Michel, Frank Mittelbach, and Alexander Samarin. 1993. /The
LaTeX Companion/. Reading, Massachusetts: Addison-Wesley.
1.2 Secondary Sources
─────────────────────
Einstein, Albert. 1905. “Zur Elektrodynamik Bewegter Körper. (German)
[on the Electrodynamics of Moving Bodies].” /Annalen Der Physik/ 322
(10):891–921.
Goossens, Michel, Frank Mittelbach, and Alexander Samarin. 1993. /The
LaTeX Companion/. Reading, Massachusetts: Addison-Wesley.
<<<<<
So two duplicate lists.
Does that clarify?
The other common case I am familiar with is a bibliography per section
of a document.
It may not be practical to do anything other than current behavior,
but I was hoping some biblatex experts might have some thoughts.
And, of course, wanting to flag this for András to think about, since
ideally citeproc-el would support this.
Bruce
next prev parent reply other threads:[~2021-05-29 16:04 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-18 15:13 [wip-cite-new] Initial implementation of `biblatex' citation processor 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
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 [this message]
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 \
--in-reply-to=CAF-FPGNmRVHNHRbSteU+pOc9m-ovwjAu4YRCw_fDL_SecEvEqA@mail.gmail.com \
--to=bdarcus@gmail.com \
--cc=andras.simonyi@gmail.com \
--cc=emacs-orgmode@gnu.org \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public 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).