[[email protected]: autosp.1: Some remarks and a patch with editorial changes for this man page]

Bjarni Ingi Gislason <[email protected]> Wed, 3 Jun 2026 02:03:46 +0000
Newsgroups gmane.linux.debian.devel.tetex
Message-ID <[email protected]>
  Additional remarks.

  Mails from me to "[email protected]" are no longer acknowledged.  A
Debian maintainer told me, that he would contact the mail administrator
about me not wanting to send bugs upstream.


----- Forwarded message from Bjarni Ingi Gislason <[email protected]> -----

Date: Wed, 3 Jun 2026 01:16:49 +0000
From: Bjarni Ingi Gislason <[email protected]>
To: Debian Bug Tracking System <[email protected]>
Subject: autosp.1: Some remarks and a patch with editorial changes for this man page
X-Mailer: reportbug 13.2.0

Package: texlive-binaries
Version: 2026.20260303.78225+ds-4
Severity: minor
Tags: patch upstream

Dear Maintainer,

>From "/usr/share/doc/debian/bug-reporting.txt.gz":

  Don't file bugs upstream

   If you file a bug in Debian, don't send a copy to the upstream software
   maintainers yourself, as it is possible that the bug exists only in
   Debian. If necessary, the maintainer of the package will forward the
   bug upstream.

-.-

  For forwarding bug reports to upstream see:

https://www.debian.org/Bugs/Developer#forward

-.-

  "Handling bug reports" in
http://people.debian.org/~enrico/dcg/ch03s02.html

-.-

  I do not send reports upstream if I have to get an account there.
The Debian maintainers have one already.

  If I get a negative (or no) response from upstream, I send henceforth
bugs to Debian.

-.-

   * What led up to the situation?

     Checking for defects with a new version

test-[g|n]roff -mandoc -t -K utf8 -rF0 -rHY=0 -rCHECKSTYLE=0 -ww -z < "man page"

  [Use 

grep -n -e ' $' -e '\\~$' -e ' \\f.$' -e ' \\"' <file>

  to find (most) 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?

Output from "test-nroff  -mandoc -t -K utf8 -rF0 -rHY=0 -rCHECKSTYLE=0 -ww -z ":

troff:<stdin>:18: warning: trailing whitespace [-w trail]
troff:<stdin>:20: warning: trailing whitespace [-w trail]
troff:<stdin>:23: warning: trailing whitespace [-w trail]
troff:<stdin>:30: warning: trailing whitespace [-w trail]
troff:<stdin>:45: warning: trailing whitespace [-w trail]
troff:<stdin>:47: warning: trailing whitespace [-w trail]
troff:<stdin>:48: warning: trailing whitespace [-w trail]
troff:<stdin>:56: warning: trailing whitespace [-w trail]
troff:<stdin>:66: warning: trailing whitespace [-w trail]
troff:<stdin>:67: warning: trailing whitespace [-w trail]
troff:<stdin>:69: warning: trailing whitespace [-w trail]
troff:<stdin>:88: warning: trailing whitespace [-w trail]
troff:<stdin>:90: warning: trailing whitespace [-w trail]
troff:<stdin>:94: warning: trailing whitespace [-w trail]
troff:<stdin>:97: warning: trailing whitespace [-w trail]
troff:<stdin>:99: warning: trailing whitespace [-w trail]
troff:<stdin>:103: warning: trailing whitespace [-w trail]
troff:<stdin>:104: warning: trailing whitespace [-w trail]
troff:<stdin>:106: warning: trailing whitespace [-w trail]
troff:<stdin>:108: warning: trailing whitespace [-w trail]
troff:<stdin>:112: warning: trailing whitespace [-w trail]
troff:<stdin>:121: warning: trailing whitespace [-w trail]
troff:<stdin>:123: warning: trailing whitespace [-w trail]
troff:<stdin>:126: warning: trailing whitespace [-w trail]
troff:<stdin>:128: warning: trailing whitespace [-w trail]
troff:<stdin>:131: warning: trailing whitespace [-w trail]
troff:<stdin>:134: warning: trailing whitespace [-w trail]
troff:<stdin>:136: warning: trailing whitespace [-w trail]
troff:<stdin>:137: warning: trailing whitespace [-w trail]
troff:<stdin>:140: warning: trailing whitespace [-w trail]
troff:<stdin>:141: warning: trailing whitespace [-w trail]
troff:<stdin>:147: warning: trailing whitespace [-w trail]
troff:<stdin>:149: warning: trailing whitespace [-w trail]
troff:<stdin>:152: warning: trailing whitespace [-w trail]
troff:<stdin>:155: warning: trailing whitespace [-w trail]
troff:<stdin>:157: warning: trailing whitespace [-w trail]
troff:<stdin>:167: warning: trailing whitespace [-w trail]
troff:<stdin>:171: warning: trailing whitespace [-w trail]
troff:<stdin>:174: warning: trailing whitespace [-w trail]
troff:<stdin>:176: warning: trailing whitespace [-w trail]
troff:<stdin>:178: warning: trailing whitespace [-w trail]
troff:<stdin>:182: warning: trailing whitespace [-w trail]
troff:<stdin>:184: warning: trailing whitespace [-w trail]
troff:<stdin>:203: warning: trailing whitespace [-w trail]
troff:<stdin>:207: warning: trailing whitespace [-w trail]
troff:<stdin>:221: warning: trailing whitespace [-w trail]
troff:<stdin>:222: warning: trailing whitespace [-w trail]
troff:<stdin>:228: warning: trailing whitespace [-w trail]
troff:<stdin>:230: warning: trailing whitespace [-w trail]
troff:<stdin>:235: warning: trailing whitespace [-w trail]
troff:<stdin>:242: warning: trailing whitespace [-w trail]
troff:<stdin>:253: warning: trailing whitespace [-w trail]
troff:<stdin>:259: warning: trailing whitespace [-w trail]
troff:<stdin>:285: warning: trailing whitespace [-w trail]
troff:<stdin>:290: warning: trailing whitespace [-w trail]


   * 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: forky/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 7.0.9+deb14-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.42-16
ii  libcairo2            1.18.4-3+b1
ii  libfontconfig1       2.17.1-5
ii  libfreetype6         2.14.3+dfsg-1
ii  libgcc-s1            16.1.0-1
ii  libgraphite2-3       1.3.14-13
ii  libharfbuzz-subset0  12.3.2-2+b2
ii  libharfbuzz0b        12.3.2-2+b2
ii  libicu78             78.3-2
ii  libkpathsea6         2026.20260303.78225+ds-4
ii  libmpfi0             1.5.4+ds-5
ii  libmpfr6             4.2.2-3
ii  libpaper2            2.2.5-0.4
ii  libpixman-1-0        0.46.4-1+b2
ii  libpng16-16t64       1.6.58-1
ii  libpotrace0          1.16-2+b3
ii  libptexenc1          2026.20260303.78225+ds-4
ii  libstdc++6           16.1.0-1
ii  libsynctex2          2026.20260303.78225+ds-4
ii  libteckit0           2.5.13+ds-1+b1
ii  libtexlua53-5        2026.20260303.78225+ds-4
ii  libx11-6             2:1.8.13-1
ii  libxaw7              2:1.0.16-1+b2
ii  libxi6               2:1.8.2-2+b1
ii  libxmu6              2:1.1.3-4+b1
ii  libxpm4              1:3.5.19-1
ii  libxt6t64            1:1.2.1-1.3+b2
ii  libzzip-0-13t64      0.13.78+dfsg.1-0.2+b1
ii  perl                 5.40.1-7+b1
ii  t1utils              1.41-4
ii  tex-common           6.20
ii  zlib1g               1:1.3.dfsg+really1.3.2-3

Versions of packages texlive-binaries recommends:
pn  dvisvgm       <none>
ii  texlive-base  2026.20260328-4

Versions of packages texlive-binaries suggests:
pn  hintview               <none>
pn  texlive-binaries-sse2  <none>

Versions of packages tex-common depends on:
ii  bzip2  1.0.8-6+b2
ii  ucf    3.0053

Versions of packages tex-common suggests:
pn  debhelper  <none>

Versions of packages texlive-binaries is related to:
ii  tex-common    6.20
ii  texlive-base  2026.20260328-4

-- no debconf information

Input file is autosp.1

Output from "mandoc -T lint  autosp.1": (shortened list)

     23 STYLE: input text line longer than 80 bytes
      1 STYLE: input text line longer than 80 bytes:
     74 STYLE: whitespace at end of input line

Find trailing whitespace with:
grep -n -e ' $' -e ' \\f.$' -e ' \\"' <man page>

-.-.

Output from
test-nroff -mandoc -t -Kutf8 -ww -z autosp.1: (shortened list)

     55 trailing whitespace [-w trail]

Find trailing whitespace with:
grep -n -e ' $' -e ' \\f.$' -e ' \\"' <man page>

-.-.

Remove space characters (whitespace) at the end of lines.
Use "git apply ... --whitespace=fix" to fix extra space issues, or use
global configuration "core.whitespace".

See more information in the attachment "trailing whitespace".

Number of lines affected is

77

-.-.

Reduce space between words.

autosp.1:2:.TH AUTOSP 1 2023-11-26  "" ""
autosp.1:9:.RB  [ \-v\ |\ \-\-version\ |\ \-h\ |\ \-\-help ]
autosp.1:121:\\QQsk, \\HQsk \\TQsk and \\Qsk in the source generate "global" skips; i.e., the effect of \\qqsk, \\hqsk, \\tqsk or \\qsk, respectively,  in 

-.-.

Test nr. 15:

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, 

-.-.

Wrong distance (not two spaces, not a new line character (\n)) 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.

Mark a final abbreviation point as such by suffixing it with "\&".

Some sentences (etc.) do not begin on a new line.

Split (sometimes) lines after a punctuation mark; before a conjunction.

  Lines with only one (or two) space(s) between sentences could be split,
so latter sentences begin on a new line.

Use

#!/usr/bin/sh

sed -e '/^\./n' \
-e 's/\([[:alpha:]]\)\.  */\1.\n/g' $1

to split lines after a sentence period.
Check result with the difference between the formatted outputs.
See also the attachment "general.bugs"

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
275:    \\def\\atnextbar{\\znotes ... \\en}
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 (fill completely
an A4 sized page line on a terminal)
into two or more lines.
Appropriate break points are the end of a sentence and a subordinate
clause; after punctuation marks.

[List of affected lines removed.]

Longest line is number 121 with 142 characters
\\QQsk, \\HQsk \\TQsk and \\Qsk in the source generate "global" skips; i.e., the effect of \\qqsk, \\hqsk, \\tqsk or \\qsk, respectively,  in 

-.-.

Put a parenthetical sentence, phrase on a separate line,
if not part of a code.
See man-pages(7), item "semantic newline".

[List of affected lines removed.]

-.-.

Test nr. 66:

"[" and "]", showing optional arguments to options, should be typeset in
roman.

9:.RB  [ \-v\ |\ \-\-version\ |\ \-h\ |\ \-\-help ]
14:.IR infile [\fR.aspc\fP]
15:.RI [ outfile [ \fR.tex\fP ]]

-.-.

Protect "^{Ff}rom " 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 

-.-.

Only one space character is after a possible end of sentence
(after a punctuation, that can end a sentence).

[List of affected lines removed.]


autosp.1:19:form \\anotes ... \\en (or \\an ... \\en) into one or more conventional
autosp.1:111:are merged into a multi-bar rest. Bar-centered rests can be
autosp.1:123:staff. These ensure that staffs remain synchronized if additional spacing is needed in any staff(s). 
autosp.1:151:pre-processor. This
autosp.1:181:multiplicity, so that \\ib... results in \\Notes, \\ibb... results in
autosp.1:199:of 1.45\\elemskip is used. If this isn't suitable and can't be corrected with a small skip, a
autosp.1:235:themselves are correctly spaced. In these cases, it is possible to suppress 
autosp.1:244:In some baroque scores, particularly by J.S. Bach, a beamed sixteenth note is vertically aligned
autosp.1:275:    \\def\\atnextbar{\\znotes ... \\en}
autosp.1:284:may not be effective for music with more than one voice in a single staff. It might be

-.-.

Remove a space character after a macro call.

8:.B autosp 
49:.IR infile .aspc 
57:.I outfile 
89:.B \-l 
95:.B \-d  
98:.I dotted 
100:.I not 
122:.I every 
132:.I not 
138:.I explicit 
154:.B autosp 
179:.IR beamed 
189:.B autosp 
202:.B autosp 
204:.I x-tuplets 
208:.I triplets 
220:.B autosp 
231:.I six 
299:.PP 
302:.SH AUTHOR 

-.-.

Add "\&" after an ellipsis, when it does not end a sentence.

19:form \\anotes ... \\en (or \\an ... \\en) into one or more conventional
181:multiplicity, so that \\ib... results in \\Notes, \\ibb... results in
275:    \\def\\atnextbar{\\znotes ... \\en}

-.-.

Output from "test-groff  -mandoc -t -K utf8 -rF0 -rHY=0 -rCHECKSTYLE=0 -ww -z ":

troff:<stdin>:18: warning: trailing whitespace [-w trail]
troff:<stdin>:20: warning: trailing whitespace [-w trail]
troff:<stdin>:23: warning: trailing whitespace [-w trail]
troff:<stdin>:30: warning: trailing whitespace [-w trail]
troff:<stdin>:45: warning: trailing whitespace [-w trail]
troff:<stdin>:47: warning: trailing whitespace [-w trail]
troff:<stdin>:48: warning: trailing whitespace [-w trail]
troff:<stdin>:56: warning: trailing whitespace [-w trail]
troff:<stdin>:66: warning: trailing whitespace [-w trail]
troff:<stdin>:67: warning: trailing whitespace [-w trail]
troff:<stdin>:69: warning: trailing whitespace [-w trail]
troff:<stdin>:88: warning: trailing whitespace [-w trail]
troff:<stdin>:90: warning: trailing whitespace [-w trail]
troff:<stdin>:94: warning: trailing whitespace [-w trail]
troff:<stdin>:97: warning: trailing whitespace [-w trail]
troff:<stdin>:99: warning: trailing whitespace [-w trail]
troff:<stdin>:103: warning: trailing whitespace [-w trail]
troff:<stdin>:104: warning: trailing whitespace [-w trail]
troff:<stdin>:106: warning: trailing whitespace [-w trail]
troff:<stdin>:108: warning: trailing whitespace [-w trail]
troff:<stdin>:112: warning: trailing whitespace [-w trail]
troff:<stdin>:121: warning: trailing whitespace [-w trail]
troff:<stdin>:123: warning: trailing whitespace [-w trail]
troff:<stdin>:126: warning: trailing whitespace [-w trail]
troff:<stdin>:128: warning: trailing whitespace [-w trail]
troff:<stdin>:131: warning: trailing whitespace [-w trail]
troff:<stdin>:134: warning: trailing whitespace [-w trail]
troff:<stdin>:136: warning: trailing whitespace [-w trail]
troff:<stdin>:137: warning: trailing whitespace [-w trail]
troff:<stdin>:140: warning: trailing whitespace [-w trail]
troff:<stdin>:141: warning: trailing whitespace [-w trail]
troff:<stdin>:147: warning: trailing whitespace [-w trail]
troff:<stdin>:149: warning: trailing whitespace [-w trail]
troff:<stdin>:152: warning: trailing whitespace [-w trail]
troff:<stdin>:155: warning: trailing whitespace [-w trail]
troff:<stdin>:157: warning: trailing whitespace [-w trail]
troff:<stdin>:167: warning: trailing whitespace [-w trail]
troff:<stdin>:171: warning: trailing whitespace [-w trail]
troff:<stdin>:174: warning: trailing whitespace [-w trail]
troff:<stdin>:176: warning: trailing whitespace [-w trail]
troff:<stdin>:178: warning: trailing whitespace [-w trail]
troff:<stdin>:182: warning: trailing whitespace [-w trail]
troff:<stdin>:184: warning: trailing whitespace [-w trail]
troff:<stdin>:203: warning: trailing whitespace [-w trail]
troff:<stdin>:207: warning: trailing whitespace [-w trail]
troff:<stdin>:221: warning: trailing whitespace [-w trail]
troff:<stdin>:222: warning: trailing whitespace [-w trail]
troff:<stdin>:228: warning: trailing whitespace [-w trail]
troff:<stdin>:230: warning: trailing whitespace [-w trail]
troff:<stdin>:235: warning: trailing whitespace [-w trail]
troff:<stdin>:242: warning: trailing whitespace [-w trail]
troff:<stdin>:253: warning: trailing whitespace [-w trail]
troff:<stdin>:259: warning: trailing whitespace [-w trail]
troff:<stdin>:285: warning: trailing whitespace [-w trail]
troff:<stdin>:290: warning: trailing whitespace [-w trail]

-.-

Additionally:

Abbreviation: J.S. Bach -> J.S.\& Bach

-.-

Generally:

Split (sometimes) lines after a punctuation mark; before a conjunction.

-.-

Tables:

  Use the preprocessor 'tbl' to make tables.

  Put data, that are wider than the header in the (centered) last column,
in a "T{...\nT}" block(, when the table gets wider than the output line).

  Table headings, that are wider than any data in the corresponding
column, do not need to be centered, so left adjustment (l, L) is
sufficient.


--- autosp.1	2026-06-02 22:56:49.975519629 +0000
+++ autosp.1.new	2026-06-03 01:05:56.469353498 +0000
@@ -1,161 +1,161 @@
 .\" This manpage is licensed under the GNU Public License
-.TH AUTOSP 1 2023-11-26  "" ""
+.TH AUTOSP 1 2023-11-26 "" ""
 
 .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 ]
-.RB [ \-l\ |\ \-\-log ]
+.RB [ \-d " | " \-\-dotted ]
+.RB [ \-l " | " \-\-log ]
 .IR infile [\fR.aspc\fP]
 .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, 
+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
 .IR outfile .tex.
-If no 
-.I outfile 
+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. 
+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 \\def\\atnextbar notation but 
-the non-standard command \\Cpause (or \\Cp) in a note segment also generates a
+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 \\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.
+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 
+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.  
+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 \\ha{*}, \\qa{.*}, \\qa{*}, \\ca{*}, etc. 
+form \eha{*}, \eqa{.*}, \eqa{*}, \eca{*}, etc.
 
-From version 2017-06-14, the effects of \\TransformNotes calls are implemented by the 
+\&From version 2017-06-14, the effects of \eTransformNotes calls are implemented by the
 .B autosp
 pre-processor. This
-enables use of 
+enables use of
 musixlyr in
-.B autosp 
-scores; musixlyr.tex 
+.B autosp
+scores; musixlyr.tex
 is incompatible with the
-musixtnt.tex 
-implementation of \\TransformNotes.
+musixtnt.tex
+implementation of \eTransformNotes.
 
 All other conventional MusiXTeX commands are output exactly as given in the input.
 
@@ -164,130 +164,130 @@ All other conventional MusiXTeX commands
 
 .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 
+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 
+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 
+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.  
+total note durations are identical.
 
-In some baroque scores, particularly by J.S. Bach, a beamed sixteenth note is vertically aligned
+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
 .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, 
+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
@@ -296,8 +296,8 @@ can be used to convert "legacy" MusiXTeX
 .SH SEE ALSO
 .BR msxlint (1)
 .BR tex2aspc (1)
-.PP 
+.PP
 musixdoc.pdf
 
-.SH AUTHOR 
+.SH AUTHOR
 This program and manual page were written by Bob Tennent <[email protected]>.

  Check the output from "lintian" in the Debian distribution.

  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>

  To find most trailing spaces use

grep -n -e ' $' -e ' \\f.$' -e ' \\"' <man page>

  The same goes for man pages that are used as an input.

-.-

  For a style guide use

  mandoc -T lint

-.-

  For general input conventions consult the man page "nroff(7)" (item
"Input conventions") or the Texinfo manual about the same item.

-.-

  Any "autogenerator" should check its products with the above mentioned
'groff', 'mandoc', and additionally with 'nroff ...'.

  It should also check its input files for too long (> 80) lines.

  This is just a simple quality control measure.

  The "autogenerator" may have to be corrected to get a better man page,
the source file may, and any additional file may.

-.-

  Common defects:

  Not removing trailing spaces (in in- and output).
  The reason for these trailing spaces should be found and eliminated.

  "git" has a "tool" to point out whitespace,
see for example "git-apply(1)" and git-config(1)")

-.-

  Not beginning each input sentence on a new line.

Line length and patch size should thus be reduced when that has been fixed.

  The script "reportbug" uses 'quoted-printable' encoding when a line is
longer than 1024 characters in an 'ascii' file.

  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 -d -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 from 'diff -d -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)

-.-

Subject: clean files of trailing whitespace

  Trailing whitespace is so unnecessary, that its presence may be removed
before files containing it are distributed.

  Some programs have a tool to point out its presence, like

gcc

  with option "-Wtrailing-whitespace"

git
  with option "apply --whitespace=..."

  and in ".git/config"

[core]
	whitespace=...

grep

  with option -e ' $'

less

  with command "/ $"

mandoc -T lint

  default action


----- End forwarded message -----