emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Mike McLean <mike.mclean@pobox.com>
To: Emacs-orgmode@gnu.org
Subject: Question About New Exporter
Date: Mon, 20 Aug 2012 06:49:37 -0400	[thread overview]
Message-ID: <29B7FC2F-B771-4F10-931C-FE7E86A05D93@pobox.com> (raw)


I use Org mode quite a bit to:
a) Export raw HTML that I use on my corporate Sharepoint site (currently via copy/paste) for Wiki entries, Blog posts, etc.
b) Export HTML to a browser that I copy/paste into corporate Outlook for Mac client for formatted email
c) PDF documents via LaTeX

On point (c), I have 3 custom LaTeX classes (each based off of and ultimately including the memoir class). These classes are similar in function and exist for format a corporate document via corporate branding, personal documents in a way that pleases me, and documents for my non-profit volunteer efforts in a style that match that branding.

For all 3 I use the LaTeX biblatex-chicago package, and to help the tex build process use latexmk.

I am on a Mac so I use xelatex instead of pdflatex to get system fonts, Open Type fonts, etc.

My Org mode LaTeX build is:

(setq texcmd "latexmk -gg -f -shell-escape -xelatex -pdf %f")
(setq org-latex-to-pdf-process (list texcmd))

Given all of that; what do I need to be wary of before I switch to the e-html and e-latex exporters?

Are they far enough along that I should be able to just swap and have every thing “just work” or “mostly work” ?


             reply	other threads:[~2012-08-20 10:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-20 10:49 Mike McLean [this message]
2012-08-20 12:13 ` Question About New Exporter Bastien

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:

  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=29B7FC2F-B771-4F10-931C-FE7E86A05D93@pobox.com \
    --to=mike.mclean@pobox.com \
    --cc=Emacs-orgmode@gnu.org \


* 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


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).