From: "Sebastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: Org-special-blogs does not make well-formed xhtml
Date: Mon, 03 Oct 2011 15:26:19 +0200 [thread overview]
Message-ID: <80r52unr44.fsf@somewhere.org> (raw)
In-Reply-To: 4E89AE38.3020309@christianmoe.com
Hi Christian Moe,
Christian Moe wrote:
> Hi,
>
> XHTML produced with Org-special-blocks is not well-formed; <div> tags
> get wrapped in <p> tags. Example:
>
> Some text.
>
> #+begin_sidebar
> Some details left out of the main text.
>
> Some more details.
> #+end_sidebar
>
> Some more text.
>
> This results in the following html, which causes XML processors to fail.
>
> <p>
> <div class="sidebar">
> Some details left out of the main text.
> </p>
> <p>
> Some more details.
> </div>
> </p>
> <p>
> Some more text.
> </p></div>
>
> The problem seems to be fixed by un-commenting the fifth line in the
> below function in org-special-blocks.el:
>
> (defun org-special-blocks-convert-html-special-cookies ()
> "Converts the special cookies into div blocks."
> ;; Uses the dynamically-bound variable `line'.
> (when (string-match "^ORG-\\(.*\\)-\\(START\\|END\\)$" line)
> ; (org-close-par-maybe)
> (message "%s" (match-string 1))
> (if (equal (match-string 2 line) "START")
> (insert "<div class=\"" (match-string 1 line) "\">\n")
> (insert "</div>\n"))
> (throw 'nextline nil)))
>
> Does anyone know if that was commented out for a reason?
git blame suggests it was there since that file org-special-blocks.el has been
added (in contrib/lisp, by Carsten, on 2009-05-07 13:53)...
Best regards,
Seb
--
Sebastien Vauban
next prev parent reply other threads:[~2011-10-03 13:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-03 12:44 Org-special-blogs does not make well-formed xhtml Christian Moe
2011-10-03 13:26 ` Sebastien Vauban [this message]
2011-10-04 11:23 ` Carsten Dominik
2011-10-04 12:45 ` Christian Moe
2011-10-04 14:22 ` Carsten Dominik
2011-10-04 14:36 ` Jambunathan K
2011-10-04 19:01 ` Christian Moe
2011-10-04 21:33 ` Carsten Dominik
2011-10-06 10:17 ` Christian Moe
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
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=80r52unr44.fsf@somewhere.org \
--to=wxhgmqzgwmuf-genee64ty+gs+fvcfc7uqw@public.gmane.org \
--cc=emacs-orgmode-mXXj517/zsQ@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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).