From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Achim Gratz <Stromeko@Nexgo.DE>
Cc: emacs-orgmode@gnu.org
Subject: Re: [BUG] [ODT] Annotations break paragraphs
Date: Wed, 27 Mar 2013 16:48:43 +0100 [thread overview]
Message-ID: <87k3osg7xg.fsf@gmail.com> (raw)
In-Reply-To: <kirg0t$1pm$1@ger.gmane.org> (Achim Gratz's message of "Tue, 26 Mar 2013 07:28:17 +0100")
Hello,
Achim Gratz <Stromeko@Nexgo.DE> writes:
> Am 25.03.2013 23:15, schrieb Nicolas Goaziou:
>>> The proper way to handle this is to introduce a new syntax for
>>> inlined annotations and to treat them appropriately in exporters.
>>>
>>> Since we have both #+begin_src and src_<lang>{...} I'd suggest
>>> having annotation_{...} or something similar.
>>
>> I would suggest [annotation:label] or [note:label] a dedicated section
>> for contents, much like footnotes (aren't they just special footnotes,
>> after all?). That way, they can be inlined while still being able to
>> contain paragraphs.
>
> That only solves this single problem. Provide something like an
> (implicit) P-Block that will become a paragraph in each exporter and can
> contain other elements like all other blocks. I suggest to follow the
> lead of (La)TeX and determine begin and end of such blocks by blank lines.
>
> So this would be a single P-Block with an annotation inside:
>
> ----8<----
> There is an annotation by the original author here
> #+BEGIN_ANNOTATION
> I never meant to break this paragraph.
> #+END_ANNOTATION
> in the middle of the paragraph.
> ---->8----
It wouldn't allow paragraphs within the annotation.
Anyway, every back-end has its own interpretation of what a paragraph
is. Some back-ends don't even know what a paragraph is. Org cannot fit
them all.
On the other hand, as the ox-odt patch somehow demonstrates, it is
possible for a back-end to ignore Org paragraph definition and rolls its
own. It requires some additional code, but I'm open to discussion about
implementing tools in ox.el in order to ease the process.
In any case, I think we ought to keep raw Org syntax as simple as
possible. The current definition of a paragraph is simple enough.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2013-03-27 15:48 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-21 21:18 [BUG] [ODT] Annotations break paragraphs Christian Moe
2013-03-25 5:59 ` Samuel Wales
2013-03-25 10:29 ` Christian Moe
2013-03-25 10:40 ` Achim Gratz
2013-03-25 15:12 ` Bastien
2013-03-25 16:12 ` Christian Moe
2013-03-25 16:17 ` Bastien
2013-03-25 16:27 ` Achim Gratz
2013-03-25 17:39 ` Christian Moe
2013-03-25 18:54 ` Bastien
2013-03-25 20:26 ` Christian Moe
2013-03-25 17:05 ` Bastien
2013-03-25 17:13 ` Achim Gratz
2013-03-25 20:10 ` Nicolas Goaziou
2013-03-25 21:12 ` Christian Moe
2013-03-25 20:00 ` Christian Moe
2013-03-25 21:56 ` Bastien
2013-03-25 22:15 ` Nicolas Goaziou
2013-03-26 6:28 ` Achim Gratz
2013-03-27 15:48 ` Nicolas Goaziou [this message]
2013-03-28 6:24 ` Achim Gratz
2013-03-28 14:41 ` Nicolas Goaziou
2013-03-28 19:12 ` Achim Gratz
2013-03-28 20:58 ` Christian Moe
2013-03-28 23:04 ` Christian Moe
2013-03-26 9:38 ` Christian Moe
2013-03-27 22:33 ` Nicolas Goaziou
2013-03-28 8:40 ` Christian Moe
2013-03-28 9:46 ` Christian Moe
2013-03-25 22:36 ` 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=87k3osg7xg.fsf@gmail.com \
--to=n.goaziou@gmail.com \
--cc=Stromeko@Nexgo.DE \
--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).