emacs-orgmode
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[O] Re: [bug] Problem with Worg (html?) publishing


From: Sébastien Vauban
Subject: [O] Re: [bug] Problem with Worg (html?) publishing
Date: Fri, 25 Mar 2011 22:33:37 +0100
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1.50 (windows-nt)

Hi Nick,

Nick Dokos wrote:
> It's not clear to me how to fix it properly: at the point where
> org-export-select-backend-specific-text is called, there's been a
> partial transformation of the input, so the function is looking at the
> following:
>
> ,----
> | 
> | #+BEGIN_HTML
> | <pre class="example">
> | *** A block                                           
> :B_ignoreheading:BMCOL:
> |     :PROPERTIES:
> |     :BEAMER_env: ignoreheading
> |     :BEAMER_col: 0.4
> |     :END:
> |     - this slide consists of two columns
> |     - the first (left) column has no heading and consists of text
> |     - the second (right) column has an image and is enclosed in an
> |       @example@ block
> | 
> | *** A screenshot                                            
> :BMCOL:B_example:
> |     :PROPERTIES:
> |     :BEAMER_col: 0.6
> |     :BEAMER_env: example
> |     :END:
> |     #+ATTR_LATEX: width=\textwidth
> |     [[file://../../images/org-beamer/a-simple-slide.png]]
> | </pre>
> | 
> | #+END_HTML
> | 
> `----
>
> It could use the fact that it is in a <pre> section - but the function
> is generic wrt backends, so it doesn't worry about details like this.
> Maybe a backend-specific function can be called at this point to deal
> with it - and that can be smarter about how to transform it properly.

A comment from a 30,000 feet view: why looking at <pre>?  Maybe looking at the
fact it is (still, at that point in time) a LaTeX order in a HTML block?

The opposite could be as generic: not interpreting HTML orders when in LaTeX
blocks?

Best regards,
  Seb

-- 
Sébastien Vauban




reply via email to

[Prev in Thread] Current Thread [Next in Thread]