From: "András Simonyi" <firstname.lastname@example.org>
To: Ihor Radchenko <email@example.com>
Cc: emacs-orgmode list <firstname.lastname@example.org>
Subject: Re: [PATCH] oc-csl: Add support for sub-bibliographies
Date: Fri, 29 Jul 2022 21:51:27 +0200 [thread overview]
Message-ID: <CAOWRwxBWo2_wXat+YehRaoM6BET8jV67qZDH6gOUxCb_FRt7oA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1006 bytes --]
On Fri, 29 Jul 2022 at 03:32, Ihor Radchenko <email@example.com> wrote:
> This is an important point. I think that we should describe this gotcha
> in the "Bibliography printing". oc-basic and oc-csl just print the list
> of bibliography entries, while oc-bibtex/oc-natbib/oc-biblatex insert a
> separate section. It is a very important information and users should be
> aware of it.
I agree, so I've attached a new version in which a sentence is added
about this difference in behaviour.
Also, this is kind of annoying - this way mixing oc-bibtex
> and oc-basic for LaTeX and non-LaTeX export gets awkward.
Yes, in the long run we might want to unify the behaviour of the
processors in this respect. OTOH changing "basic" and "csl" to
automatically print a heading would be a breaking change, e.g., AFAIK,
ox-hugo currently adds a heading on its own when org-cite is used for
bibliography printing with the "csl" processor.
[-- Attachment #2: 0001-doc-org-manual.org-Document-PRINT_BIBLIOGRAPHY-optio.patch --]
[-- Type: text/x-patch, Size: 3637 bytes --]
From b765d8bd65ece076041b8c280c0a7f076a376338 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Andr=C3=A1s=20Simonyi?= <firstname.lastname@example.org>
Date: Thu, 28 Jul 2022 22:50:26 +0200
Subject: [PATCH] * doc/org-manual.org: Document "PRINT_BIBLIOGRAPHY" options
doc/org-manual.org | 63 +++++++++++++++++++++++++++++++++++++++++++++-
1 file changed, 62 insertions(+), 1 deletion(-)
diff --git a/doc/org-manual.org b/doc/org-manual.org
index 596ab3723..9ec49c14e 100644
@@ -16818,11 +16818,72 @@ conformant to the Harvard style and the specification of the
Wolkers-Kluwer publisher; since it relies on the ~bibtex~ processor of
your LaTeX installation, it won't export to anything but PDF.
+** Bibliography printing
The =PRINT_BIBLIOGRAPHY= keyword specifies where the bibliography
+should be printed (note the colon):
+The bibliography printed by the LaTeX-based export processors
+"bibtex", "natbib" and "biblatex" has a chapter or section heading by
+default, while the "basic" and "csl" processors print the list of
+bibliography entries without a heading.
+A document may contain more than one =PRINT_BIBLIOGRAPHY= keywords.
+Each of the keywords will trigger printing the bibliography.
+The keywords can be used with or without additional options. Options
+can be used, for example, to print only entries that belong to a
+certain category or to control formatting. The set of supported
+=PRINT_BIBLIOGRAPHY= options and their interpretation varies between
+the different citation export processors. Some export processors do
+not support passing options.
+*** Bibliography options in the "biblatex" and "csl" export processors
+The "biblatex" and "csl" export processors support bibliography
+options through a property list attached to the =PRINT_BIBLIOGRAPHY=
+keyword. For example,
+: #print_bibliography: :keyword algebra :type book
+Values including spaces must be surrounded with double quotes. If you
+need to use a key multiple times, you can separate its values with
+commas, but without any space in-between:
+: #print_bibliography: :keyword "algebraic logic" :nottype article,book
+The "biblatex" export processor accepts all options supported by
+BibLaTeX's ~\printbibliography~ command, while the "csl" processor
+accepts the following ones:
+- =:keyword <keyword(,keyword2...)>= :: Print only entries whose
+ keyword field contains all given keywords.
+- =:notkeyword <keyword(,keyword2...)>= :: Print only entries whose
+ keyword field does not contain any of the given keywords.
+- =:type <entrytype>= :: Print only entries whose type is
+ =<entrytype>=. Entry type is the BibTeX/BibLaTeX entry type if this
+ information is available (the entry was read from a BibTeX/BibLaTeX
+ bibliography) and the CSL entry type otherwise.
+- =:nottype <entrytype(,entrytype2...)>= :: Print only entries whose
+ type is not among the given entry types. Entry type is determined
+ as in the case of =:type=.
+- =:csltype <entrytype>= :: Print only entries whose CSL entry type
+ (possibly based on a conversion from BibTeX/BibLaTeX to CSL) is
+- =:notcsltype <entrytype(,entrytype2...)>= :: Print only entries whose
+ CSL entry type (possibly based on a conversion from BibTeX/BibLaTeX
+ to CSL) is not among the listed entry types.
+- =:filter <predicate>= :: Print only entries for which the given
+ Emacs Lisp predicate returns a non-~nil~ value.
* Working with Source Code
:DESCRIPTION: Export, evaluate, and tangle code blocks.
next prev parent reply other threads:[~2022-07-29 19:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-11 22:13 András Simonyi
2022-07-16 8:44 ` Ihor Radchenko
2022-07-20 22:03 ` András Simonyi
2022-07-21 6:06 ` András Simonyi
2022-07-23 4:00 ` Ihor Radchenko
2022-07-23 20:10 ` András Simonyi
2022-07-24 7:42 ` Ihor Radchenko
2022-07-25 18:18 ` András Simonyi
2022-07-25 18:44 ` Bruce D'Arcus
2022-07-26 6:23 ` Fraga, Eric
2022-07-26 5:38 ` Ihor Radchenko
2022-07-28 21:36 ` András Simonyi
2022-07-29 1:33 ` Ihor Radchenko
2022-07-29 19:51 ` András Simonyi [this message]
2022-07-31 2:33 ` Ihor Radchenko
2022-08-02 10:53 ` András Simonyi
2022-07-31 2:28 ` Ihor Radchenko
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).