emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Sebastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: Escaping in HTML Export
Date: Sat, 17 Sep 2011 10:08:39 +0200	[thread overview]
Message-ID: <80obyj1th4.fsf@somewhere.org> (raw)
In-Reply-To: CAE4=OQ_4d-LscexLnoU2WPxwBwsSc97HztoLE+rw+2mSkJ3x0A@mail.gmail.com

Hi Pavel,

Pavel Panchekha wrote:
> I'm seeing an example where Org-mode fails to escape < and > signs on HTML
> exporting.  This is also breaking the claim of XHTML Strict.

Could you maybe provide us with a minimal example of Org file that gets an
erroneous translation in HTML? That could be included in the test suite for
later, so that we can check against regression.

Best regards,

Sebastien Vauban

  reply	other threads:[~2011-09-17  8:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-16 20:48 Escaping in HTML Export Pavel Panchekha
2011-09-17  8:08 ` Sebastien Vauban [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-09-17 22:00 Pavel Panchekha

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=80obyj1th4.fsf@somewhere.org \
    --to=wxhgmqzgwmuf-genee64ty+gs+fvcfc7uqw@public.gmane.org \
    --cc=emacs-orgmode-mXXj517/zsQ@public.gmane.org \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox


This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).