From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?utf-8?Q?S=C3=A9bastien_Vauban?= Subject: Re: [bug] Problem with Worg (html?) publishing Date: Fri, 25 Mar 2011 22:33:37 +0100 Message-ID: <80ipv6yjf2.fsf@somewhere.org> References: <19834758-735D-4ADE-AA66-8ACF44F2CE46@gmail.com> <87bp105nva.fsf@ucl.ac.uk> <4D8BB89A.70908@gmail.com> <874o6rwjox.fsf@pinto.chemeng.ucl.ac.uk> <4D8CC930.9050201@gmail.com> <871v1v9f5m.fsf_-_@ucl.ac.uk> <11249.1301087227@alphaville.usa.hp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org-mXXj517/zsQ@public.gmane.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org-mXXj517/zsQ@public.gmane.org To: emacs-orgmode-mXXj517/zsQ@public.gmane.org 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: > > ,---- > |=20 > | #+BEGIN_HTML > | 
> | *** 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
> |=20
> | *** A screenshot                                            :BMCOL:B_ex=
ample:
> |     :PROPERTIES:
> |     :BEAMER_col: 0.6
> |     :BEAMER_env: example
> |     :END:
> |     #+ATTR_LATEX: width=3D\textwidth
> |     [[file://../../images/org-beamer/a-simple-slide.png]]
> |
> |=20 > | #+END_HTML > |=20 > `---- > > It could use the fact that it is in a 
 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 
?  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

--=20
S=C3=A9bastien Vauban