Am 26.03.2012 19:23, schrieb James:
Sure, go for it. Could you though de-html-ize it unless you are going
to do the patch. I'd personally rather work with plain text
instruction. Thanks James
thanks - added in
https://code.google.com/p/lilypond/issues/detail?id=2442&colspec=ID%20Type%20Stat
Hello,
On 26 March 2012 15:14, Eluze wrote:
>
>
> Am 26.03.2012 02:44, schrieb David Kastrup:
>
>> Eluze writes:
>>
>>> Am 25.03.2012 23:50, schrieb David Kastrup:
Eluze writes:
> Am 25.03.2012 19:35, schrieb David Kastrup:
>
>
>
> Personally, I think it woul
sorry for the attachment...
Am 26.03.2012 16:14, schrieb Eluze:
Am 26.03.2012 02:44, schrieb David Kastrup:
Eluze writes:
Am 25.03.2012 23:50, schrieb David Kastrup:
Eluze writes:
Am 25.03.2012 19:35, schrieb David Kastrup:
Personally, I think it would make more sense if people jus
Am 26.03.2012 02:44, schrieb David Kastrup:
Eluze writes:
Am 25.03.2012 23:50, schrieb David Kastrup:
Eluze writes:
Am 25.03.2012 19:35, schrieb David Kastrup:
Personally, I think it would make more sense if people just placed
assignments to output-filename and output-suffix inside o
Eluze writes:
> Am 25.03.2012 23:50, schrieb David Kastrup:
>> Eluze writes:
>>
>>> Am 25.03.2012 19:35, schrieb David Kastrup:
>>>
>>>
>>>
>>> Personally, I think it would make more sense if people just placed
>>> assignments to output-filename and output-suffix inside of the book's
>>> paper b
Am 25.03.2012 23:50, schrieb David Kastrup:
Eluze writes:
Am 25.03.2012 19:35, schrieb David Kastrup:
Personally, I think it would make more sense if people just placed
assignments to output-filename and output-suffix inside of the book's
paper block. That's straightforward to understand
Eluze writes:
> Am 25.03.2012 19:35, schrieb David Kastrup:
>
>
>
> Personally, I think it would make more sense if people just placed
> assignments to output-filename and output-suffix inside of the book's
> paper block. That's straightforward to understand and does not require
> kee
Am 25.03.2012 19:35, schrieb David Kastrup:
Personally, I think it would make more sense if people just placed
assignments to output-filename and output-suffix inside of the book's
paper block. That's straightforward to understand and does not require
keeping magical ordering relations in mind
Eluze writes:
> Hi Mark
>
> the question was more if somebody else thinks it should be mentioned
> in the doc - but here we go;
>
> in NR 3.1.4 I suggest to add a note/warning just before the next
> chapter (3.1.5):
>
> "If in the \book there is a \paper block containing previously defined
> vari
Hi Mark
the question was more if somebody else thinks it should be mentioned in
the doc - but here we go;
in NR 3.1.4 I suggest to add a note/warning just before the next chapter
(3.1.5):
"If in the \book there is a \paper block containing previously defined
variables the \bookOutputName a
I don't know, but if you feel it should be, please refer to the following
link:
http://lilypond.org/doc/v2.15/Documentation/contributor/documentation-suggestions.html
If you think that the
docs are unclear, please suggest an improvement as described by
“Simple tasks -- Documentation” on:
http://
thanks for your quick reply - it works fine!
do you feel it should be documented?!
Eluze
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
-Eluze writes:
> this code does not produce the expected output file paper-test.pdf:
>
> aFivePaper = \paper { paperheight = 21.0 \cm }
> \book {
> \bookOutputName "paper-test"
> \relative {c d e f}
> \paper {\aFivePaper}
> }
\bookOutputName sets the output name in the paper block, so with
this code does not produce the expected output file paper-test.pdf:
aFivePaper = \paper { paperheight = 21.0 \cm }
\book {
\bookOutputName "paper-test"
\relative {c d e f}
\paper {\aFivePaper}
}
thanks
Eluze
--
View this message in context:
http://old.nabble.com/%5CbookOutputName-not-wor
14 matches
Mail list logo
