From: John Hendy <jw.hendy@gmail.com>
To: "Thomas S. Dye" <tsd@tsdye.com>
Cc: Michael Strey <mstrey@strey.biz>,
emacs-orgmode <emacs-orgmode@gnu.org>,
"J. David Boyd" <jdavidboyd@adboyd.com>
Subject: Re: setting left margin in PDF output of ORG file
Date: Mon, 28 Apr 2014 21:47:39 -0500 [thread overview]
Message-ID: <CA+M2ft_d+cr18NGV+3eyBHCZrnb7B=QiWQasQ7MSa1ViyeARng@mail.gmail.com> (raw)
In-Reply-To: <m2siox578q.fsf@tsdye.com>
On Mon, Apr 28, 2014 at 7:06 PM, Thomas S. Dye <tsd@tsdye.com> wrote:
> John Hendy <jw.hendy@gmail.com> writes:
>
>> I'm thinking that the article class must either 1)
>> not embody "the classic rules" that well or 2) the classic rules
>> aren't very aesthetically pleasing after all.
>
> or 3) the classic rules are variable and flexible.
I love out-of-the-box thinking :)
>
> Here is a quote from the Koma script manual:
>
> Many LATEX classes, including the standard classes, present the user
> with the largely fixed configuration of margins and typearea. With the
> standard classes, the configuration determined is very much dependent
> on the chosen font size. There are separate packages, such as geometry
> (see [Ume00]), which give the user complete control, but also full
> responsibility, of the settings of typearea and margins.
>
> KOMA-Script takes a somewhat different approach with its typearea
> package. Here the user is given several construction setting and
> automatization possibilities based on established typography standards
> in order to help guide him or her in making a good choice.
>
Interesting quote! You've sold me on Michael's original suggestion and
I'll be checking out Koma more closely very soon. It's great timing as
a semi-annual technical report at work is due from me shortly :)
John
> All the best,
> Tom
>
> --
> Thomas S. Dye
> http://www.tsdye.com
next prev parent reply other threads:[~2014-04-29 2:47 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-23 14:48 setting left margin in PDF output of ORG file J. David Boyd
2014-04-23 14:54 ` Bastien
2014-04-23 16:59 ` J. David Boyd
2014-04-23 17:41 ` John Hendy
2014-04-23 18:24 ` J. David Boyd
2014-04-23 17:47 ` Nick Dokos
2014-04-23 18:25 ` J. David Boyd
2014-04-24 10:29 ` Michael Strey
2014-04-25 19:01 ` John Hendy
2014-04-25 19:31 ` Martin Schöön
2014-04-25 19:51 ` Thomas S. Dye
2014-04-25 19:57 ` Martin Schöön
2014-04-28 13:58 ` Michael Strey
2014-04-28 23:13 ` John Hendy
2014-04-28 23:23 ` John Hendy
2014-04-29 0:06 ` Thomas S. Dye
2014-04-29 2:47 ` John Hendy [this message]
2014-04-25 20:19 ` Achim Gratz
2014-04-26 12:23 ` J. David Boyd
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='CA+M2ft_d+cr18NGV+3eyBHCZrnb7B=QiWQasQ7MSa1ViyeARng@mail.gmail.com' \
--to=jw.hendy@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=jdavidboyd@adboyd.com \
--cc=mstrey@strey.biz \
--cc=tsd@tsdye.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).