Reacted on some of the complaints of codespell
This commit is contained in:
@ -50,7 +50,7 @@
|
||||
@c man .\" First parameter, NAME, should be all caps
|
||||
@c man .\" Second parameter, SECTION, should be 1-8, maybe w/ subsection
|
||||
@c man .\" other parameters are allowed: see man(7), man(1)
|
||||
@c man .TH XORRISO 1 "Version 1.4.5, Jul 03, 2016"
|
||||
@c man .TH XORRISO 1 "Version 1.4.5, Jul 20, 2016"
|
||||
@c man .\" Please adjust this date whenever revising the manpage.
|
||||
@c man .\"
|
||||
@c man .\" Some roff macros, for reference:
|
||||
@ -2999,7 +2999,7 @@ as reported by the drive. They would be chosen by -read_speed "min" or
|
||||
@item -close_damaged "as_needed"|"force"
|
||||
@kindex -close_damaged closes damaged track and session
|
||||
@cindex Damaged track and session, close, -close_damaged
|
||||
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
|
||||
@ -6041,7 +6041,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.
|
||||
@*
|
||||
@ -6070,7 +6070,7 @@ input lines minus one tells xorriso how many newline characters are
|
||||
part of the input text.
|
||||
@*
|
||||
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.
|
||||
@ -6080,7 +6080,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.
|
||||
@*
|
||||
If -backslash_codes "encode_output" is enabled, then the strings undergo
|
||||
encoding as if they were enclosed in quotes. Escpecially each string
|
||||
@ -6101,11 +6101,11 @@ issue.
|
||||
@*
|
||||
@strong{parse_silently}
|
||||
@*
|
||||
Like "parse" but not issueing a prompting message. Confusing to humans.
|
||||
Like "parse" but not issuing a prompting message. Confusing to humans.
|
||||
@*
|
||||
@strong{parse_bulk_silently}
|
||||
@*
|
||||
Like "parse_bulk" but not issueing a prompting message. Confusing to humans.
|
||||
Like "parse_bulk" but not issuing a prompting message. Confusing to humans.
|
||||
@*
|
||||
@strong{compare_sev}
|
||||
@*
|
||||
|
Reference in New Issue
Block a user