Re: markup in environments in latex export

[Chris Gray <chrismgray@gmail.com>]

Hi Carsten,

That seems like a good solution.  I will work on it and test it over the
next couple of days and let you know when it is ready.  Do you have any
preference for the name of the file?

BTW, I also have signed and sent the copyright papers.  I don't know if
that's necessary for a contrib package, but now it's done...

Cheers,
Chris

Carsten Dominik wrote:

> Hi Chris,

> I have been pondering about this idea, and I prefer to not integrate
> it into the Org core because I think it may lead to undesired behavior,
> in particular in the other backends like docbook or ASCII.

> However, I have just created three new hooks

> 	* org-exp.el (org-export-preprocess-after-blockquote-hook): New hook.
> 	(org-export-preprocess-string): Run the new hook.

>         * org-latex.el (org-export-latex-after-blockquotes-hook): New
> hook.
>         (org-export-latex-preprocess): Run the new hook.

> 	* org-html.el (org-export-html-after-blockquotes-hook): New hook.
> 	(org-export-as-html): Run the new hook.

> which would allow to easily implement your idea as an add-on package
> that we could include in the contrib directory.  Would you like to
> reformulate your patch into a small add-on?  The only thing I would
> like to ask is to keep it LaTeX/HTML-specific, and this means that
> the action to turn #+begin_..... into the cookies should be wrapped
> into

> (when (or latexp htmlp)
>    .......
>   )



> latexp and htmlp are a local variables available when the
> first of the three hooks is run.

> - Carsten