From: Robert Goldman <rpgoldman@sift.info>
To: Carsten Dominik <carsten.dominik@gmail.com>
Cc: Org Mode <emacs-orgmode@gnu.org>
Subject: Re: Export question
Date: Sun, 30 May 2010 15:40:34 -0500 [thread overview]
Message-ID: <4C02CD42.60606@sift.info> (raw)
In-Reply-To: <E043D3F8-305D-4C28-AC9B-6B3EE59B11FE@gmail.com>
On 5/25/10 May 25 -6:52 AM, Carsten Dominik wrote:
>
> On May 25, 2010, at 5:09 AM, Robert Goldman wrote:
>
>> I have the org-generic-export working better, but I'm having one
>> remaining problem:
>>
>> I have been using org-export-preprocess-string to make it possible to
>> handle emphasis (previously o-g-e couldn't handle emphasis because it
>> did the translation line-by-line).
>>
>> org-export-preprocess-string has fixed the problem of emphasis that
>> crosses line boundaries, so that I can handle fontification.
>>
>> But now I have a problem of o-e-p-s smashing together more than one list
>> item into a single line, if those list items are on adjacent lines, like
>>
>> + foo
>> + bar
>>
>> question: is this just something we should never do? Should list items
>> always have line skips in the middle? Or am I misusing o-e-p-s?
>
>
> I cannot reproduce this. But you give little context. Please make a
> more detailed example, maybe a simple test case where you throw some
> data at o-e-p-s and it comes back wrong...
You were right and I was wrong. I thought it was a problem with
o-e-p-s, but it turns out to be a problem with org-generic-export's
line-by-line processing. Sorry about the red herring. I have a fix to
org-generic-export that will handle this.
I am working on a wiki format (tikiwiki: tikiwiki.org) where the
processor decides that any line breaks indicate intent to preformat on
the part of the user. It's turning out to be quite difficult to
harmonize this with line-by-line processing a la org-generic-export.
best,
r
next prev parent reply other threads:[~2010-05-30 20:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-25 3:09 Export question Robert Goldman
2010-05-25 11:52 ` Carsten Dominik
2010-05-30 20:40 ` Robert Goldman [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-09-01 16:49 export question Manfred Lotz
2013-09-01 18:50 ` Suvayu Ali
2013-09-02 19:34 ` Manfred Lotz
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=4C02CD42.60606@sift.info \
--to=rpgoldman@sift.info \
--cc=carsten.dominik@gmail.com \
--cc=emacs-orgmode@gnu.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).