Re: [BUG] Cannot export a raw link

[Nicolas Goaziou <n.goaziou@gmail.com>]

Achim Gratz <Stromeko@nexgo.de> writes:

> groff has this snippet:
>
>
>                   (if (file-name-absolute-p raw-path)
>                       (concat "file://" (expand-file-name raw-path))
>                     (concat "file://" raw-path)))

This needs to be fixed, along with ox-man.el. Anyway, that wasn't
introduced with the patch being discussed.

> Well, there's the option of correctly parsing into scheme, authority,
> path, query and fragment...  But that is probably not going into 8.2.6
> in any case.

I don't think we need to completely parse the URI because:

  - we are not going to consume it,
  - Org syntax is not completely compatible with RFC3986 (e.g., search
    options like [[file:test.org::* My headline]]).

I think we need scheme, authority, path+query+fragment, and search
options. At the moment, the parser handles scheme,
authority+path+query+fragment and search options.
`url-generic-parse-url' may help, too.

We also need a function to build back the link, in order to make life of
back-end developers easier. This is why authority is needed.

>> Another one is to drop the whole thing, return to previous state, and
>> implement ad-hoc rules to fix "file:", which is probably the only scheme
>> introducing problems.
>
> I forgot what the previous state was, but trying to fix file: URIs
> without correctly parsing them sounds like a losing proposition.

Previous state was, in a nutshell, to recognize scheme:blob, which leads
to the same kind of problem since blob may or may not contain the
authority part.


Regards,

-- 
Nicolas Goaziou