emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Mark Barton <mbarton98@gmail.com>
To: Luca Ferrari <fluca1978@gmail.com>
Cc: emacs-org list <emacs-orgmode@gnu.org>
Subject: Re: prevent underscores to be translates in subscript when exporting to latex
Date: Sat, 8 Oct 2022 07:43:12 -0700	[thread overview]
Message-ID: <CFA59737-42F7-406B-9D3F-2206D3CF64BF@gmail.com> (raw)
In-Reply-To: <CAKoxK+7EvnVME+on1BC6DuNANdpF_6YtH62YLebiNsTXzZCXMg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 974 bytes --]



> On Oct 8, 2022, at 6:58 AM, Luca Ferrari <fluca1978@gmail.com> wrote:
> 
> Hi all,
> I've a link like
> [[https://foo.com/bar_baz.html][https://foo.com/bar_baz.html] <https://foo.com/bar_baz.html][https://foo.com/bar_baz.html]>] that,
> once rendered in LaTeX, is converted to a subscript like
> bar\textsubscript{baz}.
> Is there a way to prevent this?

I settled on adding an OPTION line to my org file to disable this behavior, since the documents I'm working on rarely need subscripts and I can use the LaTeX form when I do need to specify them.

#+OPTIONS: toc:nil H:3 num:nil ^:nil

The last part forces the export to recognize just the LaTeX form of specifying subscripts.

[[info:org#Export Settings][org#Export Settings]]
‘^’
     Toggle TeX-like syntax for sub- and superscripts.  If you write
     ‘^:{}’, ‘a_{b}’ is interpreted, but the simple ‘a_b’ is left as it
     is (‘org-export-with-sub-superscripts’).

Mark

[-- Attachment #2: Type: text/html, Size: 6432 bytes --]

  parent reply	other threads:[~2022-10-08 14:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-08 13:58 prevent underscores to be translates in subscript when exporting to latex Luca Ferrari
2022-10-08 14:13 ` Ihor Radchenko
2022-10-08 14:32   ` Luca Ferrari
2022-10-08 14:43 ` Mark Barton [this message]
2022-10-12 12:22   ` Luca Ferrari

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=CFA59737-42F7-406B-9D3F-2206D3CF64BF@gmail.com \
    --to=mbarton98@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=fluca1978@gmail.com \
    /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).