From mboxrd@z Thu Jan  1 00:00:00 1970
From: =?utf-8?Q?S=C3=A9bastien_Vauban?= <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
Subject: Re: [Bug] Verbatim code gets interpreted
Date: Tue, 08 Mar 2011 17:02:08 +0100
Message-ID: <80mxl561of.fsf@somewhere.org>
References: <80lj0rpd5r.fsf@somewhere.org> <87pqq3yml2.fsf@gnu.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org-mXXj517/zsQ@public.gmane.org>
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <http://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request-mXXj517/zsQ@public.gmane.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/emacs-orgmode>
List-Post: <mailto:emacs-orgmode-mXXj517/zsQ@public.gmane.org>
List-Help: <mailto:emacs-orgmode-request-mXXj517/zsQ@public.gmane.org?subject=help>
List-Subscribe: <http://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request-mXXj517/zsQ@public.gmane.org?subject=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 Bastien,

> S=C3=A9bastien Vauban <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org> writes:
>
>> #+begin_html
>> <div id=3D"disqus_thread"></div>
>> <script type=3D"text/javascript">
>>     (function() {
>>         var dsq =3D document.createElement('script'); dsq.type =3D 'text=
/javascript'; dsq.async =3D true;
>>         dsq.src =3D 'http://' + disqus_shortname + '.disqus.com/embed.js=
';
>>         (document.getElementsByTagName('head')[0] || document.getElement=
sByTagName('body')[0]).appendChild(dsq);
>>     })();
>> </script>
>> #+end_html
>>
>> But the [0] gets interpreted as a footnote... which is not found, hence =
an
>> error on the page, and the JS code is not usable.
>>
>> [...]
>>
>> But I wanted to report this finding.
>
> Thanks for reporting this. I think we could rewrite the export preprocess
> function to allow export parameters to be added:
>
> ,----
> | #+begin_html ^:nil=20
> | ...
> | #+end_html
> `----
>
> In such a block, the ^:nil option would take precedence over the possibly
> ^:t option in the buffer. I'll have a look into this for the next release.

Such a behavior is OK for me (as who can do more can do less), but I wonder
why we simply don't treat the block between `#+begin/end_html' as verbatim,
without touching it at all?

Couldn't one do the same as what happens for the lines prefixed by `#+HTML'?

Best regards,
  Seb

--=20
S=C3=A9bastien Vauban