From: Nick Dokos <nicholas.dokos@hp.com>
To: Eraldo Helal <eraldo@eraldo.org>
Cc: Org-Mode <emacs-orgmode@gnu.org>
Subject: Re: keep newlines on pdf export
Date: Sun, 13 Dec 2009 13:21:51 -0500 [thread overview]
Message-ID: <31640.1260728511@gamaville.dokosmarshall.org> (raw)
In-Reply-To: Message from Eraldo Helal <eraldo@eraldo.org> of "Sun, 13 Dec 2009 02:04:28 +0100." <1bcd1ad60912121704s1cfd465dh95b942c2be78d30a@mail.gmail.com>
Eraldo Helal <eraldo@eraldo.org> wrote:
> When I export an org file like the following to pdf:
> test.org
> > line1
> > line2
> > line3
>
> what I get is:
> test.pdf
> > line1 line2 line3
>
> however, I would like to get the following in the pdf:
> test.pdf
> > line1
> > line2
> > line3
>
> How can I get pdf export to keep my org newlines?
> Remark: I do have "\n:t" set in my options line.
>
org-to-pdf is really org-to-latex-to-pdf, and generally
speaking[1] newlines in latex are not significant. One way
to make them significant is
line1\\
line2\\
line3
Another might be
#+LATEX: \obeylines { %}
line1
line2
line3
#+LATEX: }
The %} might or might not be necessary to prevent the org LaTeX exporter
from complaining, but it's a useful workaround for an area that has had
problems in the past.
HTH,
Nick
[1] with exceptions, e.g. paragraph demarcation.
next prev parent reply other threads:[~2009-12-13 18:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <eraldo@eraldo.org>
2009-12-13 1:04 ` keep newlines on pdf export Eraldo Helal
2009-12-13 18:21 ` Nick Dokos [this message]
2009-12-13 20:51 ` Eraldo Helal
2009-12-13 20:53 ` Eraldo Helal
2009-12-13 23:42 ` Nick Dokos
2009-12-14 15:18 ` Bill Powell
2009-12-14 14:58 ` andrea
2009-12-14 15:35 ` Carsten Dominik
2009-12-14 21:56 ` Bill Powell
2009-12-14 22:20 ` Nick Dokos
2009-12-14 23:25 ` Bill Powell
2009-12-16 4:05 ` Eraldo Helal
2009-12-16 6:24 ` Carsten Dominik
2009-12-14 3:40 ` Nick Dokos
2009-12-14 7:49 ` Carsten Dominik
2009-12-13 2:39 Eraldo Helal
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=31640.1260728511@gamaville.dokosmarshall.org \
--to=nicholas.dokos@hp.com \
--cc=emacs-orgmode@gnu.org \
--cc=eraldo@eraldo.org \
/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).