From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nick Dokos Subject: Re: Re: [bug] Problem with Worg (html?) publishing Date: Fri, 25 Mar 2011 17:56:35 -0400 Message-ID: <11617.1301090195@alphaville.usa.hp.com> 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> <80ipv6yjf2.fsf@somewhere.org> Reply-To: nicholas.dokos@hp.com Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from [140.186.70.92] (port=38861 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Q3Ezn-0002da-45 for emacs-orgmode@gnu.org; Fri, 25 Mar 2011 17:56:40 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Q3Ezl-00070b-FC for emacs-orgmode@gnu.org; Fri, 25 Mar 2011 17:56:38 -0400 Received: from g5t0009.atlanta.hp.com ([15.192.0.46]:29659) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Q3Ezl-00070Q-Bo for emacs-orgmode@gnu.org; Fri, 25 Mar 2011 17:56:37 -0400 In-Reply-To: Message from =?us-ascii?Q?=3D=3Futf-8=3FQ=3FS=3DC3=3DA9bastie?= =?us-ascii?Q?n=5FVauban=3F=3D?= of "Fri\, 25 Mar 2011 22\:33\:37 BST." <80ipv6yjf2.fsf@somewhere.org> 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@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: =?us-ascii?Q?=3D=3Futf-8=3FQ=3FS=3DC3=3DA9bastien=5FVauban=3F=3D?= Cc: nicholas.dokos@hp.com, emacs-orgmode@gnu.org S=C3=A9bastien Vauban wrote: > > > > 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.
>=20
> A comment from a 30,000 feet view: why looking at 
?  Maybe looking a=
t the
> fact it is (still, at that point in time) a LaTeX order in a HTML block?
>=20

Well, my view is maybe from 29000 feet, so I'm not sure I can see any
better than you can: the 
 suggestion was because clearly anything
in a 
 should not be transformed any further by the HTML exporter;
I'm not sure whether you can make similar (but perhaps somewhat weaker)
statements outside of a 
.

> The opposite could be as generic: not interpreting HTML orders when in La=
TeX
> blocks?
>=20

Yes, the way that is done today is draconian: delete the thing. If it's
not there, it cannot be interpreted. So off with its head! Dead men tell
no tales :-)

You are right: it is a generic problem - writing HTML examples to be
published with LaTeX would lead to the same difficulties.

Nick