emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@posteo.net>
To: Stefano Ghirlanda <dr.ghirlanda@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Exporting user labels to non-latex backends
Date: Fri, 17 May 2024 13:45:26 +0000	[thread overview]
Message-ID: <87a5kosgax.fsf@localhost> (raw)
In-Reply-To: <CAK_gY-Tjk3r5BXx7xDR4WGQ=SJ_L1Kw0rA9bM4VTBK4ydPxf=A@mail.gmail.com>

Stefano Ghirlanda <dr.ghirlanda@gmail.com> writes:

> There may be an issue with using #+name: labels when exporting to
> non-latex backends. For example:
> ...
> #+name: eq:x
> \begin{equation}
>    x = 1
> \end{equation}
>
> cref:eq:x
> ---
>
> exports with a mix of org labels and user labels:
>
> ---
> \begin{equation}
>   \label{orgf29908c}
>   x = 1
> \end{equation}
>
> equation \ref{eq:x}
> ---
>
> This does not affect latex export because one can set
> org-latex-prefer-user-labels, but most other backends do not seem to
> have this setting. I think there is one for HTML but I could not find
> one for markdown. Would it be useful to have a global setting for all
> backends? Or, is there a way to fix this with the current code base?

AFAIK, there is nothing to fix - the current behavior is intentional:

Commit 981f25031dd17
* lisp/ox-md.el (org-md-latex-environment, org-md-latex-fragment):
These two new filters wrap LaTeX maths in $ / $$ TeX-style notation.
While ox-md endeavours to adhere to the original Markdown specification,
and not any particular variant, the original specification does not deal
with LaTeX fragments at all, and so this change does not reduce how
faithfully the original specification is followed.
There is a major upside to this though. Of the many Markdown variants
that have emerged, those that support LaTeX very often exclusively
support TeX style notation.  This change thus improves the utility of
the Markdown export for many use cases, and deviates no more from the
original specification that the current method.

Please, provide more context about the problem you are trying to solve.

-- 
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:[~2024-05-17 13:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-16 18:51 Exporting user labels to non-latex backends Stefano Ghirlanda
2024-05-17 13:45 ` Ihor Radchenko [this message]
2024-05-17 20:42   ` Stefano Ghirlanda

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=87a5kosgax.fsf@localhost \
    --to=yantar92@posteo.net \
    --cc=dr.ghirlanda@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).