Re: DOC: NR Dynamics context and postfix dynamics (issue3743045)

[k-ohara5a5a]

> I don't see a patch to convertrules.py.
> [...] Am I missing something?

Reinhold created the rule months ago, along with the implementation of
the new \cresc.  (I should have said "is *already* convert-ly-ed".)

> Deprecated doesn't mean removed, it means "still in
> place, but we recommend that it not be used in new
> code."

True.

> [...] when we finally remove it (for version 3.0)

That is the part that I doubted.  The syntax and usage of \dimTextDecr
looks to me the same as many other commands, like \dynamicUp



http://codereview.appspot.com/3743045/diff/10001/Documentation/notation/expressive.itely
File Documentation/notation/expressive.itely (right):

http://codereview.appspot.com/3743045/diff/10001/Documentation/notation/expressive.itely#newcode390
Documentation/notation/expressive.itely:390: Textual marks for dynamic
changes can also replace haripins:
=> "hairpins"

http://codereview.appspot.com/3743045/diff/10001/Documentation/snippets/new/dynamics-text-spanner-postfix.ly
File Documentation/snippets/new/dynamics-text-spanner-postfix.ly
(right):

http://codereview.appspot.com/3743045/diff/10001/Documentation/snippets/new/dynamics-text-spanner-postfix.ly#newcode7
Documentation/snippets/new/dynamics-text-spanner-postfix.ly:7: hairpins
by default, \cresc etc. produce text spanners by default."
@code{\cresc}

http://codereview.appspot.com/3743045/