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 06:19:27 -1000 [thread overview]
Message-ID: <m162cnwzqo.fsf@tsdye.com> (raw)
In-Reply-To: <jn8er2$3vf$1@dough.gmane.org> (Karl Voit's message of "Wed, 25 Apr 2012 11:06:42 +0200")
Karl Voit <devnull@Karl-Voit.at> writes:
> * Thomas S. Dye <tsd@tsdye.com> wrote:
>>
>> One of the ideas behind the new exporter is that Org-mode source
>> prepared for one target can be easily exported to other targets.
>
> I see.
>
>> My brief experience with the LaTeX exporter so far has been very
>> positive and I'm relatively certain that it will be the default
>> export engine in the not too distant future. If the ACM template
>> is written for the new exporter, then its use life will likely be
>> enhanced.
>
> Right.
>
>> Also, I agree with Jambunathan's comment that exercising the new
>> exporter on a practical project might possibly indicate how it
>> could be made better.
>
> To what extent does the new exporter differ from the features
> described in the documentation and the tutorial?
>
> Where is the new exporter described? I could only find [1].
>
>> On a practical note, using the new exporter is easy. I have these
>> two lines (along with other configuration) in an Org-babel code
>> block that I use to setup Org-mode:
>>
>> (require 'org-export) (require 'org-e-latex)
>>
>> Then, I can access the dispatcher with M-x org-export-dispatch and
>> choose the target. It feels easy and natural from the get go.
>
> So no more «C-c C-e d»?
You could bind those familiar keystrokes to the new command, if you like.
>
>
> OK, you convinced me that it would be better to use the new method
> then. As you can see in my naive questions: I am not really familiar
> withe the old exporter and neither with the new one. So using the
> (good) documentation on the old one, I planned to contribute to this
> template as much as possible. But I am not sure whether I can
> contribute to the new one.
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.
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?
Do you have a repository for the project?
All the best,
Tom
>
> 1. http://orgmode.org/Changes.html
--
Thomas S. Dye
http://www.tsdye.com
next prev parent reply other threads:[~2012-04-25 16:19 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 ` Thomas S. Dye [this message]
2012-04-25 21:16 ` Exporting to ACM format using new LaTeX exporter Karl Voit
2012-04-25 21:54 ` Nicolas Goaziou
2012-04-26 8:26 ` Karl Voit
2012-04-26 0:33 ` Thomas S. Dye
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=m162cnwzqo.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).