From: edgar@openmail.cc
To: emacs-orgmode@gnu.org
Subject: How to enforce sub-scripts with {} only for HTML export?
Date: Sun, 20 Feb 2022 21:31:14 +0000 [thread overview]
Message-ID: <9432222bbe3ace826a5450dd406d590a@openmail.cc> (raw)
Hi. I hope that this is not a known issue and that you can help me.
* Short description
If I export this as html
#+begin_src org
test_my_subs
#+end_src
the corresponding line is exported as
#+begin_src html
<p>
test<sub>my</sub><sub>subs</sub>
</p>
#+end_src
* Expected output
I was expecting the output to be
#+begin_src html
<p>
test_my_subs
</p>
#+end_src
In the [[help:org-export-with-sub-superscripts][documentation]], it
reads:
#+begin_quote
Still, ambiguity is possible. So when in doubt, use {} to enclose
the sub/superscript. If you set this variable to the symbol ‘{}’,
the braces are *required* in order to trigger interpretations as
sub/superscript. This can be helpful in documents that need "_"
frequently in plain text.
#+end_src
What am I doing wrong? Thanks!
* Emacs and Org configuration
I am using this with ~emacs -q~:
#+begin_src emacs-lisp
(setq
;; Use {} for super and subscripts
org-export-with-sub-superscripts "{}")
#+end_src
#+begin_src emacs-lisp
(emacs-version)
#+end_src
#+RESULTS:
: GNU Emacs 27.2 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.27,
cairo version 1.17.4)
: of 2021-03-26
#+begin_src emacs-lisp
(org-version)
#+end_src
#+RESULTS:
: 9.4.6
-------------------------------------------------
This free account was provided by VFEmail.net - report spam to abuse@vfemail.net
ONLY AT VFEmail! - Use our Metadata Mitigator to keep your email out of the NSA's hands!
$24.95 ONETIME Lifetime accounts with Privacy Features!
15GB disk! No bandwidth quotas!
Commercial and Bulk Mail Options!
next reply other threads:[~2022-02-20 21:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-20 21:31 edgar [this message]
2022-02-20 21:49 ` How to enforce sub-scripts with {} only for HTML export? Kyle Meyer
2022-02-21 0:47 ` edgar
2022-02-20 23:29 ` Greg Minshall
2022-02-21 0:50 ` edgar
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9432222bbe3ace826a5450dd406d590a@openmail.cc \
--to=edgar@openmail.cc \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.