X-Git-Url: https://www.chiark.greenend.org.uk/ucgi/~mdw/git/mup/blobdiff_plain/cdb3c0882392596f814cf939cbfbd38adc6f2bfe..ddf6330b56bcfb657e0186b24b9b1422c51d3424:/mup/docs/uguide/mantup.html diff --git a/mup/docs/uguide/mantup.html b/mup/docs/uguide/mantup.html new file mode 100644 index 0000000..823284c --- /dev/null +++ b/mup/docs/uguide/mantup.html @@ -0,0 +1,47 @@ + + +Manually placed tuplet numbers + + +

+   <-- previous page + +     Table of Contents    next page --> +

+ +

+Manually placed tuplet numbers +

+

+Generally, Mup will place +tuplet +numbers for you. +However, you do need to print them yourself on +cross-staff beams. +And there may be cases where you choose +to use 'n' to turn off Mup's automatic printing of tuplet numbers, +in order to print them manually in a different place than Mup would. +Mup normally uses newcentury boldital font for tuplet numbers, in 11-point +size for regular notes and 9-point for cue notes. +So to make your manually placed tuplet numbers +look the same as automatic ones, you might use a +macro +something like this: +

+define TUPNUM(NUM) "\f(NX)\s(11)" +`NUM` @
+1: { 8c; d; e; } 3n; 2.us;         
+rom above 1 dist0: 1.34 TUPNUM(3);
+bar
+

+Or another approach would be something like this: +
+define TN(NUM,WHERE,D,N) newcentury boldital WHERE dist D: N `NUM`;@
+1: { 8c; d; e; } 3n; 2.us;         
+TN(3,above 1,0,1.34)
+bar
+

+

+

+   <-- previous page     Table of Contents    next page --> +

+