emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Peter Davis <pfd@pfdstudio.com>
To: Nick Dokos <ndokos@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Exporting text
Date: Mon, 27 Jan 2014 18:37:16 -0500	[thread overview]
Message-ID: <20140127233715.GA496@pfdstudio-air.home> (raw)
In-Reply-To: <8761p513i9.fsf@alphaville.bos.redhat.com>

On Mon, Jan 27, 2014 at 05:09:02PM -0500, Nick Dokos wrote:
> 
> Why were you using org-article in the first place? Was it supposed to
> help with the font choices? Bear in mind that I know nothing about
> org-article.

I found org-article when trying to find out how to control fonts,
etc. Basically, I have my own LaTeX template I use when
hand-constructing documents, and I was hoping to be able to use those
same settings when org creates a LaTeX document for me. I thought
org-article would give me that degree of control, but it probably
hasn't been updated since some prior version of org (based on the
variable names), and so is probably broken.

> 
> So you have a choice to make: either fix org-article and continue using
> it or throw it away and find some other way to do what you want.
> 
> For example, all you have to do to get Times is
> 
> #+LATEX_HEADER: \usepackage{times}
> 
> Getting finer control should also be possible using basic latex
> techniques. Whether that's a "better" way to go is of course
> debatable: it depends on a lot of variables.

Since most of these settings I'll want to use in *all* my documents,
putting all the parameters in each org file would be pretty
tedious. I'll keep looking for a more elegant solution. I'll be happy
to post here when I find something (that works!)

Thank you!

-pd


-- 
----
Peter Davis
The Tech Curmudgeon
www.techcurmudgeon.com

  reply	other threads:[~2014-01-27 23:37 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-26 19:31 Exporting text Peter Davis
2014-01-26 22:14 ` Bastien
2014-01-27 15:05   ` Peter Davis
2014-01-27 16:19     ` Peter Davis
2014-01-27 16:31       ` Peter Davis
2014-01-27 17:00         ` Nick Dokos
2014-01-27 17:28           ` Peter Davis
2014-01-27 18:06             ` Nick Dokos
2014-01-27 21:33               ` Peter Davis
2014-01-27 22:09                 ` Nick Dokos
2014-01-27 23:37                   ` Peter Davis [this message]
2014-01-28  1:41                 ` Thomas S. Dye
2014-01-28  1:58                   ` Peter Davis
2014-01-28  3:06                     ` Thomas S. Dye

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=20140127233715.GA496@pfdstudio-air.home \
    --to=pfd@pfdstudio.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=ndokos@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).