RE: PDF-Editor Links in Windows

[Thomas Wilmot]

I hope I'm doing this right...still trying to figure out this mailing list
after all these years!

I replied to the message but sent a carbon copy to address@hidden

I used the Gmane Web interface in the past, but it's down, so trying to do
it the "normal" way by actually using eMail!  Quite a barrier to new users I
think!

Anyway,  I did try doing everything from the root of the drive, with a
one-word file name and got the same error message.  I also tried it with
another text editor (TextPad) and got a similar error message.  I just don't
think any of the text editors (including LilyPad) are programmed to
understand this textedit protocol!

Should I be posting in the bug mailing list?

Thanks,
    Thomas


> -----Original Message-----
> From: Phil Holmes [mailto:address@hidden 
> Sent: Wednesday December 14, 2016 6:20 a.m.
> To: Thomas Wilmot
> Subject: Re: PDF-Editor Links in Windows
> 
> 
> ----- Original Message ----- 
> From: "Thomas Wilmot" <address@hidden>
> To: "LilyPond Usergroup!" <address@hidden>
> Sent: Wednesday, December 14, 2016 5:15 AM
> Subject: PDF-Editor Links in Windows
> 
> 
> > Hello everyone,
> >
> > I just thought I should once again draw some attention to the PDF 
> > Document-Text Editor hyperlink bug which exists at least in 
> Microsoft 
> > Windows.
> >
> > There is a post archived here: 
> > 
> http://lists.gnu.org/archive/html/bug-lilypond/2013-04/msg00055.html 
> > in which Phil concludes that this is in fact a bug, as the Windows 
> > installer does not create a functioning environment.
> >
> > I posted a while back about the same issue here: 
> > 
> http://lilypond.1069038.n5.nabble.com/PDF-Links-in-Windows-td181761.ht
> > ml
> >
> > I ran into it again today, but seem to have made new progress!
> >
> > I was again trying to follow the guidelines at this page: 
> > https://msdn.microsoft.com/en-us/library/aa767914(v=vs.85).aspx
> >
> > I tried simply making a text file with .REG extension, then
> > double-clicking
> > to merge with the registry, but it didn't work.  When I dug 
> in with the
> > Registry Editor, the Guile scheme was there, presumably 
> from the initial
> > installation.
> >
> > Anyway, after messing around with the registry for a while, 
> I finally 
> > got the [editor] application I requested to open!
> >
> > This means that all the links in the hyperlink chain are 
> working but 
> > the last!
> >
> > 1.  The PDF viewer is recognizing and sending out the URI request
> > properly.
> > 2.  Internet Explorer is translating the URI, as described 
> on the MSDN 
> > page.
> > 3.  The registry is calling the editor application (or whatever 
> > application
> > I tell it to)
> > 4.  The Editor Application is receiving the message from MSIE and 
> > appearing
> > when called for even though the slashes are the wrong way!
> > 5.  The last step is the editor actually understanding the URI and 
> > handling
> > it correctly.
> >
> > All the people who have this working seem to be using Vim, 
> Emacs, or 
> > some other crazy editor! I just want any simple text editor 
> to be able 
> > to understand the URI. I would
> > personally like Frescobaldi to understand it (which is 
> probably something 
> > I
> > should go contact them about), but given that LilyPad is 
> the text editor
> > which is included with LilyPond, it would make sense for it 
> to be fully
> > functional out of the box, including the hyperlinking 
> between the original
> > and Gold standard PDF reader from the creators of the 
> format (Acrobat
> > Reader) and the LilyPond-included text editor!
> >
> > It seems that some Unicode support has been gained by 
> LilyPad since I 
> > last used it which is great! (hence the lilypad-ascii.exe version), 
> > though I think this hyperlinking is a much more basic feature! (At 
> > least for an English speaker :P)
> >
> > I have attached a screenshot of the error message given by 
> LilyPad for 
> > not knowing what to do with the URI.
> >
> > Thanks,
> >      Thomas
> 
> 
> It's possible that it doesn't like the spaces in your 
> filename's directory 
> path. Could you try with a file that's on a path with no spaces?
> 
> --
> Phil Holmes 
> 
>