RE: Need help with Lily Pond File

[Mark Stephen Mrotek]

Yeko,

I see four lines of code in your word document. Each has some very minor 
error/additions

1) remove the braces {  }
2) remove the braces {  }, change \trill to \startTrillSpan
3) remove the brace, }, after the \afterGrace and the brace, }, at the very end
4) remove the brace, }, after the \afterGrace and the brace, }, at the very end

Yes, 3 and 4 have the same error.

Mark

-----Original Message-----
From: lilypond-user [mailto:address@hidden On Behalf Of Yerko Difonis
Sent: Sunday, March 17, 2019 3:03 PM
To: address@hidden
Subject: Re: Need help with Lily Pond File

Dear all,
Thank you very much for your replies, and I apologize for the inconvenience. As 
I am blind, and it was late when I sent the e-mail, I didn't feel I could 
figure out the errors on my own. Thomas, I asked permission of the people who 
transcribed the music into braille for me, so that I could transcribe it for 
the flautist I have to play a concert with. Andrew and Brian, thank you for 
your suggestions. I went through the file, copied everything after that which I 
knew to be correct into a Word file, and pasted in the code bit by bit to find 
out where the problems were. I corrected some errors, and the piece now 
processes successfully. The compilation file still gives me some errors having 
to do with bar checks and characters, but it is compiled. Thank you.

I do have a question about pitched trills and trills that end in grace notes. 
Are the attached examples correct?

Thank you again.

Regards,
Yerko
On 3/16/19, Brian Barker <address@hidden> wrote:
> At 03:05 16/03/2019 -0300, you wrote:
>>... I am new to Lily Pond. I am writing because I tried to write out a 
>>piece of music, but it gives me a lot of errors when I tried to 
>>compile it at the end.
>
> I think this is your first mistake. Don't wait until you have 
> completed your source file before compiling. Instead, repeatedly 
> compile it as you go. That way, you can correct any simple slips or 
> misunderstandings gradually, instead of being confronted with pages of 
> error messages at the end. You don't need to compile the complete 
> source every time: see 
> http://lilypond.org/doc/v2.18/Documentation/notation/skipping-correcte
> d-music
>
> for how to skip parts that you are confident are correct.
>
>>I used all the rules of syntax as I understood them.
>
> It's very easy to make slips in coding, of course.
>
>>If you could please help me with this, I would truly appreciate it. I 
>>have attached the .ly file, and the compilation  report.
>
> Reading through the log file and determining what needs to change in 
> your source file is very much your job, and you shouldn't expect 
> anyone to do your work for you. If you exhaust what you can do and ask 
> about remaining genuine problems, there will be plenty of help 
> available from people on the list. But you are expected to do at least 
> some work by identifying exactly where your problem lies. In this 
> process, you will be able to create a small example file - not your 
> actual source file - that is just enough to show the problem.
>
>>C:/Users/YERKO/Google Drive/Lily Pond/Poulenc - Flute Sonata - III. 
>>Presto giocoso.ly:27:13:
>>error: unknown escaped string: `\italics'
>>   \markup {
>>             \italics "léger et mordant"
>
> It is very easy to see what is wrong here:
> Lilypond does not recognise "\italics". That is not surprising, as the 
> keyword is "\italic" - without the "s". See 
> http://lilypond.org/doc/v2.18/Documentation/notation/formatting-text .
>
>>C:/Users/YERKO/Google Drive/Lily Pond/Poulenc - Flute Sonata - III. 
>>Presto giocoso.ly:27:24: warning: non-UTF-8 input
>>   \markup { \italics "l
>>                        éger et mordant"
>
> You have saved your .ly file in ASCII format. If you need characters 
> outside the ASCII character set (as here your accented characters), 
> you need to save it in UTF-8 format. See 
> http://lilypond.org/doc/v2.18/Documentation/notation/writing-text .
>
> In addition, you can use \markup without braces here:
> \markup \italic "léger et mordant"
> or with braces:
> \markup { \italics "léger et mordant" }
> - but you have an opening brace but no closing brace. That has left 
> the rest of your source file within that braced expression, thus 
> disabling it.
> Make this simple correction and most of your errors disappear.
>
>>C:/Users/YERKO/Google Drive/Lily Pond/Poulenc - Flute Sonata - III. 
>>Presto giocoso.ly:31:1:
>>error: unrecognized string, not in text script or \lyricmode cis4~ 
>>cis8{) r8 | r2 | r | r | c4--\f b8-- b-- | bes\( c16 bes aes8 ges\) | 
>>\pitchedTrill { b4\trill cis } ais8( b | c4) f8( c) | \pitchedTrill { 
>>b4\trill cis } ais8( b | c4) f8( c | ees2)\> | ees,2~\p | ees8 r8 
>>ees4( | ees'~) ees8 r8 |
>
> That opening brace after "cis8" is simply an error, isn't it?
>
>>C:/Users/YERKO/Google Drive/Lily Pond/Poulenc - Flute Sonata - III. 
>>Presto giocoso.ly:51:4: error: EOF found inside string
>>   \
>>    midi {  }
>>
>>C:/Users/YERKO/Google Drive/Lily Pond/Poulenc - Flute Sonata - III. 
>>Presto giocoso.ly:51:4: error: Unfinished main input
>>   \
>>    midi {  }
>>
>>C:/Users/YERKO/Google Drive/Lily Pond/Poulenc - Flute Sonata - III. 
>>Presto giocoso.ly:51:4:
>>error: syntax error, unexpected end of input
>>   \
>>    midi {  }
>>
>>fatal error: failed files:
>>"C:\\Users\\YERKO\\Google Drive\\Lily
>>Pond\\Poulenc - Flute Sonata - III. Presto giocoso.ly"
>
> These errors almost certainly come from unpaired braces somewhere in 
> your source text.
>
> Brian Barker - privately
>
>