lilypond-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Doc: specify which \header blocks generate PDF metadata (issue 30062


From: dak
Subject: Re: Doc: specify which \header blocks generate PDF metadata (issue 300620043 by address@hidden)
Date: Fri, 08 Jul 2016 04:58:31 -0700


https://codereview.appspot.com/300620043/diff/1/Documentation/notation/input.itely
File Documentation/notation/input.itely (right):

https://codereview.appspot.com/300620043/diff/1/Documentation/notation/input.itely#newcode1211
Documentation/notation/input.itely:1211: output file, only
@address@hidden blocks located at top level or within an
Why are you using @bs{} here instead of just \ ?

https://codereview.appspot.com/300620043/diff/1/Documentation/notation/input.itely#newcode1214
Documentation/notation/input.itely:1214: @address@hidden block will
appear only in the output.
"will appear only in the output." sounds strange.  It's more like

while @code{\header} variables in a @code{\bookpart} or @code{\score}
block will be reflected in the printed output of the respective blocks,
the document-wide PDF metadata will not be affected by headers at that
level.

https://codereview.appspot.com/300620043/diff/1/Documentation/notation/input.itely#newcode1220
Documentation/notation/input.itely:1220: @address@hidden
@example creates example code.  Please don't wrap every line in @code:
this will lead to quite absurd quoting artifacts in several backends.
Inside of @example, you need to escape { } @ by preceding them with @
but that's all.

https://codereview.appspot.com/300620043/



reply via email to

[Prev in Thread] Current Thread [Next in Thread]