From: Edgar Lux <edgarlux@mailfence.com>
To: emacs-orgmode@gnu.org
Subject: Re: [BUG] #+cite_export: ... bibstyle citestyle cannot be universally used as global defaults (was: Patch for \usepackage[ ... natbib = true ...]{...biblatex} with org-cite)
Date: Fri, 3 Feb 2023 10:33:54 +0100 (CET) [thread overview]
Message-ID: <746321315.112536.1675416834079@ichabod.co-bxl> (raw)
In-Reply-To: <87fsc05hkl.fsf@localhost>
On Jan 24, 2023 at 11:54 AM, Ihor Radchenko <yantar92@posteo.net> wrote:Edgar Lux <edgarlux@mailfence.com> writes:
> I understand. My takeaway from here is that there is a need to provide
> extended global defaults for both bibliography style and citation style.
>
> Which is a questionable design choice. I was referring to higher-level
> docstring for `org-cite-export-processors':
>
> (NAME BIBLIOGRAPHY-STYLE CITATION-STYLE)
>
> There, NAME is the name of a registered citation processor providing
> export
> functionality, as a symbol. BIBLIOGRAPHY-STYLE (respectively
> CITATION-STYLE)
> is the desired default style to use when printing a bibliography
> (respectively
> exporting a citation), as a string or nil. Both BIBLIOGRAPHY-STYLE and
> CITATION-STYLE are optional. NAME is mandatory.
>
> oc-biblatex simply deviates from the global paradigm, making oc-biblatex
> special compared to other citation processors. Not ideal.
>
> I think that we have a fundamental design flaw with org-cite:
>
> #+cite_export: processor bibliography-style citation-style
>
> introduces:
>
> - default bibliography style set document-wide
> - default citation style set individually in every citation via
> low-level commands, BUT NOT GLOBAL DEFAULT CITATION STYLE.
>
> Basically, CITATION_STYLE cannot currently affect document preamble by
> design.
>
> That's why awkward workarounds in oc-biblatex, where default citation
> style can be set globally, and we have to attach citation style to
> BIBLIOGRAPHY_STYLE keyword.
>
> I suggest the following changes to the org-cite:
>
> 1. :export-finalizer should accept export processor triplet instead of
> bibliography style as 4th argument. The assumption that only
> bibliography style is required to finalize the export is clearly not
> accurate.
>
> 2. Allow passing extra arguments in #+cite_export:
>
> #+cite_export: processor[opt1=val1,opt2=val2,...] bibliography-style[...]
> citation-style[...]
>
> The options listed within the square brackets will pass extra default
> options
> to the processor/styles and used as needed by citation processor
> implementations.
>
> WDYT?
> --
> Ihor Radchenko // yantar92,
> Learn more about Org mode at <https://orgmode.org/>.
> Support Org development at <https://liberapay.com/org-mode>,
> or support my work at <https://liberapay.com/yantar92>
Dear Ihor and Org mailing list,
I wanted to answer last weekend, because I had the intention to contribute a little in terms of code. However, I was very busy, and I will be very busy this weekend as well. All in all, the idea sounds great. I appreciate that my opinion is taken into account, but I know very little about citation systems. I was only a bit concerned about the effort which is needed to implement the changes, as little as they may be.
--
Sent with https://mailfence.com
Secure and private email
next prev parent reply other threads:[~2023-02-03 15:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-18 21:31 Patch for \usepackage[ ... natbib = true ...]{...biblatex} with org-cite Edgar Lux
2023-01-20 10:59 ` Ihor Radchenko
2023-01-20 16:57 ` Edgar Lux
2023-01-21 8:37 ` Ihor Radchenko
2023-01-21 20:25 ` Edgar Lux
2023-01-22 11:15 ` Ihor Radchenko
2023-01-22 11:36 ` András Simonyi
2023-01-22 19:47 ` Edgar Lux
2023-01-23 10:43 ` Ihor Radchenko
2023-01-22 19:19 ` Edgar Lux
2023-01-23 11:06 ` Ihor Radchenko
2023-01-23 20:58 ` Edgar Lux
2023-01-24 10:54 ` [BUG] #+cite_export: ... bibstyle citestyle cannot be universally used as global defaults (was: Patch for \usepackage[ ... natbib = true ...]{...biblatex} with org-cite) Ihor Radchenko
2023-02-03 9:33 ` Edgar Lux [this message]
2023-02-04 11:31 ` Ihor Radchenko
2023-02-04 23:14 ` Edgar Lux
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=746321315.112536.1675416834079@ichabod.co-bxl \
--to=edgarlux@mailfence.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).