emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Robert Goldman <rpgoldman@real-time.com>
To: Wes Hardaker <wjhns209@hardakers.net>
Cc: dominik@uva.nl, emacs-orgmode@gnu.org,
	"Robert P. Goldman" <rpgoldman@sift.info>
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	[thread overview]
Message-ID: <4BD99F1B.4040904@real-time.com> (raw)
In-Reply-To: <sdaasmweii.fsf@wjh.hardakers.net>

On 4/29/10 Apr 29 -8:54 AM, Wes Hardaker wrote:
>>>>>> On Wed, 28 Apr 2010 16:39:59 -0500, "Robert P. Goldman" <rpgoldman@sift.info> 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 <pre>, 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

  parent reply	other threads:[~2010-04-29 15:05 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-28 21:39 org-export-generic patch Robert P. Goldman
2010-04-28 21:39 ` [PATCH 4/4] Add handling of blockquote and output formats that must be flowed Robert P. Goldman
2010-04-29 13:54   ` Orgmode[PATCH " Wes Hardaker
2010-04-29 13:58     ` Carsten Dominik
2010-04-29 15:05       ` Robert Goldman
2010-04-29 17:00         ` Bernt Hansen
2010-04-29 17:25           ` Robert Goldman
2010-04-29 18:08             ` Bernt Hansen
2010-04-29 15:00     ` Robert Goldman [this message]
2010-04-30 14:51       ` Wes Hardaker
2010-04-30 15:15         ` Robert Goldman
2010-04-30 15:28           ` Carsten Dominik
2010-04-30 15:45             ` Robert Goldman
2010-04-29 10:44 ` org-export-generic patch Carsten Dominik

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=4BD99F1B.4040904@real-time.com \
    --to=rpgoldman@real-time.com \
    --cc=dominik@uva.nl \
    --cc=emacs-orgmode@gnu.org \
    --cc=rpgoldman@sift.info \
    --cc=wjhns209@hardakers.net \
    /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).