Reacted on some of the complaints of codespell
This commit is contained in:
@ -9,7 +9,7 @@
|
||||
.\" First parameter, NAME, should be all caps
|
||||
.\" Second parameter, SECTION, should be 1-8, maybe w/ subsection
|
||||
.\" other parameters are allowed: see man(7), man(1)
|
||||
.TH XORRISO 1 "Version 1.4.5, Jul 03, 2016"
|
||||
.TH XORRISO 1 "Version 1.4.5, Jul 20, 2016"
|
||||
.\" Please adjust this date whenever revising the manpage.
|
||||
.\"
|
||||
.\" Some roff macros, for reference:
|
||||
@ -2549,7 +2549,7 @@ as reported by the drive. They would be chosen by \-read_speed "min" or
|
||||
"52xCD", "24xDVD", "20xBD".
|
||||
.TP
|
||||
\fB\-close_damaged\fR "as_needed"|"force"
|
||||
Try to close the upcomming track and session if the drive reported the medium
|
||||
Try to close the upcoming track and session if the drive reported the medium
|
||||
as damaged. This may apply to CD\-R, CD\-RW, DVD\-R, DVD\-RW, DVD+R, DVD+R DL,
|
||||
or BD\-R media. It is indicated by warning messages when the drive gets
|
||||
acquired, and by a remark "but next track is damaged" with the line
|
||||
@ -5212,7 +5212,7 @@ into lines which tell their structure.
|
||||
The first line tells the return value of Xorriso_sieve_get_result().
|
||||
The next line tells the number of strings. Each string begins by a line that
|
||||
tells the number of lines of the string. Then follow these lines. They are to
|
||||
be concatenated with a newline character inbetween each of them.
|
||||
be concatenated with a newline character between each of them.
|
||||
Finally the number of still available recorded results of the given name
|
||||
is put out.
|
||||
.br
|
||||
@ -5241,7 +5241,7 @@ input lines minus one tells xorriso how many newline characters are
|
||||
part of the input text.
|
||||
.br
|
||||
The announced number of text lines will be read from dialog input,
|
||||
concatenated with a newline character inbetween each of them,
|
||||
concatenated with a newline character between each of them,
|
||||
and submitted to Xorriso_parse_line() as parameter line.
|
||||
Note that newlines outside of quotation marks are
|
||||
interpreted as separators if the separators parameter is empty.
|
||||
@ -5251,7 +5251,7 @@ into lines which tell their structure.
|
||||
The first line tells the return value of Xorriso_parse_line().
|
||||
The next line tells the number of strings. Each string begins by a line that
|
||||
tells the number of lines of the string. Then follow these lines. They are to
|
||||
be concatenated with a newline character inbetween each of them.
|
||||
be concatenated with a newline character between each of them.
|
||||
.br
|
||||
If \-backslash_codes "encode_output" is enabled, then the strings undergo
|
||||
encoding as if they were enclosed in quotes. Escpecially each string
|
||||
@ -5272,11 +5272,11 @@ issue.
|
||||
.br
|
||||
\fBparse_silently\fR
|
||||
.br
|
||||
Like "parse" but not issueing a prompting message. Confusing to humans.
|
||||
Like "parse" but not issuing a prompting message. Confusing to humans.
|
||||
.br
|
||||
\fBparse_bulk_silently\fR
|
||||
.br
|
||||
Like "parse_bulk" but not issueing a prompting message. Confusing to humans.
|
||||
Like "parse_bulk" but not issuing a prompting message. Confusing to humans.
|
||||
.br
|
||||
\fBcompare_sev\fR
|
||||
.br
|
||||
|
Reference in New Issue
Block a user