From: Bastien <bzg@altern.org>
To: emacs-orgmode@gnu.org
Subject: Re: Thanks
Date: Wed, 19 Sep 2007 03:53:17 +0200 [thread overview]
Message-ID: <87abrjv2sy.fsf@bzg.ath.cx> (raw)
In-Reply-To: <m3sl5bse2z.fsf@gnu.org> (David O'Toole's message of "Tue, 18 Sep 2007 20:17:56 -0400")
David O'Toole <dto@gnu.org> writes:
> As for org-publish, the new LaTeX support is nice.
Thanks!
> I'm not sure what is coming next for org-publish.el, perhaps people
> can suggest ideas.
What about a new ":extension" property for project?
For example, we could use this to publish "HTML" pages as .php files,
given that PHP code can be inserted between #+BEGIN_HTML and #+END_HTML
And maybe an Org option for this (no going through the org-publish
interface) would also be useful: org-export-html-extension
> I can think of at least one: I want both the ability to export to
> LaTeX (and then to PDFs with hyperlinks) AND to make a PDF whose
> styles come directly from your CSS.
Good idea to let the LaTeX export trigger PDF conversion. I guess the
conversion functions would likely to be set in a `:finition-function'
(symmetric to the :preparation-function) or within a new hook for Org,
`org-export-latex-hook' (like the `org-export-html-hook' would process
HTML outputs).
For the PDF to look like the HTML+CSS page... I'm not convinced. Not
only it would be tricky to achieve, but I'm not sure it's desirable.
> At one point I was working with an HTML->PDF exporter that had
> great-looking output; unfortunately it is implemented as a PHP CGI, so
> you need to have Apache running even to use it. I never could get it
> working properly with org, but perhaps there are other programs out
> there now.
I guess such an exporter doesn't translate the HTML content into LaTeX
before exporting it to PDF, it relies on graphical libraries. Having a
LaTeX layer inbetween makes the task even more complicated.
...
Two minor issues about org-publish.el:
1. org-publish-org-to-html is defined twice. You can get rid of the
first instance.
2. The documentation about "Tweaking HTML export" (section 13.1) should
say "Tweaking HTML and LaTeX export" :)
That's all for today!
--
Bastien
next prev parent reply other threads:[~2007-09-19 1:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-18 8:15 Thanks Carsten Dominik
2007-09-18 9:43 ` Thanks Leo
2007-09-18 9:52 ` Thanks Levin
2007-09-22 1:00 ` Xavier Maillard
2007-09-19 0:17 ` Thanks David O'Toole
2007-09-19 1:53 ` Bastien [this message]
2007-09-20 8:45 ` Thanks Carsten Dominik
2007-09-20 13:15 ` Thanks Bastien
2007-09-19 2:02 ` Thanks Russell Adams
2007-09-22 6:30 ` Thanks Carsten Dominik
-- strict thread matches above, loose matches on Subject: below --
2011-08-16 17:11 thanks Patrick O'Neill
2011-08-17 18:37 ` thanks Nick Dokos
2011-08-17 18:55 ` thanks Nick Dokos
2011-08-17 18:59 ` thanks Nick Dokos
2011-08-17 22:27 ` thanks Bernt Hansen
2012-04-26 11:32 thanks Domenico Orlando
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=87abrjv2sy.fsf@bzg.ath.cx \
--to=bzg@altern.org \
--cc=emacs-orgmode@gnu.org \
/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).