emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: tsd@tsdye.com (Thomas S. Dye)
To: news1142@Karl-Voit.at
Cc: emacs-orgmode@gnu.org
Subject: Re: Exporting to ACM format using new LaTeX exporter
Date: Wed, 25 Apr 2012 14:33:33 -1000	[thread overview]
Message-ID: <m1wr53tjqa.fsf@tsdye.com> (raw)
In-Reply-To: <2012-04-25T23-11-35@devnull.Karl-Voit.at> (Karl Voit's message of "Wed, 25 Apr 2012 23:16:00 +0200")

Karl Voit <devnull@Karl-Voit.at> writes:

> * Thomas S. Dye <tsd@tsdye.com> wrote:
>>
>> AFAICT, the new exporter preserves most of the interface of the old
>> exporter, but smooths over some of the rough edges.  It shouldn't
>> represent a barrier to your contribution.  In fact, it might be useful
>> to write a template for both exporters, then document how they differ as
>> a guide to using the new exporter.
>
> Good idea!
>
>> I took a brief look at the ACM web site and saw that there is more than
>> one LaTeX template.  Which one are you interested in for Org-mode?
>
> I took the "Option 1: LaTeX2e - Strict Adherence to SIGS style"
>
>> Do you have a repository for the project?
>
> Yea, that might be appropriate. So I set up a github repos:
>
>         https://github.com/novoid/orgmode-ACM-template
>
Hi Karl,

Got it, thanks.

IIUC, you'd like to configure Org-mode to export a LaTeX file that is
functionally equivalent to sigproc-sp.tex.  If this is the case, it
might be best to change the name of orgmode.org to sigproc-sp.org or
something similar.  If the goal is to support both exporters, perhaps
sigproc-sp-old.org and sigproc-sp-new.org?

In my view, it is best to encapsulate as much of the Org-mode
configuration as possible in an init.el file.  That way, users of the
Org-mode template can launch with emacs -Q etc. and not have to worry
about their own customizations that might conflict with the
configuration.  An example is here:  https://github.com/tsdye/LKFS.git.
Perhaps two initialization files would be needed: init-new.el and
init-old.el?

> With the new exporter, I was not able to compile the Org-mode file
> at all. Since the old exporter had troubles using this
> "per-file-class" I do have a feeling that this might be the cause
> for the error message with the new exporter too.

I'll have a look at this and send you patches off list.  

>
> Maybe someone more familiar with the (new) LaTeX exporter can send
> me some patches ...

All the best,
Tom

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

  parent reply	other threads:[~2012-04-26  0:33 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-24 20:08 LaTeX-export to ACM SIG Proceedings format Karl Voit
2012-04-24 21:26 ` Thomas S. Dye
2012-04-24 22:14   ` Karl Voit
2012-04-24 22:29     ` Jambunathan K
2012-04-24 23:39       ` Thomas S. Dye
2012-04-25  9:06         ` Exporting to ACM format using new LaTeX exporter (was: LaTeX-export to ACM SIG Proceedings format) Karl Voit
2012-04-25 16:19           ` Exporting to ACM format using new LaTeX exporter Thomas S. Dye
2012-04-25 21:16             ` Karl Voit
2012-04-25 21:54               ` Nicolas Goaziou
2012-04-26  8:26                 ` Karl Voit
2012-04-26  0:33               ` Thomas S. Dye [this message]
2012-04-26  8:33                 ` Karl Voit
2012-04-25 16:16         ` LaTeX-export to ACM SIG Proceedings format Achim Gratz
2012-04-25 17:30           ` Mike McLean
2012-04-25 18:07             ` Achim Gratz
2012-04-25 18:59               ` Mike McLean

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=m1wr53tjqa.fsf@tsdye.com \
    --to=tsd@tsdye.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=news1142@Karl-Voit.at \
    /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).