Follow-up Comment #7, bug #68668 (group groff): [comment #6 comment #6:]
> My preferred API is:-
>
> .UR link _scheme_
> _hotspot text_
> .UE _after_
>
> _scheme_ is optional depending on whether it is "usual" to see it as part of
> the link - http/https yes, but mailto/sms not often. As an example I've put
> together a skeleton UR/UE just to demonstrate what it would look like for pdf
> device, see URexample.ms. It demonstrates mailto, https, and sms links, and
> in URexample.pdf clicking on the hotspots starts 3 different programs,
> depending on your xdg-mime settings.
>
> Run with:-
>
> groff -Tpdf -ms URexample.ms | okular -
>
> (file #59096, file #59097)
I like the output but we disagree on the details of the API. People are
_extremely_ accustomed to writing--and copy-and-pasting--full URLs as-is. And
while one can still do that with your proposal, what happens if the hyperlink
has a scheme and the second argument declares a different one? Who wins?
I remain confident in my proposal of comment #2.
We'll eventually want to rename and rescope the `PDFFEAT` register to have a
meaning more like `U` of _groff_ _man_ and _mdoc_, so that people can get all
the hyperlinks disabled and formatted as text if they like. But I'd want a
name more expressive than `U`.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?68668>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
signature.asc
Description: PGP signature
