From: Mathias Bauer <mbauer@gmx.org>
To: emacs-orgmode@gnu.org
Subject: Bug: text export and multi-word link descriptions with line breaks
Date: Thu, 3 Apr 2014 16:28:34 +0200 [thread overview]
Message-ID: <20140403142834.GA27238@gmx.org> (raw)
Dear Maintainers,
I just stumbled over Org's plain text export and how it works on
links with descriptions consisting of multiple words and line
breaks between them. I'm running Org stable version 8.2.5h.
Org source (spaces at the end of line 1 and 2 don't matter):
--------------------snip--------------------
"OpenPGP Message Format" ([[https://tools.ietf.org/html/rfc4880][RFC
4880]] which obsoletes [[https://tools.ietf.org/html/rfc1991][RFC
1991]] and [[https://tools.ietf.org/html/rfc2440][RFC 2440]])...
...
foo [[https://tools.ietf.org/html/rfc4880][RFC 4880]] bar
baz [[https://tools.ietf.org/html/rfc1991][RFC 1991]] foo
bar [[https://tools.ietf.org/html/rfc2440][RFC 2440]] baz
--------------------snip--------------------
Text export result:
--------------------snip--------------------
"OpenPGP Message Format" ([RFC 4880] which obsoletes [RFC 1991] and [RFC
2440])... ... foo [RFC 4880] bar baz [RFC 1991] foo bar [RFC 2440] baz
[RFC 4880] https://tools.ietf.org/html/rfc4880
[RFC 1991] https://tools.ietf.org/html/rfc1991
[RFC 2440] https://tools.ietf.org/html/rfc2440
[RFC 4880] https://tools.ietf.org/html/rfc4880
[RFC 1991] https://tools.ietf.org/html/rfc1991
--------------------snip--------------------
These multiple references look quite bad. Is it possible to
"normalize" the descriptions in some way *before* checking them
for uniqueness and output them thereafter?
Thanks for considering this issue.
Kind regards
Mathias
next reply other threads:[~2014-04-03 14:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-03 14:28 Mathias Bauer [this message]
2014-04-03 15:25 ` Bug: text export and multi-word link descriptions with line breaks Nicolas Goaziou
2014-04-03 16:30 ` Mathias Bauer
2014-04-03 20:54 ` Nicolas Goaziou
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=20140403142834.GA27238@gmx.org \
--to=mbauer@gmx.org \
--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).