---
** [issues:#4761] several errors in NR chapter 5**
**Status:** Accepted
**Created:** Mon Feb 01, 2016 04:29 PM UTC by Federico Bruni
**Last Updated:** Mon Feb 01, 2016 04:29 PM UTC
**Owner:** nobody
While translating the 5th chapter of Notation Reference I found some minor
errors or things to improve.
The last one is probably the most important to be fixed.
a) 5.1.1 Contexts explained
"""
DrumStaff
Handles typesetting for percussion. Can contain DrumVoice
"""
Missing trailing dot.
b) 5.2.3 Determining the grob property
"""
Inserting this command before the Fingering object is created, i.e., before c2,
yields the following result:
"""
i.e., before c-2,
c) 5.2.4 Naming conventions
"""
scheme functions: lowercase-with-hyphens (incl. one-word names)
scheme functions: ly:plus-scheme-style
"""
isn't ly:plus-scheme-style a _lilypond_ scheme function? (then different from
the first item)
d) 5.3.5 \set vs. \override
"""
In contrast to ordinary context properties, grob definitions have the
bookkeeping required to keep track of its parts, the individual grob properties
(and even subproperties of them) separately so that it is possible to define
those parts in different contexts and have the overall grob definition at the
time of grob creation be assembled from pieces provided in different contexts
among the current context and its parents.
"""
This sentence is too long and complex.
e) 5.4.1 Input modes
"""
To create fret diagrams above a staff, you have two choices. You can either use
the FretBoards context (see Automatic fret diagrams or you can enter them...
"""
missing closing ) --> (see Automatic fret diagrams)
f) 5.4.2 Direction and placement
"""
For more information. See @ref{Multiple voices}.
"""
dot should be replaced with a comma: For more information, see...
g) 5.4.6 Spanners
"""
arrow
Setting this sub-property to #t produces an arrowhead at the end of the
line.
"""
Shouldn'be more correct "at the end points of the line"? Because it depends
on the command used:
\override TextSpanner.bound-details.left.arrow = ##t
\override TextSpanner.bound-details.right.arrow = ##t
i) 5.4.7 Visibility of objects
"""
Double percent repeats are either all printed or all suppressed. Use begin-of
line-invisible to print and all-invisible to suppress.
"""
--> begin-of-line-invisible (there's a space instead)
j) 5.5.3 Modifying the stencils
"""
Any of the glyphs in the feta Font can be supplied to the \musicglyph markup
command
"""
feta Font --> Feta font
k) 5.5.6 unpure-pure containers
"""
In the first measure, without the unpure-pure container, the spacing engine
does not know the width of the note head and lets it collide with the
accidentals. In the second measure, with unpure-pure containers, the spacing
engine knows the width of the note heads and avoids the collision by
lengthening the line accordingly.
"""
The collision is present in version 2.16 of manuals, but it seems that LilyPond
is smart enough since version 2.18.
We should find another example of collision...
...
---
Sent from sourceforge.net because [email protected] is
subscribed to https://sourceforge.net/p/testlilyissues/issues/
To unsubscribe from further messages, a project admin can change settings at
https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is
a mailing list, you can unsubscribe from the mailing list.------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140
_______________________________________________
Testlilyissues-auto mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
