emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Karl Voit <devnull@Karl-Voit.at>
To: emacs-orgmode@gnu.org
Subject: Re: Exporting to ACM format using new LaTeX exporter
Date: Thu, 26 Apr 2012 10:26:10 +0200	[thread overview]
Message-ID: <2012-04-26T10-22-53@devnull.Karl-Voit.at> (raw)
In-Reply-To: 874ns7eau9.fsf@gmail.com

* Nicolas Goaziou <n.goaziou@gmail.com> wrote:
> Hello,

Hi Nicolas!

> Karl Voit <devnull@Karl-Voit.at> writes:
>
>> * Thomas S. Dye <tsd@tsdye.com> wrote:
>>>
>> Yea, that might be appropriate. So I set up a github repos:
>>
>>         https://github.com/novoid/orgmode-ACM-template
>>
>> 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.
>>
>> Maybe someone more familiar with the (new) LaTeX exporter can send
>> me some patches ...
>
> I don't understand what you are trying to achieve. Would you mind
> summarizing it for someone too lazy to browse docs?

Sure: when I want to hand in a paper for a conference which demands
LaTeX documents that fulfill the requirements of the ACM template, I
want to have to possibility to use Org-mode with its LaTeX export
method in order to get PDF output which will be accepted by the
conference.

Most of the time, only the PDF have to look like the template
result, some times it is required to hand in also the TeX sources of
the paper.

> Note that `org-splice-latex-header' belongs to neither the legacy
> exporter nor the new one: it's an org.el function. Thus your problem may
> lie elsewhere.

Oh gosh.

I guess I have to strip down my Org-mode file and start all over
with a minimal version trying to expand until the error occures.

-- 
Karl Voit

  reply	other threads:[~2012-04-26  8:26 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 [this message]
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=2012-04-26T10-22-53@devnull.Karl-Voit.at \
    --to=devnull@karl-voit.at \
    --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).