emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Brian van den Broek <brian.van.den.broek@gmail.com>
To: John Hendy <jw.hendy@gmail.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>, Jeff Rush <jrush@taupro.com>
Subject: Re: LaTex Adjustments for Org-Export
Date: Sun, 4 Aug 2013 00:16:21 -0400	[thread overview]
Message-ID: <CAF6Daj+r=GsfExUZBz645gMWFhxaB9+iBmXtqXLkmXjjbPne5Q@mail.gmail.com> (raw)
In-Reply-To: <CA+M2ft-54tZeNF5nc=20reSaDw-6s35k_QyZh0J9SLOdaj8s+g@mail.gmail.com>

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

On Aug 3, 2013 9:26 PM, "John Hendy" <jw.hendy@gmail.com> wrote:
>
> On Sat, Aug 3, 2013 at 3:49 PM, Brian van den Broek
> <brian.van.den.broek@gmail.com> wrote:
> >
> > On Jul 31, 2013 8:28 AM, "Jeff Rush" <jrush@taupro.com> wrote:
> >>
> >> I'm trying to export a .org file to .pdf and although I've gotten past
> >> many formatting hurdles, I am stuck on two problems.
> >>
> >
> > <snip>
> >
> >>
> >> 2) How can I change the basic formatting of paragraphs everywhere to
> >>
> >>      a) omit the leading indent, and
> >>      b) have a blank line between paragraphs
> >>
> >>     Instead of this strange-looking style:
> >>
> >>         This is a test paragraph
> >>     of the following kind of thing.
> >>         And so is this one.
> >>
> >>     I want it to look like this:
> >>
> >>     This is a test paragraph
> >>     of the following kind of thing.
> >>       And so is this one.
> >
> > Hi all,
> >
> > (Catching up on the traffic, so a bit late to the thread.)
> >
> > I don't use org's export facilities, so I am not sure how and where to
> > object this into org's export process. But, the LaTeX way is to use the
> > parskip package.
> >
> > Please do reconsider, though. Just about every book on my shelves
follows
> > what you label a 'strange style,' for the good reason that the style you
> > favour can result in ambiguity. (A paragraph that ends a page, takes up
the
> > entire last line and is followed by a new paragraph cannot be
distinguished
> > from a paragraph that spans the page break.)
> >
>

<snip>

> That was [mostly] a joke. I'm actually not clear from the text above
> what is desired. The description says "no leading indent and blank
> line between," but the example text shows non-indent on first
> paragraph, indent on second (which would void the page-span concern),
> and no line break...

Indeed it does. I missed that reading on my phone. I don't see how I can
blame my strange typo on that though, so perhaps I ought just give up :-)

As I said, I don't export from org to latex, but I am puzzled. The style
you describe (and which the OP appears to display) is what LaTeX does for
me by default. I know that no leading indent and inter-paragraph separation
is a common desire, so I guess I let lazy thinking take over.

> I take it you have literary experience, which I'm glad to have on the
> list. Your comment made me consider that I often fiddle with "what
> seems to look nice," overlooking that some of these things have a very
> specific purpose in terms of avoiding ambiguity or what you described
> -- I'd never have thought of that!

I care about typography and have come to embrace that Knuth, Lamport, and
that maintainers of all things TeXnical are rather better at it than am I.
It is hard to resist the urge to fiddle, but I try :-)

Best,

Brian vdB

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

  parent reply	other threads:[~2013-08-04  4:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-31 12:27 LaTex Adjustments for Org-Export Jeff Rush
2013-07-31 13:44 ` John Hendy
2013-07-31 14:01 ` Nick Dokos
2013-07-31 16:24 ` Nick Dokos
2013-07-31 18:56   ` Suvayu Ali
2013-07-31 21:26     ` Nick Dokos
2013-08-03 20:49 ` Brian van den Broek
2013-08-04  1:26   ` John Hendy
2013-08-04  2:03     ` David Rogers
2013-08-04  4:16     ` Brian van den Broek [this message]
2013-08-04 14:51 ` Anthony Lander

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='CAF6Daj+r=GsfExUZBz645gMWFhxaB9+iBmXtqXLkmXjjbPne5Q@mail.gmail.com' \
    --to=brian.van.den.broek@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=jrush@taupro.com \
    --cc=jw.hendy@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).