emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Jambunathan K <kjambunathan@gmail.com>
To: James Harkins <jamshark70@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: ODT preferred format option per-file?
Date: Sun, 02 Sep 2012 00:15:06 +0530	[thread overview]
Message-ID: <87sjb1fuq5.fsf@gmail.com> (raw)
In-Reply-To: <877gsfr7a5.wl%jamshark70@dewdrop-world.net> (James Harkins's message of "Fri, 31 Aug 2012 12:53:54 +0800")

James Harkins <jamshark70@gmail.com> writes:

> Hi,
>
> I have one particular org file that I would like to export to PDF by
> way of ODT. (I already set up outline styling in LibreOffice and I
> would like to use that, instead of trying to reconfigure a similar
> look in LaTeX. For fun, I did try the LaTeX pdf export and the output
> format is not what I need for this case.)
>
> But I may want to export other org files to ODT *without* converting them to PDF.
>
> http://orgmode.org/manual/Extending-ODT-export.html
>
> This says I can customize the org-export-odt-preferred-output-format
> variable. This works beautifully, but it's a global setting that will
> apply to every ODT export.
>
> So my question is -- is there any export option for the preferred
> format, per file? Something like:
>
> #+ODT_PREFERRED_FORMAT: pdf
>
> I couldn't find any documentation in the ODT export section of the
> manual for an option like this.
>
> Alternately, I suppose I could write a lisp function that would set
> the variable and call the export, but that would definitely be a hack.

Old exporter
============

If you are using org-odt.el, then you can use file local variables.  I
have pushed a fix which makes string values of this variable safe.

    M-x add-file-local-variable RET org-export-odt-preferred-output-format
    RET "pdf" RET

Or 

Add the following to your Org file.  Remember to re-visit the file to
activate the newly installed value.

    # Local Variables:
    # org-export-odt-preferred-output-format: "pdf"
    # End:


New exporter
============

The above local variable trick will fail in case of org-e-odt.el.  When
I get some time I will introduce a per-buffer keyword for this variable.
-- 

  reply	other threads:[~2012-09-01 18:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-31  4:53 ODT preferred format option per-file? James Harkins
2012-09-01 18:45 ` Jambunathan K [this message]
2012-09-01 20:40   ` Jambunathan K
2012-09-02  8:43     ` Bastien
2012-09-02  9:25   ` Nicolas Goaziou
2012-09-02  8:57 James Harkins

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=87sjb1fuq5.fsf@gmail.com \
    --to=kjambunathan@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=jamshark70@gmail.com \
    /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).