From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bastien Subject: Re: Thanks Date: Wed, 19 Sep 2007 03:53:17 +0200 Message-ID: <87abrjv2sy.fsf@bzg.ath.cx> References: <20609d837d8bf9ffa69f64c5b607d8ab@science.uva.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1IXokn-0000c7-Fc for emacs-orgmode@gnu.org; Tue, 18 Sep 2007 21:53:25 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1IXokl-0000X0-Gw for emacs-orgmode@gnu.org; Tue, 18 Sep 2007 21:53:24 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IXokl-0000Wj-DT for emacs-orgmode@gnu.org; Tue, 18 Sep 2007 21:53:23 -0400 Received: from ug-out-1314.google.com ([66.249.92.168]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1IXokk-0002mI-UM for emacs-orgmode@gnu.org; Tue, 18 Sep 2007 21:53:23 -0400 Received: by ug-out-1314.google.com with SMTP id m4so202820uge for ; Tue, 18 Sep 2007 18:53:21 -0700 (PDT) In-Reply-To: (David O'Toole's message of "Tue, 18 Sep 2007 20:17:56 -0400") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org David O'Toole 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