Re: bookOutputName variable title

2020-04-15 Thread Hans Åberg
> On 15 Apr 2020, at 22:31, Urs Liska wrote: > > Am Mittwoch, den 15.04.2020, 22:30 +0200 schrieb Hans Åberg: >>> On 15 Apr 2020, at 21:56, Urs Liska wrote: >>> >>> If you change >>> >>> \bookOutputName \title >>> to >>> \bookOutputName "test" >>> it works. >>> >>> This is because Frescobald

Re: bookOutputName variable title

2020-04-15 Thread Urs Liska
Am Mittwoch, den 15.04.2020, 22:30 +0200 schrieb Hans Åberg: > > On 15 Apr 2020, at 21:56, Urs Liska wrote: > > > > If you change > > > > \bookOutputName \title > > to > > \bookOutputName "test" > > it works. > > > > This is because Frescobaldi is not able to resolve the "\title" > > variable

Re: bookOutputName variable title

2020-04-15 Thread Hans Åberg
> On 15 Apr 2020, at 21:56, Urs Liska wrote: > > If you change > > \bookOutputName \title > to > \bookOutputName "test" > it works. > > This is because Frescobaldi is not able to resolve the "\title" > variable. This has been known for a long time and is anything but > trivial, as you can se

Re: bookOutputName variable title

2020-04-15 Thread Urs Liska
Am Mittwoch, den 15.04.2020, 12:50 -0700 schrieb thse: > In Frescobaldi, the filename of the lilypond source should be the > same as of > the output files. In your case - as long as you don't save it under a > different name - the source is named "document.ly" (at least on my > linux > system), but

Re: bookOutputName variable title

2020-04-15 Thread Aaron Hill
On 2020-04-15 12:50 pm, thse wrote: In Frescobaldi, the filename of the lilypond source should be the same as of the output files. In your case - as long as you don't save it under a different name - the source is named "document.ly" (at least on my linux system), but the produced files are "te

Re: bookOutputName variable title

2020-04-15 Thread thse
In Frescobaldi, the filename of the lilypond source should be the same as of the output files. In your case - as long as you don't save it under a different name - the source is named "document.ly" (at least on my linux system), but the produced files are "test.pdf" and "test.midi". Frescobaldi sea

Re: bookOutputName variable title

2020-04-15 Thread Gloops via bug-lilypond
Hi Torsten I thought exactly the same thing and I contacted Frescobaldi but they sent me here... Thank you for your help. Gloops -- Sent from: http://lilypond.1069038.n5.nabble.com/Bugs-f58488.html ___ bug-lilypond mailing list bug-lilypond@gnu.org h

Re: bookOutputName variable title

2020-04-15 Thread Torsten Hämmerle
Bugs mailing list wrote > I think it is a Lilypond bug but I let you judge ... > […] Hi Gloops, I can't see a LilyPond bug here because LilyPond does exactly what it is supposed to do (at least in my LilyPond/Frescobaldi/Windows environment): It creates a PDF file named test.pdf and a MIDI file n

Re: bookOutputName variable title

2020-04-15 Thread David Kastrup
Gloops via bug-lilypond writes: > Hello! > I think it is a Lilypond bug but I let you judge ... > No matter the version of Lilypond from "2.18.2" to "2.21.0" > No matter the version of Frescobaldi from "2.18" to "3.1.1" > On Windows 10 64 > Thank you > > \version "2.20.0" > > title = "test" > \bo

bookOutputName variable title

2020-04-15 Thread Gloops via bug-lilypond
Hello! I think it is a Lilypond bug but I let you judge ... No matter the version of Lilypond from "2.18.2" to "2.21.0" No matter the version of Frescobaldi from "2.18" to "3.1.1" On Windows 10 64 Thank you \version "2.20.0" title = "test" \book { \bookOutputName \title \paper { } \header {