[Bug-indent] Bug#132399: indent: bad quotes in manual page (fwd)

[Santiago Vila]

Hello.

I received this from the Debian bug system:

---------- Forwarded message ----------
Date: Mon, 4 Feb 2002 15:08:45 -0800
From: Matt Kraai <address@hidden>
To: Debian Bug Tracking System <address@hidden>
Subject: Bug#132399: indent: bad quotes in manual page

Package: indent
Version: 2.2.7-2
Severity: minor
Tags: patch

The indent manual page uses \' instead of '.  This is rendered as
an accent, ´ (0xb4), which displays as a solid box on my console.
It only needs to be escaped when it comes at the start of the
line, and the appropriate way to escape it is by preceding it with
a \& (a zero-width space).  The following patch fixes this
problem.

--- indent-2.2.7/man/indent.1   Mon Feb  4 15:02:09 2002
+++ indent/man/indent.1 Mon Feb  4 15:01:52 2002
@@ -103,12 +103,12 @@
 See \fB\ COMMENTS\fR.
 .TP
 .B -cdw\fR, \fB--cuddle-do-while\fR
-Cuddle while of \fBdo {} while;\fR and preceeding \`}\'.
+Cuddle while of \fBdo {} while;\fR and preceeding \`}'.
 .br
 See \fB\ COMMENTS\fR.
 .TP
 .B -ce\fR, \fB--cuddle-else\fR
-Cuddle else and preceeding \`}\'.
+Cuddle else and preceeding \`}'.
 .br
 See \fB\ COMMENTS\fR.
 .TP
@@ -201,7 +201,7 @@
 See \fB\ INDENTATION\fR.
 .TP
 .B -lps\fR, \fB--leave-preprocessor-space\fR
-Leave space between \`#\' and preprocessor directive.
+Leave space between \`#' and preprocessor directive.
 .br
 See \fB\ INDENTATION\fR.
 .TP
@@ -226,7 +226,7 @@
 See \fB\ DECLARATIONS\fR.
 .TP
 .B -nbfda\fR, \fB--dont-break-function-decl-args\fR
-Don\'t put each argument in a function declaration on a seperate line.
+Don't put each argument in a function declaration on a seperate line.
 .br
 See \fB\ DECLARATIONS\fR.
 .TP
@@ -281,7 +281,7 @@
 See \fB\ STATEMENTS\fR.
 .TP
 .B -nprs\fR, \fB--no-space-after-parentheses\fR
-Do not put a space after every \'(\' and before every \')\'.
+Do not put a space after every '(' and before every ')'.
 .br
 See \fB\ STATEMENTS\fR.
 .TP
@@ -306,7 +306,7 @@
 See \fB\ STATEMENTS\fR.
 .TP
 .B -nsc\fR, \fB--dont-star-comments\fR
-Do not put the \`*\' character at the left of comments.
+Do not put the \`*' character at the left of comments.
 .br
 See \fB\ COMMENTS\fR.
 .TP
@@ -317,7 +317,7 @@
 .TP
 .B -nss\fR, \fB--dont-space-special-semicolon\fR
 Do not force a space before the semicolon after certain statements.
-Disables \`-ss\'.
+Disables \`-ss'.
 .br
 See \fB\ STATEMENTS\fR.
 .TP
@@ -337,25 +337,25 @@
 See \fB\ COMMON\ STYLES\fR.
 .TP
 .B -npro\fR, \fB--ignore-profile\fR
-Do not read \`.indent.pro\' files.
+Do not read \`.indent.pro' files.
 .br
 See \fB\ INVOKING\ INDENT\fR.
 .TP
 .B -pcs\fR, \fB--space-after-procedure-calls\fR
 Insert a space between the name of the
-procedure being called and the \`(\'.
+procedure being called and the \`('.
 .br
 See \fB\ STATEMENTS\fR.
 .TP
 .B -pi\fIn\fB\fR, \fB--paren-indentation\fIn\fB\fR
-Specify the extra indentation per open parentheses \'(\' when a
+Specify the extra indentation per open parentheses '(' when a
 statement is broken.See \fB\ STATEMENTS\fR.
 .TP
 .B -pmt\fR, \fB--preserve-mtime\fR
 Preserve access and modification times on output files.See \fB\ MISCELLANEOUS\ 
OPTIONS\fR.
 .TP
 .B -prs\fR, \fB--space-after-parentheses\fR
-Put a space after every \'(\' and before every \')\'.
+Put a space after every '(' and before every ')'.
 .br
 See \fB\ STATEMENTS\fR.
 .TP
@@ -385,7 +385,7 @@
 See \fB\ STATEMENTS\fR.
 .TP
 .B -sc\fR, \fB--start-left-side-of-comments\fR
-Put the \`*\' character at the left of comments.
+Put the \`*' character at the left of comments.
 .br
 See \fB\ COMMENTS\fR.
 .TP
@@ -456,19 +456,19 @@

 In the second form, only one input file is specified.  In this case, or
 when the standard input is used, you may specify an output file after
-the \`-o\' option.
+the \`-o' option.

-To cause \fBindent\fR to write to standard output, use the \`-st\'
+To cause \fBindent\fR to write to standard output, use the \`-st'
 option.  This is only allowed when there is only one input file, or when
 the standard input is used.

 If no input files are named, the standard input is read for input.
-Also, if a filename named \`-\' is specified, then the standard input
+Also, if a filename named \`-' is specified, then the standard input
 is read.

 As an example, each of the following commands will input the program
-\`slithy_toves.c\' and write its indented text to
-\`slithy_toves.out\':
+\`slithy_toves.c' and write its indented text to
+\`slithy_toves.out':

 .in +5
 .nf
@@ -486,9 +486,9 @@

 Most other options to \fBindent\fR control how programs are formatted.
 As of version 1.2, \fBindent\fR also recognizes a long name for each
-option name.  Long options are prefixed by either \`--\' or
-\`+\'.
-[ \`+\' is being superseded by \`--\' to
+option name.  Long options are prefixed by either \`--' or
+\`+'.
+[ \`+' is being superseded by \`--' to
 maintain consistency with the POSIX standard.]
  In most of this document,
 the traditional, short names are used for the sake of brevity.
@@ -505,10 +505,10 @@
 .ad
 .fi

-This will indent the program \`test/metabolism.c\' using the
-\`-br\' and \`-l85\' options, write the output back to
-\`test/metabolism.c\', and write the original contents of
-\`test/metabolism.c\' to a backup file in the directory \`test\'.
+This will indent the program \`test/metabolism.c' using the
+\`-br' and \`-l85' options, write the output back to
+\`test/metabolism.c', and write the original contents of
+\`test/metabolism.c' to a backup file in the directory \`test'.

 Equivalent invocations using long option names for this example would
 be:
@@ -526,24 +526,24 @@
 .fi

 If you find that you often use \fBindent\fR with the same options, you
-may put those options into a file named \`.indent.pro\'.
-.B indent\fR will first look for \`.indent.pro\' in the current
+may put those options into a file named \`.indent.pro'.
+.B indent\fR will first look for \`.indent.pro' in the current
 directory and use that if found.  Otherwise, \fBindent\fR will search
-your home directory for \`.indent.pro\' and use that file if it is
+your home directory for \`.indent.pro' and use that file if it is
 found.  This behaviour is different from that of other versions of
 .B indent\fR, which load both files if they both exist.

-The format of \`.indent.pro\' is simply a list of options, just as
+The format of \`.indent.pro' is simply a list of options, just as
 they would appear on the command line, separated by white space (tabs,
-spaces, and newlines).  Options in \`.indent.pro\' may be surrounded by C
+spaces, and newlines).  Options in \`.indent.pro' may be surrounded by C
 or C++ comments, in which case they are ignored.

 Command line switches are handled \fIafter\fR processing
-\`.indent.pro\'.  Options specified later override arguments
+\`.indent.pro'.  Options specified later override arguments
 specified earlier, with one exception: Explicitly specified options
 always override background options (See \fBCOMMON\ STYLES\fR).  You can
-prevent \fBindent\fR from reading an \`.indent.pro\' file by
-specifying the \`-npro\' option.
+prevent \fBindent\fR from reading an \`.indent.pro' file by
+specifying the \`-npro' option.

 .SH "BACKUP FILES"

@@ -553,36 +553,36 @@

 Simple backup file names are generated by appending a suffix to the
 original file name.  The default for this suffix is the
-one-character string \`~\' (tilde).  Thus, the backup file for
-\`python.c\' would be \`python.c~\'.
+one-character string \`~' (tilde).  Thus, the backup file for
+\`python.c' would be \`python.c~'.

 Instead of the default, you may specify any string as a suffix by
 setting the environment variable \fBSIMPLE_BACKUP_SUFFIX\fR to
 your preferred suffix.

-Numbered backup versions of a file \`momeraths.c\' look like
-\`momeraths.c.~23~\', where 23 is the version of this particular
-backup.  When making a numbered backup of the file \`src/momeraths.c\',
-the backup file will be named \`src/momeraths.c.~\fIV\fR~\', where
+Numbered backup versions of a file \`momeraths.c' look like
+\`momeraths.c.~23~', where 23 is the version of this particular
+backup.  When making a numbered backup of the file \`src/momeraths.c',
+the backup file will be named \`src/momeraths.c.~\fIV\fR~', where
 .I V\fR is one greater than the highest version currently existing in
-the directory \`src\'.  The environment variable \fBVERSION_WIDTH\fR
+the directory \`src'.  The environment variable \fBVERSION_WIDTH\fR
 controls the number of digits, using left zero padding when necessary.
 For instance, setting this variable to "2" will lead to the backup
-file being named \`momeraths.c.~04~\'.
+file being named \`momeraths.c.~04~'.

 The type of backup file made is controlled by the value of the
 environment variable \fBVERSION_CONTROL\fR.  If it is the string
-\`simple\', then only simple backups will be made.  If its value is
-the string \`numbered\', then numbered backups will be made.  If its
-value is \`numbered-existing\', then numbered backups will be made if
+\`simple', then only simple backups will be made.  If its value is
+the string \`numbered', then numbered backups will be made.  If its
+value is \`numbered-existing', then numbered backups will be made if
 there \fIalready exist\fR numbered backups for the file being indented;
 otherwise, a simple backup is made.  If \fBVERSION_CONTROL\fR is not
 set, then \fBindent\fR assumes the behaviour of
-\`numbered-existing\'.
+\`numbered-existing'.

-Other versions of \fBindent\fR use the suffix \`.BAK\' in naming
+Other versions of \fBindent\fR use the suffix \`.BAK' in naming
 backup files.  This behaviour can be emulated by setting
-.B SIMPLE_BACKUP_SUFFIX\fR to \`.BAK\'.
+.B SIMPLE_BACKUP_SUFFIX\fR to \`.BAK'.

 Note also that other versions of \fBindent\fR make backups in the
 current directory, rather than in the directory of the source file as
@@ -598,7 +598,7 @@

 As of version 1.2, the default style of GNU \fBindent\fR is the GNU
 style.  Thus, it is no longer necessary to specify the option
-\`-gnu\' to obtain this format, although doing so will not cause an
+\`-gnu' to obtain this format, although doing so will not cause an
 error.  Option settings which correspond to the GNU style are:

 .in +5
@@ -619,7 +619,7 @@
 size of integers, etc.)

 The Kernighan & Ritchie style is used throughout their well-known book
-"The C Programming Language".  It is enabled with the \`-kr\'
+"The C Programming Language".  It is enabled with the \`-kr'
 option.  The Kernighan & Ritchie style corresponds to the following set
 of options:

@@ -639,7 +639,7 @@
 chosen column 33.

 The style of the original Berkeley \fBindent\fR may be obtained by
-specifying \`-orig\' (or by specifying \`--original\', using the
+specifying \`-orig' (or by specifying \`--original', using the
 long option name).  This style is equivalent to the following settings:

 .in +5
@@ -658,27 +658,27 @@
 .B indent\fR has a number of options to insert or delete blank lines in
 specific places.

-The \`-bad\' option causes \fBindent\fR to force a blank line after
-every block of declarations.  The \`-nbad\' option causes
+The \`-bad' option causes \fBindent\fR to force a blank line after
+every block of declarations.  The \`-nbad' option causes
 .B indent\fR not to force such blank lines.

-The \`-bap\' option forces a blank line after every procedure body.
-The \`-nbap\' option forces no such blank line.
+The \`-bap' option forces a blank line after every procedure body.
+The \`-nbap' option forces no such blank line.

-The \`-bbb\' option forces a blank line before every boxed comment
+The \`-bbb' option forces a blank line before every boxed comment
 (See \fBCOMMENTS\fR.)
-The \`-nbbb\' option does not force such blank lines.
+The \`-nbbb' option does not force such blank lines.

-The \`-sob\' option causes \fBindent\fR to swallow optional blank
+The \`-sob' option causes \fBindent\fR to swallow optional blank
 lines (that is, any optional blank lines present in the input will be
-removed from the output).  If the \`-nsob\' is specified, any blank
+removed from the output).  If the \`-nsob' is specified, any blank
 lines present in the input file will be copied to the output file.


 .SH "--blank-lines-after-declarations"

-The \`-bad\' option forces a blank line after every block of
-declarations.  The \`-nbad\' option does not add any such blank
+The \`-bad' option forces a blank line after every block of
+declarations.  The \`-nbad' option does not add any such blank
 lines.

 For example, given the input
@@ -722,7 +722,7 @@

 .SH "--blank-lines-after-procedures"

-The \`-bap\' option forces a blank line after every procedure body.
+The \`-bap' option forces a blank line after every procedure body.

 For example, given the input

@@ -790,8 +790,8 @@
 .SH "COMMENTS"

 .B indent\fR formats both C and C++ comments. C comments are begun with
-\`/*\', terminated with \`*/\' and may contain newline characters.
-C++ comments begin with the delimiter \`//\' and end at the newline.
+\`/*', terminated with \`*/' and may contain newline characters.
+C++ comments begin with the delimiter \`//' and end at the newline.

 .B indent\fR handles comments differently depending upon their context.
 .B indent\fR attempts to distinguish between comments which follow
@@ -809,11 +809,11 @@

 .B indent\fR attempts to leave \fIboxed comments\fR unmodified.  The
 general idea of such a comment is that it is enclosed in a rectangle or
-\`\`box\'\' of stars or dashes to visually set it apart.  More precisely,
-boxed comments are defined as those in which the initial \`/*\' is
-followed immediately by the character \`*\', \`=\', \`_\', or
-\`-\', or those in which the beginning comment delimiter (\`/*\')
-is on a line by itself, and the following line begins with a \`*\' in
+\`\`box'' of stars or dashes to visually set it apart.  More precisely,
+boxed comments are defined as those in which the initial \`/*' is
+followed immediately by the character \`*', \`=', \`_', or
+\`-', or those in which the beginning comment delimiter (\`/*')
+is on a line by itself, and the following line begins with a \`*' in
 the same column as the star of the opening delimiter.

 Examples of boxed comments are:
@@ -839,7 +839,7 @@
 that an embedded tab character may be converted into the appropriate
 number of spaces.

-If the \`-bbb\' option is specified, all such boxed comments will be
+If the \`-bbb' option is specified, all such boxed comments will be
 preceded by a blank line, unless such a comment is preceded by code.

 Comments which are not boxed comments may be formatted, which means that
@@ -847,11 +847,11 @@
 whitespace.  Single newlines are equivalent to a space, but blank lines
 (two or more newlines in a row) are taken to mean a paragraph break.
 Formatting of comments which begin after the first column is enabled
-with the \`-fca\' option.  To format those beginning in column one,
-specify \`-fc1\'.  Such formatting is disabled by default.
+with the \`-fca' option.  To format those beginning in column one,
+specify \`-fc1'.  Such formatting is disabled by default.

 The right margin for formatting defaults to 78, but may be changed with
-the \`-lc\' option.  If the margin specified does not allow the
+the \`-lc' option.  If the margin specified does not allow the
 comment to be printed, the margin will be automatically extended for the
 duration of that comment.  The margin is not respected if the comment is
 not being formatted.
@@ -860,17 +860,17 @@
 left), it will be indented to the column it was found in unless the
 comment is within a block of code.  In that case, such a comment will be
 aligned with the indented code of that block (unless the comment began
-in the first column).  This alignment may be affected by the \`-d\'
+in the first column).  This alignment may be affected by the \`-d'
 option, which specifies an amount by which such comments are moved to
-the \fIleft\fR, or unindented.  For example, \`-d2\' places comments
+the \fIleft\fR, or unindented.  For example, \`-d2' places comments
 two spaces to the left of code.  By default, comments are aligned with
 code, unless they begin in the first column, in which case they are left
-there by default --- to get them aligned with the code, specify \`-fc1\'.
+there by default --- to get them aligned with the code, specify \`-fc1'.

 Comments to the right of code will appear by default in column 33.
-This may be changed with one of three options.  \`-c\' will specify
-the column for comments following code, \`-cd\' specifies the
-column for comments following declarations, and \`-cp\' specifies
+This may be changed with one of three options.  \`-c' will specify
+the column for comments following code, \`-cd' specifies the
+column for comments following declarations, and \`-cp' specifies
 the column for comments following preprocessor directives \fB#else\fR
 and \fB#endif\fR.

@@ -880,7 +880,7 @@
 space past the end of the directive.  This extension lasts only for
 the output of that particular comment.

-The \`-cdb\' option places the comment delimiters on blank lines.
+The \`-cdb' option places the comment delimiters on blank lines.
 Thus, a single line comment like \fB/* Loving hug */\fR can be
 transformed into:

@@ -895,8 +895,8 @@
 .fi

 Stars can be placed at the beginning of multi-line comments with the
-\`-sc\' option.  Thus, the single-line comment above can be
-transformed (with \`-cdb -sc\') into:
+\`-sc' option.  Thus, the single-line comment above can be
+transformed (with \`-cdb -sc') into:

 .in +5
 .nf
@@ -910,9 +910,9 @@

 .SH "STATEMENTS"

-The \`-br\' or \`-bl\' option specifies how to format braces.
+The \`-br' or \`-bl' option specifies how to format braces.

-The \`-br\' option formats statement braces like this:
+The \`-br' option formats statement braces like this:

 .in +5
 .nf
@@ -924,7 +924,7 @@
 .ad
 .fi

-The \`-bl\' option formats them like this:
+The \`-bl' option formats them like this:

 .in +5
 .nf
@@ -937,10 +937,10 @@
 .ad
 .fi

-If you use the \`-bl\' option, you may also want to specify the
-\`-bli\' option.  This option specifies the number of spaces by
-which braces are indented.  \`-bli2\', the default, gives the
-result shown above.  \`-bli0\' results in the following:
+If you use the \`-bl' option, you may also want to specify the
+\`-bli' option.  This option specifies the number of spaces by
+which braces are indented.  \`-bli2', the default, gives the
+result shown above.  \`-bli0' results in the following:

 .in +5
 .nf
@@ -953,10 +953,10 @@
 .ad
 .fi

-If you are using the \`-br\' option, you probably want to also use
-the \`-ce\' option.  This causes the \fBelse\fR in an if-then-else
-construct to cuddle up to the immediately preceding \`}\'.  For
-example, with \`-br -ce\' you get the following:
+If you are using the \`-br' option, you probably want to also use
+the \`-ce' option.  This causes the \fBelse\fR in an if-then-else
+construct to cuddle up to the immediately preceding \`}'.  For
+example, with \`-br -ce' you get the following:

 .in +5
 .nf
@@ -970,7 +970,7 @@
 .ad
 .fi

-With \`-br -nce\' that code would appear as
+With \`-br -nce' that code would appear as

 .in +5
 .nf
@@ -986,8 +986,8 @@
 .fi

 This causes the \fBwhile\fR in a do-while
-loop to cuddle up to the immediately preceding \`}\'.  For
-example, with \`-cdw\' you get the following:
+loop to cuddle up to the immediately preceding \`}'.  For
+example, with \`-cdw' you get the following:

 .in +5
 .nf
@@ -999,7 +999,7 @@
 .ad
 .fi

-With \`-ncdw\' that code would appear as
+With \`-ncdw' that code would appear as

 .in +5
 .nf
@@ -1012,7 +1012,7 @@
 .ad
 .fi

-The \`-cli\' option specifies the number of spaces that case labels
+The \`-cli' option specifies the number of spaces that case labels
 should be indented to the right of the containing \fBswitch\fR
 statement.

@@ -1036,7 +1036,7 @@
 .ad
 .fi

-Using the \`-cli2\' that would become:
+Using the \`-cli2' that would become:

 .in +5
 .nf
@@ -1057,8 +1057,8 @@
 .fi

 The indentation of the braces below a case statement can be
-controlled with the \`-cbi\fIn\fR\' option.  For example,
-using \`-cli2 -cbi0\' results in:
+controlled with the \`-cbi\fIn\fR' option.  For example,
+using \`-cli2 -cbi0' results in:

 .in +5
 .nf
@@ -1079,33 +1079,33 @@
 .fi

 If a semicolon is on the same line as a \fBfor\fR or \fBwhile\fR
-statement, the \`-ss\' option will cause a space to be placed before
+statement, the \`-ss' option will cause a space to be placed before
 the semicolon.  This emphasizes the semicolon, making it clear that the
 body of the \fBfor\fR or \fBwhile\fR statement is an empty statement.
-\`-nss\' disables this feature.
+\`-nss' disables this feature.

-The \`-pcs\' option causes a space to be placed between the name of
-the procedure being called and the \`(\' (for example, \fBputs\ ("Hi");\fR.  
The \`-npcs\' option would give \fBputs("Hi");\fR).
+The \`-pcs' option causes a space to be placed between the name of
+the procedure being called and the \`(' (for example, \fBputs\ ("Hi");\fR.  
The \`-npcs' option would give \fBputs("Hi");\fR).


-If the \`-cs\' option is specified, \fBindent\fR puts a space after
+If the \`-cs' option is specified, \fBindent\fR puts a space after
 a cast operator.

-The \`-bs\' option ensures that there is a space between the
+The \`-bs' option ensures that there is a space between the
 keyword \fBsizeof\fR and its argument.  In some versions, this is
-known as the \`Bill_Shannon\' option.
+known as the \`Bill_Shannon' option.

-The \`-saf\' option forces a space between an \fBfor\fR
+The \`-saf' option forces a space between an \fBfor\fR
 and the following parenthesis.  This is the default.

-The \`-sai\' option forces a space between an \fBif\fR
+The \`-sai' option forces a space between an \fBif\fR
 and the following parenthesis.  This is the default.

-The \`-saw\' option forces a space between an \fBwhile\fR
+The \`-saw' option forces a space between an \fBwhile\fR
 and the following parenthesis.  This is the default.

-The \`-prs\' option causes all parentheses to be seperated with
-a space from the what is between them.  For example, using \`-prs\'
+The \`-prs' option causes all parentheses to be seperated with
+a space from the what is between them.  For example, using \`-prs'
 results in code like:

 .in +5
@@ -1114,7 +1114,7 @@
   while ( ( e_code - s_code ) < ( dec_ind - 1 ) )
     {
       set_buf_break ( bb_dec_ind );
-      *e_code++ = \' \';
+      *e_code++ = ' ';
     }
 .in -5
 .ad
@@ -1123,7 +1123,7 @@
 .SH "DECLARATIONS"

 By default \fBindent\fR will line up identifiers, in the column
-specified by the \`-di\' option.  For example, \`-di16\' makes
+specified by the \`-di' option.  For example, \`-di16' makes
 things look like:

 .in +5
@@ -1135,7 +1135,7 @@
 .ad
 .fi

-Using a small value (such as one or two) for the \`-di\' option can
+Using a small value (such as one or two) for the \`-di' option can
 be used to cause the identifiers to be placed in the first available
 position; for example:

@@ -1148,9 +1148,9 @@
 .ad
 .fi

-The value given to the \`-di\' option will still affect variables
+The value given to the \`-di' option will still affect variables
 which are put on separate lines from their types, for example
-\`-di2\' will lead to:
+\`-di2' will lead to:

 .in +5
 .nf
@@ -1161,7 +1161,7 @@
 .ad
 .fi

-If the \`-bc\' option is specified, a newline is forced after each
+If the \`-bc' option is specified, a newline is forced after each
 comma in a declaration.  For example,

 .in +5
@@ -1174,7 +1174,7 @@
 .ad
 .fi

-With the \`-nbc\' option this would look like
+With the \`-nbc' option this would look like

 .in +5
 .nf
@@ -1184,7 +1184,7 @@
 .ad
 .fi

-The \`-bfda\' option causes a newline to be forced after the comma
+The \`-bfda' option causes a newline to be forced after the comma
 separating the arguments of a function declaration.  The arguments will
 appear at the current indention level matching the opening paren.  This
 is particularly helpful for functions with long argument lists.   For
@@ -1197,7 +1197,7 @@
 .in -5
 .ad
 .fi
-With the \`-bfda\' option this would look like
+With the \`-bfda' option this would look like

 .in +5
 .nf
@@ -1211,14 +1211,14 @@
 .ad
 .fi

-The \`-psl\' option causes the type of a procedure being defined to
+The \`-psl' option causes the type of a procedure being defined to
 be placed on the line before the name of the procedure.  This style is
 required for the \fBetags\fR program to work correctly, as well as some
 of the \fBc-mode\fR functions of Emacs.

-You must use the \`-T\'
+You must use the \`-T'
 option to tell \fBindent\fR the name of all the typenames in your
-program that are defined by \fBtypedef\fR.  \`-T\' can be specified
+program that are defined by \fBtypedef\fR.  \`-T' can be specified
 more than once, and all names specified are used.  For example, if your
 program contains

@@ -1231,10 +1231,10 @@
 .ad
 .fi

-you would use the options \`-T CODE_ADDR -T COLOR\'.
+you would use the options \`-T CODE_ADDR -T COLOR'.

-The \`-brs\' or \`-bls\' option specifies how to format braces
-in struct declarations.  The \`-brs\' option formats braces like
+The \`-brs' or \`-bls' option specifies how to format braces
+in struct declarations.  The \`-brs' option formats braces like
 this:

 .in +5
@@ -1247,7 +1247,7 @@
 .ad
 .fi

-The \`-bls\' option formats them like this:
+The \`-bls' option formats them like this:

 .in +5
 .nf
@@ -1265,17 +1265,17 @@
 One issue in the formatting of code is how far each line should be
 indented from the left margin.  When the beginning of a statement such
 as \fBif\fR or \fBfor\fR is encountered, the indentation level is
-increased by the value specified by the \`-i\' option.  For example,
-use \`-i8\' to specify an eight character indentation for each
+increased by the value specified by the \`-i' option.  For example,
+use \`-i8' to specify an eight character indentation for each
 level.  When a statement is broken across two lines, the second line is
-indented by a number of additional spaces specified by the \`-ci\'
-option.  \`-ci\' defaults to 0.  However, if the \`-lp\' option is
+indented by a number of additional spaces specified by the \`-ci'
+option.  \`-ci' defaults to 0.  However, if the \`-lp' option is
 specified, and a line has a left parenthesis which is not closed on that
 line, then continuation lines will be lined up to start at the character
 position just after the left parenthesis.  This processing also applies
-to \`[\' and applies to \`{\' when it occurs in initialization
+to \`[' and applies to \`{' when it occurs in initialization
 lists.  For example, a piece of continued code might look like this with
-\`-nlp -ci3\' in effect:
+\`-nlp -ci3' in effect:

 .in +5
 .nf
@@ -1286,7 +1286,7 @@
 .ad
 .fi

-With \`-lp\' in effect the code looks somewhat clearer:
+With \`-lp' in effect the code looks somewhat clearer:

 .in +5
 .nf
@@ -1311,8 +1311,8 @@
 .ad
 .fi

-The option \`-ip\fIN\fR\' can be used to set the extra offset per paren.
-For instance, \`-ip0\' would format the above as:
+The option \`-ip\fIN\fR' can be used to set the extra offset per paren.
+For instance, \`-ip0' would format the above as:

 .in +5
 .nf
@@ -1327,13 +1327,13 @@

 .B indent\fR assumes that tabs are placed at regular intervals of both
 input and output character streams.  These intervals are by default 8
-columns wide, but (as of version 1.2) may be changed by the \`-ts\'
+columns wide, but (as of version 1.2) may be changed by the \`-ts'
 option.  Tabs are treated as the equivalent number of spaces.

 The indentation of type declarations in old-style function definitions
-is controlled by the \`-ip\' parameter.  This is a numeric parameter
+is controlled by the \`-ip' parameter.  This is a numeric parameter
 specifying how many spaces to indent type declarations.  For example,
-the default \`-ip5\' makes definitions look like this:
+the default \`-ip5' makes definitions look like this:

 .in +5
 .nf
@@ -1350,17 +1350,17 @@
 .ad
 .fi

-For compatibility with other versions of indent, the option \`-nip\'
-is provided, which is equivalent to \`-ip0\'.
+For compatibility with other versions of indent, the option \`-nip'
+is provided, which is equivalent to \`-ip0'.

 ANSI C allows white space to be placed on preprocessor command lines
-between the character \`#\' and the command name.  By default,
-.B indent\fR removes this space, but specifying the \`-lps\' option
+between the character \`#' and the command name.  By default,
+.B indent\fR removes this space, but specifying the \`-lps' option
 directs \fBindent\fR to leave this space unmodified.

 .SH "BREAKING LONG LINES"

-With the option \`-l\fIn\fR\', or \`--line-length\fIn\fR\', it is
+With the option \`-l\fIn\fR', or \`--line-length\fIn\fR', it is
 possible to specify the maximum length of a line of C code, not including
 possible comments that follow it.

@@ -1371,38 +1371,38 @@
 Currently there are two options that allows one to interfere with the
 algorithm that determines where to break a line.

-The \`-bbo\' option causes GNU \fBindent\fR to prefer to break
+The \`-bbo' option causes GNU \fBindent\fR to prefer to break
 long lines before the boolean operators \fB&&\fR and \fB||\fR.  The
-\`-nbbo\' option causes GNU \fBindent\fR not have that
-preference.  For example, the default option \`-bbo\' (together
-with \`--line-length60\' and \`--ignore-newlines\') makes code
+\`-nbbo' option causes GNU \fBindent\fR not have that
+preference.  For example, the default option \`-bbo' (together
+with \`--line-length60' and \`--ignore-newlines') makes code
 look like this:

 .in +5
 .nf
 .na
   if (mask
-      && ((mask[0] == \'\\0\')
-          || (mask[1] == \'\\0\'
-              && ((mask[0] == \'0\') || (mask[0] == \'*\')))))
+      && ((mask[0] == '\\0')
+          || (mask[1] == '\\0'
+              && ((mask[0] == '0') || (mask[0] == '*')))))
 .in -5
 .ad
 .fi

-Using the option \`-nbbo\' will make it look like this:
+Using the option \`-nbbo' will make it look like this:

 .in +5
 .nf
 .na
   if (mask &&
-      ((mask[0] == \'\\0\') ||
-       (mask[1] == \'\\0\' &&
-        ((mask[0] == \'0\') || (mask[0] == \'*\')))))
+      ((mask[0] == '\\0') ||
+       (mask[1] == '\\0' &&
+        ((mask[0] == '0') || (mask[0] == '*')))))
 .in -5
 .ad
 .fi

-The default \`-hnl\', however, honours newlines in the input file by
+The default \`-hnl', however, honours newlines in the input file by
 giving them the highest possible priority to break lines at.  For example,
 when the input file looks like this:

@@ -1410,15 +1410,15 @@
 .nf
 .na
   if (mask
-      && ((mask[0] == \'\\0\')
-      || (mask[1] == \'\\0\' && ((mask[0] == \'0\') || (mask[0] == \'*\')))))
+      && ((mask[0] == '\\0')
+      || (mask[1] == '\\0' && ((mask[0] == '0') || (mask[0] == '*')))))
 .in -5
 .ad
 .fi

-then using the option \`-hnl\', or \`--honour-newlines\',
-together with the previously mentioned \`-nbbo\' and
-\`--line-length60\', will cause the output not to be what is given
+then using the option \`-hnl', or \`--honour-newlines',
+together with the previously mentioned \`-nbbo' and
+\`--line-length60', will cause the output not to be what is given
 in the last example but instead will prefer to break at the positions
 where the code was broken in the input file:

@@ -1426,9 +1426,9 @@
 .nf
 .na
   if (mask
-      && ((mask[0] == \'\\0\')
-          || (mask[1] == \'\\0\' &&
-              ((mask[0] == \'0\') || (mask[0] == \'*\')))))
+      && ((mask[0] == '\\0')
+          || (mask[1] == '\\0' &&
+              ((mask[0] == '0') || (mask[0] == '*')))))
 .in -5
 .ad
 .fi
@@ -1436,7 +1436,7 @@
 The idea behind this option is that lines which are too long, but are already
 broken up, will not be touched by GNU \fBindent\fR.  Really messy code
 should be run through \fBindent\fR at least once using the
-\`--ignore-newlines\' option though.
+\`--ignore-newlines' option though.

 .SH "DISABLING FORMATTING"

@@ -1477,15 +1477,15 @@
 .B indent -version\fR.  This will report the version number of
 .B indent\fR, without doing any of the normal processing.

-The \`-v\' option can be used to turn on verbose mode.  When in
+The \`-v' option can be used to turn on verbose mode.  When in
 verbose mode, \fBindent\fR reports when it splits one line of input
 into two more more lines of output, and gives some size statistics at
 completion.

-The \`-pmt\' option causes \fBindent\fR to preserve the access
+The \`-pmt' option causes \fBindent\fR to preserve the access
 and modification times on the output files.  Using this option
 has the advantage that running indent on all source and header
-files in a project won\'t cause \fBmake\fR to rebuild all targets.
+files in a project won't cause \fBmake\fR to rebuild all targets.
 This option is only available on Operating Systems that have the
 POSIX \fButime(2)\fR function.

@@ -1502,18 +1502,18 @@
 the inability to join lines.  The result is that running a file
 through \fBindent\fR is \fIirreversible\fR, even if the used input
 file was the result of running \fBindent\fR with a given profile
-(\`.indent.pro\').
+(\`.indent.pro').

 While an attempt was made to get \fBindent\fR working for C++, it
 will not do a good job on any C++ source except the very simple.

-.B indent\fR does not look at the given \`--line-length\' option
+.B indent\fR does not look at the given \`--line-length' option
 when writing comments to the output file.  This results often in comments
 being put far to the right.  In order to prohibit \fBindent\fR from
 joining a broken line that has a comment at the end, make sure that the
 comments start on the first line of the break.

-.B indent\fR does not count lines and comments (see the \`-v\'
+.B indent\fR does not count lines and comments (see the \`-v'
 option) when \fBindent\fR is turned off with
 .B /* *INDENT-OFF* */\fR.

@@ -1526,8 +1526,8 @@

 The following copyright notice applies to the \fBindent\fR program.
 The copyright and copying permissions for this manual appear near the
-beginning of \`indent.texinfo\' and \`indent.info\', and near the
-end of \`indent.1\'.
+beginning of \`indent.texinfo' and \`indent.info', and near the
+end of \`indent.1'.

 .nf
 .na
@@ -1549,14 +1549,14 @@
 Urbana, and Sun Microsystems, Inc.  The name of either University
 or Sun Microsystems may not be used to endorse or promote products
 derived from this software without specific prior written permission.
-THIS SOFTWARE IS PROVIDED \`\`AS IS\'\' AND WITHOUT ANY EXPRESS OR
+THIS SOFTWARE IS PROVIDED \`\`AS IS'' AND WITHOUT ANY EXPRESS OR
 IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED
 WARRANTIES OF MERCHANTIBILITY AND FITNESS FOR A PARTICULAR
 PURPOSE.
 .ad
 .fi

-.SH "Options\' Cross Key"
+.SH "Options' Cross Key"

 Here is a list of options alphabetized by long option, to help you find
 the corresponding short option.

-- System Information
Debian Release: 3.0
Architecture: powerpc
Kernel: Linux catalonia 2.4.16-newpmac #1 Mon Jan 7 20:51:25 EST 2002 ppc
Locale: LANG=C, LC_CTYPE=C

Versions of packages indent depends on:
ii  libc6                         2.2.5-1    GNU C Library: Shared libraries an