From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: Bug: text export and multi-word link descriptions with line breaks Date: Thu, 03 Apr 2014 17:25:01 +0200 Message-ID: <87ha6a4er6.fsf@gmail.com> References: <20140403142834.GA27238@gmx.org> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:55732) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WVjVO-0002nt-6i for emacs-orgmode@gnu.org; Thu, 03 Apr 2014 11:24:42 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WVjVJ-0003D3-QD for emacs-orgmode@gnu.org; Thu, 03 Apr 2014 11:24:38 -0400 Received: from mail-wi0-x229.google.com ([2a00:1450:400c:c05::229]:39857) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WVjVJ-0003Cx-JG for emacs-orgmode@gnu.org; Thu, 03 Apr 2014 11:24:33 -0400 Received: by mail-wi0-f169.google.com with SMTP id hm4so1114505wib.0 for ; Thu, 03 Apr 2014 08:24:32 -0700 (PDT) Received: from selenimh ([91.224.148.150]) by mx.google.com with ESMTPSA id h8sm11827860wiz.12.2014.04.03.08.24.31 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 03 Apr 2014 08:24:31 -0700 (PDT) In-Reply-To: <20140403142834.GA27238@gmx.org> (Mathias Bauer's message of "Thu, 3 Apr 2014 16:28:34 +0200") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org Hello, Mathias Bauer writes: > 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. Could you be more explicit? What does look quite bad? What did you expect instead? How is related to line breaks in the descriptions? Regards, -- Nicolas Goaziou