From mboxrd@z Thu Jan  1 00:00:00 1970
From: Christian Moe <mail@christianmoe.com>
Subject: Re: Org-special-blogs does not make well-formed xhtml
Date: Tue, 04 Oct 2011 21:01:15 +0200
Message-ID: <4E8B57FB.5040808@christianmoe.com>
References: <4E89AE38.3020309@christianmoe.com> <80r52unr44.fsf@somewhere.org>
	<BC7DC1E0-4705-476D-833E-EC02B6462897@gmail.com>
	<81ipo4u8ln.fsf@gmail.com>
Reply-To: mail@christianmoe.com
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([140.186.70.92]:52364)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <mail@christianmoe.com>) id 1RBACv-00032V-LY
	for emacs-orgmode@gnu.org; Tue, 04 Oct 2011 14:59:14 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <mail@christianmoe.com>) id 1RBACu-0005NQ-HL
	for emacs-orgmode@gnu.org; Tue, 04 Oct 2011 14:59:13 -0400
Received: from mars.hitrost.net ([91.185.211.18]:54635)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <mail@christianmoe.com>) id 1RBACu-0005L0-Ar
	for emacs-orgmode@gnu.org; Tue, 04 Oct 2011 14:59:12 -0400
In-Reply-To: <81ipo4u8ln.fsf@gmail.com>
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=unsubscribe>
List-Archive: </archive/html/emacs-orgmode>
List-Post: <mailto:emacs-orgmode@gnu.org>
List-Help: <mailto:emacs-orgmode-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=subscribe>
Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
To: Carsten Dominik <carsten.dominik@gmail.com>, Sebastien Vauban <wxhgmqzgwmuf@spammotel.com>, emacs-orgmode@gnu.org

Hi,

Carsten, thanks.

Jambunathan's probably right, though, that this fix (while necessary) 
is incomplete. Sorry, I hadn't thought it through.

Now, when the first paragraph of a special block comes right after the 
#+BEGIN_WHATEVER line, it will just come as the first text node of the 
<div> block, and will not be wrapped in a <p> element. So among other 
things, any special CSS styling for <p>s will not be applied to it.

It's not a big deal -- if you need a <p> (and often you really don't) 
the workaround is as simple as leaving an empty line between 
#+BEGIN_WHATEVER and the first paragraph.

But I guess it would be more consistent/expected/helpful behavior for 
special-blocks to start a new paragraph -- this time *after* the 
opening <div> tag and not around it!

Yours,
Christian


On 10/4/11 4:36 PM, Jambunathan K wrote:
>
> Carsten Dominik<carsten.dominik@gmail.com>  writes:
>> I see no reason to not uncomment this line.  Shall we just do this?
>
> Shouldn't a paragraph be opened/closed while entering/leaving the div.
>
> ,---- See org-xhtml-format-environment
> |     (center
> |      (case beg-end
> |        (BEGIN
> | 	(org-lparse-end-paragraph)
> | 	(insert "\n<div style=\"text-align: center\">")
> | 	(org-lparse-begin-paragraph))
> |        (END
> | 	(org-lparse-end-paragraph)
> | 	(insert "\n</div>")
> | 	(org-lparse-begin-paragraph))))
> `----
>
> We can always open a paragraph gratis, because empty paragraphs are
> pruned at the end of export.