From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eli Zaretskii Subject: bug#16751: 24.3.50; Export during Org export to HTML Date: Tue, 25 Feb 2014 22:53:22 +0200 Message-ID: <83ios2zzgd.fsf@gnu.org> References: <86fvnmoxyp.fsf@somewhere.org> <86txbwlkeh.fsf@somewhere.org> <83ha7w75sc.fsf@gnu.org> <86wqgk7npj.fsf@somewhere.org> <86mwhf4jpo.fsf@somewhere.org> <834n3n17vg.fsf@gnu.org> <87ob1vnml6.fsf@bzg.ath.cx> <87vbw3t6g5.fsf@gmail.com> <83lhwzyrdw.fsf@gnu.org> <9e1tyrjar9.fsf@fencepost.gnu.org> Reply-To: Eli Zaretskii Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:50656) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WIP0x-0002gD-IP for emacs-orgmode@gnu.org; Tue, 25 Feb 2014 15:54:12 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WIP0s-0001Wm-8R for emacs-orgmode@gnu.org; Tue, 25 Feb 2014 15:54:07 -0500 Sender: "Debbugs-submit" Resent-Message-ID: In-reply-to: <9e1tyrjar9.fsf@fencepost.gnu.org> 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: Glenn Morris Cc: sva-news@mygooglest.com, bzg@altern.org, n.goaziou@gmail.com, 16751@debbugs.gnu.org > From: Glenn Morris > Cc: Nicolas Goaziou , sva-news@mygooglest.com, bzg@altern.org, 16751@debbugs.gnu.org > Date: Tue, 25 Feb 2014 13:41:14 -0500 > > Eli Zaretskii wrote: > > >> file:path > >> > >> is a valid file link type in Org. Therefore, > [...] > > But that's exactly the problem: producing a file name from a file:// > > URL requires to remove the "file://" prefix. It is invalid to leave > > the 2 extra slashes and remove only "file:". Why does Org do that? > > Presumably because Org decided to use "file:" rather than standard > "file://" URI, hence leading to exactly this confusion. That cannot be right, though, can it? If Org wants to support file:/foo, fine, but then it should try the standard file:///foo before falling back on non-standard forms, I think. Am I missing something?