emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Mike McLean <mike.mclean@pobox.com>
To: Fabrice Popineau <fabrice.popineau@supelec.fr>
Cc: Org-Mode mailing list <emacs-orgmode@gnu.org>,
	Marcin Borkowski <mbork@wmi.amu.edu.pl>
Subject: Re: An Org-mode LaTeX class?
Date: Tue, 28 Oct 2014 05:49:22 -0400	[thread overview]
Message-ID: <CANid5Q5=nOegQV-9osdzsRSG2LevrjxsxnampLdpy=oQShOqng@mail.gmail.com> (raw)
In-Reply-To: <CAFgFV9Pjs+VB4AzPCAWUkS18FdT_s9CqAzG4cN4hwTJaJ1CkAg@mail.gmail.com>

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

On Tue, Oct 28, 2014 at 4:02 AM, Fabrice Popineau <
fabrice.popineau@supelec.fr> wrote:

> I think that I don't know if you can suit everybody's need but that is
> worth a try.
> For myself, I already wrote a dedicated LaTeX class, because it was too
> cumbersome
> to configure org-mode for the different kind of documents I need to produce
> (not impossible, just too lengthy to duplicate parameters).
>

I did something similar, for similar reasons. I found it easier to make a
LaTeX Template look like what I wanted than to force Org into generating
LaTeX that was what I wanted.


> Hence, I have a class that can output exams, lab sessions texts, course
> notes and slides
> with only a couple of options.
>

I haven't done slides yet, because I've not picked up Beamer and my
approach was more branding. I have once class that brand-matches my primary
employer (Font, logo usage, etc.), another one that matches one of my large
volunteer efforts, and yet another generic “personal” one for “my”
documents.


> And I export only subtrees that are configured for
> this class. it took a bit of time, but it definitely worth it.
>

Agreed


>
> 2014-10-28 2:37 GMT+01:00 Marcin Borkowski <mbork@wmi.amu.edu.pl>:
>
>> Hi all,
>>
>> I have a dream;-).
>>
>> Imagine someone wrote a dedicated Org-mode LaTeX class, and the LaTeX
>> exporter got an option to export to this class.  The class modifies
>> LaTeX so that it supports all Org's elements and objects, and things
>> like tags, timestamps, checkboxes etc.  Moreover, the look of these
>> elements is configurable on the LaTeX end, and further by means of Org
>> options.  This way, we drop the "generic LaTeX" thing (which is nice for
>> people sending articles to journals etc. – so my dream should not
>> replace the current LaTeX exporter, only constitute a variant!), but
>> instead we gain a beautiful, configurable pdf rendering of Org buffers.
>>
>>
Though I'll admit this does sound intriguing.

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

  reply	other threads:[~2014-10-28  9:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-28  1:37 An Org-mode LaTeX class? Marcin Borkowski
2014-10-28  8:02 ` Fabrice Popineau
2014-10-28  9:49   ` Mike McLean [this message]
2014-10-28  9:15 ` Thorsten Jolitz
2014-10-28  9:54 ` Rasmus
2014-10-28 17:38   ` 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='CANid5Q5=nOegQV-9osdzsRSG2LevrjxsxnampLdpy=oQShOqng@mail.gmail.com' \
    --to=mike.mclean@pobox.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=fabrice.popineau@supelec.fr \
    --cc=mbork@wmi.amu.edu.pl \
    /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).