Re: Doc: improve doc on markup command writing (issue157133)

[ian]

Nicolas,
These are mainly stylistic changes.  Please double-check to ensure I
haven't changed the meaning of what you intended.

Cheers,
Ian


http://codereview.appspot.com/157133/diff/1/2
File Documentation/extending/programming-interface.itely (right):

http://codereview.appspot.com/157133/diff/1/2#newcode1045
Documentation/extending/programming-interface.itely:1045: The
@code{layout} and @code{props} arguments of markup commands bring a
The @code{layout} and @code{props} arguments to markup commands provide
a

http://codereview.appspot.com/157133/diff/1/2#newcode1046
Documentation/extending/programming-interface.itely:1046: context to the
markup interpretation: font size, line width, etc.
context for interpretation by the markup: e.g. font size line width etc.

http://codereview.appspot.com/157133/diff/1/2#newcode1048
Documentation/extending/programming-interface.itely:1048: Properties
defined in @code{paper} blocks are accessible through the
The @code{layout} argument allows access to properties defined in

http://codereview.appspot.com/157133/diff/1/2#newcode1049
Documentation/extending/programming-interface.itely:1049: @code{layout}
argument, using the @code{ly:output-def-lookup} function.
@code{paper} blocks, using the @code{ly:output-def-lookup} function.

http://codereview.appspot.com/157133/diff/1/2#newcode1060
Documentation/extending/programming-interface.itely:1060: title,
composer, etc.  It is also a way to configure a markup command
title, composer, etc.  It is also the way to configure the behaviour

http://codereview.appspot.com/157133/diff/1/2#newcode1061
Documentation/extending/programming-interface.itely:1061: behavior: when
a command uses e.g. the font size in its processings,
of a markup command: for example, when a command uses font size during
processing,

http://codereview.appspot.com/157133/diff/1/2#newcode1062
Documentation/extending/programming-interface.itely:1062: instead of
having a @code{font-size} argument, the font size is read
the font size is read from @code{props} rather than having a
@code{font-size}

http://codereview.appspot.com/157133/diff/1/2#newcode1063
Documentation/extending/programming-interface.itely:1063: from
@code{props}, and the caller of a markup command may change the
argument.  The caller of a markup command may change the value

http://codereview.appspot.com/157133/diff/1/2#newcode1064
Documentation/extending/programming-interface.itely:1064: value of the
font size property to change the behavior. Property values
of the font size property in order to change the behaviour.  Use the

http://codereview.appspot.com/157133/diff/1/2#newcode1065
Documentation/extending/programming-interface.itely:1065: are read from
the @code{props} argument using the @code{chain-assoc-get}
@code{chain-assoc-get} function to read property values from the
@code{props} .

http://codereview.appspot.com/157133/diff/1/2#newcode1066
Documentation/extending/programming-interface.itely:1066: function.
argument.

http://codereview.appspot.com/157133/diff/1/2#newcode1074
Documentation/extending/programming-interface.itely:1074: As an example,
a markup command which draws a double box around a piece
The following example defines a markup command to draw a double box

http://codereview.appspot.com/157133/diff/1/2#newcode1075
Documentation/extending/programming-interface.itely:1075: of text will
be defined.
around a piece of text.

http://codereview.appspot.com/157133/diff/1/2#newcode1077
Documentation/extending/programming-interface.itely:1077: First, one
should try to build an approximative result using markups.
Firstly, we need to build an approximate result using markups.

http://codereview.appspot.com/157133/diff/1/2#newcode1078
Documentation/extending/programming-interface.itely:1078: By consulting
the builtin @ruser{Text markup commands}, we find that the
Consulting the @ruser{Text markup commands} shows us the

http://codereview.appspot.com/157133/diff/1/2#newcode1103
Documentation/extending/programming-interface.itely:1103: taking one
argument (the text), and draws the two boxes, with some
taking one argument (the text).  This draws the two boxes, with some

http://codereview.appspot.com/157133/diff/1/2#newcode1129
Documentation/extending/programming-interface.itely:1129: changed by the
user.  Moreover, it would be better to distinguish
changed by the user. Also, it would be better to distinguish

http://codereview.appspot.com/157133/diff/1/2#newcode1130
Documentation/extending/programming-interface.itely:1130: between the
padding between the two boxes, from the padding between the
the padding between the two boxes, from the padding between the

http://codereview.appspot.com/157133/diff/1/2#newcode1131
Documentation/extending/programming-interface.itely:1131: inner box and
the text.  We introduce a new property,
inner box and the text. So we will introduce a new property,

http://codereview.appspot.com/157133/diff/1/2#newcode1134
Documentation/extending/programming-interface.itely:1134: as follow:
now as follows:

http://codereview.appspot.com/157133/diff/1/2#newcode1152
Documentation/extending/programming-interface.itely:1152: the comma in
the @code{\override} argument: they allow to introduce a
the comma in the @code{\override} argument: they allow you to introduce
a

http://codereview.appspot.com/157133