emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@posteo.net>
To: Stanislav Vlasov <S.Vlasov@tilburguniversity.edu>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: [BUG] Org citations do not render in tables [9.5.5 (9.5.5-g8ef620 @ /home/stas/.emacs.d/straight/build/org/)]
Date: Wed, 25 Jan 2023 12:26:59 +0000	[thread overview]
Message-ID: <87edrin6jw.fsf@localhost> (raw)
In-Reply-To: <87tu0f50af.fsf@disroot.org>

Stanislav Vlasov <S.Vlasov@tilburguniversity.edu> writes:

> #+BEGIN_SRC emacs-lisp :results table replace
> "Prior research [cite:@paper] suggests that..."
> | Prior research suggests that... |
> The expected outcome should be:
> | Prior research [cite:@paper] suggests that... |
> It seems that this does not depend on src language (I have also tried with R and got the same issue).


The problem is rather fundamental one.

Citation processing is supposed to be independent from the export
backends. However, `orgtbl-to-generic' is bypassing the citation
processing and calls `org-export-data-with-backend` directly with ox-org
backend not handling citation objects.

There are multiple issues revealed here:
1. ox.el currently treats missing transcoder info as "export all the
   unknown elements/objects and empty strings" - this is rather
   forward-incompatible design that may catch users by surprise when Org
   adds new syntax elements (as it happened here, with citations)

   May ox.el treat missing transcoders as `identity' and only export
   empty string when transcoder is set to nil explicitly?

2. Does it even make sense to apply the default oc-basic when exporting
   to org? Should we instead introduce something like oc-identity that
   does nothing and simply leaves the citations in the original Org
   syntax, later possibly processed by the specific export backend?
   Then, we can use this oc-identity in the default value of
   `org-cite-export-processors': (org identity)?

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:[~2023-01-25 12:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-24 17:08 [BUG] Org citations do not render in tables [9.5.5 (9.5.5-g8ef620 @ /home/stas/.emacs.d/straight/build/org/)] Stanislav Vlasov
2023-01-25 12:26 ` Ihor Radchenko [this message]

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=87edrin6jw.fsf@localhost \
    --to=yantar92@posteo.net \
    --cc=S.Vlasov@tilburguniversity.edu \
    --cc=emacs-orgmode@gnu.org \


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