Package: texlive-binaries
Version: 2024.20240313.70630+ds-5
Severity: minor
Tags: patch
* What led up to the situation?
Checking for defects with
test-[g|n]roff -mandoc -t -K utf8 -rF0 -rHY=0 -ww -b -z < "man page"
[Use "groff -e ' $' <file>" to find trailing spaces.]
["test-groff" is a script in the repository for "groff"; is not shipped]
(local copy and "troff" slightly changed by me).
[The fate of "test-nroff" was decided in groff bug #55941.]
* What was the outcome of this action?
troff: backtrace: file '<stdin>':18
troff:<stdin>:18: warning: trailing space in the line
troff: backtrace: file '<stdin>':20
troff:<stdin>:20: warning: trailing space in the line
troff: backtrace: file '<stdin>':23
troff:<stdin>:23: warning: trailing space in the line
troff: backtrace: file '<stdin>':30
troff:<stdin>:30: warning: trailing space in the line
troff: backtrace: file '<stdin>':45
troff:<stdin>:45: warning: trailing space in the line
troff: backtrace: file '<stdin>':47
troff:<stdin>:47: warning: trailing space in the line
troff: backtrace: file '<stdin>':48
troff:<stdin>:48: warning: trailing space in the line
troff: backtrace: file '<stdin>':56
troff:<stdin>:56: warning: trailing space in the line
troff: backtrace: file '<stdin>':66
troff:<stdin>:66: warning: trailing space in the line
troff: backtrace: file '<stdin>':67
troff:<stdin>:67: warning: trailing space in the line
troff: backtrace: file '<stdin>':69
troff:<stdin>:69: warning: trailing space in the line
troff: backtrace: file '<stdin>':88
troff:<stdin>:88: warning: trailing space in the line
troff: backtrace: file '<stdin>':90
troff:<stdin>:90: warning: trailing space in the line
troff: backtrace: file '<stdin>':94
troff:<stdin>:94: warning: trailing space in the line
troff: backtrace: file '<stdin>':97
troff:<stdin>:97: warning: trailing space in the line
troff: backtrace: file '<stdin>':99
troff:<stdin>:99: warning: trailing space in the line
troff: backtrace: file '<stdin>':103
troff:<stdin>:103: warning: trailing space in the line
troff: backtrace: file '<stdin>':104
troff:<stdin>:104: warning: trailing space in the line
troff: backtrace: file '<stdin>':106
troff:<stdin>:106: warning: trailing space in the line
troff: backtrace: file '<stdin>':108
troff:<stdin>:108: warning: trailing space in the line
troff: backtrace: file '<stdin>':112
troff:<stdin>:112: warning: trailing space in the line
troff: backtrace: file '<stdin>':121
troff:<stdin>:121: warning: trailing space in the line
troff: backtrace: file '<stdin>':123
troff:<stdin>:123: warning: trailing space in the line
troff: backtrace: file '<stdin>':126
troff:<stdin>:126: warning: trailing space in the line
troff: backtrace: file '<stdin>':128
troff:<stdin>:128: warning: trailing space in the line
troff: backtrace: file '<stdin>':131
troff:<stdin>:131: warning: trailing space in the line
troff: backtrace: file '<stdin>':134
troff:<stdin>:134: warning: trailing space in the line
troff: backtrace: file '<stdin>':136
troff:<stdin>:136: warning: trailing space in the line
troff: backtrace: file '<stdin>':137
troff:<stdin>:137: warning: trailing space in the line
troff: backtrace: file '<stdin>':140
troff:<stdin>:140: warning: trailing space in the line
troff: backtrace: file '<stdin>':141
troff:<stdin>:141: warning: trailing space in the line
troff: backtrace: file '<stdin>':147
troff:<stdin>:147: warning: trailing space in the line
troff: backtrace: file '<stdin>':149
troff:<stdin>:149: warning: trailing space in the line
troff: backtrace: file '<stdin>':152
troff:<stdin>:152: warning: trailing space in the line
troff: backtrace: file '<stdin>':155
troff:<stdin>:155: warning: trailing space in the line
troff: backtrace: file '<stdin>':157
troff:<stdin>:157: warning: trailing space in the line
troff: backtrace: file '<stdin>':167
troff:<stdin>:167: warning: trailing space in the line
troff: backtrace: file '<stdin>':171
troff:<stdin>:171: warning: trailing space in the line
troff: backtrace: file '<stdin>':174
troff:<stdin>:174: warning: trailing space in the line
troff: backtrace: file '<stdin>':176
troff:<stdin>:176: warning: trailing space in the line
troff: backtrace: file '<stdin>':178
troff:<stdin>:178: warning: trailing space in the line
troff: backtrace: file '<stdin>':182
troff:<stdin>:182: warning: trailing space in the line
troff: backtrace: file '<stdin>':184
troff:<stdin>:184: warning: trailing space in the line
troff: backtrace: file '<stdin>':203
troff:<stdin>:203: warning: trailing space in the line
troff: backtrace: file '<stdin>':207
troff:<stdin>:207: warning: trailing space in the line
troff: backtrace: file '<stdin>':221
troff:<stdin>:221: warning: trailing space in the line
troff: backtrace: file '<stdin>':222
troff:<stdin>:222: warning: trailing space in the line
troff: backtrace: file '<stdin>':228
troff:<stdin>:228: warning: trailing space in the line
troff: backtrace: file '<stdin>':230
troff:<stdin>:230: warning: trailing space in the line
troff: backtrace: file '<stdin>':235
troff:<stdin>:235: warning: trailing space in the line
troff: backtrace: file '<stdin>':242
troff:<stdin>:242: warning: trailing space in the line
troff: backtrace: file '<stdin>':253
troff:<stdin>:253: warning: trailing space in the line
troff: backtrace: file '<stdin>':259
troff:<stdin>:259: warning: trailing space in the line
troff: backtrace: file '<stdin>':285
troff:<stdin>:285: warning: trailing space in the line
troff: backtrace: file '<stdin>':290
troff:<stdin>:290: warning: trailing space in the line
* What outcome did you expect instead?
No output (no warnings).
-.-
General remarks and further material, if a diff-file exist, are in the
attachments.
-- System Information:
Debian Release: trixie/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 6.11.10-amd64 (SMP w/2 CPU threads; PREEMPT)
Locale: LANG=is_IS.iso88591, LC_CTYPE=is_IS.iso88591 (charmap=ISO-8859-1),
LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: sysvinit (via /sbin/init)
Versions of packages texlive-binaries depends on:
ii libc6 2.40-3
ii libcairo2 1.18.2-2
ii libfontconfig1 2.15.0-1.1+b1
ii libfreetype6 2.13.3+dfsg-1
ii libgcc-s1 14.2.0-8
ii libgraphite2-3 1.3.14-2+b1
ii libharfbuzz0b 10.0.1-1
ii libicu72 72.1-5+b1
ii libkpathsea6 2024.20240313.70630+ds-5
ii libmpfi0 1.5.4+ds-4
ii libmpfr6 4.2.1-1+b2
ii libpaper1 1.1.29+b2
ii libpixman-1-0 0.44.0-3
ii libpng16-16t64 1.6.44-2
ii libpotrace0 1.16-2+b2
ii libptexenc1 2024.20240313.70630+ds-5
ii libstdc++6 14.2.0-8
ii libsynctex2 2024.20240313.70630+ds-5
ii libteckit0 2.5.12+ds1-1+b1
ii libtexlua53-5 2024.20240313.70630+ds-5
ii libx11-6 2:1.8.10-2
ii libxaw7 2:1.0.16-1
ii libxi6 2:1.8.2-1
ii libxmu6 2:1.1.3-3+b3
ii libxpm4 1:3.5.17-1+b2
ii libxt6t64 1:1.2.1-1.2+b1
ii libzzip-0-13t64 0.13.72+dfsg.1-1.2+b1
ii perl 5.40.0-8
ii t1utils 1.41-4
ii tex-common 6.18
ii zlib1g 1:1.3.dfsg+really1.3.1-1+b1
Versions of packages texlive-binaries recommends:
pn dvisvgm <none>
ii texlive-base 2024.20241115-1
Versions of packages texlive-binaries suggests:
pn hintview <none>
pn texlive-binaries-sse2 <none>
Versions of packages tex-common depends on:
ii ucf 3.0043+nmu1
Versions of packages tex-common suggests:
pn debhelper <none>
Versions of packages texlive-binaries is related to:
ii tex-common 6.18
ii texlive-base 2024.20241115-1
-- no debconf information
Input file is autosp.1
Any program (person), that produces man pages, should check the output
for defects by using (both groff and nroff)
[gn]roff -mandoc -t -ww -b -z -K utf8 <man page>
The same goes for man pages that are used as an input.
For a style guide use
mandoc -T lint
-.-
So any 'generator' should check its products with the above mentioned
'groff', 'mandoc', and additionally with 'nroff ...'.
This is just a simple quality control measure.
The 'generator' may have to be corrected to get a better man page,
the source file may, and any additional file may.
Common defects:
Input text line longer than 80 bytes.
Not removing trailing spaces (in in- and output).
The reason for these trailing spaces should be found and eliminated.
Not beginning each input sentence on a new line.
Lines should thus be shorter.
See man-pages(7), item 'semantic newline'.
-.-
The difference between the formatted output of the original and patched file
can be seen with:
nroff -mandoc <file1> > <out1>
nroff -mandoc <file2> > <out2>
diff -u <out1> <out2>
and for groff, using
"printf '%s\n%s\n' '.kern 0' '.ss 12 0' | groff -mandoc -Z - "
instead of 'nroff -mandoc'
Add the option '-t', if the file contains a table.
Read the output of 'diff -u' with 'less -R' or similar.
-.-.
If 'man' (man-db) is used to check the manual for warnings,
the following must be set:
The option "-warnings=w"
The environmental variable:
export MAN_KEEP_STDERR=yes (or any non-empty value)
or
(produce only warnings):
export MANROFFOPT="-ww -b -z"
export MAN_KEEP_STDERR=yes (or any non-empty value)
-.-.
Output from "mandoc -T lint autosp.1 ": (shortened list)
24 input text line longer than 80 bytes
74 whitespace at end of input line
-.-.
Output from "test-groff -mandoc -t -ww -b -z autosp.1 ": (shortened list)
55 trailing space in the line
-.-.
Output from "mandoc -T lint autosp.1 ":
mandoc: autosp.1:8:11: STYLE: whitespace at end of input line
mandoc: autosp.1:18:100: STYLE: input text line longer than 80 bytes: This
program makes i...
mandoc: autosp.1:18:100: STYLE: whitespace at end of input line
mandoc: autosp.1:20:53: STYLE: whitespace at end of input line
mandoc: autosp.1:21:87: STYLE: input text line longer than 80 bytes: determined
by the ac...
mandoc: autosp.1:23:57: STYLE: whitespace at end of input line
mandoc: autosp.1:25:88: STYLE: input text line longer than 80 bytes: concern
for note-spa...
mandoc: autosp.1:45:7: STYLE: whitespace at end of input line
mandoc: autosp.1:47:9: STYLE: whitespace at end of input line
mandoc: autosp.1:48:54: STYLE: whitespace at end of input line
mandoc: autosp.1:49:18: STYLE: whitespace at end of input line
mandoc: autosp.1:56:6: STYLE: whitespace at end of input line
mandoc: autosp.1:57:12: STYLE: whitespace at end of input line
mandoc: autosp.1:66:92: STYLE: input text line longer than 80 bytes: line
breaks and spac...
mandoc: autosp.1:66:92: STYLE: whitespace at end of input line
mandoc: autosp.1:67:59: STYLE: whitespace at end of input line
mandoc: autosp.1:69:13: STYLE: whitespace at end of input line
mandoc: autosp.1:88:7: STYLE: whitespace at end of input line
mandoc: autosp.1:89:8: STYLE: whitespace at end of input line
mandoc: autosp.1:90:54: STYLE: whitespace at end of input line
mandoc: autosp.1:94:7: STYLE: whitespace at end of input line
mandoc: autosp.1:95:9: STYLE: whitespace at end of input line
mandoc: autosp.1:97:16: STYLE: whitespace at end of input line
mandoc: autosp.1:98:11: STYLE: whitespace at end of input line
mandoc: autosp.1:99:57: STYLE: whitespace at end of input line
mandoc: autosp.1:100:8: STYLE: whitespace at end of input line
mandoc: autosp.1:103:3: STYLE: whitespace at end of input line
mandoc: autosp.1:104:22: STYLE: whitespace at end of input line
mandoc: autosp.1:106:87: STYLE: input text line longer than 80 bytes: Commands
of the form...
mandoc: autosp.1:106:87: STYLE: whitespace at end of input line
mandoc: autosp.1:108:14: STYLE: whitespace at end of input line
mandoc: autosp.1:112:55: STYLE: whitespace at end of input line
mandoc: autosp.1:121:142: STYLE: whitespace at end of input line
mandoc: autosp.1:122:10: STYLE: whitespace at end of input line
mandoc: autosp.1:123:101: STYLE: input text line longer than 80 bytes: staff.
These ensure ...
mandoc: autosp.1:123:101: STYLE: whitespace at end of input line
mandoc: autosp.1:126:29: STYLE: whitespace at end of input line
mandoc: autosp.1:128:54: STYLE: whitespace at end of input line
mandoc: autosp.1:129:94: STYLE: input text line longer than 80 bytes:
automatically insert...
mandoc: autosp.1:131:40: STYLE: whitespace at end of input line
mandoc: autosp.1:132:8: STYLE: whitespace at end of input line
mandoc: autosp.1:134:10: STYLE: whitespace at end of input line
mandoc: autosp.1:136:3: STYLE: whitespace at end of input line
mandoc: autosp.1:137:11: STYLE: whitespace at end of input line
mandoc: autosp.1:138:13: STYLE: whitespace at end of input line
mandoc: autosp.1:140:102: STYLE: input text line longer than 80 bytes: If the
automatic spa...
mandoc: autosp.1:140:102: STYLE: whitespace at end of input line
mandoc: autosp.1:141:53: STYLE: whitespace at end of input line
mandoc: autosp.1:147:47: STYLE: whitespace at end of input line
mandoc: autosp.1:149:86: STYLE: input text line longer than 80 bytes: From
version 2017-06...
mandoc: autosp.1:149:86: STYLE: whitespace at end of input line
mandoc: autosp.1:152:15: STYLE: whitespace at end of input line
mandoc: autosp.1:154:11: STYLE: whitespace at end of input line
mandoc: autosp.1:155:21: STYLE: whitespace at end of input line
mandoc: autosp.1:157:13: STYLE: whitespace at end of input line
mandoc: autosp.1:160:82: STYLE: input text line longer than 80 bytes: All other
convention...
mandoc: autosp.1:167:34: STYLE: whitespace at end of input line
mandoc: autosp.1:171:9: STYLE: whitespace at end of input line
mandoc: autosp.1:174:42: STYLE: whitespace at end of input line
mandoc: autosp.1:176:11: STYLE: whitespace at end of input line
mandoc: autosp.1:178:16: STYLE: whitespace at end of input line
mandoc: autosp.1:179:12: STYLE: whitespace at end of input line
mandoc: autosp.1:182:14: STYLE: whitespace at end of input line
mandoc: autosp.1:184:80: STYLE: whitespace at end of input line
mandoc: autosp.1:189:11: STYLE: whitespace at end of input line
mandoc: autosp.1:195:112: STYLE: input text line longer than 80 bytes: assumes
that & and |...
mandoc: autosp.1:198:87: STYLE: input text line longer than 80 bytes:
Appoggiaturas and gr...
mandoc: autosp.1:199:93: STYLE: input text line longer than 80 bytes: of
1.45\\elemskip is...
mandoc: autosp.1:202:11: STYLE: whitespace at end of input line
mandoc: autosp.1:203:9: STYLE: whitespace at end of input line
mandoc: autosp.1:204:14: STYLE: whitespace at end of input line
mandoc: autosp.1:207:4: STYLE: whitespace at end of input line
mandoc: autosp.1:208:13: STYLE: whitespace at end of input line
mandoc: autosp.1:210:94: STYLE: input text line longer than 80 bytes: using any
of the fol...
mandoc: autosp.1:220:11: STYLE: whitespace at end of input line
mandoc: autosp.1:221:44: STYLE: whitespace at end of input line
mandoc: autosp.1:222:21: STYLE: whitespace at end of input line
mandoc: autosp.1:224:94: STYLE: input text line longer than 80 bytes: So, for
example, a t...
mandoc: autosp.1:228:78: STYLE: whitespace at end of input line
mandoc: autosp.1:230:3: STYLE: whitespace at end of input line
mandoc: autosp.1:231:8: STYLE: whitespace at end of input line
mandoc: autosp.1:234:82: STYLE: input text line longer than 80 bytes: In some
polyrhythmic...
mandoc: autosp.1:235:76: STYLE: whitespace at end of input line
mandoc: autosp.1:236:86: STYLE: input text line longer than 80 bytes: the
normal output of...
mandoc: autosp.1:241:81: STYLE: input text line longer than 80 bytes: can deal
with simult...
mandoc: autosp.1:242:37: STYLE: whitespace at end of input line
mandoc: autosp.1:244:96: STYLE: input text line longer than 80 bytes: In some
baroque scor...
mandoc: autosp.1:246:87: STYLE: input text line longer than 80 bytes: the third
note of a ...
mandoc: autosp.1:253:30: STYLE: whitespace at end of input line
mandoc: autosp.1:259:58: STYLE: whitespace at end of input line
mandoc: autosp.1:272:94: STYLE: input text line longer than 80 bytes:
Generally, user-defi...
mandoc: autosp.1:284:86: STYLE: input text line longer than 80 bytes: may not
be effective...
mandoc: autosp.1:285:84: STYLE: input text line longer than 80 bytes: advisable
to use a s...
mandoc: autosp.1:285:84: STYLE: whitespace at end of input line
mandoc: autosp.1:290:103: STYLE: input text line longer than 80 bytes: See
files quod2.aspc...
mandoc: autosp.1:290:103: STYLE: whitespace at end of input line
mandoc: autosp.1:299:4: STYLE: whitespace at end of input line
mandoc: autosp.1:302:12: STYLE: whitespace at end of input line
-.-.
Remove space characters at the end of lines.
Use "git apply ... --whitespace=fix" to fix extra space issues, or use
global configuration "core.whitespace".
8:.B autosp
18:This program makes it easier to create MusiXTeX scores by converting
(non-standard) commands of the
20:note-spacing commands (\\notes \\Notes \\NOtes ...),
23:for an entire measure can be entered one part at a time,
30: \\anotes\\qa J\\qa K&\\ca l\\qa m\\ca n\\en
45:If the
47:argument
48:does not have an .aspc extension, input is taken from
49:.IR infile .aspc
56:If no
57:.I outfile
66:line breaks and spaces may precede note segments, allowing more flexible
source formatting;
67:the line breaks and spaces will be elided from the output.
69:For example,
88:If the
89:.B \-l
90:( \fB\-\-log\fP ) option is used, a very detailed log
94:If the
95:.B \-d
97:option is used,
98:.I dotted
99:beam notes of the form \\qb{\fIn\fP}{\fB.\fP\fIp\fP} are
100:.I not
103:by
104:a \\roff-like command
106:Commands of the form \\qlp{\fIp\fP}, \\qlpp{\fIp\fP}, ...,
\\qpb{\fIn\fP}{\fIp\fP} and
108:as indicated.
112:coded using the standard \\def\\atnextbar notation but
121:\\QQsk, \\HQsk \\TQsk and \\Qsk in the source generate "global" skips;
i.e., the effect of \\qqsk, \\hqsk, \\tqsk or \\qsk, respectively, in
122:.I every
123:staff. These ensure that staffs remain synchronized if additional spacing
is needed in any staff(s).
126:up to four successive commas
128:Global skips \\tqsk (or, for double-flats, \\qsk) are
131:If this automatic additional spacing is
132:.I not
134:replacing
136:by
137:any of the
138:.I explicit
140:If the automatic spacing is insufficient, the spacing may be increased by
adding sufficient commas or
141:using a conventional notes command instead of \\an.
147:form \\ha{*}, \\qa{.*}, \\qa{*}, \\ca{*}, etc.
149:From version 2017-06-14, the effects of \\TransformNotes calls are
implemented by the
152:enables use of
154:.B autosp
155:scores; musixlyr.tex
157:musixtnt.tex
167:commands themselves; for example,
171:\\NOtes;
174:\\ca, \\cu, \\cl, \\ds result in \\Notes;
176:and so on.
178:The spacing for
179:.IR beamed
182:\\notes, etc.
184:Collective coding of note sequences (including accidentals and dots) is
handled
189:.B autosp
202:.B autosp
203:supports
204:.I x-tuplets
207:and
208:.I triplets
220:.B autosp
221:assumes that an x-tuplet is to be played in
222:(\fIx\fP\-1)/\fIx\fP
228:measure of barsant2.aspc for an example of a non-standard x-tuplet: a
5-tuple
230:of
231:.I six
235:themselves are correctly spaced. In these cases, it is possible to suppress
242:total note durations are identical.
253:would be played as if notated
259:The following coding will align the beamed sixteenth note
285:advisable to use a separate staff for each voice, to avoid \\anotes when
necessary,
290:See files quod2.aspc, kinder2.aspc, geminiani.aspc and barsant2.aspc for
scores suitable for input to
299:.PP
302:.SH AUTHOR
-.-.
Change two HYPHEN-MINUSES (code 0x2D) to an em-dash (\(em),
if one is intended.
" \(em " creates a too big gap in the text (in "troff").
An en-dash is usually surrounded by a space,
while an em-dash is used without spaces.
"man" (1 byte characters in input) transforms an en-dash (\(en) to one
HYPHEN-MINUS,
and an em-dash to two HYPHEN-MINUSES without considering the space
around it.
If "--" are two single "-"
(begin of an option or end of options)
then use "\-\-".
autosp.1:96:( \fB--dotted\fP )
-.-.
Change -- in x--y to \(em (em-dash), or, if an
option, to \-\-
96:( \fB--dotted\fP )
-.-.
Use the correct macro for the font change of a single argument or
split the argument into two.
179:.IR beamed
-.-.
Use "\e" to print the escape character instead of "\\" (which gets
interpreted in copy mode).
19:form \\anotes ... \\en (or \\an ... \\en) into one or more conventional
20:note-spacing commands (\\notes \\Notes \\NOtes ...),
21:determined by the actual note values, with \\sk spacing commands inserted as
necessary.
30: \\anotes\\qa J\\qa K&\\ca l\\qa m\\ca n\\en
37: \\Notes\\qa J\\sk\\qa K\\sk&\\ca l\\qa m\\sk\\ca n\\en
62:if a \\documentclass declaration is encountered).
72: \\an
73: \\ibl0K0\\qb0K\\nbbl0\\qb0{.K}\\tbbbl0\\tbbl0\\tql0L&
74: \\ibbl1m{-2}\\qb1{.m}\\tbbbl1\\tbbl1\\qb1l\\tql1k\\en
80: \\notesp\\ibl0K0\\qb0K&\\ibbl1m{-2}\\qb1{.m}\\en
81: \\nnotes\\sk&\\tbbbl1\\tbbl1\\qb1l\\en
82: \\notesp\\nbbl0\\qb0{.K}&\\tql1k\\en
83: \\nnotes\\tbbbl0\\tbbl0\\tql0L&\\sk\\en
99:beam notes of the form \\qb{\fIn\fP}{\fB.\fP\fIp\fP} are
104:a \\roff-like command
105:or a spacing command such as \\qsk or \\hqsk.
106:Commands of the form \\qlp{\fIp\fP}, \\qlpp{\fIp\fP}, ...,
\\qpb{\fIn\fP}{\fIp\fP} and
112:coded using the standard \\def\\atnextbar notation but
113:the non-standard command \\Cpause (or \\Cp) in a note segment also
generates a
116:Spacing commands \\sk and \\bsk in the source are discarded,
117:but not "small" skips \\hsk, \\qsk, \\tqsk, \\hqsk or \\qqsk,
118:or the small "backward" skips \\hbsk, \\bqsk, \\btsk, or \\bhsk.
121:\\QQsk, \\HQsk \\TQsk and \\Qsk in the source generate "global" skips;
i.e., the effect of \\qqsk, \\hqsk, \\tqsk or \\qsk, respectively, in
127:to get the effects of \\QQsk, \\HQsk, \\TQsk or \\Qsk, respectively.
128:Global skips \\tqsk (or, for double-flats, \\qsk) are
139:accidental commands: \\sh, \\fl, \\na, \\smallsh, \\bigsh, etc.
141:using a conventional notes command instead of \\an.
147:form \\ha{*}, \\qa{.*}, \\qa{*}, \\ca{*}, etc.
149:From version 2017-06-14, the effects of \\TransformNotes calls are
implemented by the
158:implementation of \\TransformNotes.
170:\\qa, \\qu, \\ql, \\qp result in
174:\\ca, \\cu, \\cl, \\ds result in \\Notes;
181:multiplicity, so that \\ib... results in \\Notes, \\ibb... results in
195:assumes that & and | (rather than \\nextinstrument and \\nextstaff) are
used to separate instruments and staffs.
198:Appoggiaturas and grace notes are recognized by the use of \\tinynotesize;
note-spacing
199:of 1.45\\elemskip is used. If this isn't suitable and can't be corrected
with a small skip, a
205:introduced using \\xtuplet{\fIx\fP}
206:or \\xxtuplet{\fIx:y\fP}
210:using any of the following commands (regardless of any re-definition of
\\txt or \\tuplettxt):
213: \\triolet
214: \\uptrio
215: \\downtrio
216: \\uptuplet
217: \\downtuplet
227:be coded explicitly using a suitable \\vnotes command; see the first
234:In some polyrhythmic scores, the \\txt numeral may be displaced, even if
the notes
236:the normal output of \\txt by using the non-standard commands \\Triolet (no
arguments)
237:or \\Xtuplet{k}\\
238:and placing a numeral at the correct location using \\zcn (i.e.,
\\zcharnote).
250: \\ibl0L0\\qb0{.L}\\tqql0L
256: \\uptrio{b}10\\ql L\\hroff{\\cl L}
263: \\ibl0L0\\qb0{.L}\\hbsk\\tqql0L
269: \\ibbu0J0\\qb0{.J}\\hbsk\\nqqqu0J\\qb0{.J}\\hbsk\\tqqqu0J
275: \\def\\atnextbar{\\znotes ... \\en}
278:generate definitions that do take account of \\TransformNotes.
285:advisable to use a separate staff for each voice, to avoid \\anotes when
necessary,
-.-.
Move a full stop (period) and a comma outside of a quoted text, if it is
at the end of the quote and does not end a quoted sentence.
145:with or contain a "space," the note-value
-.-.
Wrong distance between sentences in the input file.
Separate the sentences and subordinate clauses; each begins on a new
line. See man-pages(7) ("Conventions for source file layout") and
"info groff" ("Input Conventions").
The best procedure is to always start a new sentence on a new line,
at least, if you are typing on a computer.
Remember coding: Only one command ("sentence") on each (logical) line.
E-mail: Easier to quote exactly the relevant lines.
Generally: Easier to edit the sentence.
Patches: Less unaffected text.
Search for two adjacent words is easier, when they belong to the same line,
and the same phrase.
The amount of space between sentences in the output can then be
controlled with the ".ss" request.
19:form \\anotes ... \\en (or \\an ... \\en) into one or more conventional
111:are merged into a multi-bar rest. Bar-centered rests can be
123:staff. These ensure that staffs remain synchronized if additional spacing
is needed in any staff(s).
151:pre-processor. This
181:multiplicity, so that \\ib... results in \\Notes, \\ibb... results in
199:of 1.45\\elemskip is used. If this isn't suitable and can't be corrected
with a small skip, a
235:themselves are correctly spaced. In these cases, it is possible to suppress
244:In some baroque scores, particularly by J.S. Bach, a beamed sixteenth note
is vertically aligned
284:may not be effective for music with more than one voice in a single staff.
It might be
-.-.
Split lines longer than 80 characters into two or more lines.
Appropriate break points are the end of a sentence and a subordinate
clause; after punctuation marks.
N.B.
The number of lines affected can be too large to be in a patch.
Line 18, length 100
This program makes it easier to create MusiXTeX scores by converting
(non-standard) commands of the
Line 21, length 87
determined by the actual note values, with \\sk spacing commands inserted as
necessary.
Line 25, length 88
concern for note-spacing changes within the part or spacing requirements of
other parts.
Line 66, length 92
line breaks and spaces may precede note segments, allowing more flexible source
formatting;
Line 106, length 87
Commands of the form \\qlp{\fIp\fP}, \\qlpp{\fIp\fP}, ...,
\\qpb{\fIn\fP}{\fIp\fP} and
Line 121, length 142
\\QQsk, \\HQsk \\TQsk and \\Qsk in the source generate "global" skips; i.e.,
the effect of \\qqsk, \\hqsk, \\tqsk or \\qsk, respectively, in
Line 123, length 101
staff. These ensure that staffs remain synchronized if additional spacing is
needed in any staff(s).
Line 129, length 94
automatically inserted before accidentals ('^', '_', '=', '<', '>') on
collective-coding notes
Line 140, length 102
If the automatic spacing is insufficient, the spacing may be increased by
adding sufficient commas or
Line 149, length 86
>From version 2017-06-14, the effects of \\TransformNotes calls are implemented
>by the
Line 160, length 82
All other conventional MusiXTeX commands are output exactly as given in the
input.
Line 195, length 112
assumes that & and | (rather than \\nextinstrument and \\nextstaff) are used to
separate instruments and staffs.
Line 198, length 87
Appoggiaturas and grace notes are recognized by the use of \\tinynotesize;
note-spacing
Line 199, length 93
of 1.45\\elemskip is used. If this isn't suitable and can't be corrected with a
small skip, a
Line 210, length 94
using any of the following commands (regardless of any re-definition of \\txt
or \\tuplettxt):
Line 224, length 94
So, for example, a triplet in eighths is assumed to be played in the time of
one quarter note.
Line 234, length 82
In some polyrhythmic scores, the \\txt numeral may be displaced, even if the
notes
Line 236, length 86
the normal output of \\txt by using the non-standard commands \\Triolet (no
arguments)
Line 241, length 81
can deal with simultaneous x-tuplets in multiple staffs provided the x values
and
Line 244, length 96
In some baroque scores, particularly by J.S. Bach, a beamed sixteenth note is
vertically aligned
Line 246, length 87
the third note of a triplet of eighth notes in another staff (implying that
they should
Line 272, length 94
Generally, user-defined macros are not processed or expanded; however,
definitions of the form
Line 284, length 86
may not be effective for music with more than one voice in a single staff. It
might be
Line 285, length 84
advisable to use a separate staff for each voice, to avoid \\anotes when
necessary,
Line 290, length 103
See files quod2.aspc, kinder2.aspc, geminiani.aspc and barsant2.aspc for scores
suitable for input to
-.-.
Put a parenthetical sentence, phrase on a separate line,
if not part of a code.
See man-pages(7), item "semantic newline".
autosp.1:18:This program makes it easier to create MusiXTeX scores by
converting (non-standard) commands of the
autosp.1:19:form \\anotes ... \\en (or \\an ... \\en) into one or more
conventional
autosp.1:20:note-spacing commands (\\notes \\Notes \\NOtes ...),
autosp.1:128:Global skips \\tqsk (or, for double-flats, \\qsk) are
autosp.1:129:automatically inserted before accidentals ('^', '_', '=', '<',
'>') on collective-coding notes
autosp.1:184:Collective coding of note sequences (including accidentals and
dots) is handled
autosp.1:195:assumes that & and | (rather than \\nextinstrument and
\\nextstaff) are used to separate instruments and staffs.
autosp.1:210:using any of the following commands (regardless of any
re-definition of \\txt or \\tuplettxt):
autosp.1:236:the normal output of \\txt by using the non-standard commands
\\Triolet (no arguments)
autosp.1:238:and placing a numeral at the correct location using \\zcn (i.e.,
\\zcharnote).
-.-.
Protect "^From " from forcing a mail software to use "quoted-printable"
encoding, by adding "\&" in front of it.
149:From version 2017-06-14, the effects of \\TransformNotes calls are
implemented by the
-.-.
Two or more space charaters between printable characters.
When the distance is between sentences,
start the beginning of the second one on a separate line
("semantic newline", see man-pages(7)).
2:.TH AUTOSP 1 2023-09-01 "" ""
9:.RB [ \-v\ |\ \-\-version\ |\ \-h\ |\ \-\-help ]
121:\\QQsk, \\HQsk \\TQsk and \\Qsk in the source generate "global" skips;
i.e., the effect of \\qqsk, \\hqsk, \\tqsk or \\qsk, respectively, in
-.-.
Output from "test-groff -mandoc -t -K utf8 -rF0 -rHY=0 -ww -b -z ":
troff: backtrace: file '<stdin>':18
troff:<stdin>:18: warning: trailing space in the line
troff: backtrace: file '<stdin>':20
troff:<stdin>:20: warning: trailing space in the line
troff: backtrace: file '<stdin>':23
troff:<stdin>:23: warning: trailing space in the line
troff: backtrace: file '<stdin>':30
troff:<stdin>:30: warning: trailing space in the line
troff: backtrace: file '<stdin>':45
troff:<stdin>:45: warning: trailing space in the line
troff: backtrace: file '<stdin>':47
troff:<stdin>:47: warning: trailing space in the line
troff: backtrace: file '<stdin>':48
troff:<stdin>:48: warning: trailing space in the line
troff: backtrace: file '<stdin>':56
troff:<stdin>:56: warning: trailing space in the line
troff: backtrace: file '<stdin>':66
troff:<stdin>:66: warning: trailing space in the line
troff: backtrace: file '<stdin>':67
troff:<stdin>:67: warning: trailing space in the line
troff: backtrace: file '<stdin>':69
troff:<stdin>:69: warning: trailing space in the line
troff: backtrace: file '<stdin>':88
troff:<stdin>:88: warning: trailing space in the line
troff: backtrace: file '<stdin>':90
troff:<stdin>:90: warning: trailing space in the line
troff: backtrace: file '<stdin>':94
troff:<stdin>:94: warning: trailing space in the line
troff: backtrace: file '<stdin>':97
troff:<stdin>:97: warning: trailing space in the line
troff: backtrace: file '<stdin>':99
troff:<stdin>:99: warning: trailing space in the line
troff: backtrace: file '<stdin>':103
troff:<stdin>:103: warning: trailing space in the line
troff: backtrace: file '<stdin>':104
troff:<stdin>:104: warning: trailing space in the line
troff: backtrace: file '<stdin>':106
troff:<stdin>:106: warning: trailing space in the line
troff: backtrace: file '<stdin>':108
troff:<stdin>:108: warning: trailing space in the line
troff: backtrace: file '<stdin>':112
troff:<stdin>:112: warning: trailing space in the line
troff: backtrace: file '<stdin>':121
troff:<stdin>:121: warning: trailing space in the line
troff: backtrace: file '<stdin>':123
troff:<stdin>:123: warning: trailing space in the line
troff: backtrace: file '<stdin>':126
troff:<stdin>:126: warning: trailing space in the line
troff: backtrace: file '<stdin>':128
troff:<stdin>:128: warning: trailing space in the line
troff: backtrace: file '<stdin>':131
troff:<stdin>:131: warning: trailing space in the line
troff: backtrace: file '<stdin>':134
troff:<stdin>:134: warning: trailing space in the line
troff: backtrace: file '<stdin>':136
troff:<stdin>:136: warning: trailing space in the line
troff: backtrace: file '<stdin>':137
troff:<stdin>:137: warning: trailing space in the line
troff: backtrace: file '<stdin>':140
troff:<stdin>:140: warning: trailing space in the line
troff: backtrace: file '<stdin>':141
troff:<stdin>:141: warning: trailing space in the line
troff: backtrace: file '<stdin>':147
troff:<stdin>:147: warning: trailing space in the line
troff: backtrace: file '<stdin>':149
troff:<stdin>:149: warning: trailing space in the line
troff: backtrace: file '<stdin>':152
troff:<stdin>:152: warning: trailing space in the line
troff: backtrace: file '<stdin>':155
troff:<stdin>:155: warning: trailing space in the line
troff: backtrace: file '<stdin>':157
troff:<stdin>:157: warning: trailing space in the line
troff: backtrace: file '<stdin>':167
troff:<stdin>:167: warning: trailing space in the line
troff: backtrace: file '<stdin>':171
troff:<stdin>:171: warning: trailing space in the line
troff: backtrace: file '<stdin>':174
troff:<stdin>:174: warning: trailing space in the line
troff: backtrace: file '<stdin>':176
troff:<stdin>:176: warning: trailing space in the line
troff: backtrace: file '<stdin>':178
troff:<stdin>:178: warning: trailing space in the line
troff: backtrace: file '<stdin>':182
troff:<stdin>:182: warning: trailing space in the line
troff: backtrace: file '<stdin>':184
troff:<stdin>:184: warning: trailing space in the line
troff: backtrace: file '<stdin>':203
troff:<stdin>:203: warning: trailing space in the line
troff: backtrace: file '<stdin>':207
troff:<stdin>:207: warning: trailing space in the line
troff: backtrace: file '<stdin>':221
troff:<stdin>:221: warning: trailing space in the line
troff: backtrace: file '<stdin>':222
troff:<stdin>:222: warning: trailing space in the line
troff: backtrace: file '<stdin>':228
troff:<stdin>:228: warning: trailing space in the line
troff: backtrace: file '<stdin>':230
troff:<stdin>:230: warning: trailing space in the line
troff: backtrace: file '<stdin>':235
troff:<stdin>:235: warning: trailing space in the line
troff: backtrace: file '<stdin>':242
troff:<stdin>:242: warning: trailing space in the line
troff: backtrace: file '<stdin>':253
troff:<stdin>:253: warning: trailing space in the line
troff: backtrace: file '<stdin>':259
troff:<stdin>:259: warning: trailing space in the line
troff: backtrace: file '<stdin>':285
troff:<stdin>:285: warning: trailing space in the line
troff: backtrace: file '<stdin>':290
troff:<stdin>:290: warning: trailing space in the line
--- autosp.1 2024-12-02 02:35:04.211249200 +0000
+++ autosp.1.new 2024-12-02 03:24:31.150815128 +0000
@@ -1,12 +1,12 @@
.\" This manpage is licensed under the GNU Public License
-.TH AUTOSP 1 2023-09-01 "" ""
+.TH AUTOSP 1 2023-09-01 "" ""
.SH NAME
autosp \- preprocessor to generate note-spacing commands for MusiXTeX scores
.SH SYNOPSIS
-.B autosp
-.RB [ \-v\ |\ \-\-version\ |\ \-h\ |\ \-\-help ]
+.B autosp
+.RB [ \-v\ |\ \-\-version\ |\ \-h\ |\ \-\-help ]
.B autosp
.RB [ \-d\ |\ \-\-dotted ]
@@ -15,289 +15,322 @@ autosp \- preprocessor to generate note-
.RI [ outfile [ \fR.tex\fP ]]
.SH DESCRIPTION
-This program makes it easier to create MusiXTeX scores by converting
(non-standard) commands of the
-form \\anotes ... \\en (or \\an ... \\en) into one or more conventional
-note-spacing commands (\\notes \\Notes \\NOtes ...),
-determined by the actual note values, with \\sk spacing commands inserted as
necessary.
+This program makes it easier to create MusiXTeX scores by
+converting
+(non-standard)
+commands of the form \eanotes ... \een
+(or \ean ... \een)
+into one or more conventional note-spacing commands
+(\enotes \eNotes \eNOtes ...),
+determined by the actual note values,
+with \esk spacing commands inserted as necessary.
The coding
-for an entire measure can be entered one part at a time,
-without
-concern for note-spacing changes within the part or spacing requirements of
other parts.
+for an entire measure can be entered one part at a time,
+without concern for note-spacing changes within the part
+or spacing requirements of other parts.
For example, if applied to
.nf
- \\anotes\\qa J\\qa K&\\ca l\\qa m\\ca n\\en
+ \eanotes\eqa J\eqa K&\eca l\eqa m\eca n\een
.fi
.B autosp
generates
.nf
- \\Notes\\qa J\\sk\\qa K\\sk&\\ca l\\qa m\\sk\\ca n\\en
+ \eNotes\eqa J\esk\eqa K\esk&\eca l\eqa m\esk\eca n\een
.fi
Typically,
an
-\\anotes command generates several conventional
+\eanotes command generates several conventional
note-spacing commands.
-If the
+If the
.I infile
-argument
-does not have an .aspc extension, input is taken from
-.IR infile .aspc
+argument does not have an .aspc extension,
+input is taken from
+.IR infile .aspc
if that file exists.
If the
.I outfile
-argument does not have a .tex extension, output is sent to
+argument does not have a .tex extension,
+output is sent to
.IR outfile .tex.
-If no
-.I outfile
-argument is provided, output will go to
+If no
+.I outfile
+argument is provided,
+output will go to
.IR infile .tex
(or to
.IR infile .ltx
-if a \\documentclass declaration is encountered).
+if a \edocumentclass declaration is encountered).
For
-\\anotes commands,
-line breaks and spaces may precede note segments, allowing more flexible
source formatting;
-the line breaks and spaces will be elided from the output.
+\eanotes commands,
+line breaks and spaces may precede note segments,
+allowing more flexible source formatting;
+the line breaks and spaces will be elided from the output.
-For example,
+For example,
.nf
- \\an
- \\ibl0K0\\qb0K\\nbbl0\\qb0{.K}\\tbbbl0\\tbbl0\\tql0L&
- \\ibbl1m{-2}\\qb1{.m}\\tbbbl1\\tbbl1\\qb1l\\tql1k\\en
+ \ean
+ \eibl0K0\eqb0K\enbbl0\eqb0{.K}\etbbbl0\etbbl0\etql0L&
+ \eibbl1m{-2}\eqb1{.m}\etbbbl1\etbbl1\eqb1l\etql1k\een
.fi
is acceptable and generates
.nf
- \\notesp\\ibl0K0\\qb0K&\\ibbl1m{-2}\\qb1{.m}\\en
- \\nnotes\\sk&\\tbbbl1\\tbbl1\\qb1l\\en
- \\notesp\\nbbl0\\qb0{.K}&\\tql1k\\en
- \\nnotes\\tbbbl0\\tbbl0\\tql0L&\\sk\\en
+ \enotesp\eibl0K0\eqb0K&\eibbl1m{-2}\eqb1{.m}\een
+ \ennotes\esk&\etbbbl1\etbbl1\eqb1l\een
+ \enotesp\enbbl0\eqb0{.K}&\etql1k\een
+ \ennotes\etbbbl0\etbbl0\etql0L&\esk\een
.fi
-If the
-.B \-l
-( \fB\-\-log\fP ) option is used, a very detailed log
+If the
+.B \-l
+( \fB\-\-log\fP ) option is used, a very detailed log
.IR infile .alog
is generated.
-If the
-.B \-d
-( \fB--dotted\fP )
-option is used,
-.I dotted
-beam notes of the form \\qb{\fIn\fP}{\fB.\fP\fIp\fP} are
-.I not
+If the
+.B \-d
+( \fB\-\-dotted\fP )
+option is used,
+.I dotted
+beam notes of the form \eqb{\fIn\fP}{\fB.\fP\fIp\fP} are
+.I not
given extra space;
it is assumed that the subsequent note will be shifted
-by
-a \\roff-like command
-or a spacing command such as \\qsk or \\hqsk.
-Commands of the form \\qlp{\fIp\fP}, \\qlpp{\fIp\fP}, ...,
\\qpb{\fIn\fP}{\fIp\fP} and
-\\qppb{\fIn\fP}{\fIp\fP} are always spaced
-as indicated.
-
-If there is a single staff, consecutive whole-bar rest bars
-are merged into a multi-bar rest. Bar-centered rests can be
-coded using the standard \\def\\atnextbar notation but
-the non-standard command \\Cpause (or \\Cp) in a note segment also generates a
-bar-centered rest.
-
-Spacing commands \\sk and \\bsk in the source are discarded,
-but not "small" skips \\hsk, \\qsk, \\tqsk, \\hqsk or \\qqsk,
-or the small "backward" skips \\hbsk, \\bqsk, \\btsk, or \\bhsk.
+by
+a \eroff-like command
+or a spacing command such as \eqsk or \ehqsk.
+Commands of the form \eqlp{\fIp\fP}, \eqlpp{\fIp\fP},
+\&..., \eqpb{\fIn\fP}{\fIp\fP}
+and \eqppb{\fIn\fP}{\fIp\fP} are always spaced as indicated.
+
+If there is a single staff,
+consecutive whole-bar rest bars are merged into a multi-bar rest.
+Bar-centered rests can be coded using the standard \edef\eatnextbar notation
+but the non-standard command \eCpause
+(or \eCp)
+in a note segment also generates a bar-centered rest.
+
+Spacing commands \esk and \ebsk in the source are discarded,
+but not "small" skips \ehsk, \eqsk, \etqsk, \ehqsk or \eqqsk,
+or the small "backward" skips \ehbsk, \ebqsk, \ebtsk, or \ebhsk.
Moreover,
non-standard commands
-\\QQsk, \\HQsk \\TQsk and \\Qsk in the source generate "global" skips; i.e.,
the effect of \\qqsk, \\hqsk, \\tqsk or \\qsk, respectively, in
-.I every
-staff. These ensure that staffs remain synchronized if additional spacing is
needed in any staff(s).
+\eQQsk, \eHQsk \eTQsk and \eQsk in the source generate "global" skips;
+i.e., the effect of \eqqsk, \ehqsk, \etqsk or \eqsk, respectively, in
+.I every
+staff.
+These ensure that staffs remain synchronized
+if additional spacing is needed in any staff(s).
Global skips may also be obtained within collective-coding sequences by using
-up to four successive commas
-to get the effects of \\QQsk, \\HQsk, \\TQsk or \\Qsk, respectively.
-Global skips \\tqsk (or, for double-flats, \\qsk) are
-automatically inserted before accidentals ('^', '_', '=', '<', '>') on
collective-coding notes
+up to four successive commas
+to get the effects of \eQQsk, \eHQsk, \eTQsk or \eQsk, respectively.
+Global skips \etqsk
+(or, for double-flats, \eqsk)
+are automatically inserted before accidentals
+('^', '_', '=', '<', '>')
+on collective-coding notes
(except when the preceding note is "virtual"; i.e., a skip).
-If this automatic additional spacing is
-.I not
+If this automatic additional spacing is
+.I not
wanted in some context, it may be avoided by
-replacing
+replacing
the accidental in the collective-coding sequence
-by
-any of the
-.I explicit
-accidental commands: \\sh, \\fl, \\na, \\smallsh, \\bigsh, etc.
-If the automatic spacing is insufficient, the spacing may be increased by
adding sufficient commas or
-using a conventional notes command instead of \\an.
-
-
-A note segment can be completely empty, but if a note segment should start
-with or contain a "space," the note-value
-of that space must be made explicit with a command of the
-form \\ha{*}, \\qa{.*}, \\qa{*}, \\ca{*}, etc.
-
-From version 2017-06-14, the effects of \\TransformNotes calls are implemented
by the
-.B autosp
-pre-processor. This
-enables use of
-musixlyr in
-.B autosp
-scores; musixlyr.tex
-is incompatible with the
-musixtnt.tex
-implementation of \\TransformNotes.
+by
+any of the
+.I explicit
+accidental commands: \esh, \efl, \ena, \esmallsh, \ebigsh, etc.
+If the automatic spacing is insufficient,
+the spacing may be increased by adding sufficient commas or
+using a conventional notes command instead of \ean.
+
+
+A note segment can be completely empty,
+but if a note segment should start with
+or contain a "space",
+the note-value of that space must be made explicit with a command of the
+form \eha{*}, \eqa{.*}, \eqa{*}, \eca{*}, etc.
+
+\&From version 2017-06-14,
+the effects of \eTransformNotes calls are implemented by the
+.B autosp
+pre-processor.
+This enables use of musixlyr in
+.B autosp
+scores;
+musixlyr.tex is incompatible with the musixtnt.tex implementation of
+\eTransformNotes.
-All other conventional MusiXTeX commands are output exactly as given in the
input.
+All other conventional MusiXTeX commands are output exactly
+as given in the input.
.SH OPERATION
.B autosp
determines the spacing for ordinary notes from the note
-commands themselves; for example,
+commands themselves; for example,
.TP 3
+
-\\qa, \\qu, \\ql, \\qp result in
-\\NOtes;
+\eqa, \equ, \eql, \eqp result in
+\eNOtes;
.TP 3
+
-\\ca, \\cu, \\cl, \\ds result in \\Notes;
+\eca, \ecu, \ecl, \eds result in \eNotes;
.PP
-and so on.
-
-The spacing for
-.IR beamed
+and so on.
+
+The spacing for
+.I beamed
notes is determined by the beam
-multiplicity, so that \\ib... results in \\Notes, \\ibb... results in
-\\notes, etc.
+multiplicity, so that \eib... results in \eNotes, \eibb... results in
+\enotes, etc.
-Collective coding of note sequences (including accidentals and dots) is
handled
-by expanding the sequence
-into a sequence of individual note commands.
+Collective coding of note sequences
+(including accidentals and dots)
+is handled by expanding the sequence into a sequence of individual note
+commands.
-.B autosp
+.B autosp
scales notes by the relevant instrument-size value.
-
+
.SH LIMITATIONS
.B autosp
-assumes that & and | (rather than \\nextinstrument and \\nextstaff) are used
to separate instruments and staffs.
+assumes that & and |
+(rather than \enextinstrument and \enextstaff)
+are used to separate instruments and staffs.
+
+Appoggiaturas and grace notes are recognized by the use of \etinynotesize;
+note-spacing of 1.45\eelemskip is used.
+If this isn't suitable
+and can't be corrected with a small skip,
+a \evnotes command with any desired spacing can be used.
-Appoggiaturas and grace notes are recognized by the use of \\tinynotesize;
note-spacing
-of 1.45\\elemskip is used. If this isn't suitable and can't be corrected with
a small skip, a
-\\vnotes command with any desired spacing can be used.
-
-.B autosp
-supports
-.I x-tuplets
-introduced using \\xtuplet{\fIx\fP}
-or \\xxtuplet{\fIx:y\fP}
-and
-.I triplets
+.B autosp
+supports
+.I x-tuplets
+introduced using \extuplet{\fIx\fP}
+or \exxtuplet{\fIx:y\fP}
+and
+.I triplets
introduced
-using any of the following commands (regardless of any re-definition of \\txt
or \\tuplettxt):
+using any of the following commands
+(regardless of any re-definition of \etxt or \etuplettxt):
.nf
- \\triolet
- \\uptrio
- \\downtrio
- \\uptuplet
- \\downtuplet
+ \etriolet
+ \euptrio
+ \edowntrio
+ \euptuplet
+ \edowntuplet
.fi
-.B autosp
-assumes that an x-tuplet is to be played in
-(\fIx\fP\-1)/\fIx\fP
+.B autosp
+assumes that an x-tuplet is to be played in
+(\fIx\fP\-1)/\fIx\fP
of the apparent x-tuplet duration.
-So, for example, a triplet in eighths is assumed to be played in the time of
one quarter note.
-If this assumption
-isn't valid, the x-tuplet must
-be coded explicitly using a suitable \\vnotes command; see the first
-measure of barsant2.aspc for an example of a non-standard x-tuplet: a 5-tuple
-of 64th notes with an intended duration
-of
-.I six
+So, for example,
+a triplet in eighths is assumed to be played in the time of one quarter note.
+If this assumption isn't valid,
+the x-tuplet must be coded explicitly using a suitable \evnotes command;
+see the first measure of barsant2.aspc for an example of a non-standard
+x-tuplet:
+a 5-tuple of 64th notes with an intended duration of
+.I six
64ths.
-In some polyrhythmic scores, the \\txt numeral may be displaced, even if the
notes
-themselves are correctly spaced. In these cases, it is possible to suppress
-the normal output of \\txt by using the non-standard commands \\Triolet (no
arguments)
-or \\Xtuplet{k}\\
-and placing a numeral at the correct location using \\zcn (i.e., \\zcharnote).
+In some polyrhythmic scores,
+the \etxt numeral may be displaced,
+even if the notes themselves are correctly spaced.
+In these cases,
+it is possible to suppress the normal output of \etxt
+by using the non-standard commands \eTriolet
+(no arguments)
+or \eXtuplet{k}\e
+and placing a numeral at the correct location using \ezcn
+(i.e., \ezcharnote).
.B autosp
-can deal with simultaneous x-tuplets in multiple staffs provided the x values
and
-total note durations are identical.
-
-In some baroque scores, particularly by J.S. Bach, a beamed sixteenth note is
vertically aligned
-with
-the third note of a triplet of eighth notes in another staff (implying that
they should
-be sounded simultaneously); e.g.,
+can deal with simultaneous x-tuplets in multiple staffs
+provided the x values and total note durations are identical.
+
+In some baroque scores,
+particularly by J.S.\& Bach,
+a beamed sixteenth note is vertically aligned with
+the third note of a triplet of eighth notes in another staff
+(implying that they should be sounded simultaneously);
+e.g.,
.nf
- \\ibl0L0\\qb0{.L}\\tqql0L
+ \eibl0L0\eqb0{.L}\etqql0L
.fi
-would be played as if notated
+would be played as if notated
.nf
- \\uptrio{b}10\\ql L\\hroff{\\cl L}
+ \euptrio{b}10\eql L\ehroff{\ecl L}
.fi
-The following coding will align the beamed sixteenth note
+The following coding will align the beamed sixteenth note
with the third note of a triplet in another staff:
.nf
- \\ibl0L0\\qb0{.L}\\hbsk\\tqql0L
+ \eibl0L0\eqb0{.L}\ehbsk\etqql0L
.fi
and, similarly, for triplets of sixteenth notes:
.nf
- \\ibbu0J0\\qb0{.J}\\hbsk\\nqqqu0J\\qb0{.J}\\hbsk\\tqqqu0J
+ \eibbu0J0\eqb0{.J}\ehbsk\enqqqu0J\eqb0{.J}\ehbsk\etqqqu0J
.fi
-Generally, user-defined macros are not processed or expanded; however,
definitions of the form
+Generally, user-defined macros are not processed or expanded;
+however, definitions of the form
.nf
- \\def\\atnextbar{\\znotes ... \\en}
+ \edef\eatnextbar{\eznotes ... \een}
.fi
-generate definitions that do take account of \\TransformNotes.
+generate definitions that do take account of \eTransformNotes.
All staffs are assumed to have the same meter; see kinder2.aspc for
an example of how to work around this.
.B autosp
-may not be effective for music with more than one voice in a single staff. It
might be
-advisable to use a separate staff for each voice, to avoid \\anotes when
necessary,
-or to omit certain voices
-initially and add them into the resulting TeX file.
+may not be effective for music with more than one voice in a single staff.
+It might be advisable to use a separate staff for each voice,
+to avoid \eanotes when necessary,
+or to omit certain voices initially
+and add them into the resulting TeX file.
.SH EXAMPLES
-See files quod2.aspc, kinder2.aspc, geminiani.aspc and barsant2.aspc for
scores suitable for input to
+See files quod2.aspc, kinder2.aspc, geminiani.aspc
+and barsant2.aspc for scores suitable for input to
.BR autosp .
The program
.B tex2aspc
can be used to convert "legacy" MusiXTeX scores to .aspc format.
.SH SEE ALSO
-.BR msxlint (1)
-.BR tex2aspc (1)
-.PP
+.BR msxlint (1),
+.BR tex2aspc (1).
+.PP
musixdoc.pdf
-.SH AUTHOR
+.SH AUTHOR
This program and manual page were written by Bob Tennent <r...@cs.queensu.ca>.
