Re: adding to the LSR

[Chip]

Jonathan Kulp wrote:

Chip wrote:

Neil Puttock wrote:

2009/4/26 Chip <address@hidden>:

 

Hmm, did run into an apparent error - after I click on the Save button I get
a pop-up box that says "No output from Lilypond", did I do something wrong?
   

Probably not. :)

It normally means your snippet is incompatible with the version of
LilyPond being run on LSR (2.10.12) or needs either `Standalone
snippet' or `Large snippet' ticked.  If you still can't get it
working, please post it here and I'll give it the once over.

Regards,
Neil

Thanks Neil,
I have tried with just plain text in the description and selected Standalone and again selected Large and again selected neither of those two options, I've tried with html and plain text, with and without a code sample in the description, choose a directory or no directory, just can't get it to go through.

Regards,
Chip

Below is what I am trying to add to the LSR -

Hi Chip,

I've added your snippet to the repo but had to modify it to get it to work, since I had the same troubles you had.  I simplified the musical part drastically, and that's what finally made it compile.

I also left off all of the stuff about changing the parameters of the date format, because it came out as a big jumbled mess.  If you'd like to send that part of your description with some html formatting commands I'll be happy to add it back in there.  For now I just said the format of the date can be changed according to the parameters found in the date manpage on Linux/Unix systems.  I did add <p></p> markup to the first three paragraphs of your description but didn't have time to do that to all of the lines in the date formatting.

Thanks Jon,
I got those parameters from a Linus manpage and tested all of them and more, and the ones listed below work as expected. There were several others that did not work on the Lilypond output. That is why I think these should be listed, so someone doesn't try one of the others that didn't work, then have to do the troubleshooting testing to find out which ones do/don't work. I already did that. Below is the list of tested/usable parameters -

<p>The format of the date can be changed according to these parameters:</p>
<ul>
<li>%a - is replaced by the locale's abbreviated weekday name.</li>
<li>%A - is replaced by the locale's full weekday name.</li>
<li>%b - is replaced by the locale's abbreviated month name.</li>
<li>%B - is replaced by the locale's full month name.</li>
<li>%c - is replaced by the locale's appropriate date and time representation.</li>
<li>%d - is replaced by the day of the month as a decimal number [01,31].</li>
<li>%I - is replaced by the hour (12-hour clock) as a decimal number [01,12].</li>
<li>%j - is replaced by the day of the year as a decimal number [001,366].</li>
<li>%m - is replaced by the month as a decimal number [01,12].</li>
<li>%M - is replaced by the minute as a decimal number [00,59].</li>
<li>%p - is replaced by the locale's equivalent of either a.m. or p.m.</li>
<li>%U - is replaced by the week number of the year (Sunday as the first day of the week) as a decimal number [00,53].</li>
<li>%w - is replaced by the weekday as a decimal number [0,6], with 0 representing Sunday.</li>
<li>%W - is replaced by the week number of the year (Monday as the first day of the week) as a decimal number [00,53]. All days in a new year preceding the first Monday are considered to be in week 0.</li>
<li>%x - is replaced by the locale's appropriate date representation.</li>
<li>%X - is replaced by the locale's appropriate time representation.</li>
<li>%y - is replaced by the year without century as a decimal number [00,99].</li>
<li>%Y - is replaced by the year with century as a decimal number.</li>
<li>%Z - is replaced by the timezone name or abbreviation, or by no bytes if no timezone information exists.</li>
</ul>

Regards,
Chip

You can find the snippet once you're in the database by typing "current" in the title field and clicking "enable filter."  The snippet is called "adding the current date to a footer or tagline."

Best,

Jon

No virus found in this incoming message.
Checked by AVG - www.avg.com 
Version: 8.5.287 / Virus Database: 270.12.4/2081 - Release Date: 04/26/09 09:44:00