tex export overshoots right margin with mixed fonts

tex export overshoots right margin with mixed fonts

[Rob Sargent]

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

Looks to me like this only happens if the last word of the line is 
"emphasized" and larger font.

I'm using emacs 28, org 9.5.5

#+OPTIONS: author:nil
#+OPTIONS: toc:nil
#+OPTIONS: date:nil
#+OPTIONS: ^:nil

#+LaTeX_HEADER: \usepackage[T1]{fontenc}
#+LaTeX_HEADER: \usepackage{libertine}
#+LATEX_HEADER: \usepackage[margin=0.70in]{geometry}
#+LATEX_HEADER: \usepackage{setspace}
#+LATEX_HEADER: \usepackage{enumitem}
#+LaTeX_HEADER: \usepackage{endnotes}

#+ATTR_LATEX: :options [noitemsep, nolistsep]
#+ATTR_LATEX: :options frame=single,backgroundcolor=\color{lightgray}

* Database Retooling
** Mapping instructions
A feature (or is it a bug) of the current processing is the "look ahead" 
feature which
scans the _=MappingInstruction=_ table for instructions "related" to the 
one in hand.  Any
found are processed along with the instruction in hand.  It was found 
that looking ahead
when there /too many/ instruction became too expensive. To guard against 
that, "extra"
records are moved to _=MappingQueue=_ table (and back again) to keep 
_=MappingInstruction=_
under approximately 5000 records.  This to-and-fro happens on a five 
minute interval,
external to the =Resolve= application.

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

Re: tex export overshoots right margin with mixed fonts

[Fraga, Eric]

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.

-- 
: Eric S Fraga, with org release_9.6.1-250-ge6353d in Emacs 30.0.50

Re: tex export overshoots right margin with mixed fonts

[Alain.Cochard]

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
@@latex:\ul{\texttt{MappingInstruction}}@@.

Now, is there a way to tell Org to export _=MappingInstruction=_ as
\ul{\texttt{MappingInstruction}}?








-- 
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 ]

Re: tex export overshoots right margin with mixed fonts

[Fraga, Eric]

On Friday, 24 Feb 2023 at 11:42, Alain.Cochard@unistra.fr wrote:
> Now, is there a way to tell Org to export _=MappingInstruction=_ as
> \ul{\texttt{MappingInstruction}}?

Well, I found I never used strike-through but definitely wanted to be
able to highlight text.  So, I redefined the +...+ markup to generate
\hl{} with the following in my custom variables:

'(org-latex-text-markup-alist
   '((bold . "\\textbf{%s}")
     (code . protectedtexttt)
     (italic . "\\emph{%s}")
     (strike-through . "\\hl{%s}")
     (underline . "\\uline{%s}")
     (verbatim . protectedtexttt)))

(and equivalent for HTML export).  You could do similar for _..._?

I also changed the face used so that +...+ was highlighted by
customising:

'(org-emphasis-alist
   '(("*" bold)
     ("/" italic)
     ("_" underline)
     ("=" org-verbatim verbatim)
     ("~" org-code verbatim)
     ("+" highlight)))
 
I did these changes years ago and have never found the lack of
strike-through an issue but do use highlighting all the time, especially
when sharing work-in-progress documents (PDF) with others.

HTH,
eric

-- 
: Eric S Fraga, with org release_9.6.1-250-ge6353d in Emacs 30.0.50