Hello Bastien, Thanks for your pointer to org-export! I got it running and see it is an improvement. Reading the archives, I've gathered some notions. (Please correct me if I'm wrong!) 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). 2. It is now an "experimental" Contributed Package: http://orgmode.org/worg/org-contrib 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. 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/ 5. Documentation for back-end developers working on new export tools is here: http://orgmode.org/worg/dev/org-export-reference.html 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 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). 8. "The Manual" does not (yet) document the org-export package: http://orgmode.org/manual/index.html 9. This mailing list is the best place to ask questions. ------------------------------------------------------------ Even if it's not a full BNF, and "only" 98% as Nicolas says, a quasi-complete grammar is a really good place to start, or re-start, building a "spaghetti-free" export system, IMO. ------------------------------------------------------------ ------------------------------------------------------------ Turning to my immediate challenge, exporting to html, I have some questions ( M-x org-export-dispatch h ): 1. UTF-8 How can I change the encoding, which defaults to: I set org-export-coding-system: (setq org-export-coding-system 'utf-8) And now: org-export-coding-system is a variable defined in `org-export.el'. Its value is utf-8 Original value was nil But the exported html file still shows iso-8859-1 -------------------------------------------------- 2. CSS I used to link to an external style file thus: #+STYLE: What syntax works now? -------------------------------------------------- 3. Configuring paths to images #+ATTR_HTML: alt="BC Crandall" [[/sites/a.png]] Exports to: BC Crandall

One win; one fail. #+ATTR_HTML: works fine! But I'd like the path to be My link How can I keep the path "as it was", and get this: My link without "file://g:" -------------------------------------------------- 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. -------------------------------------------------- 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? -------------------------------------------------- Thanks for any pointers or suggestions! And thanks to everyone working on this. -BC Org-mode: 7.8.11 Emacs: 24.1.50.1 Windows 7 On Thu, May 24, 2012 at 2:01 AM, Bastien wrote: > Hi William, > > William Crandall writes: > > > Drupal inline image syntax is: > > > > BC > > > > Default Org-mode html-export, for [[/sites/a.png]] seems to be: > > > > file://g:/sites/a.png > > Nicolas export engine does it right : > > a.png > > To use it, please pull from the git master repository then > > - add the "contrib/" directory to your load-path > - (require 'org-export) > - M-x org-export-dispatch h > > HTH, > > -- > Bastien >