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 @code{@bs{}header} blocks located at top level ...
8 years, 9 months ago
(2016-07-08 11:58:31 UTC)
#2
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 @code{@bs{}header} blocks located at top level ...
8 years, 9 months ago
(2016-07-08 14:35:02 UTC)
#3
https://codereview.appspot.com/300620043/diff/1/Documentation/notation/input....
File Documentation/notation/input.itely (right):
https://codereview.appspot.com/300620043/diff/1/Documentation/notation/input....
Documentation/notation/input.itely:1211: output file, only @code{@bs{}header}
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....
Documentation/notation/input.itely:1214: @code{@bs{}score} 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....
Documentation/notation/input.itely:1220: @code{\header@{}
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
Issue 300620043: Doc: specify which \header blocks generate PDF metadata
(Closed)
Created 8 years, 9 months ago by fedelogy
Modified 8 years, 8 months ago
Reviewers: dak, lucyrodz07
Base URL:
Comments: 6