From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: Drupal syntax on html-export for image links Date: Sun, 27 May 2012 09:35:09 +0200 Message-ID: <87mx4u5b6a.fsf@gmail.com> References: <87wr42j6l6.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([208.118.235.92]:35682) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SYY3I-0004g3-TI for emacs-orgmode@gnu.org; Sun, 27 May 2012 03:38:14 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SYY3H-0003uz-1S for emacs-orgmode@gnu.org; Sun, 27 May 2012 03:38:12 -0400 In-Reply-To: (William Crandall's message of "Sat, 26 May 2012 21:43:23 -0700") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: William Crandall Cc: Bastien , emacs-orgmode@gnu.org Hello, William Crandall writes: > Is it true that: > > 1. The org-export Package is a "Generic Export Engine" > and is intended to support a new generation of > org export tools (to HTML, LaTeX, ODT, etc). Correct. > 2. It is now an "experimental" Contributed Package: > http://orgmode.org/worg/org-contrib Correct. > 3. The current (old) export command (C-c C-e) executes > a function called "org-export" in org-exp.el (line 943) > but it is not related to the new org-export package. Correct. > 4. API documentation for the new org-export, and it's family > (org-e-ascii.el, org-e-html.el, org-e-latex.el, org-e-odt.el > org-e-publish.el org-element.el), is here: > http://orgmode.org/worg/org-api/ Correct, but be warned that some functions in org-exp.el use org-export-* prefix and might be found under "org-export" section. > 5. Documentation for back-end developers working on new > export tools is here: > http://orgmode.org/worg/dev/org-export-reference.html Correct. > 6. Current org tutorials describe the old tool set, e.g., > "Publishing Org-mode files to HTML", not the new: > http://orgmode.org/worg/org-tutorials/org-publish-html-tutorial.html Correct. > 7. No end-user documentation for the org-export package > has been created, describing for example, how to link > to an external CSS file (as #+STYLE used to work). Correct. > 8. "The Manual" does not (yet) document the org-export package: > http://orgmode.org/manual/index.html Correct. > 9. This mailing list is the best place to ask questions. Correct. > Turning to my immediate challenge, exporting to html, > I have some questions ( M-x org-export-dispatch h ): Since I don't maintain `e-html' back-end, I'll only answer partially. > 5. Removing Pre- and Postamble > > What now works like: > > (setq org-export-html-preamble nil) > (setq org-export-html-postamble nil) > > Now, there is no preamble. > > The postamble is: > >
>

Date: 2012-05-26 20:59:51 Pacific Daylight Time

>

Author : William BC Crandall

>

Generated by Org mode 7.8.11 in Emacs 24.1.50.1.

> Validate XHTML > 1.0 >
> > I'd like to remove both. You may have a look at `org-e-html-preamble' and `org-e-html-postamble' variables. > -------------------------------------------------- > > > 6. Special strings > > I was able to get a TM (&trade) in the old system with: > > (eval-after-load "org" > '(setq org-export-html-special-string-regexps > (append org-export-html-special-string-regexps > '(("-TM-" . "™"))))) > > How now? You can add a filter to plain text objects, which will only be applied to `e-html' back-end: #+begin_src emacs-lisp (defun my-html-trademark-markup (text backend info) (if (not (eq back-end 'e-html)) text (replace-regexp-in-string "-TM-" "™" text))) (add-to-list 'org-export-filter-plain-text-functions 'my-html-trademark-markup) #+end_src Though, I would suggest to use entity \trade instead. Regards, -- Nicolas Goaziou