Hello,
William Crandall bc3141...@gmail.com 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:
The exporter is new. Needless to say there are bugs, known and
unknown. (Think, Rome wasn't built in a day)
I have fixed few things. I will respond later for unresolved other
things in your list.
7. No end-user documentation for the org-export package
has been created, describing for
Since I don't maintain `e-html' back-end, I'll only answer partially.
I don't want to take over the maintainership of org-e-html.
What I am saying is that, anyone with commit access to Orgmode - this
includes me - can fix or patch up org-e-html without it being routed via
me.
+1 to Bastien
Hello Nicolas and Jambunathan,
Many thanks, to you both, for such quick and detailed responses!
I look forward to checking things out later today.
And yes, +1 to Bastien for recommending!
Regarding your notes on image and file paths:
JK I will respond to 3 and 4 separately. I need to look
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
Hi William,
William Crandall bc3141...@gmail.com writes:
Drupal inline image syntax is:
img src=/sites/default/files/images/BC.png alt=BC
Default Org-mode html-export, for [[/sites/a.png]] seems to be:
img src=file://g:/sites/a.png alt=file://g:/sites/a.png /
Nicolas export engine
