bug-lilypond
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Broken URL / Documentation Help


From: SoundsFromSound
Subject: Re: Broken URL / Documentation Help
Date: Thu, 30 May 2019 07:01:47 -0700 (MST)

James Lowe-3 wrote
> Hello,
> 
> On 06/05/2019 15:52, Phil Holmes wrote:
>>
>> "Ben L." <

> soundsfromsound@

> > wrote in message 
>> news:

> e8f7c2b9-171d-5077-a3fd-1e608c06758b@

> ...
>>> Hello,
>>>
>>> I hope you all are doing well.
>>> May I ask for a little help with something?
>>>
>>> Could someone please assist me by changing a few URL links that I 
>>> noticed are no longer functioning correctly? My website domain has 
>>> changed and finally stabilized. I am unsure how to handle this kind 
>>> of request, sorry I lack the experience with any sort of patch upload 
>>> / review process here. I would be very appreciative of any help with 
>>> this.
>>>
>>> I believe the links in the "Pondings" section of the LilyPond website 
>>> as well as within the documentation are still pointing to the old 
>>> domain for my resources. My current domain is now permanent and 
>>> securely hosted.
>>>
>>> My website address is now:
>>> https://benl.xyz/lilypond/operation-lilypond
>>>
>>> Which replaces all instances of:
>>> http://benlemon.me/blog/music/lilypond/operation-lilypond
>>>
>>> */Documentation/web/text-input (Beginner Documentation) I think is 
>>> one...
>>>
>>> -----
>>> I have been so happy to hear from users who have discovered LilyPond 
>>> and found their way to my introductory learning material, while 
>>> finding it to be helpful to them. I only just realized now that the 
>>> links were dead. Thank you for helping me with the URLs.
>>>
>>> And a big thank you to everyone who has helped and done so much for 
>>> the LilyPond community! From development to maintaining the 
>>> outstandingly comprehensive documentation, we appreciate you! :)
>>>
>>> Have a great day,
>>> Ben
>>
>> Anyone wanting to do this quickly will need to update 
>> Documentation/web/server/tweets.xml.
> 
> 
> Thanks Phil, I have pushed a change to staging - I didn't create a 
> tracker issue (I hope that is OK?).
> 
> ---
> 
> Pondings: fixed URL for Ben Lemon staging
> author    James Lowe <

> pkx166h@

> >
>      Mon, 6 May 2019 19:54:46 +0100 (19:54 +0100)
> committer    James Lowe <

> pkx166h@

> >
>      Mon, 6 May 2019 19:54:46 +0100 (19:54 +0100)
> commit    a33f922e0fb330d3168025948735f99fc6e90a3d
> 
> ---
> 
> 
> James
> 
> 
> _______________________________________________
> bug-lilypond mailing list

> bug-lilypond@

> https://lists.gnu.org/mailman/listinfo/bug-lilypond

Hi everyone,

I just wanted to let you know that there are still some 404 errors in the
LilyPond documentation from my previous email to the list. I checked just
now on the LilyPond.org source and I noticed this:

/"Created on May 14, 2019"/

I am unfamiliar with the inner workings of how to update documentation via
"texi2html" as well as the timetable for such a process, so please forgive
me if this is a silly question. But I've been receiving some emails from new
users who eventually find their way to my tutorials and want to thank me,
and ask if I knew about the 404 errors, or if there was something wrong with
their browser, etc. - trying to be helpful, of course.

So I thought I would post just once more and see if there was a way to fix
them for the community, and especially new users.

Thanks all.

-------------------------
Current 404 error
_______________

*source: http://lilypond.org/text-input.html*

http://benlemon.me/blog/music/lilypond/operation-lilypond/

* should become *

https://benl.xyz/lilypond/operation-lilypond

---------------------------
Out-of-date URL
________________

*source: http://lilypond.org/manuals.html*

("Video tutorials" section "other material")

http://bit.ly/LilyPondBeginners

* should ideally become *

https://bit.ly/LearnLilyPond





-----
composer | sound designer | asmr artist 
--
Sent from: http://lilypond.1069038.n5.nabble.com/Bugs-f58488.html



reply via email to

[Prev in Thread] Current Thread [Next in Thread]