emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Thomas S. Dye <tsd@tsdye.com>
To: Rasmus <rasmus@gmx.us>
Cc: emacs-orgmode@gnu.org
Subject: Re: ox-tufte-latex
Date: Tue, 02 Feb 2016 15:35:49 -1000	[thread overview]
Message-ID: <m2si1aeft6.fsf@tsdye.com> (raw)
In-Reply-To: <87lh72k57t.fsf@gmx.us>

Aloha Rasmus,

You've got it exactly right.  I read through ox-latex.el, found the
functions I wanted to change, copied them to ox-tufte-latex.el and added
a few lines of code here and there (using babel and noweb chunks).

It would indeed be easy to modify ox-latex.el so it supports the
non-standard commands of the Tufte LaTeX package.  I can send patches to
that effect, if you like.  Ox-latex would need to recognize a few new
LaTeX attributes and export marginfigure, marginnote, and sidenote
commands.  I hijacked footnote for sidenote, so this would probably need
some work to recognize when one or the other was needed.

The reason I originally decided not to suggest patches to ox-latex.el
is that the Tufte LaTeX package is a bit cranky and I was unsure of its
future. I thought it might be better to leave ox-latex to the more
stable and mature LaTeX packages.  I hadn't thought about backporting,
etc.

hth,
Tom


Rasmus <rasmus@gmx.us> writes:

> Mojn Tom,
>
> I'm pretty invested in KOMA-Script but this is a great as a lot of 
> people really appreciate the Tufte package.
>
> Thomas S. Dye <tsd@tsdye.com> writes:
>
>> I've cobbled together an exporter for the Tufte LaTeX classes, 
>> which I'd like to contribute to Org mode contrib/.
>
> My initial beef with your code it that it seems, from skimming the 
> code, to replicate a lot of functions from ox-latex.  This means 
> that when ox-latex.el updates, we might have to backport the 
> changes into ox-tufte-latex.  It’s already some work keeping 
> ox-beamer and ox-latex up to date (e.g. I added a some feature to 
> ox-latex and only realized much later that I hadn’t added it to 
> ox-beamer).
>
> E.g. org-tufte-latex--inline-image is very much alike 
> org-latex--inline-image.
>
> I don’t know to what extend it would be possible to minimize 
> replication.  Perhaps you already did this and perhaps my comments 
> are merely following from the fact that I did not study your patch 
> appropriately (I’m traveling ATM).
>
> Another question is, what features would we need to make more 
> flexible in ox-latex in order to obsolete your class or reduce it 
> to an element in org-latex-classes?  Is there some areas where 
> it’s lacking for the purpose of "tufing" ox-latex output?
>
> In any I’m very happy that you are working on this.  I hope the 
> above is not discouraging; that’s at least not what it’s meant to 
> be.
>
> Thanks,
> Rasmus


-- 
Thomas S. Dye
http://www.tsdye.com

  reply	other threads:[~2016-02-03  1:36 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-02  0:26 ox-tufte-latex Thomas S. Dye
2016-02-02  1:10 ` ox-tufte-latex Titus von der Malsburg
2016-02-02  1:49   ` ox-tufte-latex Thomas S. Dye
2016-02-03 21:57     ` ox-tufte-latex Spencer Boucher
2016-02-02  8:52 ` ox-tufte-latex Eric S Fraga
2016-02-03  0:28 ` ox-tufte-latex Rasmus
2016-02-03  1:35   ` Thomas S. Dye [this message]
2016-02-03  2:29     ` ox-tufte-latex Lawrence Bottorff
2016-02-03 11:05     ` ox-tufte-latex Rasmus
2016-02-03 11:26       ` ox-tufte-latex Marcin Borkowski
2016-02-03 11:41         ` ox-tufte-latex Rasmus
2016-02-03 13:33           ` ox-tufte-latex Marcin Borkowski
2016-02-03 16:07             ` ox-tufte-latex Thomas S. Dye
2016-02-03 15:41       ` ox-tufte-latex Thomas S. Dye
2016-02-03 16:42         ` ox-tufte-latex Rasmus
2016-02-03 17:15           ` ox-tufte-latex Thomas S. Dye
2016-02-12 18:28 ` ox-tufte-latex Eduardo Mercovich
2016-02-12 19:02   ` ox-tufte-latex Thomas S. Dye
2016-02-18 18:43     ` ox-tufte-latex Eduardo Mercovich
2016-02-19  3:03       ` ox-tufte-latex Thomas S. Dye
2016-02-19  3:54       ` ox-tufte-latex Thomas S. Dye
2016-02-22 17:59         ` ox-tufte-latex Eduardo Mercovich
2016-02-22 18:52           ` ox-tufte-latex Thomas S. Dye
2016-02-22 19:35 ` ox-tufte-latex John Hendy
2016-02-23  0:00   ` ox-tufte-latex 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=m2si1aeft6.fsf@tsdye.com \
    --to=tsd@tsdye.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=rasmus@gmx.us \
    /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).