Hi Eric,
I think this interesting functionality could at least initially
be implemented as a add-on, hooking into `org-export-preprocess-hook'.
This hook is called before Org looks at any of the blocks, so the hook
could remove blocks or format them and replace them with finished
HTML (in the case of HTML export....) in a BEGIN_HTML ... END_HTML
block.
- Carsten
On Nov 7, 2008, at 8:02 PM, Eric Schulte wrote:
Hi,
This has had me thinking about the exportation of blocks in
general. I
think it makes sense to pull block exportation out into it's own
component both for simplicity and for ease of code-reading, hacking,
and
customization.
with a set of blocks of forms like...
#+begin_html
#+begin_src
#+begin_comment
#+begin_example
etc...
We could have an alist in which we look up the type of the block, and
call the appropriate function to handle exportation. Users could then
add their own custom block export functions to this list.
The optional exportation of these blocks could then be controlled by a
single #+option variable which takes a list of blocks not to export.
For example
#+OPTION hidden_blocks:comment,src
I'd be interested to hear anyone's thoughts on this. If it sounds
like
a good idea I'd be happy to take a stab at implementation.
Cheers -- Eric
_______________________________________________
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
