From mboxrd@z Thu Jan 1 00:00:00 1970 From: Robert Goldman Subject: Re: Orgmode[PATCH 4/4] Add handling of blockquote and output formats that must be flowed. Date: Thu, 29 Apr 2010 10:00:43 -0500 Message-ID: <4BD99F1B.4040904@real-time.com> References: <1272490799-22448-1-git-send-email-rpgoldman@sift.info> <1272490799-22448-2-git-send-email-rpgoldman@sift.info> Reply-To: rpgoldman@real-time.com Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1O7VIc-0004Af-ML for emacs-orgmode@gnu.org; Thu, 29 Apr 2010 11:05:10 -0400 Received: from [140.186.70.92] (port=49325 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1O7VIb-0004AK-CV for emacs-orgmode@gnu.org; Thu, 29 Apr 2010 11:05:10 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1O7VIU-00076o-GF for emacs-orgmode@gnu.org; Thu, 29 Apr 2010 11:05:09 -0400 Received: from enchanter.real-time.com ([63.170.91.11]:4038) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1O7VIU-00074t-5v for emacs-orgmode@gnu.org; Thu, 29 Apr 2010 11:05:02 -0400 In-Reply-To: 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: Wes Hardaker Cc: dominik@uva.nl, emacs-orgmode@gnu.org, "Robert P. Goldman" On 4/29/10 Apr 29 -8:54 AM, Wes Hardaker wrote: >>>>>> On Wed, 28 Apr 2010 16:39:59 -0500, "Robert P. Goldman" said: > > RPG> Added a handler for blockquotes. > > That looks great. Thanks! > > RPG> Also added :body-newline-paragraph to the org-set-generic-type. > > I'm fine with that too, but in the end couldn't you just put a "\n" in > the format strings? I thought about what to do about newlines when I > wrote the code base and in the end I decided that with the existing > methods you could always add "\n"s everywhere you needed them which > provided the maximum flexibility. The downside is that reading "\n"s > everywhere isn't exactly pretty on the specification side :-/ No, unfortunately, I couldn't make this work for the tikiwiki export. As far as I can tell, if you give the tikiwiki a block of text with newlines in it, the tikiwiki will "decide" that you wanted to set the linebreaks yourself, and will format the block as 
, making it
impossible for a browser to reflow the text.  This is not what I wanted.
 I want paragraphs in my org document to look like paragraphs when exported.

So what I wanted here was newlines /only/ where the paragraphs break.

Honestly, I don't understand how this is done in the wiki engine --- it
seems hard to specify this as an unambiguous translation and get the
edge cases (like single-line paragraphs) right.  However, my appetite
for reading PHP code is /extremely/ limited, so I have been learning the
format rules by experimentation.

Hope that explains things,

Best,


r