Re: On creating "title pages" and the like

2013-11-06 Thread Paul Morris
Urs Liska wrote
> The issue is that the LSR file is written for 2.14, and the syntax has 
> changed in the meantime: \markuplines is now \markuplist.
> That's what David is referring to with his advice to use convert-ly.

The only indication that I could find on the LSR site that the snippets are
for LilyPond 2.14 is at the very bottom of the "contributing" page.  Not
somewhere that most would come across it.  

Would it make sense to include a version statement at the top of the code
for each snippet?  Maybe with a comment on using convert-ly for later
versions of LilyPond:

\version "2.14.0"
% Use convert-ly before using this code with later versions of LilyPond.  
% See the Usage manual for how to use convert-ly.

(And/or somewhere more prominent like in the header or footer of each page?)

Especially since the LSR will soon be two stable versions behind 2.18, and
it is a big job to update all the snippets to 2.18, and/or a bigger job to
get the LSR to support multiple versions of LilyPond...  adding a version
statement, in some automated way, would be a relatively simple step to help
people know what they need to do to use the snippets.

Just a suggestion,
-Paul





--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/On-creating-title-pages-and-the-like-tp153025p153456.html
Sent from the User mailing list archive at Nabble.com.

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


Re: On creating "title pages" and the like

2013-11-06 Thread David Kastrup
Joshua Nichols  writes:

> I want to apologize for inciting any frustration... I guess in my small
> mind (with limited understanding of TeX systems and the like) I thought
> when a particular documentation supported using a command that I associate
> with LaTeX, (such as the preverbal \begin and \end commands) I assumed
> someone was saying LaTeX recognizes it.

We changed the syntax at some point to be more compatible with that
manner of operation (it was \begin[options]{lilypond} at some point of
time).  But as long as nobody puts in the work for writing something
like lilypond-book.sty that does the hard work, that's more or less
cosmetic.

It _should_ have made you suspicious that no custom package was loaded
in the examples...

-- 
David Kastrup

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


Lua/LaTeX assistance (was: On creating "title pages" and the like)

2013-11-06 Thread Urs Liska

Am 06.11.2013 07:05, schrieb Joshua Nichols:
I guess in the end I didn't understand anything at all, and my hard 
head saw LaTeX and didn't see "preprocessed with lilypond-book."


Maybe this is a good opportunity to hook in.
If there is anybody out there experienced with LaTeX and Lua I'd be glad 
he/she would get in touch with me.


I have written a LaTeX package 'musicexamples' 
(http://www.openlilylib.org/musicexamples) which is currently useful but 
not spectacularly unique. I'm using it for managing music examples in my 
LaTeX documents.
It's on my agenda however to extend this package through Lua (although 
the new functionality would of course be restricted to LuaLaTeX) in 
order to accept embedded LilyPond code like lilypond-book does.
It's not the explicit intention to make a verbatim copy of 
lilypond-book, but moving the functionality _inside_ the LaTeX 
compilation process would offer at least the following fixes for 
problems that have so far led me not to use lilypond-book:


- You can compile the document at any time directly, no need for 
preprocessing and intermediate .tex files
- You don't have to chose between cluttering your working directory with 
intermediate files

  or causing relative-path problems by using the -out option
- You have reliable access to the _currently effective_ text width, e.g. 
in multicolumn context


I know that even without any prior Lua experience I would be able to 
dive into that and somehow manage to come up with something. But 
collaborating with someone who already knows the field would 
dramatically raise the probability this will become reality ...


Best
Urs

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


Re: On creating "title pages" and the like

2013-11-05 Thread Joshua Nichols
I want to apologize for inciting any frustration... I guess in my small
mind (with limited understanding of TeX systems and the like) I thought
when a particular documentation supported using a command that I associate
with LaTeX, (such as the preverbal \begin and \end commands) I assumed
someone was saying LaTeX recognizes it. I think Philippe on the forum
answered the question I was trying to ask, which is probably more like
asking "how do I directly connect lilypond-book with a LaTeX editor (as he
said, Texworks)... I guess in the end I didn't understand anything at all,
and my hard head saw LaTeX and didn't see "preprocessed with lilypond-book."

Thanks for putting up with me. I am learning a lot. :)


IC,

Josh


On Fri, Nov 1, 2013 at 5:41 PM, Joshua Nichols wrote:

> >JoshTeX systems are not required or intended to recognize either
> lilypond or
> >lilypond-book.
>
> I understood this. But from what I can see in the documentation, my
> problem isn't addressed in the lilypond documentation
>
>
> >What particularly was your problem in applying this to your case?
>
> I don't know how to get my latex system to recognize the following:
>
> \begin{lilypond}
> \relative c' {
>   c2 e2 \tuplet 3/2 { f8 a b } a2 e4
> }
> \end{lilypond}
>
>
>
>
> Probably because I don't have some package. The problem is that I don't
> see a package described anywhere... and everytime I just "try" using
> \begin{lilypond}\end{lilypond} or \lilypond {...}. When I try using
> \usepackage{lilypond}, and process through LaTeX, I get wierd looks from my
> process log
>
> ! LaTeX Error: Environment lilypond undefined.
>
>
> That's after copying and pasting the example given in the documentation.
>
>
> Help? Thanks again for dealing with me (and what I think might be an
> obvious solution).
>
>
> On Fri, Nov 1, 2013 at 10:44 AM, David Kastrup  wrote:
>
>> TeX systems are not required or intended to recognize either lilypond or
>> lilypond-book.
>>
>
>
>
> IC,
>
>
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


Re: On creating "title pages" and the like

2013-11-04 Thread Tim Roberts
David Kastrup  wrote:
> Helge Kruse  writes:
>> > C:\lybook>lilypond-book --output=out --pdf demo.lytex
>> > Usage: lilypond-book [OPTION]... FILE
>> >
>> > Process LilyPond snippets in hybrid HTML, LaTeX, texinfo or DocBook
>> > document.
> I seem to remember that Windows does something weird with = on the
> command line.

No, this is a red herring.  The Windows "shell" does not interpret the
command line in any way.  The text is passed untouched to the new
process.  It's then up to your run-time library to parse that into
argc/argv.  Different compiler run-time libraries do that slightly
differently, but even the Microsoft run-time library handles = correctly.

Now, if you were actually saying that "getopt_long mishandles = on
Windows", that's something I can't address.

-- 
Tim Roberts, t...@probo.com
Providenza & Boekelheide, Inc.

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


Re: On creating "title pages" and the like

2013-11-02 Thread Helge Kruse

Am 01.11.2013 19:13, schrieb David Kastrup:


I seem to remember that Windows does something weird with = on the
command line.


I know for sure that the equal sign is nothing special for Windows. The 
command line is passed to the process as we give it at the command line. 
The Scheme interpreter guile or the C-runtime that is used for guile 
might do further "work" with the arguments.


But that's not the problem. When I use your recommendation and write

lilypond-book -o out --pdf demo.lytex

I get the same result.

Regards
Helge

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


Re: On creating "title pages" and the like

2013-11-01 Thread flup2
If you're not confortable with the Terminal and use Texworks, you have to
tell to Texworks with command to run: lilypond-book in place of pdflatex (or
pdfxelatex etc. according to your usual LaTeX choice).

In Texworks, go to the Preferences, in the "Typesetting" tab.

In "Path for Tex...", add the path to lilypond binaries:
/Applications/LilyPond.app/Contents/Resources/bin (or another place if you
placed lilypond elsewhere)

In "Processing tools", create a new one, give it a name, and type
lilypond-book in the program field.

(under OS X, I find TeXShop easier for lilypond-book: it comes with a script
that automate a lot a things for lilypond-book)

Philippe



--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/On-creating-title-pages-and-the-like-tp153025p153228.html
Sent from the User mailing list archive at Nabble.com.

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


Re: On creating "title pages" and the like

2013-11-01 Thread David Kastrup
Joshua Nichols  writes:

>>JoshTeX systems are not required or intended to recognize either lilypond
> or
>>lilypond-book.
>
> I understood this. But from what I can see in the documentation, my problem
> isn't addressed in the lilypond documentation
>
>>What particularly was your problem in applying this to your case?
>
> I don't know how to get my latex system to recognize the following:
>
> \begin{lilypond}
> \relative c' {
>   c2 e2 \tuplet 3/2 { f8 a b } a2 e4
> }
> \end{lilypond}

LaTeX does not recognize this.  Period.  Simple as that.  The program
that recognizes this is lilypond-book, and lilypond-book then writes a
LaTeX program that LaTeX will be able to work with.

> Probably because I don't have some package.

No.  LaTeX does not recognize this.  There is no package for making it
do that.

> The problem is that I don't see a package described anywhere... and
> everytime I just "try" using \begin{lilypond}\end{lilypond} or
> \lilypond {...}. When I try using \usepackage{lilypond}, and process
> through LaTeX, I get wierd looks from my process log
>
> ! LaTeX Error: Environment lilypond undefined.

LaTeX does not recognize this.  On nobody's system.  Anywhere.  There is
no way to make it recognize it.  You use lilypond-book to convert the
file into one that LaTeX can recognize.

I don't know how I can spell this out more clearly.

-- 
David Kastrup


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


Re: On creating "title pages" and the like

2013-11-01 Thread Joshua Nichols
>JoshTeX systems are not required or intended to recognize either lilypond
or
>lilypond-book.

I understood this. But from what I can see in the documentation, my problem
isn't addressed in the lilypond documentation

>What particularly was your problem in applying this to your case?

I don't know how to get my latex system to recognize the following:

\begin{lilypond}
\relative c' {
  c2 e2 \tuplet 3/2 { f8 a b } a2 e4
}
\end{lilypond}




Probably because I don't have some package. The problem is that I don't see
a package described anywhere... and everytime I just "try" using
\begin{lilypond}\end{lilypond} or \lilypond {...}. When I try using
\usepackage{lilypond}, and process through LaTeX, I get wierd looks from my
process log

! LaTeX Error: Environment lilypond undefined.


That's after copying and pasting the example given in the documentation.


Help? Thanks again for dealing with me (and what I think might be an
obvious solution).


On Fri, Nov 1, 2013 at 10:44 AM, David Kastrup  wrote:

> TeX systems are not required or intended to recognize either lilypond or
> lilypond-book.
>



IC,
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


Re: On creating "title pages" and the like

2013-11-01 Thread David Kastrup
Helge Kruse  writes:

> C:\lybook>lilypond-book --output=out --pdf demo.lytex
> Usage: lilypond-book [OPTION]... FILE
>
> Process LilyPond snippets in hybrid HTML, LaTeX, texinfo or DocBook
> document.

I seem to remember that Windows does something weird with = on the
command line.  You either need to write

lilypond-book --output#out --pdf demo.lytex

or, if that does not work, use the short option

lilypond-book -o out --pdf demo.lytex

-- 
David Kastrup


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


Re: On creating "title pages" and the like

2013-11-01 Thread Helge Kruse

Am 01.11.2013 16:44, schrieb David Kastrup:

Joshua Nichols  writes:


Somewhat related: How in the world do I invoke lilypond or
lilypond-book in LaTeX, or TexWorks?


I don't know TexWorks, and one does not invoke lilypond or lilypond-book
in LaTeX.  lilypond-book converts a .lytex files into images and a
normal LaTeX .tex file which can be compiled using LaTeX as usual.


[...]

You did look in
http://lilypond.org/doc/v2.17/Documentation/usage/lilypond_002dbook>
?

What particularly was your problem in applying this to your case?



I just wanted to prepare an example how to use lilypond-book in 
TeXworks. But I failed to run lilypond.book too. I saved the example 
from the link you gave to a file demo.lytex. And started the program as 
show in the documentation:


-<>-<>-<>-<>-<>-<>-<>-<>
C:\lybook>dir *.lytex
 Volume in drive C has no label.
 Volume Serial Number is 60D0-9F85

 Directory of C:\lybook

01.11.2013  18:27   635 demo.lytex
   1 File(s)635 bytes
   0 Dir(s)  113.230.843.904 bytes free

C:\lybook>lilypond-book --output=out --pdf demo.lytex
Usage: lilypond-book [OPTION]... FILE

Process LilyPond snippets in hybrid HTML, LaTeX, texinfo or DocBook 
document.


Examples:
 $ lilypond-book --filter="tr '[a-z]' '[A-Z]'" BOOK
 $ lilypond-book -F "convert-ly --no-version --from=2.0.0 -" BOOK
 $ lilypond-book --process='lilypond -I include' BOOK

Options:
[a lot of options skipped]
-<>-<>-<>-<>-<>-<>-<>-<>
It looks like lilypond-book does not know what I want it to do.

Regards
Helge

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


Re: On creating "title pages" and the like

2013-11-01 Thread David Kastrup
Joshua Nichols  writes:

> Somewhat related: How in the world do I invoke lilypond or
> lilypond-book in LaTeX, or TexWorks?

I don't know TexWorks, and one does not invoke lilypond or lilypond-book
in LaTeX.  lilypond-book converts a .lytex files into images and a
normal LaTeX .tex file which can be compiled using LaTeX as usual.

> I hate to sound idiotic, but I don't see *anything* talking about how
> to use lilypond-book in TeX systems anywhere. The documentation in
> lilypond.orgonly describes how to use it, but I don't see a full
> example with inclusions on how to get any TeX system to recognize
> lilypond, or lilypond-book.

TeX systems are not required or intended to recognize either lilypond or
lilypond-book.

> I'm a bit frustrated about this; I spent hours looking this up. HELP?
> What am I missing?!? I hope this is an idiotic claim; I hope someone
> can be patient with me about this.

You did look in
http://lilypond.org/doc/v2.17/Documentation/usage/lilypond_002dbook>
?

What particularly was your problem in applying this to your case?

-- 
David Kastrup

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


Re: On creating "title pages" and the like

2013-11-01 Thread Joshua Nichols
I've tried using the terminal, I cannot get anything to pull up. Truth be
told, however, I feel a bit turned around. But your help and support is
wonderful, and I will keep hacking at it until I can get something to work.

There were examples scrubbed in the mailing list that I was not able to
look at (other than this extendable one quoted a couple times). Help on
that?

Somewhat related: How in the world do I invoke lilypond or lilypond-book in
LaTeX, or TexWorks?

I hate to sound idiotic, but I don't see *anything* talking about how to
use lilypond-book in TeX systems anywhere. The documentation in
lilypond.orgonly describes how to use it, but I don't see a full
example with
inclusions on how to get any TeX system to recognize lilypond, or
lilypond-book.

I'm a bit frustrated about this; I spent hours looking this up. HELP? What
am I missing?!? I hope this is an idiotic claim; I hope someone can be
patient with me about this.

IC,

Josh


On Tue, Oct 29, 2013 at 2:24 PM, Graham King wrote:

> **
> Josh,
> you can run convert-ly from the command line
> (/Applications/Utilities/Terminal.app) using the commands in my previous
> post to this thread this afternoon.  I hope you have better luck than I had!
>
> -- Graham
>
>
> On Tue, 2013-10-29 at 11:41 -0500, Joshua Nichols wrote:
>
> I have no idea how to do that. I'm using MacOSX, and I'm not familiar with
> internals.
>
>
>  IC,
>
> Josh
>
>
>
>  On Mon, Oct 28, 2013 at 1:54 AM, David Kastrup  wrote:
>
>  Kevin Tough  writes:
>
> > My lilypond install of 2.16.2 cannot parse the input file. It hangs at
> > fatal error:  failed files: "SnippetForBookWithTitleAndTOC"
> > (4 of 29): error: unknown escaped string: *\markuplines'
>
>
>   Did you run
>
> convert-ly -ed
>
> on the file in order to upgrade the syntax to version 2.16.2 ?
>
> --
> David Kastrup
>
>
>
>  ___lilypond-user mailing 
> listlilypond-user@gnu.orghttps://lists.gnu.org/mailman/listinfo/lilypond-user
>
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


Re: On creating "title pages" and the like (with snippet 368)

2013-10-31 Thread Graham King
Hi Harm,
I don't know what caused all the trouble either.  Perhaps it was because
my editor (eclipse) was not using unicode by default (now fixed!).  In
any case, the result is now working for me and I have a neat score.

all the best
-- Graham

On Thu, 2013-10-31 at 15:57 +0100, Thomas Morley wrote:

> 2013/10/31 Graham King :
> > Here's some progress in getting snippet 368 to run with lilypond 2.16.2.
> [...]
> 
> Hi Graham,
> 
> I followed this thread only cursorily.
> Though, now I tried it out and had no problems with said snippet.
> 
> I copied it to file with \version "2.14.2" statement.
> Ran convert-ly -e
> Compiled it successfully with 2.16.2
> 
> No idea what's the problem for you.
> 
> 
> 
> Cheers,
>   Harm
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


Re: On creating "title pages" and the like (with snippet 368)

2013-10-31 Thread Thomas Morley
2013/10/31 Graham King :
> Here's some progress in getting snippet 368 to run with lilypond 2.16.2.
[...]

Hi Graham,

I followed this thread only cursorily.
Though, now I tried it out and had no problems with said snippet.

I copied it to file with \version "2.14.2" statement.
Ran convert-ly -e
Compiled it successfully with 2.16.2

No idea what's the problem for you.



Cheers,
  Harm

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


Re: On creating "title pages" and the like (with snippet 368)

2013-10-31 Thread Graham King
Here's some progress in getting snippet 368 to run with lilypond 2.16.2.
I suspect that guile has, at some point, become unicode-aware, so I

  * downloaded the snippet  from
http://nicolas.sceaux.free.fr/tmp/book-titling.ily not from
http://lsr.dsi.unimi.it/LSR/Item?id=368 (where the character
encoding is messed up) - see

http://www.archivum.info/lilypond-user@gnu.org/2008-01/00557/Re-Lilypond-book-and-LaTeX-a-few-issues.html
  * saved the embedded, commented, example to a separate file;
  * added a statement: \version "2.11.0" to both files;
  * ran convert-ly on both files;
  * changed two lines in book-titling.ily:

%#(let ((lower-case-accented-string "éèêëáà âäí
ìîïóòôöúùûüçœæ")
%   (upper-case-accented-string "ÉÈÊËÃÀÂÄÃÌÎÃÓÒÔÖÚÙÛÜÇŒÆ"))
#(let ((lower-case-accented-string "é")
   (upper-case-accented-string "É"))

  * changed the encoding of both files to unicode in my editor
(eclipse);
  * in the example file, changed the two special characters (lines
13 and 31) to the equivalent unicode characters;
  * compiled book-titling.ily and the example.

The way ahead is probably to avoid the entire section of
book-titling.ily that deals with "accented characters" by using unicode
in the source file for your score.

If this works, then clearly I've left book-titling.ily containing a lot
of now-redundant code.

hope it helps
-- Graham


On Tue, 2013-10-29 at 12:44 +, Graham King wrote:

> I ran convert-ly -ed as suggested, and then ran lilypond on the
> resulting file to have a look at the embedded example.  
> Here's the resulting error message (lilypond 2.16.2 on OSX 10.6.8):



> 
> On Mon, 2013-10-28 at 07:54 +0100, David Kastrup wrote: 
> 
> > Kevin Tough  writes:
> > 
> > > My lilypond install of 2.16.2 cannot parse the input file. It hangs at 
> > > fatal error:  failed files: "SnippetForBookWithTitleAndTOC"
> > > (4 of 29): error: unknown escaped string: *\markuplines'
> > 
> > Did you run
> > 
> > convert-ly -ed
> > 
> > on the file in order to upgrade the syntax to version 2.16.2 ?
> > 
> 
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


Re: On creating "title pages" and the like

2013-10-29 Thread Graham King
Josh,
you can run convert-ly from the command line
(/Applications/Utilities/Terminal.app) using the commands in my previous
post to this thread this afternoon.  I hope you have better luck than I
had!

-- Graham

On Tue, 2013-10-29 at 11:41 -0500, Joshua Nichols wrote:
> I have no idea how to do that. I'm using MacOSX, and I'm not familiar
> with internals. 
> 
> 
> IC,
> 
> Josh
> 
> 
> 
> 
> On Mon, Oct 28, 2013 at 1:54 AM, David Kastrup  wrote:
> 
> Kevin Tough  writes:
> 
> > My lilypond install of 2.16.2 cannot parse the input file.
> It hangs at
> > fatal error:  failed files: "SnippetForBookWithTitleAndTOC"
> > (4 of 29): error: unknown escaped string: *\markuplines'
> 
> 
> 
> Did you run
> 
> convert-ly -ed
> 
> on the file in order to upgrade the syntax to version 2.16.2 ?
> 
> --
> David Kastrup
> 
> 
> 
> 
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


Re: On creating "title pages" and the like

2013-10-29 Thread Joshua Nichols
I have no idea how to do that. I'm using MacOSX, and I'm not familiar with
internals.

IC,

Josh


On Mon, Oct 28, 2013 at 1:54 AM, David Kastrup  wrote:

> Kevin Tough  writes:
>
> > My lilypond install of 2.16.2 cannot parse the input file. It hangs at
> > fatal error:  failed files: "SnippetForBookWithTitleAndTOC"
> > (4 of 29): error: unknown escaped string: *\markuplines'
>
> Did you run
>
> convert-ly -ed
>
> on the file in order to upgrade the syntax to version 2.16.2 ?
>
> --
> David Kastrup
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


Re: On creating "title pages" and the like

2013-10-29 Thread Graham King
I ran convert-ly -ed as suggested, and then ran lilypond on the
resulting file to have a look at the embedded example.  
Here's the resulting error message (lilypond 2.16.2 on OSX 10.6.8):


Processing `book-titling.ily'

Parsing.../Applications/LilyPond.app/Contents/Resources/bin/../share/guile/1.8/ice-9/regex.scm:180:45:
 In procedure make-regexp in expression (make-regexp regexp):

/Applications/LilyPond.app/Contents/Resources/bin/../share/guile/1.8/ice-9/regex.scm:180:45:
 illegal byte sequence
LilyPond terminated in 0.673 seconds.


Curiously, before spotting the suggested "-ed" options to convert-ly, I
had tried adding a \version "2.14.0" statement to the top of the file
and running convert-ly without options.  Eeek!


$ /Applications/LilyPond.app/Contents/Resources/bin/convert-ly
book-titling-a.ily > book-titling-a.convert-ly.ily
convert-ly (GNU LilyPond) 2.16.2

convert-ly: Processing `book-titling-a.ily'... 
Applying conversion: 2.15.7, 2.15.9, 2.15.10, 2.15.16, 2.15.17,
2.15.18, 2.15.19, 2.15.20, 2.15.25, 2.15.32, 2.15.39, 2.15.40,
2.15.42, 2.15.43, 2.16.0


Traceback (most recent call last):
  File
"/Applications/LilyPond.app/Contents/Resources/bin/convert-ly",
line 374, in 
main ()
  File
"/Applications/LilyPond.app/Contents/Resources/bin/convert-ly",
line 362, in main
do_one_file (f)
  File
"/Applications/LilyPond.app/Contents/Resources/bin/convert-ly",
line 316, in do_one_file
outfile.write (result)
  File

"/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/codecs.py",
 line 351, in write
data, consumed = self.encode(object, self.errors)
UnicodeDecodeError: 'utf8' codec can't decode byte 0x8e in
position 1331: invalid start byte


and, in a spirit of inquiry, thought I might have a look inside
convert-ly:


$
file /Applications/LilyPond.app/Contents/Resources/bin/convert-ly
/Applications/LilyPond.app/Contents/Resources/bin/convert-ly:
ERROR: line 163: regex error 17, (illegal byte sequence)


I suspect that there might be a problem with convert-ly on OSX.

kind regards
-- Graham King

On Mon, 2013-10-28 at 07:54 +0100, David Kastrup wrote:

> Kevin Tough  writes:
> 
> > My lilypond install of 2.16.2 cannot parse the input file. It hangs at 
> > fatal error:  failed files: "SnippetForBookWithTitleAndTOC"
> > (4 of 29): error: unknown escaped string: *\markuplines'
> 
> Did you run
> 
> convert-ly -ed
> 
> on the file in order to upgrade the syntax to version 2.16.2 ?
> 
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


Re: On creating "title pages" and the like

2013-10-28 Thread Urs Liska

Am 28.10.2013 05:22, schrieb Kevin Tough:

My lilypond install of 2.16.2 cannot parse the input file. It hangs at
fatal error:  failed files: "SnippetForBookWithTitleAndTOC"
(4 of 29): error: unknown escaped string: *\markuplines'
I am guessing now that a snippet then is a separate file that should be
located somewhere where Lilypond can find it.


No, that's not the issue.


Only respond to this mail if you have had a problem with the file. I
will dig into the documentation about snippets, should I need to get
this working.


The issue is that the LSR file is written for 2.14, and the syntax has 
changed in the meantime: \markuplines is now \markuplist.

That's what David is referring to with his advice to use convert-ly.

HTH
Urs



Cheers,
Kevin Tough

On Sun, 2013-10-27 at 21:07 -0500, James wrote:

On Oct 27, 2013, at 19:03 , Joshua Nichols wrote:


I'm not familiar enough to know how well LilyPond works with creating separate 
title pages...

Is there a feasible way of doing this within LilyPond?

I'm not talking about using TeX, LaTeX, or invoking "lilypond-book," but just 
through the use of markups, etc

Or, perhaps a compromise is available?

Thanks for your thoughts!

Sincerely,

Josh

I've heavily adapted this snippet for my own use. It should be a starting place 
at least to develop your own.
http://lsr.dsi.unimi.it/LSR/Item?id=368

James Worlton


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user



___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user



___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


Re: On creating "title pages" and the like

2013-10-28 Thread Helge Kruse

Am 28.10.2013 01:03, schrieb Joshua Nichols:

I'm not familiar enough to know how well LilyPond works with creating
separate title pages...

Is there a feasible way of doing this within LilyPond?



Here is a complete real live example. It might be improved though.

Regards
Helge


%=
%
%   Konservatorium Schwerin
%
%   author: Helge Kruse   
%
%=

\version "2.16.0"


#(ly:set-option 'midi-extension "midi") 
#(ly:set-option 'delete-intermediate-files #t)
#(ly:set-option 'point-and-click #f)

#(set-default-paper-size "a4")

%\include "../../Tools/Tools.ily"
%% Bookpart first page and last page predicates
  #(define (not-part-first-page layout props arg)
 (if (= (chain-assoc-get 'page:page-number props -1)
(ly:output-def-lookup layout 'first-page-number))
 empty-stencil
 (interpret-markup layout props arg)))

  #(define (part-first-page layout props arg)
 (if (= (chain-assoc-get 'page:page-number props -1)
(ly:output-def-lookup layout 'first-page-number))
 (interpret-markup layout props arg)
 empty-stencil
 ))


\paper {
  %%set to ##t if your score is less than one page: 
  ragged-last-bottom = ##t
  ragged-bottom = ##f  

  oddFooterMarkup = \markup { \on-the-fly #part-first-page \teeny { Notensatz: Helge Kruse } }
  oddHeaderMarkup = \markup \fill-line {
""
\on-the-fly #not-part-first-page \fromproperty #'header:composer
\on-the-fly #not-part-first-page \fromproperty #'header:title
\on-the-fly #not-part-first-page \fromproperty #'header:instrument
\on-the-fly #print-page-number-check-first \fromproperty #'page:page-number-string
  }
  evenHeaderMarkup = \markup \fill-line {
\on-the-fly #print-page-number-check-first \fromproperty #'page:page-number-string
\on-the-fly #not-part-first-page \fromproperty #'header:instrument
\on-the-fly #not-part-first-page \fromproperty #'header:title
\on-the-fly #not-part-first-page \fromproperty #'header:composer
""
  }
  
  tocTitleMarkup = \markup \huge \column {
\hspace #1
\hspace #1
\fill-line { \null "Inhaltsverzeichnis" \null }
\hspace #1
\hspace #1
  }
  tocItemMarkup = \markup \fill-line {
\fromproperty #'toc:text \fromproperty #'toc:page
  }
}

changeBeaming = \set beamExceptions =
#'((end . (
((1 . 8) . (2 2 2 2))
((1 . 16) . (4 4 4 4))
((1 . 24) . (3 3 3 3 3 3 3 3))
((1 . 32) . (8 8 8 8))
))) 

revertBeaming = \set beamExceptions = #'() 

hideTuplet = {
  \override TupletNumber #'stencil = ##f
  \override TupletBracket #'bracket-visibility = ##f
}

showTuplet = {
  \revert TupletNumber #'stencil
  \override TupletBracket #'bracket-visibility = ##t
}


%\include "Allegro.ly"
AllegroCornoOne = \relative c'' { c }
AllegroCornoTwo = \relative c'' { c }
AllegroViolinoOne = \relative c'' { c }
AllegroViolinoTwo = \relative c'' { c }
AllegroViola = \relative c'' { c }
AllegroBasso = \relative c' { c }
AllegroHarpRight = \relative c'' { c }
AllegroHarpLeft = \relative c' { c }

%\include "Affettuoso.ly"
AffettuosoFlautoOne = \relative c'' { c }
AffettuosoFlautoTwo = \relative c'' { c }
AffettuosoViolinoOne = \relative c'' { c }
AffettuosoViolinoTwo = \relative c'' { c }
AffettuosoViola = \relative c'' { c}
AffettuosoBasso = \relative c' { c }
AffettuosoHarpRight= \relative c'' { c }
AffettuosoHarpLeft = \relative c' { c }

%\include "AllegroNonTroppo.ly"
AllegroNonTroppoCornoOne = \relative c'' { c }
AllegroNonTroppoCornoTwo = \relative c'' { c }
AllegroNonTroppoViolinoOne = \relative c'' { c }
AllegroNonTroppoViolinoTwo = \relative c'' { c }
AllegroNonTroppoViola = \relative c'' { c }
AllegroNonTroppoBasso = \relative c' { c }
AllegroNonTroppoHarpRight = \relative c'' { c }
AllegroNonTroppoHarpLeft = \relative c' { c }

\book {
  \bookpart {
\header {
  title = \markup \center-column { " " " " " " " " "Concerto in G" " " "per la Arpa o il Cembalo concertato" " " " " }
  subtitle = \markup \center-column { "accompagnate " "da due Violini e Basso," "con due Corni e due Flauti per rinforza" " " " " " " " " }
  dedication = "Giovanni Guglielmo Hertel"
  date = "1727-1789"
  tagline = ##f
  copyright = ##f
}
\markuplist \table-of-contents
\pageBreak
  }
 
  \bookpart {
\tocItem \markup {Partitur}
\header {
  title="Concerto per la Arpa"
  composer = "Hertel"
}

\tocItem \markup {"   Allegro"}
\score {
  <<
\new StaffGroup <<
  \new Staff=CornoOne \with { instrumentName = #"Corno 1" } { \AllegroCornoOne  }
  \new Staff=CornoTwo \with { instrumentName = #"Corno 2" } { \AllegroCornoTwo }
>>
\new StaffGroup <<
  \new Staff=ViolinoOne \with { instrumentName = #"Violino 1" } { \AllegroViolinoOne }
  \new Staff=ViolinoTwo \with { instrumentName = #"Violino 2"  }{ \AllegroViolinoTwo }
>>
\new Staff=Viola \with { instrum

Re: On creating "title pages" and the like

2013-10-27 Thread David Kastrup
Kevin Tough  writes:

> My lilypond install of 2.16.2 cannot parse the input file. It hangs at 
> fatal error:  failed files: "SnippetForBookWithTitleAndTOC"
> (4 of 29): error: unknown escaped string: *\markuplines'

Did you run

convert-ly -ed

on the file in order to upgrade the syntax to version 2.16.2 ?

-- 
David Kastrup

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


Re: On creating "title pages" and the like

2013-10-27 Thread Joshua Nichols
> Only respond to this mail if you have had a problem with the file.

Thanks, I had the fatal error too. What should be the next step?

I apologize in advance for the lack of mobility with programming. I'm
hoping that I can get better at this soon.

IC,

Josh


On Sun, Oct 27, 2013 at 11:22 PM, Kevin Tough  wrote:

> My lilypond install of 2.16.2 cannot parse the input file. It hangs at
> fatal error:  failed files: "SnippetForBookWithTitleAndTOC"
> (4 of 29): error: unknown escaped string: *\markuplines'
> I am guessing now that a snippet then is a separate file that should be
> located somewhere where Lilypond can find it.
> Only respond to this mail if you have had a problem with the file. I
> will dig into the documentation about snippets, should I need to get
> this working.
>
> Cheers,
> Kevin Tough
>
> On Sun, 2013-10-27 at 21:07 -0500, James wrote:
> > On Oct 27, 2013, at 19:03 , Joshua Nichols wrote:
> >
> > > I'm not familiar enough to know how well LilyPond works with creating
> separate title pages...
> > >
> > > Is there a feasible way of doing this within LilyPond?
> > >
> > > I'm not talking about using TeX, LaTeX, or invoking "lilypond-book,"
> but just through the use of markups, etc
> > >
> > > Or, perhaps a compromise is available?
> > >
> > > Thanks for your thoughts!
> > >
> > > Sincerely,
> > >
> > > Josh
> >
> > I've heavily adapted this snippet for my own use. It should be a
> starting place at least to develop your own.
> > http://lsr.dsi.unimi.it/LSR/Item?id=368
> >
> > James Worlton
> >
> >
> > ___
> > lilypond-user mailing list
> > lilypond-user@gnu.org
> > https://lists.gnu.org/mailman/listinfo/lilypond-user
>
>
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


Re: On creating "title pages" and the like

2013-10-27 Thread Kevin Tough
My lilypond install of 2.16.2 cannot parse the input file. It hangs at 
fatal error:  failed files: "SnippetForBookWithTitleAndTOC"
(4 of 29): error: unknown escaped string: *\markuplines'
I am guessing now that a snippet then is a separate file that should be
located somewhere where Lilypond can find it.
Only respond to this mail if you have had a problem with the file. I
will dig into the documentation about snippets, should I need to get
this working.

Cheers,
Kevin Tough 

On Sun, 2013-10-27 at 21:07 -0500, James wrote:
> On Oct 27, 2013, at 19:03 , Joshua Nichols wrote:
> 
> > I'm not familiar enough to know how well LilyPond works with creating 
> > separate title pages...
> > 
> > Is there a feasible way of doing this within LilyPond? 
> > 
> > I'm not talking about using TeX, LaTeX, or invoking "lilypond-book," but 
> > just through the use of markups, etc
> > 
> > Or, perhaps a compromise is available?
> > 
> > Thanks for your thoughts!
> > 
> > Sincerely,
> > 
> > Josh
> 
> I've heavily adapted this snippet for my own use. It should be a starting 
> place at least to develop your own.
> http://lsr.dsi.unimi.it/LSR/Item?id=368
> 
> James Worlton
> 
> 
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user



___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


Re: On creating "title pages" and the like

2013-10-27 Thread Nick Payne

On 28/10/13 11:03, Joshua Nichols wrote:
I'm not familiar enough to know how well LilyPond works with creating 
separate title pages...


Is there a feasible way of doing this within LilyPond?


Here's my template for this. It allows for multiple pieces within the 
document - just delete the additional bootparts and the


\markuplist \table-of-contents if you only have one piece and don't need 
a ToC.


\version "2.17.29"

date = #(strftime "%d/%m/%Y" (localtime (current-time)))

\paper {
  #(define (print-positive-page-number layout props arg)
 (if (> (chain-assoc-get 'page:page-number props -1) 0)
 (create-page-number-stencil layout props arg)
 empty-stencil))
  
  #(define (not-last-page layout props arg)
 (if (and (chain-assoc-get 'page:is-bookpart-last-page props #f)
  (chain-assoc-get 'page:is-last-bookpart props #f))
 empty-stencil
 (interpret-markup layout props arg)))
  
  print-all-headers = ##f
  first-page-number = -1
  tocItemMarkup = \tocItemWithDotsMarkup
  oddHeaderMarkup = \markup \fill-line { " " }
  evenHeaderMarkup = \oddHeaderMarkup
  oddFooterMarkup = \markup \fill-line { \column { \fontsize #-1
\on-the-fly #not-first-page \on-the-fly #not-last-page 
\on-the-fly #print-positive-page-number \fromproperty #'page:page-number-string
\on-the-fly #last-page \fromproperty #'header:tagline
  } }
  evenFooterMarkup = \oddFooterMarkup
}

\header {
  title = \markup {
\lower #50 \left-align \center-column { 
  \fontsize #4 \bold "Overall Title"
}
  }
  subtitle = \markup {
\lower #4 \left-align \center-column { 
  \fontsize #1 \bold "Overall Subtitle"
}
  }
  tagline = \markup {
\fontsize #-3.5 {
  \override #'(box-padding . 1.0) \override #'(baseline-skip . 2.7) \box \center-column {
\line {
  Engraved on \date using \with-url #"http://lilypond.org/";
  \line {
LilyPond \simple #(lilypond-version) (http://lilypond.org/)
  }
}
  }
}
  }
}

\pageBreak

\markuplist \table-of-contents
\markup \null

\bookpart {
  \paper {
print-page-number = ##t
  }
  \header { 
title = \markup { \fromproperty #'toc:number " Piece One" } % overrides overall title
subtitle = ##f % prevent overall subtitle from appearing
composer = "Composer One"
  } 
  \tocItem \markup { 1. Piece One }
  \relative c' { c1 }
}

\bookpart {
  \paper {
print-page-number = ##t
  }
  \header { 
title = \markup { \fromproperty #'toc:number " Piece Two" } % overrides overall title
subtitle = ##f % prevent overall subtitle from appearing
composer = "Composer Two"
  }
  \tocItem \markup { 2. Piece Two }
  \relative c' { c1 }
}

\bookpart {
  \paper {
print-page-number = ##t
  }
  \header {
title = \markup { \fromproperty #'toc:number " Piece Three" } % overrides overall title
subtitle = ##f % prevent overall subtitle from appearing
composer = "Composer Three"
  }
  \tocItem \markup { 3. Piece Three }
  \relative c' { c1 }
}
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


Re: On creating "title pages" and the like

2013-10-27 Thread SoundsFromSound
That's a great snippet James! I've based my title and instrument list pages
off that one as well. Josh, you should check that out and see if you can
make your own custom template.

Ben


James Worlton wrote
> On Oct 27, 2013, at 19:03 , Joshua Nichols wrote:
> 
>> I'm not familiar enough to know how well LilyPond works with creating
>> separate title pages...
>> 
>> Is there a feasible way of doing this within LilyPond? 
>> 
>> I'm not talking about using TeX, LaTeX, or invoking "lilypond-book," but
>> just through the use of markups, etc
>> 
>> Or, perhaps a compromise is available?
>> 
>> Thanks for your thoughts!
>> 
>> Sincerely,
>> 
>> Josh
> 
> I've heavily adapted this snippet for my own use. It should be a starting
> place at least to develop your own.
> http://lsr.dsi.unimi.it/LSR/Item?id=368
> 
> James Worlton
> 
> 
> ___
> lilypond-user mailing list

> lilypond-user@

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





-
composer | sound designer 
LilyPond Tutorials (for beginners) --> http://bit.ly/bcl-lilypond
--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/On-creating-title-pages-and-the-like-tp153025p153028.html
Sent from the User mailing list archive at Nabble.com.

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


Re: On creating "title pages" and the like

2013-10-27 Thread James

On Oct 27, 2013, at 19:03 , Joshua Nichols wrote:

> I'm not familiar enough to know how well LilyPond works with creating 
> separate title pages...
> 
> Is there a feasible way of doing this within LilyPond? 
> 
> I'm not talking about using TeX, LaTeX, or invoking "lilypond-book," but just 
> through the use of markups, etc
> 
> Or, perhaps a compromise is available?
> 
> Thanks for your thoughts!
> 
> Sincerely,
> 
> Josh

I've heavily adapted this snippet for my own use. It should be a starting place 
at least to develop your own.
http://lsr.dsi.unimi.it/LSR/Item?id=368

James Worlton


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


On creating "title pages" and the like

2013-10-27 Thread Joshua Nichols
I'm not familiar enough to know how well LilyPond works with creating
separate title pages...

Is there a feasible way of doing this within LilyPond?

I'm not talking about using TeX, LaTeX, or invoking "lilypond-book," but
just through the use of markups, etc

Or, perhaps a compromise is available?

Thanks for your thoughts!

Sincerely,

Josh
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user