emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "András Simonyi" <andras.simonyi@gmail.com>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: "M. ‘quintus’ Gülker" <post+orgmodeml@guelker.eu>, emacs-orgmode@gnu.org
Subject: Re: Formatting in citation locator
Date: Wed, 26 Oct 2022 17:49:06 +0200	[thread overview]
Message-ID: <CAOWRwxABfv4ga9bh=Av04RZB5oosyS5WVYBCsAUryuZO9qUkdA@mail.gmail.com> (raw)
In-Reply-To: <87eduwrw42.fsf@localhost>

Dear All,

On Tue, 25 Oct 2022 at 13:16, Ihor Radchenko <yantar92@posteo.net> wrote:
> Maybe file a bug report to citeproc repo?

I've ended up making the necessary changes in citeproc and also posted
a patch here which should enable formatting in locators. Marvin, I'd
appreciate it if you could test it.

best wishes,


On Tue, 25 Oct 2022 at 13:16, Ihor Radchenko <yantar92@posteo.net> wrote:
> András Simonyi <andras.simonyi@gmail.com> writes:
> >> No. It is some bug in org-cite-csl--create-structure.
> >> I am CCing the oc-csl maintainer.
> >> András, can you please take a look?
> >
> > first of all, apologies for reacting that late. I had a look now, and
> > the reason of the behaviour is not an oc-csl bug, but rather a
> > citeproc-el limitation: formatting is not supported in locators, so if
> > present it is passed in an unparsed form through the processor and it
> > depends on the used citeproc output formatter what happens to it
> > during finalization. In practice, Org markup seems to go through
> > unchanged when the citeproc output format is set to Org. As a
> > consequence, a possible workaround for making the html export work
> > with formatted locators is to circumvent the citeproc-el html
> > formatter by exporting the Org document first to Org and then the
> > result to html. Of course, this solution might lose some advanced html
> > formatting produced by directly using citeproc such as small caps or
> > style-specific bibliography indentation.
> Maybe file a bug report to citeproc repo?
> --
> Ihor Radchenko // yantar92,
> Org mode contributor,
> 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>

  reply	other threads:[~2022-10-26 15:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-14  7:07 Formatting in citation locator Marvin Gülker
2022-10-19  8:41 ` Ihor Radchenko
2022-10-19 17:40   ` M. ‘quintus’ Gülker
2022-10-20  5:24     ` Ihor Radchenko
2022-10-25  6:44       ` András Simonyi
2022-10-25 11:17         ` Ihor Radchenko
2022-10-26 15:49           ` András Simonyi [this message]
2022-11-11 20:28             ` M. ‘quintus’ Gülker
2022-11-12 13:04               ` Ihor Radchenko

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:

  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='CAOWRwxABfv4ga9bh=Av04RZB5oosyS5WVYBCsAUryuZO9qUkdA@mail.gmail.com' \
    --to=andras.simonyi@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=post+orgmodeml@guelker.eu \
    --cc=yantar92@posteo.net \


* 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).