emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Rob Sargent <rsargent@xmission.com>
To: emacs-orgmode@gnu.org
Subject: tex export overshoots right margin with mixed fonts
Date: Thu, 23 Feb 2023 16:25:05 -0700	[thread overview]
Message-ID: <126ef632-d0c3-60bc-2048-aca1ceba1ae1@xmission.com> (raw)

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

             reply	other threads:[~2023-02-23 23:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-23 23:25 Rob Sargent [this message]
2023-02-24  8:06 ` tex export overshoots right margin with mixed fonts Fraga, Eric
2023-02-24 10:42   ` Alain.Cochard
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=126ef632-d0c3-60bc-2048-aca1ceba1ae1@xmission.com \
    --to=rsargent@xmission.com \
    --cc=emacs-orgmode@gnu.org \


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