From: Christian Moe <mail@christianmoe.com>
To: Bastien <bzg@altern.org>
Cc: Emacs-orgmode@gnu.org
Subject: Re: [BUG] [ODT] Annotations break paragraphs
Date: Mon, 25 Mar 2013 23:36:31 +0100 [thread overview]
Message-ID: <m2ip4fxg28.fsf@christianmoe.com> (raw)
In-Reply-To: <87r4j35ejb.fsf@bzg.ath.cx>
Hi Bastien,
Thanks for giving it a try. Let's see what Nicolas comes up with.
>
> I would not favor a solution that allows more #+begin_ blocks to
> be inlined.
We've had this one for a while. It's always been a bit anomalous though.
> The proper way to handle this is to introduce a new syntax for
> inlined annotations and to treat them appropriately in exporters.
I think I'd agree.
> Since we have both #+begin_src and src_<lang>{...} I'd suggest
> having annotation_{...} or something similar.
But if annotations are not meant to live in blocks anyway, that analogy
fails.
Aren't annotations/comments more analogous to footnotes? They expand on
the text, but you don't want to clutter the text with them. Could we
imagine e.g. an [cmt:: This is an inline comment] syntax? (It would be
good to support timestamps and authornames, though. Maybe colons aren't
good separators if we put timestamps inside. Hm, needs thinking about.)
> The LaTeX exporter could use \marginpar{...} and the HTML back-end
> could make them appear when hovering with the mouse on the annotated
> parts (just an idea.)
Whatever the solution it would be good to have it work for all backends
where it makes sense.
> Maybe we will have to live with the current "regression" for 8.0
> and implement the new syntax for 8.1. Or for 8.0, if Nicolas thinks
> the change is okay and not too error prone.
I can always go back to inserting ODT annotations with macros, for the
time being.
Yours,
Christian
prev parent reply other threads:[~2013-03-25 22:35 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
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 [this message]
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=m2ip4fxg28.fsf@christianmoe.com \
--to=mail@christianmoe.com \
--cc=Emacs-orgmode@gnu.org \
--cc=bzg@altern.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).