emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Alain.Cochard@unistra.fr
To: "Fraga, Eric" <e.fraga@ucl.ac.uk>
Cc: Rob Sargent <rsargent@xmission.com>,
	"emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: tex export overshoots right margin with mixed fonts
Date: Fri, 24 Feb 2023 11:42:12 +0100	[thread overview]
Message-ID: <25592.38020.591168.169869@gargle.gargle.HOWL> (raw)
In-Reply-To: <87a6131o9f.fsf@ucl.ac.uk>

Fraga, Eric writes on Fri 24 Feb 2023 08:06:
 > On Thursday, 23 Feb 2023 at 16:25, Rob Sargent wrote:
 > > Looks to me like this only happens if the last word of the line is
 > > "emphasized" and larger font.
 > This is not an org problem; it's LaTeX.  It's happening because LaTeX
 > has a problem breaking up the line at the previous word.  You can help
 > LaTeX by adding the line
 > \sloppy
 > just before the paragraph in question.

Perhaps another (less sloppy :-) way:

The Org's _=MappingInstruction=_ is exported as
\uline{\texttt{MappingInstruction}} in the .tex file.

If one replaces this by \ul{\texttt{MappingInstruction}} and one uses
\usepackage{soul}, then MappingInstruction is correctly hyphenated.

So in the org file, one can use

Now, is there a way to tell Org to export _=MappingInstruction=_ as

EOST (École et Observatoire des Sciences de la Terre) 
ITE (Institut Terre & Environnement) | alain.cochard@unistra.fr
5 rue René Descartes   [bureau 110]  | Phone: +33 (0)3 68 85 50 44 
F-67084 Strasbourg Cedex, France     | [ slot available for rent ]

  reply	other threads:[~2023-02-24 10:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-23 23:25 tex export overshoots right margin with mixed fonts Rob Sargent
2023-02-24  8:06 ` Fraga, Eric
2023-02-24 10:42   ` Alain.Cochard [this message]
2023-02-24 11:03     ` Fraga, Eric

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=25592.38020.591168.169869@gargle.gargle.HOWL \
    --to=alain.cochard@unistra.fr \
    --cc=e.fraga@ucl.ac.uk \
    --cc=emacs-orgmode@gnu.org \
    --cc=rsargent@xmission.com \


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