Re: Doc: specify which \header blocks generate PDF metadata (issue 300620043 by address@hidden)

[fedelogy]

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
On 2016/07/08 11:58:31, dak wrote:
> Why are you using @bs{} here instead of just \ ?

Because I started writing that paragraph in a @warning{}, where @bs{}
was required. Then moved it out and forgot to change it.
Done

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.
On 2016/07/08 11:58:31, dak wrote:
> "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.

Done.

https://codereview.appspot.com/300620043/diff/1/Documentation/notation/input.itely#newcode1220
Documentation/notation/input.itely:1220: @address@hidden
On 2016/07/08 11:58:31, dak wrote:
> @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.

Well, it was there before my patch :)
But I'll fix it

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