From: James Lowe <james.lowe@datacore.com>
Date: Wed, 2 Jun 2010 12:31:54 +0000 (+0100)
Subject: Doc: Issue 995 added @knownissue for tuplets - NR
X-Git-Tag: release/2.13.23-1~11
X-Git-Url: https://git.donarmstrong.com/?a=commitdiff_plain;h=4e70a2dd784a2be0d9fc9b9040986d76a84a5d1d;p=lilypond.git

Doc: Issue 995 added @knownissue for tuplets - NR
---

diff --git a/Documentation/notation/rhythms.itely b/Documentation/notation/rhythms.itely
index 74f27f6fe7..e1d7476d83 100644
--- a/Documentation/notation/rhythms.itely
+++ b/Documentation/notation/rhythms.itely
@@ -293,7 +293,9 @@ Internals Reference:
 When the first note on a staff is a grace note followed by a
 tuplet the grace note must be placed before the @code{\times}
 command to avoid errors.  Anywhere else, grace notes may be
-placed within tuplet brackets.
+placed within tuplet brackets.  When using a tuplet at the beginning
+of a piece with a @code{\tempo} mark, you must add an explicit
+@code{\new Voice} as discussed in @rlearning{Voices contain music}.
 
 
 @node Scaling durations