On 09/26/2016 03:51 AM, Phil Holmes wrote:

Paul - I assume that these updates to the news system mean that different edits will be needed for each release? Could you confirm what will have to be done? Ta.

Sure thing. First, add the news entry to news-front.itexi -- same as before.

Second, update the news-headlines.itexi file with a headline for the new entry. For releases you can just update/edit the existing headline about the previous release. This will look like my patch from yesterday:

http://git.savannah.gnu.org/gitweb/?p=lilypond.git;a=blobdiff;f=Documentation/web/news-headlines.itexi;h=97689a68080a6a8679a22bc6c33278345bc96e4e;hp=e5154c6bde1ce35158de5f7eaae3146f41a49efc;hb=36e230cf09bf2755528d2252ee256f88f330e66d;hpb=c626c7105b3ae2ece4e4e678f9b9b495e4f8ffa6

There are two tricky parts:

A. The headlines file has one version of the headlines for the website which includes the anchor links, and another version for other formats that does not. So you have to make the changes in both places.

B. For the website version you have to update both the headline text and the link (URL). Both are inside the @uref{...}. The URL will have some encoded characters, for example "_002e" is "." and "_002c" is "," (Spaces in the headline text become "-" in the URL.)

So to update the version part of the URL from 2.19.48 to 2.19.49 looks like 2_002e19_002e48 to 2_002e19_002e49 The release date would be like August-25_002c-2016 to September-13_002c-2016

For new entries, to get the exact URL you can "make website" and then open the resulting news.html file, then copy and paste the url from the name attribute of the <a> tag for that news entry. It should look something like this:

<div class="news-item"> <a name="Two-LilyPond-projects-in-Google-Summer-of-Code-2016-April-23_002c-2016"></a><h3 class="subheading">Two LilyPond projects in Google Summer of Code 2016 <em>April 23, 2016</em></h3><p>We are happy to see two students... </p></div>


Probably this should go in the CG. (It would be nice to have automated headline generation... Maybe a script could be devised? It's unfortunate that the new setup adds some friction to the process of adding new entries... at least for releases it is pretty straightforward.)

-Paul


_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Reply via email to