Mark Knoop <[email protected]> writes: > At 10:32 on 17 May 2016, Urs Liska wrote: >>Am 17.05.2016 um 14:30 schrieb Mark Knoop: >>> At 05:47 on 17 May 2016, Urs Liska wrote: >>>> Mark, can you give us a reason why you consider relative >>>> point-and-click links "broken"? >>> I am unaware of any way for the pdf viewer, or the whatever handles >>> the textedit url, to know what the link is relative to. Correct me >>> if I am wrong on this. >> >>I think the links should be relative to the location of the PDF. But as >>David pointed out it's less trivial than one might think to determine >>what that properly is always. > > Indeed, it's not trivial for lilypond to know that, but that is not my > point. > > Even if the links *are* valid, relative to the location of the pdf, do > you then expect the pdf viewer to convert them to absolute links?
By starting the respective URI handler with the cwd set to the directory the PDF is in. > Or instead, if the relative link is passed to the url-handler (usually > via a desktop environment such as Gnome, Windows, etc), how does that > handler know what the link is relative to? i.e.: what file should > > lilypond-invoke-editor textedit://file.ly:1:2:3 > > open? file.ly as seen from the current work directory with which lilypond-invoke-editor is started. > Could you indicate a working setup where relative point-and-click > links are *not* broken? They work like other file-relative links in URIs. -- David Kastrup _______________________________________________ bug-lilypond mailing list [email protected] https://lists.gnu.org/mailman/listinfo/bug-lilypond
