bug#16751: 24.3.50; Export during Org export to HTML

[Eli Zaretskii <eliz@gnu.org>]

> From: Nicolas Goaziou <n.goaziou@gmail.com>
> Cc: Eli Zaretskii <eliz@gnu.org>,  Sebastien Vauban <sva-news@mygooglest.com>,  16751@debbugs.gnu.org
> Date: Tue, 25 Feb 2014 19:04:10 +0100
> 
> >> Ugh.  Bastien, could you (or someone else of Org developers) please
> >> look into this?  Why does the URI above causes the recent version of
> >> Org to pass an invalid file name such as
> >>
> >>    ///opt/tomcat/4/apache-tomcat-4.1.40/... to expand-file-name
> >
> > I will look into this, but I can't promise anything before next week.
> >
> > Thanks for the heads up,
> 
> A quick analysis.
> 
>     file:path
> 
> is a valid file link type in Org. Therefore,
> 
>     file:///opt/tomcat/4/apache-tomcat-4.1.40/webapps/../user_projects/GHIJSP2/deploy/WEB-INF/sharedfiles/resources/FR/domVal.xml
> 
> is parsed as a file link with path:
> 
>     ///opt/tomcat/4/apache-tomcat-4.1.40/webapps/../user_projects/GHIJSP2/deploy/WEB-INF/sharedfiles/resources/FR/domVal.xml

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?

> FWIW, I don't see any wrong behaviour here (except that "file://" should
> probably not be prepended to path in this case).

Now I'm confused: why are you talking about prepending "file://", when
the problem, as I understand it, happens because "file://" was not
_removed_ from it together with the 2 slashes?