Reviewers: Graham Percival,
Message:
On 2013/04/11 22:37:41, Graham Percival wrote:
I think it would be nicer if we could find a word that wasn't a
command word
("modifications"? "adjustments" ? "customizations"?) but I agree
that in this
case "override" is better than "tweak".
Yes, we need a word or phrase that can be used to replace
tweaks and tweaking in all the places where they are used
generically, leaving tweaks and tweaking to refer to the
specific use of \tweak as a command. Earlier, when \tweak
as a comand was rarely used, no confusion arose, but now that
\tweak is more useful and is appearing more frequently in
replies and documentation I think the time has come to make
the change. Although long, I think "fine-tuning the layout"
captures the generic meaning of tweaking quite well, and once
introduced it could be shortened to just "fine-tuning". The
noun could be "fine-tuning adjustments."
So this section could entitled "Using variables for fine-tuning"
or "Using variables for fine-tuning the layout".
The main difficulty with this, and the reason why I'm looking
for further comment, is that many tweaks and overrides are rather
more than _fine_-tuning, but I think I could live with this.
Trevor
Description:
Doc: rename section in LM (3280)
In the LM, the word "tweaks" is used both generically, meaning
"modifying LilyPond's action", and specifically to refer to the
\tweak command. The old section heading used the word in the former
sense, but this was confusing as the section dealt exclusively
with \override commands.
Please review this at https://codereview.appspot.com/8575044/
Affected files:
M Documentation/learning/fundamental.itely
M Documentation/learning/tweaks.itely
Index: Documentation/learning/fundamental.itely
diff --git a/Documentation/learning/fundamental.itely
b/Documentation/learning/fundamental.itely
index
482425df14fa14818bf55b9b2dcad81caf8de36b..b50c5f27745feda38fe5e92af719fd8f97e4735b
100644
--- a/Documentation/learning/fundamental.itely
+++ b/Documentation/learning/fundamental.itely
@@ -749,7 +749,7 @@ used here) reverts the style back to the default.
We shall see later how commands like these may be created by the
user.
See @ref{Visibility and color of objects} and
-@ref{Using variables for tweaks}.
+@ref{Using variables for overrides}.
@cindex polyphony and relative note entry
@cindex relative note entry and polyphony
Index: Documentation/learning/tweaks.itely
diff --git a/Documentation/learning/tweaks.itely
b/Documentation/learning/tweaks.itely
index
3d88ca1c684a3404824c9c3aa54614a1ea07d083..d9867b45aae3c6afd5a19974ee7ffa11c738ba24
100644
--- a/Documentation/learning/tweaks.itely
+++ b/Documentation/learning/tweaks.itely
@@ -3572,7 +3572,7 @@ lhMusic = \relative c' {
@menu
* Other uses for tweaks::
-* Using variables for tweaks::
+* Using variables for overrides::
* Style sheets::
* Other sources of information::
* Advanced tweaks with Scheme::
@@ -3751,12 +3751,12 @@ second (with the stencil removed) does not.
Music Glossary:
@rglos{system}.
-@node Using variables for tweaks
-@subsection Using variables for tweaks
+@node Using variables for overrides
+@subsection Using variables for overrides
-@cindex variables, using for tweaks
-@cindex using variables for tweaks
-@cindex tweaks, using variables for
+@cindex variables, using for overrides
+@cindex using variables for overrides
+@cindex overrides, using variables for
Override commands are often long and tedious to type, and they
have to be absolutely correct. If the same overrides are to be
_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
