From: Marcin Borkowski <mbork@mbork.pl>
To: Dan Griswold <kc5gmr@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: inter-word space in org -> latex
Date: Tue, 22 Sep 2015 22:17:16 +0200 [thread overview]
Message-ID: <87pp1a2oqb.fsf@mbork.pl> (raw)
In-Reply-To: <CAGO+QKvqz_m0AcQgqwCSM-TA=92Bv1QYGQ0aiOCkHy=OZofEjQ@mail.gmail.com>
On 2015-09-14, at 16:42, Dan Griswold <kc5gmr@gmail.com> wrote:
> Dear org-mode community,
>
> In LaTeX, a space after a period is treated as an inter-sentence space,
> which is wider than an inter-word space. This can lead to overly wide
> spacing after a period that ends an abbreviation rather than a space. The
> way to cover this in LaTeX is to use a backslash prior to the space, as in:
>
> Mr.\ Henry Higgins.
>
> I have some documents in org that have the same issue: periods concluding
> abbreviations, with the result that LaTeX puts more space than I want after
> the abbreviation. Yet the use of "\ " does not work, as the backslash is
> exported to LaTeX as a literal backslash.
>
> How should I mark in org mode that I want a space following a period
> concluding an abbreviation to be seen by LaTeX as an interword space?
#+LATEX_HEADER: \frenchspacing
and never worry again.
OTOH, it would be relatively easy to write a filter which converts Emacs
rules wrt. spaces (single/double space) into LaTeX ones.
BTW: Bringhurst claims that using larger spaces at the end of the
sentence is Bad Style™.
> Thanks,
>
> Dan
--
Marcin Borkowski
http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski
Faculty of Mathematics and Computer Science
Adam Mickiewicz University
next prev parent reply other threads:[~2015-09-22 20:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-14 14:42 inter-word space in org -> latex Dan Griswold
2015-09-14 16:50 ` Rasmus
2015-09-16 15:32 ` Dan Griswold
2015-09-14 16:54 ` Suvayu Ali
2015-09-16 15:33 ` Dan Griswold
2015-09-22 20:17 ` Marcin Borkowski [this message]
2015-09-22 20:51 ` Marcin Borkowski
2015-09-22 20:59 ` Rasmus
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=87pp1a2oqb.fsf@mbork.pl \
--to=mbork@mbork.pl \
--cc=emacs-orgmode@gnu.org \
--cc=kc5gmr@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).