texi2html-cvs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Texi2html-cvs] texi2html ChangeLog texi2html.init Tests/German...


From: Patrice Dumas
Subject: [Texi2html-cvs] texi2html ChangeLog texi2html.init Tests/German...
Date: Wed, 03 Oct 2007 09:35:02 +0000

CVSROOT:        /cvsroot/texi2html
Module name:    texi2html
Changes by:     Patrice Dumas <pertusus>        07/10/03 09:34:58

Modified files:
        .              : ChangeLog texi2html.init 
        Tests/GermanNodeTest_res: nodetest.html 
                                  nodetest_for_makeinfo.html 
        Tests/ccvs_res : cvs_1.html cvs_10.html cvs_12.html cvs_13.html 
                         cvs_16.html cvs_17.html cvs_18.html cvs_19.html 
                         cvs_2.html cvs_21.html cvs_22.html cvs_23.html 
                         cvs_25.html cvs_27.html cvs_4.html cvs_5.html 
                         cvs_7.html cvs_8.html cvs_toc.html 
        Tests/documentlanguage_res: multi_lang.html 
        Tests/floats_res: float.html 
        Tests/formatting_res: 
                              
_0021_005f_0022_0023_0024_0025_0026_0027_0028_0029_002a_002b_002d_002e_002f_003b_003c_003d_003e_003f_005b_005c_005d_005e_005f_0060_007c_007e.html
 
                              chapter_test_refs.html 
                              chapter_test_refs_1.html clean.html 
                              comments.html comments_redefined.html 
                              exotic_formatting.html formatting.html 
                              fr_formatting.html 
                              icons_fr_formatting.html imbrications.html 
                              no_unicode_nodetest.html 
                              no_unicode_nodetest_latin1.html 
                              no_unicode_nodetest_utf8.html 
                              node_test_refs.html nodetest_2.html 
                              nodetest_latin1.html nodetest_utf8.html 
                              other-nodes.html quotes.html 
                              test_refs.html umlaut.html 
                              verbatim_html.html 
                              weird_quotes_formatting.html 
        Tests/htmlxref-only_mono_res: 
                                      
_0021_005f_0022_0023_0024_0025_0026_0027_0028_0029_002a_002b_002d_002e_002f_003b_003c_003d_003e_003f_005b_005c_005d_005e_005f_0060_007c_007e.html
 
                                      no_split_test_refs.html 
                                      other-nodes.html test_refs.html 
        Tests/htmlxref-only_split_res: 
                                       
_0021_005f_0022_0023_0024_0025_0026_0027_0028_0029_002a_002b_002d_002e_002f_003b_003c_003d_003e_003f_005b_005c_005d_005e_005f_0060_007c_007e.html
 
                                       no_split_test_refs.html 
                                       other-nodes.html test_refs.html 
        Tests/htmlxref_res: 
                            
_0021_005f_0022_0023_0024_0025_0026_0027_0028_0029_002a_002b_002d_002e_002f_003b_003c_003d_003e_003f_005b_005c_005d_005e_005f_0060_007c_007e.html
 
                            no_split_test_refs.html other-nodes.html 
                            test_refs.html 
        Tests/macros_res: bib-example.html macros.html simple_macro.html 
        Tests/node_translit_no_unicode_res: a.html 
        Tests/node_translit_no_unidecode_res: a.html 
        Tests/node_translit_res: a.html 
        Tests/node_utf8_translit_no_unidecode_res: a.html 
        Tests/node_utf8_translit_res: a.html 
        Tests/nodes_texinfo_res: A4-Paper.html Abstract-Objects.html 
                                 Batch-Formatting.html 
                                 Beginning-a-File.html Breaks.html 
                                 Combining-Indices.html 
                                 Command-List.html Command-Syntax.html 
                                 Command-and-Variable-Index.html 
                                 Compile_002dCommand.html Contents.html 
                                 Conventions.html 
                                 Cross-Reference-Commands.html 
                                 Cross-References.html 
                                 Custom-Headings.html 
                                 Debugging-with-Info.html 
                                 Def-Cmd-Template.html 
                                 Defining-Macros.html 
                                 Defining-New-Texinfo-Commands.html 
                                 Definition-Commands.html 
                                 Directory-File.html 
                                 Document-Permissions.html 
                                 Emacs-Editing.html 
                                 Ending-a-Sentence.html Error-Glyph.html 
                                 First-Node.html Footnote-Commands.html 
                                 Footnote-Styles.html 
                                 Format-with-tex_002ftexindex.html 
                                 Formatting-Commands.html 
                                 Functions-Commands.html 
                                 GNU-Free-Documentation-License.html 
                                 GNU-Sample-Texts.html Hardcopy.html 
                                 History.html Images.html 
                                 Include-File-Requirements.html 
                                 Include-Files-Evolution.html 
                                 Indexing-Commands.html Info-Files.html 
                                 Inserting-Accents.html 
                                 Inserting-Space.html Inserting.html 
                                 Installing-Dir-Entries.html 
                                 Invoking-install_002dinfo.html 
                                 Line-Breaks.html Macro-Details.html 
                                 Menu-Parts.html Minimum.html 
                                 Multitable-Column-Widths.html 
                                 Multitable-Rows.html 
                                 Node-Menu-Illustration.html 
                                 Node-Names.html 
                                 Other-Info-Directories.html 
                                 Other-Info-Files.html 
                                 Other-Updating-Commands.html 
                                 Overfull-hboxes.html PDF-Output.html 
                                 Pointer-Validation.html 
                                 Preparing-for-TeX.html 
                                 Print-with-lpr.html Printed-Books.html 
                                 Quotations-and-Examples.html 
                                 Raise_002flower-sections.html 
                                 Reporting-Bugs.html 
                                 Requirements-Summary.html 
                                 Running-Info_002dValidate.html 
                                 Sample-Function-Definition.html 
                                 Short-Sample.html 
                                 Showing-the-Structure.html 
                                 Six-Parts.html Smallcaps.html 
                                 Software-Copying-Permissions.html 
                                 Structuring.html TeX-and-copyright.html 
                                 Texinfo-Mode-Printing.html 
                                 Texinfo-Mode-Summary.html 
                                 Texinfo-Mode.html The-Top-Node.html 
                                 Three-Arguments.html Tips.html 
                                 Titlepage-_0026-Copyright-Page.html 
                                 Top-Node-Naming.html 
                                 Two_002dcolumn-Tables.html 
                                 Typed-Functions.html 
                                 Updating-Nodes-and-Menus.html 
                                 Updating-Requirements.html 
                                 Using-Include-Files.html 
                                 Using-Info_002dvalidate.html 
                                 Using-Texinfo.html Using-occur.html 
                                 Using-texinfo_002dshow_002dstructure.html 
                                 Variables-Commands.html 
                                 Writing-a-Node.html 
                                 _002d-and-hyphenation.html acronym.html 
                                 alias.html anchor.html command.html 
                                 copying.html copyright-symbol.html 
                                 deffnx.html definfoenclose.html 
                                 documentlanguage.html dots.html 
                                 emph-_0026-strong.html exdent.html 
                                 ifset-ifclear.html insertcopying.html 
                                 itemize.html key.html 
                                 makeinfo-Pointer-Creation.html 
                                 makeinfo-html.html 
                                 makeinfo-in-Emacs.html 
                                 makeinfo-top-command.html 
                                 makeinfo-top.html math.html node.html 
                                 noindent.html pounds.html pxref.html 
                                 ref.html samp.html 
                                 setchapternewpage.html 
                                 subsubsection.html syncodeindex.html 
                                 synindex.html tex.html texinfo.html 
                                 texinfo_002dmultiple_002dfiles_002dupdate.html 
                                 texinfo_285.html texinfo_286.html 
                                 texinfo_288.html texinfo_289.html 
                                 texinfo_290.html texinfo_291.html 
                                 texinfo_292.html texinfo_fot.html 
                                 texinfo_toc.html titlepage.html 
                                 uref.html url.html value-Example.html 
                                 verb.html 
        Tests/sectionning_res: novalidate.html novalidate_split_0.html 
        Tests/tar_res  : tar.html 
        Tests/texi2html_res: texi2html.html 
        Tests/texinfo_res: Copying-This-Manual.html Cursor-Commands.html 
                           Custom-Key-Bindings.html Invoking-Info.html 
                           Miscellaneous-Commands.html 
                           Node-Commands.html Printing-Nodes.html 
                           Searching-Commands.html Variables.html 
                           Window-Commands.html Xref-Commands.html 
                           info-stnd.html info-stnd_fot.html 
                           texinfo.html texinfo_10.html texinfo_11.html 
                           texinfo_12.html texinfo_13.html 
                           texinfo_14.html texinfo_15.html 
                           texinfo_16.html texinfo_17.html 
                           texinfo_18.html texinfo_19.html 
                           texinfo_2.html texinfo_20.html 
                           texinfo_21.html texinfo_22.html 
                           texinfo_23.html texinfo_24.html 
                           texinfo_25.html texinfo_26.html 
                           texinfo_27.html texinfo_29.html 
                           texinfo_3.html texinfo_31.html 
                           texinfo_32.html texinfo_33.html 
                           texinfo_34.html texinfo_36.html 
                           texinfo_37.html texinfo_38.html 
                           texinfo_39.html texinfo_4.html 
                           texinfo_40.html texinfo_5.html texinfo_6.html 
                           texinfo_7.html texinfo_8.html texinfo_9.html 
                           texinfo_fot.html texinfo_toc.html 
        Tests/viper_monolithic_res: viper.html 
        Tests/viper_res: viper_0.html viper_2.html viper_3.html 
                         viper_4.html viper_5.html viper_6.html 
        Tests/xemacs_frame_res: xemacs.html xemacs_1.html xemacs_11.html 
                                xemacs_12.html xemacs_13.html 
                                xemacs_14.html xemacs_15.html 
                                xemacs_16.html xemacs_17.html 
                                xemacs_18.html xemacs_19.html 
                                xemacs_2.html xemacs_20.html 
                                xemacs_21.html xemacs_22.html 
                                xemacs_23.html xemacs_24.html 
                                xemacs_25.html xemacs_26.html 
                                xemacs_28.html xemacs_29.html 
                                xemacs_3.html xemacs_30.html 
                                xemacs_31.html xemacs_32.html 
                                xemacs_4.html xemacs_5.html 
                                xemacs_6.html xemacs_7.html 
                                xemacs_8.html xemacs_9.html 
                                xemacs_frame.html xemacs_toc.html 
        Tests/xemacs_res: xemacs.html xemacs_1.html xemacs_11.html 
                          xemacs_12.html xemacs_13.html xemacs_14.html 
                          xemacs_15.html xemacs_16.html xemacs_17.html 
                          xemacs_18.html xemacs_19.html xemacs_2.html 
                          xemacs_20.html xemacs_21.html xemacs_22.html 
                          xemacs_23.html xemacs_24.html xemacs_25.html 
                          xemacs_26.html xemacs_28.html xemacs_29.html 
                          xemacs_3.html xemacs_30.html xemacs_31.html 
                          xemacs_32.html xemacs_4.html xemacs_5.html 
                          xemacs_6.html xemacs_7.html xemacs_8.html 
                          xemacs_9.html xemacs_toc.html 
        doc            : texi2html.html 

Log message:
                * texi2html.init: use entities for simple quotes in normal text.

CVSWeb URLs:
http://cvs.savannah.gnu.org/viewcvs/texi2html/ChangeLog?cvsroot=texi2html&r1=1.275&r2=1.276
http://cvs.savannah.gnu.org/viewcvs/texi2html/texi2html.init?cvsroot=texi2html&r1=1.124&r2=1.125
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/GermanNodeTest_res/nodetest.html?cvsroot=texi2html&r1=1.45&r2=1.46
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/GermanNodeTest_res/nodetest_for_makeinfo.html?cvsroot=texi2html&r1=1.29&r2=1.30
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/ccvs_res/cvs_1.html?cvsroot=texi2html&r1=1.28&r2=1.29
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/ccvs_res/cvs_10.html?cvsroot=texi2html&r1=1.29&r2=1.30
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/ccvs_res/cvs_12.html?cvsroot=texi2html&r1=1.34&r2=1.35
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/ccvs_res/cvs_13.html?cvsroot=texi2html&r1=1.24&r2=1.25
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/ccvs_res/cvs_16.html?cvsroot=texi2html&r1=1.36&r2=1.37
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/ccvs_res/cvs_17.html?cvsroot=texi2html&r1=1.31&r2=1.32
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/ccvs_res/cvs_18.html?cvsroot=texi2html&r1=1.29&r2=1.30
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/ccvs_res/cvs_19.html?cvsroot=texi2html&r1=1.24&r2=1.25
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/ccvs_res/cvs_2.html?cvsroot=texi2html&r1=1.28&r2=1.29
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/ccvs_res/cvs_21.html?cvsroot=texi2html&r1=1.27&r2=1.28
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/ccvs_res/cvs_22.html?cvsroot=texi2html&r1=1.22&r2=1.23
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/ccvs_res/cvs_23.html?cvsroot=texi2html&r1=1.23&r2=1.24
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/ccvs_res/cvs_25.html?cvsroot=texi2html&r1=1.20&r2=1.21
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/ccvs_res/cvs_27.html?cvsroot=texi2html&r1=1.18&r2=1.19
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/ccvs_res/cvs_4.html?cvsroot=texi2html&r1=1.26&r2=1.27
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/ccvs_res/cvs_5.html?cvsroot=texi2html&r1=1.33&r2=1.34
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/ccvs_res/cvs_7.html?cvsroot=texi2html&r1=1.28&r2=1.29
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/ccvs_res/cvs_8.html?cvsroot=texi2html&r1=1.25&r2=1.26
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/ccvs_res/cvs_toc.html?cvsroot=texi2html&r1=1.23&r2=1.24
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/documentlanguage_res/multi_lang.html?cvsroot=texi2html&r1=1.1&r2=1.2
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/floats_res/float.html?cvsroot=texi2html&r1=1.13&r2=1.14
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/formatting_res/_0021_005f_0022_0023_0024_0025_0026_0027_0028_0029_002a_002b_002d_002e_002f_003b_003c_003d_003e_003f_005b_005c_005d_005e_005f_0060_007c_007e.html?cvsroot=texi2html&r1=1.9&r2=1.10
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/formatting_res/chapter_test_refs.html?cvsroot=texi2html&r1=1.10&r2=1.11
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/formatting_res/chapter_test_refs_1.html?cvsroot=texi2html&r1=1.8&r2=1.9
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/formatting_res/clean.html?cvsroot=texi2html&r1=1.28&r2=1.29
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/formatting_res/comments.html?cvsroot=texi2html&r1=1.25&r2=1.26
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/formatting_res/comments_redefined.html?cvsroot=texi2html&r1=1.6&r2=1.7
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/formatting_res/exotic_formatting.html?cvsroot=texi2html&r1=1.63&r2=1.64
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/formatting_res/formatting.html?cvsroot=texi2html&r1=1.64&r2=1.65
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/formatting_res/fr_formatting.html?cvsroot=texi2html&r1=1.57&r2=1.58
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/formatting_res/icons_fr_formatting.html?cvsroot=texi2html&r1=1.19&r2=1.20
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/formatting_res/imbrications.html?cvsroot=texi2html&r1=1.35&r2=1.36
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/formatting_res/no_unicode_nodetest.html?cvsroot=texi2html&r1=1.11&r2=1.12
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/formatting_res/no_unicode_nodetest_latin1.html?cvsroot=texi2html&r1=1.9&r2=1.10
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/formatting_res/no_unicode_nodetest_utf8.html?cvsroot=texi2html&r1=1.10&r2=1.11
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/formatting_res/node_test_refs.html?cvsroot=texi2html&r1=1.2&r2=1.3
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/formatting_res/nodetest_2.html?cvsroot=texi2html&r1=1.18&r2=1.19
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/formatting_res/nodetest_latin1.html?cvsroot=texi2html&r1=1.13&r2=1.14
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/formatting_res/nodetest_utf8.html?cvsroot=texi2html&r1=1.13&r2=1.14
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/formatting_res/other-nodes.html?cvsroot=texi2html&r1=1.9&r2=1.10
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/formatting_res/quotes.html?cvsroot=texi2html&r1=1.1&r2=1.2
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/formatting_res/test_refs.html?cvsroot=texi2html&r1=1.12&r2=1.13
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/formatting_res/umlaut.html?cvsroot=texi2html&r1=1.16&r2=1.17
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/formatting_res/verbatim_html.html?cvsroot=texi2html&r1=1.43&r2=1.44
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/formatting_res/weird_quotes_formatting.html?cvsroot=texi2html&r1=1.12&r2=1.13
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/htmlxref-only_mono_res/_0021_005f_0022_0023_0024_0025_0026_0027_0028_0029_002a_002b_002d_002e_002f_003b_003c_003d_003e_003f_005b_005c_005d_005e_005f_0060_007c_007e.html?cvsroot=texi2html&r1=1.2&r2=1.3
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/htmlxref-only_mono_res/no_split_test_refs.html?cvsroot=texi2html&r1=1.3&r2=1.4
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/htmlxref-only_mono_res/other-nodes.html?cvsroot=texi2html&r1=1.2&r2=1.3
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/htmlxref-only_mono_res/test_refs.html?cvsroot=texi2html&r1=1.2&r2=1.3
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/htmlxref-only_split_res/_0021_005f_0022_0023_0024_0025_0026_0027_0028_0029_002a_002b_002d_002e_002f_003b_003c_003d_003e_003f_005b_005c_005d_005e_005f_0060_007c_007e.html?cvsroot=texi2html&r1=1.2&r2=1.3
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/htmlxref-only_split_res/no_split_test_refs.html?cvsroot=texi2html&r1=1.3&r2=1.4
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/htmlxref-only_split_res/other-nodes.html?cvsroot=texi2html&r1=1.2&r2=1.3
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/htmlxref-only_split_res/test_refs.html?cvsroot=texi2html&r1=1.2&r2=1.3
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/htmlxref_res/_0021_005f_0022_0023_0024_0025_0026_0027_0028_0029_002a_002b_002d_002e_002f_003b_003c_003d_003e_003f_005b_005c_005d_005e_005f_0060_007c_007e.html?cvsroot=texi2html&r1=1.2&r2=1.3
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/htmlxref_res/no_split_test_refs.html?cvsroot=texi2html&r1=1.4&r2=1.5
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/htmlxref_res/other-nodes.html?cvsroot=texi2html&r1=1.2&r2=1.3
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/htmlxref_res/test_refs.html?cvsroot=texi2html&r1=1.2&r2=1.3
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/macros_res/bib-example.html?cvsroot=texi2html&r1=1.5&r2=1.6
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/macros_res/macros.html?cvsroot=texi2html&r1=1.29&r2=1.30
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/macros_res/simple_macro.html?cvsroot=texi2html&r1=1.30&r2=1.31
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/node_translit_no_unicode_res/a.html?cvsroot=texi2html&r1=1.6&r2=1.7
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/node_translit_no_unidecode_res/a.html?cvsroot=texi2html&r1=1.6&r2=1.7
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/node_translit_res/a.html?cvsroot=texi2html&r1=1.6&r2=1.7
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/node_utf8_translit_no_unidecode_res/a.html?cvsroot=texi2html&r1=1.4&r2=1.5
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/node_utf8_translit_res/a.html?cvsroot=texi2html&r1=1.4&r2=1.5
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/A4-Paper.html?cvsroot=texi2html&r1=1.18&r2=1.19
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/Abstract-Objects.html?cvsroot=texi2html&r1=1.25&r2=1.26
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/Batch-Formatting.html?cvsroot=texi2html&r1=1.21&r2=1.22
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/Beginning-a-File.html?cvsroot=texi2html&r1=1.19&r2=1.20
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/Breaks.html?cvsroot=texi2html&r1=1.24&r2=1.25
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/Combining-Indices.html?cvsroot=texi2html&r1=1.19&r2=1.20
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/Command-List.html?cvsroot=texi2html&r1=1.26&r2=1.27
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/Command-Syntax.html?cvsroot=texi2html&r1=1.23&r2=1.24
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/Command-and-Variable-Index.html?cvsroot=texi2html&r1=1.26&r2=1.27
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/Compile_002dCommand.html?cvsroot=texi2html&r1=1.10&r2=1.11
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/Contents.html?cvsroot=texi2html&r1=1.22&r2=1.23
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/Conventions.html?cvsroot=texi2html&r1=1.26&r2=1.27
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/Cross-Reference-Commands.html?cvsroot=texi2html&r1=1.24&r2=1.25
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/Cross-References.html?cvsroot=texi2html&r1=1.24&r2=1.25
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/Custom-Headings.html?cvsroot=texi2html&r1=1.26&r2=1.27
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/Debugging-with-Info.html?cvsroot=texi2html&r1=1.24&r2=1.25
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/Def-Cmd-Template.html?cvsroot=texi2html&r1=1.22&r2=1.23
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/Defining-Macros.html?cvsroot=texi2html&r1=1.22&r2=1.23
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/Defining-New-Texinfo-Commands.html?cvsroot=texi2html&r1=1.24&r2=1.25
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/Definition-Commands.html?cvsroot=texi2html&r1=1.20&r2=1.21
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/Directory-File.html?cvsroot=texi2html&r1=1.24&r2=1.25
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/Document-Permissions.html?cvsroot=texi2html&r1=1.19&r2=1.20
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/Emacs-Editing.html?cvsroot=texi2html&r1=1.20&r2=1.21
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/Ending-a-Sentence.html?cvsroot=texi2html&r1=1.20&r2=1.21
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/Error-Glyph.html?cvsroot=texi2html&r1=1.22&r2=1.23
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/First-Node.html?cvsroot=texi2html&r1=1.24&r2=1.25
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/Footnote-Commands.html?cvsroot=texi2html&r1=1.22&r2=1.23
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/Footnote-Styles.html?cvsroot=texi2html&r1=1.27&r2=1.28
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/Format-with-tex_002ftexindex.html?cvsroot=texi2html&r1=1.11&r2=1.12
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/Formatting-Commands.html?cvsroot=texi2html&r1=1.25&r2=1.26
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/Functions-Commands.html?cvsroot=texi2html&r1=1.26&r2=1.27
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/GNU-Free-Documentation-License.html?cvsroot=texi2html&r1=1.23&r2=1.24
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/GNU-Sample-Texts.html?cvsroot=texi2html&r1=1.74&r2=1.75
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/Hardcopy.html?cvsroot=texi2html&r1=1.19&r2=1.20
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/History.html?cvsroot=texi2html&r1=1.20&r2=1.21
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/Images.html?cvsroot=texi2html&r1=1.24&r2=1.25
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/Include-File-Requirements.html?cvsroot=texi2html&r1=1.18&r2=1.19
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/Include-Files-Evolution.html?cvsroot=texi2html&r1=1.19&r2=1.20
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/Indexing-Commands.html?cvsroot=texi2html&r1=1.23&r2=1.24
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/Info-Files.html?cvsroot=texi2html&r1=1.23&r2=1.24
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/Inserting-Accents.html?cvsroot=texi2html&r1=1.19&r2=1.20
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/Inserting-Space.html?cvsroot=texi2html&r1=1.19&r2=1.20
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/Inserting.html?cvsroot=texi2html&r1=1.25&r2=1.26
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/Installing-Dir-Entries.html?cvsroot=texi2html&r1=1.23&r2=1.24
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/Invoking-install_002dinfo.html?cvsroot=texi2html&r1=1.11&r2=1.12
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/Line-Breaks.html?cvsroot=texi2html&r1=1.20&r2=1.21
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/Macro-Details.html?cvsroot=texi2html&r1=1.23&r2=1.24
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/Menu-Parts.html?cvsroot=texi2html&r1=1.22&r2=1.23
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/Minimum.html?cvsroot=texi2html&r1=1.24&r2=1.25
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/Multitable-Column-Widths.html?cvsroot=texi2html&r1=1.21&r2=1.22
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/Multitable-Rows.html?cvsroot=texi2html&r1=1.20&r2=1.21
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/Node-Menu-Illustration.html?cvsroot=texi2html&r1=1.21&r2=1.22
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/Node-Names.html?cvsroot=texi2html&r1=1.21&r2=1.22
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/Other-Info-Directories.html?cvsroot=texi2html&r1=1.25&r2=1.26
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/Other-Info-Files.html?cvsroot=texi2html&r1=1.22&r2=1.23
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/Other-Updating-Commands.html?cvsroot=texi2html&r1=1.22&r2=1.23
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/Overfull-hboxes.html?cvsroot=texi2html&r1=1.22&r2=1.23
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/PDF-Output.html?cvsroot=texi2html&r1=1.21&r2=1.22
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/Pointer-Validation.html?cvsroot=texi2html&r1=1.24&r2=1.25
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/Preparing-for-TeX.html?cvsroot=texi2html&r1=1.23&r2=1.24
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/Print-with-lpr.html?cvsroot=texi2html&r1=1.23&r2=1.24
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/Printed-Books.html?cvsroot=texi2html&r1=1.22&r2=1.23
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/Quotations-and-Examples.html?cvsroot=texi2html&r1=1.21&r2=1.22
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/Raise_002flower-sections.html?cvsroot=texi2html&r1=1.9&r2=1.10
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/Reporting-Bugs.html?cvsroot=texi2html&r1=1.21&r2=1.22
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/Requirements-Summary.html?cvsroot=texi2html&r1=1.20&r2=1.21
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/Running-Info_002dValidate.html?cvsroot=texi2html&r1=1.8&r2=1.9
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/Sample-Function-Definition.html?cvsroot=texi2html&r1=1.21&r2=1.22
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/Short-Sample.html?cvsroot=texi2html&r1=1.23&r2=1.24
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/Showing-the-Structure.html?cvsroot=texi2html&r1=1.22&r2=1.23
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/Six-Parts.html?cvsroot=texi2html&r1=1.20&r2=1.21
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/Smallcaps.html?cvsroot=texi2html&r1=1.22&r2=1.23
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/Software-Copying-Permissions.html?cvsroot=texi2html&r1=1.19&r2=1.20
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/Structuring.html?cvsroot=texi2html&r1=1.22&r2=1.23
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/TeX-and-copyright.html?cvsroot=texi2html&r1=1.22&r2=1.23
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/Texinfo-Mode-Printing.html?cvsroot=texi2html&r1=1.24&r2=1.25
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/Texinfo-Mode-Summary.html?cvsroot=texi2html&r1=1.23&r2=1.24
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/Texinfo-Mode.html?cvsroot=texi2html&r1=1.23&r2=1.24
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/The-Top-Node.html?cvsroot=texi2html&r1=1.19&r2=1.20
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/Three-Arguments.html?cvsroot=texi2html&r1=1.21&r2=1.22
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/Tips.html?cvsroot=texi2html&r1=1.27&r2=1.28
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/Titlepage-_0026-Copyright-Page.html?cvsroot=texi2html&r1=1.10&r2=1.11
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/Top-Node-Naming.html?cvsroot=texi2html&r1=1.23&r2=1.24
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/Two_002dcolumn-Tables.html?cvsroot=texi2html&r1=1.11&r2=1.12
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/Typed-Functions.html?cvsroot=texi2html&r1=1.26&r2=1.27
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/Updating-Nodes-and-Menus.html?cvsroot=texi2html&r1=1.27&r2=1.28
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/Updating-Requirements.html?cvsroot=texi2html&r1=1.24&r2=1.25
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/Using-Include-Files.html?cvsroot=texi2html&r1=1.21&r2=1.22
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/Using-Info_002dvalidate.html?cvsroot=texi2html&r1=1.11&r2=1.12
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/Using-Texinfo.html?cvsroot=texi2html&r1=1.21&r2=1.22
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/Using-occur.html?cvsroot=texi2html&r1=1.21&r2=1.22
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/Using-texinfo_002dshow_002dstructure.html?cvsroot=texi2html&r1=1.11&r2=1.12
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/Variables-Commands.html?cvsroot=texi2html&r1=1.26&r2=1.27
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/Writing-a-Node.html?cvsroot=texi2html&r1=1.22&r2=1.23
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/_002d-and-hyphenation.html?cvsroot=texi2html&r1=1.12&r2=1.13
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/acronym.html?cvsroot=texi2html&r1=1.20&r2=1.21
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/alias.html?cvsroot=texi2html&r1=1.20&r2=1.21
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/anchor.html?cvsroot=texi2html&r1=1.20&r2=1.21
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/command.html?cvsroot=texi2html&r1=1.21&r2=1.22
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/copying.html?cvsroot=texi2html&r1=1.22&r2=1.23
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/copyright-symbol.html?cvsroot=texi2html&r1=1.22&r2=1.23
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/deffnx.html?cvsroot=texi2html&r1=1.20&r2=1.21
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/definfoenclose.html?cvsroot=texi2html&r1=1.20&r2=1.21
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/documentlanguage.html?cvsroot=texi2html&r1=1.21&r2=1.22
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/dots.html?cvsroot=texi2html&r1=1.21&r2=1.22
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/emph-_0026-strong.html?cvsroot=texi2html&r1=1.11&r2=1.12
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/exdent.html?cvsroot=texi2html&r1=1.20&r2=1.21
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/ifset-ifclear.html?cvsroot=texi2html&r1=1.21&r2=1.22
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/insertcopying.html?cvsroot=texi2html&r1=1.19&r2=1.20
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/itemize.html?cvsroot=texi2html&r1=1.27&r2=1.28
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/key.html?cvsroot=texi2html&r1=1.24&r2=1.25
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/makeinfo-Pointer-Creation.html?cvsroot=texi2html&r1=1.18&r2=1.19
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/makeinfo-html.html?cvsroot=texi2html&r1=1.20&r2=1.21
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/makeinfo-in-Emacs.html?cvsroot=texi2html&r1=1.25&r2=1.26
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/makeinfo-top-command.html?cvsroot=texi2html&r1=1.19&r2=1.20
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/makeinfo-top.html?cvsroot=texi2html&r1=1.20&r2=1.21
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/math.html?cvsroot=texi2html&r1=1.21&r2=1.22
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/node.html?cvsroot=texi2html&r1=1.21&r2=1.22
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/noindent.html?cvsroot=texi2html&r1=1.20&r2=1.21
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/pounds.html?cvsroot=texi2html&r1=1.21&r2=1.22
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/pxref.html?cvsroot=texi2html&r1=1.23&r2=1.24
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/ref.html?cvsroot=texi2html&r1=1.20&r2=1.21
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/samp.html?cvsroot=texi2html&r1=1.22&r2=1.23
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/setchapternewpage.html?cvsroot=texi2html&r1=1.23&r2=1.24
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/subsubsection.html?cvsroot=texi2html&r1=1.22&r2=1.23
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/syncodeindex.html?cvsroot=texi2html&r1=1.23&r2=1.24
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/synindex.html?cvsroot=texi2html&r1=1.18&r2=1.19
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/tex.html?cvsroot=texi2html&r1=1.21&r2=1.22
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/texinfo.html?cvsroot=texi2html&r1=1.3&r2=1.4
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/texinfo_002dmultiple_002dfiles_002dupdate.html?cvsroot=texi2html&r1=1.9&r2=1.10
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/texinfo_285.html?cvsroot=texi2html&r1=1.25&r2=1.26
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/texinfo_286.html?cvsroot=texi2html&r1=1.19&r2=1.20
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/texinfo_288.html?cvsroot=texi2html&r1=1.75&r2=1.76
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/texinfo_289.html?cvsroot=texi2html&r1=1.21&r2=1.22
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/texinfo_290.html?cvsroot=texi2html&r1=1.24&r2=1.25
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/texinfo_291.html?cvsroot=texi2html&r1=1.25&r2=1.26
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/texinfo_292.html?cvsroot=texi2html&r1=1.74&r2=1.75
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/texinfo_fot.html?cvsroot=texi2html&r1=1.19&r2=1.20
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/texinfo_toc.html?cvsroot=texi2html&r1=1.22&r2=1.23
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/titlepage.html?cvsroot=texi2html&r1=1.18&r2=1.19
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/uref.html?cvsroot=texi2html&r1=1.22&r2=1.23
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/url.html?cvsroot=texi2html&r1=1.19&r2=1.20
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/value-Example.html?cvsroot=texi2html&r1=1.23&r2=1.24
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/nodes_texinfo_res/verb.html?cvsroot=texi2html&r1=1.19&r2=1.20
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/sectionning_res/novalidate.html?cvsroot=texi2html&r1=1.14&r2=1.15
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/sectionning_res/novalidate_split_0.html?cvsroot=texi2html&r1=1.2&r2=1.3
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/tar_res/tar.html?cvsroot=texi2html&r1=1.4&r2=1.5
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/texi2html_res/texi2html.html?cvsroot=texi2html&r1=1.30&r2=1.31
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/texinfo_res/Copying-This-Manual.html?cvsroot=texi2html&r1=1.9&r2=1.10
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/texinfo_res/Cursor-Commands.html?cvsroot=texi2html&r1=1.9&r2=1.10
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/texinfo_res/Custom-Key-Bindings.html?cvsroot=texi2html&r1=1.9&r2=1.10
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/texinfo_res/Invoking-Info.html?cvsroot=texi2html&r1=1.9&r2=1.10
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/texinfo_res/Miscellaneous-Commands.html?cvsroot=texi2html&r1=1.9&r2=1.10
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/texinfo_res/Node-Commands.html?cvsroot=texi2html&r1=1.9&r2=1.10
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/texinfo_res/Printing-Nodes.html?cvsroot=texi2html&r1=1.9&r2=1.10
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/texinfo_res/Searching-Commands.html?cvsroot=texi2html&r1=1.9&r2=1.10
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/texinfo_res/Variables.html?cvsroot=texi2html&r1=1.9&r2=1.10
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/texinfo_res/Window-Commands.html?cvsroot=texi2html&r1=1.9&r2=1.10
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/texinfo_res/Xref-Commands.html?cvsroot=texi2html&r1=1.9&r2=1.10
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/texinfo_res/info-stnd.html?cvsroot=texi2html&r1=1.23&r2=1.24
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/texinfo_res/info-stnd_fot.html?cvsroot=texi2html&r1=1.20&r2=1.21
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/texinfo_res/texinfo.html?cvsroot=texi2html&r1=1.30&r2=1.31
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/texinfo_res/texinfo_10.html?cvsroot=texi2html&r1=1.31&r2=1.32
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/texinfo_res/texinfo_11.html?cvsroot=texi2html&r1=1.28&r2=1.29
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/texinfo_res/texinfo_12.html?cvsroot=texi2html&r1=1.33&r2=1.34
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/texinfo_res/texinfo_13.html?cvsroot=texi2html&r1=1.27&r2=1.28
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/texinfo_res/texinfo_14.html?cvsroot=texi2html&r1=1.31&r2=1.32
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/texinfo_res/texinfo_15.html?cvsroot=texi2html&r1=1.29&r2=1.30
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/texinfo_res/texinfo_16.html?cvsroot=texi2html&r1=1.28&r2=1.29
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/texinfo_res/texinfo_17.html?cvsroot=texi2html&r1=1.29&r2=1.30
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/texinfo_res/texinfo_18.html?cvsroot=texi2html&r1=1.23&r2=1.24
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/texinfo_res/texinfo_19.html?cvsroot=texi2html&r1=1.27&r2=1.28
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/texinfo_res/texinfo_2.html?cvsroot=texi2html&r1=1.31&r2=1.32
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/texinfo_res/texinfo_20.html?cvsroot=texi2html&r1=1.31&r2=1.32
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/texinfo_res/texinfo_21.html?cvsroot=texi2html&r1=1.30&r2=1.31
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/texinfo_res/texinfo_22.html?cvsroot=texi2html&r1=1.26&r2=1.27
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/texinfo_res/texinfo_23.html?cvsroot=texi2html&r1=1.27&r2=1.28
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/texinfo_res/texinfo_24.html?cvsroot=texi2html&r1=1.78&r2=1.79
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/texinfo_res/texinfo_25.html?cvsroot=texi2html&r1=1.30&r2=1.31
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/texinfo_res/texinfo_26.html?cvsroot=texi2html&r1=1.30&r2=1.31
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/texinfo_res/texinfo_27.html?cvsroot=texi2html&r1=1.31&r2=1.32
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/texinfo_res/texinfo_29.html?cvsroot=texi2html&r1=1.23&r2=1.24
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/texinfo_res/texinfo_3.html?cvsroot=texi2html&r1=1.32&r2=1.33
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/texinfo_res/texinfo_31.html?cvsroot=texi2html&r1=1.25&r2=1.26
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/texinfo_res/texinfo_32.html?cvsroot=texi2html&r1=1.28&r2=1.29
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/texinfo_res/texinfo_33.html?cvsroot=texi2html&r1=1.26&r2=1.27
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/texinfo_res/texinfo_34.html?cvsroot=texi2html&r1=1.18&r2=1.19
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/texinfo_res/texinfo_36.html?cvsroot=texi2html&r1=1.79&r2=1.80
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/texinfo_res/texinfo_37.html?cvsroot=texi2html&r1=1.21&r2=1.22
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/texinfo_res/texinfo_38.html?cvsroot=texi2html&r1=1.24&r2=1.25
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/texinfo_res/texinfo_39.html?cvsroot=texi2html&r1=1.25&r2=1.26
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/texinfo_res/texinfo_4.html?cvsroot=texi2html&r1=1.29&r2=1.30
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/texinfo_res/texinfo_40.html?cvsroot=texi2html&r1=1.78&r2=1.79
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/texinfo_res/texinfo_5.html?cvsroot=texi2html&r1=1.25&r2=1.26
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/texinfo_res/texinfo_6.html?cvsroot=texi2html&r1=1.28&r2=1.29
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/texinfo_res/texinfo_7.html?cvsroot=texi2html&r1=1.30&r2=1.31
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/texinfo_res/texinfo_8.html?cvsroot=texi2html&r1=1.28&r2=1.29
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/texinfo_res/texinfo_9.html?cvsroot=texi2html&r1=1.31&r2=1.32
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/texinfo_res/texinfo_fot.html?cvsroot=texi2html&r1=1.18&r2=1.19
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/texinfo_res/texinfo_toc.html?cvsroot=texi2html&r1=1.21&r2=1.22
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/viper_monolithic_res/viper.html?cvsroot=texi2html&r1=1.38&r2=1.39
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/viper_res/viper_0.html?cvsroot=texi2html&r1=1.16&r2=1.17
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/viper_res/viper_2.html?cvsroot=texi2html&r1=1.29&r2=1.30
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/viper_res/viper_3.html?cvsroot=texi2html&r1=1.28&r2=1.29
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/viper_res/viper_4.html?cvsroot=texi2html&r1=1.28&r2=1.29
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/viper_res/viper_5.html?cvsroot=texi2html&r1=1.27&r2=1.28
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/viper_res/viper_6.html?cvsroot=texi2html&r1=1.17&r2=1.18
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/xemacs_frame_res/xemacs.html?cvsroot=texi2html&r1=1.22&r2=1.23
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/xemacs_frame_res/xemacs_1.html?cvsroot=texi2html&r1=1.21&r2=1.22
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/xemacs_frame_res/xemacs_11.html?cvsroot=texi2html&r1=1.24&r2=1.25
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/xemacs_frame_res/xemacs_12.html?cvsroot=texi2html&r1=1.26&r2=1.27
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/xemacs_frame_res/xemacs_13.html?cvsroot=texi2html&r1=1.23&r2=1.24
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/xemacs_frame_res/xemacs_14.html?cvsroot=texi2html&r1=1.23&r2=1.24
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/xemacs_frame_res/xemacs_15.html?cvsroot=texi2html&r1=1.28&r2=1.29
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/xemacs_frame_res/xemacs_16.html?cvsroot=texi2html&r1=1.22&r2=1.23
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/xemacs_frame_res/xemacs_17.html?cvsroot=texi2html&r1=1.25&r2=1.26
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/xemacs_frame_res/xemacs_18.html?cvsroot=texi2html&r1=1.22&r2=1.23
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/xemacs_frame_res/xemacs_19.html?cvsroot=texi2html&r1=1.21&r2=1.22
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/xemacs_frame_res/xemacs_2.html?cvsroot=texi2html&r1=1.17&r2=1.18
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/xemacs_frame_res/xemacs_20.html?cvsroot=texi2html&r1=1.27&r2=1.28
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/xemacs_frame_res/xemacs_21.html?cvsroot=texi2html&r1=1.19&r2=1.20
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/xemacs_frame_res/xemacs_22.html?cvsroot=texi2html&r1=1.23&r2=1.24
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/xemacs_frame_res/xemacs_23.html?cvsroot=texi2html&r1=1.24&r2=1.25
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/xemacs_frame_res/xemacs_24.html?cvsroot=texi2html&r1=1.27&r2=1.28
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/xemacs_frame_res/xemacs_25.html?cvsroot=texi2html&r1=1.30&r2=1.31
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/xemacs_frame_res/xemacs_26.html?cvsroot=texi2html&r1=1.23&r2=1.24
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/xemacs_frame_res/xemacs_28.html?cvsroot=texi2html&r1=1.23&r2=1.24
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/xemacs_frame_res/xemacs_29.html?cvsroot=texi2html&r1=1.26&r2=1.27
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/xemacs_frame_res/xemacs_3.html?cvsroot=texi2html&r1=1.18&r2=1.19
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/xemacs_frame_res/xemacs_30.html?cvsroot=texi2html&r1=1.28&r2=1.29
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/xemacs_frame_res/xemacs_31.html?cvsroot=texi2html&r1=1.23&r2=1.24
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/xemacs_frame_res/xemacs_32.html?cvsroot=texi2html&r1=1.20&r2=1.21
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/xemacs_frame_res/xemacs_4.html?cvsroot=texi2html&r1=1.26&r2=1.27
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/xemacs_frame_res/xemacs_5.html?cvsroot=texi2html&r1=1.27&r2=1.28
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/xemacs_frame_res/xemacs_6.html?cvsroot=texi2html&r1=1.27&r2=1.28
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/xemacs_frame_res/xemacs_7.html?cvsroot=texi2html&r1=1.25&r2=1.26
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/xemacs_frame_res/xemacs_8.html?cvsroot=texi2html&r1=1.18&r2=1.19
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/xemacs_frame_res/xemacs_9.html?cvsroot=texi2html&r1=1.24&r2=1.25
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/xemacs_frame_res/xemacs_frame.html?cvsroot=texi2html&r1=1.1&r2=1.2
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/xemacs_frame_res/xemacs_toc.html?cvsroot=texi2html&r1=1.14&r2=1.15
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/xemacs_res/xemacs.html?cvsroot=texi2html&r1=1.28&r2=1.29
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/xemacs_res/xemacs_1.html?cvsroot=texi2html&r1=1.25&r2=1.26
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/xemacs_res/xemacs_11.html?cvsroot=texi2html&r1=1.29&r2=1.30
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/xemacs_res/xemacs_12.html?cvsroot=texi2html&r1=1.31&r2=1.32
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/xemacs_res/xemacs_13.html?cvsroot=texi2html&r1=1.28&r2=1.29
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/xemacs_res/xemacs_14.html?cvsroot=texi2html&r1=1.27&r2=1.28
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/xemacs_res/xemacs_15.html?cvsroot=texi2html&r1=1.33&r2=1.34
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/xemacs_res/xemacs_16.html?cvsroot=texi2html&r1=1.26&r2=1.27
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/xemacs_res/xemacs_17.html?cvsroot=texi2html&r1=1.30&r2=1.31
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/xemacs_res/xemacs_18.html?cvsroot=texi2html&r1=1.27&r2=1.28
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/xemacs_res/xemacs_19.html?cvsroot=texi2html&r1=1.25&r2=1.26
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/xemacs_res/xemacs_2.html?cvsroot=texi2html&r1=1.20&r2=1.21
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/xemacs_res/xemacs_20.html?cvsroot=texi2html&r1=1.31&r2=1.32
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/xemacs_res/xemacs_21.html?cvsroot=texi2html&r1=1.23&r2=1.24
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/xemacs_res/xemacs_22.html?cvsroot=texi2html&r1=1.27&r2=1.28
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/xemacs_res/xemacs_23.html?cvsroot=texi2html&r1=1.30&r2=1.31
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/xemacs_res/xemacs_24.html?cvsroot=texi2html&r1=1.32&r2=1.33
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/xemacs_res/xemacs_25.html?cvsroot=texi2html&r1=1.34&r2=1.35
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/xemacs_res/xemacs_26.html?cvsroot=texi2html&r1=1.27&r2=1.28
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/xemacs_res/xemacs_28.html?cvsroot=texi2html&r1=1.27&r2=1.28
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/xemacs_res/xemacs_29.html?cvsroot=texi2html&r1=1.32&r2=1.33
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/xemacs_res/xemacs_3.html?cvsroot=texi2html&r1=1.22&r2=1.23
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/xemacs_res/xemacs_30.html?cvsroot=texi2html&r1=1.34&r2=1.35
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/xemacs_res/xemacs_31.html?cvsroot=texi2html&r1=1.27&r2=1.28
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/xemacs_res/xemacs_32.html?cvsroot=texi2html&r1=1.24&r2=1.25
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/xemacs_res/xemacs_4.html?cvsroot=texi2html&r1=1.30&r2=1.31
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/xemacs_res/xemacs_5.html?cvsroot=texi2html&r1=1.32&r2=1.33
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/xemacs_res/xemacs_6.html?cvsroot=texi2html&r1=1.32&r2=1.33
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/xemacs_res/xemacs_7.html?cvsroot=texi2html&r1=1.30&r2=1.31
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/xemacs_res/xemacs_8.html?cvsroot=texi2html&r1=1.22&r2=1.23
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/xemacs_res/xemacs_9.html?cvsroot=texi2html&r1=1.29&r2=1.30
http://cvs.savannah.gnu.org/viewcvs/texi2html/Tests/xemacs_res/xemacs_toc.html?cvsroot=texi2html&r1=1.18&r2=1.19
http://cvs.savannah.gnu.org/viewcvs/texi2html/doc/texi2html.html?cvsroot=texi2html&r1=1.56&r2=1.57

Patches:
Index: ChangeLog
===================================================================
RCS file: /cvsroot/texi2html/texi2html/ChangeLog,v
retrieving revision 1.275
retrieving revision 1.276
diff -u -b -r1.275 -r1.276
--- ChangeLog   3 Oct 2007 08:44:00 -0000       1.275
+++ ChangeLog   3 Oct 2007 09:34:35 -0000       1.276
@@ -2,6 +2,7 @@
 
        * texi2html.pl, texi2html.init: use relative file names for frame
        file names (report from Graham Percival).
+       * texi2html.init: use entities for simple quotes in normal text.
 
 2007-10-02  Patrice Dumas  <address@hidden>
 

Index: texi2html.init
===================================================================
RCS file: /cvsroot/texi2html/texi2html/texi2html.init,v
retrieving revision 1.124
retrieving revision 1.125
diff -u -b -r1.124 -r1.125
--- texi2html.init      3 Oct 2007 08:44:00 -0000       1.124
+++ texi2html.init      3 Oct 2007 09:34:36 -0000       1.125
@@ -12,7 +12,7 @@
 # Afterwards, load the file with command-line 
 # option -init-file <your_init_file>
 #
-# $Id: texi2html.init,v 1.124 2007/10/03 08:44:00 pertusus Exp $
+# $Id: texi2html.init,v 1.125 2007/10/03 09:34:36 pertusus Exp $
 
 ######################################################################
 # The following variables can also be set by command-line options
@@ -3645,8 +3645,8 @@
            $text =~ s/''/\&rdquo\;/g;
            if (! $in_simple)
            { # lquot and rquot don't seem to be accepted in title.
-           #    $text =~ s/'/$iso_symbols{"'"}/g if (defined 
($iso_symbols{"'"}));
-           #    $text =~ s/`/$iso_symbols{'`'}/g if (defined 
($iso_symbols{'`'}));
+               $text =~ s/'/$iso_symbols{"'"}/g if (defined 
($iso_symbols{"'"}));
+               $text =~ s/`/$iso_symbols{'`'}/g if (defined 
($iso_symbols{'`'}));
            }
        }
        else

Index: Tests/GermanNodeTest_res/nodetest.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/GermanNodeTest_res/nodetest.html,v
retrieving revision 1.45
retrieving revision 1.46
diff -u -b -r1.45 -r1.46
--- Tests/GermanNodeTest_res/nodetest.html      30 Sep 2007 12:47:12 -0000      
1.45
+++ Tests/GermanNodeTest_res/nodetest.html      3 Oct 2007 09:34:36 -0000       
1.46
@@ -459,7 +459,7 @@
 <td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? 
</a>]</td>
 </tr></table>
 <h2 class="section"> 2.1 &aacute; </h2>
-<p>With brace &aacute;. Testing ' &quot; ` ^.
+<p>With brace &aacute;. Testing &rsquo; &quot; &lsquo; ^.
 </p><hr size="6">
 <a name="g_t_00e9"></a>
 <a name="SEC18"></a>

Index: Tests/GermanNodeTest_res/nodetest_for_makeinfo.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/GermanNodeTest_res/nodetest_for_makeinfo.html,v
retrieving revision 1.29
retrieving revision 1.30
diff -u -b -r1.29 -r1.30
--- Tests/GermanNodeTest_res/nodetest_for_makeinfo.html 30 Sep 2007 12:47:12 
-0000      1.29
+++ Tests/GermanNodeTest_res/nodetest_for_makeinfo.html 3 Oct 2007 09:34:36 
-0000       1.30
@@ -459,7 +459,7 @@
 <td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? 
</a>]</td>
 </tr></table>
 <h2 class="section"> 2.1 &aacute; </h2>
-<p>With brace &aacute;. Testing ' &quot; ` ^.
+<p>With brace &aacute;. Testing &rsquo; &quot; &lsquo; ^.
 </p><hr size="6">
 <a name="g_t_00e9"></a>
 <a name="SEC18"></a>

Index: Tests/ccvs_res/cvs_1.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/ccvs_res/cvs_1.html,v
retrieving revision 1.28
retrieving revision 1.29
diff -u -b -r1.28 -r1.29
--- Tests/ccvs_res/cvs_1.html   5 Feb 2007 15:30:22 -0000       1.28
+++ Tests/ccvs_res/cvs_1.html   3 Oct 2007 09:34:36 -0000       1.29
@@ -72,7 +72,7 @@
 <table class="menu" border="0" cellspacing="0">
 <tr><td align="left" valign="top"><a href="#SEC2">1.1 What is 
CVS?</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">                
What you can do with <small>CVS</small>
 </td></tr>
-<tr><td align="left" valign="top"><a href="#SEC3">1.2 What is CVS 
not?</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">            
Problems <small>CVS</small> doesn't try to solve
+<tr><td align="left" valign="top"><a href="#SEC3">1.2 What is CVS 
not?</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">            
Problems <small>CVS</small> doesn&rsquo;t try to solve
 </td></tr>
 <tr><td align="left" valign="top"><a href="#SEC4">1.3 A sample 
session</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">            
A tour of basic <small>CVS</small> usage
 </td></tr>
@@ -119,7 +119,7 @@
 </p>
 <p><small>CVS</small> also helps you if you are part of a group of people 
working
 on the same project.  It is all too easy to overwrite
-each others' changes unless you are extremely careful.
+each others&rsquo; changes unless you are extremely careful.
 Some editors, like <small>GNU</small> Emacs, try to make sure that
 the same file is never modified by two people at the
 same time.  Unfortunately, if someone is using another
@@ -246,7 +246,7 @@
 <p>Your managers and project leaders are expected to talk
 to you frequently enough to make certain you are aware
 of schedules, merge points, branch names and release
-dates.  If they don't, <small>CVS</small> can't help.
+dates.  If they don&rsquo;t, <small>CVS</small> can&rsquo;t help.
 </p>
 <p><small>CVS</small> is an instrument for making sources dance to
 your tune.  But you are the piper and the composer.  No
@@ -275,7 +275,7 @@
 <code>X</code> defined in file &lsquo;<tt>A</tt>&rsquo;.  At the same time,
 someone edits file &lsquo;<tt>B</tt>&rsquo;, adding new calls to
 function <code>X</code> using the old arguments.  You are
-outside the realm of <small>CVS</small>'s competence.
+outside the realm of <small>CVS</small>&rsquo;s competence.
 </p>
 <p>Acquire the habit of reading specs and talking to your
 peers.
@@ -318,7 +318,7 @@
 <dt> <small>CVS</small> is not an automated testing program</dt>
 <dd>
 <p>It should be possible to enforce mandatory use of a
-testsuite using the <code>commitinfo</code> file.  I haven't
+testsuite using the <code>commitinfo</code> file.  I haven&rsquo;t
 heard a lot about projects trying to do that or whether
 there are subtle gotchas, however.
 </p>
@@ -329,7 +329,7 @@
 releases go through various steps, with various
 approvals as needed.  Generally, one can accomplish
 this with <small>CVS</small> but it might be a little more work.
-In some cases you'll want to use the &lsquo;<tt>commitinfo</tt>&rsquo;,
+In some cases you&rsquo;ll want to use the &lsquo;<tt>commitinfo</tt>&rsquo;,
 &lsquo;<tt>loginfo</tt>&rsquo;, &lsquo;<tt>rcsinfo</tt>&rsquo;, or 
&lsquo;<tt>verifymsg</tt>&rsquo;
 files, to require that certain steps be performed
 before cvs will allow a checkin.  Also consider whether
@@ -362,7 +362,7 @@
 <h2 class="section"> 1.3 A sample session </h2>
 
 
-<p>As a way of introducing <small>CVS</small>, we'll go through a
+<p>As a way of introducing <small>CVS</small>, we&rsquo;ll go through a
 typical work-session using <small>CVS</small>.  The first thing
 to understand is that <small>CVS</small> stores all files in a
 centralized <em>repository</em> (see section <a href="cvs_2.html#SEC9">The 
Repository</a>); this
@@ -485,7 +485,7 @@
 this list is based on comparing the modification time
 of the file against the modification time that the file
 had when it was last gotten or updated.  Therefore, if
-a file's modification time has changed but its contents
+a file&rsquo;s modification time has changed but its contents
 have not, it will show up as modified.  The simplest
 way to handle this is simply not to worry about it&mdash;if
 you proceed with the commit <small>CVS</small> will detect that

Index: Tests/ccvs_res/cvs_10.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/ccvs_res/cvs_10.html,v
retrieving revision 1.29
retrieving revision 1.30
diff -u -b -r1.29 -r1.30
--- Tests/ccvs_res/cvs_10.html  5 Feb 2007 15:30:22 -0000       1.29
+++ Tests/ccvs_res/cvs_10.html  3 Oct 2007 09:34:36 -0000       1.30
@@ -203,7 +203,7 @@
 </dd>
 <dt> Unknown</dt>
 <dd><a name="IDX145"></a>
-<p><small>CVS</small> doesn't know anything about this file.  For
+<p><small>CVS</small> doesn&rsquo;t know anything about this file.  For
 example, you have created a new file and have not run
 <code>add</code>.
 </p>
@@ -462,7 +462,7 @@
 Because
 your file may legitimately contain conflict markers (that
 is, occurrences of &lsquo;<samp>&gt;&gt;&gt;&gt;&gt;&gt;&gt; </samp>&rsquo; at 
the start of a
-line that don't mark a conflict), the current
+line that don&rsquo;t mark a conflict), the current
 version of <small>CVS</small> will print a warning and proceed to
 check in the file.
 </p>
@@ -537,13 +537,13 @@
 if it still needs to wait.  If a lock seems to stick
 around for an undue amount of time, find the person
 holding the lock and ask them about the cvs command
-they are running.  If they aren't running a cvs
+they are running.  If they aren&rsquo;t running a cvs
 command, look in the repository directory mentioned in
 the message and remove files which they own whose names
 start with &lsquo;<tt>#cvs.rfl</tt>&rsquo;,
 &lsquo;<tt>#cvs.wfl</tt>&rsquo;, or &lsquo;<tt>#cvs.lock</tt>&rsquo;.
 </p>
-<p>Note that these locks are to protect <small>CVS</small>'s
+<p>Note that these locks are to protect <small>CVS</small>&rsquo;s
 internal data structures and have no relationship to
 the word <em>lock</em> in the sense used by
 <small>RCS</small>&mdash;which refers to reserved checkouts
@@ -753,7 +753,7 @@
 applying the <code>cvs unedit</code> command (described below) to the file
 
 </li><li>
-applying the <code>cvs release</code> command (see section <a 
href="cvs_16.html#SEC149">release&mdash;Indicate that a Module is no longer in 
use</a>) to the file's parent directory
+applying the <code>cvs release</code> command (see section <a 
href="cvs_16.html#SEC149">release&mdash;Indicate that a Module is no longer in 
use</a>) to the file&rsquo;s parent directory
 (or recursively to a directory more than one level up)
 
 </li><li>
@@ -1037,7 +1037,7 @@
 
 <p>Reserved and unreserved checkouts each have pros and
 cons.  Let it be said that a lot of this is a matter of
-opinion or what works given different groups' working
+opinion or what works given different groups&rsquo; working
 styles, but here is a brief description of some of the
 issues.  There are many ways to organize a team of
 developers.  <small>CVS</small> does not try to enforce a certain

Index: Tests/ccvs_res/cvs_12.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/ccvs_res/cvs_12.html,v
retrieving revision 1.34
retrieving revision 1.35
diff -u -b -r1.34 -r1.35
--- Tests/ccvs_res/cvs_12.html  5 Feb 2007 15:30:22 -0000       1.34
+++ Tests/ccvs_res/cvs_12.html  3 Oct 2007 09:34:36 -0000       1.35
@@ -427,9 +427,9 @@
 </p>
 </dd>
 <dt> &lsquo;<samp>-kkvl</samp>&rsquo;</dt>
-<dd><p>Like &lsquo;<samp>-kkv</samp>&rsquo;, except that a locker's name is 
always
+<dd><p>Like &lsquo;<samp>-kkv</samp>&rsquo;, except that a locker&rsquo;s name 
is always
 inserted if the given revision is currently locked.
-The locker's name is only relevant if <code>cvs admin
+The locker&rsquo;s name is only relevant if <code>cvs admin
 -l</code> is in use.
 </p>
 </dd>
@@ -478,7 +478,7 @@
 used with care.
 </p>
 <p>One often would like to use &lsquo;<samp>-kv</samp>&rsquo; with <code>cvs
-export</code>&mdash;see section <a 
href="cvs_16.html#SEC135">export&mdash;Export sources from CVS, similar to 
checkout</a>.  But be aware that doesn't
+export</code>&mdash;see section <a 
href="cvs_16.html#SEC135">export&mdash;Export sources from CVS, similar to 
checkout</a>.  But be aware that doesn&rsquo;t
 handle an export containing binary files correctly.
 </p>
 </dd>

Index: Tests/ccvs_res/cvs_13.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/ccvs_res/cvs_13.html,v
retrieving revision 1.24
retrieving revision 1.25
diff -u -b -r1.24 -r1.25
--- Tests/ccvs_res/cvs_13.html  5 Feb 2007 15:30:22 -0000       1.24
+++ Tests/ccvs_res/cvs_13.html  3 Oct 2007 09:34:36 -0000       1.25
@@ -82,10 +82,10 @@
 </p>
 <p>Use the <code>import</code> command to create and update
 the vendor branch.  When you import a new file,
-the vendor branch is made the `head' revision, so
+the vendor branch is made the &lsquo;head&rsquo; revision, so
 anyone that checks out a copy of the file gets that
 revision.  When a local modification is committed it is
-placed on the main trunk, and made the `head'
+placed on the main trunk, and made the &lsquo;head&rsquo;
 revision.
 </p>
 <table class="menu" border="0" cellspacing="0">
@@ -210,7 +210,7 @@
 More importantly, using the release tags allows <small>CVS</small> to detect 
files
 that were removed between the two vendor releases and mark them for
 removal.  Since <code>import</code> has no way to detect removed files, you
-should do a merge like this even if <code>import</code> doesn't tell you to.
+should do a merge like this even if <code>import</code> doesn&rsquo;t tell you 
to.
 </p>
 <hr size="6">
 <a name="Reverting-local-changes"></a>
@@ -234,11 +234,11 @@
 <h2 class="section"> 13.3 Reverting to the latest vendor release </h2>
 
 <p>You can also revert local changes completely and return
-to the latest vendor release by changing the `head'
+to the latest vendor release by changing the &lsquo;head&rsquo;
 revision back to the vendor branch on all files.  For
 example, if you have a checked-out copy of the sources
 in &lsquo;<tt>~/work.d/wdiff</tt>&rsquo;, and you want to revert to the
-vendor's version for all the files in that directory,
+vendor&rsquo;s version for all the files in that directory,
 you would type:
 </p>
 <table><tr><td>&nbsp;</td><td><pre class="example">$ cd ~/work.d/wdiff
@@ -310,7 +310,7 @@
 import</code> the first time you import the file.
 This will turn off keyword expansion
 for that file entirely, so if you want to be more
-selective you'll have to think about what you want
+selective you&rsquo;ll have to think about what you want
 and use the &lsquo;<samp>-k</samp>&rsquo; option to <code>cvs update</code> or
 <code>cvs admin</code> as appropriate.
 </p>
@@ -353,9 +353,9 @@
 </p>
 <p>For example, suppose that there are two teams, the red
 team and the blue team, that are sending you sources.
-You want to import the red team's efforts to branch
+You want to import the red team&rsquo;s efforts to branch
 1.1.1 and use the vendor tag RED.  You want to import
-the blue team's efforts to branch 1.1.3 and use the
+the blue team&rsquo;s efforts to branch 1.1.3 and use the
 vendor tag BLUE.  So the commands you might use are:
 </p>
 <table><tr><td>&nbsp;</td><td><pre class="example">$ cvs import dir RED RED_1-0
@@ -370,9 +370,9 @@
 </pre></td></tr></table>
 
 <p>Be careful; this kind of mismatch is sure to sow
-confusion or worse.  I can't think of a useful purpose
+confusion or worse.  I can&rsquo;t think of a useful purpose
 for the ability to specify a mismatch here, but if you
-discover such a use, don't.  <small>CVS</small> is likely to make this
+discover such a use, don&rsquo;t.  <small>CVS</small> is likely to make this
 an error in some future release.
 </p>
 

Index: Tests/ccvs_res/cvs_16.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/ccvs_res/cvs_16.html,v
retrieving revision 1.36
retrieving revision 1.37
diff -u -b -r1.36 -r1.37
--- Tests/ccvs_res/cvs_16.html  5 Feb 2007 15:30:22 -0000       1.36
+++ Tests/ccvs_res/cvs_16.html  3 Oct 2007 09:34:36 -0000       1.37
@@ -68,7 +68,7 @@
 </p>
 <table class="menu" border="0" cellspacing="0">
 <tr><td align="left" valign="top"><a href="#SEC115">A.1 Overall structure of 
CVS commands</a></td><td>&nbsp;&nbsp;</td><td align="left" 
valign="top"></td></tr>
-<tr><td align="left" valign="top"><a href="#SEC116">A.2 CVS's exit 
status</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">              
   Indicating CVS's success or failure
+<tr><td align="left" valign="top"><a href="#SEC116">A.2 CVS&rsquo;s exit 
status</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">              
   Indicating CVS&rsquo;s success or failure
 </td></tr>
 <tr><td align="left" valign="top"><a href="#SEC117">A.3 Default options and 
the ~/.cvsrc file</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">   
                 Default options with the ~/.csvrc file
 </td></tr>
@@ -92,7 +92,7 @@
 </td></tr>
 <tr><td align="left" valign="top"><a href="#SEC143">A.13 log&mdash;Print out 
log information for files</a></td><td>&nbsp;&nbsp;</td><td align="left" 
valign="top">                         Show log messages for files
 </td></tr>
-<tr><td align="left" valign="top"><a href="#SEC146">A.14 rdiff&mdash;'patch' 
format diffs between releases</a></td><td>&nbsp;&nbsp;</td><td align="left" 
valign="top">                       'patch' format diffs between releases
+<tr><td align="left" valign="top"><a href="#SEC146">A.14 
rdiff&mdash;&rsquo;patch&rsquo; format diffs between 
releases</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">            
           &rsquo;patch&rsquo; format diffs between releases
 </td></tr>
 <tr><td align="left" valign="top"><a href="#SEC149">A.15 
release&mdash;Indicate that a Module is no longer in 
use</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">                 
    Indicate that a directory is no longer in use
 </td></tr>
@@ -182,7 +182,7 @@
 <td valign="middle" align="left">[<a href="cvs_24.html#SEC189" 
title="Index">Index</a>]</td>
 <td valign="middle" align="left">[<a href="cvs_abt.html#SEC_About" 
title="About (help)"> ? </a>]</td>
 </tr></table>
-<h2 class="appendixsec"> A.2 CVS's exit status </h2>
+<h2 class="appendixsec"> A.2 CVS&rsquo;s exit status </h2>
 
 <p><small>CVS</small> can indicate to the calling environment whether it
 succeeded or failed by setting its <em>exit status</em>.
@@ -248,7 +248,7 @@
 <p>If a command has two names (e.g., <code>checkout</code> and
 <code>co</code>), the official name, not necessarily the one
 used on the command line, will be used to match against
-the file.  So if this is the contents of the user's
+the file.  So if this is the contents of the user&rsquo;s
 &lsquo;<tt>~/.cvsrc</tt>&rsquo; file:
 </p>
 <table><tr><td>&nbsp;</td><td><pre class="example">log -N
@@ -267,7 +267,7 @@
 diff foobar</samp>&rsquo; will be in unidiff format.  &lsquo;<samp>cvs diff
 -c foobar</samp>&rsquo; will provide context diffs, as usual.
 Getting &quot;old&quot; format diffs would be slightly more
-complicated, because <code>diff</code> doesn't have an option
+complicated, because <code>diff</code> doesn&rsquo;t have an option
 to specify use of the &quot;old&quot; format, so you would need
 &lsquo;<samp>cvs -f diff foobar</samp>&rsquo;.
 </p>
@@ -375,7 +375,7 @@
 <dt> <code>-H</code></dt>
 <dt> <code>--help</code></dt>
 <dd><p>Display usage information about the specified 
&lsquo;<samp>cvs_command</samp>&rsquo;
-(but do not actually execute the command).  If you don't specify
+(but do not actually execute the command).  If you don&rsquo;t specify
 a command name, &lsquo;<samp>cvs -H</samp>&rsquo; displays overall help for
 <small>CVS</small>, including a list of other help options.
 </p>
@@ -393,7 +393,7 @@
 </p>
 <p>Same effect as if the <code>CVSREADONLYFS</code> environment
 variable is set. Using &lsquo;<samp>-R</samp>&rsquo; can also considerably
-speed up checkout's over NFS.
+speed up checkout&rsquo;s over NFS.
 </p>
 <a name="IDX213"></a>
 </dd>
@@ -555,7 +555,7 @@
 </pre></td></tr></table>
 
 <p>There are a lot more ISO8601 date formats, and <small>CVS</small>
-accepts many of them, but you probably don't want to
+accepts many of them, but you probably don&rsquo;t want to
 hear the <em>whole</em> long story :-).
 </p>
 
@@ -584,7 +584,7 @@
 not April 1.
 </p>
 <p>Remember to quote the argument to the &lsquo;<samp>-D</samp>&rsquo;
-flag so that your shell doesn't interpret spaces as
+flag so that your shell doesn&rsquo;t interpret spaces as
 argument separators.  A command using the &lsquo;<samp>-D</samp>&rsquo;
 flag can look like this:
 </p>
@@ -839,7 +839,7 @@
 normally do not manipulate default branches; sticky
 tags (see section <a href="cvs_4.html#SEC53">Sticky tags</a>) are a better way 
to decide
 which branch you want to work on.  There is one reason
-to run <code>cvs admin -b</code>: to revert to the vendor's
+to run <code>cvs admin -b</code>: to revert to the vendor&rsquo;s
 version when using vendor branches (see section <a 
href="cvs_13.html#SEC108">Reverting to the latest vendor release</a>).
 There can be no space between &lsquo;<samp>-b</samp>&rsquo; and its argument.
 </p>
@@ -1045,7 +1045,7 @@
 revisions but leave the symbolic names pointing to
 nonexistent revisions.  This behavior is preserved for
 compatibility with previous versions of <small>CVS</small>, but
-because it isn't very useful, in the future it may
+because it isn&rsquo;t very useful, in the future it may
 change to be like the &lsquo;<samp>::</samp>&rsquo; case.
 </p>
 <p>Due to the way <small>CVS</small> handles branches <var>rev</var>
@@ -1229,7 +1229,7 @@
 to use <code>checkout</code> this way it must be run from the
 top level directory (where you originally ran
 <code>checkout</code> from), so before you run
-<code>checkout</code> to update an existing directory, don't
+<code>checkout</code> to update an existing directory, don&rsquo;t
 forget to change your directory to the top level
 directory.
 </p>
@@ -1342,7 +1342,7 @@
 </p>
 <p>There is an important exception, however.  It is very
 convenient when checking out a single item to have the
-output appear in a directory that doesn't contain empty
+output appear in a directory that doesn&rsquo;t contain empty
 intermediate directories.  In this case <em>only</em>,
 <small>CVS</small> tries to &ldquo;shorten&rdquo; pathnames to avoid those 
empty
 directories.
@@ -1458,7 +1458,7 @@
 
 <ul>
 <li>
-Synopsis: commit [-lnRf] [-m 'log_message' |
+Synopsis: commit [-lnRf] [-m &rsquo;log_message&rsquo; |
 -F file] [-r revision] [files&hellip;]
 </li><li>
 Requires: working directory, repository.
@@ -1472,7 +1472,7 @@
 from your working source files into the source
 repository.
 </p>
-<p>If you don't specify particular files to commit, all of
+<p>If you don&rsquo;t specify particular files to commit, all of
 the files in your working current directory are
 examined.  <code>commit</code> is careful to change in the
 repository only those files that you have really
@@ -1562,7 +1562,7 @@
 <dd><p>Note that this is not the standard behavior of
 the &lsquo;<samp>-f</samp>&rsquo; option as defined in <a 
href="#SEC119">Common command options</a>.
 </p>
-<p>Force <small>CVS</small> to commit a new revision even if you haven't
+<p>Force <small>CVS</small> to commit a new revision even if you haven&rsquo;t
 made any changes to the file.  If the current revision
 of <var>file</var> is 1.7, then the following two commands
 are equivalent:
@@ -1749,7 +1749,7 @@
 under them will be compared.
 </p>
 <p>The exit status for diff is different than for other
-<small>CVS</small> commands; for details <a href="#SEC116">CVS's exit 
status</a>.
+<small>CVS</small> commands; for details <a href="#SEC116">CVS&rsquo;s exit 
status</a>.
 </p>
 <table class="menu" border="0" cellspacing="0">
 <tr><td align="left" valign="top"><a href="#SEC131">A.9.1 diff 
options</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top"></td></tr>
@@ -2245,7 +2245,7 @@
 </dd>
 <dt> &lsquo;<samp><var>F</var><var>n</var></samp>&rsquo;</dt>
 <dd><p>where <var>F</var> is a <code>printf</code> conversion specification 
and <var>n</var> is one
-of the following letters, stands for <var>n</var>'s value formatted with 
<var>F</var>.
+of the following letters, stands for <var>n</var>&rsquo;s value formatted with 
<var>F</var>.
 </p>
 <dl compact="compact">
 <dt> &lsquo;<samp>e</samp>&rsquo;</dt>
@@ -2292,7 +2292,7 @@
 <var>A</var> and <var>B</var> are each either a decimal constant
 or a single letter interpreted as above.
 This format spec is equivalent to <var>T</var> if
-<var>A</var>'s value equals <var>B</var>'s; otherwise it is equivalent to 
<var>E</var>.
+<var>A</var>&rsquo;s value equals <var>B</var>&rsquo;s; otherwise it is 
equivalent to <var>E</var>.
 </p>
 <p>For example, &lsquo;<samp>%(N=0?no:%dN) line%(N=1?:s)</samp>&rsquo; is 
equivalent to
 &lsquo;<samp>no lines</samp>&rsquo; if <var>N</var> (the number of lines in 
the group in the
@@ -2414,8 +2414,8 @@
 </p>
 <p>Taken together, the line and line group formats let you specify many
 different formats.  For example, the following command uses a format
-similar to <code>diff</code>'s normal format.  You can tailor this command
-to get fine control over <code>diff</code>'s output.
+similar to <code>diff</code>&rsquo;s normal format.  You can tailor this 
command
+to get fine control over <code>diff</code>&rsquo;s output.
 </p>
 <table><tr><td>&nbsp;</td><td><pre class="example">cvs diff \
    --old-line-format='&lt; %l
@@ -2527,7 +2527,7 @@
 export</code>.  This causes any keywords to be
 expanded such that an import done at some other site
 will not lose the keyword revision information.  But be
-aware that doesn't handle an export containing binary
+aware that doesn&rsquo;t handle an export containing binary
 files correctly.  Also be aware that after having used
 &lsquo;<samp>-kv</samp>&rsquo;, one can no longer use the <code>ident</code>
 command (which is part of the <small>RCS</small> suite&mdash;see
@@ -2697,7 +2697,7 @@
 &lsquo;<samp>-e</samp>&rsquo; will also include record types which are
 added in a future version of <small>CVS</small>; if you are
 writing a script which can only handle certain record
-types, you'll want to specify &lsquo;<samp>-x</samp>&rsquo;.
+types, you&rsquo;ll want to specify &lsquo;<samp>-x</samp>&rsquo;.
 </p>
 </dd>
 <dt> <code>-m <var>module</var></code></dt>
@@ -2987,7 +2987,7 @@
 <dd><p>Specify file names that should be ignored during
 import.  You can use this option repeatedly.  To avoid
 ignoring any files at all (even those ignored by
-default), specify `-I !'.
+default), specify &lsquo;-I !&rsquo;.
 </p>
 <p><var>name</var> can be a file name pattern of the same type
 that you can specify in the &lsquo;<tt>.cvsignore</tt>&rsquo; file.
@@ -3222,7 +3222,7 @@
 <dt> <code>-N</code></dt>
 <dd><p>Do not print the list of tags for this file.  This
 option can be very useful when your site uses a lot of
-tags, so rather than &quot;more&quot;'ing over 3 pages of tag
+tags, so rather than &quot;more&quot;&rsquo;ing over 3 pages of tag
 information, the log information is presented without
 tags at all.
 </p>
@@ -3302,7 +3302,7 @@
 <dt> <code>-w<var>logins</var></code></dt>
 <dd><p>Print information about revisions checked in by users
 with login names appearing in the comma-separated list
-<var>logins</var>.  If <var>logins</var> is omitted, the user's
+<var>logins</var>.  If <var>logins</var> is omitted, the user&rsquo;s
 login is assumed.  There can be no space between the
 &lsquo;<samp>-w</samp>&rsquo; option and its argument.
 </p></dd>
@@ -3355,7 +3355,7 @@
 <td valign="middle" align="left">[<a href="cvs_24.html#SEC189" 
title="Index">Index</a>]</td>
 <td valign="middle" align="left">[<a href="cvs_abt.html#SEC_About" 
title="About (help)"> ? </a>]</td>
 </tr></table>
-<h2 class="appendixsec"> A.14 rdiff&mdash;'patch' format diffs between 
releases </h2>
+<h2 class="appendixsec"> A.14 rdiff&mdash;&rsquo;patch&rsquo; format diffs 
between releases </h2>
 
 <ul>
 <li>
@@ -3372,7 +3372,7 @@
 releases, that can be fed directly into the <code>patch</code>
 program to bring an old release up-to-date with the new
 release.  (This is one of the few <small>CVS</small> commands that
-operates directly from the repository, and doesn't
+operates directly from the repository, and doesn&rsquo;t
 require a prior checkout.) The diff output is sent to
 the standard output device.
 </p>
@@ -3430,7 +3430,7 @@
 </p>
 </dd>
 <dt> <code>-l</code></dt>
-<dd><p>Local; don't descend subdirectories.
+<dd><p>Local; don&rsquo;t descend subdirectories.
 </p>
 </dd>
 <dt> <code>-R</code></dt>
@@ -3467,7 +3467,7 @@
 <dt> <code>-u</code></dt>
 <dd><p>Use the unidiff format for the context diffs.
 Remember that old versions
-of the <code>patch</code> program can't handle the unidiff
+of the <code>patch</code> program can&rsquo;t handle the unidiff
 format, so if you plan to post this patch to the net
 you should probably not use &lsquo;<samp>-u</samp>&rsquo;.
 </p>
@@ -3555,12 +3555,12 @@
 </li></ul>
 
 <p>This command is meant to safely cancel the effect of
-&lsquo;<samp>cvs checkout</samp>&rsquo;.  Since <small>CVS</small> doesn't 
lock files, it
-isn't strictly necessary to use this command.  You can
+&lsquo;<samp>cvs checkout</samp>&rsquo;.  Since <small>CVS</small> 
doesn&rsquo;t lock files, it
+isn&rsquo;t strictly necessary to use this command.  You can
 always simply delete your working directory, if you
 like; but you risk losing changes you may have
 forgotten, and you leave no trace in the <small>CVS</small> history
-file (see section <a href="cvs_18.html#SEC178">The history file</a>) that 
you've abandoned your
+file (see section <a href="cvs_18.html#SEC178">The history file</a>) that 
you&rsquo;ve abandoned your
 checkout.
 </p>
 <p>Use &lsquo;<samp>cvs release</samp>&rsquo; to avoid these problems.  This
@@ -3744,7 +3744,7 @@
 Changes: working directory.
 </li></ul>
 
-<p>After you've run checkout to create your private copy
+<p>After you&rsquo;ve run checkout to create your private copy
 of source from the common repository, other developers
 will continue changing the central source.  From time
 to time, when it is convenient in your development
@@ -3851,7 +3851,7 @@
 </dd>
 <dt> <code>-d</code></dt>
 <dd><p>Create any directories that exist in the repository if
-they're missing from the working directory.  Normally,
+they&rsquo;re missing from the working directory.  Normally,
 <code>update</code> acts only on directories and files that
 were already enrolled in your working directory.
 </p>
@@ -3944,7 +3944,7 @@
 <dd><p>The file was brought up to date with respect to the
 repository.  This is done for any file that exists in
 the repository but not in your source, and for files
-that you haven't changed but are not the most recent
+that you haven&rsquo;t changed but are not the most recent
 versions available in the repository.
 </p>
 </dd>
@@ -3971,7 +3971,7 @@
 <dd><p>The file is modified in  your  working  directory.
 </p>
 <p>&lsquo;<samp>M</samp>&rsquo; can indicate one of two states for a file
-you're working on: either there were no modifications
+you&rsquo;re working on: either there were no modifications
 to the same file in the repository, so that your file
 remains as you last saw it; or there were modifications
 in the repository as well as in your copy, but they

Index: Tests/ccvs_res/cvs_17.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/ccvs_res/cvs_17.html,v
retrieving revision 1.31
retrieving revision 1.32
diff -u -b -r1.31 -r1.32
--- Tests/ccvs_res/cvs_17.html  5 Feb 2007 15:30:22 -0000       1.31
+++ Tests/ccvs_res/cvs_17.html  3 Oct 2007 09:34:36 -0000       1.32
@@ -337,7 +337,7 @@
 </p>
 </dd>
 <dt> <code>-N</code></dt>
-<dd><p>Don't &ldquo;shorten&rdquo; module paths if -d specified.  See
+<dd><p>Don&rsquo;t &ldquo;shorten&rdquo; module paths if -d specified.  See
 <a href="cvs_16.html#SEC123">checkout options</a>.
 </p>
 </dd>
@@ -507,7 +507,7 @@
 </p>
 </dd>
 <dt> <code>-N</code></dt>
-<dd><p>Don't &ldquo;shorten&rdquo; module paths if -d specified.  See
+<dd><p>Don&rsquo;t &ldquo;shorten&rdquo; module paths if -d specified.  See
 <a href="cvs_16.html#SEC136">export options</a>.
 </p>
 </dd>
@@ -613,7 +613,7 @@
 </p>
 </dd>
 <dt> <code>-d</code></dt>
-<dd><p>Use the file's modification time as the time of
+<dd><p>Use the file&rsquo;s modification time as the time of
 import.  See <a href="cvs_16.html#SEC140">import options</a>.
 </p>
 </dd>
@@ -639,7 +639,7 @@
 
 </dd>
 <dt> <code>init</code></dt>
-<dd><p>Create a <small>CVS</small> repository if it doesn't exist.  See
+<dd><p>Create a <small>CVS</small> repository if it doesn&rsquo;t exist.  See
 <a href="cvs_2.html#SEC23">Creating a repository</a>.
 </p>
 </dd>
@@ -745,7 +745,7 @@
 
 </dd>
 <dt> <code>rdiff [<var>options</var>] <var>modules</var>&hellip;</code></dt>
-<dd><p>Show differences between releases.  See <a 
href="cvs_16.html#SEC146">rdiff&mdash;'patch' format diffs between releases</a>.
+<dd><p>Show differences between releases.  See <a 
href="cvs_16.html#SEC146">rdiff&mdash;&rsquo;patch&rsquo; format diffs between 
releases</a>.
 </p>
 <dl compact="compact">
 <dt> <code>-c</code></dt>

Index: Tests/ccvs_res/cvs_18.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/ccvs_res/cvs_18.html,v
retrieving revision 1.29
retrieving revision 1.30
diff -u -b -r1.29 -r1.30
--- Tests/ccvs_res/cvs_18.html  5 Feb 2007 15:30:22 -0000       1.29
+++ Tests/ccvs_res/cvs_18.html  3 Oct 2007 09:34:36 -0000       1.30
@@ -725,7 +725,7 @@
 that the modified, added and removed files are really
 ready to be committed.  This could be used, for
 instance, to verify that the changed files conform to
-to your site's standards for coding practice.
+to your site&rsquo;s standards for coding practice.
 </p>
 <p>As mentioned earlier, each line in the
 &lsquo;<tt>commitinfo</tt>&rsquo; file consists of a regular expression
@@ -863,13 +863,13 @@
 that is run by &lsquo;<tt>verifymsg</tt>&rsquo;.
 </p>
 <p>An example of an update might be to change all
-occurrences of 'BugId:' to be 'DefectId:' (which can be
+occurrences of &rsquo;BugId:&rsquo; to be &rsquo;DefectId:&rsquo; (which can be
 useful if the rcstemplate has recently been changed and
 there are still checked-out user trees with cached
 copies in the CVS/Template file of the older version).
 </p>
 <p>Another example of an update might be to delete a line
-that contains 'BugID: none' from the log message after
+that contains &rsquo;BugID: none&rsquo; from the log message after
 validation of that value as being allowed is made.
 </p>
 <p>The following is a little silly example of a
@@ -1139,7 +1139,7 @@
 </p>
 <p>The output will be a space separated string of tokens enclosed in
 quotation marks (<tt>&quot;</tt>).
-Any embedded dollar signs (<tt>$</tt>), backticks (<tt>`</tt>),
+Any embedded dollar signs (<tt>$</tt>), backticks (<tt>&lsquo;</tt>),
 backslashes (<tt>\</tt>), or quotation marks will be preceded
 by a backslash (this allows the shell to correctly parse it
 as a single string, regardless of the characters it contains).
@@ -1338,11 +1338,11 @@
 <h2 class="appendixsec"> C.5 Ignoring files via cvsignore </h2>
 
 <p>There are certain file names that frequently occur
-inside your working copy, but that you don't want to
+inside your working copy, but that you don&rsquo;t want to
 put under <small>CVS</small> control.  Examples are all the object
 files that you get while you compile your sources.
 Normally, when you run &lsquo;<samp>cvs update</samp>&rsquo;, it prints a
-line for each file it encounters that it doesn't know
+line for each file it encounters that it doesn&rsquo;t know
 about (see section <a href="cvs_16.html#SEC155">update output</a>).
 </p>
 <p><small>CVS</small> has a list of files (or sh(1) file name patterns)
@@ -1469,7 +1469,7 @@
 </p>
 <p>After setting up &lsquo;<tt>checkoutlist</tt>&rsquo; in this fashion,
 the files listed there will function just like
-<small>CVS</small>'s built-in administrative files.  For example,
+<small>CVS</small>&rsquo;s built-in administrative files.  For example,
 when checking in one of the files you should get a
 message such as:
 </p>
@@ -1551,7 +1551,7 @@
 &lsquo;<samp>~</samp>&rsquo; followed by &lsquo;<samp>/</samp>&rsquo; or the 
end of the line.
 Likewise for the home directory of <var>user</var>, use
 &lsquo;<samp>~<var>user</var></samp>&rsquo;.  These variables are expanded on
-the server machine, and don't get any reasonable
+the server machine, and don&rsquo;t get any reasonable
 expansion if pserver (see section <a href="cvs_2.html#SEC29">Direct connection 
with password authentication</a>)
 is in use; therefore user variables (see below) may be
 a better choice to customize behavior based on the user
@@ -1714,7 +1714,7 @@
 </dd>
 <dt> <code>SystemAuth=<var>value</var></code></dt>
 <dd><p>If <var>value</var> is &lsquo;<samp>yes</samp>&rsquo;, then pserver 
should check
-for users in the system's user database if not found in
+for users in the system&rsquo;s user database if not found in
 &lsquo;<tt>CVSROOT/passwd</tt>&rsquo;.  If it is 
&lsquo;<samp>no</samp>&rsquo;, then all
 pserver users must exist in &lsquo;<tt>CVSROOT/passwd</tt>&rsquo;.
 The default is &lsquo;<samp>yes</samp>&rsquo;.  For more on pserver, see
@@ -1734,7 +1734,7 @@
 many commands at the top level of your working
 directory, rather than in one of the checked out
 subdirectories.  The &lsquo;<tt>CVS</tt>&rsquo; directory created there
-will mean you don't have to specify <code>CVSROOT</code> for
+will mean you don&rsquo;t have to specify <code>CVSROOT</code> for
 each command.  It also provides a place for the
 &lsquo;<tt>CVS/Template</tt>&rsquo; file (see section <a 
href="cvs_2.html#SEC19">How data is stored in the working directory</a>).
 </p>
@@ -1757,7 +1757,7 @@
 <p>Before enabling the LockDir option, make sure that you
 have tracked down and removed any copies of <small>CVS</small> 1.9 or
 older.  Such versions neither support LockDir, nor will
-give an error indicating that they don't support it.
+give an error indicating that they don&rsquo;t support it.
 The result, if this is allowed to happen, is that some
 <small>CVS</small> users will put the locks one place, and others will
 put them another place, and therefore the repository
@@ -1788,7 +1788,7 @@
 &lsquo;<samp>stat()</samp>&rsquo; function to see if it has changed (see 
warning below)
 before rereading.  The default value is &lsquo;<samp>always</samp>&rsquo;.
 </p>
-<p><strong>Note: the `stat' mode can cause CVS to pause for up to
+<p><strong>Note: the &lsquo;stat&rsquo; mode can cause CVS to pause for up to
 one extra second per directory committed.  This can be less IO and
 CPU intensive but is not recommended for use with large repositories</strong>
 </p>

Index: Tests/ccvs_res/cvs_19.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/ccvs_res/cvs_19.html,v
retrieving revision 1.24
retrieving revision 1.25
diff -u -b -r1.24 -r1.25
--- Tests/ccvs_res/cvs_19.html  5 Feb 2007 15:30:22 -0000       1.24
+++ Tests/ccvs_res/cvs_19.html  3 Oct 2007 09:34:36 -0000       1.25
@@ -152,7 +152,7 @@
 file, and other such files, are searched.  On Unix, <small>CVS</small>
 just checks for <code>HOME</code>.  On Windows NT, the system will
 set <code>HOMEDRIVE</code>, for example to &lsquo;<samp>d:</samp>&rsquo; and 
<code>HOMEPATH</code>,
-for example to &lsquo;<tt>\joe</tt>&rsquo;.  On Windows 95, you'll
+for example to &lsquo;<tt>\joe</tt>&rsquo;.  On Windows 95, you&rsquo;ll
 probably need to set <code>HOMEDRIVE</code> and <code>HOMEPATH</code> yourself.
 </p>
 <a name="IDX304"></a>
@@ -182,7 +182,7 @@
 </dd>
 <dt> <code>$CVS_CLIENT_PORT</code></dt>
 <dd><p>Used in client-server mode to set the port to use when accessing the 
server
-via Kerberos, GSSAPI, or <small>CVS</small>'s password authentication protocol
+via Kerberos, GSSAPI, or <small>CVS</small>&rsquo;s password authentication 
protocol
 if the port is not specified in the CVSROOT.
 see section <a href="cvs_2.html#SEC26">Remote repositories</a>
 </p>

Index: Tests/ccvs_res/cvs_2.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/ccvs_res/cvs_2.html,v
retrieving revision 1.28
retrieving revision 1.29
diff -u -b -r1.28 -r1.29
--- Tests/ccvs_res/cvs_2.html   5 Feb 2007 15:30:22 -0000       1.28
+++ Tests/ccvs_res/cvs_2.html   3 Oct 2007 09:34:37 -0000       1.29
@@ -69,7 +69,7 @@
 repository directly.  Instead, you use <small>CVS</small>
 commands to get your own copy of the files into a
 <em>working directory</em>, and then
-work on that copy.  When you've finished a set of
+work on that copy.  When you&rsquo;ve finished a set of
 changes, you check (or <em>commit</em>) them back into the
 repository.  The repository then contains the changes
 which you have made, as well as recording exactly what
@@ -182,7 +182,7 @@
 <a name="IDX19"></a>
 <p>        A repository specified with <code>-d</code> will
 override the <code>$CVSROOT</code> environment variable.
-Once you've checked a working copy out from the
+Once you&rsquo;ve checked a working copy out from the
 repository, it will remember where its repository is
 (the information is recorded in the
 &lsquo;<tt>CVS/Root</tt>&rsquo; file in the working copy).
@@ -214,7 +214,7 @@
 </tr></table>
 <h2 class="section"> 2.2 How data is stored in the repository </h2>
 
-<p>For most purposes it isn't important <em>how</em>
+<p>For most purposes it isn&rsquo;t important <em>how</em>
 <small>CVS</small> stores information in the repository.  In
 fact, the format has changed in the past, and is likely
 to change in the future.  Since in almost all cases one
@@ -352,7 +352,7 @@
 <p>The <small>RCS</small> files used in <small>CVS</small> differ in a few
 ways from the standard format.  The biggest difference
 is magic branches; for more information see <a href="cvs_5.html#SEC59">Magic 
branch numbers</a>.  Also in <small>CVS</small> the valid tag names
-are a subset of what <small>RCS</small> accepts; for <small>CVS</small>'s
+are a subset of what <small>RCS</small> accepts; for <small>CVS</small>&rsquo;s
 rules see <a href="cvs_4.html#SEC48">Tags&ndash;Symbolic revisions</a>.
 </p>
 <hr size="6">
@@ -487,7 +487,7 @@
 <p>Some file permission issues are specific to Windows
 operating systems (Windows 95, Windows NT, and
 presumably future operating systems in this family.
-Some of the following might apply to OS/2 but I'm not
+Some of the following might apply to OS/2 but I&rsquo;m not
 sure).
 </p>
 <p>If you are using local <small>CVS</small> and the repository is on a
@@ -495,7 +495,7 @@
 server, some people have reported problems with
 permissions.  Enabling WRITE=YES in the samba
 configuration is said to fix/workaround it.
-Disclaimer: I haven't investigated enough to know the
+Disclaimer: I haven&rsquo;t investigated enough to know the
 implications of enabling that option, nor do I know
 whether there is something which <small>CVS</small> could be doing
 differently in order to avoid the problem.  If you find
@@ -608,7 +608,7 @@
 <p>There is currently no way of quoting tabs or linefeeds in the
 filename, &lsquo;<samp>=</samp>&rsquo; in <var>attrname</var>,
 &lsquo;<samp>;</samp>&rsquo; in <var>attrval</var>, etc.  Note: some 
implementations also
-don't handle a NUL character in any of the fields, but
+don&rsquo;t handle a NUL character in any of the fields, but
 implementations are encouraged to allow it.
 </p>
 <p>By convention, <var>attrname</var> starting with 
&lsquo;<samp>_</samp>&rsquo; is for an attribute given
@@ -803,9 +803,9 @@
 <p>By default, the &lsquo;<tt>modules</tt>&rsquo; file behaves as
 described above.  If the modules file is very large,
 storing it as a flat text file may make looking up
-modules slow (I'm not sure whether this is as much of a
+modules slow (I&rsquo;m not sure whether this is as much of a
 concern now as when <small>CVS</small> first evolved this
-feature; I haven't seen benchmarks).  Therefore, by
+feature; I haven&rsquo;t seen benchmarks).  Therefore, by
 making appropriate edits to the <small>CVS</small> source code
 one can store the modules file in a database which
 implements the <code>ndbm</code> interface, such as Berkeley
@@ -963,9 +963,9 @@
 <p>The timezone on the timestamp in CVS/Entries (local or
 universal) should be the same as the operating system
 stores for the timestamp of the file itself.  For
-example, on Unix the file's timestamp is in universal
+example, on Unix the file&rsquo;s timestamp is in universal
 time (UT), so the timestamp in CVS/Entries should be
-too.  On <small>VMS</small>, the file's timestamp is in local
+too.  On <small>VMS</small>, the file&rsquo;s timestamp is in local
 time, so <small>CVS</small> on <small>VMS</small> should use local time.
 This rule is so that files do not appear to be modified
 merely because the timezone changed (for example, to or
@@ -1299,7 +1299,7 @@
 times the size of the code to be under <small>CVS</small> for the
 repository (you will eventually outgrow this, but not
 for a while).  On the machines on which the developers
-will be working, you'll want disk space for
+will be working, you&rsquo;ll want disk space for
 approximately one working directory for each developer
 (either the entire tree or a portion of it, depending
 on what each developer uses).
@@ -1328,7 +1328,7 @@
 repository.
 </p>
 <p><code>cvs init</code> will enable history logging; if you
-don't want that, remove the history file after running
+don&rsquo;t want that, remove the history file after running
 <code>cvs init</code>.  See section <a href="cvs_18.html#SEC178">The history 
file</a>.
 </p>
 <hr size="6">
@@ -1431,17 +1431,17 @@
 <p>The main thing to consider is that working directories
 point to the repository.  The simplest way to deal with
 a moved repository is to just get a fresh working
-directory after the move.  Of course, you'll want to
+directory after the move.  Of course, you&rsquo;ll want to
 make sure that the old working directory had been
 checked in before the move, or you figured out some
-other way to make sure that you don't lose any
+other way to make sure that you don&rsquo;t lose any
 changes.  If you really do want to reuse the existing
 working directory, it should be possible with manual
 surgery on the &lsquo;<tt>CVS/Repository</tt>&rsquo; files.  You can
 see <a href="#SEC19">How data is stored in the working directory</a>, for 
information on
 the &lsquo;<tt>CVS/Repository</tt>&rsquo; and &lsquo;<tt>CVS/Root</tt>&rsquo; 
files, but
 unless you are sure you want to bother, it probably
-isn't worth it.
+isn&rsquo;t worth it.
 </p>
 <hr size="6">
 <a name="Remote-repositories"></a>
@@ -1613,7 +1613,7 @@
 the local machine &lsquo;<samp>toe.example.com</samp>&rsquo;, and the
 server machine is &lsquo;<samp>faun.example.org</samp>&rsquo;.  On
 faun, put the following line into the file
-&lsquo;<tt>.rhosts</tt>&rsquo; in &lsquo;<samp>bach</samp>&rsquo;'s home 
directory:
+&lsquo;<tt>.rhosts</tt>&rsquo; in &lsquo;<samp>bach</samp>&rsquo;&rsquo;s home 
directory:
 </p>
 <table><tr><td>&nbsp;</td><td><pre class="example">toe.example.com  mozart
 </pre></td></tr></table>
@@ -1826,7 +1826,7 @@
 <a name="IDX83"></a>
 <p>Because the client stores and transmits passwords in
 cleartext (almost&mdash;see <a href="#SEC32">Security considerations with 
password authentication</a>, for details), a separate <small>CVS</small> 
password
-file is generally used, so people don't compromise
+file is generally used, so people don&rsquo;t compromise
 their regular passwords when they access the
 repository.  This file is
 &lsquo;<tt>$CVSROOT/CVSROOT/passwd</tt>&rsquo; (see section <a 
href="#SEC20">The administrative files</a>).  It uses a colon-separated
@@ -1880,7 +1880,7 @@
 different <small>CVS</small> usernames is that <small>CVS</small> will log 
their
 actions under those names: when <code>melissa</code> commits
 a change to a project, the checkin is recorded in the
-project's history under the name <code>melissa</code>, not
+project&rsquo;s history under the name <code>melissa</code>, not
 <code>pubcvs</code>.  And the reason to have them share a
 system username is so that you can arrange permissions
 in the relevant area of the repository such that only
@@ -1907,7 +1907,7 @@
 </pre></td></tr></table>
 
 <p>When the password field is omitted or empty, then the
-client's authentication attempt will succeed with any
+client&rsquo;s authentication attempt will succeed with any
 password, including the empty string.  However, the
 colon after the <small>CVS</small> username is always necessary,
 even if the password is empty.
@@ -1919,7 +1919,7 @@
 authentication as described above.  But if it does not
 find the user, or if the <small>CVS</small> &lsquo;<tt>passwd</tt>&rsquo; file
 does not exist, then the server can try to authenticate
-the username and password using the operating system's
+the username and password using the operating system&rsquo;s
 user-lookup routines (this &quot;fallback&quot; behavior can be
 disabled by setting <code>SystemAuth=no</code> in the
 <small>CVS</small> &lsquo;<tt>config</tt>&rsquo; file, see section <a 
href="cvs_18.html#SEC180">The CVSROOT/config configuration file</a>).
@@ -1980,7 +1980,7 @@
 </p>
 <p>Be aware, also, that falling back to system
 authentication might be a security risk: <small>CVS</small>
-operations would then be authenticated with that user's
+operations would then be authenticated with that user&rsquo;s
 regular login password, and the password flies across
 the network in plaintext.  See <a href="#SEC32">Security considerations with 
password authentication</a> for more on this.
 This may be more of a problem with PAM authentication
@@ -2021,7 +2021,7 @@
 is normal to edit the &lsquo;<tt>passwd</tt>&rsquo; file in-place,
 rather than via <small>CVS</small>.  This is because of the
 possible security risks of having the &lsquo;<tt>passwd</tt>&rsquo;
-file checked out to people's working copies.  If you do
+file checked out to people&rsquo;s working copies.  If you do
 want to include the &lsquo;<tt>passwd</tt>&rsquo; file in checkouts of
 &lsquo;<tt>$CVSROOT/CVSROOT</tt>&rsquo;, see <a href="cvs_18.html#SEC177">The 
checkoutlist file</a>.
 </p>
@@ -2060,12 +2060,12 @@
 cvs checkout someproj
 </pre></td></tr></table>
 
-<p>However, unless you're connecting to a public-access
-repository (i.e., one where that username doesn't
-require a password), you'll need to supply a password or <em>log in</em> first.
+<p>However, unless you&rsquo;re connecting to a public-access
+repository (i.e., one where that username doesn&rsquo;t
+require a password), you&rsquo;ll need to supply a password or <em>log in</em> 
first.
 Logging in verifies your password with the repository and stores it in a file.
-It's done with the <code>login</code> command, which will
-prompt you interactively for the password if you didn't supply one as part of
+It&rsquo;s done with the <code>login</code> command, which will
+prompt you interactively for the password if you didn&rsquo;t supply one as 
part of
 <var>$CVSROOT</var>:
 </p>
 <table><tr><td>&nbsp;</td><td><pre class="example">cvs -d 
:pserver:address@hidden:/usr/local/cvsroot login
@@ -2081,13 +2081,13 @@
 the server.  If the verification succeeds, then that
 combination of username, host, repository, and password
 is permanently recorded, so future transactions with
-that repository won't require you to run <code>cvs
+that repository won&rsquo;t require you to run <code>cvs
 login</code>.  (If verification fails, <small>CVS</small> will exit
 complaining that the password was incorrect, and
 nothing will be recorded.)
 </p>
 <p>The records are stored, by default, in the file
-&lsquo;<tt>$HOME/.cvspass</tt>&rsquo;.  That file's format is
+&lsquo;<tt>$HOME/.cvspass</tt>&rsquo;.  That file&rsquo;s format is
 human-readable, and to a degree human-editable, but
 note that the passwords are not stored in
 cleartext&mdash;they are trivially encoded to protect them
@@ -2112,7 +2112,7 @@
 </pre></td></tr></table>
 
 <p>should just work (unless the password changes on the
-server side, in which case you'll have to re-run
+server side, in which case you&rsquo;ll have to re-run
 <code>cvs login</code>).
 </p>
 <p>Note that if the &lsquo;<samp>:pserver:</samp>&rsquo; were not present in
@@ -2124,7 +2124,7 @@
 are running <small>CVS</small> commands from within it, there is
 no longer any need to specify the repository
 explicitly, because <small>CVS</small> can deduce the repository
-from the working copy's &lsquo;<tt>CVS</tt>&rsquo; subdirectory.
+from the working copy&rsquo;s &lsquo;<tt>CVS</tt>&rsquo; subdirectory.
 </p>
 <a name="IDX86"></a>
 <p>The password for a given remote repository can be
@@ -2431,7 +2431,7 @@
 jrandom
 </pre></td></tr></table>
 
-<p>        (Don't forget the newline after the last user.)
+<p>        (Don&rsquo;t forget the newline after the last user.)
 </p>
 <p>        &quot;Exclusion&quot; means explicitly listing everyone
 who has <em>write</em> access&mdash;if the file
@@ -2454,7 +2454,7 @@
 &lsquo;<tt>writers</tt>&rsquo; files contain cvs usernames, which may
 or may not be the same as system usernames.
 </p>
-<p>        Here is a complete description of the server's
+<p>        Here is a complete description of the server&rsquo;s
 behavior in deciding whether to grant read-only or
 read-write access:
 </p>

Index: Tests/ccvs_res/cvs_21.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/ccvs_res/cvs_21.html,v
retrieving revision 1.27
retrieving revision 1.28
diff -u -b -r1.27 -r1.28
--- Tests/ccvs_res/cvs_21.html  5 Feb 2007 15:30:22 -0000       1.27
+++ Tests/ccvs_res/cvs_21.html  3 Oct 2007 09:34:37 -0000       1.28
@@ -134,8 +134,8 @@
 <dd><p>This message indicates that you removed a file, and
 someone else modified it.  To resolve the conflict,
 first run &lsquo;<samp>cvs add <var>file</var></samp>&rsquo;.  If desired, look
-at the other party's modification to decide whether you
-still want to remove it.  If you don't want to remove
+at the other party&rsquo;s modification to decide whether you
+still want to remove it.  If you don&rsquo;t want to remove
 it, stop here.  If you do want to remove it, proceed
 with &lsquo;<samp>cvs remove <var>file</var></samp>&rsquo; and commit your
 removal.
@@ -146,7 +146,7 @@
 </pre></td></tr></table>
 <p>This message has been happening in a non-reproducible,
 occasional way when we run the client/server testsuite,
-both on Red Hat Linux 3.0.3 and 4.1.  We haven't been
+both on Red Hat Linux 3.0.3 and 4.1.  We haven&rsquo;t been
 able to figure out what causes it, nor is it known
 whether it is specific to linux (or even to this
 particular machine!).  If the problem does occur on
@@ -212,7 +212,7 @@
 running the <small>CVS</small> client and it is having trouble
 connecting to the server.  Current versions of <small>CVS</small>
 should print a much more specific error message.  If
-you get this message when you didn't mean to run the
+you get this message when you didn&rsquo;t mean to run the
 client at all, you probably forgot to specify
 <code>:local:</code>, as described in <a href="cvs_2.html#SEC9">The 
Repository</a>.
 </p>
@@ -278,7 +278,7 @@
 <dd><p>There is a known bug in the server for <small>CVS</small> 1.9.18
 and older which can cause this.  For me, this was
 reproducible if I used the &lsquo;<samp>-t</samp>&rsquo; global option.  It
-was fixed by Andy Piper's 14 Nov 1997 change to
+was fixed by Andy Piper&rsquo;s 14 Nov 1997 change to
 src/filesubr.c, if anyone is curious.
 If you see the message,
 you probably can just retry the operation which failed,
@@ -339,7 +339,7 @@
 </p>
 </dd>
 <dt> <code>cvs [checkout aborted]: no such tag <var>tag</var></code></dt>
-<dd><p>This message means that <small>CVS</small> isn't familiar with
+<dd><p>This message means that <small>CVS</small> isn&rsquo;t familiar with
 the tag <var>tag</var>.  Usually this means that you have
 mistyped a tag name; however there are (relatively
 obscure) cases in which <small>CVS</small> will require you to
@@ -374,8 +374,8 @@
 </dd>
 <dt> <code>cvs [server aborted]: received broken pipe signal</code></dt>
 <dd><p>This message seems to be caused by a hard-to-track-down
-bug in <small>CVS</small> or the systems it runs on (we don't
-know&mdash;we haven't tracked it down yet!).  It seems to
+bug in <small>CVS</small> or the systems it runs on (we don&rsquo;t
+know&mdash;we haven&rsquo;t tracked it down yet!).  It seems to
 happen only after a <small>CVS</small> command has completed, and
 you should be able to just ignore the message.
 However, if you have discovered information concerning its
@@ -407,7 +407,7 @@
 older expects the logfile as an argument whereas the
 &lsquo;<tt>log.pl</tt>&rsquo; from <small>CVS</small> 1.5 and newer expects the
 logfile to be specified with a &lsquo;<samp>-f</samp>&rsquo; option.  Of
-course, if you don't need &lsquo;<tt>log.pl</tt>&rsquo; you can just
+course, if you don&rsquo;t need &lsquo;<tt>log.pl</tt>&rsquo; you can just
 comment it out of &lsquo;<tt>loginfo</tt>&rsquo;.
 </p>
 </dd>
@@ -530,13 +530,13 @@
 <dt> <code>:ext:</code></dt>
 <dd><p>Try running the rsh program from the command line.  For
 example: &quot;rsh servername cvs -v&quot; should print <small>CVS</small>
-version information.  If this doesn't work, you need to
+version information.  If this doesn&rsquo;t work, you need to
 fix it before you can worry about <small>CVS</small> problems.
 </p>
 <a name="IDX319"></a>
 </dd>
 <dt> <code>:server:</code></dt>
-<dd><p>You don't need a command line rsh program to use this
+<dd><p>You don&rsquo;t need a command line rsh program to use this
 access method, but if you have an rsh program around,
 it may be useful as a debugging tool.  Follow the
 directions given for :ext:.
@@ -545,7 +545,7 @@
 </dd>
 <dt> <code>:pserver:</code></dt>
 <dd><p>Errors along the lines of &quot;connection refused&quot; typically 
indicate
-that inetd isn't even listening for connections on port 2401
+that inetd isn&rsquo;t even listening for connections on port 2401
 whereas errors like &quot;connection reset by peer&quot;,
 &quot;received broken pipe signal&quot;, &quot;recv() from server: EOF&quot;,
 or &quot;end of file from server&quot;
@@ -573,9 +573,9 @@
 ...
 </pre></td></tr></table>
 
-<p>then you're missing the &lsquo;<samp>pserver</samp>&rsquo; command at the 
end of the
+<p>then you&rsquo;re missing the &lsquo;<samp>pserver</samp>&rsquo; command at 
the end of the
 line in &lsquo;<tt>inetd.conf</tt>&rsquo;; check to make sure that the entire 
command
-is on one line and that it's complete.
+is on one line and that it&rsquo;s complete.
 </p>
 <p>Likewise, if you get something like:
 </p>
@@ -586,7 +586,7 @@
 ...
 </pre></td></tr></table>
 
-<p>then you've misspelled &lsquo;<samp>pserver</samp>&rsquo; in some way.  If 
it isn't
+<p>then you&rsquo;ve misspelled &lsquo;<samp>pserver</samp>&rsquo; in some 
way.  If it isn&rsquo;t
 obvious, check for invisible control characters (particularly
 carriage returns) in &lsquo;<tt>inetd.conf</tt>&rsquo;.
 </p>
@@ -600,12 +600,12 @@
 <p>After making that change and instructing inetd to
 re-read its configuration file, &quot;telnet servername
 2401&quot; should show you the text hello and then the
-server should close the connection.  If this doesn't
+server should close the connection.  If this doesn&rsquo;t
 work, you need to fix it before you can worry about
 <small>CVS</small> problems.
 </p>
 <p>On AIX systems, the system will often have its own
-program trying to use port 2401.  This is AIX's problem
+program trying to use port 2401.  This is AIX&rsquo;s problem
 in the sense that port 2401 is registered for use with
 <small>CVS</small>.  I hear that there is an AIX patch available
 to address this problem.
@@ -620,7 +620,7 @@
 cvs [server aborted]: can't chdir(/root): Permission denied
 </pre></td></tr></table>
 
-<p>then you probably haven't specified &lsquo;<samp>-f</samp>&rsquo; in 
&lsquo;<tt>inetd.conf</tt>&rsquo;.
+<p>then you probably haven&rsquo;t specified &lsquo;<samp>-f</samp>&rsquo; in 
&lsquo;<tt>inetd.conf</tt>&rsquo;.
 (In releases prior to <small>CVS</small> 1.11.1, this problem can be caused by
 your system setting the <code>$HOME</code> environment variable
 for programs being run by inetd.  In this case, you can either
@@ -628,8 +628,8 @@
 <small>CVS</small>, or you can use <code>env</code> to run <small>CVS</small> 
with a pristine
 environment.)
 </p>
-<p>If you can connect successfully for a while but then can't,
-you've probably hit inetd's rate limit.
+<p>If you can connect successfully for a while but then can&rsquo;t,
+you&rsquo;ve probably hit inetd&rsquo;s rate limit.
 (If inetd receives too many requests for the same service
 in a short period of time, it assumes that something is wrong
 and temporarily disables the service.)
@@ -677,7 +677,7 @@
 If you are running <small>CVS</small> 1.9.18 or older, and
 <code>cvs update</code> finds a conflict and tries to
 merge, as described in <a href="cvs_10.html#SEC86">Conflicts example</a>, but
-doesn't tell you there were conflicts, then you may
+doesn&rsquo;t tell you there were conflicts, then you may
 have an old version of <small>RCS</small>.  The easiest solution
 probably is to upgrade to a current version of
 <small>CVS</small>, which does not rely on external <small>RCS</small>

Index: Tests/ccvs_res/cvs_22.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/ccvs_res/cvs_22.html,v
retrieving revision 1.22
retrieving revision 1.23
diff -u -b -r1.22 -r1.23
--- Tests/ccvs_res/cvs_22.html  5 Feb 2007 15:30:22 -0000       1.22
+++ Tests/ccvs_res/cvs_22.html  3 Oct 2007 09:34:37 -0000       1.23
@@ -83,7 +83,7 @@
 use <small>CVS</small>, at least).
 </p>
 <p>In addition, the following persons have helped by
-telling me about mistakes I've made:
+telling me about mistakes I&rsquo;ve made:
 </p>
 <table><tr><td>&nbsp;</td><td><pre class="display">Roxanne Brunskill 
&lt;<tt>address@hidden</tt>&gt;,
 Kathy Dyer &lt;<tt>address@hidden</tt>&gt;,

Index: Tests/ccvs_res/cvs_23.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/ccvs_res/cvs_23.html,v
retrieving revision 1.23
retrieving revision 1.24
diff -u -b -r1.23 -r1.24
--- Tests/ccvs_res/cvs_23.html  5 Feb 2007 15:30:22 -0000       1.23
+++ Tests/ccvs_res/cvs_23.html  3 Oct 2007 09:34:37 -0000       1.24
@@ -137,7 +137,7 @@
 send email to <code>address@hidden</code>.  Note
 that submissions to <code>bug-cvs</code> may be distributed
 under the terms of the <small>GNU</small> Public License, so if
-you don't like this, don't submit them.  There is
+you don&rsquo;t like this, don&rsquo;t submit them.  There is
 usually no justification for sending mail directly to
 one of the <small>CVS</small> maintainers rather than to
 <code>bug-cvs</code>; those maintainers who want to hear
@@ -154,7 +154,7 @@
 <p>People often ask if there is a list of known bugs or
 whether a particular bug is a known one.  The file
 <small>BUGS</small> in the <small>CVS</small> source distribution is one
-list of known bugs, but it doesn't necessarily try to
+list of known bugs, but it doesn&rsquo;t necessarily try to
 be comprehensive.  Perhaps there will never be a
 comprehensive, detailed list of known bugs.
 </p>

Index: Tests/ccvs_res/cvs_25.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/ccvs_res/cvs_25.html,v
retrieving revision 1.20
retrieving revision 1.21
diff -u -b -r1.20 -r1.21
--- Tests/ccvs_res/cvs_25.html  5 Feb 2007 15:30:22 -0000       1.20
+++ Tests/ccvs_res/cvs_25.html  3 Oct 2007 09:34:37 -0000       1.21
@@ -189,7 +189,7 @@
 <tr><td></td><td valign="top"><a href="cvs_5.html#IDX123">Example, branch 
merge</a></td><td valign="top"><a href="cvs_5.html#SEC60">5.6 Merging an entire 
branch</a></td></tr>
 <tr><td></td><td valign="top"><a href="cvs_18.html#SEC162">Excluding 
directories, in modules file</a></td><td valign="top"><a 
href="cvs_18.html#SEC162">C.1.4 Excluding directories</a></td></tr>
 <tr><td></td><td valign="top"><a href="cvs_18.html#IDX262">Exit status, of 
commitinfo</a></td><td valign="top"><a href="cvs_18.html#SEC168">C.3.2 
Commitinfo</a></td></tr>
-<tr><td></td><td valign="top"><a href="cvs_16.html#SEC116">Exit status, of 
CVS</a></td><td valign="top"><a href="cvs_16.html#SEC116">A.2 CVS's exit 
status</a></td></tr>
+<tr><td></td><td valign="top"><a href="cvs_16.html#SEC116">Exit status, of 
CVS</a></td><td valign="top"><a href="cvs_16.html#SEC116">A.2 CVS&rsquo;s exit 
status</a></td></tr>
 <tr><td></td><td valign="top"><a href="cvs_21.html#IDX317">Exit status, of 
editor</a></td><td valign="top"><a href="cvs_21.html#SEC184">F.1 Partial list 
of error messages</a></td></tr>
 <tr><td></td><td valign="top"><a href="cvs_8.html#IDX134">Exit status, of 
taginfo</a></td><td valign="top"><a href="cvs_8.html#SEC78">8.3 User-defined 
logging</a></td></tr>
 <tr><td></td><td valign="top"><a href="cvs_18.html#IDX268">Exit status, of 
&lsquo;<tt>verifymsg</tt>&rsquo;</a></td><td valign="top"><a 
href="cvs_18.html#SEC169">C.3.3 Verifying log messages</a></td></tr>

Index: Tests/ccvs_res/cvs_27.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/ccvs_res/cvs_27.html,v
retrieving revision 1.18
retrieving revision 1.19
diff -u -b -r1.18 -r1.19
--- Tests/ccvs_res/cvs_27.html  5 Feb 2007 15:30:22 -0000       1.18
+++ Tests/ccvs_res/cvs_27.html  3 Oct 2007 09:34:37 -0000       1.19
@@ -164,7 +164,7 @@
 <tr><td></td><td valign="top"><a href="cvs_16.html#IDX204">RCSBIN, 
overriding</a></td><td valign="top"><a href="cvs_16.html#SEC118">A.4 Global 
options</a></td></tr>
 <tr><td></td><td valign="top"><a href="cvs_12.html#IDX190">RCSfile 
keyword</a></td><td valign="top"><a href="cvs_12.html#SEC99">12.1 Keyword 
List</a></td></tr>
 <tr><td></td><td valign="top"><a href="cvs_18.html#SEC175">rcsinfo (admin 
file)</a></td><td valign="top"><a href="cvs_18.html#SEC175">C.4 
Rcsinfo</a></td></tr>
-<tr><td></td><td valign="top"><a href="cvs_16.html#SEC146">rdiff 
(subcommand)</a></td><td valign="top"><a href="cvs_16.html#SEC146">A.14 
rdiff&mdash;'patch' format diffs between releases</a></td></tr>
+<tr><td></td><td valign="top"><a href="cvs_16.html#SEC146">rdiff 
(subcommand)</a></td><td valign="top"><a href="cvs_16.html#SEC146">A.14 
rdiff&mdash;&rsquo;patch&rsquo; format diffs between releases</a></td></tr>
 <tr><td></td><td valign="top"><a href="cvs_16.html#IDX214">Read-only files, 
and -r</a></td><td valign="top"><a href="cvs_16.html#SEC118">A.4 Global 
options</a></td></tr>
 <tr><td></td><td valign="top"><a href="cvs_19.html#IDX295">Read-only files, 
and CVSREAD</a></td><td valign="top"><a href="cvs_19.html#SEC181">D. All 
environment variables which affect CVS</a></td></tr>
 <tr><td></td><td valign="top"><a href="cvs_10.html#IDX164">Read-only files, 
and watches</a></td><td valign="top"><a href="cvs_10.html#SEC90">10.6.1 Telling 
CVS to watch certain files</a></td></tr>

Index: Tests/ccvs_res/cvs_4.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/ccvs_res/cvs_4.html,v
retrieving revision 1.26
retrieving revision 1.27
diff -u -b -r1.26 -r1.27
--- Tests/ccvs_res/cvs_4.html   5 Feb 2007 15:30:22 -0000       1.26
+++ Tests/ccvs_res/cvs_4.html   3 Oct 2007 09:34:37 -0000       1.27
@@ -61,7 +61,7 @@
 </tr></table>
 <h1 class="chapter"> 4. Revisions </h1>
 
-<p>For many uses of <small>CVS</small>, one doesn't need to worry
+<p>For many uses of <small>CVS</small>, one doesn&rsquo;t need to worry
 too much about revision numbers; <small>CVS</small> assigns
 numbers such as <code>1.1</code>, <code>1.2</code>, and so on, and
 that is all one needs to know.  However, some people
@@ -212,7 +212,7 @@
 files to be committed even if they are not modified.
 </p>
 <p>For example, to bring all your files up to
-revision 3.0 (including those that haven't changed),
+revision 3.0 (including those that haven&rsquo;t changed),
 you might invoke:
 </p>
 <table><tr><td>&nbsp;</td><td><pre class="example">$ cvs commit -r 3.0
@@ -288,14 +288,14 @@
 <code>BASE</code> and <code>HEAD</code>, to avoid conflicts with
 actual tag names.
 </p>
-<p>You'll want to choose some convention for naming tags,
+<p>You&rsquo;ll want to choose some convention for naming tags,
 based on information such as the name of the program
 and the version number of the release.  For example,
 one might take the name of the program, immediately
 followed by the version number with &lsquo;<samp>.</samp>&rsquo; changed to
 &lsquo;<samp>-</samp>&rsquo;, so that <small>CVS</small> 1.9 would be tagged 
with the name
 <code>cvs1-9</code>.  If you choose a consistent convention,
-then you won't constantly be guessing whether a tag is
+then you won&rsquo;t constantly be guessing whether a tag is
 <code>cvs-1-9</code> or <code>cvs1_9</code> or what.  You might
 even want to consider enforcing your convention in the
 taginfo file (see section <a href="cvs_8.html#SEC78">User-defined logging</a>).
@@ -569,7 +569,7 @@
 </p>
 <p><strong>WARNING: Moving branch tags is very dangerous!  If you think
 you need the <code>-B</code> option, think again and ask your 
<small>CVS</small>
-administrator about it (if that isn't you).  There is almost certainly
+administrator about it (if that isn&rsquo;t you).  There is almost certainly
 another way to accomplish what you want to accomplish.</strong>
 </p>
 <a name="IDX110"></a>
@@ -597,7 +597,7 @@
 </p>
 <p><strong>WARNING: Moving branch tags is very dangerous!  If you think you
 need the <code>-B</code> option, think again and ask your <small>CVS</small>
-administrator about it (if that isn't you).  There is almost certainly
+administrator about it (if that isn&rsquo;t you).  There is almost certainly
 another way to accomplish what you want to accomplish.</strong>
 </p>
 <a name="IDX114"></a>
@@ -646,7 +646,7 @@
 corresponding to what is being tagged.  Files which did
 not exist yet, or which were already removed, simply
 omit the tag, and <small>CVS</small> knows to treat the absence
-of a tag as meaning that the file didn't exist as of
+of a tag as meaning that the file didn&rsquo;t exist as of
 that tag.
 </p>
 <p>However, this can lose a small amount of information.
@@ -667,7 +667,7 @@
 moving a tag.  If one moved a tag without &lsquo;<samp>-a</samp>&rsquo;,
 then the tag in the removed files might still refer to
 the old revision, rather than reflecting the fact that
-the file had been removed.  I don't think this is
+the file had been removed.  I don&rsquo;t think this is
 necessary if &lsquo;<samp>-r</samp>&rsquo; is specified, as noted above.
 </p>
 <hr size="6">
@@ -692,7 +692,7 @@
 <h2 class="section"> 4.9 Sticky tags </h2>
 
 
-<p>Sometimes a working copy's revision has extra data
+<p>Sometimes a working copy&rsquo;s revision has extra data
 associated with it, for example it might be on a branch
 (see section <a href="cvs_5.html#SEC54">Branching and merging</a>), or 
restricted to
 versions prior to a certain date by &lsquo;<samp>checkout -D</samp>&rsquo;
@@ -701,8 +701,8 @@
 working copy &ndash; we refer to it as <em>sticky</em>.
 </p>
 <p>Most of the time, stickiness is an obscure aspect of
-<small>CVS</small> that you don't need to think about.  However,
-even if you don't want to use the feature, you may need
+<small>CVS</small> that you don&rsquo;t need to think about.  However,
+even if you don&rsquo;t want to use the feature, you may need
 to know <em>something</em> about sticky tags (for
 example, how to avoid them!).
 </p>
@@ -765,7 +765,7 @@
 $
 </pre></td></tr></table>
 
-<p>However, this isn't the easiest way, if you are asking
+<p>However, this isn&rsquo;t the easiest way, if you are asking
 how to undo a previous checkin (in this example, put
 &lsquo;<tt>file1</tt>&rsquo; back to the way it was as of revision
 1.1).  In that case you are better off using the

Index: Tests/ccvs_res/cvs_5.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/ccvs_res/cvs_5.html,v
retrieving revision 1.33
retrieving revision 1.34
diff -u -b -r1.33 -r1.34
--- Tests/ccvs_res/cvs_5.html   5 Feb 2007 15:30:22 -0000       1.33
+++ Tests/ccvs_res/cvs_5.html   3 Oct 2007 09:34:37 -0000       1.34
@@ -150,7 +150,7 @@
 <h2 class="section"> 5.2 Creating a branch </h2>
 
 <p>You can create a branch with <code>tag -b</code>; for
-example, assuming you're in a working copy:
+example, assuming you&rsquo;re in a working copy:
 </p>
 <table><tr><td>&nbsp;</td><td><pre class="example">$ cvs tag -b rel-1-0-patches
 </pre></td></tr></table>
@@ -176,7 +176,7 @@
 <p>&lsquo;<samp>-r rel-1-0</samp>&rsquo; says that this branch should be
 rooted at the revision that
 corresponds to the tag &lsquo;<samp>rel-1-0</samp>&rsquo;.  It need not
-be the most recent revision &ndash; it's often useful to
+be the most recent revision &ndash; it&rsquo;s often useful to
 split a branch off an old revision (for example, when
 fixing a bug in a past release otherwise known to be
 stable).
@@ -253,7 +253,7 @@
 <p>To find out what branch a working copy is on, you can
 use the &lsquo;<samp>status</samp>&rsquo; command.  In its output, look for
 the field named &lsquo;<samp>Sticky tag</samp>&rsquo; (see section <a 
href="cvs_4.html#SEC53">Sticky tags</a>)
-&ndash; that's <small>CVS</small>'s way of telling you the branch, if
+&ndash; that&rsquo;s <small>CVS</small>&rsquo;s way of telling you the branch, 
if
 any, of the current working files:
 </p>
 <table><tr><td>&nbsp;</td><td><pre class="example">$ cvs status -v driver.c 
backend.c
@@ -286,12 +286,12 @@
 
 </pre></td></tr></table>
 
-<p>Don't be confused by the fact that the branch numbers
+<p>Don&rsquo;t be confused by the fact that the branch numbers
 for each file are different (&lsquo;<samp>1.7.2</samp>&rsquo; and
 &lsquo;<samp>1.4.2</samp>&rsquo; respectively).  The branch tag is the
 same, &lsquo;<samp>rel-1-0-patches</samp>&rsquo;, and the files are
 indeed on the same branch.  The numbers simply reflect
-the point in each file's revision history at which the
+the point in each file&rsquo;s revision history at which the
 branch was made.  In the above example, one can deduce
 that &lsquo;<samp>driver.c</samp>&rsquo; had been through more changes than
 &lsquo;<samp>backend.c</samp>&rsquo; before this branch was created.
@@ -320,7 +320,7 @@
 </tr></table>
 <h2 class="section"> 5.4 Branches and revisions </h2>
 
-<p>Ordinarily, a file's revision history is a linear
+<p>Ordinarily, a file&rsquo;s revision history is a linear
 series of increments (see section <a href="cvs_4.html#SEC45">Revision 
numbers</a>):
 </p>
 <table><tr><td>&nbsp;</td><td><pre class="example">       +-----+    +-----+   
 +-----+    +-----+    +-----+

Index: Tests/ccvs_res/cvs_7.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/ccvs_res/cvs_7.html,v
retrieving revision 1.28
retrieving revision 1.29
diff -u -b -r1.28 -r1.29
--- Tests/ccvs_res/cvs_7.html   5 Feb 2007 15:30:22 -0000       1.28
+++ Tests/ccvs_res/cvs_7.html   3 Oct 2007 09:34:37 -0000       1.29
@@ -339,7 +339,7 @@
 existed.
 </p>
 <p>The way that you remove a directory is to remove all
-the files in it.  You don't remove the directory
+the files in it.  You don&rsquo;t remove the directory
 itself; there is no way to do that.
 Instead you specify the &lsquo;<samp>-P</samp>&rsquo; option to
 <code>cvs update</code> or <code>cvs checkout</code>,

Index: Tests/ccvs_res/cvs_8.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/ccvs_res/cvs_8.html,v
retrieving revision 1.25
retrieving revision 1.26
diff -u -b -r1.25 -r1.26
--- Tests/ccvs_res/cvs_8.html   5 Feb 2007 15:30:22 -0000       1.25
+++ Tests/ccvs_res/cvs_8.html   3 Oct 2007 09:34:37 -0000       1.26
@@ -239,7 +239,7 @@
 The <code>ssfile line 1</code> line was checked in by
 <code>mary</code> on March 27.  Then, on March 28, <code>joe</code>
 added a line <code>ssfile line 2</code>, without modifying
-the <code>ssfile line 1</code> line.  This report doesn't
+the <code>ssfile line 1</code> line.  This report doesn&rsquo;t
 tell you anything about lines which have been deleted
 or replaced; you need to use <code>cvs diff</code> for that
 (see section <a href="cvs_16.html#SEC130">diff&mdash;Show differences between 
revisions</a>).

Index: Tests/ccvs_res/cvs_toc.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/ccvs_res/cvs_toc.html,v
retrieving revision 1.23
retrieving revision 1.24
diff -u -b -r1.23 -r1.24
--- Tests/ccvs_res/cvs_toc.html 5 Feb 2007 15:30:22 -0000       1.23
+++ Tests/ccvs_res/cvs_toc.html 3 Oct 2007 09:34:37 -0000       1.24
@@ -209,7 +209,7 @@
   <li><a name="TOC114" href="cvs_16.html#SEC114">A. Guide to CVS commands</a>
   <ul class="toc">
     <li><a name="TOC115" href="cvs_16.html#SEC115">A.1 Overall structure of 
CVS commands</a></li>
-    <li><a name="TOC116" href="cvs_16.html#SEC116">A.2 CVS's exit 
status</a></li>
+    <li><a name="TOC116" href="cvs_16.html#SEC116">A.2 CVS&rsquo;s exit 
status</a></li>
     <li><a name="TOC117" href="cvs_16.html#SEC117">A.3 Default options and the 
~/.cvsrc file</a></li>
     <li><a name="TOC118" href="cvs_16.html#SEC118">A.4 Global options</a></li>
     <li><a name="TOC119" href="cvs_16.html#SEC119">A.5 Common command 
options</a></li>
@@ -260,7 +260,7 @@
       <li><a name="TOC144" href="cvs_16.html#SEC144">A.13.1 log 
options</a></li>
       <li><a name="TOC145" href="cvs_16.html#SEC145">A.13.2 log 
examples</a></li>
     </ul></li>
-    <li><a name="TOC146" href="cvs_16.html#SEC146">A.14 rdiff&mdash;'patch' 
format diffs between releases</a>
+    <li><a name="TOC146" href="cvs_16.html#SEC146">A.14 
rdiff&mdash;&rsquo;patch&rsquo; format diffs between releases</a>
     <ul class="toc">
       <li><a name="TOC147" href="cvs_16.html#SEC147">A.14.1 rdiff 
options</a></li>
       <li><a name="TOC148" href="cvs_16.html#SEC148">A.14.2 rdiff 
examples</a></li>

Index: Tests/documentlanguage_res/multi_lang.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/documentlanguage_res/multi_lang.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- Tests/documentlanguage_res/multi_lang.html  30 Sep 2007 12:47:13 -0000      
1.1
+++ Tests/documentlanguage_res/multi_lang.html  3 Oct 2007 09:34:37 -0000       
1.2
@@ -47,7 +47,7 @@
 <tr><td valign="middle" align="left">[<a href="#SEC_Top" title="Couverture 
(top) du document">Top</a>]</td>
 <td valign="middle" align="left">[Table des mati&egrave;res]</td>
 <td valign="middle" align="left">[Index]</td>
-<td valign="middle" align="left">[<a href="#SEC_About" title="A propos (page 
d'aide)"> ? </a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="A propos (page 
d&rsquo;aide)"> ? </a>]</td>
 </tr></table>
 <h1 class="settitle">Multi language file</h1>
 
@@ -68,8 +68,8 @@
 <a name="chapter-fr_005fNOWHERE"></a>
 <a name="SEC1"></a>
 <table cellpadding="1" cellspacing="1" border="0">
-<tr><td valign="middle" align="left">[<a href="#SEC_Top" title="Section 
pr&eacute;c&eacute;dente dans l'ordre de lecture"> &lt; </a>]</td>
-<td valign="middle" align="left">[<a href="#SEC2" title="Section suivante dans 
l'ordre de lecture"> &gt; </a>]</td>
+<tr><td valign="middle" align="left">[<a href="#SEC_Top" title="Section 
pr&eacute;c&eacute;dente dans l&rsquo;ordre de lecture"> &lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#SEC2" title="Section suivante dans 
l&rsquo;ordre de lecture"> &gt; </a>]</td>
 <td valign="middle" align="left"> &nbsp; </td>
 <td valign="middle" align="left">[ &lt;&lt; ]</td>
 <td valign="middle" align="left">[<a href="#SEC_Top" title="Section 
sup&eacute;rieure">Plus haut</a>]</td>
@@ -81,7 +81,7 @@
 <td valign="middle" align="left">[<a href="#SEC_Top" title="Couverture (top) 
du document">Top</a>]</td>
 <td valign="middle" align="left">[Table des mati&egrave;res]</td>
 <td valign="middle" align="left">[Index]</td>
-<td valign="middle" align="left">[<a href="#SEC_About" title="A propos (page 
d'aide)"> ? </a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="A propos (page 
d&rsquo;aide)"> ? </a>]</td>
 </tr></table>
 <h1 class="chapter"> 1. Fr_NOWHERE </h1>
 
@@ -96,8 +96,8 @@
 <a name="sub-fr_005fNOWHERE"></a>
 <a name="SEC2"></a>
 <table cellpadding="1" cellspacing="1" border="0">
-<tr><td valign="middle" align="left">[<a href="#SEC1" title="Section 
pr&eacute;c&eacute;dente dans l'ordre de lecture"> &lt; </a>]</td>
-<td valign="middle" align="left">[<a href="#SEC3" title="Section suivante dans 
l'ordre de lecture"> &gt; </a>]</td>
+<tr><td valign="middle" align="left">[<a href="#SEC1" title="Section 
pr&eacute;c&eacute;dente dans l&rsquo;ordre de lecture"> &lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#SEC3" title="Section suivante dans 
l&rsquo;ordre de lecture"> &gt; </a>]</td>
 <td valign="middle" align="left"> &nbsp; </td>
 <td valign="middle" align="left">[<a href="#SEC1" title="D&eacute;but de ce 
chapitre ou chapitre pr&eacute;c&eacute;dent"> &lt;&lt; </a>]</td>
 <td valign="middle" align="left">[<a href="#SEC1" title="Section 
sup&eacute;rieure">Plus haut</a>]</td>
@@ -109,7 +109,7 @@
 <td valign="middle" align="left">[<a href="#SEC_Top" title="Couverture (top) 
du document">Top</a>]</td>
 <td valign="middle" align="left">[Table des mati&egrave;res]</td>
 <td valign="middle" align="left">[Index]</td>
-<td valign="middle" align="left">[<a href="#SEC_About" title="A propos (page 
d'aide)"> ? </a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="A propos (page 
d&rsquo;aide)"> ? </a>]</td>
 </tr></table>
 <h2 class="section"> 1.1 fr_NOWHERE section </h2>
 

Index: Tests/floats_res/float.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/floats_res/float.html,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -b -r1.13 -r1.14
--- Tests/floats_res/float.html 30 Sep 2007 12:47:14 -0000      1.13
+++ Tests/floats_res/float.html 3 Oct 2007 09:34:37 -0000       1.14
@@ -464,7 +464,7 @@
 <a href="manual.html#text-with-a-lot-of-features">cross ref: (manual)text with 
a lot of features</a>.
 </p>
 <p>And now a ref (without manual with a printed manual) 
-section `title' in <cite>printed manual title</cite>.
+section &lsquo;title&rsquo; in <cite>printed manual title</cite>.
 </p>
 <p>A ref to float without type <a href="#label-but-no-type">label but no 
type</a>.
 </p>

Index: 
Tests/formatting_res/_0021_005f_0022_0023_0024_0025_0026_0027_0028_0029_002a_002b_002d_002e_002f_003b_003c_003d_003e_003f_005b_005c_005d_005e_005f_0060_007c_007e.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/formatting_res/_0021_005f_0022_0023_0024_0025_0026_0027_0028_0029_002a_002b_002d_002e_002f_003b_003c_003d_003e_003f_005b_005c_005d_005e_005f_0060_007c_007e.html,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -b -r1.9 -r1.10
--- 
Tests/formatting_res/_0021_005f_0022_0023_0024_0025_0026_0027_0028_0029_002a_002b_002d_002e_002f_003b_003c_003d_003e_003f_005b_005c_005d_005e_005f_0060_007c_007e.html
      5 Feb 2007 15:30:22 -0000       1.9
+++ 
Tests/formatting_res/_0021_005f_0022_0023_0024_0025_0026_0027_0028_0029_002a_002b_002d_002e_002f_003b_003c_003d_003e_003f_005b_005c_005d_005e_005f_0060_007c_007e.html
      3 Oct 2007 09:34:37 -0000       1.10
@@ -59,7 +59,7 @@
 <td valign="middle" align="left">[<a href="node_test_refs_abt.html#SEC_About" 
title="About (help)"> ? </a>]</td>
 </tr></table>
 <hr size="1">
-<h3 class="node"> !_&quot;#$%&amp;'()*+-./;&lt;=&gt;?[\]^_`|~ </h3>
+<h3 class="node"> !_&quot;#$%&amp;&rsquo;()*+-./;&lt;=&gt;?[\]^_&lsquo;|~ </h3>
 <table><tr><td>&nbsp;</td><td><pre class="example">id: 
_0021_005f_0022_0023_0024_0025_0026_0027_0028_0029_002a_002b_002d_002e_002f_003b_003c_003d_003e_003f_005b_005c_005d_005e_005f_0060_007c_007e
 </pre></td></tr></table>
 

Index: Tests/formatting_res/chapter_test_refs.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/formatting_res/chapter_test_refs.html,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -b -r1.10 -r1.11
--- Tests/formatting_res/chapter_test_refs.html 5 Feb 2007 15:30:22 -0000       
1.10
+++ Tests/formatting_res/chapter_test_refs.html 3 Oct 2007 09:34:38 -0000       
1.11
@@ -85,7 +85,7 @@
 <a name="SEC3"></a>
 <h3 class="subheading"> Testing local nodes </h3>
 
-<p><tt>!_&quot;#$%&amp;'()*+-./;&lt;=&gt;?[\]^_`|~</tt> <a 
href="chapter_test_refs_1.html#g_t_0021_005f_0022_0023_0024_0025_0026_0027_0028_0029_002a_002b_002d_002e_002f_003b_003c_003d_003e_003f_005b_005c_005d_005e_005f_0060_007c_007e">!_&quot;#$%&amp;'()*+-./;&lt;=&gt;?[\]^_`|~</a><br>
+<p><tt>!_&quot;#$%&amp;'()*+-./;&lt;=&gt;?[\]^_`|~</tt> <a 
href="chapter_test_refs_1.html#g_t_0021_005f_0022_0023_0024_0025_0026_0027_0028_0029_002a_002b_002d_002e_002f_003b_003c_003d_003e_003f_005b_005c_005d_005e_005f_0060_007c_007e">!_&quot;#$%&amp;&rsquo;()*+-./;&lt;=&gt;?[\]^_&lsquo;|~</a><br>
 </p><table><tr><td>&nbsp;</td><td><pre class="example">target: 
#_0021_005f_0022_0023_0024_0025_0026_0027_0028_0029_002a_002b_002d_002e_002f_003b_003c_003d_003e_003f_005b_005c_005d_005e_005f_0060_007c_007e
 </pre></td></tr></table>
 

Index: Tests/formatting_res/chapter_test_refs_1.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/formatting_res/chapter_test_refs_1.html,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -b -r1.8 -r1.9
--- Tests/formatting_res/chapter_test_refs_1.html       5 Feb 2007 15:30:22 
-0000       1.8
+++ Tests/formatting_res/chapter_test_refs_1.html       3 Oct 2007 09:34:38 
-0000       1.9
@@ -69,7 +69,7 @@
 </pre></td></tr></table>
 
 <table class="menu" border="0" cellspacing="0">
-<tr><td align="left" valign="top"><a 
href="#g_t_0021_005f_0022_0023_0024_0025_0026_0027_0028_0029_002a_002b_002d_002e_002f_003b_003c_003d_003e_003f_005b_005c_005d_005e_005f_0060_007c_007e">&bull;
 !_&quot;#$%&amp;'()*+-./;&lt;=&gt;?[\]^_`|~</a></td><td>&nbsp;&nbsp;</td><td 
align="left" valign="top">
+<tr><td align="left" valign="top"><a 
href="#g_t_0021_005f_0022_0023_0024_0025_0026_0027_0028_0029_002a_002b_002d_002e_002f_003b_003c_003d_003e_003f_005b_005c_005d_005e_005f_0060_007c_007e">&bull;
 
!_&quot;#$%&amp;&rsquo;()*+-./;&lt;=&gt;?[\]^_&lsquo;|~</a></td><td>&nbsp;&nbsp;</td><td
 align="left" valign="top">
 </td></tr>
 <tr><td align="left" valign="top"><a href="#local-node">&bull; local 
node</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">
 </td></tr>

Index: Tests/formatting_res/clean.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/formatting_res/clean.html,v
retrieving revision 1.28
retrieving revision 1.29
diff -u -b -r1.28 -r1.29
--- Tests/formatting_res/clean.html     30 Sep 2007 12:47:14 -0000      1.28
+++ Tests/formatting_res/clean.html     3 Oct 2007 09:34:38 -0000       1.29
@@ -438,10 +438,10 @@
 @&quot;{U} &Uuml; 
 @~n &ntilde;
 @^a &acirc;
-@'e &eacute;
+@&rsquo;e &eacute;
 @=o &#333;
address@hidden &igrave;
-@'address@hidden &iacute; 
+@&lsquo;i &igrave;
+@&rsquo;address@hidden &iacute; 
 @dotless{i} i
 </p>
 <p>@* <br>
@@ -782,9 +782,9 @@
 <dd><p>d&ndash;eftypemethod
 </p></dd></dl>
 
-<p><code>@xref{chapter, cross ref name, title, file name, manual}</code> See 
<a href="file name.html#chapter">cross ref name: (file name)chapter</a> section 
`title' in <cite>manual</cite>.
-<code>@ref{chapter, cross ref name, title, file name, manual}</code> <a 
href="file name.html#chapter">cross ref name: (file name)chapter</a> section 
`title' in <cite>manual</cite>
-<code>@pxref{chapter, cross ref name, title, file name, manual}</code> see <a 
href="file name.html#chapter">cross ref name: (file name)chapter</a> section 
`title' in <cite>manual</cite>
+<p><code>@xref{chapter, cross ref name, title, file name, manual}</code> See 
<a href="file name.html#chapter">cross ref name: (file name)chapter</a> section 
&lsquo;title&rsquo; in <cite>manual</cite>.
+<code>@ref{chapter, cross ref name, title, file name, manual}</code> <a 
href="file name.html#chapter">cross ref name: (file name)chapter</a> section 
&lsquo;title&rsquo; in <cite>manual</cite>
+<code>@pxref{chapter, cross ref name, title, file name, manual}</code> see <a 
href="file name.html#chapter">cross ref name: (file name)chapter</a> section 
&lsquo;title&rsquo; in <cite>manual</cite>
 <code>@inforef{chapter, cross ref name, file name}</code> See <a href="file 
name.html#chapter">cross ref name: (file name)chapter</a>
 </p>
 <p><code>@ref{chapter}</code> <a href="#SEC1">chapter</a>
@@ -792,31 +792,31 @@
 <code>@ref{chapter,cross ref name}</code> <a href="#SEC1">cross ref name</a>
 <code>@ref{chapter,,title}</code> <a href="#SEC1">title</a>
 <code>@ref{chapter,,,file name}</code> <a href="file name.html#chapter">(file 
name)chapter</a>
-<code>@ref{chapter,,,,manual}</code> section `chapter' in <cite>manual</cite>
+<code>@ref{chapter,,,,manual}</code> section &lsquo;chapter&rsquo; in 
<cite>manual</cite>
 <code>@ref{node,cross ref name}</code> <a href="#node">cross ref name</a>
 <code>@ref{node,,title}</code> <a href="#node">title</a>
 <code>@ref{node,,,file name}</code> <a href="file name.html#node">(file 
name)node</a>
-<code>@ref{node,,,,manual}</code> section `node' in <cite>manual</cite>
+<code>@ref{node,,,,manual}</code> section &lsquo;node&rsquo; in 
<cite>manual</cite>
 <code>@ref{chapter,cross ref name,title,}</code> <a href="#SEC1">title</a>
 <code>@ref{chapter,cross ref name,,file name}</code> <a href="file 
name.html#chapter">cross ref name: (file name)chapter</a>
-<code>@ref{chapter,cross ref name,,,manual}</code> section `chapter' in 
<cite>manual</cite>
+<code>@ref{chapter,cross ref name,,,manual}</code> section 
&lsquo;chapter&rsquo; in <cite>manual</cite>
 <code>@ref{node,cross ref name,title,}</code> <a href="#node">title</a>
 <code>@ref{node,cross ref name,,file name}</code> <a href="file 
name.html#node">cross ref name: (file name)node</a>
-<code>@ref{node,cross ref name,,,manual}</code> section `node' in 
<cite>manual</cite>
+<code>@ref{node,cross ref name,,,manual}</code> section &lsquo;node&rsquo; in 
<cite>manual</cite>
 <code>@ref{chapter,cross ref name,title,file name}</code> <a href="file 
name.html#chapter">cross ref name: (file name)chapter</a>
-<code>@ref{chapter,cross ref name,title,,manual}</code> section `title' in 
<cite>manual</cite>
+<code>@ref{chapter,cross ref name,title,,manual}</code> section 
&lsquo;title&rsquo; in <cite>manual</cite>
 <code>@ref{node,cross ref name,title,file name}</code> <a href="file 
name.html#node">cross ref name: (file name)node</a>
-<code>@ref{node,cross ref name,title,,manual}</code> section `title' in 
<cite>manual</cite>
-<code>@ref{chapter,cross ref name,title, file name, manual}</code> <a 
href="file name.html#chapter">cross ref name: (file name)chapter</a> section 
`title' in <cite>manual</cite>
-<code>@ref{node,cross ref name,title, file name, manual}</code> <a href="file 
name.html#node">cross ref name: (file name)node</a> section `title' in 
<cite>manual</cite>
+<code>@ref{node,cross ref name,title,,manual}</code> section 
&lsquo;title&rsquo; in <cite>manual</cite>
+<code>@ref{chapter,cross ref name,title, file name, manual}</code> <a 
href="file name.html#chapter">cross ref name: (file name)chapter</a> section 
&lsquo;title&rsquo; in <cite>manual</cite>
+<code>@ref{node,cross ref name,title, file name, manual}</code> <a href="file 
name.html#node">cross ref name: (file name)node</a> section &lsquo;title&rsquo; 
in <cite>manual</cite>
 <code>@ref{chapter,,title,file name}</code> <a href="file 
name.html#chapter">(file name)chapter</a>
-<code>@ref{chapter,,title,,manual}</code> section `title' in 
<cite>manual</cite>
+<code>@ref{chapter,,title,,manual}</code> section &lsquo;title&rsquo; in 
<cite>manual</cite>
 <code>@ref{node,,title,file name}</code> <a href="file name.html#node">(file 
name)node</a>
-<code>@ref{node,,title,,manual}</code> section `title' in <cite>manual</cite>
-<code>@ref{chapter,,title, file name, manual}</code> <a href="file 
name.html#chapter">(file name)chapter</a> section `title' in <cite>manual</cite>
-<code>@ref{node,,title, file name, manual}</code> <a href="file 
name.html#node">(file name)node</a> section `title' in <cite>manual</cite>
-<code>@ref{chapter,,,file name,manual}</code> <a href="file 
name.html#chapter">(file name)chapter</a> section `chapter' in 
<cite>manual</cite>
-<code>@ref{node,,,file name,manual}</code> <a href="file name.html#node">(file 
name)node</a> section `node' in <cite>manual</cite>
+<code>@ref{node,,title,,manual}</code> section &lsquo;title&rsquo; in 
<cite>manual</cite>
+<code>@ref{chapter,,title, file name, manual}</code> <a href="file 
name.html#chapter">(file name)chapter</a> section &lsquo;title&rsquo; in 
<cite>manual</cite>
+<code>@ref{node,,title, file name, manual}</code> <a href="file 
name.html#node">(file name)node</a> section &lsquo;title&rsquo; in 
<cite>manual</cite>
+<code>@ref{chapter,,,file name,manual}</code> <a href="file 
name.html#chapter">(file name)chapter</a> section &lsquo;chapter&rsquo; in 
<cite>manual</cite>
+<code>@ref{node,,,file name,manual}</code> <a href="file name.html#node">(file 
name)node</a> section &lsquo;node&rsquo; in <cite>manual</cite>
 </p>
 <p><code>@inforef{chapter, cross ref name, file name}</code> See <a href="file 
name.html#chapter">cross ref name: (file name)chapter</a>
 <code>@inforef{chapter}</code> 
@@ -888,10 +888,10 @@
 @&quot;{U} &Uuml; 
 @~n &ntilde;
 @^a &acirc;
-@'e &eacute;
+@&rsquo;e &eacute;
 @=o &#333;
address@hidden &igrave;
-@'address@hidden &iacute; 
+@&lsquo;i &igrave;
+@&rsquo;address@hidden &iacute; 
 @dotless{i} i
 </p>
 <p>@* <br>
@@ -1211,9 +1211,9 @@
 <dd><p>d&ndash;eftypemethod
 </p></dd></dl>
 
-<p><code>@xref{chapter, cross ref name, title, file name, manual}</code> See 
<a href="file name.html#chapter">cross ref name: (file name)chapter</a> section 
`title' in <cite>manual</cite>.
-<code>@ref{chapter, cross ref name, title, file name, manual}</code> <a 
href="file name.html#chapter">cross ref name: (file name)chapter</a> section 
`title' in <cite>manual</cite>
-<code>@pxref{chapter, cross ref name, title, file name, manual}</code> see <a 
href="file name.html#chapter">cross ref name: (file name)chapter</a> section 
`title' in <cite>manual</cite>
+<p><code>@xref{chapter, cross ref name, title, file name, manual}</code> See 
<a href="file name.html#chapter">cross ref name: (file name)chapter</a> section 
&lsquo;title&rsquo; in <cite>manual</cite>.
+<code>@ref{chapter, cross ref name, title, file name, manual}</code> <a 
href="file name.html#chapter">cross ref name: (file name)chapter</a> section 
&lsquo;title&rsquo; in <cite>manual</cite>
+<code>@pxref{chapter, cross ref name, title, file name, manual}</code> see <a 
href="file name.html#chapter">cross ref name: (file name)chapter</a> section 
&lsquo;title&rsquo; in <cite>manual</cite>
 <code>@inforef{chapter, cross ref name, file name}</code> See <a href="file 
name.html#chapter">cross ref name: (file name)chapter</a>
 </p>
 <p><code>@ref{chapter}</code> <a href="#SEC1">chapter</a>
@@ -1221,31 +1221,31 @@
 <code>@ref{chapter,cross ref name}</code> <a href="#SEC1">cross ref name</a>
 <code>@ref{chapter,,title}</code> <a href="#SEC1">title</a>
 <code>@ref{chapter,,,file name}</code> <a href="file name.html#chapter">(file 
name)chapter</a>
-<code>@ref{chapter,,,,manual}</code> section `chapter' in <cite>manual</cite>
+<code>@ref{chapter,,,,manual}</code> section &lsquo;chapter&rsquo; in 
<cite>manual</cite>
 <code>@ref{node,cross ref name}</code> <a href="#node">cross ref name</a>
 <code>@ref{node,,title}</code> <a href="#node">title</a>
 <code>@ref{node,,,file name}</code> <a href="file name.html#node">(file 
name)node</a>
-<code>@ref{node,,,,manual}</code> section `node' in <cite>manual</cite>
+<code>@ref{node,,,,manual}</code> section &lsquo;node&rsquo; in 
<cite>manual</cite>
 <code>@ref{chapter,cross ref name,title,}</code> <a href="#SEC1">title</a>
 <code>@ref{chapter,cross ref name,,file name}</code> <a href="file 
name.html#chapter">cross ref name: (file name)chapter</a>
-<code>@ref{chapter,cross ref name,,,manual}</code> section `chapter' in 
<cite>manual</cite>
+<code>@ref{chapter,cross ref name,,,manual}</code> section 
&lsquo;chapter&rsquo; in <cite>manual</cite>
 <code>@ref{node,cross ref name,title,}</code> <a href="#node">title</a>
 <code>@ref{node,cross ref name,,file name}</code> <a href="file 
name.html#node">cross ref name: (file name)node</a>
-<code>@ref{node,cross ref name,,,manual}</code> section `node' in 
<cite>manual</cite>
+<code>@ref{node,cross ref name,,,manual}</code> section &lsquo;node&rsquo; in 
<cite>manual</cite>
 <code>@ref{chapter,cross ref name,title,file name}</code> <a href="file 
name.html#chapter">cross ref name: (file name)chapter</a>
-<code>@ref{chapter,cross ref name,title,,manual}</code> section `title' in 
<cite>manual</cite>
+<code>@ref{chapter,cross ref name,title,,manual}</code> section 
&lsquo;title&rsquo; in <cite>manual</cite>
 <code>@ref{node,cross ref name,title,file name}</code> <a href="file 
name.html#node">cross ref name: (file name)node</a>
-<code>@ref{node,cross ref name,title,,manual}</code> section `title' in 
<cite>manual</cite>
-<code>@ref{chapter,cross ref name,title, file name, manual}</code> <a 
href="file name.html#chapter">cross ref name: (file name)chapter</a> section 
`title' in <cite>manual</cite>
-<code>@ref{node,cross ref name,title, file name, manual}</code> <a href="file 
name.html#node">cross ref name: (file name)node</a> section `title' in 
<cite>manual</cite>
+<code>@ref{node,cross ref name,title,,manual}</code> section 
&lsquo;title&rsquo; in <cite>manual</cite>
+<code>@ref{chapter,cross ref name,title, file name, manual}</code> <a 
href="file name.html#chapter">cross ref name: (file name)chapter</a> section 
&lsquo;title&rsquo; in <cite>manual</cite>
+<code>@ref{node,cross ref name,title, file name, manual}</code> <a href="file 
name.html#node">cross ref name: (file name)node</a> section &lsquo;title&rsquo; 
in <cite>manual</cite>
 <code>@ref{chapter,,title,file name}</code> <a href="file 
name.html#chapter">(file name)chapter</a>
-<code>@ref{chapter,,title,,manual}</code> section `title' in 
<cite>manual</cite>
+<code>@ref{chapter,,title,,manual}</code> section &lsquo;title&rsquo; in 
<cite>manual</cite>
 <code>@ref{node,,title,file name}</code> <a href="file name.html#node">(file 
name)node</a>
-<code>@ref{node,,title,,manual}</code> section `title' in <cite>manual</cite>
-<code>@ref{chapter,,title, file name, manual}</code> <a href="file 
name.html#chapter">(file name)chapter</a> section `title' in <cite>manual</cite>
-<code>@ref{node,,title, file name, manual}</code> <a href="file 
name.html#node">(file name)node</a> section `title' in <cite>manual</cite>
-<code>@ref{chapter,,,file name,manual}</code> <a href="file 
name.html#chapter">(file name)chapter</a> section `chapter' in 
<cite>manual</cite>
-<code>@ref{node,,,file name,manual}</code> <a href="file name.html#node">(file 
name)node</a> section `node' in <cite>manual</cite>
+<code>@ref{node,,title,,manual}</code> section &lsquo;title&rsquo; in 
<cite>manual</cite>
+<code>@ref{chapter,,title, file name, manual}</code> <a href="file 
name.html#chapter">(file name)chapter</a> section &lsquo;title&rsquo; in 
<cite>manual</cite>
+<code>@ref{node,,title, file name, manual}</code> <a href="file 
name.html#node">(file name)node</a> section &lsquo;title&rsquo; in 
<cite>manual</cite>
+<code>@ref{chapter,,,file name,manual}</code> <a href="file 
name.html#chapter">(file name)chapter</a> section &lsquo;chapter&rsquo; in 
<cite>manual</cite>
+<code>@ref{node,,,file name,manual}</code> <a href="file name.html#node">(file 
name)node</a> section &lsquo;node&rsquo; in <cite>manual</cite>
 </p>
 <p><code>@inforef{chapter, cross ref name, file name}</code> See <a href="file 
name.html#chapter">cross ref name: (file name)chapter</a>
 <code>@inforef{chapter}</code> 

Index: Tests/formatting_res/comments.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/formatting_res/comments.html,v
retrieving revision 1.25
retrieving revision 1.26
diff -u -b -r1.25 -r1.26
--- Tests/formatting_res/comments.html  30 Sep 2007 12:47:14 -0000      1.25
+++ Tests/formatting_res/comments.html  3 Oct 2007 09:34:38 -0000       1.26
@@ -95,7 +95,7 @@
 <h3 class="subheading"> ignore arg </h3>
 
 
-<p>Commands doesn't accept anything after a non numerical arg on the line
+<p>Commands doesn&rsquo;t accept anything after a non numerical arg on the line
 and ignore things after a numerical arg
 </p>
 <p>@paragraphindent asis @paragraphindent 0 @paragraphindent none 
@paragraphindent 4 @firstparagraphindent none @exampleindent 6 @exampleindent 6 
@footnotestyle @footnotestyle </p>
@@ -133,7 +133,7 @@
   noindent after space at beginning of line
          page at beginning of line
 
-After page on it's own line.
+After page on it&rsquo;s own line.
 </p>
 <p>@page    @noindent @refill  @novalidate  something
 </p>

Index: Tests/formatting_res/comments_redefined.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/formatting_res/comments_redefined.html,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -b -r1.6 -r1.7
--- Tests/formatting_res/comments_redefined.html        30 Sep 2007 12:47:15 
-0000      1.6
+++ Tests/formatting_res/comments_redefined.html        3 Oct 2007 09:34:38 
-0000       1.7
@@ -99,7 +99,7 @@
 <h3 class="subheading"> ignore arg </h3>
 
 
-<p>Commands doesn't accept anything after a non numerical arg on the line
+<p>Commands doesn&rsquo;t accept anything after a non numerical arg on the line
 and ignore things after a numerical arg
 </p>
 <p>@paragraphindent asis @paragraphindent 0 @paragraphindent none 
@paragraphindent 4 @firstparagraphindent none @exampleindent 6 @exampleindent 6 
@footnotestyle @footnotestyle </p>
@@ -137,7 +137,7 @@
   noindent after space at beginning of line
          page at beginning of line
 
-After page on it's own line.
+After page on it&rsquo;s own line.
 </p>
 <p>@page    @noindent @refill  @novalidate  something
 </p>

Index: Tests/formatting_res/exotic_formatting.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/formatting_res/exotic_formatting.html,v
retrieving revision 1.63
retrieving revision 1.64
diff -u -b -r1.63 -r1.64
--- Tests/formatting_res/exotic_formatting.html 3 Oct 2007 07:39:30 -0000       
1.63
+++ Tests/formatting_res/exotic_formatting.html 3 Oct 2007 09:34:38 -0000       
1.64
@@ -545,7 +545,7 @@
 strong: 
<strong>&ldquo;simple-double&ndash;three&mdash;four&mdash;-&rdquo;</strong> <br>
 kbd: <kbd>``simple-double--three---four----''</kbd> <br>
 </p>
-<p>``simple-double--three&mdash;four&mdash;-''<br>
+<p>&lsquo;&lsquo;simple-double--three&mdash;four&mdash;-&rsquo;&rsquo;<br>
 </p>
 <a name="IDX1"></a>
 <a name="IDX2"></a>
@@ -556,16 +556,16 @@
 @&quot;{U} &Uuml; 
 @~n &ntilde;
 @^a &acirc;
-@'e &eacute;
+@&rsquo;e &eacute;
 @=o &#333;
address@hidden &igrave;
-@'{e} &eacute;
-@'address@hidden &iacute; 
+@&lsquo;i &igrave;
+@&rsquo;{e} &eacute;
+@&rsquo;address@hidden &iacute; 
 @dotless{i} i
 @dotless{ij} ij
address@hidden@=E} &#274;` 
+@&lsquo;address@hidden &#274;` 
 @l{} &#322;
-@,{@'C} &#262;,
+@,{@&rsquo;C} &#262;,
 @,c &ccedil;
 @,c@&quot;u &ccedil;&uuml; <br>
 </p>
@@ -574,10 +574,10 @@
 <br>
 @,@&quot;u ,&uuml;
 </p>
-<p>Invalid use of @':<br>
-@' '
+<p>Invalid use of @&rsquo;:<br>
+@&rsquo; &rsquo;
 <br>
-@'@&quot;u @'&quot;u
+@&rsquo;@&quot;u @'&quot;u
 </p>
 <p>@dotless{truc} truc
 </p>
@@ -1174,9 +1174,9 @@
 <tr><td colspan="2"><p>d&ndash;eftypemethod
 </p></td></tr></table>
 
-<p><code>@xref{c---hapter@@, cross r---ef name@@, t---itle@@, file n---ame@@, 
ma---nual@@}</code> See <a href="../file 
n---ame@@/c_002d_002d_002dhapter_0040.html#c_002d_002d_002dhapter_0040">cross 
r&mdash;ef name@: (file n&mdash;ame@)c&mdash;hapter@</a> section 
`t&mdash;itle@' in <cite>ma&mdash;nual@</cite>
-<code>@ref{chapter, cross ref name, title, file name, manual}</code> <a 
href="../file name/chapter.html#chapter">cross ref name: (file name)chapter</a> 
section `title' in <cite>manual</cite>
-<code>@pxref{chapter, cross ref name, title, file name, manual}</code> see <a 
href="../file name/chapter.html#chapter">cross ref name: (file name)chapter</a> 
section `title' in <cite>manual</cite>
+<p><code>@xref{c---hapter@@, cross r---ef name@@, t---itle@@, file n---ame@@, 
ma---nual@@}</code> See <a href="../file 
n---ame@@/c_002d_002d_002dhapter_0040.html#c_002d_002d_002dhapter_0040">cross 
r&mdash;ef name@: (file n&mdash;ame@)c&mdash;hapter@</a> section 
&lsquo;t&mdash;itle@&rsquo; in <cite>ma&mdash;nual@</cite>
+<code>@ref{chapter, cross ref name, title, file name, manual}</code> <a 
href="../file name/chapter.html#chapter">cross ref name: (file name)chapter</a> 
section &lsquo;title&rsquo; in <cite>manual</cite>
+<code>@pxref{chapter, cross ref name, title, file name, manual}</code> see <a 
href="../file name/chapter.html#chapter">cross ref name: (file name)chapter</a> 
section &lsquo;title&rsquo; in <cite>manual</cite>
 <code>@inforef{chapter, cross ref name, file name}</code> See <a href="../file 
name/chapter.html#chapter">cross ref name: (file name)chapter</a>
 </p>
 <p><code>@ref{chapter}</code> <a 
href="exotic_formatting_2.html#SEC1">chapter</a>
@@ -1188,40 +1188,40 @@
 <code>@ref{chapter,cross ref name}</code> <a 
href="exotic_formatting_2.html#SEC1">cross ref name</a>
 <code>@ref{chapter,,title}</code> <a 
href="exotic_formatting_2.html#SEC1">title</a>
 <code>@ref{chapter,,,file name}</code> <a href="../file 
name/chapter.html#chapter">(file name)chapter</a>
-<code>@ref{chapter,,,,manual}</code> section `chapter' in <cite>manual</cite>
+<code>@ref{chapter,,,,manual}</code> section &lsquo;chapter&rsquo; in 
<cite>manual</cite>
 <code>@ref{node,cross ref name}</code> @ref{node,cross ref name}
 <code>@ref{node,,title}</code> @ref{node,,title}
 <code>@ref{node,,,file name}</code> <a href="../file 
name/node.html#node">(file name)node</a>
-<code>@ref{node,,,,manual}</code> section `node' in <cite>manual</cite>
+<code>@ref{node,,,,manual}</code> section &lsquo;node&rsquo; in 
<cite>manual</cite>
 <code>@ref{chapter,cross ref name,title,}</code> <a 
href="exotic_formatting_2.html#SEC1">title</a>
 <code>@ref{chapter,cross ref name,,file name}</code> <a href="../file 
name/chapter.html#chapter">cross ref name: (file name)chapter</a>
-<code>@ref{chapter,cross ref name,,,manual}</code> section `chapter' in 
<cite>manual</cite>
+<code>@ref{chapter,cross ref name,,,manual}</code> section 
&lsquo;chapter&rsquo; in <cite>manual</cite>
 <code>@ref{node,cross ref name,title,}</code> @ref{node,cross ref name,title,}
 <code>@ref{node,cross ref name,,file name}</code> <a href="../file 
name/node.html#node">cross ref name: (file name)node</a>
-<code>@ref{node,cross ref name,,,manual}</code> section `node' in 
<cite>manual</cite>
+<code>@ref{node,cross ref name,,,manual}</code> section &lsquo;node&rsquo; in 
<cite>manual</cite>
 <code>@ref{chapter,cross ref name,title,file name}</code> <a href="../file 
name/chapter.html#chapter">cross ref name: (file name)chapter</a>
-<code>@ref{chapter,cross ref name,title,,manual}</code> section `title' in 
<cite>manual</cite>
+<code>@ref{chapter,cross ref name,title,,manual}</code> section 
&lsquo;title&rsquo; in <cite>manual</cite>
 <code>@ref{node,cross ref name,title,file name}</code> <a href="../file 
name/node.html#node">cross ref name: (file name)node</a>
-<code>@ref{node,cross ref name,title,,manual}</code> section `title' in 
<cite>manual</cite>
-<code>@ref{chapter,cross ref name,title, file name, manual}</code> <a 
href="../file name/chapter.html#chapter">cross ref name: (file name)chapter</a> 
section `title' in <cite>manual</cite>
-<code>@ref{node,cross ref name,title, file name, manual}</code> <a 
href="../file name/node.html#node">cross ref name: (file name)node</a> section 
`title' in <cite>manual</cite>
+<code>@ref{node,cross ref name,title,,manual}</code> section 
&lsquo;title&rsquo; in <cite>manual</cite>
+<code>@ref{chapter,cross ref name,title, file name, manual}</code> <a 
href="../file name/chapter.html#chapter">cross ref name: (file name)chapter</a> 
section &lsquo;title&rsquo; in <cite>manual</cite>
+<code>@ref{node,cross ref name,title, file name, manual}</code> <a 
href="../file name/node.html#node">cross ref name: (file name)node</a> section 
&lsquo;title&rsquo; in <cite>manual</cite>
 <code>@ref{chapter,,title,file name}</code> <a href="../file 
name/chapter.html#chapter">(file name)chapter</a>
-<code>@ref{chapter,,title,,manual}</code> section `title' in 
<cite>manual</cite>
+<code>@ref{chapter,,title,,manual}</code> section &lsquo;title&rsquo; in 
<cite>manual</cite>
 <code>@ref{node,,title,file name}</code> <a href="../file 
name/node.html#node">(file name)node</a>
-<code>@ref{node,,title,,manual}</code> section `title' in <cite>manual</cite>
-<code>@ref{chapter,,title, file name, manual}</code> <a href="../file 
name/chapter.html#chapter">(file name)chapter</a> section `title' in 
<cite>manual</cite>
-<code>@ref{node,,title, file name, manual}</code> <a href="../file 
name/node.html#node">(file name)node</a> section `title' in <cite>manual</cite>
-<code>@ref{chapter,,,file name,manual}</code> <a href="../file 
name/chapter.html#chapter">(file name)chapter</a> section `chapter' in 
<cite>manual</cite>
-<code>@ref{node,,,file name,manual}</code> <a href="../file 
name/node.html#node">(file name)node</a> section `node' in <cite>manual</cite>
+<code>@ref{node,,title,,manual}</code> section &lsquo;title&rsquo; in 
<cite>manual</cite>
+<code>@ref{chapter,,title, file name, manual}</code> <a href="../file 
name/chapter.html#chapter">(file name)chapter</a> section &lsquo;title&rsquo; 
in <cite>manual</cite>
+<code>@ref{node,,title, file name, manual}</code> <a href="../file 
name/node.html#node">(file name)node</a> section &lsquo;title&rsquo; in 
<cite>manual</cite>
+<code>@ref{chapter,,,file name,manual}</code> <a href="../file 
name/chapter.html#chapter">(file name)chapter</a> section &lsquo;chapter&rsquo; 
in <cite>manual</cite>
+<code>@ref{node,,,file name,manual}</code> <a href="../file 
name/node.html#node">(file name)node</a> section &lsquo;node&rsquo; in 
<cite>manual</cite>
 <code>@ref{,cross ref name,title,}</code> @ref{,cross ref name,title,}
 <code>@ref{,cross ref name,,file name}</code> <a href="../file 
name/index.html#Top">cross ref name: (file name)</a>
 <code>@ref{,cross ref name,,,manual}</code> <cite>manual</cite>
 <code>@ref{,cross ref name,title,file name}</code> <a href="../file 
name/index.html#Top">cross ref name: (file name)</a>
-<code>@ref{,cross ref name,title,,manual}</code> section `title' in 
<cite>manual</cite>
-<code>@ref{,cross ref name,title, file name, manual}</code> <a href="../file 
name/index.html#Top">cross ref name: (file name)</a> section `title' in 
<cite>manual</cite>
+<code>@ref{,cross ref name,title,,manual}</code> section &lsquo;title&rsquo; 
in <cite>manual</cite>
+<code>@ref{,cross ref name,title, file name, manual}</code> <a href="../file 
name/index.html#Top">cross ref name: (file name)</a> section 
&lsquo;title&rsquo; in <cite>manual</cite>
 <code>@ref{,,title,file name}</code> <a href="../file 
name/index.html#Top">(file name)</a>
-<code>@ref{,,title,,manual}</code> section `title' in <cite>manual</cite>
-<code>@ref{,,title, file name, manual}</code> <a href="../file 
name/index.html#Top">(file name)</a> section `title' in <cite>manual</cite>
+<code>@ref{,,title,,manual}</code> section &lsquo;title&rsquo; in 
<cite>manual</cite>
+<code>@ref{,,title, file name, manual}</code> <a href="../file 
name/index.html#Top">(file name)</a> section &lsquo;title&rsquo; in 
<cite>manual</cite>
 <code>@ref{,,,file name,manual}</code> <a href="../file 
name/index.html#Top">(file name)</a> <cite>manual</cite>
 </p>
 <p><code>@inforef{chapter, cross ref name, file name}</code> See <a 
href="../file name/chapter.html#chapter">cross ref name: (file name)chapter</a>
@@ -1238,7 +1238,7 @@
 </p>
 <p><code>@address@hidden, a @comma{} in cross
 ref, a address@hidden in title, a address@hidden in file, a @comma{} in manual 
name }</code>
-<a href="../a address@hidden in 
file/s_002d_002dect_002cion.html#s_002d_002dect_002cion">a , in cross ref: (a 
comma, in file)s&ndash;ect,ion</a> section `a comma, in title' in <cite>a , in 
manual name</cite>
+<a href="../a address@hidden in 
file/s_002d_002dect_002cion.html#s_002d_002dect_002cion">a , in cross ref: (a 
comma, in file)s&ndash;ect,ion</a> section &lsquo;a comma, in title&rsquo; in 
<cite>a , in manual name</cite>
 </p>
 <p><code>@address@hidden</code> <a 
href="exotic_formatting_3.html#SEC2">s&ndash;ect,ion</a>
 </p>

Index: Tests/formatting_res/formatting.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/formatting_res/formatting.html,v
retrieving revision 1.64
retrieving revision 1.65
diff -u -b -r1.64 -r1.65
--- Tests/formatting_res/formatting.html        3 Oct 2007 07:39:31 -0000       
1.64
+++ Tests/formatting_res/formatting.html        3 Oct 2007 09:34:38 -0000       
1.65
@@ -544,7 +544,7 @@
 strong: 
<strong>&ldquo;simple-double&ndash;three&mdash;four&mdash;-&rdquo;</strong> <br>
 kbd: <kbd>``simple-double--three---four----''</kbd> <br>
 </p>
-<p>``simple-double--three&mdash;four&mdash;-''<br>
+<p>&lsquo;&lsquo;simple-double--three&mdash;four&mdash;-&rsquo;&rsquo;<br>
 </p>
 <a name="IDX1"></a>
 <a name="IDX2"></a>
@@ -555,16 +555,16 @@
 @&quot;{U} &Uuml; 
 @~n &ntilde;
 @^a &acirc;
-@'e &eacute;
+@&rsquo;e &eacute;
 @=o &#333;
address@hidden &igrave;
-@'{e} &eacute;
-@'address@hidden &iacute; 
+@&lsquo;i &igrave;
+@&rsquo;{e} &eacute;
+@&rsquo;address@hidden &iacute; 
 @dotless{i} i
 @dotless{ij} ij
address@hidden@=E} &#274;` 
+@&lsquo;address@hidden &#274;` 
 @l{} &#322;
-@,{@'C} &#262;,
+@,{@&rsquo;C} &#262;,
 @,c &ccedil;
 @,c@&quot;u &ccedil;&uuml; <br>
 </p>
@@ -573,10 +573,10 @@
 <br>
 @,@&quot;u ,&uuml;
 </p>
-<p>Invalid use of @':<br>
-@' '
+<p>Invalid use of @&rsquo;:<br>
+@&rsquo; &rsquo;
 <br>
-@'@&quot;u @'&quot;u
+@&rsquo;@&quot;u @'&quot;u
 </p>
 <p>@dotless{truc} truc
 </p>
@@ -1029,9 +1029,9 @@
 <dd><p>d&ndash;eftypemethod
 </p></dd></dl>
 
-<p><code>@xref{c---hapter@@, cross r---ef name@@, t---itle@@, file n---ame@@, 
ma---nual@@}</code> See <a href="file 
n---ame@@.html#c_002d_002d_002dhapter_0040">cross r&mdash;ef name@: (file 
n&mdash;ame@)c&mdash;hapter@</a> section `t&mdash;itle@' in 
<cite>ma&mdash;nual@</cite>
-<code>@ref{chapter, cross ref name, title, file name, manual}</code> <a 
href="file name.html#chapter">cross ref name: (file name)chapter</a> section 
`title' in <cite>manual</cite>
-<code>@pxref{chapter, cross ref name, title, file name, manual}</code> see <a 
href="file name.html#chapter">cross ref name: (file name)chapter</a> section 
`title' in <cite>manual</cite>
+<p><code>@xref{c---hapter@@, cross r---ef name@@, t---itle@@, file n---ame@@, 
ma---nual@@}</code> See <a href="file 
n---ame@@.html#c_002d_002d_002dhapter_0040">cross r&mdash;ef name@: (file 
n&mdash;ame@)c&mdash;hapter@</a> section &lsquo;t&mdash;itle@&rsquo; in 
<cite>ma&mdash;nual@</cite>
+<code>@ref{chapter, cross ref name, title, file name, manual}</code> <a 
href="file name.html#chapter">cross ref name: (file name)chapter</a> section 
&lsquo;title&rsquo; in <cite>manual</cite>
+<code>@pxref{chapter, cross ref name, title, file name, manual}</code> see <a 
href="file name.html#chapter">cross ref name: (file name)chapter</a> section 
&lsquo;title&rsquo; in <cite>manual</cite>
 <code>@inforef{chapter, cross ref name, file name}</code> See <a href="file 
name.html#chapter">cross ref name: (file name)chapter</a>
 </p>
 <p><code>@ref{chapter}</code> <a href="#SEC1">chapter</a>
@@ -1043,40 +1043,40 @@
 <code>@ref{chapter,cross ref name}</code> <a href="#SEC1">cross ref name</a>
 <code>@ref{chapter,,title}</code> <a href="#SEC1">title</a>
 <code>@ref{chapter,,,file name}</code> <a href="file name.html#chapter">(file 
name)chapter</a>
-<code>@ref{chapter,,,,manual}</code> section `chapter' in <cite>manual</cite>
+<code>@ref{chapter,,,,manual}</code> section &lsquo;chapter&rsquo; in 
<cite>manual</cite>
 <code>@ref{node,cross ref name}</code> @ref{node,cross ref name}
 <code>@ref{node,,title}</code> @ref{node,,title}
 <code>@ref{node,,,file name}</code> <a href="file name.html#node">(file 
name)node</a>
-<code>@ref{node,,,,manual}</code> section `node' in <cite>manual</cite>
+<code>@ref{node,,,,manual}</code> section &lsquo;node&rsquo; in 
<cite>manual</cite>
 <code>@ref{chapter,cross ref name,title,}</code> <a href="#SEC1">title</a>
 <code>@ref{chapter,cross ref name,,file name}</code> <a href="file 
name.html#chapter">cross ref name: (file name)chapter</a>
-<code>@ref{chapter,cross ref name,,,manual}</code> section `chapter' in 
<cite>manual</cite>
+<code>@ref{chapter,cross ref name,,,manual}</code> section 
&lsquo;chapter&rsquo; in <cite>manual</cite>
 <code>@ref{node,cross ref name,title,}</code> @ref{node,cross ref name,title,}
 <code>@ref{node,cross ref name,,file name}</code> <a href="file 
name.html#node">cross ref name: (file name)node</a>
-<code>@ref{node,cross ref name,,,manual}</code> section `node' in 
<cite>manual</cite>
+<code>@ref{node,cross ref name,,,manual}</code> section &lsquo;node&rsquo; in 
<cite>manual</cite>
 <code>@ref{chapter,cross ref name,title,file name}</code> <a href="file 
name.html#chapter">cross ref name: (file name)chapter</a>
-<code>@ref{chapter,cross ref name,title,,manual}</code> section `title' in 
<cite>manual</cite>
+<code>@ref{chapter,cross ref name,title,,manual}</code> section 
&lsquo;title&rsquo; in <cite>manual</cite>
 <code>@ref{node,cross ref name,title,file name}</code> <a href="file 
name.html#node">cross ref name: (file name)node</a>
-<code>@ref{node,cross ref name,title,,manual}</code> section `title' in 
<cite>manual</cite>
-<code>@ref{chapter,cross ref name,title, file name, manual}</code> <a 
href="file name.html#chapter">cross ref name: (file name)chapter</a> section 
`title' in <cite>manual</cite>
-<code>@ref{node,cross ref name,title, file name, manual}</code> <a href="file 
name.html#node">cross ref name: (file name)node</a> section `title' in 
<cite>manual</cite>
+<code>@ref{node,cross ref name,title,,manual}</code> section 
&lsquo;title&rsquo; in <cite>manual</cite>
+<code>@ref{chapter,cross ref name,title, file name, manual}</code> <a 
href="file name.html#chapter">cross ref name: (file name)chapter</a> section 
&lsquo;title&rsquo; in <cite>manual</cite>
+<code>@ref{node,cross ref name,title, file name, manual}</code> <a href="file 
name.html#node">cross ref name: (file name)node</a> section &lsquo;title&rsquo; 
in <cite>manual</cite>
 <code>@ref{chapter,,title,file name}</code> <a href="file 
name.html#chapter">(file name)chapter</a>
-<code>@ref{chapter,,title,,manual}</code> section `title' in 
<cite>manual</cite>
+<code>@ref{chapter,,title,,manual}</code> section &lsquo;title&rsquo; in 
<cite>manual</cite>
 <code>@ref{node,,title,file name}</code> <a href="file name.html#node">(file 
name)node</a>
-<code>@ref{node,,title,,manual}</code> section `title' in <cite>manual</cite>
-<code>@ref{chapter,,title, file name, manual}</code> <a href="file 
name.html#chapter">(file name)chapter</a> section `title' in <cite>manual</cite>
-<code>@ref{node,,title, file name, manual}</code> <a href="file 
name.html#node">(file name)node</a> section `title' in <cite>manual</cite>
-<code>@ref{chapter,,,file name,manual}</code> <a href="file 
name.html#chapter">(file name)chapter</a> section `chapter' in 
<cite>manual</cite>
-<code>@ref{node,,,file name,manual}</code> <a href="file name.html#node">(file 
name)node</a> section `node' in <cite>manual</cite>
+<code>@ref{node,,title,,manual}</code> section &lsquo;title&rsquo; in 
<cite>manual</cite>
+<code>@ref{chapter,,title, file name, manual}</code> <a href="file 
name.html#chapter">(file name)chapter</a> section &lsquo;title&rsquo; in 
<cite>manual</cite>
+<code>@ref{node,,title, file name, manual}</code> <a href="file 
name.html#node">(file name)node</a> section &lsquo;title&rsquo; in 
<cite>manual</cite>
+<code>@ref{chapter,,,file name,manual}</code> <a href="file 
name.html#chapter">(file name)chapter</a> section &lsquo;chapter&rsquo; in 
<cite>manual</cite>
+<code>@ref{node,,,file name,manual}</code> <a href="file name.html#node">(file 
name)node</a> section &lsquo;node&rsquo; in <cite>manual</cite>
 <code>@ref{,cross ref name,title,}</code> @ref{,cross ref name,title,}
 <code>@ref{,cross ref name,,file name}</code> <a href="file 
name.html#Top">cross ref name: (file name)</a>
 <code>@ref{,cross ref name,,,manual}</code> <cite>manual</cite>
 <code>@ref{,cross ref name,title,file name}</code> <a href="file 
name.html#Top">cross ref name: (file name)</a>
-<code>@ref{,cross ref name,title,,manual}</code> section `title' in 
<cite>manual</cite>
-<code>@ref{,cross ref name,title, file name, manual}</code> <a href="file 
name.html#Top">cross ref name: (file name)</a> section `title' in 
<cite>manual</cite>
+<code>@ref{,cross ref name,title,,manual}</code> section &lsquo;title&rsquo; 
in <cite>manual</cite>
+<code>@ref{,cross ref name,title, file name, manual}</code> <a href="file 
name.html#Top">cross ref name: (file name)</a> section &lsquo;title&rsquo; in 
<cite>manual</cite>
 <code>@ref{,,title,file name}</code> <a href="file name.html#Top">(file 
name)</a>
-<code>@ref{,,title,,manual}</code> section `title' in <cite>manual</cite>
-<code>@ref{,,title, file name, manual}</code> <a href="file 
name.html#Top">(file name)</a> section `title' in <cite>manual</cite>
+<code>@ref{,,title,,manual}</code> section &lsquo;title&rsquo; in 
<cite>manual</cite>
+<code>@ref{,,title, file name, manual}</code> <a href="file 
name.html#Top">(file name)</a> section &lsquo;title&rsquo; in 
<cite>manual</cite>
 <code>@ref{,,,file name,manual}</code> <a href="file name.html#Top">(file 
name)</a> <cite>manual</cite>
 </p>
 <p><code>@inforef{chapter, cross ref name, file name}</code> See <a href="file 
name.html#chapter">cross ref name: (file name)chapter</a>
@@ -1093,7 +1093,7 @@
 </p>
 <p><code>@address@hidden, a @comma{} in cross
 ref, a address@hidden in title, a address@hidden in file, a @comma{} in manual 
name }</code>
-<a href="a address@hidden in file.html#s_002d_002dect_002cion">a , in cross 
ref: (a comma, in file)s&ndash;ect,ion</a> section `a comma, in title' in 
<cite>a , in manual name</cite>
+<a href="a address@hidden in file.html#s_002d_002dect_002cion">a , in cross 
ref: (a comma, in file)s&ndash;ect,ion</a> section &lsquo;a comma, in 
title&rsquo; in <cite>a , in manual name</cite>
 </p>
 <p><code>@address@hidden</code> <a href="#SEC2">A section</a>
 </p>

Index: Tests/formatting_res/fr_formatting.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/formatting_res/fr_formatting.html,v
retrieving revision 1.57
retrieving revision 1.58
diff -u -b -r1.57 -r1.58
--- Tests/formatting_res/fr_formatting.html     3 Oct 2007 07:39:31 -0000       
1.57
+++ Tests/formatting_res/fr_formatting.html     3 Oct 2007 09:34:38 -0000       
1.58
@@ -518,7 +518,7 @@
 <tr><td valign="middle" align="left">[<a href="#SEC_Top" title="Couverture 
(top) du document">Top</a>]</td>
 <td valign="middle" align="left">[<a href="#SEC_Contents" title="Table des 
mati&egrave;res">Table des mati&egrave;res</a>]</td>
 <td valign="middle" align="left">[<a href="#SEC_Top" 
title="Index">Index</a>]</td>
-<td valign="middle" align="left">[<a href="#SEC_About" title="A propos (page 
d'aide)"> ? </a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="A propos (page 
d&rsquo;aide)"> ? </a>]</td>
 </tr></table>
 
 <table class="menu" border="0" cellspacing="0">
@@ -544,7 +544,7 @@
 strong: 
<strong>&ldquo;simple-double&ndash;three&mdash;four&mdash;-&rdquo;</strong> <br>
 kbd: <kbd>``simple-double--three---four----''</kbd> <br>
 </p>
-<p>``simple-double--three&mdash;four&mdash;-''<br>
+<p>&lsquo;&lsquo;simple-double--three&mdash;four&mdash;-&rsquo;&rsquo;<br>
 </p>
 <a name="IDX1"></a>
 <a name="IDX2"></a>
@@ -555,16 +555,16 @@
 @&quot;{U} &Uuml; 
 @~n &ntilde;
 @^a &acirc;
-@'e &eacute;
+@&rsquo;e &eacute;
 @=o &#333;
address@hidden &igrave;
-@'{e} &eacute;
-@'address@hidden &iacute; 
+@&lsquo;i &igrave;
+@&rsquo;{e} &eacute;
+@&rsquo;address@hidden &iacute; 
 @dotless{i} i
 @dotless{ij} ij
address@hidden@=E} &#274;` 
+@&lsquo;address@hidden &#274;` 
 @l{} &#322;
-@,{@'C} &#262;,
+@,{@&rsquo;C} &#262;,
 @,c &ccedil;
 @,c@&quot;u &ccedil;&uuml; <br>
 </p>
@@ -573,10 +573,10 @@
 <br>
 @,@&quot;u ,&uuml;
 </p>
-<p>Invalid use of @':<br>
-@' '
+<p>Invalid use of @&rsquo;:<br>
+@&rsquo; &rsquo;
 <br>
-@'@&quot;u @'&quot;u
+@&rsquo;@&quot;u @'&quot;u
 </p>
 <p>@dotless{truc} truc
 </p>
@@ -1029,9 +1029,9 @@
 <dd><p>d&ndash;eftypemethod
 </p></dd></dl>
 
-<p><code>@xref{c---hapter@@, cross r---ef name@@, t---itle@@, file n---ame@@, 
ma---nual@@}</code> Voir <a href="file 
n---ame@@.html#c_002d_002d_002dhapter_0040">cross r&mdash;ef name@: (file 
n&mdash;ame@)c&mdash;hapter@</a> section `t&mdash;itle@' dans 
<cite>ma&mdash;nual@</cite>
-<code>@ref{chapter, cross ref name, title, file name, manual}</code> <a 
href="file name.html#chapter">cross ref name: (file name)chapter</a> section 
`title' dans <cite>manual</cite>
-<code>@pxref{chapter, cross ref name, title, file name, manual}</code> voir <a 
href="file name.html#chapter">cross ref name: (file name)chapter</a> section 
`title' dans <cite>manual</cite>
+<p><code>@xref{c---hapter@@, cross r---ef name@@, t---itle@@, file n---ame@@, 
ma---nual@@}</code> Voir <a href="file 
n---ame@@.html#c_002d_002d_002dhapter_0040">cross r&mdash;ef name@: (file 
n&mdash;ame@)c&mdash;hapter@</a> section &lsquo;t&mdash;itle@&rsquo; dans 
<cite>ma&mdash;nual@</cite>
+<code>@ref{chapter, cross ref name, title, file name, manual}</code> <a 
href="file name.html#chapter">cross ref name: (file name)chapter</a> section 
&lsquo;title&rsquo; dans <cite>manual</cite>
+<code>@pxref{chapter, cross ref name, title, file name, manual}</code> voir <a 
href="file name.html#chapter">cross ref name: (file name)chapter</a> section 
&lsquo;title&rsquo; dans <cite>manual</cite>
 <code>@inforef{chapter, cross ref name, file name}</code> Voir <a href="file 
name.html#chapter">cross ref name: (file name)chapter</a>
 </p>
 <p><code>@ref{chapter}</code> <a href="#SEC1">chapter</a>
@@ -1043,40 +1043,40 @@
 <code>@ref{chapter,cross ref name}</code> <a href="#SEC1">cross ref name</a>
 <code>@ref{chapter,,title}</code> <a href="#SEC1">title</a>
 <code>@ref{chapter,,,file name}</code> <a href="file name.html#chapter">(file 
name)chapter</a>
-<code>@ref{chapter,,,,manual}</code> section `chapter' dans <cite>manual</cite>
+<code>@ref{chapter,,,,manual}</code> section &lsquo;chapter&rsquo; dans 
<cite>manual</cite>
 <code>@ref{node,cross ref name}</code> @ref{node,cross ref name}
 <code>@ref{node,,title}</code> @ref{node,,title}
 <code>@ref{node,,,file name}</code> <a href="file name.html#node">(file 
name)node</a>
-<code>@ref{node,,,,manual}</code> section `node' dans <cite>manual</cite>
+<code>@ref{node,,,,manual}</code> section &lsquo;node&rsquo; dans 
<cite>manual</cite>
 <code>@ref{chapter,cross ref name,title,}</code> <a href="#SEC1">title</a>
 <code>@ref{chapter,cross ref name,,file name}</code> <a href="file 
name.html#chapter">cross ref name: (file name)chapter</a>
-<code>@ref{chapter,cross ref name,,,manual}</code> section `chapter' dans 
<cite>manual</cite>
+<code>@ref{chapter,cross ref name,,,manual}</code> section 
&lsquo;chapter&rsquo; dans <cite>manual</cite>
 <code>@ref{node,cross ref name,title,}</code> @ref{node,cross ref name,title,}
 <code>@ref{node,cross ref name,,file name}</code> <a href="file 
name.html#node">cross ref name: (file name)node</a>
-<code>@ref{node,cross ref name,,,manual}</code> section `node' dans 
<cite>manual</cite>
+<code>@ref{node,cross ref name,,,manual}</code> section &lsquo;node&rsquo; 
dans <cite>manual</cite>
 <code>@ref{chapter,cross ref name,title,file name}</code> <a href="file 
name.html#chapter">cross ref name: (file name)chapter</a>
-<code>@ref{chapter,cross ref name,title,,manual}</code> section `title' dans 
<cite>manual</cite>
+<code>@ref{chapter,cross ref name,title,,manual}</code> section 
&lsquo;title&rsquo; dans <cite>manual</cite>
 <code>@ref{node,cross ref name,title,file name}</code> <a href="file 
name.html#node">cross ref name: (file name)node</a>
-<code>@ref{node,cross ref name,title,,manual}</code> section `title' dans 
<cite>manual</cite>
-<code>@ref{chapter,cross ref name,title, file name, manual}</code> <a 
href="file name.html#chapter">cross ref name: (file name)chapter</a> section 
`title' dans <cite>manual</cite>
-<code>@ref{node,cross ref name,title, file name, manual}</code> <a href="file 
name.html#node">cross ref name: (file name)node</a> section `title' dans 
<cite>manual</cite>
+<code>@ref{node,cross ref name,title,,manual}</code> section 
&lsquo;title&rsquo; dans <cite>manual</cite>
+<code>@ref{chapter,cross ref name,title, file name, manual}</code> <a 
href="file name.html#chapter">cross ref name: (file name)chapter</a> section 
&lsquo;title&rsquo; dans <cite>manual</cite>
+<code>@ref{node,cross ref name,title, file name, manual}</code> <a href="file 
name.html#node">cross ref name: (file name)node</a> section &lsquo;title&rsquo; 
dans <cite>manual</cite>
 <code>@ref{chapter,,title,file name}</code> <a href="file 
name.html#chapter">(file name)chapter</a>
-<code>@ref{chapter,,title,,manual}</code> section `title' dans 
<cite>manual</cite>
+<code>@ref{chapter,,title,,manual}</code> section &lsquo;title&rsquo; dans 
<cite>manual</cite>
 <code>@ref{node,,title,file name}</code> <a href="file name.html#node">(file 
name)node</a>
-<code>@ref{node,,title,,manual}</code> section `title' dans <cite>manual</cite>
-<code>@ref{chapter,,title, file name, manual}</code> <a href="file 
name.html#chapter">(file name)chapter</a> section `title' dans 
<cite>manual</cite>
-<code>@ref{node,,title, file name, manual}</code> <a href="file 
name.html#node">(file name)node</a> section `title' dans <cite>manual</cite>
-<code>@ref{chapter,,,file name,manual}</code> <a href="file 
name.html#chapter">(file name)chapter</a> section `chapter' dans 
<cite>manual</cite>
-<code>@ref{node,,,file name,manual}</code> <a href="file name.html#node">(file 
name)node</a> section `node' dans <cite>manual</cite>
+<code>@ref{node,,title,,manual}</code> section &lsquo;title&rsquo; dans 
<cite>manual</cite>
+<code>@ref{chapter,,title, file name, manual}</code> <a href="file 
name.html#chapter">(file name)chapter</a> section &lsquo;title&rsquo; dans 
<cite>manual</cite>
+<code>@ref{node,,title, file name, manual}</code> <a href="file 
name.html#node">(file name)node</a> section &lsquo;title&rsquo; dans 
<cite>manual</cite>
+<code>@ref{chapter,,,file name,manual}</code> <a href="file 
name.html#chapter">(file name)chapter</a> section &lsquo;chapter&rsquo; dans 
<cite>manual</cite>
+<code>@ref{node,,,file name,manual}</code> <a href="file name.html#node">(file 
name)node</a> section &lsquo;node&rsquo; dans <cite>manual</cite>
 <code>@ref{,cross ref name,title,}</code> @ref{,cross ref name,title,}
 <code>@ref{,cross ref name,,file name}</code> <a href="file 
name.html#Top">cross ref name: (file name)</a>
 <code>@ref{,cross ref name,,,manual}</code> <cite>manual</cite>
 <code>@ref{,cross ref name,title,file name}</code> <a href="file 
name.html#Top">cross ref name: (file name)</a>
-<code>@ref{,cross ref name,title,,manual}</code> section `title' dans 
<cite>manual</cite>
-<code>@ref{,cross ref name,title, file name, manual}</code> <a href="file 
name.html#Top">cross ref name: (file name)</a> section `title' dans 
<cite>manual</cite>
+<code>@ref{,cross ref name,title,,manual}</code> section &lsquo;title&rsquo; 
dans <cite>manual</cite>
+<code>@ref{,cross ref name,title, file name, manual}</code> <a href="file 
name.html#Top">cross ref name: (file name)</a> section &lsquo;title&rsquo; dans 
<cite>manual</cite>
 <code>@ref{,,title,file name}</code> <a href="file name.html#Top">(file 
name)</a>
-<code>@ref{,,title,,manual}</code> section `title' dans <cite>manual</cite>
-<code>@ref{,,title, file name, manual}</code> <a href="file 
name.html#Top">(file name)</a> section `title' dans <cite>manual</cite>
+<code>@ref{,,title,,manual}</code> section &lsquo;title&rsquo; dans 
<cite>manual</cite>
+<code>@ref{,,title, file name, manual}</code> <a href="file 
name.html#Top">(file name)</a> section &lsquo;title&rsquo; dans 
<cite>manual</cite>
 <code>@ref{,,,file name,manual}</code> <a href="file name.html#Top">(file 
name)</a> <cite>manual</cite>
 </p>
 <p><code>@inforef{chapter, cross ref name, file name}</code> Voir <a 
href="file name.html#chapter">cross ref name: (file name)chapter</a>
@@ -1093,7 +1093,7 @@
 </p>
 <p><code>@address@hidden, a @comma{} in cross
 ref, a address@hidden in title, a address@hidden in file, a @comma{} in manual 
name }</code>
-<a href="a address@hidden in file.html#s_002d_002dect_002cion">a , in cross 
ref: (a comma, in file)s&ndash;ect,ion</a> section `a comma, in title' dans 
<cite>a , in manual name</cite>
+<a href="a address@hidden in file.html#s_002d_002dect_002cion">a , in cross 
ref: (a comma, in file)s&ndash;ect,ion</a> section &lsquo;a comma, in 
title&rsquo; dans <cite>a , in manual name</cite>
 </p>
 <p><code>@address@hidden</code> <a href="#SEC2">A section</a>
 </p>
@@ -1727,7 +1727,7 @@
  &nbsp; 
 </td></tr></table>
 <table border="0" class="index-cp">
-<tr><td></td><th align="left">Entr&eacute;e d'index</th><th align="left"> 
Section</th></tr>
+<tr><td></td><th align="left">Entr&eacute;e d&rsquo;index</th><th 
align="left"> Section</th></tr>
 <tr><td colspan="3"> <hr></td></tr>
 <tr><th><a name="SEC_Top_0">&quot;</a></th><td></td><td></td></tr>
 <tr><td></td><td valign="top"><a href="#SEC_Top">&ldquo;</a></td><td 
valign="top"><a href="#SEC_Top">Top section</a></td></tr>
@@ -1796,7 +1796,7 @@
  &nbsp; 
 </td></tr></table>
 <table border="0" class="index-fn">
-<tr><td></td><th align="left">Entr&eacute;e d'index</th><th align="left"> 
Section</th></tr>
+<tr><td></td><th align="left">Entr&eacute;e d&rsquo;index</th><th 
align="left"> Section</th></tr>
 <tr><td colspan="3"> <hr></td></tr>
 <tr><th><a name="SEC_Top_0">&quot;</a></th><td></td><td></td></tr>
 <tr><td></td><td valign="top"><a href="#SEC_Top"><code>``</code></a></td><td 
valign="top"><a href="#SEC_Top">Top section</a></td></tr>
@@ -1964,7 +1964,7 @@
  &nbsp; 
 </td></tr></table>
 <table border="0" class="index-vr">
-<tr><td></td><th align="left">Entr&eacute;e d'index</th><th align="left"> 
Section</th></tr>
+<tr><td></td><th align="left">Entr&eacute;e d&rsquo;index</th><th 
align="left"> Section</th></tr>
 <tr><td colspan="3"> <hr></td></tr>
 <tr><th><a name="SEC_Top_0">A</a></th><td></td><td></td></tr>
 <tr><td></td><td valign="top"><a href="#SEC_Top"><code>a</code></a></td><td 
valign="top"><a href="#SEC_Top">Top section</a></td></tr>
@@ -2013,7 +2013,7 @@
  &nbsp; 
 </td></tr></table>
 <table border="0" class="index-tp">
-<tr><td></td><th align="left">Entr&eacute;e d'index</th><th align="left"> 
Section</th></tr>
+<tr><td></td><th align="left">Entr&eacute;e d&rsquo;index</th><th 
align="left"> Section</th></tr>
 <tr><td colspan="3"> <hr></td></tr>
 <tr><th><a name="SEC_Top_0">D</a></th><td></td><td></td></tr>
 <tr><td></td><td valign="top"><a 
href="#SEC_Top"><code>d--eftp_name</code></a></td><td valign="top"><a 
href="#SEC_Top">Top section</a></td></tr>
@@ -2031,8 +2031,8 @@
 <a name="chapter"></a>
 <a name="SEC1"></a>
 <table cellpadding="1" cellspacing="1" border="0">
-<tr><td valign="middle" align="left">[<a href="#SEC_Top" title="Section 
pr&eacute;c&eacute;dente dans l'ordre de lecture"> &lt; </a>]</td>
-<td valign="middle" align="left">[<a href="#SEC2" title="Section suivante dans 
l'ordre de lecture"> &gt; </a>]</td>
+<tr><td valign="middle" align="left">[<a href="#SEC_Top" title="Section 
pr&eacute;c&eacute;dente dans l&rsquo;ordre de lecture"> &lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#SEC2" title="Section suivante dans 
l&rsquo;ordre de lecture"> &gt; </a>]</td>
 <td valign="middle" align="left"> &nbsp; </td>
 <td valign="middle" align="left">[ &lt;&lt; ]</td>
 <td valign="middle" align="left">[<a href="#SEC_Top" title="Section 
sup&eacute;rieure">Plus haut</a>]</td>
@@ -2044,7 +2044,7 @@
 <td valign="middle" align="left">[<a href="#SEC_Top" title="Couverture (top) 
du document">Top</a>]</td>
 <td valign="middle" align="left">[<a href="#SEC_Contents" title="Table des 
mati&egrave;res">Table des mati&egrave;res</a>]</td>
 <td valign="middle" align="left">[<a href="#SEC_Top" 
title="Index">Index</a>]</td>
-<td valign="middle" align="left">[<a href="#SEC_About" title="A propos (page 
d'aide)"> ? </a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="A propos (page 
d&rsquo;aide)"> ? </a>]</td>
 </tr></table>
 <h1 class="chapter"> 1. chapter </h1>
 
@@ -2064,8 +2064,8 @@
 <a name="s_002d_002dect_002cion"></a>
 <a name="SEC2"></a>
 <table cellpadding="1" cellspacing="1" border="0">
-<tr><td valign="middle" align="left">[<a href="#SEC1" title="Section 
pr&eacute;c&eacute;dente dans l'ordre de lecture"> &lt; </a>]</td>
-<td valign="middle" align="left">[<a href="#SEC3" title="Section suivante dans 
l'ordre de lecture"> &gt; </a>]</td>
+<tr><td valign="middle" align="left">[<a href="#SEC1" title="Section 
pr&eacute;c&eacute;dente dans l&rsquo;ordre de lecture"> &lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#SEC3" title="Section suivante dans 
l&rsquo;ordre de lecture"> &gt; </a>]</td>
 <td valign="middle" align="left"> &nbsp; </td>
 <td valign="middle" align="left">[<a href="#SEC1" title="D&eacute;but de ce 
chapitre ou chapitre pr&eacute;c&eacute;dent"> &lt;&lt; </a>]</td>
 <td valign="middle" align="left">[<a href="#SEC1" title="Section 
sup&eacute;rieure">Plus haut</a>]</td>
@@ -2077,7 +2077,7 @@
 <td valign="middle" align="left">[<a href="#SEC_Top" title="Couverture (top) 
du document">Top</a>]</td>
 <td valign="middle" align="left">[<a href="#SEC_Contents" title="Table des 
mati&egrave;res">Table des mati&egrave;res</a>]</td>
 <td valign="middle" align="left">[<a href="#SEC_Top" 
title="Index">Index</a>]</td>
-<td valign="middle" align="left">[<a href="#SEC_About" title="A propos (page 
d'aide)"> ? </a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="A propos (page 
d&rsquo;aide)"> ? </a>]</td>
 </tr></table>
 <h2 class="section"> 1.1 A section </h2>
 
@@ -2090,8 +2090,8 @@
 <a name="subsection"></a>
 <a name="SEC3"></a>
 <table cellpadding="1" cellspacing="1" border="0">
-<tr><td valign="middle" align="left">[<a href="#SEC2" title="Section 
pr&eacute;c&eacute;dente dans l'ordre de lecture"> &lt; </a>]</td>
-<td valign="middle" align="left">[<a href="#SEC4" title="Section suivante dans 
l'ordre de lecture"> &gt; </a>]</td>
+<tr><td valign="middle" align="left">[<a href="#SEC2" title="Section 
pr&eacute;c&eacute;dente dans l&rsquo;ordre de lecture"> &lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#SEC4" title="Section suivante dans 
l&rsquo;ordre de lecture"> &gt; </a>]</td>
 <td valign="middle" align="left"> &nbsp; </td>
 <td valign="middle" align="left">[<a href="#SEC1" title="D&eacute;but de ce 
chapitre ou chapitre pr&eacute;c&eacute;dent"> &lt;&lt; </a>]</td>
 <td valign="middle" align="left">[<a href="#SEC2" title="Section 
sup&eacute;rieure">Plus haut</a>]</td>
@@ -2103,7 +2103,7 @@
 <td valign="middle" align="left">[<a href="#SEC_Top" title="Couverture (top) 
du document">Top</a>]</td>
 <td valign="middle" align="left">[<a href="#SEC_Contents" title="Table des 
mati&egrave;res">Table des mati&egrave;res</a>]</td>
 <td valign="middle" align="left">[<a href="#SEC_Top" 
title="Index">Index</a>]</td>
-<td valign="middle" align="left">[<a href="#SEC_About" title="A propos (page 
d'aide)"> ? </a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="A propos (page 
d&rsquo;aide)"> ? </a>]</td>
 </tr></table>
 <h3 class="subsection"> 1.1.1 subsection </h3>
 
@@ -2118,8 +2118,8 @@
 <a name="subsubsection"></a>
 <a name="SEC4"></a>
 <table cellpadding="1" cellspacing="1" border="0">
-<tr><td valign="middle" align="left">[<a href="#SEC3" title="Section 
pr&eacute;c&eacute;dente dans l'ordre de lecture"> &lt; </a>]</td>
-<td valign="middle" align="left">[<a href="#SEC5" title="Section suivante dans 
l'ordre de lecture"> &gt; </a>]</td>
+<tr><td valign="middle" align="left">[<a href="#SEC3" title="Section 
pr&eacute;c&eacute;dente dans l&rsquo;ordre de lecture"> &lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#SEC5" title="Section suivante dans 
l&rsquo;ordre de lecture"> &gt; </a>]</td>
 <td valign="middle" align="left"> &nbsp; </td>
 <td valign="middle" align="left">[<a href="#SEC1" title="D&eacute;but de ce 
chapitre ou chapitre pr&eacute;c&eacute;dent"> &lt;&lt; </a>]</td>
 <td valign="middle" align="left">[<a href="#SEC3" title="Section 
sup&eacute;rieure">Plus haut</a>]</td>
@@ -2131,7 +2131,7 @@
 <td valign="middle" align="left">[<a href="#SEC_Top" title="Couverture (top) 
du document">Top</a>]</td>
 <td valign="middle" align="left">[<a href="#SEC_Contents" title="Table des 
mati&egrave;res">Table des mati&egrave;res</a>]</td>
 <td valign="middle" align="left">[<a href="#SEC_Top" 
title="Index">Index</a>]</td>
-<td valign="middle" align="left">[<a href="#SEC_About" title="A propos (page 
d'aide)"> ? </a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="A propos (page 
d&rsquo;aide)"> ? </a>]</td>
 </tr></table>
 <h4 class="subsubsection"> 1.1.1.1 subsubsection </h4>
 
@@ -2139,7 +2139,7 @@
 <a name="chapter2"></a>
 <a name="SEC5"></a>
 <table cellpadding="1" cellspacing="1" border="0">
-<tr><td valign="middle" align="left">[<a href="#SEC4" title="Section 
pr&eacute;c&eacute;dente dans l'ordre de lecture"> &lt; </a>]</td>
+<tr><td valign="middle" align="left">[<a href="#SEC4" title="Section 
pr&eacute;c&eacute;dente dans l&rsquo;ordre de lecture"> &lt; </a>]</td>
 <td valign="middle" align="left">[ &gt; ]</td>
 <td valign="middle" align="left"> &nbsp; </td>
 <td valign="middle" align="left">[<a href="#SEC1" title="D&eacute;but de ce 
chapitre ou chapitre pr&eacute;c&eacute;dent"> &lt;&lt; </a>]</td>
@@ -2152,7 +2152,7 @@
 <td valign="middle" align="left">[<a href="#SEC_Top" title="Couverture (top) 
du document">Top</a>]</td>
 <td valign="middle" align="left">[<a href="#SEC_Contents" title="Table des 
mati&egrave;res">Table des mati&egrave;res</a>]</td>
 <td valign="middle" align="left">[<a href="#SEC_Top" 
title="Index">Index</a>]</td>
-<td valign="middle" align="left">[<a href="#SEC_About" title="A propos (page 
d'aide)"> ? </a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="A propos (page 
d&rsquo;aide)"> ? </a>]</td>
 </tr></table>
 <h1 class="centerchap" align="center"> 2. chapter 2 </h1>
 
@@ -2171,7 +2171,7 @@
  &nbsp; 
 </td></tr></table>
 <table border="0" class="index-cp">
-<tr><td></td><th align="left">Entr&eacute;e d'index</th><th align="left"> 
Section</th></tr>
+<tr><td></td><th align="left">Entr&eacute;e d&rsquo;index</th><th 
align="left"> Section</th></tr>
 <tr><td colspan="3"> <hr></td></tr>
 <tr><th><a name="SEC5_0">&quot;</a></th><td></td><td></td></tr>
 <tr><td></td><td valign="top"><a href="#SEC_Top">&ldquo;</a></td><td 
valign="top"><a href="#SEC_Top">Top section</a></td></tr>
@@ -2238,7 +2238,7 @@
  &nbsp; 
 </td></tr></table>
 <table border="0" class="index-fn">
-<tr><td></td><th align="left">Entr&eacute;e d'index</th><th align="left"> 
Section</th></tr>
+<tr><td></td><th align="left">Entr&eacute;e d&rsquo;index</th><th 
align="left"> Section</th></tr>
 <tr><td colspan="3"> <hr></td></tr>
 <tr><th><a name="SEC5_0">&quot;</a></th><td></td><td></td></tr>
 <tr><td></td><td valign="top"><a href="#SEC_Top"><code>``</code></a></td><td 
valign="top"><a href="#SEC_Top">Top section</a></td></tr>
@@ -2405,7 +2405,7 @@
 <tr><td valign="middle" align="left">[<a href="#SEC_Top" title="Couverture 
(top) du document">Top</a>]</td>
 <td valign="middle" align="left">[<a href="#SEC_Contents" title="Table des 
mati&egrave;res">Table des mati&egrave;res</a>]</td>
 <td valign="middle" align="left">[<a href="#SEC_Top" 
title="Index">Index</a>]</td>
-<td valign="middle" align="left">[<a href="#SEC_About" title="A propos (page 
d'aide)"> ? </a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="A propos (page 
d&rsquo;aide)"> ? </a>]</td>
 </tr></table>
 <h1>Notes de bas de page</h1>
 <h3><a name="FOOT1" href="#DOCF1">(1)</a></h3>
@@ -2424,7 +2424,7 @@
 <tr><td valign="middle" align="left">[<a href="#SEC_Top" title="Couverture 
(top) du document">Top</a>]</td>
 <td valign="middle" align="left">[<a href="#SEC_Contents" title="Table des 
mati&egrave;res">Table des mati&egrave;res</a>]</td>
 <td valign="middle" align="left">[<a href="#SEC_Top" 
title="Index">Index</a>]</td>
-<td valign="middle" align="left">[<a href="#SEC_About" title="A propos (page 
d'aide)"> ? </a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="A propos (page 
d&rsquo;aide)"> ? </a>]</td>
 </tr></table>
 <h1>Table des mati&egrave;res</h1>
 <div class="contents">
@@ -2451,7 +2451,7 @@
 <tr><td valign="middle" align="left">[<a href="#SEC_Top" title="Couverture 
(top) du document">Top</a>]</td>
 <td valign="middle" align="left">[<a href="#SEC_Contents" title="Table des 
mati&egrave;res">Table des mati&egrave;res</a>]</td>
 <td valign="middle" align="left">[<a href="#SEC_Top" 
title="Index">Index</a>]</td>
-<td valign="middle" align="left">[<a href="#SEC_About" title="A propos (page 
d'aide)"> ? </a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="A propos (page 
d&rsquo;aide)"> ? </a>]</td>
 </tr></table>
 <h1>R&eacute;sum&eacute; du contenu</h1>
 <div class="shortcontents">
@@ -2466,7 +2466,7 @@
 <tr><td valign="middle" align="left">[<a href="#SEC_Top" title="Couverture 
(top) du document">Top</a>]</td>
 <td valign="middle" align="left">[<a href="#SEC_Contents" title="Table des 
mati&egrave;res">Table des mati&egrave;res</a>]</td>
 <td valign="middle" align="left">[<a href="#SEC_Top" 
title="Index">Index</a>]</td>
-<td valign="middle" align="left">[<a href="#SEC_About" title="A propos (page 
d'aide)"> ? </a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="A propos (page 
d&rsquo;aide)"> ? </a>]</td>
 </tr></table>
 <h1>A propos de ce document</h1>
 <p>
@@ -2485,13 +2485,13 @@
   <tr>
     <td align="center"> [ &lt; ] </td>
     <td align="center">Retour</td>
-    <td>Section pr&eacute;c&eacute;dente dans l'ordre de lecture</td>
+    <td>Section pr&eacute;c&eacute;dente dans l&rsquo;ordre de lecture</td>
     <td>1.2.2</td>
   </tr>
   <tr>
     <td align="center"> [ &gt; ] </td>
     <td align="center">Avant</td>
-    <td>Section suivante dans l'ordre de lecture</td>
+    <td>Section suivante dans l&rsquo;ordre de lecture</td>
     <td>1.2.4</td>
   </tr>
   <tr>
@@ -2533,7 +2533,7 @@
   <tr>
     <td align="center"> [ ? ] </td>
     <td align="center">A propos</td>
-    <td>A propos (page d'aide)</td>
+    <td>A propos (page d&rsquo;aide)</td>
     <td> &nbsp; </td>
   </tr>
 </table>

Index: Tests/formatting_res/icons_fr_formatting.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/formatting_res/icons_fr_formatting.html,v
retrieving revision 1.19
retrieving revision 1.20
diff -u -b -r1.19 -r1.20
--- Tests/formatting_res/icons_fr_formatting.html       3 Oct 2007 07:39:32 
-0000       1.19
+++ Tests/formatting_res/icons_fr_formatting.html       3 Oct 2007 09:34:38 
-0000       1.20
@@ -518,7 +518,7 @@
 <tr><td valign="middle" align="left"><a href="#SEC_Top" title="Couverture 
(top) du document"><img src="a_top.png" border="0" alt="Top: Top section" 
align="middle"></a></td>
 <td valign="middle" align="left"><a href="#SEC_Contents" title="Table des 
mati&egrave;res"><img src="a_tableofcon.png" border="0" alt="Table des 
mati&egrave;res: Table des mati&egrave;res" align="middle"></a></td>
 <td valign="middle" align="left"><a href="#SEC_Top" title="Index"><img 
src="a_index.png" border="0" alt="Index: Top section" align="middle"></a></td>
-<td valign="middle" align="left"><a href="#SEC_About" title="A propos (page 
d'aide)"><img src="a_help.png" border="0" alt="A propos: A propos de ce 
document" align="middle"></a></td>
+<td valign="middle" align="left"><a href="#SEC_About" title="A propos (page 
d&rsquo;aide)"><img src="a_help.png" border="0" alt="A propos: A propos de ce 
document" align="middle"></a></td>
 </tr></table>
 
 <table class="menu" border="0" cellspacing="0">
@@ -544,7 +544,7 @@
 strong: 
<strong>&ldquo;simple-double&ndash;three&mdash;four&mdash;-&rdquo;</strong> <br>
 kbd: <kbd>``simple-double--three---four----''</kbd> <br>
 </p>
-<p>``simple-double--three&mdash;four&mdash;-''<br>
+<p>&lsquo;&lsquo;simple-double--three&mdash;four&mdash;-&rsquo;&rsquo;<br>
 </p>
 <a name="IDX1"></a>
 <a name="IDX2"></a>
@@ -555,16 +555,16 @@
 @&quot;{U} &Uuml; 
 @~n &ntilde;
 @^a &acirc;
-@'e &eacute;
+@&rsquo;e &eacute;
 @=o &#333;
address@hidden &igrave;
-@'{e} &eacute;
-@'address@hidden &iacute; 
+@&lsquo;i &igrave;
+@&rsquo;{e} &eacute;
+@&rsquo;address@hidden &iacute; 
 @dotless{i} i
 @dotless{ij} ij
address@hidden@=E} &#274;` 
+@&lsquo;address@hidden &#274;` 
 @l{} &#322;
-@,{@'C} &#262;,
+@,{@&rsquo;C} &#262;,
 @,c &ccedil;
 @,c@&quot;u &ccedil;&uuml; <br>
 </p>
@@ -573,10 +573,10 @@
 <br>
 @,@&quot;u ,&uuml;
 </p>
-<p>Invalid use of @':<br>
-@' '
+<p>Invalid use of @&rsquo;:<br>
+@&rsquo; &rsquo;
 <br>
-@'@&quot;u @'&quot;u
+@&rsquo;@&quot;u @'&quot;u
 </p>
 <p>@dotless{truc} truc
 </p>
@@ -1029,9 +1029,9 @@
 <dd><p>d&ndash;eftypemethod
 </p></dd></dl>
 
-<p><code>@xref{c---hapter@@, cross r---ef name@@, t---itle@@, file n---ame@@, 
ma---nual@@}</code> Voir <a href="file 
n---ame@@.html#c_002d_002d_002dhapter_0040">cross r&mdash;ef name@: (file 
n&mdash;ame@)c&mdash;hapter@</a> section `t&mdash;itle@' dans 
<cite>ma&mdash;nual@</cite>
-<code>@ref{chapter, cross ref name, title, file name, manual}</code> <a 
href="file name.html#chapter">cross ref name: (file name)chapter</a> section 
`title' dans <cite>manual</cite>
-<code>@pxref{chapter, cross ref name, title, file name, manual}</code> voir <a 
href="file name.html#chapter">cross ref name: (file name)chapter</a> section 
`title' dans <cite>manual</cite>
+<p><code>@xref{c---hapter@@, cross r---ef name@@, t---itle@@, file n---ame@@, 
ma---nual@@}</code> Voir <a href="file 
n---ame@@.html#c_002d_002d_002dhapter_0040">cross r&mdash;ef name@: (file 
n&mdash;ame@)c&mdash;hapter@</a> section &lsquo;t&mdash;itle@&rsquo; dans 
<cite>ma&mdash;nual@</cite>
+<code>@ref{chapter, cross ref name, title, file name, manual}</code> <a 
href="file name.html#chapter">cross ref name: (file name)chapter</a> section 
&lsquo;title&rsquo; dans <cite>manual</cite>
+<code>@pxref{chapter, cross ref name, title, file name, manual}</code> voir <a 
href="file name.html#chapter">cross ref name: (file name)chapter</a> section 
&lsquo;title&rsquo; dans <cite>manual</cite>
 <code>@inforef{chapter, cross ref name, file name}</code> Voir <a href="file 
name.html#chapter">cross ref name: (file name)chapter</a>
 </p>
 <p><code>@ref{chapter}</code> <a href="#SEC1">chapter</a>
@@ -1043,40 +1043,40 @@
 <code>@ref{chapter,cross ref name}</code> <a href="#SEC1">cross ref name</a>
 <code>@ref{chapter,,title}</code> <a href="#SEC1">title</a>
 <code>@ref{chapter,,,file name}</code> <a href="file name.html#chapter">(file 
name)chapter</a>
-<code>@ref{chapter,,,,manual}</code> section `chapter' dans <cite>manual</cite>
+<code>@ref{chapter,,,,manual}</code> section &lsquo;chapter&rsquo; dans 
<cite>manual</cite>
 <code>@ref{node,cross ref name}</code> @ref{node,cross ref name}
 <code>@ref{node,,title}</code> @ref{node,,title}
 <code>@ref{node,,,file name}</code> <a href="file name.html#node">(file 
name)node</a>
-<code>@ref{node,,,,manual}</code> section `node' dans <cite>manual</cite>
+<code>@ref{node,,,,manual}</code> section &lsquo;node&rsquo; dans 
<cite>manual</cite>
 <code>@ref{chapter,cross ref name,title,}</code> <a href="#SEC1">title</a>
 <code>@ref{chapter,cross ref name,,file name}</code> <a href="file 
name.html#chapter">cross ref name: (file name)chapter</a>
-<code>@ref{chapter,cross ref name,,,manual}</code> section `chapter' dans 
<cite>manual</cite>
+<code>@ref{chapter,cross ref name,,,manual}</code> section 
&lsquo;chapter&rsquo; dans <cite>manual</cite>
 <code>@ref{node,cross ref name,title,}</code> @ref{node,cross ref name,title,}
 <code>@ref{node,cross ref name,,file name}</code> <a href="file 
name.html#node">cross ref name: (file name)node</a>
-<code>@ref{node,cross ref name,,,manual}</code> section `node' dans 
<cite>manual</cite>
+<code>@ref{node,cross ref name,,,manual}</code> section &lsquo;node&rsquo; 
dans <cite>manual</cite>
 <code>@ref{chapter,cross ref name,title,file name}</code> <a href="file 
name.html#chapter">cross ref name: (file name)chapter</a>
-<code>@ref{chapter,cross ref name,title,,manual}</code> section `title' dans 
<cite>manual</cite>
+<code>@ref{chapter,cross ref name,title,,manual}</code> section 
&lsquo;title&rsquo; dans <cite>manual</cite>
 <code>@ref{node,cross ref name,title,file name}</code> <a href="file 
name.html#node">cross ref name: (file name)node</a>
-<code>@ref{node,cross ref name,title,,manual}</code> section `title' dans 
<cite>manual</cite>
-<code>@ref{chapter,cross ref name,title, file name, manual}</code> <a 
href="file name.html#chapter">cross ref name: (file name)chapter</a> section 
`title' dans <cite>manual</cite>
-<code>@ref{node,cross ref name,title, file name, manual}</code> <a href="file 
name.html#node">cross ref name: (file name)node</a> section `title' dans 
<cite>manual</cite>
+<code>@ref{node,cross ref name,title,,manual}</code> section 
&lsquo;title&rsquo; dans <cite>manual</cite>
+<code>@ref{chapter,cross ref name,title, file name, manual}</code> <a 
href="file name.html#chapter">cross ref name: (file name)chapter</a> section 
&lsquo;title&rsquo; dans <cite>manual</cite>
+<code>@ref{node,cross ref name,title, file name, manual}</code> <a href="file 
name.html#node">cross ref name: (file name)node</a> section &lsquo;title&rsquo; 
dans <cite>manual</cite>
 <code>@ref{chapter,,title,file name}</code> <a href="file 
name.html#chapter">(file name)chapter</a>
-<code>@ref{chapter,,title,,manual}</code> section `title' dans 
<cite>manual</cite>
+<code>@ref{chapter,,title,,manual}</code> section &lsquo;title&rsquo; dans 
<cite>manual</cite>
 <code>@ref{node,,title,file name}</code> <a href="file name.html#node">(file 
name)node</a>
-<code>@ref{node,,title,,manual}</code> section `title' dans <cite>manual</cite>
-<code>@ref{chapter,,title, file name, manual}</code> <a href="file 
name.html#chapter">(file name)chapter</a> section `title' dans 
<cite>manual</cite>
-<code>@ref{node,,title, file name, manual}</code> <a href="file 
name.html#node">(file name)node</a> section `title' dans <cite>manual</cite>
-<code>@ref{chapter,,,file name,manual}</code> <a href="file 
name.html#chapter">(file name)chapter</a> section `chapter' dans 
<cite>manual</cite>
-<code>@ref{node,,,file name,manual}</code> <a href="file name.html#node">(file 
name)node</a> section `node' dans <cite>manual</cite>
+<code>@ref{node,,title,,manual}</code> section &lsquo;title&rsquo; dans 
<cite>manual</cite>
+<code>@ref{chapter,,title, file name, manual}</code> <a href="file 
name.html#chapter">(file name)chapter</a> section &lsquo;title&rsquo; dans 
<cite>manual</cite>
+<code>@ref{node,,title, file name, manual}</code> <a href="file 
name.html#node">(file name)node</a> section &lsquo;title&rsquo; dans 
<cite>manual</cite>
+<code>@ref{chapter,,,file name,manual}</code> <a href="file 
name.html#chapter">(file name)chapter</a> section &lsquo;chapter&rsquo; dans 
<cite>manual</cite>
+<code>@ref{node,,,file name,manual}</code> <a href="file name.html#node">(file 
name)node</a> section &lsquo;node&rsquo; dans <cite>manual</cite>
 <code>@ref{,cross ref name,title,}</code> @ref{,cross ref name,title,}
 <code>@ref{,cross ref name,,file name}</code> <a href="file 
name.html#Top">cross ref name: (file name)</a>
 <code>@ref{,cross ref name,,,manual}</code> <cite>manual</cite>
 <code>@ref{,cross ref name,title,file name}</code> <a href="file 
name.html#Top">cross ref name: (file name)</a>
-<code>@ref{,cross ref name,title,,manual}</code> section `title' dans 
<cite>manual</cite>
-<code>@ref{,cross ref name,title, file name, manual}</code> <a href="file 
name.html#Top">cross ref name: (file name)</a> section `title' dans 
<cite>manual</cite>
+<code>@ref{,cross ref name,title,,manual}</code> section &lsquo;title&rsquo; 
dans <cite>manual</cite>
+<code>@ref{,cross ref name,title, file name, manual}</code> <a href="file 
name.html#Top">cross ref name: (file name)</a> section &lsquo;title&rsquo; dans 
<cite>manual</cite>
 <code>@ref{,,title,file name}</code> <a href="file name.html#Top">(file 
name)</a>
-<code>@ref{,,title,,manual}</code> section `title' dans <cite>manual</cite>
-<code>@ref{,,title, file name, manual}</code> <a href="file 
name.html#Top">(file name)</a> section `title' dans <cite>manual</cite>
+<code>@ref{,,title,,manual}</code> section &lsquo;title&rsquo; dans 
<cite>manual</cite>
+<code>@ref{,,title, file name, manual}</code> <a href="file 
name.html#Top">(file name)</a> section &lsquo;title&rsquo; dans 
<cite>manual</cite>
 <code>@ref{,,,file name,manual}</code> <a href="file name.html#Top">(file 
name)</a> <cite>manual</cite>
 </p>
 <p><code>@inforef{chapter, cross ref name, file name}</code> Voir <a 
href="file name.html#chapter">cross ref name: (file name)chapter</a>
@@ -1093,7 +1093,7 @@
 </p>
 <p><code>@address@hidden, a @comma{} in cross
 ref, a address@hidden in title, a address@hidden in file, a @comma{} in manual 
name }</code>
-<a href="a address@hidden in file.html#s_002d_002dect_002cion">a , in cross 
ref: (a comma, in file)s&ndash;ect,ion</a> section `a comma, in title' dans 
<cite>a , in manual name</cite>
+<a href="a address@hidden in file.html#s_002d_002dect_002cion">a , in cross 
ref: (a comma, in file)s&ndash;ect,ion</a> section &lsquo;a comma, in 
title&rsquo; dans <cite>a , in manual name</cite>
 </p>
 <p><code>@address@hidden</code> <a href="#SEC2">A section</a>
 </p>
@@ -1727,7 +1727,7 @@
  &nbsp; 
 </td></tr></table>
 <table border="0" class="index-cp">
-<tr><td></td><th align="left">Entr&eacute;e d'index</th><th align="left"> 
Section</th></tr>
+<tr><td></td><th align="left">Entr&eacute;e d&rsquo;index</th><th 
align="left"> Section</th></tr>
 <tr><td colspan="3"> <hr></td></tr>
 <tr><th><a name="SEC_Top_0">&quot;</a></th><td></td><td></td></tr>
 <tr><td></td><td valign="top"><a href="#SEC_Top">&ldquo;</a></td><td 
valign="top"><a href="#SEC_Top">Top section</a></td></tr>
@@ -1796,7 +1796,7 @@
  &nbsp; 
 </td></tr></table>
 <table border="0" class="index-fn">
-<tr><td></td><th align="left">Entr&eacute;e d'index</th><th align="left"> 
Section</th></tr>
+<tr><td></td><th align="left">Entr&eacute;e d&rsquo;index</th><th 
align="left"> Section</th></tr>
 <tr><td colspan="3"> <hr></td></tr>
 <tr><th><a name="SEC_Top_0">&quot;</a></th><td></td><td></td></tr>
 <tr><td></td><td valign="top"><a href="#SEC_Top"><code>``</code></a></td><td 
valign="top"><a href="#SEC_Top">Top section</a></td></tr>
@@ -1964,7 +1964,7 @@
  &nbsp; 
 </td></tr></table>
 <table border="0" class="index-vr">
-<tr><td></td><th align="left">Entr&eacute;e d'index</th><th align="left"> 
Section</th></tr>
+<tr><td></td><th align="left">Entr&eacute;e d&rsquo;index</th><th 
align="left"> Section</th></tr>
 <tr><td colspan="3"> <hr></td></tr>
 <tr><th><a name="SEC_Top_0">A</a></th><td></td><td></td></tr>
 <tr><td></td><td valign="top"><a href="#SEC_Top"><code>a</code></a></td><td 
valign="top"><a href="#SEC_Top">Top section</a></td></tr>
@@ -2013,7 +2013,7 @@
  &nbsp; 
 </td></tr></table>
 <table border="0" class="index-tp">
-<tr><td></td><th align="left">Entr&eacute;e d'index</th><th align="left"> 
Section</th></tr>
+<tr><td></td><th align="left">Entr&eacute;e d&rsquo;index</th><th 
align="left"> Section</th></tr>
 <tr><td colspan="3"> <hr></td></tr>
 <tr><th><a name="SEC_Top_0">D</a></th><td></td><td></td></tr>
 <tr><td></td><td valign="top"><a 
href="#SEC_Top"><code>d--eftp_name</code></a></td><td valign="top"><a 
href="#SEC_Top">Top section</a></td></tr>
@@ -2031,8 +2031,8 @@
 <a name="chapter"></a>
 <a name="SEC1"></a>
 <table cellpadding="1" cellspacing="1" border="0">
-<tr><td valign="middle" align="left"><a href="#SEC_Top" title="Section 
pr&eacute;c&eacute;dente dans l'ordre de lecture"><img src="a_left.png" 
border="0" alt="Retour: Top section" align="middle"></a></td>
-<td valign="middle" align="left"><a href="#SEC2" title="Section suivante dans 
l'ordre de lecture"><img src="a_right.png" border="0" alt="Avant: 1.1 A 
section" align="middle"></a></td>
+<tr><td valign="middle" align="left"><a href="#SEC_Top" title="Section 
pr&eacute;c&eacute;dente dans l&rsquo;ordre de lecture"><img src="a_left.png" 
border="0" alt="Retour: Top section" align="middle"></a></td>
+<td valign="middle" align="left"><a href="#SEC2" title="Section suivante dans 
l&rsquo;ordre de lecture"><img src="a_right.png" border="0" alt="Avant: 1.1 A 
section" align="middle"></a></td>
 <td valign="middle" align="left"> &nbsp; </td>
 <td valign="middle" align="left"><img src="a_leftdouble_na.png" border="0" 
alt="RetourRapide" align="middle"></td>
 <td valign="middle" align="left"><a href="#SEC_Top" title="Section 
sup&eacute;rieure"><img src="a_up.png" border="0" alt="Monter: Top section" 
align="middle"></a></td>
@@ -2044,7 +2044,7 @@
 <td valign="middle" align="left"><a href="#SEC_Top" title="Couverture (top) du 
document"><img src="a_top.png" border="0" alt="Top: Top section" 
align="middle"></a></td>
 <td valign="middle" align="left"><a href="#SEC_Contents" title="Table des 
mati&egrave;res"><img src="a_tableofcon.png" border="0" alt="Table des 
mati&egrave;res: Table des mati&egrave;res" align="middle"></a></td>
 <td valign="middle" align="left"><a href="#SEC_Top" title="Index"><img 
src="a_index.png" border="0" alt="Index: Top section" align="middle"></a></td>
-<td valign="middle" align="left"><a href="#SEC_About" title="A propos (page 
d'aide)"><img src="a_help.png" border="0" alt="A propos: A propos de ce 
document" align="middle"></a></td>
+<td valign="middle" align="left"><a href="#SEC_About" title="A propos (page 
d&rsquo;aide)"><img src="a_help.png" border="0" alt="A propos: A propos de ce 
document" align="middle"></a></td>
 </tr></table>
 <h1 class="chapter"> 1. chapter </h1>
 
@@ -2064,8 +2064,8 @@
 <a name="s_002d_002dect_002cion"></a>
 <a name="SEC2"></a>
 <table cellpadding="1" cellspacing="1" border="0">
-<tr><td valign="middle" align="left"><a href="#SEC1" title="Section 
pr&eacute;c&eacute;dente dans l'ordre de lecture"><img src="a_left.png" 
border="0" alt="Retour: 1. chapter" align="middle"></a></td>
-<td valign="middle" align="left"><a href="#SEC3" title="Section suivante dans 
l'ordre de lecture"><img src="a_right.png" border="0" alt="Avant: 1.1.1 
subsection" align="middle"></a></td>
+<tr><td valign="middle" align="left"><a href="#SEC1" title="Section 
pr&eacute;c&eacute;dente dans l&rsquo;ordre de lecture"><img src="a_left.png" 
border="0" alt="Retour: 1. chapter" align="middle"></a></td>
+<td valign="middle" align="left"><a href="#SEC3" title="Section suivante dans 
l&rsquo;ordre de lecture"><img src="a_right.png" border="0" alt="Avant: 1.1.1 
subsection" align="middle"></a></td>
 <td valign="middle" align="left"> &nbsp; </td>
 <td valign="middle" align="left"><a href="#SEC1" title="D&eacute;but de ce 
chapitre ou chapitre pr&eacute;c&eacute;dent"><img src="a_leftdouble.png" 
border="0" alt="RetourRapide: 1. chapter" align="middle"></a></td>
 <td valign="middle" align="left"><a href="#SEC1" title="Section 
sup&eacute;rieure"><img src="a_up.png" border="0" alt="Monter: 1. chapter" 
align="middle"></a></td>
@@ -2077,7 +2077,7 @@
 <td valign="middle" align="left"><a href="#SEC_Top" title="Couverture (top) du 
document"><img src="a_top.png" border="0" alt="Top: Top section" 
align="middle"></a></td>
 <td valign="middle" align="left"><a href="#SEC_Contents" title="Table des 
mati&egrave;res"><img src="a_tableofcon.png" border="0" alt="Table des 
mati&egrave;res: Table des mati&egrave;res" align="middle"></a></td>
 <td valign="middle" align="left"><a href="#SEC_Top" title="Index"><img 
src="a_index.png" border="0" alt="Index: Top section" align="middle"></a></td>
-<td valign="middle" align="left"><a href="#SEC_About" title="A propos (page 
d'aide)"><img src="a_help.png" border="0" alt="A propos: A propos de ce 
document" align="middle"></a></td>
+<td valign="middle" align="left"><a href="#SEC_About" title="A propos (page 
d&rsquo;aide)"><img src="a_help.png" border="0" alt="A propos: A propos de ce 
document" align="middle"></a></td>
 </tr></table>
 <h2 class="section"> 1.1 A section </h2>
 
@@ -2090,8 +2090,8 @@
 <a name="subsection"></a>
 <a name="SEC3"></a>
 <table cellpadding="1" cellspacing="1" border="0">
-<tr><td valign="middle" align="left"><a href="#SEC2" title="Section 
pr&eacute;c&eacute;dente dans l'ordre de lecture"><img src="a_left.png" 
border="0" alt="Retour: 1.1 A section" align="middle"></a></td>
-<td valign="middle" align="left"><a href="#SEC4" title="Section suivante dans 
l'ordre de lecture"><img src="a_right.png" border="0" alt="Avant: 1.1.1.1 
subsubsection" align="middle"></a></td>
+<tr><td valign="middle" align="left"><a href="#SEC2" title="Section 
pr&eacute;c&eacute;dente dans l&rsquo;ordre de lecture"><img src="a_left.png" 
border="0" alt="Retour: 1.1 A section" align="middle"></a></td>
+<td valign="middle" align="left"><a href="#SEC4" title="Section suivante dans 
l&rsquo;ordre de lecture"><img src="a_right.png" border="0" alt="Avant: 1.1.1.1 
subsubsection" align="middle"></a></td>
 <td valign="middle" align="left"> &nbsp; </td>
 <td valign="middle" align="left"><a href="#SEC1" title="D&eacute;but de ce 
chapitre ou chapitre pr&eacute;c&eacute;dent"><img src="a_leftdouble.png" 
border="0" alt="RetourRapide: 1. chapter" align="middle"></a></td>
 <td valign="middle" align="left"><a href="#SEC2" title="Section 
sup&eacute;rieure"><img src="a_up.png" border="0" alt="Monter: 1.1 A section" 
align="middle"></a></td>
@@ -2103,7 +2103,7 @@
 <td valign="middle" align="left"><a href="#SEC_Top" title="Couverture (top) du 
document"><img src="a_top.png" border="0" alt="Top: Top section" 
align="middle"></a></td>
 <td valign="middle" align="left"><a href="#SEC_Contents" title="Table des 
mati&egrave;res"><img src="a_tableofcon.png" border="0" alt="Table des 
mati&egrave;res: Table des mati&egrave;res" align="middle"></a></td>
 <td valign="middle" align="left"><a href="#SEC_Top" title="Index"><img 
src="a_index.png" border="0" alt="Index: Top section" align="middle"></a></td>
-<td valign="middle" align="left"><a href="#SEC_About" title="A propos (page 
d'aide)"><img src="a_help.png" border="0" alt="A propos: A propos de ce 
document" align="middle"></a></td>
+<td valign="middle" align="left"><a href="#SEC_About" title="A propos (page 
d&rsquo;aide)"><img src="a_help.png" border="0" alt="A propos: A propos de ce 
document" align="middle"></a></td>
 </tr></table>
 <h3 class="subsection"> 1.1.1 subsection </h3>
 
@@ -2118,8 +2118,8 @@
 <a name="subsubsection"></a>
 <a name="SEC4"></a>
 <table cellpadding="1" cellspacing="1" border="0">
-<tr><td valign="middle" align="left"><a href="#SEC3" title="Section 
pr&eacute;c&eacute;dente dans l'ordre de lecture"><img src="a_left.png" 
border="0" alt="Retour: 1.1.1 subsection" align="middle"></a></td>
-<td valign="middle" align="left"><a href="#SEC5" title="Section suivante dans 
l'ordre de lecture"><img src="a_right.png" border="0" alt="Avant: 2. chapter 2" 
align="middle"></a></td>
+<tr><td valign="middle" align="left"><a href="#SEC3" title="Section 
pr&eacute;c&eacute;dente dans l&rsquo;ordre de lecture"><img src="a_left.png" 
border="0" alt="Retour: 1.1.1 subsection" align="middle"></a></td>
+<td valign="middle" align="left"><a href="#SEC5" title="Section suivante dans 
l&rsquo;ordre de lecture"><img src="a_right.png" border="0" alt="Avant: 2. 
chapter 2" align="middle"></a></td>
 <td valign="middle" align="left"> &nbsp; </td>
 <td valign="middle" align="left"><a href="#SEC1" title="D&eacute;but de ce 
chapitre ou chapitre pr&eacute;c&eacute;dent"><img src="a_leftdouble.png" 
border="0" alt="RetourRapide: 1. chapter" align="middle"></a></td>
 <td valign="middle" align="left"><a href="#SEC3" title="Section 
sup&eacute;rieure"><img src="a_up.png" border="0" alt="Monter: 1.1.1 
subsection" align="middle"></a></td>
@@ -2131,7 +2131,7 @@
 <td valign="middle" align="left"><a href="#SEC_Top" title="Couverture (top) du 
document"><img src="a_top.png" border="0" alt="Top: Top section" 
align="middle"></a></td>
 <td valign="middle" align="left"><a href="#SEC_Contents" title="Table des 
mati&egrave;res"><img src="a_tableofcon.png" border="0" alt="Table des 
mati&egrave;res: Table des mati&egrave;res" align="middle"></a></td>
 <td valign="middle" align="left"><a href="#SEC_Top" title="Index"><img 
src="a_index.png" border="0" alt="Index: Top section" align="middle"></a></td>
-<td valign="middle" align="left"><a href="#SEC_About" title="A propos (page 
d'aide)"><img src="a_help.png" border="0" alt="A propos: A propos de ce 
document" align="middle"></a></td>
+<td valign="middle" align="left"><a href="#SEC_About" title="A propos (page 
d&rsquo;aide)"><img src="a_help.png" border="0" alt="A propos: A propos de ce 
document" align="middle"></a></td>
 </tr></table>
 <h4 class="subsubsection"> 1.1.1.1 subsubsection </h4>
 
@@ -2139,7 +2139,7 @@
 <a name="chapter2"></a>
 <a name="SEC5"></a>
 <table cellpadding="1" cellspacing="1" border="0">
-<tr><td valign="middle" align="left"><a href="#SEC4" title="Section 
pr&eacute;c&eacute;dente dans l'ordre de lecture"><img src="a_left.png" 
border="0" alt="Retour: 1.1.1.1 subsubsection" align="middle"></a></td>
+<tr><td valign="middle" align="left"><a href="#SEC4" title="Section 
pr&eacute;c&eacute;dente dans l&rsquo;ordre de lecture"><img src="a_left.png" 
border="0" alt="Retour: 1.1.1.1 subsubsection" align="middle"></a></td>
 <td valign="middle" align="left"><img src="a_right_na.png" border="0" 
alt="Avant: 2. chapter 2" align="middle"></td>
 <td valign="middle" align="left"> &nbsp; </td>
 <td valign="middle" align="left"><a href="#SEC1" title="D&eacute;but de ce 
chapitre ou chapitre pr&eacute;c&eacute;dent"><img src="a_leftdouble.png" 
border="0" alt="RetourRapide: 1. chapter" align="middle"></a></td>
@@ -2152,7 +2152,7 @@
 <td valign="middle" align="left"><a href="#SEC_Top" title="Couverture (top) du 
document"><img src="a_top.png" border="0" alt="Top: Top section" 
align="middle"></a></td>
 <td valign="middle" align="left"><a href="#SEC_Contents" title="Table des 
mati&egrave;res"><img src="a_tableofcon.png" border="0" alt="Table des 
mati&egrave;res: Table des mati&egrave;res" align="middle"></a></td>
 <td valign="middle" align="left"><a href="#SEC_Top" title="Index"><img 
src="a_index.png" border="0" alt="Index: Top section" align="middle"></a></td>
-<td valign="middle" align="left"><a href="#SEC_About" title="A propos (page 
d'aide)"><img src="a_help.png" border="0" alt="A propos: A propos de ce 
document" align="middle"></a></td>
+<td valign="middle" align="left"><a href="#SEC_About" title="A propos (page 
d&rsquo;aide)"><img src="a_help.png" border="0" alt="A propos: A propos de ce 
document" align="middle"></a></td>
 </tr></table>
 <h1 class="centerchap" align="center"> 2. chapter 2 </h1>
 
@@ -2171,7 +2171,7 @@
  &nbsp; 
 </td></tr></table>
 <table border="0" class="index-cp">
-<tr><td></td><th align="left">Entr&eacute;e d'index</th><th align="left"> 
Section</th></tr>
+<tr><td></td><th align="left">Entr&eacute;e d&rsquo;index</th><th 
align="left"> Section</th></tr>
 <tr><td colspan="3"> <hr></td></tr>
 <tr><th><a name="SEC5_0">&quot;</a></th><td></td><td></td></tr>
 <tr><td></td><td valign="top"><a href="#SEC_Top">&ldquo;</a></td><td 
valign="top"><a href="#SEC_Top">Top section</a></td></tr>
@@ -2238,7 +2238,7 @@
  &nbsp; 
 </td></tr></table>
 <table border="0" class="index-fn">
-<tr><td></td><th align="left">Entr&eacute;e d'index</th><th align="left"> 
Section</th></tr>
+<tr><td></td><th align="left">Entr&eacute;e d&rsquo;index</th><th 
align="left"> Section</th></tr>
 <tr><td colspan="3"> <hr></td></tr>
 <tr><th><a name="SEC5_0">&quot;</a></th><td></td><td></td></tr>
 <tr><td></td><td valign="top"><a href="#SEC_Top"><code>``</code></a></td><td 
valign="top"><a href="#SEC_Top">Top section</a></td></tr>
@@ -2405,7 +2405,7 @@
 <tr><td valign="middle" align="left"><a href="#SEC_Top" title="Couverture 
(top) du document"><img src="a_top.png" border="0" alt="Top: Top section" 
align="middle"></a></td>
 <td valign="middle" align="left"><a href="#SEC_Contents" title="Table des 
mati&egrave;res"><img src="a_tableofcon.png" border="0" alt="Table des 
mati&egrave;res: Table des mati&egrave;res" align="middle"></a></td>
 <td valign="middle" align="left"><a href="#SEC_Top" title="Index"><img 
src="a_index.png" border="0" alt="Index: Top section" align="middle"></a></td>
-<td valign="middle" align="left"><a href="#SEC_About" title="A propos (page 
d'aide)"><img src="a_help.png" border="0" alt="A propos: A propos de ce 
document" align="middle"></a></td>
+<td valign="middle" align="left"><a href="#SEC_About" title="A propos (page 
d&rsquo;aide)"><img src="a_help.png" border="0" alt="A propos: A propos de ce 
document" align="middle"></a></td>
 </tr></table>
 <h1>Notes de bas de page</h1>
 <h3><a name="FOOT1" href="#DOCF1">(1)</a></h3>
@@ -2424,7 +2424,7 @@
 <tr><td valign="middle" align="left"><a href="#SEC_Top" title="Couverture 
(top) du document"><img src="a_top.png" border="0" alt="Top: Top section" 
align="middle"></a></td>
 <td valign="middle" align="left"><a href="#SEC_Contents" title="Table des 
mati&egrave;res"><img src="a_tableofcon.png" border="0" alt="Table des 
mati&egrave;res: Table des mati&egrave;res" align="middle"></a></td>
 <td valign="middle" align="left"><a href="#SEC_Top" title="Index"><img 
src="a_index.png" border="0" alt="Index: Top section" align="middle"></a></td>
-<td valign="middle" align="left"><a href="#SEC_About" title="A propos (page 
d'aide)"><img src="a_help.png" border="0" alt="A propos: A propos de ce 
document" align="middle"></a></td>
+<td valign="middle" align="left"><a href="#SEC_About" title="A propos (page 
d&rsquo;aide)"><img src="a_help.png" border="0" alt="A propos: A propos de ce 
document" align="middle"></a></td>
 </tr></table>
 <h1>Table des mati&egrave;res</h1>
 <div class="contents">
@@ -2451,7 +2451,7 @@
 <tr><td valign="middle" align="left"><a href="#SEC_Top" title="Couverture 
(top) du document"><img src="a_top.png" border="0" alt="Top: Top section" 
align="middle"></a></td>
 <td valign="middle" align="left"><a href="#SEC_Contents" title="Table des 
mati&egrave;res"><img src="a_tableofcon.png" border="0" alt="Table des 
mati&egrave;res: Table des mati&egrave;res" align="middle"></a></td>
 <td valign="middle" align="left"><a href="#SEC_Top" title="Index"><img 
src="a_index.png" border="0" alt="Index: Top section" align="middle"></a></td>
-<td valign="middle" align="left"><a href="#SEC_About" title="A propos (page 
d'aide)"><img src="a_help.png" border="0" alt="A propos: A propos de ce 
document" align="middle"></a></td>
+<td valign="middle" align="left"><a href="#SEC_About" title="A propos (page 
d&rsquo;aide)"><img src="a_help.png" border="0" alt="A propos: A propos de ce 
document" align="middle"></a></td>
 </tr></table>
 <h1>R&eacute;sum&eacute; du contenu</h1>
 <div class="shortcontents">
@@ -2466,7 +2466,7 @@
 <tr><td valign="middle" align="left"><a href="#SEC_Top" title="Couverture 
(top) du document"><img src="a_top.png" border="0" alt="Top: Top section" 
align="middle"></a></td>
 <td valign="middle" align="left"><a href="#SEC_Contents" title="Table des 
mati&egrave;res"><img src="a_tableofcon.png" border="0" alt="Table des 
mati&egrave;res: Table des mati&egrave;res" align="middle"></a></td>
 <td valign="middle" align="left"><a href="#SEC_Top" title="Index"><img 
src="a_index.png" border="0" alt="Index: Top section" align="middle"></a></td>
-<td valign="middle" align="left"><a href="#SEC_About" title="A propos (page 
d'aide)"><img src="a_help.png" border="0" alt="A propos: A propos de ce 
document" align="middle"></a></td>
+<td valign="middle" align="left"><a href="#SEC_About" title="A propos (page 
d&rsquo;aide)"><img src="a_help.png" border="0" alt="A propos: A propos de ce 
document" align="middle"></a></td>
 </tr></table>
 <h1>A propos de ce document</h1>
 <p>
@@ -2485,13 +2485,13 @@
   <tr>
     <td align="center"><img src="a_left.png" border="0" alt="Retour" 
align="middle"></td>
     <td align="center">Retour</td>
-    <td>Section pr&eacute;c&eacute;dente dans l'ordre de lecture</td>
+    <td>Section pr&eacute;c&eacute;dente dans l&rsquo;ordre de lecture</td>
     <td>1.2.2</td>
   </tr>
   <tr>
     <td align="center"><img src="a_right.png" border="0" alt="Avant" 
align="middle"></td>
     <td align="center">Avant</td>
-    <td>Section suivante dans l'ordre de lecture</td>
+    <td>Section suivante dans l&rsquo;ordre de lecture</td>
     <td>1.2.4</td>
   </tr>
   <tr>
@@ -2533,7 +2533,7 @@
   <tr>
     <td align="center"><img src="a_help.png" border="0" alt="A propos" 
align="middle"></td>
     <td align="center">A propos</td>
-    <td>A propos (page d'aide)</td>
+    <td>A propos (page d&rsquo;aide)</td>
     <td> &nbsp; </td>
   </tr>
 </table>

Index: Tests/formatting_res/imbrications.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/formatting_res/imbrications.html,v
retrieving revision 1.35
retrieving revision 1.36
diff -u -b -r1.35 -r1.36
--- Tests/formatting_res/imbrications.html      2 Oct 2007 09:17:08 -0000       
1.35
+++ Tests/formatting_res/imbrications.html      3 Oct 2007 09:34:38 -0000       
1.36
@@ -108,7 +108,7 @@
 </dt>
 <dd><p>A nice function
 </p>
-<p>makeinfo accepts a menu within defun but it isn't possible
+<p>makeinfo accepts a menu within defun but it isn&rsquo;t possible
 to follow it
 </p>
 <table class="menu" border="0" cellspacing="0">
@@ -151,7 +151,7 @@
 <p><code></code>
 </p>                           
 <p>ref with uref within:<br>                                                   
  
-<a href="index3.html#node">cross ref with uref <a 
href="href://http/myhost.com/index.html">uref1</a>: (info file with uref3 <a 
href="href://http/myhost.com/index3.html">uref3</a>)node</a> section `title 
with uref2 <a href="href://http/myhost.com/index2.html">uref2</a>' in 
<cite>printed manual with uref4 <a 
href="href://http/myhost.com/index4.html">uref4</a></cite>
+<a href="index3.html#node">cross ref with uref <a 
href="href://http/myhost.com/index.html">uref1</a>: (info file with uref3 <a 
href="href://http/myhost.com/index3.html">uref3</a>)node</a> section 
&lsquo;title with uref2 <a 
href="href://http/myhost.com/index2.html">uref2</a>&rsquo; in <cite>printed 
manual with uref4 <a href="href://http/myhost.com/index4.html">uref4</a></cite>
 </p>
 <p>footnote with code within:<br>                                              
                                  
 <a name="DOCF1" href="#FOOT1">(1)</a>

Index: Tests/formatting_res/no_unicode_nodetest.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/formatting_res/no_unicode_nodetest.html,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -b -r1.11 -r1.12
--- Tests/formatting_res/no_unicode_nodetest.html       30 Sep 2007 12:47:17 
-0000      1.11
+++ Tests/formatting_res/no_unicode_nodetest.html       3 Oct 2007 09:34:38 
-0000       1.12
@@ -459,7 +459,7 @@
 <td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? 
</a>]</td>
 </tr></table>
 <h2 class="section"> 2.1 &aacute; </h2>
-<p>With brace &aacute;. Testing ' &quot; ` ^.
+<p>With brace &aacute;. Testing &rsquo; &quot; &lsquo; ^.
 </p><hr size="6">
 <a name="g_t_00e9"></a>
 <a name="SEC18"></a>

Index: Tests/formatting_res/no_unicode_nodetest_latin1.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/formatting_res/no_unicode_nodetest_latin1.html,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -b -r1.9 -r1.10
--- Tests/formatting_res/no_unicode_nodetest_latin1.html        30 Sep 2007 
12:47:18 -0000      1.9
+++ Tests/formatting_res/no_unicode_nodetest_latin1.html        3 Oct 2007 
09:34:38 -0000       1.10
@@ -415,7 +415,7 @@
 <td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? 
</a>]</td>
 </tr></table>
 <h2 class="section"> 2.1 &aacute; </h2>
-<p>With brace &aacute;. Testing ' &quot; ` ^.
+<p>With brace &aacute;. Testing &rsquo; &quot; &lsquo; ^.
 </p><hr size="6">
 <a name="g_t_00e9"></a>
 <a name="SEC16"></a>

Index: Tests/formatting_res/no_unicode_nodetest_utf8.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/formatting_res/no_unicode_nodetest_utf8.html,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -b -r1.10 -r1.11
--- Tests/formatting_res/no_unicode_nodetest_utf8.html  30 Sep 2007 12:47:18 
-0000      1.10
+++ Tests/formatting_res/no_unicode_nodetest_utf8.html  3 Oct 2007 09:34:39 
-0000       1.11
@@ -415,7 +415,7 @@
 <td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? 
</a>]</td>
 </tr></table>
 <h2 class="section"> 2.1 &aacute; </h2>
-<p>With brace &aacute;. Testing ' &quot; ` ^.
+<p>With brace &aacute;. Testing &rsquo; &quot; &lsquo; ^.
 </p><hr size="6">
 <a name="g_t_00c3_00a9"></a>
 <a name="SEC16"></a>

Index: Tests/formatting_res/node_test_refs.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/formatting_res/node_test_refs.html,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -b -r1.2 -r1.3
--- Tests/formatting_res/node_test_refs.html    5 Feb 2007 15:30:23 -0000       
1.2
+++ Tests/formatting_res/node_test_refs.html    3 Oct 2007 09:34:39 -0000       
1.3
@@ -86,7 +86,7 @@
 <a name="SEC3"></a>
 <h3 class="subheading"> Testing local nodes </h3>
 
-<p><tt>!_&quot;#$%&amp;'()*+-./;&lt;=&gt;?[\]^_`|~</tt> <a 
href="_0021_005f_0022_0023_0024_0025_0026_0027_0028_0029_002a_002b_002d_002e_002f_003b_003c_003d_003e_003f_005b_005c_005d_005e_005f_0060_007c_007e.html#g_t_0021_005f_0022_0023_0024_0025_0026_0027_0028_0029_002a_002b_002d_002e_002f_003b_003c_003d_003e_003f_005b_005c_005d_005e_005f_0060_007c_007e">!_&quot;#$%&amp;'()*+-./;&lt;=&gt;?[\]^_`|~</a><br>
+<p><tt>!_&quot;#$%&amp;'()*+-./;&lt;=&gt;?[\]^_`|~</tt> <a 
href="_0021_005f_0022_0023_0024_0025_0026_0027_0028_0029_002a_002b_002d_002e_002f_003b_003c_003d_003e_003f_005b_005c_005d_005e_005f_0060_007c_007e.html#g_t_0021_005f_0022_0023_0024_0025_0026_0027_0028_0029_002a_002b_002d_002e_002f_003b_003c_003d_003e_003f_005b_005c_005d_005e_005f_0060_007c_007e">!_&quot;#$%&amp;&rsquo;()*+-./;&lt;=&gt;?[\]^_&lsquo;|~</a><br>
 </p><table><tr><td>&nbsp;</td><td><pre class="example">target: 
#_0021_005f_0022_0023_0024_0025_0026_0027_0028_0029_002a_002b_002d_002e_002f_003b_003c_003d_003e_003f_005b_005c_005d_005e_005f_0060_007c_007e
 </pre></td></tr></table>
 

Index: Tests/formatting_res/nodetest_2.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/formatting_res/nodetest_2.html,v
retrieving revision 1.18
retrieving revision 1.19
diff -u -b -r1.18 -r1.19
--- Tests/formatting_res/nodetest_2.html        5 Feb 2007 15:30:23 -0000       
1.18
+++ Tests/formatting_res/nodetest_2.html        3 Oct 2007 09:34:39 -0000       
1.19
@@ -94,7 +94,7 @@
 <td valign="middle" align="left">[<a href="nodetest_abt.html#SEC_About" 
title="About (help)"> ? </a>]</td>
 </tr></table>
 <h2 class="section"> 2.1 &aacute; </h2>
-<p>With brace &aacute;. Testing ' &quot; ` ^.
+<p>With brace &aacute;. Testing &rsquo; &quot; &lsquo; ^.
 </p><hr size="6">
 <a name="g_t_00e9"></a>
 <a name="SEC18"></a>

Index: Tests/formatting_res/nodetest_latin1.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/formatting_res/nodetest_latin1.html,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -b -r1.13 -r1.14
--- Tests/formatting_res/nodetest_latin1.html   30 Sep 2007 12:47:18 -0000      
1.13
+++ Tests/formatting_res/nodetest_latin1.html   3 Oct 2007 09:34:39 -0000       
1.14
@@ -415,7 +415,7 @@
 <td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? 
</a>]</td>
 </tr></table>
 <h2 class="section"> 2.1 &aacute; </h2>
-<p>With brace &aacute;. Testing ' &quot; ` ^.
+<p>With brace &aacute;. Testing &rsquo; &quot; &lsquo; ^.
 </p><hr size="6">
 <a name="g_t_00e9"></a>
 <a name="SEC16"></a>

Index: Tests/formatting_res/nodetest_utf8.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/formatting_res/nodetest_utf8.html,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -b -r1.13 -r1.14
--- Tests/formatting_res/nodetest_utf8.html     30 Sep 2007 12:47:18 -0000      
1.13
+++ Tests/formatting_res/nodetest_utf8.html     3 Oct 2007 09:34:39 -0000       
1.14
@@ -415,7 +415,7 @@
 <td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? 
</a>]</td>
 </tr></table>
 <h2 class="section"> 2.1 &aacute; </h2>
-<p>With brace &aacute;. Testing ' &quot; ` ^.
+<p>With brace &aacute;. Testing &rsquo; &quot; &lsquo; ^.
 </p><hr size="6">
 <a name="g_t_00e9"></a>
 <a name="SEC16"></a>

Index: Tests/formatting_res/other-nodes.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/formatting_res/other-nodes.html,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -b -r1.9 -r1.10
--- Tests/formatting_res/other-nodes.html       5 Feb 2007 15:30:23 -0000       
1.9
+++ Tests/formatting_res/other-nodes.html       3 Oct 2007 09:34:39 -0000       
1.10
@@ -70,7 +70,7 @@
 </pre></td></tr></table>
 
 <table class="menu" border="0" cellspacing="0">
-<tr><td align="left" valign="top"><a 
href="_0021_005f_0022_0023_0024_0025_0026_0027_0028_0029_002a_002b_002d_002e_002f_003b_003c_003d_003e_003f_005b_005c_005d_005e_005f_0060_007c_007e.html#g_t_0021_005f_0022_0023_0024_0025_0026_0027_0028_0029_002a_002b_002d_002e_002f_003b_003c_003d_003e_003f_005b_005c_005d_005e_005f_0060_007c_007e">&bull;
 !_&quot;#$%&amp;'()*+-./;&lt;=&gt;?[\]^_`|~</a></td><td>&nbsp;&nbsp;</td><td 
align="left" valign="top">
+<tr><td align="left" valign="top"><a 
href="_0021_005f_0022_0023_0024_0025_0026_0027_0028_0029_002a_002b_002d_002e_002f_003b_003c_003d_003e_003f_005b_005c_005d_005e_005f_0060_007c_007e.html#g_t_0021_005f_0022_0023_0024_0025_0026_0027_0028_0029_002a_002b_002d_002e_002f_003b_003c_003d_003e_003f_005b_005c_005d_005e_005f_0060_007c_007e">&bull;
 
!_&quot;#$%&amp;&rsquo;()*+-./;&lt;=&gt;?[\]^_&lsquo;|~</a></td><td>&nbsp;&nbsp;</td><td
 align="left" valign="top">
 </td></tr>
 <tr><td align="left" valign="top"><a href="local-node.html#local-node">&bull; 
local node</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">
 </td></tr>

Index: Tests/formatting_res/quotes.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/formatting_res/quotes.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- Tests/formatting_res/quotes.html    30 Sep 2007 12:47:18 -0000      1.1
+++ Tests/formatting_res/quotes.html    3 Oct 2007 09:34:39 -0000       1.2
@@ -76,30 +76,30 @@
 
 <p>No value for print_utf8
 </p>
-<p>&ldquo;simple-double&ndash;three&mdash;four&mdash;-&rdquo; `simple' 
quotedblleft: &ldquo; <br>
+<p>&ldquo;simple-double&ndash;three&mdash;four&mdash;-&rdquo; 
&lsquo;simple&rsquo; quotedblleft: &ldquo; <br>
 code: <code>``simple-double--three---four----'' `simple' quotedblleft: 
&ldquo;</code> <br>
-asis: &ldquo;simple-double&ndash;three&mdash;four&mdash;-&rdquo; `simple' 
quotedblleft: &ldquo; <br>
-strong: <strong>&ldquo;simple-double&ndash;three&mdash;four&mdash;-&rdquo; 
`simple' quotedblleft: &ldquo;</strong> <br>
+asis: &ldquo;simple-double&ndash;three&mdash;four&mdash;-&rdquo; 
&lsquo;simple&rsquo; quotedblleft: &ldquo; <br>
+strong: <strong>&ldquo;simple-double&ndash;three&mdash;four&mdash;-&rdquo; 
&lsquo;simple&rsquo; quotedblleft: &ldquo;</strong> <br>
 kbd: <kbd>``simple-double--three---four----'' `simple' quotedblleft: 
&ldquo;</kbd> <br>
 samp: &lsquo;<samp>``simple-double--three---four----'' `simple' quotedblleft: 
&ldquo;</samp>&rsquo; <br>
 </p>
 <table><tr><td>&nbsp;</td><td><pre class="example">@set txicodequoteundirected
 @set txicodequotebacktick
 </pre></td></tr></table>
-<p>&ldquo;simple-double&ndash;three&mdash;four&mdash;-&rdquo; `simple' 
quotedblleft: &ldquo; <br>
+<p>&ldquo;simple-double&ndash;three&mdash;four&mdash;-&rdquo; 
&lsquo;simple&rsquo; quotedblleft: &ldquo; <br>
 code: <code>``simple-double--three---four----'' `simple' quotedblleft: 
&ldquo;</code> <br>
-asis: &ldquo;simple-double&ndash;three&mdash;four&mdash;-&rdquo; `simple' 
quotedblleft: &ldquo; <br>
-strong: <strong>&ldquo;simple-double&ndash;three&mdash;four&mdash;-&rdquo; 
`simple' quotedblleft: &ldquo;</strong> <br>
+asis: &ldquo;simple-double&ndash;three&mdash;four&mdash;-&rdquo; 
&lsquo;simple&rsquo; quotedblleft: &ldquo; <br>
+strong: <strong>&ldquo;simple-double&ndash;three&mdash;four&mdash;-&rdquo; 
&lsquo;simple&rsquo; quotedblleft: &ldquo;</strong> <br>
 kbd: <kbd>``simple-double--three---four----'' `simple' quotedblleft: 
&ldquo;</kbd> <br>
 samp: &lsquo;<samp>``simple-double--three---four----'' `simple' quotedblleft: 
&ldquo;</samp>&rsquo; <br>
 </p>
 <table><tr><td>&nbsp;</td><td><pre class="example">@clear 
txicodequoteundirected
 @clear txicodequotebacktick
 </pre></td></tr></table>
-<p>&ldquo;simple-double&ndash;three&mdash;four&mdash;-&rdquo; `simple' 
quotedblleft: &ldquo; <br>
+<p>&ldquo;simple-double&ndash;three&mdash;four&mdash;-&rdquo; 
&lsquo;simple&rsquo; quotedblleft: &ldquo; <br>
 code: <code>``simple-double--three---four----'' `simple' quotedblleft: 
&ldquo;</code> <br>
-asis: &ldquo;simple-double&ndash;three&mdash;four&mdash;-&rdquo; `simple' 
quotedblleft: &ldquo; <br>
-strong: <strong>&ldquo;simple-double&ndash;three&mdash;four&mdash;-&rdquo; 
`simple' quotedblleft: &ldquo;</strong> <br>
+asis: &ldquo;simple-double&ndash;three&mdash;four&mdash;-&rdquo; 
&lsquo;simple&rsquo; quotedblleft: &ldquo; <br>
+strong: <strong>&ldquo;simple-double&ndash;three&mdash;four&mdash;-&rdquo; 
&lsquo;simple&rsquo; quotedblleft: &ldquo;</strong> <br>
 kbd: <kbd>``simple-double--three---four----'' `simple' quotedblleft: 
&ldquo;</kbd> <br>
 samp: &lsquo;<samp>``simple-double--three---four----'' `simple' quotedblleft: 
&ldquo;</samp>&rsquo; <br>
 </p>

Index: Tests/formatting_res/test_refs.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/formatting_res/test_refs.html,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -b -r1.12 -r1.13
--- Tests/formatting_res/test_refs.html 6 May 2007 12:57:06 -0000       1.12
+++ Tests/formatting_res/test_refs.html 3 Oct 2007 09:34:39 -0000       1.13
@@ -85,7 +85,7 @@
 <a name="SEC3"></a>
 <h3 class="subheading"> Testing local nodes </h3>
 
-<p><tt>!_&quot;#$%&amp;'()*+-./;&lt;=&gt;?[\]^_`|~</tt> <a 
href="#g_t_0021_005f_0022_0023_0024_0025_0026_0027_0028_0029_002a_002b_002d_002e_002f_003b_003c_003d_003e_003f_005b_005c_005d_005e_005f_0060_007c_007e">!_&quot;#$%&amp;'()*+-./;&lt;=&gt;?[\]^_`|~</a><br>
+<p><tt>!_&quot;#$%&amp;'()*+-./;&lt;=&gt;?[\]^_`|~</tt> <a 
href="#g_t_0021_005f_0022_0023_0024_0025_0026_0027_0028_0029_002a_002b_002d_002e_002f_003b_003c_003d_003e_003f_005b_005c_005d_005e_005f_0060_007c_007e">!_&quot;#$%&amp;&rsquo;()*+-./;&lt;=&gt;?[\]^_&lsquo;|~</a><br>
 </p><table><tr><td>&nbsp;</td><td><pre class="example">target: 
#_0021_005f_0022_0023_0024_0025_0026_0027_0028_0029_002a_002b_002d_002e_002f_003b_003c_003d_003e_003f_005b_005c_005d_005e_005f_0060_007c_007e
 </pre></td></tr></table>
 
@@ -126,7 +126,7 @@
 </pre></td></tr></table>
 
 <table class="menu" border="0" cellspacing="0">
-<tr><td align="left" valign="top"><a 
href="#g_t_0021_005f_0022_0023_0024_0025_0026_0027_0028_0029_002a_002b_002d_002e_002f_003b_003c_003d_003e_003f_005b_005c_005d_005e_005f_0060_007c_007e">&bull;
 !_&quot;#$%&amp;'()*+-./;&lt;=&gt;?[\]^_`|~</a></td><td>&nbsp;&nbsp;</td><td 
align="left" valign="top">
+<tr><td align="left" valign="top"><a 
href="#g_t_0021_005f_0022_0023_0024_0025_0026_0027_0028_0029_002a_002b_002d_002e_002f_003b_003c_003d_003e_003f_005b_005c_005d_005e_005f_0060_007c_007e">&bull;
 
!_&quot;#$%&amp;&rsquo;()*+-./;&lt;=&gt;?[\]^_&lsquo;|~</a></td><td>&nbsp;&nbsp;</td><td
 align="left" valign="top">
 </td></tr>
 <tr><td align="left" valign="top"><a href="#local-node">&bull; local 
node</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">
 </td></tr>

Index: Tests/formatting_res/umlaut.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/formatting_res/umlaut.html,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -b -r1.16 -r1.17
--- Tests/formatting_res/umlaut.html    6 May 2007 12:57:06 -0000       1.16
+++ Tests/formatting_res/umlaut.html    3 Oct 2007 09:34:39 -0000       1.17
@@ -83,7 +83,7 @@
 <p>macron:<br>
 &#333;
 </p>
-<p>I don't know any invalid macron:<br>
+<p>I don&rsquo;t know any invalid macron:<br>
 </p>
 
 <p>valid circumflex:<br>

Index: Tests/formatting_res/verbatim_html.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/formatting_res/verbatim_html.html,v
retrieving revision 1.43
retrieving revision 1.44
diff -u -b -r1.43 -r1.44
--- Tests/formatting_res/verbatim_html.html     2 Oct 2007 09:17:09 -0000       
1.43
+++ Tests/formatting_res/verbatim_html.html     3 Oct 2007 09:34:39 -0000       
1.44
@@ -53,7 +53,7 @@
 <table class="menu" border="0" cellspacing="0">
 <tr><td align="left" valign="top"><a href="#SEC1">1. first node 
chapter</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">    node 1
 </td></tr>
-<tr><td align="left" valign="top"><a href="#SEC2">2. node 'a with 
braces</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">    node with 
braces
+<tr><td align="left" valign="top"><a href="#SEC2">2. node &rsquo;a with 
braces</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">    node with 
braces
 </td></tr>
 <tr><td align="left" valign="top"><a href="manual.html#A-node">&bull; node: 
(manual)A node</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top"> node 
in another manual
 </td></tr>
@@ -63,7 +63,7 @@
 bidule
 
 </pre><pre class="menu-comment">
-</pre></th></tr><tr><td align="left" valign="top"><a href="#SEC3">3. node 'a 
without braces</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">      
 node without braces
+</pre></th></tr><tr><td align="left" valign="top"><a href="#SEC3">3. node 
&rsquo;a without braces</a></td><td>&nbsp;&nbsp;</td><td align="left" 
valign="top">       node without braces
 </td></tr>
 </table>
 
@@ -147,7 +147,7 @@
 
 
 <p>A list with bullet
-Before itemize, in that case @bullet isn'right, one needs @bullet{} (in info) 
</p><ul>
+Before itemize, in that case @bullet isn&rsquo;right, one needs @bullet{} (in 
info) </p><ul>
 <li> on the same line than item
 some text
 </li><li>
@@ -166,7 +166,7 @@
 
 
 @@@@ @ text before @end  verbatim </pre> Text following end verbatim, must be 
exactly one space 
-<p>between end and verbatim. @end verbatim doesn't need to begin at beginning 
+<p>between end and verbatim. @end verbatim doesn&rsquo;t need to begin at 
beginning 
 of line.
 </p>
 <p>In tex, @end verbatim must be on its own on a line.
@@ -186,7 +186,7 @@
 <p>Now html valid for TeX  <b>
 some html </b> Some text one the line following @end html
 </p>
-<p>And html on it's own line
+<p>And html on it&rsquo;s own line
 </p>
 <tt> an html tt</tt>
 
@@ -199,7 +199,7 @@
 <p>Ignore is the same than @html.
 </p>
 <p>Now ifnothtml on same line 
address@hidden ifnothtml doesn't need to begin the line, and there can be more
address@hidden ifnothtml doesn&rsquo;t need to begin the line, and there can be 
more
 than one space between @end and ifnothtml, but nothing more
 on the line.
 </p>
@@ -311,14 +311,14 @@
 <td valign="middle" align="left">[Index]</td>
 <td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? 
</a>]</td>
 </tr></table>
-<h1 class="chapter"> 2. node 'a with braces </h1>
+<h1 class="chapter"> 2. node &rsquo;a with braces </h1>
 <p>In the node with braces
 </p>
 <p>A footnote with an empty line within.
 <a name="DOCF1" href="#FOOT1">(1)</a> 
 </p>
-<p>Now a ref with a footnote within, there aren't 2 paragraphes in the footnote
-in that case in info. tex doesn't like the paragraph break in the ref
+<p>Now a ref with a footnote within, there aren&rsquo;t 2 paragraphes in the 
footnote
+in that case in info. tex doesn&rsquo;t like the paragraph break in the ref
 <a href="#SEC1">within ref a footnote <a name="DOCF2" 
href="#FOOT2">(2)</a></a>.
 </p>
 <p>Conversely, a ref in a footnote
@@ -352,7 +352,7 @@
 <td valign="middle" align="left">[Index]</td>
 <td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? 
</a>]</td>
 </tr></table>
-<h1 class="chapter"> 3. node 'a without braces </h1>
+<h1 class="chapter"> 3. node &rsquo;a without braces </h1>
 <table class="menu" border="0" cellspacing="0">
 <tr><td align="left" valign="top"><a href="#SEC4">3.1 
node</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top"></td></tr>
 </table>
@@ -437,8 +437,8 @@
 
 <ul class="toc">
   <li><a name="TOC1" href="#SEC1">1. first node chapter</a></li>
-  <li><a name="TOC2" href="#SEC2">2. node 'a with braces</a></li>
-  <li><a name="TOC3" href="#SEC3">3. node 'a without braces</a>
+  <li><a name="TOC2" href="#SEC2">2. node &rsquo;a with braces</a></li>
+  <li><a name="TOC3" href="#SEC3">3. node &rsquo;a without braces</a>
   <ul class="toc">
     <li><a name="TOC4" href="#SEC4">3.1 node</a></li>
   </ul>

Index: Tests/formatting_res/weird_quotes_formatting.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/formatting_res/weird_quotes_formatting.html,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -b -r1.12 -r1.13
--- Tests/formatting_res/weird_quotes_formatting.html   3 Oct 2007 07:39:32 
-0000       1.12
+++ Tests/formatting_res/weird_quotes_formatting.html   3 Oct 2007 09:34:39 
-0000       1.13
@@ -544,7 +544,7 @@
 strong: 
<strong>&ldquo;simple-double&ndash;three&mdash;four&mdash;-&rdquo;</strong> <br>
 kbd: <kbd>``simple-double--three---four----''</kbd> <br>
 </p>
-<p>``simple-double--three&mdash;four&mdash;-''<br>
+<p>&lsquo;&lsquo;simple-double--three&mdash;four&mdash;-&rsquo;&rsquo;<br>
 </p>
 <a name="IDX1"></a>
 <a name="IDX2"></a>
@@ -555,16 +555,16 @@
 @&quot;{U} &Uuml; 
 @~n &ntilde;
 @^a &acirc;
-@'e &eacute;
+@&rsquo;e &eacute;
 @=o &#333;
address@hidden &igrave;
-@'{e} &eacute;
-@'address@hidden &iacute; 
+@&lsquo;i &igrave;
+@&rsquo;{e} &eacute;
+@&rsquo;address@hidden &iacute; 
 @dotless{i} i
 @dotless{ij} ij
address@hidden@=E} &#274;` 
+@&lsquo;address@hidden &#274;` 
 @l{} &#322;
-@,{@'C} &#262;,
+@,{@&rsquo;C} &#262;,
 @,c &ccedil;
 @,c@&quot;u &ccedil;&uuml; <br>
 </p>
@@ -573,10 +573,10 @@
 <br>
 @,@&quot;u ,&uuml;
 </p>
-<p>Invalid use of @':<br>
-@' '
+<p>Invalid use of @&rsquo;:<br>
+@&rsquo; &rsquo;
 <br>
-@'@&quot;u @'&quot;u
+@&rsquo;@&quot;u @'&quot;u
 </p>
 <p>@dotless{truc} truc
 </p>
@@ -1029,9 +1029,9 @@
 <dd><p>d&ndash;eftypemethod
 </p></dd></dl>
 
-<p><code>@xref{c---hapter@@, cross r---ef name@@, t---itle@@, file n---ame@@, 
ma---nual@@}</code> See <a href="file 
n---ame@@.html#c_002d_002d_002dhapter_0040">cross r&mdash;ef name@: (file 
n&mdash;ame@)c&mdash;hapter@</a> section `t&mdash;itle@' in 
<cite>ma&mdash;nual@</cite>
-<code>@ref{chapter, cross ref name, title, file name, manual}</code> <a 
href="file name.html#chapter">cross ref name: (file name)chapter</a> section 
`title' in <cite>manual</cite>
-<code>@pxref{chapter, cross ref name, title, file name, manual}</code> see <a 
href="file name.html#chapter">cross ref name: (file name)chapter</a> section 
`title' in <cite>manual</cite>
+<p><code>@xref{c---hapter@@, cross r---ef name@@, t---itle@@, file n---ame@@, 
ma---nual@@}</code> See <a href="file 
n---ame@@.html#c_002d_002d_002dhapter_0040">cross r&mdash;ef name@: (file 
n&mdash;ame@)c&mdash;hapter@</a> section &lsquo;t&mdash;itle@&rsquo; in 
<cite>ma&mdash;nual@</cite>
+<code>@ref{chapter, cross ref name, title, file name, manual}</code> <a 
href="file name.html#chapter">cross ref name: (file name)chapter</a> section 
&lsquo;title&rsquo; in <cite>manual</cite>
+<code>@pxref{chapter, cross ref name, title, file name, manual}</code> see <a 
href="file name.html#chapter">cross ref name: (file name)chapter</a> section 
&lsquo;title&rsquo; in <cite>manual</cite>
 <code>@inforef{chapter, cross ref name, file name}</code> See <a href="file 
name.html#chapter">cross ref name: (file name)chapter</a>
 </p>
 <p><code>@ref{chapter}</code> <a href="#SEC1">chapter</a>
@@ -1043,40 +1043,40 @@
 <code>@ref{chapter,cross ref name}</code> <a href="#SEC1">cross ref name</a>
 <code>@ref{chapter,,title}</code> <a href="#SEC1">title</a>
 <code>@ref{chapter,,,file name}</code> <a href="file name.html#chapter">(file 
name)chapter</a>
-<code>@ref{chapter,,,,manual}</code> section `chapter' in <cite>manual</cite>
+<code>@ref{chapter,,,,manual}</code> section &lsquo;chapter&rsquo; in 
<cite>manual</cite>
 <code>@ref{node,cross ref name}</code> @ref{node,cross ref name}
 <code>@ref{node,,title}</code> @ref{node,,title}
 <code>@ref{node,,,file name}</code> <a href="file name.html#node">(file 
name)node</a>
-<code>@ref{node,,,,manual}</code> section `node' in <cite>manual</cite>
+<code>@ref{node,,,,manual}</code> section &lsquo;node&rsquo; in 
<cite>manual</cite>
 <code>@ref{chapter,cross ref name,title,}</code> <a href="#SEC1">title</a>
 <code>@ref{chapter,cross ref name,,file name}</code> <a href="file 
name.html#chapter">cross ref name: (file name)chapter</a>
-<code>@ref{chapter,cross ref name,,,manual}</code> section `chapter' in 
<cite>manual</cite>
+<code>@ref{chapter,cross ref name,,,manual}</code> section 
&lsquo;chapter&rsquo; in <cite>manual</cite>
 <code>@ref{node,cross ref name,title,}</code> @ref{node,cross ref name,title,}
 <code>@ref{node,cross ref name,,file name}</code> <a href="file 
name.html#node">cross ref name: (file name)node</a>
-<code>@ref{node,cross ref name,,,manual}</code> section `node' in 
<cite>manual</cite>
+<code>@ref{node,cross ref name,,,manual}</code> section &lsquo;node&rsquo; in 
<cite>manual</cite>
 <code>@ref{chapter,cross ref name,title,file name}</code> <a href="file 
name.html#chapter">cross ref name: (file name)chapter</a>
-<code>@ref{chapter,cross ref name,title,,manual}</code> section `title' in 
<cite>manual</cite>
+<code>@ref{chapter,cross ref name,title,,manual}</code> section 
&lsquo;title&rsquo; in <cite>manual</cite>
 <code>@ref{node,cross ref name,title,file name}</code> <a href="file 
name.html#node">cross ref name: (file name)node</a>
-<code>@ref{node,cross ref name,title,,manual}</code> section `title' in 
<cite>manual</cite>
-<code>@ref{chapter,cross ref name,title, file name, manual}</code> <a 
href="file name.html#chapter">cross ref name: (file name)chapter</a> section 
`title' in <cite>manual</cite>
-<code>@ref{node,cross ref name,title, file name, manual}</code> <a href="file 
name.html#node">cross ref name: (file name)node</a> section `title' in 
<cite>manual</cite>
+<code>@ref{node,cross ref name,title,,manual}</code> section 
&lsquo;title&rsquo; in <cite>manual</cite>
+<code>@ref{chapter,cross ref name,title, file name, manual}</code> <a 
href="file name.html#chapter">cross ref name: (file name)chapter</a> section 
&lsquo;title&rsquo; in <cite>manual</cite>
+<code>@ref{node,cross ref name,title, file name, manual}</code> <a href="file 
name.html#node">cross ref name: (file name)node</a> section &lsquo;title&rsquo; 
in <cite>manual</cite>
 <code>@ref{chapter,,title,file name}</code> <a href="file 
name.html#chapter">(file name)chapter</a>
-<code>@ref{chapter,,title,,manual}</code> section `title' in 
<cite>manual</cite>
+<code>@ref{chapter,,title,,manual}</code> section &lsquo;title&rsquo; in 
<cite>manual</cite>
 <code>@ref{node,,title,file name}</code> <a href="file name.html#node">(file 
name)node</a>
-<code>@ref{node,,title,,manual}</code> section `title' in <cite>manual</cite>
-<code>@ref{chapter,,title, file name, manual}</code> <a href="file 
name.html#chapter">(file name)chapter</a> section `title' in <cite>manual</cite>
-<code>@ref{node,,title, file name, manual}</code> <a href="file 
name.html#node">(file name)node</a> section `title' in <cite>manual</cite>
-<code>@ref{chapter,,,file name,manual}</code> <a href="file 
name.html#chapter">(file name)chapter</a> section `chapter' in 
<cite>manual</cite>
-<code>@ref{node,,,file name,manual}</code> <a href="file name.html#node">(file 
name)node</a> section `node' in <cite>manual</cite>
+<code>@ref{node,,title,,manual}</code> section &lsquo;title&rsquo; in 
<cite>manual</cite>
+<code>@ref{chapter,,title, file name, manual}</code> <a href="file 
name.html#chapter">(file name)chapter</a> section &lsquo;title&rsquo; in 
<cite>manual</cite>
+<code>@ref{node,,title, file name, manual}</code> <a href="file 
name.html#node">(file name)node</a> section &lsquo;title&rsquo; in 
<cite>manual</cite>
+<code>@ref{chapter,,,file name,manual}</code> <a href="file 
name.html#chapter">(file name)chapter</a> section &lsquo;chapter&rsquo; in 
<cite>manual</cite>
+<code>@ref{node,,,file name,manual}</code> <a href="file name.html#node">(file 
name)node</a> section &lsquo;node&rsquo; in <cite>manual</cite>
 <code>@ref{,cross ref name,title,}</code> @ref{,cross ref name,title,}
 <code>@ref{,cross ref name,,file name}</code> <a href="file 
name.html#Top">cross ref name: (file name)</a>
 <code>@ref{,cross ref name,,,manual}</code> <cite>manual</cite>
 <code>@ref{,cross ref name,title,file name}</code> <a href="file 
name.html#Top">cross ref name: (file name)</a>
-<code>@ref{,cross ref name,title,,manual}</code> section `title' in 
<cite>manual</cite>
-<code>@ref{,cross ref name,title, file name, manual}</code> <a href="file 
name.html#Top">cross ref name: (file name)</a> section `title' in 
<cite>manual</cite>
+<code>@ref{,cross ref name,title,,manual}</code> section &lsquo;title&rsquo; 
in <cite>manual</cite>
+<code>@ref{,cross ref name,title, file name, manual}</code> <a href="file 
name.html#Top">cross ref name: (file name)</a> section &lsquo;title&rsquo; in 
<cite>manual</cite>
 <code>@ref{,,title,file name}</code> <a href="file name.html#Top">(file 
name)</a>
-<code>@ref{,,title,,manual}</code> section `title' in <cite>manual</cite>
-<code>@ref{,,title, file name, manual}</code> <a href="file 
name.html#Top">(file name)</a> section `title' in <cite>manual</cite>
+<code>@ref{,,title,,manual}</code> section &lsquo;title&rsquo; in 
<cite>manual</cite>
+<code>@ref{,,title, file name, manual}</code> <a href="file 
name.html#Top">(file name)</a> section &lsquo;title&rsquo; in 
<cite>manual</cite>
 <code>@ref{,,,file name,manual}</code> <a href="file name.html#Top">(file 
name)</a> <cite>manual</cite>
 </p>
 <p><code>@inforef{chapter, cross ref name, file name}</code> See <a href="file 
name.html#chapter">cross ref name: (file name)chapter</a>
@@ -1093,7 +1093,7 @@
 </p>
 <p><code>@address@hidden, a @comma{} in cross
 ref, a address@hidden in title, a address@hidden in file, a @comma{} in manual 
name }</code>
-<a href="a address@hidden in file.html#s_002d_002dect_002cion">a , in cross 
ref: (a comma, in file)s&ndash;ect,ion</a> section `a comma, in title' in 
<cite>a , in manual name</cite>
+<a href="a address@hidden in file.html#s_002d_002dect_002cion">a , in cross 
ref: (a comma, in file)s&ndash;ect,ion</a> section &lsquo;a comma, in 
title&rsquo; in <cite>a , in manual name</cite>
 </p>
 <p><code>@address@hidden</code> <a href="#SEC2">A section</a>
 </p>

Index: 
Tests/htmlxref-only_mono_res/_0021_005f_0022_0023_0024_0025_0026_0027_0028_0029_002a_002b_002d_002e_002f_003b_003c_003d_003e_003f_005b_005c_005d_005e_005f_0060_007c_007e.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/htmlxref-only_mono_res/_0021_005f_0022_0023_0024_0025_0026_0027_0028_0029_002a_002b_002d_002e_002f_003b_003c_003d_003e_003f_005b_005c_005d_005e_005f_0060_007c_007e.html,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -b -r1.2 -r1.3
--- 
Tests/htmlxref-only_mono_res/_0021_005f_0022_0023_0024_0025_0026_0027_0028_0029_002a_002b_002d_002e_002f_003b_003c_003d_003e_003f_005b_005c_005d_005e_005f_0060_007c_007e.html
      5 Feb 2007 15:30:23 -0000       1.2
+++ 
Tests/htmlxref-only_mono_res/_0021_005f_0022_0023_0024_0025_0026_0027_0028_0029_002a_002b_002d_002e_002f_003b_003c_003d_003e_003f_005b_005c_005d_005e_005f_0060_007c_007e.html
      3 Oct 2007 09:34:39 -0000       1.3
@@ -59,7 +59,7 @@
 <td valign="middle" align="left">[<a href="test_refs_abt.html#SEC_About" 
title="About (help)"> ? </a>]</td>
 </tr></table>
 <hr size="1">
-<h3 class="node"> !_&quot;#$%&amp;'()*+-./;&lt;=&gt;?[\]^_`|~ </h3>
+<h3 class="node"> !_&quot;#$%&amp;&rsquo;()*+-./;&lt;=&gt;?[\]^_&lsquo;|~ </h3>
 <table><tr><td>&nbsp;</td><td><pre class="example">id: 
_0021_005f_0022_0023_0024_0025_0026_0027_0028_0029_002a_002b_002d_002e_002f_003b_003c_003d_003e_003f_005b_005c_005d_005e_005f_0060_007c_007e
 </pre></td></tr></table>
 

Index: Tests/htmlxref-only_mono_res/no_split_test_refs.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/htmlxref-only_mono_res/no_split_test_refs.html,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -b -r1.3 -r1.4
--- Tests/htmlxref-only_mono_res/no_split_test_refs.html        6 May 2007 
12:57:06 -0000       1.3
+++ Tests/htmlxref-only_mono_res/no_split_test_refs.html        3 Oct 2007 
09:34:39 -0000       1.4
@@ -85,7 +85,7 @@
 <a name="SEC3"></a>
 <h3 class="subheading"> Testing local nodes </h3>
 
-<p><tt>!_&quot;#$%&amp;'()*+-./;&lt;=&gt;?[\]^_`|~</tt> <a 
href="#g_t_0021_005f_0022_0023_0024_0025_0026_0027_0028_0029_002a_002b_002d_002e_002f_003b_003c_003d_003e_003f_005b_005c_005d_005e_005f_0060_007c_007e">!_&quot;#$%&amp;'()*+-./;&lt;=&gt;?[\]^_`|~</a><br>
+<p><tt>!_&quot;#$%&amp;'()*+-./;&lt;=&gt;?[\]^_`|~</tt> <a 
href="#g_t_0021_005f_0022_0023_0024_0025_0026_0027_0028_0029_002a_002b_002d_002e_002f_003b_003c_003d_003e_003f_005b_005c_005d_005e_005f_0060_007c_007e">!_&quot;#$%&amp;&rsquo;()*+-./;&lt;=&gt;?[\]^_&lsquo;|~</a><br>
 </p><table><tr><td>&nbsp;</td><td><pre class="example">target: 
#_0021_005f_0022_0023_0024_0025_0026_0027_0028_0029_002a_002b_002d_002e_002f_003b_003c_003d_003e_003f_005b_005c_005d_005e_005f_0060_007c_007e
 </pre></td></tr></table>
 
@@ -126,7 +126,7 @@
 </pre></td></tr></table>
 
 <table class="menu" border="0" cellspacing="0">
-<tr><td align="left" valign="top"><a 
href="#g_t_0021_005f_0022_0023_0024_0025_0026_0027_0028_0029_002a_002b_002d_002e_002f_003b_003c_003d_003e_003f_005b_005c_005d_005e_005f_0060_007c_007e">&bull;
 !_&quot;#$%&amp;'()*+-./;&lt;=&gt;?[\]^_`|~</a></td><td>&nbsp;&nbsp;</td><td 
align="left" valign="top">
+<tr><td align="left" valign="top"><a 
href="#g_t_0021_005f_0022_0023_0024_0025_0026_0027_0028_0029_002a_002b_002d_002e_002f_003b_003c_003d_003e_003f_005b_005c_005d_005e_005f_0060_007c_007e">&bull;
 
!_&quot;#$%&amp;&rsquo;()*+-./;&lt;=&gt;?[\]^_&lsquo;|~</a></td><td>&nbsp;&nbsp;</td><td
 align="left" valign="top">
 </td></tr>
 <tr><td align="left" valign="top"><a href="#local-node">&bull; local 
node</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">
 </td></tr>

Index: Tests/htmlxref-only_mono_res/other-nodes.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/htmlxref-only_mono_res/other-nodes.html,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -b -r1.2 -r1.3
--- Tests/htmlxref-only_mono_res/other-nodes.html       5 Feb 2007 15:30:23 
-0000       1.2
+++ Tests/htmlxref-only_mono_res/other-nodes.html       3 Oct 2007 09:34:39 
-0000       1.3
@@ -70,7 +70,7 @@
 </pre></td></tr></table>
 
 <table class="menu" border="0" cellspacing="0">
-<tr><td align="left" valign="top"><a 
href="_0021_005f_0022_0023_0024_0025_0026_0027_0028_0029_002a_002b_002d_002e_002f_003b_003c_003d_003e_003f_005b_005c_005d_005e_005f_0060_007c_007e.html#g_t_0021_005f_0022_0023_0024_0025_0026_0027_0028_0029_002a_002b_002d_002e_002f_003b_003c_003d_003e_003f_005b_005c_005d_005e_005f_0060_007c_007e">&bull;
 !_&quot;#$%&amp;'()*+-./;&lt;=&gt;?[\]^_`|~</a></td><td>&nbsp;&nbsp;</td><td 
align="left" valign="top">
+<tr><td align="left" valign="top"><a 
href="_0021_005f_0022_0023_0024_0025_0026_0027_0028_0029_002a_002b_002d_002e_002f_003b_003c_003d_003e_003f_005b_005c_005d_005e_005f_0060_007c_007e.html#g_t_0021_005f_0022_0023_0024_0025_0026_0027_0028_0029_002a_002b_002d_002e_002f_003b_003c_003d_003e_003f_005b_005c_005d_005e_005f_0060_007c_007e">&bull;
 
!_&quot;#$%&amp;&rsquo;()*+-./;&lt;=&gt;?[\]^_&lsquo;|~</a></td><td>&nbsp;&nbsp;</td><td
 align="left" valign="top">
 </td></tr>
 <tr><td align="left" valign="top"><a href="local-node.html#local-node">&bull; 
local node</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">
 </td></tr>

Index: Tests/htmlxref-only_mono_res/test_refs.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/htmlxref-only_mono_res/test_refs.html,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -b -r1.2 -r1.3
--- Tests/htmlxref-only_mono_res/test_refs.html 5 Feb 2007 15:30:23 -0000       
1.2
+++ Tests/htmlxref-only_mono_res/test_refs.html 3 Oct 2007 09:34:39 -0000       
1.3
@@ -86,7 +86,7 @@
 <a name="SEC3"></a>
 <h3 class="subheading"> Testing local nodes </h3>
 
-<p><tt>!_&quot;#$%&amp;'()*+-./;&lt;=&gt;?[\]^_`|~</tt> <a 
href="_0021_005f_0022_0023_0024_0025_0026_0027_0028_0029_002a_002b_002d_002e_002f_003b_003c_003d_003e_003f_005b_005c_005d_005e_005f_0060_007c_007e.html#g_t_0021_005f_0022_0023_0024_0025_0026_0027_0028_0029_002a_002b_002d_002e_002f_003b_003c_003d_003e_003f_005b_005c_005d_005e_005f_0060_007c_007e">!_&quot;#$%&amp;'()*+-./;&lt;=&gt;?[\]^_`|~</a><br>
+<p><tt>!_&quot;#$%&amp;'()*+-./;&lt;=&gt;?[\]^_`|~</tt> <a 
href="_0021_005f_0022_0023_0024_0025_0026_0027_0028_0029_002a_002b_002d_002e_002f_003b_003c_003d_003e_003f_005b_005c_005d_005e_005f_0060_007c_007e.html#g_t_0021_005f_0022_0023_0024_0025_0026_0027_0028_0029_002a_002b_002d_002e_002f_003b_003c_003d_003e_003f_005b_005c_005d_005e_005f_0060_007c_007e">!_&quot;#$%&amp;&rsquo;()*+-./;&lt;=&gt;?[\]^_&lsquo;|~</a><br>
 </p><table><tr><td>&nbsp;</td><td><pre class="example">target: 
#_0021_005f_0022_0023_0024_0025_0026_0027_0028_0029_002a_002b_002d_002e_002f_003b_003c_003d_003e_003f_005b_005c_005d_005e_005f_0060_007c_007e
 </pre></td></tr></table>
 

Index: 
Tests/htmlxref-only_split_res/_0021_005f_0022_0023_0024_0025_0026_0027_0028_0029_002a_002b_002d_002e_002f_003b_003c_003d_003e_003f_005b_005c_005d_005e_005f_0060_007c_007e.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/htmlxref-only_split_res/_0021_005f_0022_0023_0024_0025_0026_0027_0028_0029_002a_002b_002d_002e_002f_003b_003c_003d_003e_003f_005b_005c_005d_005e_005f_0060_007c_007e.html,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -b -r1.2 -r1.3
--- 
Tests/htmlxref-only_split_res/_0021_005f_0022_0023_0024_0025_0026_0027_0028_0029_002a_002b_002d_002e_002f_003b_003c_003d_003e_003f_005b_005c_005d_005e_005f_0060_007c_007e.html
     5 Feb 2007 15:30:23 -0000       1.2
+++ 
Tests/htmlxref-only_split_res/_0021_005f_0022_0023_0024_0025_0026_0027_0028_0029_002a_002b_002d_002e_002f_003b_003c_003d_003e_003f_005b_005c_005d_005e_005f_0060_007c_007e.html
     3 Oct 2007 09:34:40 -0000       1.3
@@ -59,7 +59,7 @@
 <td valign="middle" align="left">[<a href="test_refs_abt.html#SEC_About" 
title="About (help)"> ? </a>]</td>
 </tr></table>
 <hr size="1">
-<h3 class="node"> !_&quot;#$%&amp;'()*+-./;&lt;=&gt;?[\]^_`|~ </h3>
+<h3 class="node"> !_&quot;#$%&amp;&rsquo;()*+-./;&lt;=&gt;?[\]^_&lsquo;|~ </h3>
 <table><tr><td>&nbsp;</td><td><pre class="example">id: 
_0021_005f_0022_0023_0024_0025_0026_0027_0028_0029_002a_002b_002d_002e_002f_003b_003c_003d_003e_003f_005b_005c_005d_005e_005f_0060_007c_007e
 </pre></td></tr></table>
 

Index: Tests/htmlxref-only_split_res/no_split_test_refs.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/htmlxref-only_split_res/no_split_test_refs.html,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -b -r1.3 -r1.4
--- Tests/htmlxref-only_split_res/no_split_test_refs.html       6 May 2007 
12:57:06 -0000       1.3
+++ Tests/htmlxref-only_split_res/no_split_test_refs.html       3 Oct 2007 
09:34:40 -0000       1.4
@@ -85,7 +85,7 @@
 <a name="SEC3"></a>
 <h3 class="subheading"> Testing local nodes </h3>
 
-<p><tt>!_&quot;#$%&amp;'()*+-./;&lt;=&gt;?[\]^_`|~</tt> <a 
href="#g_t_0021_005f_0022_0023_0024_0025_0026_0027_0028_0029_002a_002b_002d_002e_002f_003b_003c_003d_003e_003f_005b_005c_005d_005e_005f_0060_007c_007e">!_&quot;#$%&amp;'()*+-./;&lt;=&gt;?[\]^_`|~</a><br>
+<p><tt>!_&quot;#$%&amp;'()*+-./;&lt;=&gt;?[\]^_`|~</tt> <a 
href="#g_t_0021_005f_0022_0023_0024_0025_0026_0027_0028_0029_002a_002b_002d_002e_002f_003b_003c_003d_003e_003f_005b_005c_005d_005e_005f_0060_007c_007e">!_&quot;#$%&amp;&rsquo;()*+-./;&lt;=&gt;?[\]^_&lsquo;|~</a><br>
 </p><table><tr><td>&nbsp;</td><td><pre class="example">target: 
#_0021_005f_0022_0023_0024_0025_0026_0027_0028_0029_002a_002b_002d_002e_002f_003b_003c_003d_003e_003f_005b_005c_005d_005e_005f_0060_007c_007e
 </pre></td></tr></table>
 
@@ -126,7 +126,7 @@
 </pre></td></tr></table>
 
 <table class="menu" border="0" cellspacing="0">
-<tr><td align="left" valign="top"><a 
href="#g_t_0021_005f_0022_0023_0024_0025_0026_0027_0028_0029_002a_002b_002d_002e_002f_003b_003c_003d_003e_003f_005b_005c_005d_005e_005f_0060_007c_007e">&bull;
 !_&quot;#$%&amp;'()*+-./;&lt;=&gt;?[\]^_`|~</a></td><td>&nbsp;&nbsp;</td><td 
align="left" valign="top">
+<tr><td align="left" valign="top"><a 
href="#g_t_0021_005f_0022_0023_0024_0025_0026_0027_0028_0029_002a_002b_002d_002e_002f_003b_003c_003d_003e_003f_005b_005c_005d_005e_005f_0060_007c_007e">&bull;
 
!_&quot;#$%&amp;&rsquo;()*+-./;&lt;=&gt;?[\]^_&lsquo;|~</a></td><td>&nbsp;&nbsp;</td><td
 align="left" valign="top">
 </td></tr>
 <tr><td align="left" valign="top"><a href="#local-node">&bull; local 
node</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">
 </td></tr>

Index: Tests/htmlxref-only_split_res/other-nodes.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/htmlxref-only_split_res/other-nodes.html,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -b -r1.2 -r1.3
--- Tests/htmlxref-only_split_res/other-nodes.html      5 Feb 2007 15:30:23 
-0000       1.2
+++ Tests/htmlxref-only_split_res/other-nodes.html      3 Oct 2007 09:34:40 
-0000       1.3
@@ -70,7 +70,7 @@
 </pre></td></tr></table>
 
 <table class="menu" border="0" cellspacing="0">
-<tr><td align="left" valign="top"><a 
href="_0021_005f_0022_0023_0024_0025_0026_0027_0028_0029_002a_002b_002d_002e_002f_003b_003c_003d_003e_003f_005b_005c_005d_005e_005f_0060_007c_007e.html#g_t_0021_005f_0022_0023_0024_0025_0026_0027_0028_0029_002a_002b_002d_002e_002f_003b_003c_003d_003e_003f_005b_005c_005d_005e_005f_0060_007c_007e">&bull;
 !_&quot;#$%&amp;'()*+-./;&lt;=&gt;?[\]^_`|~</a></td><td>&nbsp;&nbsp;</td><td 
align="left" valign="top">
+<tr><td align="left" valign="top"><a 
href="_0021_005f_0022_0023_0024_0025_0026_0027_0028_0029_002a_002b_002d_002e_002f_003b_003c_003d_003e_003f_005b_005c_005d_005e_005f_0060_007c_007e.html#g_t_0021_005f_0022_0023_0024_0025_0026_0027_0028_0029_002a_002b_002d_002e_002f_003b_003c_003d_003e_003f_005b_005c_005d_005e_005f_0060_007c_007e">&bull;
 
!_&quot;#$%&amp;&rsquo;()*+-./;&lt;=&gt;?[\]^_&lsquo;|~</a></td><td>&nbsp;&nbsp;</td><td
 align="left" valign="top">
 </td></tr>
 <tr><td align="left" valign="top"><a href="local-node.html#local-node">&bull; 
local node</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">
 </td></tr>

Index: Tests/htmlxref-only_split_res/test_refs.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/htmlxref-only_split_res/test_refs.html,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -b -r1.2 -r1.3
--- Tests/htmlxref-only_split_res/test_refs.html        5 Feb 2007 15:30:23 
-0000       1.2
+++ Tests/htmlxref-only_split_res/test_refs.html        3 Oct 2007 09:34:40 
-0000       1.3
@@ -86,7 +86,7 @@
 <a name="SEC3"></a>
 <h3 class="subheading"> Testing local nodes </h3>
 
-<p><tt>!_&quot;#$%&amp;'()*+-./;&lt;=&gt;?[\]^_`|~</tt> <a 
href="_0021_005f_0022_0023_0024_0025_0026_0027_0028_0029_002a_002b_002d_002e_002f_003b_003c_003d_003e_003f_005b_005c_005d_005e_005f_0060_007c_007e.html#g_t_0021_005f_0022_0023_0024_0025_0026_0027_0028_0029_002a_002b_002d_002e_002f_003b_003c_003d_003e_003f_005b_005c_005d_005e_005f_0060_007c_007e">!_&quot;#$%&amp;'()*+-./;&lt;=&gt;?[\]^_`|~</a><br>
+<p><tt>!_&quot;#$%&amp;'()*+-./;&lt;=&gt;?[\]^_`|~</tt> <a 
href="_0021_005f_0022_0023_0024_0025_0026_0027_0028_0029_002a_002b_002d_002e_002f_003b_003c_003d_003e_003f_005b_005c_005d_005e_005f_0060_007c_007e.html#g_t_0021_005f_0022_0023_0024_0025_0026_0027_0028_0029_002a_002b_002d_002e_002f_003b_003c_003d_003e_003f_005b_005c_005d_005e_005f_0060_007c_007e">!_&quot;#$%&amp;&rsquo;()*+-./;&lt;=&gt;?[\]^_&lsquo;|~</a><br>
 </p><table><tr><td>&nbsp;</td><td><pre class="example">target: 
#_0021_005f_0022_0023_0024_0025_0026_0027_0028_0029_002a_002b_002d_002e_002f_003b_003c_003d_003e_003f_005b_005c_005d_005e_005f_0060_007c_007e
 </pre></td></tr></table>
 

Index: 
Tests/htmlxref_res/_0021_005f_0022_0023_0024_0025_0026_0027_0028_0029_002a_002b_002d_002e_002f_003b_003c_003d_003e_003f_005b_005c_005d_005e_005f_0060_007c_007e.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/htmlxref_res/_0021_005f_0022_0023_0024_0025_0026_0027_0028_0029_002a_002b_002d_002e_002f_003b_003c_003d_003e_003f_005b_005c_005d_005e_005f_0060_007c_007e.html,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -b -r1.2 -r1.3
--- 
Tests/htmlxref_res/_0021_005f_0022_0023_0024_0025_0026_0027_0028_0029_002a_002b_002d_002e_002f_003b_003c_003d_003e_003f_005b_005c_005d_005e_005f_0060_007c_007e.html
        5 Feb 2007 15:30:23 -0000       1.2
+++ 
Tests/htmlxref_res/_0021_005f_0022_0023_0024_0025_0026_0027_0028_0029_002a_002b_002d_002e_002f_003b_003c_003d_003e_003f_005b_005c_005d_005e_005f_0060_007c_007e.html
        3 Oct 2007 09:34:40 -0000       1.3
@@ -59,7 +59,7 @@
 <td valign="middle" align="left">[<a href="test_refs_abt.html#SEC_About" 
title="About (help)"> ? </a>]</td>
 </tr></table>
 <hr size="1">
-<h3 class="node"> !_&quot;#$%&amp;'()*+-./;&lt;=&gt;?[\]^_`|~ </h3>
+<h3 class="node"> !_&quot;#$%&amp;&rsquo;()*+-./;&lt;=&gt;?[\]^_&lsquo;|~ </h3>
 <table><tr><td>&nbsp;</td><td><pre class="example">id: 
_0021_005f_0022_0023_0024_0025_0026_0027_0028_0029_002a_002b_002d_002e_002f_003b_003c_003d_003e_003f_005b_005c_005d_005e_005f_0060_007c_007e
 </pre></td></tr></table>
 

Index: Tests/htmlxref_res/no_split_test_refs.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/htmlxref_res/no_split_test_refs.html,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -b -r1.4 -r1.5
--- Tests/htmlxref_res/no_split_test_refs.html  6 May 2007 12:57:06 -0000       
1.4
+++ Tests/htmlxref_res/no_split_test_refs.html  3 Oct 2007 09:34:40 -0000       
1.5
@@ -85,7 +85,7 @@
 <a name="SEC3"></a>
 <h3 class="subheading"> Testing local nodes </h3>
 
-<p><tt>!_&quot;#$%&amp;'()*+-./;&lt;=&gt;?[\]^_`|~</tt> <a 
href="#g_t_0021_005f_0022_0023_0024_0025_0026_0027_0028_0029_002a_002b_002d_002e_002f_003b_003c_003d_003e_003f_005b_005c_005d_005e_005f_0060_007c_007e">!_&quot;#$%&amp;'()*+-./;&lt;=&gt;?[\]^_`|~</a><br>
+<p><tt>!_&quot;#$%&amp;'()*+-./;&lt;=&gt;?[\]^_`|~</tt> <a 
href="#g_t_0021_005f_0022_0023_0024_0025_0026_0027_0028_0029_002a_002b_002d_002e_002f_003b_003c_003d_003e_003f_005b_005c_005d_005e_005f_0060_007c_007e">!_&quot;#$%&amp;&rsquo;()*+-./;&lt;=&gt;?[\]^_&lsquo;|~</a><br>
 </p><table><tr><td>&nbsp;</td><td><pre class="example">target: 
#_0021_005f_0022_0023_0024_0025_0026_0027_0028_0029_002a_002b_002d_002e_002f_003b_003c_003d_003e_003f_005b_005c_005d_005e_005f_0060_007c_007e
 </pre></td></tr></table>
 
@@ -126,7 +126,7 @@
 </pre></td></tr></table>
 
 <table class="menu" border="0" cellspacing="0">
-<tr><td align="left" valign="top"><a 
href="#g_t_0021_005f_0022_0023_0024_0025_0026_0027_0028_0029_002a_002b_002d_002e_002f_003b_003c_003d_003e_003f_005b_005c_005d_005e_005f_0060_007c_007e">&bull;
 !_&quot;#$%&amp;'()*+-./;&lt;=&gt;?[\]^_`|~</a></td><td>&nbsp;&nbsp;</td><td 
align="left" valign="top">
+<tr><td align="left" valign="top"><a 
href="#g_t_0021_005f_0022_0023_0024_0025_0026_0027_0028_0029_002a_002b_002d_002e_002f_003b_003c_003d_003e_003f_005b_005c_005d_005e_005f_0060_007c_007e">&bull;
 
!_&quot;#$%&amp;&rsquo;()*+-./;&lt;=&gt;?[\]^_&lsquo;|~</a></td><td>&nbsp;&nbsp;</td><td
 align="left" valign="top">
 </td></tr>
 <tr><td align="left" valign="top"><a href="#local-node">&bull; local 
node</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">
 </td></tr>

Index: Tests/htmlxref_res/other-nodes.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/htmlxref_res/other-nodes.html,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -b -r1.2 -r1.3
--- Tests/htmlxref_res/other-nodes.html 5 Feb 2007 15:30:23 -0000       1.2
+++ Tests/htmlxref_res/other-nodes.html 3 Oct 2007 09:34:40 -0000       1.3
@@ -70,7 +70,7 @@
 </pre></td></tr></table>
 
 <table class="menu" border="0" cellspacing="0">
-<tr><td align="left" valign="top"><a 
href="_0021_005f_0022_0023_0024_0025_0026_0027_0028_0029_002a_002b_002d_002e_002f_003b_003c_003d_003e_003f_005b_005c_005d_005e_005f_0060_007c_007e.html#g_t_0021_005f_0022_0023_0024_0025_0026_0027_0028_0029_002a_002b_002d_002e_002f_003b_003c_003d_003e_003f_005b_005c_005d_005e_005f_0060_007c_007e">&bull;
 !_&quot;#$%&amp;'()*+-./;&lt;=&gt;?[\]^_`|~</a></td><td>&nbsp;&nbsp;</td><td 
align="left" valign="top">
+<tr><td align="left" valign="top"><a 
href="_0021_005f_0022_0023_0024_0025_0026_0027_0028_0029_002a_002b_002d_002e_002f_003b_003c_003d_003e_003f_005b_005c_005d_005e_005f_0060_007c_007e.html#g_t_0021_005f_0022_0023_0024_0025_0026_0027_0028_0029_002a_002b_002d_002e_002f_003b_003c_003d_003e_003f_005b_005c_005d_005e_005f_0060_007c_007e">&bull;
 
!_&quot;#$%&amp;&rsquo;()*+-./;&lt;=&gt;?[\]^_&lsquo;|~</a></td><td>&nbsp;&nbsp;</td><td
 align="left" valign="top">
 </td></tr>
 <tr><td align="left" valign="top"><a href="local-node.html#local-node">&bull; 
local node</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">
 </td></tr>

Index: Tests/htmlxref_res/test_refs.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/htmlxref_res/test_refs.html,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -b -r1.2 -r1.3
--- Tests/htmlxref_res/test_refs.html   5 Feb 2007 15:30:23 -0000       1.2
+++ Tests/htmlxref_res/test_refs.html   3 Oct 2007 09:34:40 -0000       1.3
@@ -86,7 +86,7 @@
 <a name="SEC3"></a>
 <h3 class="subheading"> Testing local nodes </h3>
 
-<p><tt>!_&quot;#$%&amp;'()*+-./;&lt;=&gt;?[\]^_`|~</tt> <a 
href="_0021_005f_0022_0023_0024_0025_0026_0027_0028_0029_002a_002b_002d_002e_002f_003b_003c_003d_003e_003f_005b_005c_005d_005e_005f_0060_007c_007e.html#g_t_0021_005f_0022_0023_0024_0025_0026_0027_0028_0029_002a_002b_002d_002e_002f_003b_003c_003d_003e_003f_005b_005c_005d_005e_005f_0060_007c_007e">!_&quot;#$%&amp;'()*+-./;&lt;=&gt;?[\]^_`|~</a><br>
+<p><tt>!_&quot;#$%&amp;'()*+-./;&lt;=&gt;?[\]^_`|~</tt> <a 
href="_0021_005f_0022_0023_0024_0025_0026_0027_0028_0029_002a_002b_002d_002e_002f_003b_003c_003d_003e_003f_005b_005c_005d_005e_005f_0060_007c_007e.html#g_t_0021_005f_0022_0023_0024_0025_0026_0027_0028_0029_002a_002b_002d_002e_002f_003b_003c_003d_003e_003f_005b_005c_005d_005e_005f_0060_007c_007e">!_&quot;#$%&amp;&rsquo;()*+-./;&lt;=&gt;?[\]^_&lsquo;|~</a><br>
 </p><table><tr><td>&nbsp;</td><td><pre class="example">target: 
#_0021_005f_0022_0023_0024_0025_0026_0027_0028_0029_002a_002b_002d_002e_002f_003b_003c_003d_003e_003f_005b_005c_005d_005e_005f_0060_007c_007e
 </pre></td></tr></table>
 

Index: Tests/macros_res/bib-example.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/macros_res/bib-example.html,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -b -r1.5 -r1.6
--- Tests/macros_res/bib-example.html   6 May 2007 12:57:07 -0000       1.5
+++ Tests/macros_res/bib-example.html   3 Oct 2007 09:34:40 -0000       1.6
@@ -82,7 +82,7 @@
 
 <p>The ability of a documentation format to make cross references to a
 bibliography, a feature of LaTeX (See item [LaTeX2e] in <a 
href="#SEC2">LaTeX2e</a>.)
-, isn't
+, isn&rsquo;t
 currently supported in Texinfo.
 </p>
 <hr size="6">
@@ -109,7 +109,7 @@
 <ul class="toc">
 <li>
 <a name="LaTeX2e"></a>[LaTeX2e]
- Leslie Lamport, LaTeX User's Guide and
+ Leslie Lamport, LaTeX User&rsquo;s Guide and
 Reference Manual, 2nd edition, Addison-Wesley, Reading,
 Massachusetts, 1994.
 

Index: Tests/macros_res/macros.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/macros_res/macros.html,v
retrieving revision 1.29
retrieving revision 1.30
diff -u -b -r1.29 -r1.30
--- Tests/macros_res/macros.html        6 May 2007 12:57:07 -0000       1.29
+++ Tests/macros_res/macros.html        3 Oct 2007 09:34:40 -0000       1.30
@@ -81,7 +81,7 @@
 
 <p>     a lone @ at the end     &nbsp;     of the line
 </p>
-<p>     now a bad accent    `
+<p>     now a bad accent    &lsquo;
  at the end of line
 </p>
 <p>The file included:

Index: Tests/macros_res/simple_macro.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/macros_res/simple_macro.html,v
retrieving revision 1.30
retrieving revision 1.31
diff -u -b -r1.30 -r1.31
--- Tests/macros_res/simple_macro.html  6 May 2007 12:57:07 -0000       1.30
+++ Tests/macros_res/simple_macro.html  3 Oct 2007 09:34:40 -0000       1.31
@@ -220,7 +220,7 @@
 </p>
 
<p>&mdash;&mdash;&mdash;&mdash;&mdash;&mdash;&mdash;&mdash;&mdash;&mdash;&mdash;&mdash;&mdash;
 </p>
-<p>makeinfo result (the comma don't separate args ; the value is expanded after
+<p>makeinfo result (the comma don&rsquo;t separate args ; the value is 
expanded after
 arguments parsing):
 </p>
 <p>result: <em>arg1 , arg2 </em> protected \ -&gt; \arg1\ <em></em>
@@ -245,8 +245,8 @@
 </p>
 
<p>&mdash;&mdash;&mdash;&mdash;&mdash;&mdash;&mdash;&mdash;&mdash;&mdash;&mdash;-
 </p>
-<p>makeinfo result (according to error message, the value isn't expanded
-when the body is expanded; it is kept, but the second \ isn't):
+<p>makeinfo result (according to error message, the value isn&rsquo;t expanded
+when the body is expanded; it is kept, but the second \ isn&rsquo;t):
 </p>
 <p>result: <em>\\arg\  </em>
 </p>

Index: Tests/node_translit_no_unicode_res/a.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/node_translit_no_unicode_res/a.html,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -b -r1.6 -r1.7
--- Tests/node_translit_no_unicode_res/a.html   21 Aug 2007 17:02:08 -0000      
1.6
+++ Tests/node_translit_no_unicode_res/a.html   3 Oct 2007 09:34:40 -0000       
1.7
@@ -83,7 +83,7 @@
 </tr></table>
 <hr size="1">
 <h2 class="section"> 2.1 &aacute; </h2>
-<p>With brace &aacute;. Testing ' &quot; ` ^.
+<p>With brace &aacute;. Testing &rsquo; &quot; &lsquo; ^.
 </p><hr size="1">
 <a name="g_t_00e0"></a>
 <a name="SEC30"></a>

Index: Tests/node_translit_no_unidecode_res/a.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/node_translit_no_unidecode_res/a.html,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -b -r1.6 -r1.7
--- Tests/node_translit_no_unidecode_res/a.html 21 Aug 2007 17:02:09 -0000      
1.6
+++ Tests/node_translit_no_unidecode_res/a.html 3 Oct 2007 09:34:41 -0000       
1.7
@@ -83,7 +83,7 @@
 </tr></table>
 <hr size="1">
 <h2 class="section"> 2.1 &aacute; </h2>
-<p>With brace &aacute;. Testing ' &quot; ` ^.
+<p>With brace &aacute;. Testing &rsquo; &quot; &lsquo; ^.
 </p><hr size="1">
 <a name="g_t_00e0"></a>
 <a name="SEC30"></a>

Index: Tests/node_translit_res/a.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/node_translit_res/a.html,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -b -r1.6 -r1.7
--- Tests/node_translit_res/a.html      21 Aug 2007 17:02:10 -0000      1.6
+++ Tests/node_translit_res/a.html      3 Oct 2007 09:34:41 -0000       1.7
@@ -83,7 +83,7 @@
 </tr></table>
 <hr size="1">
 <h2 class="section"> 2.1 &aacute; </h2>
-<p>With brace &aacute;. Testing ' &quot; ` ^.
+<p>With brace &aacute;. Testing &rsquo; &quot; &lsquo; ^.
 </p><hr size="1">
 <a name="g_t_00e0"></a>
 <a name="SEC30"></a>

Index: Tests/node_utf8_translit_no_unidecode_res/a.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/node_utf8_translit_no_unidecode_res/a.html,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -b -r1.4 -r1.5
--- Tests/node_utf8_translit_no_unidecode_res/a.html    5 Aug 2006 09:24:45 
-0000       1.4
+++ Tests/node_utf8_translit_no_unidecode_res/a.html    3 Oct 2007 09:34:41 
-0000       1.5
@@ -83,7 +83,7 @@
 </tr></table>
 <hr size="1">
 <h2 class="section"> 2.1 &aacute; </h2>
-<p>With brace &aacute;. Testing ' &quot; ` ^.
+<p>With brace &aacute;. Testing &rsquo; &quot; &lsquo; ^.
 </p><hr size="1">
 <a name="g_t_00e0"></a>
 <a name="SEC28"></a>

Index: Tests/node_utf8_translit_res/a.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/node_utf8_translit_res/a.html,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -b -r1.4 -r1.5
--- Tests/node_utf8_translit_res/a.html 5 Aug 2006 09:24:45 -0000       1.4
+++ Tests/node_utf8_translit_res/a.html 3 Oct 2007 09:34:41 -0000       1.5
@@ -83,7 +83,7 @@
 </tr></table>
 <hr size="1">
 <h2 class="section"> 2.1 &aacute; </h2>
-<p>With brace &aacute;. Testing ' &quot; ` ^.
+<p>With brace &aacute;. Testing &rsquo; &quot; &lsquo; ^.
 </p><hr size="1">
 <a name="g_t_00e0"></a>
 <a name="SEC28"></a>

Index: Tests/nodes_texinfo_res/A4-Paper.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/A4-Paper.html,v
retrieving revision 1.18
retrieving revision 1.19
diff -u -b -r1.18 -r1.19
--- Tests/nodes_texinfo_res/A4-Paper.html       5 Feb 2007 15:30:24 -0000       
1.18
+++ Tests/nodes_texinfo_res/A4-Paper.html       3 Oct 2007 09:34:41 -0000       
1.19
@@ -101,7 +101,7 @@
 <a name="IDX350"></a>
 <a name="IDX351"></a>
 <p>You may or may not prefer the formatting that results from the command
-<code>@afourlatex</code>.  There's also <code>@afourwide</code> for A4 paper in
+<code>@afourlatex</code>.  There&rsquo;s also <code>@afourwide</code> for A4 
paper in
 wide format.
 </p>
 <hr size="1">

Index: Tests/nodes_texinfo_res/Abstract-Objects.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/Abstract-Objects.html,v
retrieving revision 1.25
retrieving revision 1.26
diff -u -b -r1.25 -r1.26
--- Tests/nodes_texinfo_res/Abstract-Objects.html       5 Feb 2007 15:30:24 
-0000       1.25
+++ Tests/nodes_texinfo_res/Abstract-Objects.html       3 Oct 2007 09:34:41 
-0000       1.26
@@ -185,8 +185,8 @@
 @end defop
 </pre></td></tr></table>
 
-<p><code>@defop</code> creates an entry, such as `<code>expose</code> on
-<code>windows</code>', in the index of functions.
+<p><code>@defop</code> creates an entry, such as &lsquo;<code>expose</code> on
+<code>windows</code>&rsquo;, in the index of functions.
 </p>
 <a name="IDX282"></a>
 </dd>
@@ -226,8 +226,8 @@
 @end defmethod
 </pre></td></tr></table>
 
-<p><code>@defmethod</code> creates an entry, such as `<code>bar-method</code> 
on
-<code>bar-class</code>', in the index of functions.
+<p><code>@defmethod</code> creates an entry, such as 
&lsquo;<code>bar-method</code> on
+<code>bar-class</code>&rsquo;, in the index of functions.
 </p>
 
 </dd>

Index: Tests/nodes_texinfo_res/Batch-Formatting.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/Batch-Formatting.html,v
retrieving revision 1.21
retrieving revision 1.22
diff -u -b -r1.21 -r1.22
--- Tests/nodes_texinfo_res/Batch-Formatting.html       5 Feb 2007 15:30:24 
-0000       1.21
+++ Tests/nodes_texinfo_res/Batch-Formatting.html       3 Oct 2007 09:34:41 
-0000       1.22
@@ -83,7 +83,7 @@
 
 <p>You can format Texinfo files for Info using 
<code>batch-texinfo-format</code>
 and Emacs Batch mode.  You can run Emacs in Batch mode from any shell,
-including a shell inside of Emacs.  (See <a 
href="../emacs/Command-Switches.html#Command-Switches">(emacs)Command 
Switches</a> section `Command Line Switches and Arguments' in <cite>The GNU 
Emacs Manual</cite>.)
+including a shell inside of Emacs.  (See <a 
href="../emacs/Command-Switches.html#Command-Switches">(emacs)Command 
Switches</a> section &lsquo;Command Line Switches and Arguments&rsquo; in 
<cite>The GNU Emacs Manual</cite>.)
 </p>
 <p>Here is a shell command to format all the files that end in
 &lsquo;<tt>.texinfo</tt>&rsquo; in the current directory:

Index: Tests/nodes_texinfo_res/Beginning-a-File.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/Beginning-a-File.html,v
retrieving revision 1.19
retrieving revision 1.20
diff -u -b -r1.19 -r1.20
--- Tests/nodes_texinfo_res/Beginning-a-File.html       5 Feb 2007 15:30:24 
-0000       1.19
+++ Tests/nodes_texinfo_res/Beginning-a-File.html       3 Oct 2007 09:34:41 
-0000       1.20
@@ -97,7 +97,7 @@
 </td></tr>
 <tr><td align="left" valign="top"><a 
href="Titlepage-_0026-Copyright-Page.html#SEC52">3.4 Title and Copyright 
Pages</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">  Creating the 
title and copyright pages.
 </td></tr>
-<tr><td align="left" valign="top"><a href="The-Top-Node.html#SEC59">3.5 The 
`Top' Node and Master Menu</a></td><td>&nbsp;&nbsp;</td><td align="left" 
valign="top">                Creating the `Top' node and master menu.
+<tr><td align="left" valign="top"><a href="The-Top-Node.html#SEC59">3.5 The 
&lsquo;Top&rsquo; Node and Master Menu</a></td><td>&nbsp;&nbsp;</td><td 
align="left" valign="top">                Creating the &lsquo;Top&rsquo; node 
and master menu.
 </td></tr>
 <tr><td align="left" valign="top"><a 
href="Global-Document-Commands.html#SEC62">3.6 Global Document 
Commands</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">    
Affecting formatting throughout.
 </td></tr>

Index: Tests/nodes_texinfo_res/Breaks.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/Breaks.html,v
retrieving revision 1.24
retrieving revision 1.25
diff -u -b -r1.24 -r1.25
--- Tests/nodes_texinfo_res/Breaks.html 5 Feb 2007 15:30:24 -0000       1.24
+++ Tests/nodes_texinfo_res/Breaks.html 3 Oct 2007 09:34:41 -0000       1.25
@@ -83,7 +83,7 @@
 
 <p>Usually, a Texinfo file is processed both by TeX and by one of the
 Info formatting commands.  Line, paragraph, or page breaks sometimes
-occur in the `wrong' place in one or other form of output.  You must
+occur in the &lsquo;wrong&rsquo; place in one or other form of output.  You 
must
 ensure that text looks right both in the printed manual and in the
 Info file.
 </p>

Index: Tests/nodes_texinfo_res/Combining-Indices.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/Combining-Indices.html,v
retrieving revision 1.19
retrieving revision 1.20
diff -u -b -r1.19 -r1.20
--- Tests/nodes_texinfo_res/Combining-Indices.html      5 Feb 2007 15:30:24 
-0000       1.19
+++ Tests/nodes_texinfo_res/Combining-Indices.html      3 Oct 2007 09:34:41 
-0000       1.20
@@ -88,8 +88,8 @@
 <p>You could put functions into the concept index by writing
 <code>@cindex</code> commands for them instead of <code>@findex</code> 
commands,
 and produce a consistent manual by printing the concept index with the
-title `Function and Concept Index' and not printing the `Function
-Index' at all; but this is not a robust procedure.  It works only if
+title &lsquo;Function and Concept Index&rsquo; and not printing the 
&lsquo;Function
+Index&rsquo; at all; but this is not a robust procedure.  It works only if
 your document is never included as part of another
 document that is designed to have a separate function index; if your
 document were to be included with such a document, the functions from

Index: Tests/nodes_texinfo_res/Command-List.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/Command-List.html,v
retrieving revision 1.26
retrieving revision 1.27
diff -u -b -r1.26 -r1.27
--- Tests/nodes_texinfo_res/Command-List.html   30 Sep 2007 12:47:37 -0000      
1.26
+++ Tests/nodes_texinfo_res/Command-List.html   3 Oct 2007 09:34:42 -0000       
1.27
@@ -179,7 +179,7 @@
 </dd>
 <dt> <code>@acronym{<var>abbrev</var>}</code></dt>
 <dd><p>Tag <var>abbrev</var> as an acronym, that is, an abbreviation written 
in all
-capital letters, such as `NASA'.  See section <a 
href="acronym.html#SEC134"><code>acronym</code></a>.
+capital letters, such as &lsquo;NASA&rsquo;.  See section <a 
href="acronym.html#SEC134"><code>acronym</code></a>.
 </p>
 </dd>
 <dt> <code>@AE{}</code></dt>
@@ -231,12 +231,12 @@
 <dt> <code>@appendixsubsubsec <var>title</var></code></dt>
 <dd><p>Begin an appendix subsubsection within an appendix subsection.  The
 title appears in the table of contents of a printed manual.  In Info,
-the title is underlined with periods.  See section <a 
href="subsubsection.html#SEC83">The `subsub' Commands</a>.
+the title is underlined with periods.  See section <a 
href="subsubsection.html#SEC83">The &lsquo;subsub&rsquo; Commands</a>.
 </p>
 </dd>
 <dt> <code>@asis</code></dt>
 <dd><p>Used following <code>@table</code>, <code>@ftable</code>, and 
<code>@vtable</code> to
-print the table's first column without highlighting (&ldquo;as is&rdquo;).
+print the table&rsquo;s first column without highlighting (&ldquo;as 
is&rdquo;).
 See section <a href="Two_002dcolumn-Tables.html#SEC159">Making a Two-column 
Table</a>.
 </p>
 </dd>
@@ -502,7 +502,7 @@
 </p>
 </dd>
 <dt> <code>@dircategory <var>dirpart</var></code></dt>
-<dd><p>Specify a part of the Info directory menu where this file's entry should
+<dd><p>Specify a part of the Info directory menu where this file&rsquo;s entry 
should
 go.  See section <a href="Installing-Dir-Entries.html#SEC275">Installing Info 
Directory Files</a>.
 </p>
 </dd>
@@ -647,12 +647,12 @@
 </dd>
 <dt> <code>@footnote{<var>text-of-footnote</var>}</code></dt>
 <dd><p>Enter a footnote.  Footnote text is printed at the bottom of the page
-by TeX; Info may format in either `End' node or `Separate' node style.
+by TeX; Info may format in either &lsquo;End&rsquo; node or 
&lsquo;Separate&rsquo; node style.
 See section <a href="Footnotes.html#SEC201">Footnotes</a>.
 </p>
 </dd>
 <dt> <code>@footnotestyle <var>style</var></code></dt>
-<dd><p>Specify an Info file's footnote style, either 
&lsquo;<samp>end</samp>&rsquo; for the end
+<dd><p>Specify an Info file&rsquo;s footnote style, either 
&lsquo;<samp>end</samp>&rsquo; for the end
 node style or &lsquo;<samp>separate</samp>&rsquo; for the separate node style.
 See section <a href="Footnotes.html#SEC201">Footnotes</a>.
 </p>
@@ -857,7 +857,7 @@
 </p>
 </dd>
 <dt> <code>@minus{}</code></dt>
-<dd><p>Generate a minus sign, `-'.  See section <a 
href="minus.html#SEC191"><code>@minus</code></a>.
+<dd><p>Generate a minus sign, &lsquo;-&rsquo;.  See section <a 
href="minus.html#SEC191"><code>@minus</code></a>.
 </p>
 </dd>
 <dt> <code>@multitable <var>column-width-spec</var></code></dt>
@@ -948,7 +948,7 @@
 </p>
 </dd>
 <dt> <code>@pxref{<var>node-name</var>, [<var>entry</var>], 
[<var>topic-or-title</var>], [<var>info-file</var>], 
[<var>manual</var>]}</code></dt>
-<dd><p>Make a reference that starts with a lower case `see' in a printed
+<dd><p>Make a reference that starts with a lower case &lsquo;see&rsquo; in a 
printed
 manual.  Use within parentheses only.  Do not follow command with a
 punctuation mark&mdash;the Info formatting commands automatically insert
 terminating punctuation as needed.  Only the first argument is mandatory.
@@ -977,7 +977,7 @@
 </dd>
 <dt> <code>@ref{<var>node-name</var>, [<var>entry</var>], 
[<var>topic-or-title</var>], [<var>info-file</var>], 
[<var>manual</var>]}</code></dt>
 <dd><p>Make a reference.  In a printed manual, the reference does not start
-with a `See'.  Follow command with a punctuation mark.  Only the first
+with a &lsquo;See&rsquo;.  Follow command with a punctuation mark.  Only the 
first
 argument is mandatory.  See section <a 
href="ref.html#SEC115"><code>@ref</code></a>.
 </p>
 </dd>
@@ -1119,14 +1119,14 @@
 <dt> <code>@subsubheading <var>title</var></code></dt>
 <dd><p>Print an unnumbered subsubsection-like heading in the text, but not in
 the table of contents of a printed manual.  In Info, the title is
-underlined with periods.  See section <a href="subsubsection.html#SEC83">The 
`subsub' Commands</a>.
+underlined with periods.  See section <a href="subsubsection.html#SEC83">The 
&lsquo;subsub&rsquo; Commands</a>.
 </p>
 </dd>
 <dt> <code>@subsubsection <var>title</var></code></dt>
 <dd><p>Begin a subsubsection within a subsection.  In a printed manual,
 the subsubsection title is numbered and appears in the table of
 contents.  In Info, the title is underlined with periods.
-See section <a href="subsubsection.html#SEC83">The `subsub' Commands</a>.
+See section <a href="subsubsection.html#SEC83">The &lsquo;subsub&rsquo; 
Commands</a>.
 </p>
 </dd>
 <dt> <code>@subtitle <var>title</var></code></dt>
@@ -1186,14 +1186,14 @@
 <dt> <code>@thispage</code></dt>
 <dt> <code>@thistitle</code></dt>
 <dd><p>Only allowed in a heading or footing.  Stands for the number and name of
-the current chapter (in the format `Chapter 1: Title'), the chapter name
+the current chapter (in the format &lsquo;Chapter 1: Title&rsquo;), the 
chapter name
 only, the filename, the current page number, and the title of the
 document, respectively.  See section <a href="Custom-Headings.html#SEC307">How 
to Make Your Own Headings</a>.
 </p>
 </dd>
 <dt> <code>@tieaccent{<var>cc</var>}</code></dt>
 <dd><p>Generate a tie-after accent over the next two characters <var>cc</var>, 
as in
-`oo['.  See section <a href="Inserting-Accents.html#SEC183">Inserting 
Accents</a>.
+&lsquo;oo[&rsquo;.  See section <a 
href="Inserting-Accents.html#SEC183">Inserting Accents</a>.
 </p>
 </dd>
 <dt> <code>@tindex <var>entry</var></code></dt>
@@ -1220,14 +1220,14 @@
 </p>
 </dd>
 <dt> <code>@today{}</code></dt>
-<dd><p>Insert the current date, in `1 Jan 1900' style.  See section <a 
href="Custom-Headings.html#SEC307">How to Make Your Own Headings</a>.
+<dd><p>Insert the current date, in &lsquo;1 Jan 1900&rsquo; style.  See 
section <a href="Custom-Headings.html#SEC307">How to Make Your Own Headings</a>.
 </p>
 </dd>
 <dt> <code>@top <var>title</var></code></dt>
 <dd><p>In a Texinfo file to be formatted with <code>makeinfo</code>, identify 
the
 topmost <code>@node</code> in the file, which must be written on the line
 immediately preceding the <code>@top</code> command.  Used for
-<code>makeinfo</code>'s node pointer insertion feature.  The title is
+<code>makeinfo</code>&rsquo;s node pointer insertion feature.  The title is
 underlined with asterisks.  Both the <code>@node</code> line and the 
<code>@top</code>
 line normally should be enclosed by <code>@ifnottex</code> and <code>@end
 ifnottex</code>.  In TeX and <code>texinfo-format-buffer</code>, the 
<code>@top</code>
@@ -1267,7 +1267,7 @@
 <dd><p>In a printed manual, begin an unnumbered subsubsection within a
 chapter.  The title appears in the table of contents of a printed
 manual.  In Info, the title is underlined with periods.
-See section <a href="subsubsection.html#SEC83">The `subsub' Commands</a>.
+See section <a href="subsubsection.html#SEC83">The &lsquo;subsub&rsquo; 
Commands</a>.
 </p>
 </dd>
 <dt> <code>@uref{<var>url</var>[, <var>displayed-text</var>][, 
<var>replacement</var>}</code></dt>
@@ -1338,7 +1338,7 @@
 </p>
 </dd>
 <dt> <code>@xref{<var>node-name</var>, [<var>entry</var>], 
[<var>topic-or-title</var>], [<var>info-file</var>], 
[<var>manual</var>]}</code></dt>
-<dd><p>Make a reference that starts with `See' in a printed manual.  Follow
+<dd><p>Make a reference that starts with &lsquo;See&rsquo; in a printed 
manual.  Follow
 command with a punctuation mark.  Only the first argument is
 mandatory.  See section <a href="xref.html#SEC108"><code>@xref</code></a>.
 </p></dd>

Index: Tests/nodes_texinfo_res/Command-Syntax.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/Command-Syntax.html,v
retrieving revision 1.23
retrieving revision 1.24
diff -u -b -r1.23 -r1.24
--- Tests/nodes_texinfo_res/Command-Syntax.html 5 Feb 2007 15:30:24 -0000       
1.23
+++ Tests/nodes_texinfo_res/Command-Syntax.html 3 Oct 2007 09:34:42 -0000       
1.24
@@ -102,7 +102,7 @@
 right-hand braces.  These commands insert special symbols in the
 document; they do not require arguments.  For example,
 <code>@dots{}</code> &rArr; &lsquo;<samp>&hellip;</samp>&rsquo;, 
<code>@equiv{}</code>
-&rArr; &lsquo;<samp>&equiv;</samp>&rsquo;, <code>@TeX{}</code> &rArr; `TeX',
+&rArr; &lsquo;<samp>&equiv;</samp>&rsquo;, <code>@TeX{}</code> &rArr; 
&lsquo;TeX&rsquo;,
 and <code>@bullet{}</code> &rArr; &lsquo;<samp>&bull;</samp>&rsquo;.
 </p>
 </dd>
@@ -126,7 +126,7 @@
 <p>Thus, the alphabetic commands fall into classes that have
 different argument syntaxes.  You cannot tell to which class a command
 belongs by the appearance of its name, but you can tell by the
-command's meaning: if the command stands for a glyph, it is in
+command&rsquo;s meaning: if the command stands for a glyph, it is in
 class 2 and does not require an argument; if it makes sense to use the
 command together with other text as part of a paragraph, the command
 is in class 3 and must be followed by an argument in braces;

Index: Tests/nodes_texinfo_res/Command-and-Variable-Index.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/Command-and-Variable-Index.html,v
retrieving revision 1.26
retrieving revision 1.27
diff -u -b -r1.26 -r1.27
--- Tests/nodes_texinfo_res/Command-and-Variable-Index.html     30 Sep 2007 
12:47:37 -0000      1.26
+++ Tests/nodes_texinfo_res/Command-and-Variable-Index.html     3 Oct 2007 
09:34:42 -0000       1.27
@@ -246,7 +246,7 @@
 <tr><td></td><td valign="top"><a 
href="unnumberedsec-appendixsec-heading.html#SEC80"><code>appendixsec</code></a></td><td
 valign="top"><a href="unnumberedsec-appendixsec-heading.html#SEC80">5.8 
<code>@unnumberedsec</code>, <code>@appendixsec</code>, 
<code>@heading</code></a></td></tr>
 <tr><td></td><td valign="top"><a 
href="unnumberedsec-appendixsec-heading.html#IDX92"><code>appendixsection</code></a></td><td
 valign="top"><a href="unnumberedsec-appendixsec-heading.html#SEC80">5.8 
<code>@unnumberedsec</code>, <code>@appendixsec</code>, 
<code>@heading</code></a></td></tr>
 <tr><td></td><td valign="top"><a 
href="unnumberedsubsec-appendixsubsec-subheading.html#SEC82"><code>appendixsubsec</code></a></td><td
 valign="top"><a 
href="unnumberedsubsec-appendixsubsec-subheading.html#SEC82">5.10 The 
<code>@subsection</code>-like Commands</a></td></tr>
-<tr><td></td><td valign="top"><a 
href="subsubsection.html#SEC83"><code>appendixsubsubsec</code></a></td><td 
valign="top"><a href="subsubsection.html#SEC83">5.11 The `subsub' 
Commands</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="subsubsection.html#SEC83"><code>appendixsubsubsec</code></a></td><td 
valign="top"><a href="subsubsection.html#SEC83">5.11 The &lsquo;subsub&rsquo; 
Commands</a></td></tr>
 <tr><td></td><td valign="top"><a 
href="Sample-Function-Definition.html#IDX286"><code>apply</code></a></td><td 
valign="top"><a href="Sample-Function-Definition.html#SEC226">15.6 A Sample 
Function Definition</a></td></tr>
 <tr><td></td><td valign="top"><a 
href="Two_002dcolumn-Tables.html#IDX138"><code>asis</code></a></td><td 
valign="top"><a href="Two_002dcolumn-Tables.html#SEC160">Using the 
<code>@table</code> Command</a></td></tr>
 <tr><td></td><td valign="top"><a 
href="title-subtitle-author.html#SEC55"><code>author</code></a></td><td 
valign="top"><a href="title-subtitle-author.html#SEC55">3.4.3 
<code>@title</code>, <code>@subtitle</code>, and 
<code>@author</code></a></td></tr>
@@ -281,7 +281,7 @@
 <tr><td></td><td valign="top"><a 
href="New-Indices.html#SEC173"><code>defcodeindex</code></a></td><td 
valign="top"><a href="New-Indices.html#SEC173">12.5 Defining New 
Indices</a></td></tr>
 <tr><td></td><td valign="top"><a 
href="Abstract-Objects.html#IDX278"><code>defcv</code></a></td><td 
valign="top"><a href="Abstract-Objects.html#SEC223">15.4.5 Object-Oriented 
Programming</a></td></tr>
 <tr><td></td><td valign="top"><a 
href="Functions-Commands.html#IDX266"><code>deffn</code></a></td><td 
valign="top"><a href="Functions-Commands.html#SEC219">15.4.1 Functions and 
Similar Entities</a></td></tr>
-<tr><td></td><td valign="top"><a 
href="deffnx.html#SEC217"><code>deffnx</code></a></td><td valign="top"><a 
href="deffnx.html#SEC217">15.3 Two or More `First' Lines</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="deffnx.html#SEC217"><code>deffnx</code></a></td><td valign="top"><a 
href="deffnx.html#SEC217">15.3 Two or More &lsquo;First&rsquo; 
Lines</a></td></tr>
 <tr><td></td><td valign="top"><a 
href="New-Indices.html#SEC173"><code>defindex</code></a></td><td 
valign="top"><a href="New-Indices.html#SEC173">12.5 Defining New 
Indices</a></td></tr>
 <tr><td></td><td valign="top"><a 
href="definfoenclose.html#SEC243"><code>definfoenclose</code></a></td><td 
valign="top"><a href="definfoenclose.html#SEC243">18.5 
&lsquo;<samp>definfoenclose</samp>&rsquo;: Customized Highlighting</a></td></tr>
 <tr><td></td><td valign="top"><a 
href="Abstract-Objects.html#IDX279"><code>defivar</code></a></td><td 
valign="top"><a href="Abstract-Objects.html#SEC223">15.4.5 Object-Oriented 
Programming</a></td></tr>
@@ -331,7 +331,7 @@
 <tr><td></td><td valign="top"><a 
href="example.html#SEC144"><code>example</code></a></td><td valign="top"><a 
href="example.html#SEC144">10.3 <code>@example</code>: Example 
Text</a></td></tr>
 <tr><td></td><td valign="top"><a 
href="exampleindent.html#SEC66"><code>exampleindent</code></a></td><td 
valign="top"><a href="exampleindent.html#SEC66">3.6.4 
<code>@exampleindent</code>: Environment Indenting</a></td></tr>
 <tr><td></td><td valign="top"><a 
href="Inserting-Accents.html#IDX193"><code>exclamdown</code></a></td><td 
valign="top"><a href="Inserting-Accents.html#SEC183">13.3 Inserting 
Accents</a></td></tr>
-<tr><td></td><td valign="top"><a 
href="exdent.html#SEC151"><code>exdent</code></a></td><td valign="top"><a 
href="exdent.html#SEC151">10.10 <code>@exdent</code>: Undoing a Line's 
Indentation</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="exdent.html#SEC151"><code>exdent</code></a></td><td valign="top"><a 
href="exdent.html#SEC151">10.10 <code>@exdent</code>: Undoing a Line&rsquo;s 
Indentation</a></td></tr>
 <tr><td></td><td valign="top"><a 
href="expansion.html#SEC196"><code>expansion</code></a></td><td valign="top"><a 
href="expansion.html#SEC196">13.9.3 <code>@expansion{}</code> (&rarr;): 
Indicating an Expansion</a></td></tr>
 <tr><td colspan="3"> <hr></td></tr>
 </table>

Index: Tests/nodes_texinfo_res/Compile_002dCommand.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/Compile_002dCommand.html,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -b -r1.10 -r1.11
--- Tests/nodes_texinfo_res/Compile_002dCommand.html    5 Feb 2007 15:30:24 
-0000       1.10
+++ Tests/nodes_texinfo_res/Compile_002dCommand.html    3 Oct 2007 09:34:42 
-0000       1.11
@@ -96,7 +96,7 @@
 </pre></td></tr></table>
 
 <p>This technique is most often used by programmers who also compile programs
-this way; see <a 
href="../emacs/Compilation.html#Compilation">(emacs)Compilation</a> section 
`Compilation' in <cite>The GNU Emacs Manual</cite>.
+this way; see <a 
href="../emacs/Compilation.html#Compilation">(emacs)Compilation</a> section 
&lsquo;Compilation&rsquo; in <cite>The GNU Emacs Manual</cite>.
 </p>
 
 <hr size="1">

Index: Tests/nodes_texinfo_res/Contents.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/Contents.html,v
retrieving revision 1.22
retrieving revision 1.23
diff -u -b -r1.22 -r1.23
--- Tests/nodes_texinfo_res/Contents.html       5 Feb 2007 15:30:24 -0000       
1.22
+++ Tests/nodes_texinfo_res/Contents.html       3 Oct 2007 09:34:42 -0000       
1.23
@@ -108,7 +108,7 @@
 
 <p>Both contents commands should be written on a line by themselves.
 The contents commands automatically generate a chapter-like heading at
-the top of the first table of contents page, so don't include any
+the top of the first table of contents page, so don&rsquo;t include any
 sectioning command such as <code>@unnumbered</code> before them.
 </p>
 <p>Since an Info file uses menus instead of tables of contents, the Info

Index: Tests/nodes_texinfo_res/Conventions.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/Conventions.html,v
retrieving revision 1.26
retrieving revision 1.27
diff -u -b -r1.26 -r1.27
--- Tests/nodes_texinfo_res/Conventions.html    5 Feb 2007 15:30:24 -0000       
1.26
+++ Tests/nodes_texinfo_res/Conventions.html    3 Oct 2007 09:34:42 -0000       
1.27
@@ -95,12 +95,12 @@
 
 </li><li>
 It is customary in TeX to use doubled single-quote characters to
-begin and end quotations: <tt>``&hellip;''</tt>.  This
+begin and end quotations: <tt>&lsquo;&lsquo;&hellip;&rsquo;&rsquo;</tt>.  This
 convention should be followed in Texinfo files.  TeX converts
 two single quotes to left- and right-hand doubled
 quotation marks, 
 and Info converts doubled single-quote characters to <small>ASCII</small>
-double-quotes: <tt>``&hellip;''</tt> becomes <tt>&quot;&hellip;&quot;</tt>.
+double-quotes: <tt>&lsquo;&lsquo;&hellip;&rsquo;&rsquo;</tt> becomes 
<tt>&quot;&hellip;&quot;</tt>.
 
 </li><li>
 Use three hyphens in a row, &lsquo;<samp>---</samp>&rsquo;, for a 
dash&mdash;like this.  In

Index: Tests/nodes_texinfo_res/Cross-Reference-Commands.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/Cross-Reference-Commands.html,v
retrieving revision 1.24
retrieving revision 1.25
diff -u -b -r1.24 -r1.25
--- Tests/nodes_texinfo_res/Cross-Reference-Commands.html       5 Feb 2007 
15:30:24 -0000       1.24
+++ Tests/nodes_texinfo_res/Cross-Reference-Commands.html       3 Oct 2007 
09:34:42 -0000       1.25
@@ -85,20 +85,20 @@
 </p>
 <dl compact="compact">
 <dt> <code>@xref</code></dt>
-<dd><p>Used to start a sentence in the printed manual saying `See &hellip;'
+<dd><p>Used to start a sentence in the printed manual saying &lsquo;See 
&hellip;&rsquo;
 or an Info cross-reference saying &lsquo;<samp>*Note <var>name</var>: 
<var>node</var>.</samp>&rsquo;.
 </p>
 </dd>
 <dt> <code>@ref</code></dt>
 <dd><p>Used within or, more often, at the end of a sentence; same as
 <code>@xref</code> for Info; produces just the reference in the printed
-manual without a preceding `See'.
+manual without a preceding &lsquo;See&rsquo;.
 </p>
 </dd>
 <dt> <code>@pxref</code></dt>
 <dd><p>Used within parentheses to make a reference that suits both an Info
-file and a printed book.  Starts with a lower case `see' within the
-printed manual. (&lsquo;<samp>p</samp>&rsquo; is for `parenthesis'.)
+file and a printed book.  Starts with a lower case &lsquo;see&rsquo; within the
+printed manual. (&lsquo;<samp>p</samp>&rsquo; is for 
&lsquo;parenthesis&rsquo;.)
 </p>
 </dd>
 <dt> <code>@inforef</code></dt>

Index: Tests/nodes_texinfo_res/Cross-References.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/Cross-References.html,v
retrieving revision 1.24
retrieving revision 1.25
diff -u -b -r1.24 -r1.25
--- Tests/nodes_texinfo_res/Cross-References.html       5 Feb 2007 15:30:24 
-0000       1.24
+++ Tests/nodes_texinfo_res/Cross-References.html       3 Oct 2007 09:34:42 
-0000       1.25
@@ -92,9 +92,9 @@
 </td></tr>
 <tr><td align="left" valign="top"><a 
href="Cross-Reference-Parts.html#SEC107">8.2 Parts of a Cross 
Reference</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">       A 
cross reference has several parts.
 </td></tr>
-<tr><td align="left" valign="top"><a href="xref.html#SEC108">8.3 
<code>@xref</code></a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">  
                      Begin a reference with `See' &hellip;
+<tr><td align="left" valign="top"><a href="xref.html#SEC108">8.3 
<code>@xref</code></a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">  
                      Begin a reference with &lsquo;See&rsquo; &hellip;
 </td></tr>
-<tr><td align="left" valign="top"><a href="Top-Node-Naming.html#SEC114">8.4 
Naming a `Top' Node</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top"> 
            How to refer to the beginning of another file.
+<tr><td align="left" valign="top"><a href="Top-Node-Naming.html#SEC114">8.4 
Naming a &lsquo;Top&rsquo; Node</a></td><td>&nbsp;&nbsp;</td><td align="left" 
valign="top">             How to refer to the beginning of another file.
 </td></tr>
 <tr><td align="left" valign="top"><a href="ref.html#SEC115">8.5 
<code>@ref</code></a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">   
                      A reference for the last part of a sentence.
 </td></tr>
@@ -136,7 +136,7 @@
 This is evident in Info, in which a cross reference takes you to the
 specified location.  TeX also uses nodes to define cross reference
 locations, but the action is less obvious.  When TeX generates a DVI
-file, it records each node's page number and uses the page numbers in making
+file, it records each node&rsquo;s page number and uses the page numbers in 
making
 references.  Thus, if you are writing a manual that will only be
 printed, and will not be used online, you must nonetheless write
 <code>@node</code> lines to name the places to which you make cross

Index: Tests/nodes_texinfo_res/Custom-Headings.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/Custom-Headings.html,v
retrieving revision 1.26
retrieving revision 1.27
diff -u -b -r1.26 -r1.27
--- Tests/nodes_texinfo_res/Custom-Headings.html        5 Feb 2007 15:30:24 
-0000       1.26
+++ Tests/nodes_texinfo_res/Custom-Headings.html        3 Oct 2007 09:34:42 
-0000       1.27
@@ -132,7 +132,7 @@
 <dt> <code>@everyheading <var>left</var> @| <var>center</var> @| 
<var>right</var></code></dt>
 <dt> <code>@everyfooting <var>left</var> @| <var>center</var> @| 
<var>right</var></code></dt>
 <dd>
-<p>The `every' commands specify the format for both even- and odd-numbered
+<p>The &lsquo;every&rsquo; commands specify the format for both even- and 
odd-numbered
 pages.  These commands are for documents that are printed on one side
 of each sheet of paper, or for documents in which you want symmetrical
 headers or footers.
@@ -147,7 +147,7 @@
 <dt> <code>@evenfooting <var>left</var> @| <var>center</var> @| 
<var>right</var></code></dt>
 <dt> <code>@oddfooting  <var>left</var> @| <var>center</var> @| 
<var>right</var></code></dt>
 <dd>
-<p>The `even' and `odd' commands specify the format for even-numbered
+<p>The &lsquo;even&rsquo; and &lsquo;odd&rsquo; commands specify the format 
for even-numbered
 pages and odd-numbered pages.  These commands are for books and
 manuals that are printed on both sides of each sheet of paper.
 </p></dd>
@@ -177,7 +177,7 @@
 </dd>
 <dt> <code>@thischapter</code></dt>
 <dd><p>Expands to the number and name of the current
-chapter, in the format `Chapter 1: Title'.
+chapter, in the format &lsquo;Chapter 1: Title&rsquo;.
 </p>
 <a name="IDX459"></a>
 </dd>
@@ -198,7 +198,7 @@
 </dl>
 
 <p>You can also use the <code>@today{}</code> command, which expands to the
-current date, in `1 Jan 1900' format.
+current date, in &lsquo;1 Jan 1900&rsquo; format.
 <a name="IDX461"></a>
 </p>
 <p>Other @-commands and text are printed in a header or footer just as

Index: Tests/nodes_texinfo_res/Debugging-with-Info.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/Debugging-with-Info.html,v
retrieving revision 1.24
retrieving revision 1.25
diff -u -b -r1.24 -r1.25
--- Tests/nodes_texinfo_res/Debugging-with-Info.html    5 Feb 2007 15:30:24 
-0000       1.24
+++ Tests/nodes_texinfo_res/Debugging-with-Info.html    3 Oct 2007 09:34:42 
-0000       1.25
@@ -99,7 +99,7 @@
 occurred (or more precisely, where it was detected).
 </p>
 <p>For example, if you accidentally end a menu with the command <code>@end
-menus</code> with an `s' on the end, instead of with <code>@end menu</code>, 
you
+menus</code> with an &lsquo;s&rsquo; on the end, instead of with <code>@end 
menu</code>, you
 will see an error message that says:
 </p>
 <table><tr><td>&nbsp;</td><td><pre class="example">@end menus is not handled 
by texinfo
@@ -162,8 +162,8 @@
 after typing the Info <kbd>f</kbd> command, Info will attempt to go to the
 referenced node.  If you type <kbd>f catch &lt;TAB&gt; &lt;RET&gt;</kbd>, Info
 will complete the node name of the correctly written example and take
-you to the `Catching Mistakes' node.  (If you try this, you can return
-from the `Catching Mistakes' node by typing <kbd>l</kbd>
+you to the &lsquo;Catching Mistakes&rsquo; node.  (If you try this, you can 
return
+from the &lsquo;Catching Mistakes&rsquo; node by typing <kbd>l</kbd>
 (<code>Info-last</code>).)
 </p>
 

Index: Tests/nodes_texinfo_res/Def-Cmd-Template.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/Def-Cmd-Template.html,v
retrieving revision 1.22
retrieving revision 1.23
diff -u -b -r1.22 -r1.23
--- Tests/nodes_texinfo_res/Def-Cmd-Template.html       5 Feb 2007 15:30:24 
-0000       1.22
+++ Tests/nodes_texinfo_res/Def-Cmd-Template.html       3 Oct 2007 09:34:42 
-0000       1.23
@@ -118,7 +118,7 @@
 </blockquote>
 
 <p>Capitalize the category name like a title.  If the name of the
-category contains spaces, as in the phrase `Interactive Command',
+category contains spaces, as in the phrase &lsquo;Interactive Command&rsquo;,
 write braces around it.  For example:
 </p>
 <table><tr><td>&nbsp;</td><td><pre class="example">@deffn {Interactive 
Command} isearch-forward

Index: Tests/nodes_texinfo_res/Defining-Macros.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/Defining-Macros.html,v
retrieving revision 1.22
retrieving revision 1.23
diff -u -b -r1.22 -r1.23
--- Tests/nodes_texinfo_res/Defining-Macros.html        5 Feb 2007 15:30:24 
-0000       1.22
+++ Tests/nodes_texinfo_res/Defining-Macros.html        3 Oct 2007 09:34:42 
-0000       1.23
@@ -137,7 +137,7 @@
 @address@hidden
 </pre></td></tr></table>
 
-<p>This produces the output `a1atextb2b'.  With 
&lsquo;<samp>@macro</samp>&rsquo; instead of
+<p>This produces the output &lsquo;a1atextb2b&rsquo;.  With 
&lsquo;<samp>@macro</samp>&rsquo; instead of
 &lsquo;<samp>@rmacro</samp>&rsquo;, an error message is given.
 </p>
 <a name="IDX312"></a>

Index: Tests/nodes_texinfo_res/Defining-New-Texinfo-Commands.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/Defining-New-Texinfo-Commands.html,v
retrieving revision 1.24
retrieving revision 1.25
diff -u -b -r1.24 -r1.25
--- Tests/nodes_texinfo_res/Defining-New-Texinfo-Commands.html  5 Feb 2007 
15:30:24 -0000       1.24
+++ Tests/nodes_texinfo_res/Defining-New-Texinfo-Commands.html  3 Oct 2007 
09:34:42 -0000       1.25
@@ -107,7 +107,7 @@
 <table class="menu" border="0" cellspacing="0">
 <tr><td align="left" valign="top"><a href="Defining-Macros.html#SEC239">18.1 
Defining Macros</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">     
        Defining and undefining new commands.
 </td></tr>
-<tr><td align="left" valign="top"><a href="Invoking-Macros.html#SEC240">18.2 
Invoking Macros</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">     
        Using a macro, once you've defined it.
+<tr><td align="left" valign="top"><a href="Invoking-Macros.html#SEC240">18.2 
Invoking Macros</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">     
        Using a macro, once you&rsquo;ve defined it.
 </td></tr>
 <tr><td align="left" valign="top"><a href="Macro-Details.html#SEC241">18.3 
Macro Details</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">       
        Beyond basic macro usage.
 </td></tr>

Index: Tests/nodes_texinfo_res/Definition-Commands.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/Definition-Commands.html,v
retrieving revision 1.20
retrieving revision 1.21
diff -u -b -r1.20 -r1.21
--- Tests/nodes_texinfo_res/Definition-Commands.html    5 Feb 2007 15:30:24 
-0000       1.20
+++ Tests/nodes_texinfo_res/Definition-Commands.html    3 Oct 2007 09:34:42 
-0000       1.21
@@ -87,10 +87,10 @@
 format.
 </p>
 <p>In the Info file, a definition causes the entity
-category&mdash;`Function', `Variable', or whatever&mdash;to appear at the
+category&mdash;&lsquo;Function&rsquo;, &lsquo;Variable&rsquo;, or 
whatever&mdash;to appear at the
 beginning of the first line of the definition, followed by the
-entity's name and arguments.  In the printed manual, the command
-causes TeX to print the entity's name and its arguments on the left
+entity&rsquo;s name and arguments.  In the printed manual, the command
+causes TeX to print the entity&rsquo;s name and its arguments on the left
 margin and print the category next to the right margin.  In both
 output formats, the body of the definition is indented.  Also, the
 name of the entity is entered into the appropriate index:
@@ -108,7 +108,7 @@
 </td></tr>
 <tr><td align="left" valign="top"><a 
href="Optional-Arguments.html#SEC216">15.2 Optional and Repeated 
Arguments</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">          
How to handle optional and repeated arguments.
 </td></tr>
-<tr><td align="left" valign="top"><a href="deffnx.html#SEC217">15.3 Two or 
More `First' Lines</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">  
                    How to group two or more `first' lines.
+<tr><td align="left" valign="top"><a href="deffnx.html#SEC217">15.3 Two or 
More &lsquo;First&rsquo; Lines</a></td><td>&nbsp;&nbsp;</td><td align="left" 
valign="top">                      How to group two or more &lsquo;first&rsquo; 
lines.
 </td></tr>
 <tr><td align="left" valign="top"><a 
href="Def-Cmds-in-Detail.html#SEC218">15.4 The Definition 
Commands</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">          
All the definition commands.
 </td></tr>

Index: Tests/nodes_texinfo_res/Directory-File.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/Directory-File.html,v
retrieving revision 1.24
retrieving revision 1.25
diff -u -b -r1.24 -r1.25
--- Tests/nodes_texinfo_res/Directory-File.html 5 Feb 2007 15:30:24 -0000       
1.24
+++ Tests/nodes_texinfo_res/Directory-File.html 3 Oct 2007 09:34:42 -0000       
1.25
@@ -101,17 +101,17 @@
 &hellip;
 </pre></td></tr></table>
 
-<p>Each of these menu entries points to the `Top' node of the Info file
+<p>Each of these menu entries points to the &lsquo;Top&rsquo; node of the Info 
file
 that is named in parentheses.  (The menu entry does not need to
-specify the `Top' node, since Info goes to the `Top' node if no node
+specify the &lsquo;Top&rsquo; node, since Info goes to the &lsquo;Top&rsquo; 
node if no node
 name is mentioned.  See section <a href="Other-Info-Files.html#SEC103">Nodes 
in Other Info Files</a>.)
 </p>
-<p>Thus, the &lsquo;<samp>Info</samp>&rsquo; entry points to the `Top' node of 
the
-&lsquo;<tt>info</tt>&rsquo; file and the &lsquo;<samp>Emacs</samp>&rsquo; 
entry points to the `Top' node
+<p>Thus, the &lsquo;<samp>Info</samp>&rsquo; entry points to the 
&lsquo;Top&rsquo; node of the
+&lsquo;<tt>info</tt>&rsquo; file and the &lsquo;<samp>Emacs</samp>&rsquo; 
entry points to the &lsquo;Top&rsquo; node
 of the &lsquo;<tt>emacs</tt>&rsquo; file.
 </p>
-<p>In each of the Info files, the `Up' pointer of the `Top' node refers
-back to the <code>dir</code> file.  For example, the line for the `Top'
+<p>In each of the Info files, the &lsquo;Up&rsquo; pointer of the 
&lsquo;Top&rsquo; node refers
+back to the <code>dir</code> file.  For example, the line for the 
&lsquo;Top&rsquo;
 node of the Emacs manual looks like this in Info:
 </p>
 <table><tr><td>&nbsp;</td><td><pre class="example">File: emacs  Node: Top, Up: 
(DIR), Next: Distrib

Index: Tests/nodes_texinfo_res/Document-Permissions.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/Document-Permissions.html,v
retrieving revision 1.19
retrieving revision 1.20
diff -u -b -r1.19 -r1.20
--- Tests/nodes_texinfo_res/Document-Permissions.html   5 Feb 2007 15:30:24 
-0000       1.19
+++ Tests/nodes_texinfo_res/Document-Permissions.html   3 Oct 2007 09:34:42 
-0000       1.20
@@ -88,7 +88,7 @@
 insert the text at appropriate points.
 </p>
 <table class="menu" border="0" cellspacing="0">
-<tr><td align="left" valign="top"><a href="copying.html#SEC50">3.3.1 
<code>@copying</code>: Declare copying 
permissions</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">         
        Declare the document's copying permissions.
+<tr><td align="left" valign="top"><a href="copying.html#SEC50">3.3.1 
<code>@copying</code>: Declare copying 
permissions</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">         
        Declare the document&rsquo;s copying permissions.
 </td></tr>
 <tr><td align="left" valign="top"><a href="insertcopying.html#SEC51">3.3.2 
<code>@insertcopying</code>: Include permissions 
text</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">           
Where to insert the permissions.
 </td></tr>

Index: Tests/nodes_texinfo_res/Emacs-Editing.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/Emacs-Editing.html,v
retrieving revision 1.20
retrieving revision 1.21
diff -u -b -r1.20 -r1.21
--- Tests/nodes_texinfo_res/Emacs-Editing.html  5 Feb 2007 15:30:24 -0000       
1.20
+++ Tests/nodes_texinfo_res/Emacs-Editing.html  3 Oct 2007 09:34:42 -0000       
1.21
@@ -83,7 +83,7 @@
 
 <p>In most cases, the usual Text mode commands work the same in Texinfo
 mode as they do in Text mode.  Texinfo mode adds new editing commands
-and tools to GNU Emacs' general purpose editing features.  The major
+and tools to GNU Emacs&rsquo; general purpose editing features.  The major
 difference concerns filling.  In Texinfo mode, the paragraph
 separation variable and syntax table are redefined so that Texinfo
 commands that should be on lines of their own are not inadvertently
@@ -98,7 +98,7 @@
 delimiter, you can jump from chapter title to chapter title with the
 <kbd>C-x ]</kbd> (<code>forward-page</code>) and <kbd>C-x [</kbd>
 (<code>backward-page</code>) commands and narrow to a chapter with the
-<kbd>C-x p</kbd> (<code>narrow-to-page</code>) command.  (See <a 
href="../emacs/Pages.html#Pages">(emacs)Pages</a> section `Pages' in <cite>The 
GNU Emacs Manual</cite>, for details about the page commands.)
+<kbd>C-x p</kbd> (<code>narrow-to-page</code>) command.  (See <a 
href="../emacs/Pages.html#Pages">(emacs)Pages</a> section &lsquo;Pages&rsquo; 
in <cite>The GNU Emacs Manual</cite>, for details about the page commands.)
 </p>
 <p>You may name a Texinfo file however you wish, but the convention is to
 end a Texinfo file name with one of the extensions

Index: Tests/nodes_texinfo_res/Ending-a-Sentence.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/Ending-a-Sentence.html,v
retrieving revision 1.20
retrieving revision 1.21
diff -u -b -r1.20 -r1.21
--- Tests/nodes_texinfo_res/Ending-a-Sentence.html      5 Feb 2007 15:30:24 
-0000       1.20
+++ Tests/nodes_texinfo_res/Ending-a-Sentence.html      3 Oct 2007 09:34:42 
-0000       1.21
@@ -102,7 +102,7 @@
 &lsquo;<samp>.</samp>&rsquo;; likewise for <code>@!</code> and <code>@?</code>.
 </p>
 <p>The meanings of <code>@:</code> and <code>@.</code> in Texinfo are designed 
to
-work well with the Emacs sentence motion commands (see <a 
href="../emacs/Sentences.html#Sentences">(emacs)Sentences</a> section 
`Sentences' in <cite>The GNU Emacs Manual</cite>).
+work well with the Emacs sentence motion commands (see <a 
href="../emacs/Sentences.html#Sentences">(emacs)Sentences</a> section 
&lsquo;Sentences&rsquo; in <cite>The GNU Emacs Manual</cite>).
 </p>
 <p>Do not put braces after any of these commands.
 </p>

Index: Tests/nodes_texinfo_res/Error-Glyph.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/Error-Glyph.html,v
retrieving revision 1.22
retrieving revision 1.23
diff -u -b -r1.22 -r1.23
--- Tests/nodes_texinfo_res/Error-Glyph.html    5 Feb 2007 15:30:24 -0000       
1.22
+++ Tests/nodes_texinfo_res/Error-Glyph.html    3 Oct 2007 09:34:42 -0000       
1.23
@@ -85,7 +85,7 @@
 designate the error message with the <code>@error{}</code> command.
 </p>
 <p>The <code>@error{}</code> command is displayed as 
&lsquo;<samp>error--&gt;</samp>&rsquo; in Info
-and as the word `error' in a box in the printed output.
+and as the word &lsquo;error&rsquo; in a box in the printed output.
 </p>
 <p>Thus,
 </p>

Index: Tests/nodes_texinfo_res/First-Node.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/First-Node.html,v
retrieving revision 1.24
retrieving revision 1.25
diff -u -b -r1.24 -r1.25
--- Tests/nodes_texinfo_res/First-Node.html     5 Feb 2007 15:30:24 -0000       
1.24
+++ Tests/nodes_texinfo_res/First-Node.html     3 Oct 2007 09:34:42 -0000       
1.25
@@ -83,7 +83,7 @@
 
 <p>The first node of a Texinfo file is the <em>Top</em> node, except in an
 included file (see section <a href="Include-Files.html#SEC297">Include 
Files</a>).  The Top node should contain a
-short summary, copying permissions, and a master menu.  See section <a 
href="The-Top-Node.html#SEC59">The `Top' Node and Master Menu</a>, for more 
information on the Top node contents and examples.
+short summary, copying permissions, and a master menu.  See section <a 
href="The-Top-Node.html#SEC59">The &lsquo;Top&rsquo; Node and Master Menu</a>, 
for more information on the Top node contents and examples.
 </p>
 <p>Here is a description of the node pointers to be used in the Top node:
 </p>
@@ -92,7 +92,7 @@
 <a name="IDX106"></a>
 <a name="IDX107"></a>
 The Top node (which must be named &lsquo;<samp>top</samp>&rsquo; or 
&lsquo;<samp>Top</samp>&rsquo;) should have
-as its `Up' node the name of a node in another file, where there is a
+as its &lsquo;Up&rsquo; node the name of a node in another file, where there 
is a
 menu that leads to this file.  Specify the file name in parentheses.
 
 <p>Usually, all Info files are installed in the same Info directory tree;
@@ -102,7 +102,7 @@
 </p>
 </li><li>
 <a name="IDX108"></a>
-On the other hand, do not define the `Previous' node of the Top node to
+On the other hand, do not define the &lsquo;Previous&rsquo; node of the Top 
node to
 be &lsquo;<samp>(dir)</samp>&rsquo;, as it causes confusing behavior for 
users: if you are
 in the Top node and hits &lt;DEL&gt; to go backwards, you wind up in the
 middle of the some other entry in the &lsquo;<tt>dir</tt>&rsquo; file, which 
has nothing
@@ -110,7 +110,7 @@
 
 </li><li>
 <a name="IDX109"></a>
-The `Next' node of the Top node should be the first chapter in your
+The &lsquo;Next&rsquo; node of the Top node should be the first chapter in your
 document.
 
 </li></ul>

Index: Tests/nodes_texinfo_res/Footnote-Commands.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/Footnote-Commands.html,v
retrieving revision 1.22
retrieving revision 1.23
diff -u -b -r1.22 -r1.23
--- Tests/nodes_texinfo_res/Footnote-Commands.html      5 Feb 2007 15:30:24 
-0000       1.22
+++ Tests/nodes_texinfo_res/Footnote-Commands.html      3 Oct 2007 09:34:42 
-0000       1.23
@@ -104,7 +104,7 @@
 <p>As you can see, the source includes two punctuation marks next to each
 other; in this case, &lsquo;<samp>.};</samp>&rsquo; is the sequence.  This is 
normal (the
 first ends the footnote and the second belongs to the sentence being
-footnoted), so don't worry that it looks odd.
+footnoted), so don&rsquo;t worry that it looks odd.
 </p>
 <p>In a printed manual or book, the reference mark for a footnote is a
 small, superscripted number; the text of the footnote appears at the
@@ -112,7 +112,7 @@
 </p>
 <p>In Info, the reference mark for a footnote is a pair of parentheses
 with the footnote number between them, like this: 
&lsquo;<samp>(1)</samp>&rsquo;.  The
-reference mark is followed by a cross-reference link to the footnote's
+reference mark is followed by a cross-reference link to the footnote&rsquo;s
 text.
 </p>
 <p>In the HTML output, footnote references are marked with a small,

Index: Tests/nodes_texinfo_res/Footnote-Styles.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/Footnote-Styles.html,v
retrieving revision 1.27
retrieving revision 1.28
diff -u -b -r1.27 -r1.28
--- Tests/nodes_texinfo_res/Footnote-Styles.html        5 Feb 2007 15:30:24 
-0000       1.27
+++ Tests/nodes_texinfo_res/Footnote-Styles.html        3 Oct 2007 09:34:42 
-0000       1.28
@@ -87,7 +87,7 @@
 <ul>
 <li><a name="IDX227"></a>
 </li><li>
-In the `End' node style, all the footnotes for a single node
+In the &lsquo;End&rsquo; node style, all the footnotes for a single node
 are placed at the end of that node.  The footnotes are separated from
 the rest of the node by a line of dashes with the word
 &lsquo;<samp>Footnotes</samp>&rsquo; within it.  Each footnote begins with an
@@ -102,7 +102,7 @@
 
 <a name="IDX228"></a>
 </li><li>
-In the `Separate' node style, all the footnotes for a single
+In the &lsquo;Separate&rsquo; node style, all the footnotes for a single
 node are placed in an automatically constructed node of
 their own.  In this style, a &ldquo;footnote reference&rdquo; follows
 each &lsquo;<samp>(<var>n</var>)</samp>&rsquo; reference mark in the body of 
the
@@ -111,10 +111,10 @@
 
 <p>The name of the node with the footnotes is constructed
 by appending &lsquo;<samp>-Footnotes</samp>&rsquo; to the name of the node
-that contains the footnotes. (Consequently, the footnotes'
+that contains the footnotes. (Consequently, the footnotes&rsquo;
 node for the &lsquo;<tt>Footnotes</tt>&rsquo; node is
-&lsquo;<tt>Footnotes-Footnotes</tt>&rsquo;!)  The footnotes' node has an
-`Up' node pointer that leads back to its parent node.
+&lsquo;<tt>Footnotes-Footnotes</tt>&rsquo;!)  The footnotes&rsquo; node has an
+&lsquo;Up&rsquo; node pointer that leads back to its parent node.
 </p>
 <p>Here is how the first footnote in this manual looks after being
 formatted for Info in the separate node style:
@@ -130,7 +130,7 @@
 style.
 </p>
 <a name="IDX229"></a>
-<p>Use the <code>@footnotestyle</code> command to specify an Info file's
+<p>Use the <code>@footnotestyle</code> command to specify an Info file&rsquo;s
 footnote style.  Write this command at the beginning of a line followed
 by an argument, either &lsquo;<samp>end</samp>&rsquo; for the end node style or
 &lsquo;<samp>separate</samp>&rsquo; for the separate node style.
@@ -151,8 +151,8 @@
 </p>
 <p>If you do not specify a footnote style, the formatting commands use
 their default style.  Currently, <code>texinfo-format-buffer</code> and
-<code>texinfo-format-region</code> use the `separate' style and
-<code>makeinfo</code> uses the `end' style.
+<code>texinfo-format-region</code> use the &lsquo;separate&rsquo; style and
+<code>makeinfo</code> uses the &lsquo;end&rsquo; style.
 </p>
 <p>This chapter contains two footnotes.
 </p>

Index: Tests/nodes_texinfo_res/Format-with-tex_002ftexindex.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/Format-with-tex_002ftexindex.html,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -b -r1.11 -r1.12
--- Tests/nodes_texinfo_res/Format-with-tex_002ftexindex.html   5 Feb 2007 
15:30:24 -0000       1.11
+++ Tests/nodes_texinfo_res/Format-with-tex_002ftexindex.html   3 Oct 2007 
09:34:42 -0000       1.12
@@ -105,7 +105,7 @@
 <a name="IDX322"></a>
 <p>The <code>tex</code> formatting command outputs unsorted index files under
 names that obey a standard convention: the name of your main input file
-with any &lsquo;<samp>.tex</samp>&rsquo; (or similar, see <a 
href="../web2c/tex-invocation.html#tex-invocation">(web2c)tex invocation</a> 
section `tex invocation' in <cite>Web2c</cite>) extension removed, followed by 
the two letter names of indices.
+with any &lsquo;<samp>.tex</samp>&rsquo; (or similar, see <a 
href="../web2c/tex-invocation.html#tex-invocation">(web2c)tex invocation</a> 
section &lsquo;tex invocation&rsquo; in <cite>Web2c</cite>) extension removed, 
followed by the two letter names of indices.
 For example, the raw index output files for the input file
 &lsquo;<tt>foo.texinfo</tt>&rsquo; would be &lsquo;<tt>foo.cp</tt>&rsquo;, 
&lsquo;<tt>foo.vr</tt>&rsquo;, &lsquo;<tt>foo.fn</tt>&rsquo;,
 &lsquo;<tt>foo.tp</tt>&rsquo;, &lsquo;<tt>foo.pg</tt>&rsquo; and 
&lsquo;<tt>foo.ky</tt>&rsquo;.  Those are exactly the
@@ -166,7 +166,7 @@
 </li></ol>
 
 <a name="IDX325"></a>
-<p>Alternatively, it's a one-step process: run <code>texi2dvi</code>
+<p>Alternatively, it&rsquo;s a one-step process: run <code>texi2dvi</code>
 (see section <a href="Format-with-texi2dvi.html#SEC247">Format with 
<code>texi2dvi</code></a>).
 </p>
 <p>You need not run <code>texindex</code> each time after you run 
<code>tex</code>.  If

Index: Tests/nodes_texinfo_res/Formatting-Commands.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/Formatting-Commands.html,v
retrieving revision 1.25
retrieving revision 1.26
diff -u -b -r1.25 -r1.26
--- Tests/nodes_texinfo_res/Formatting-Commands.html    5 Feb 2007 15:30:24 
-0000       1.25
+++ Tests/nodes_texinfo_res/Formatting-Commands.html    3 Oct 2007 09:34:43 
-0000       1.26
@@ -112,7 +112,7 @@
 
 </li><li>
 Write a command such as <code>@chapter</code> at the beginning of a line
-followed by the command's arguments, in this case the chapter title, on
+followed by the command&rsquo;s arguments, in this case the chapter title, on
 the rest of the line.  (<code>@chapter</code> creates chapter titles.)
 
 </li><li>
@@ -130,7 +130,7 @@
 body-text on following lines; and write the matching <code>@end</code>
 command, <code>@end example</code> in this case, at the on a line of its own
 after the body-text. (<code>@example</code> &hellip; <code>@end example</code>
-indents and typesets body-text as an example.)  It's usually ok to
+indents and typesets body-text as an example.)  It&rsquo;s usually ok to
 indent environment commands like this, but in complicated and
 hard-to-define circumstances the extra spaces cause extra space to
 appear in the output, so beware.

Index: Tests/nodes_texinfo_res/Functions-Commands.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/Functions-Commands.html,v
retrieving revision 1.26
retrieving revision 1.27
diff -u -b -r1.26 -r1.27
--- Tests/nodes_texinfo_res/Functions-Commands.html     5 Feb 2007 15:30:24 
-0000       1.26
+++ Tests/nodes_texinfo_res/Functions-Commands.html     3 Oct 2007 09:34:43 
-0000       1.27
@@ -164,7 +164,7 @@
 <dt> <code>@defspec <var>name</var> <var>arguments</var>&hellip;</code></dt>
 <dd><p>The <code>@defspec</code> command is the definition command for special
 forms.  (In Lisp, a special form is an entity much like a function,
-see <a href="../elisp/Special-Forms.html#Special-Forms">(elisp)Special 
Forms</a> section `Special Forms' in <cite>GNU Emacs Lisp Reference 
Manual</cite>.)
+see <a href="../elisp/Special-Forms.html#Special-Forms">(elisp)Special 
Forms</a> section &lsquo;Special Forms&rsquo; in <cite>GNU Emacs Lisp Reference 
Manual</cite>.)
 <code>@defspec</code> is equivalent to &lsquo;<samp>@deffn {Special Form}
 &hellip;</samp>&rsquo; and works like <code>@defun</code>.
 </p></dd>

Index: Tests/nodes_texinfo_res/GNU-Free-Documentation-License.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/GNU-Free-Documentation-License.html,v
retrieving revision 1.23
retrieving revision 1.24
diff -u -b -r1.23 -r1.24
--- Tests/nodes_texinfo_res/GNU-Free-Documentation-License.html 5 Feb 2007 
15:30:24 -0000       1.23
+++ Tests/nodes_texinfo_res/GNU-Free-Documentation-License.html 3 Oct 2007 
09:34:43 -0000       1.24
@@ -130,7 +130,7 @@
 </p>
 <p>A &ldquo;Secondary Section&rdquo; is a named appendix or a front-matter 
section of
 the Document that deals exclusively with the relationship of the
-publishers or authors of the Document to the Document's overall subject
+publishers or authors of the Document to the Document&rsquo;s overall subject
 (or to related matters) and contains nothing that could fall directly
 within that overall subject.  (For example, if the Document is in part a
 textbook of mathematics, a Secondary Section may not explain any
@@ -174,7 +174,7 @@
 plus such following pages as are needed to hold, legibly, the material
 this License requires to appear in the title page.  For works in
 formats which do not have any title page as such, &ldquo;Title Page&rdquo; 
means
-the text near the most prominent appearance of the work's title,
+the text near the most prominent appearance of the work&rsquo;s title,
 preceding the beginning of the body of the text.
 </p>
 </li><li>
@@ -197,7 +197,7 @@
 COPYING IN QUANTITY
 
 <p>If you publish printed copies of the Document numbering more than 100,
-and the Document's license notice requires Cover Texts, you must enclose
+and the Document&rsquo;s license notice requires Cover Texts, you must enclose
 the copies in covers that carry, clearly and legibly, all these Cover
 Texts: Front-Cover Texts on the front cover, and Back-Cover Texts on
 the back cover.  Both covers must also clearly and legibly identify
@@ -273,7 +273,7 @@
 
 </li><li>
 Preserve in that license notice the full lists of Invariant Sections
-and required Cover Texts given in the Document's license notice.
+and required Cover Texts given in the Document&rsquo;s license notice.
 
 </li><li>
 Include an unaltered copy of this License.
@@ -298,7 +298,7 @@
 
 </li><li>
 In any section entitled &ldquo;Acknowledgments&rdquo; or 
&ldquo;Dedications&rdquo;,
-preserve the section's title, and preserve in the section all the
+preserve the section&rsquo;s title, and preserve in the section all the
 substance and tone of each of the contributor acknowledgments
 and/or dedications given therein.
 
@@ -320,7 +320,7 @@
 appendices that qualify as Secondary Sections and contain no material
 copied from the Document, you may at your option designate some or all
 of these sections as invariant.  To do this, add their titles to the
-list of Invariant Sections in the Modified Version's license notice.
+list of Invariant Sections in the Modified Version&rsquo;s license notice.
 These titles must be distinct from any other section titles.
 </p>
 <p>You may add a section entitled &ldquo;Endorsements&rdquo;, provided it 
contains
@@ -396,7 +396,7 @@
 </p>
 <p>If the Cover Text requirement of section 3 is applicable to these
 copies of the Document, then if the Document is less than one quarter
-of the entire aggregate, the Document's Cover Texts may be placed on
+of the entire aggregate, the Document&rsquo;s Cover Texts may be placed on
 covers that surround only the Document within the aggregate.
 Otherwise they must appear on covers around the whole aggregate.
 </p>

Index: Tests/nodes_texinfo_res/GNU-Sample-Texts.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/GNU-Sample-Texts.html,v
retrieving revision 1.74
retrieving revision 1.75
diff -u -b -r1.74 -r1.75
--- Tests/nodes_texinfo_res/GNU-Sample-Texts.html       5 Feb 2007 15:30:24 
-0000       1.74
+++ Tests/nodes_texinfo_res/GNU-Sample-Texts.html       3 Oct 2007 09:34:43 
-0000       1.75
@@ -86,10 +86,10 @@
 used in GNU manuals.
 </p>
 <p>As well as the legal texts, it also serves as a practical example of how
-many elements in a GNU system can affect the manual.  If you're not
-familiar with all these different elements, don't worry.  They're not
+many elements in a GNU system can affect the manual.  If you&rsquo;re not
+familiar with all these different elements, don&rsquo;t worry.  They&rsquo;re 
not
 required and a perfectly good manual can be written without them.
-They're included here nonetheless because many manuals do (or could)
+They&rsquo;re included here nonetheless because many manuals do (or could)
 benefit from them.
 </p>
 <p>See section <a href="Short-Sample.html#SEC12">A Short Sample Texinfo 
File</a>, for a minimal example of a Texinfo file.
@@ -103,7 +103,7 @@
 <a name="IDX446"></a>
 <a name="IDX447"></a>
 <a name="IDX448"></a>
-The &lsquo;<samp>Id: texinfo.txi,v 1.2 2003/02/24 18:17:06 pertusus Exp 
$</samp>&rsquo; comment is for CVS (see <a 
href="../cvs/index.html#Top">(cvs)Top</a> section `Overview' in 
<cite>Concurrent Versions System</cite>) or RCS (see rcsintro(1)) version 
control
+The &lsquo;<samp>Id: texinfo.txi,v 1.2 2003/02/24 18:17:06 pertusus Exp 
$</samp>&rsquo; comment is for CVS (see <a 
href="../cvs/index.html#Top">(cvs)Top</a> section &lsquo;Overview&rsquo; in 
<cite>Concurrent Versions System</cite>) or RCS (see rcsintro(1)) version 
control
 systems, which expand it into a string such as:
 <table><tr><td>&nbsp;</td><td><pre class="example">Id: texinfo.txi,v 1.2 
2003/02/24 18:17:06 pertusus Exp $
 </pre></td></tr></table>
@@ -112,8 +112,8 @@
 </li><li>
 <a name="IDX449"></a>
 The &lsquo;<tt>version.texi</tt>&rsquo; in the <code>@include</code> command 
is maintained
-automatically by Automake (see <a 
href="../automake/index.html#Top">(automake)Top</a> section `Introduction' in 
<cite>GNU Automake</cite>).  It sets the &lsquo;<samp>VERSION</samp>&rsquo; and 
&lsquo;<samp>UPDATED</samp>&rsquo; values used
-elsewhere.  If your distribution doesn't use Automake, you can mimic
+automatically by Automake (see <a 
href="../automake/index.html#Top">(automake)Top</a> section 
&lsquo;Introduction&rsquo; in <cite>GNU Automake</cite>).  It sets the 
&lsquo;<samp>VERSION</samp>&rsquo; and &lsquo;<samp>UPDATED</samp>&rsquo; 
values used
+elsewhere.  If your distribution doesn&rsquo;t use Automake, you can mimic
 these or equivalent settings.
 
 </li><li>
@@ -126,8 +126,8 @@
 category names.
 
 </li><li>
-The `Invoking' node is a GNU standard to help users find the basic
-information about command-line usage of a given program.  See <a 
href="../standards/Manual-Structure-Details.html#Manual-Structure-Details">(standards)Manual
 Structure Details</a> section `Manual Structure Details' in <cite>GNU Coding 
Standards</cite>.
+The &lsquo;Invoking&rsquo; node is a GNU standard to help users find the basic
+information about command-line usage of a given program.  See <a 
href="../standards/Manual-Structure-Details.html#Manual-Structure-Details">(standards)Manual
 Structure Details</a> section &lsquo;Manual Structure Details&rsquo; in 
<cite>GNU Coding Standards</cite>.
 
 </li><li>
 It is best to include the entire GNU Free Documentation License in a GNU
@@ -142,7 +142,7 @@
 </p>
 </li><li>
 If your manual has invariant sections (again, see the license itself for
-details), then don't forget to include them.
+details), then don&rsquo;t forget to include them.
 </li></ul>
 
 <p>Here is the sample document:

Index: Tests/nodes_texinfo_res/Hardcopy.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/Hardcopy.html,v
retrieving revision 1.19
retrieving revision 1.20
diff -u -b -r1.19 -r1.20
--- Tests/nodes_texinfo_res/Hardcopy.html       5 Feb 2007 15:30:24 -0000       
1.19
+++ Tests/nodes_texinfo_res/Hardcopy.html       3 Oct 2007 09:34:43 -0000       
1.20
@@ -107,7 +107,7 @@
 </td></tr>
 <tr><td align="left" valign="top"><a 
href="Texinfo-Mode-Printing.html#SEC250">19.6 Formatting and Printing in 
Texinfo Mode</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">       
How to format and print in Texinfo mode.
 </td></tr>
-<tr><td align="left" valign="top"><a 
href="Compile_002dCommand.html#SEC251">19.7 Using the Local Variables 
List</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">             
How to print using Emacs's compile command.
+<tr><td align="left" valign="top"><a 
href="Compile_002dCommand.html#SEC251">19.7 Using the Local Variables 
List</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">             
How to print using Emacs&rsquo;s compile command.
 </td></tr>
 <tr><td align="left" valign="top"><a 
href="Requirements-Summary.html#SEC252">19.8 TeX Formatting Requirements 
Summary</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">        TeX 
formatting requirements summary.
 </td></tr>

Index: Tests/nodes_texinfo_res/History.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/History.html,v
retrieving revision 1.20
retrieving revision 1.21
diff -u -b -r1.20 -r1.21
--- Tests/nodes_texinfo_res/History.html        5 Feb 2007 15:30:24 -0000       
1.20
+++ Tests/nodes_texinfo_res/History.html        3 Oct 2007 09:34:43 -0000       
1.21
@@ -109,7 +109,7 @@
 <a name="IDX27"></a>
 <a name="IDX28"></a>
 <a name="IDX29"></a>
-<p>A bit of history: in the 1970's at CMU, Brian Reid developed a program
+<p>A bit of history: in the 1970&rsquo;s at CMU, Brian Reid developed a program
 and format named Scribe to mark up documents for printing.  It used the
 <code>@</code> character to introduce commands, as Texinfo does.  Much more
 consequentially, it strived to describe document contents rather than

Index: Tests/nodes_texinfo_res/Images.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/Images.html,v
retrieving revision 1.24
retrieving revision 1.25
diff -u -b -r1.24 -r1.25
--- Tests/nodes_texinfo_res/Images.html 5 Feb 2007 15:30:24 -0000       1.24
+++ Tests/nodes_texinfo_res/Images.html 3 Oct 2007 09:34:43 -0000       1.25
@@ -98,7 +98,7 @@
 format).
 </li><li>
 <a name="IDX232"></a>
-PDFTeX reads &lsquo;<tt><var>filename</var>.pdf</tt>&rsquo; (Adobe's Portable 
Document Format).
+PDFTeX reads &lsquo;<tt><var>filename</var>.pdf</tt>&rsquo; (Adobe&rsquo;s 
Portable Document Format).
 </li><li>
 <code>makeinfo</code> uses &lsquo;<tt><var>filename</var>.txt</tt>&rsquo; 
verbatim for
 Info output (more or less as if it was an <code>@example</code>).

Index: Tests/nodes_texinfo_res/Include-File-Requirements.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/Include-File-Requirements.html,v
retrieving revision 1.18
retrieving revision 1.19
diff -u -b -r1.18 -r1.19
--- Tests/nodes_texinfo_res/Include-File-Requirements.html      5 Feb 2007 
15:30:24 -0000       1.18
+++ Tests/nodes_texinfo_res/Include-File-Requirements.html      3 Oct 2007 
09:34:43 -0000       1.19
@@ -97,8 +97,8 @@
 <code>@unnumbered</code> node.  Thus, normally, each included file contains
 one, and only one, chapter or equivalent-level node.
 </p>
-<p>The outer file should contain only <em>one</em> node, the `Top' node.  It
-should <em>not</em> contain any nodes besides the single `Top' node.  The
+<p>The outer file should contain only <em>one</em> node, the &lsquo;Top&rsquo; 
node.  It
+should <em>not</em> contain any nodes besides the single &lsquo;Top&rsquo; 
node.  The
 <code>texinfo-multiple-files-update</code> command will not process
 them.
 </p>

Index: Tests/nodes_texinfo_res/Include-Files-Evolution.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/Include-Files-Evolution.html,v
retrieving revision 1.19
retrieving revision 1.20
diff -u -b -r1.19 -r1.20
--- Tests/nodes_texinfo_res/Include-Files-Evolution.html        5 Feb 2007 
15:30:24 -0000       1.19
+++ Tests/nodes_texinfo_res/Include-Files-Evolution.html        3 Oct 2007 
09:34:43 -0000       1.20
@@ -95,7 +95,7 @@
 <p>Include files were designed primarily as a way to create a single,
 large printed manual out of several smaller Info files.  In a printed
 manual, all the references were within the same document, so TeX
-could automatically determine the references' page numbers.  The Info
+could automatically determine the references&rsquo; page numbers.  The Info
 formatting commands used include files only for creating joint
 indices; each of the individual Texinfo files had to be formatted for
 Info individually.  (Each, therefore, required its own

Index: Tests/nodes_texinfo_res/Indexing-Commands.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/Indexing-Commands.html,v
retrieving revision 1.23
retrieving revision 1.24
diff -u -b -r1.23 -r1.24
--- Tests/nodes_texinfo_res/Indexing-Commands.html      5 Feb 2007 15:30:24 
-0000       1.23
+++ Tests/nodes_texinfo_res/Indexing-Commands.html      3 Oct 2007 09:34:43 
-0000       1.24
@@ -110,10 +110,10 @@
 the index often looks better if the entries are not capitalized, but
 written just as they would appear in the middle of a sentence.
 (Capitalize proper names and acronyms that always call for upper case
-letters.)  This is the case convention we use in most GNU manuals'
+letters.)  This is the case convention we use in most GNU manuals&rsquo;
 indices.
 </p>
-<p>If you don't see how to make an entry terse yet clear, make it longer
+<p>If you don&rsquo;t see how to make an entry terse yet clear, make it longer
 and clear&mdash;not terse and confusing.  If many of the entries are several
 words long, the index may look better if you use a different convention:
 to capitalize the first word of each entry.  But do not capitalize a
@@ -179,7 +179,7 @@
 preprocessor macros.  You could put them in the function index along
 with actual functions, just by writing <code>@findex</code> commands for
 them; then, when you print the &ldquo;Function Index&rdquo; as an unnumbered
-chapter, you could give it the title `Function and Macro Index' and
+chapter, you could give it the title &lsquo;Function and Macro Index&rsquo; and
 all will be consistent for the reader.  Or you could put the macros in
 with the data types by writing <code>@tindex</code> commands for them, and
 give that index a suitable title so the reader will understand.

Index: Tests/nodes_texinfo_res/Info-Files.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/Info-Files.html,v
retrieving revision 1.23
retrieving revision 1.24
diff -u -b -r1.23 -r1.24
--- Tests/nodes_texinfo_res/Info-Files.html     5 Feb 2007 15:30:24 -0000       
1.23
+++ Tests/nodes_texinfo_res/Info-Files.html     3 Oct 2007 09:34:43 -0000       
1.24
@@ -96,7 +96,7 @@
 <p>See <a href="../info/index.html#Top">info: (info)Top</a>, for more 
information about using Info.
 </p>
 <p>Each node of an Info file may have any number of child nodes that
-describe subtopics of the node's topic.  The names of child
+describe subtopics of the node&rsquo;s topic.  The names of child
 nodes are listed in a <em>menu</em> within the parent node; this
 allows you to use certain Info commands to move to one of the child
 nodes.  Generally, an Info file is organized like a book.  If a node
@@ -105,25 +105,25 @@
 of subsections.
 </p>
 <p>All the children of any one parent are linked together in a
-bidirectional chain of `Next' and `Previous' pointers.  The `Next'
-pointer provides a link to the next section, and the `Previous' pointer
+bidirectional chain of &lsquo;Next&rsquo; and &lsquo;Previous&rsquo; pointers. 
 The &lsquo;Next&rsquo;
+pointer provides a link to the next section, and the &lsquo;Previous&rsquo; 
pointer
 provides a link to the previous section.  This means that all the nodes
 that are at the level of sections within a chapter are linked together.
 Normally the order in this chain is the same as the order of the
-children in the parent's menu.  Each child node records the parent node
-name as its `Up' pointer.  The last child has no `Next' pointer, and the
-first child has the parent both as its `Previous' and as its `Up'
+children in the parent&rsquo;s menu.  Each child node records the parent node
+name as its &lsquo;Up&rsquo; pointer.  The last child has no 
&lsquo;Next&rsquo; pointer, and the
+first child has the parent both as its &lsquo;Previous&rsquo; and as its 
&lsquo;Up&rsquo;
 pointer.<a name="DOCF2" href="texinfo_fot.html#FOOT2">(2)</a>
 </p>
 <p>The book-like structuring of an Info file into nodes that correspond
 to chapters, sections, and the like is a matter of convention, not a
-requirement.  The `Up', `Previous', and `Next' pointers of a node can
+requirement.  The &lsquo;Up&rsquo;, &lsquo;Previous&rsquo;, and 
&lsquo;Next&rsquo; pointers of a node can
 point to any other nodes, and a menu can contain any other nodes.
 Thus, the node structure can be any directed graph.  But it is usually
 more comprehensible to follow a structure that corresponds to the
 structure of chapters and sections in a printed book or report.
 </p>
-<p>In addition to menus and to `Next', `Previous', and `Up' pointers, Info
+<p>In addition to menus and to &lsquo;Next&rsquo;, &lsquo;Previous&rsquo;, and 
&lsquo;Up&rsquo; pointers, Info
 provides pointers of another kind, called references, that can be
 sprinkled throughout the text.  This is usually the best way to
 represent links that do not fit a hierarchical structure.
@@ -136,14 +136,14 @@
 printed output.
 </p>
 <p>Generally, you enter an Info file through a node that by convention is
-named `Top'.  This node normally contains just a brief summary of the
-file's purpose, and a large menu through which the rest of the file is
+named &lsquo;Top&rsquo;.  This node normally contains just a brief summary of 
the
+file&rsquo;s purpose, and a large menu through which the rest of the file is
 reached.  From this node, you can either traverse the file
 systematically by going from node to node, or you can go to a specific
 node listed in the main menu, or you can search the index menus and then
 go directly to the node that has the information you want.  Alternatively,
 with the standalone Info program, you can specify specific menu items on
-the command line (see <a href="../info/index.html#Top">(info)Top</a> section 
`Top' in <cite>Info</cite>).
+the command line (see <a href="../info/index.html#Top">(info)Top</a> section 
&lsquo;Top&rsquo; in <cite>Info</cite>).
 </p>
 <p>If you want to read through an Info file in sequence, as if it were a
 printed manual, you can hit &lt;SPC&gt; repeatedly, or you get the whole
@@ -151,7 +151,7 @@
 </p>
 <p>The &lsquo;<tt>dir</tt>&rsquo; file in the &lsquo;<tt>info</tt>&rsquo; 
directory serves as the
 departure point for the whole Info system.  From it, you can reach the
-`Top' nodes of each of the documents in a complete Info system.
+&lsquo;Top&rsquo; nodes of each of the documents in a complete Info system.
 </p>
 <a name="IDX12"></a>
 <p>If you wish to refer to an Info file in a URI, you can use the
@@ -162,7 +162,7 @@
 info://localhost/usr/info/emacs#Dissociated%20Press
 </pre></td></tr></table>
 
-<p>The <code>info</code> program itself does not follow URI's of any kind.
+<p>The <code>info</code> program itself does not follow URI&rsquo;s of any 
kind.
 </p>
 
 <hr size="1">

Index: Tests/nodes_texinfo_res/Inserting-Accents.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/Inserting-Accents.html,v
retrieving revision 1.19
retrieving revision 1.20
diff -u -b -r1.19 -r1.20
--- Tests/nodes_texinfo_res/Inserting-Accents.html      5 Feb 2007 15:30:24 
-0000       1.19
+++ Tests/nodes_texinfo_res/Inserting-Accents.html      3 Oct 2007 09:34:43 
-0000       1.20
@@ -124,7 +124,7 @@
 </p></td></tr>
 <tr><td><p> <tt>@&quot;o</tt>              </p></td><td><p> &ouml;            
</p></td><td><p> umlaut accent
 </p></td></tr>
-<tr><td><p> <tt>@'o</tt>              </p></td><td><p> &oacute;            
</p></td><td><p> acute accent
+<tr><td><p> <tt>@&rsquo;o</tt>              </p></td><td><p> &oacute;          
  </p></td><td><p> acute accent
 </p></td></tr>
 <tr><td><p> <tt>@,{c}</tt>          </p></td><td><p> &ccedil;          
</p></td><td><p> cedilla accent
 </p></td></tr>
@@ -132,7 +132,7 @@
 </p></td></tr>
 <tr><td><p> <tt>@^o</tt>              </p></td><td><p> &ocirc;            
</p></td><td><p> circumflex accent
 </p></td></tr>
-<tr><td><p> <tt>@`o</tt>              </p></td><td><p> &ograve;            
</p></td><td><p> grave accent
+<tr><td><p> <tt>@&lsquo;o</tt>              </p></td><td><p> &ograve;          
  </p></td><td><p> grave accent
 </p></td></tr>
 <tr><td><p> <tt>@~o</tt>              </p></td><td><p> &otilde;            
</p></td><td><p> tilde accent
 </p></td></tr>

Index: Tests/nodes_texinfo_res/Inserting-Space.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/Inserting-Space.html,v
retrieving revision 1.19
retrieving revision 1.20
diff -u -b -r1.19 -r1.20
--- Tests/nodes_texinfo_res/Inserting-Space.html        5 Feb 2007 15:30:24 
-0000       1.19
+++ Tests/nodes_texinfo_res/Inserting-Space.html        3 Oct 2007 09:34:43 
-0000       1.20
@@ -85,7 +85,7 @@
 kinds within and after sentences.
 </p>
 <table class="menu" border="0" cellspacing="0">
-<tr><td align="left" valign="top"><a 
href="Not-Ending-a-Sentence.html#SEC179">13.2.1 Not Ending a 
Sentence</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">       
Sometimes a . doesn't end a sentence.
+<tr><td align="left" valign="top"><a 
href="Not-Ending-a-Sentence.html#SEC179">13.2.1 Not Ending a 
Sentence</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">       
Sometimes a . doesn&rsquo;t end a sentence.
 </td></tr>
 <tr><td align="left" valign="top"><a 
href="Ending-a-Sentence.html#SEC180">13.2.2 Ending a 
Sentence</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">           
Sometimes it does.
 </td></tr>

Index: Tests/nodes_texinfo_res/Inserting.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/Inserting.html,v
retrieving revision 1.25
retrieving revision 1.26
diff -u -b -r1.25 -r1.26
--- Tests/nodes_texinfo_res/Inserting.html      5 Feb 2007 15:30:24 -0000       
1.25
+++ Tests/nodes_texinfo_res/Inserting.html      3 Oct 2007 09:34:43 -0000       
1.26
@@ -130,8 +130,8 @@
 <dt> <kbd>M-x address@hidden</kbd></dt>
 <dd><a name="IDX37"></a>
 <p>Insert <code>@node</code> and a comment line
-listing the sequence for the `Next',
-`Previous', and `Up' nodes.
+listing the sequence for the &lsquo;Next&rsquo;,
+&lsquo;Previous&rsquo;, and &lsquo;Up&rsquo; nodes.
 Leave point after the <code>@node</code>.
 </p>
 </dd>
@@ -209,7 +209,7 @@
 <a name="IDX47"></a>
 <p><kbd>C-c C-c C-d</kbd> (<code>texinfo-start-menu-description</code>) is an 
insert
 command that works differently from the other insert commands.  It
-inserts a node's section or chapter title in the space for the
+inserts a node&rsquo;s section or chapter title in the space for the
 description in a menu entry line.  (A menu entry has three parts, the
 entry name, the node name, and the description.  Only the node name is
 required, but a description helps explain what the node is about.

Index: Tests/nodes_texinfo_res/Installing-Dir-Entries.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/Installing-Dir-Entries.html,v
retrieving revision 1.23
retrieving revision 1.24
diff -u -b -r1.23 -r1.24
--- Tests/nodes_texinfo_res/Installing-Dir-Entries.html 5 Feb 2007 15:30:24 
-0000       1.23
+++ Tests/nodes_texinfo_res/Installing-Dir-Entries.html 3 Oct 2007 09:34:43 
-0000       1.24
@@ -104,7 +104,7 @@
 @end direntry
 </pre></td></tr></table>
 
-<p>Here's what this produces in the Info file:
+<p>Here&rsquo;s what this produces in the Info file:
 </p>
 <table><tr><td>&nbsp;</td><td><pre class="smallexample">INFO-DIR-SECTION 
Texinfo documentation system
 START-INFO-DIR-ENTRY
@@ -123,7 +123,7 @@
 will not notice them.
 </p>
 <p>If you use <code>@dircategory</code> more than once in the Texinfo source,
-each usage specifies the `current' category; any subsequent
+each usage specifies the &lsquo;current&rsquo; category; any subsequent
 <code>@direntry</code> commands will add to that category.  
 </p>
 <p>Here are some recommended <code>@dircategory</code> categories:
@@ -137,8 +137,8 @@
 Individual utilities
 </pre></td></tr></table>
 
-<p>The idea is to include the `Invoking' node for every program installed
-by a package under `Individual utilities', and an entry for the manual
+<p>The idea is to include the &lsquo;Invoking&rsquo; node for every program 
installed
+by a package under &lsquo;Individual utilities&rsquo;, and an entry for the 
manual
 as a whole in the appropriate other category.
 </p>
 

Index: Tests/nodes_texinfo_res/Invoking-install_002dinfo.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/Invoking-install_002dinfo.html,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -b -r1.11 -r1.12
--- Tests/nodes_texinfo_res/Invoking-install_002dinfo.html      5 Feb 2007 
15:30:24 -0000       1.11
+++ Tests/nodes_texinfo_res/Invoking-install_002dinfo.html      3 Oct 2007 
09:34:44 -0000       1.12
@@ -84,7 +84,7 @@
 
 <p><code>install-info</code> inserts menu entries from an Info file into the
 top-level &lsquo;<tt>dir</tt>&rsquo; file in the Info system (see the previous 
sections
-for an explanation of how the &lsquo;<tt>dir</tt>&rsquo; file works).  It's 
most often
+for an explanation of how the &lsquo;<tt>dir</tt>&rsquo; file works).  
It&rsquo;s most often
 run as part of software installation, or when constructing a 
&lsquo;<tt>dir</tt>&rsquo; file
 for all manuals on a system.  Synopsis:
 </p>
@@ -102,7 +102,7 @@
 </p>
 <a name="IDX421"></a>
 <a name="IDX422"></a>
-<p>If any input file is compressed with <code>gzip</code> (see <a 
href="../gzip/Invoking-gzip.html#Invoking-gzip">(gzip)Invoking gzip</a> section 
`Invoking gzip' in <cite>Gzip</cite>), <code>install-info</code> automatically 
uncompresses it
+<p>If any input file is compressed with <code>gzip</code> (see <a 
href="../gzip/Invoking-gzip.html#Invoking-gzip">(gzip)Invoking gzip</a> section 
&lsquo;Invoking gzip&rsquo; in <cite>Gzip</cite>), <code>install-info</code> 
automatically uncompresses it
 for reading.  And if <var>dir-file</var> is compressed, 
<code>install-info</code>
 also automatically leaves it compressed after writing any changes.
 If <var>dir-file</var> itself does not exist, <code>install-info</code> tries 
to
@@ -115,7 +115,7 @@
 <dd><a name="IDX423"></a>
 <p>Delete the entries in <var>info-file</var> from <var>dir-file</var>.  The 
file
 name in the entry in <var>dir-file</var> must be <var>info-file</var> (except 
for
-an optional &lsquo;<samp>.info</samp>&rsquo; in either one).  Don't insert any 
new entries.
+an optional &lsquo;<samp>.info</samp>&rsquo; in either one).  Don&rsquo;t 
insert any new entries.
 </p>
 </dd>
 <dt> <code>--dir-file=<var>name</var></code></dt>
@@ -133,7 +133,7 @@
 <p>Insert <var>text</var> as an Info directory entry; <var>text</var> should 
have the
 form of an Info menu item line plus zero or more extra lines starting
 with whitespace.  If you specify more than one entry, they are all
-added.  If you don't specify any entries, they are determined from
+added.  If you don&rsquo;t specify any entries, they are determined from
 information in the Info file itself.
 </p>
 </dd>
@@ -183,9 +183,9 @@
 <dt> <code>-s <var>sec</var></code></dt>
 <dd><a name="IDX438"></a>
 <a name="IDX439"></a>
-<p>Put this file's entries in section <var>sec</var> of the directory.  If you
+<p>Put this file&rsquo;s entries in section <var>sec</var> of the directory.  
If you
 specify more than one section, all the entries are added in each of the
-sections.  If you don't specify any sections, they are determined from
+sections.  If you don&rsquo;t specify any sections, they are determined from
 information in the Info file itself.
 </p>
 </dd>

Index: Tests/nodes_texinfo_res/Line-Breaks.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/Line-Breaks.html,v
retrieving revision 1.20
retrieving revision 1.21
diff -u -b -r1.20 -r1.21
--- Tests/nodes_texinfo_res/Line-Breaks.html    5 Feb 2007 15:30:24 -0000       
1.20
+++ Tests/nodes_texinfo_res/Line-Breaks.html    3 Oct 2007 09:34:44 -0000       
1.21
@@ -99,7 +99,7 @@
 <p>(Note that the space after the first <code>@*</code> command is faithfully
 carried down to the next line.)
 </p>
-<p>The <code>@*</code> command is often used in a file's copyright page:
+<p>The <code>@*</code> command is often used in a file&rsquo;s copyright page:
 </p>
 <table><tr><td>&nbsp;</td><td><pre class="example">This is edition 2.0 of the 
Texinfo documentation,@*
 and is for &hellip;

Index: Tests/nodes_texinfo_res/Macro-Details.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/Macro-Details.html,v
retrieving revision 1.23
retrieving revision 1.24
diff -u -b -r1.23 -r1.24
--- Tests/nodes_texinfo_res/Macro-Details.html  5 Feb 2007 15:30:24 -0000       
1.23
+++ Tests/nodes_texinfo_res/Macro-Details.html  3 Oct 2007 09:34:44 -0000       
1.24
@@ -95,7 +95,7 @@
 conditional, cannot be invoked in the middle of a line.
 
 </li><li>
-Commas in macro arguments, even if escaped by a backslash, don't
+Commas in macro arguments, even if escaped by a backslash, don&rsquo;t
 always work.
 
 </li><li>

Index: Tests/nodes_texinfo_res/Menu-Parts.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/Menu-Parts.html,v
retrieving revision 1.22
retrieving revision 1.23
diff -u -b -r1.22 -r1.23
--- Tests/nodes_texinfo_res/Menu-Parts.html     5 Feb 2007 15:30:24 -0000       
1.22
+++ Tests/nodes_texinfo_res/Menu-Parts.html     3 Oct 2007 09:34:44 -0000       
1.23
@@ -112,7 +112,7 @@
 complements the node name rather than repeats it.  The description,
 which is optional, can spread over two or more lines; if it does, some
 authors prefer to indent the second line while others prefer to align it
-with the first (and all others).  It's up to you.
+with the first (and all others).  It&rsquo;s up to you.
 </p>
 
 <hr size="1">

Index: Tests/nodes_texinfo_res/Minimum.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/Minimum.html,v
retrieving revision 1.24
retrieving revision 1.25
diff -u -b -r1.24 -r1.25
--- Tests/nodes_texinfo_res/Minimum.html        5 Feb 2007 15:30:24 -0000       
1.24
+++ Tests/nodes_texinfo_res/Minimum.html        3 Oct 2007 09:34:44 -0000       
1.25
@@ -103,7 +103,7 @@
 </pre></td></tr></table>
 
 <a name="IDX19"></a>
-<p>Here's an explanation:
+<p>Here&rsquo;s an explanation:
 </p>
 <ul>
 <li>
@@ -121,7 +121,7 @@
 The <code>@settitle</code> line specifies a title for the page headers (or
 footers) of the printed manual, and the default document description for
 the &lsquo;<samp>&lt;head&gt;</samp>&rsquo; in HTML format.  Strictly 
speaking, <code>@settitle</code>
-is optional&mdash;if you don't mind your document being titled `Untitled'.
+is optional&mdash;if you don&rsquo;t mind your document being titled 
&lsquo;Untitled&rsquo;.
 
 </li><li>
 The <code>@bye</code> line at the end of the file on a line of its own tells

Index: Tests/nodes_texinfo_res/Multitable-Column-Widths.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/Multitable-Column-Widths.html,v
retrieving revision 1.21
retrieving revision 1.22
diff -u -b -r1.21 -r1.22
--- Tests/nodes_texinfo_res/Multitable-Column-Widths.html       5 Feb 2007 
15:30:24 -0000       1.21
+++ Tests/nodes_texinfo_res/Multitable-Column-Widths.html       3 Oct 2007 
09:34:44 -0000       1.22
@@ -109,8 +109,8 @@
 <table><tr><td>&nbsp;</td><td><pre class="example">@multitable {some text for 
column one} {for column two}
 </pre></td></tr></table>
 
-<p>The first column will then have the width of the typeset `some text for
-column one', and the second column the width of `for column two'.
+<p>The first column will then have the width of the typeset &lsquo;some text 
for
+column one&rsquo;, and the second column the width of &lsquo;for column 
two&rsquo;.
 </p>
 <p>The prototype entries need not appear in the table itself.
 </p>

Index: Tests/nodes_texinfo_res/Multitable-Rows.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/Multitable-Rows.html,v
retrieving revision 1.20
retrieving revision 1.21
diff -u -b -r1.20 -r1.21
--- Tests/nodes_texinfo_res/Multitable-Rows.html        5 Feb 2007 15:30:24 
-0000       1.20
+++ Tests/nodes_texinfo_res/Multitable-Rows.html        3 Oct 2007 09:34:44 
-0000       1.21
@@ -88,7 +88,7 @@
 input lines in your source file as necessary.
 </p>
 <p>Here is a complete example of a multi-column table (the text is from
-<cite>The GNU Emacs Manual</cite>, see <a 
href="../emacs/Split-Window.html#Split-Window">(emacs)Split Window</a> section 
`Splitting Windows' in <cite>The GNU Emacs Manual</cite>):
+<cite>The GNU Emacs Manual</cite>, see <a 
href="../emacs/Split-Window.html#Split-Window">(emacs)Split Window</a> section 
&lsquo;Splitting Windows&rsquo; in <cite>The GNU Emacs Manual</cite>):
 </p>
 <table><tr><td>&nbsp;</td><td><pre class="example">@multitable 
@columnfractions .15 .45 .4
 @item Key @tab Command @tab Description

Index: Tests/nodes_texinfo_res/Node-Menu-Illustration.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/Node-Menu-Illustration.html,v
retrieving revision 1.21
retrieving revision 1.22
diff -u -b -r1.21 -r1.22
--- Tests/nodes_texinfo_res/Node-Menu-Illustration.html 5 Feb 2007 15:30:24 
-0000       1.21
+++ Tests/nodes_texinfo_res/Node-Menu-Illustration.html 3 Oct 2007 09:34:44 
-0000       1.22
@@ -87,7 +87,7 @@
 <p>The &ldquo;root&rdquo; is at the top of the diagram and the 
&ldquo;leaves&rdquo; are at the
 bottom.  This is how such a diagram is drawn conventionally; it
 illustrates an upside-down tree.  For this reason, the root node is
-called the `Top' node, and `Up' node pointers carry you closer to the
+called the &lsquo;Top&rsquo; node, and &lsquo;Up&rsquo; node pointers carry 
you closer to the
 root.
 </p>
 <table><tr><td>&nbsp;</td><td><pre class="example">                          
Top
@@ -109,20 +109,20 @@
 </pre></td></tr></table>
 
 <p>This <code>@node</code> line says that the name of this node is 
&ldquo;Chapter
-2&rdquo;, the name of the `Next' node is &ldquo;Chapter 3&rdquo;, the name of 
the
-`Previous' node is &ldquo;Chapter 1&rdquo;, and the name of the `Up' node is
+2&rdquo;, the name of the &lsquo;Next&rsquo; node is &ldquo;Chapter 3&rdquo;, 
the name of the
+&lsquo;Previous&rsquo; node is &ldquo;Chapter 1&rdquo;, and the name of the 
&lsquo;Up&rsquo; node is
 &ldquo;Top&rdquo;.  You can omit writing out these node names if your document 
is
 hierarchically organized (see section <a 
href="makeinfo-Pointer-Creation.html#SEC95">Creating Pointers with 
<code>makeinfo</code></a>), but the
 pointer relationships still obtain.
 </p>
-<blockquote><p><strong>Please Note:</strong> `Next' refers to the next node at 
the same
+<blockquote><p><strong>Please Note:</strong> &lsquo;Next&rsquo; refers to the 
next node at the same
 hierarchical level in the manual, not necessarily to the next node
 within the Texinfo file.  In the Texinfo file, the subsequent node may
 be at a lower level&mdash;a section-level node most often follows a
-chapter-level node, for example.  `Next' and `Previous' refer to nodes
-at the <em>same</em> hierarchical level.  (The `Top' node contains the
-exception to this rule.  Since the `Top' node is the only node at that
-level, `Next' refers to the first following node, which is almost always
+chapter-level node, for example.  &lsquo;Next&rsquo; and 
&lsquo;Previous&rsquo; refer to nodes
+at the <em>same</em> hierarchical level.  (The &lsquo;Top&rsquo; node contains 
the
+exception to this rule.  Since the &lsquo;Top&rsquo; node is the only node at 
that
+level, &lsquo;Next&rsquo; refers to the first following node, which is almost 
always
 a chapter or chapter-level node.)
 </p></blockquote>
 
@@ -142,12 +142,12 @@
     @comment  node-name, next,      previous,  up
 </pre></td></tr></table>
 
-<p>In Info format, the `Next' and `Previous' pointers of a node usually
+<p>In Info format, the &lsquo;Next&rsquo; and &lsquo;Previous&rsquo; pointers 
of a node usually
 lead to other nodes at the same level&mdash;from chapter to chapter or from
-section to section (sometimes, as shown, the `Previous' pointer points
-up); an `Up' pointer usually leads to a node at the level above (closer
-to the `Top' node); and a `Menu' leads to nodes at a level below (closer
-to `leaves').  (A cross reference can point to a node at any level;
+section to section (sometimes, as shown, the &lsquo;Previous&rsquo; pointer 
points
+up); an &lsquo;Up&rsquo; pointer usually leads to a node at the level above 
(closer
+to the &lsquo;Top&rsquo; node); and a &lsquo;Menu&rsquo; leads to nodes at a 
level below (closer
+to &lsquo;leaves&rsquo;).  (A cross reference can point to a node at any level;
 see <a href="Cross-References.html#SEC104">Cross References</a>.)
 </p>
 <p>Usually, an <code>@node</code> command and a chapter structuring command are

Index: Tests/nodes_texinfo_res/Node-Names.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/Node-Names.html,v
retrieving revision 1.21
retrieving revision 1.22
diff -u -b -r1.21 -r1.22
--- Tests/nodes_texinfo_res/Node-Names.html     5 Feb 2007 15:30:24 -0000       
1.21
+++ Tests/nodes_texinfo_res/Node-Names.html     3 Oct 2007 09:34:44 -0000       
1.22
@@ -84,20 +84,20 @@
 <p>The name of a node identifies the node.  The pointers enable
 you to reach other nodes and consist of the names of those nodes.
 </p>
-<p>Normally, a node's `Up' pointer contains the name of the node whose menu
-mentions that node.  The node's `Next' pointer contains the name of the
-node that follows that node in that menu and its `Previous' pointer
+<p>Normally, a node&rsquo;s &lsquo;Up&rsquo; pointer contains the name of the 
node whose menu
+mentions that node.  The node&rsquo;s &lsquo;Next&rsquo; pointer contains the 
name of the
+node that follows that node in that menu and its &lsquo;Previous&rsquo; pointer
 contains the name of the node that precedes it in that menu.  When a
-node's `Previous' node is the same as its `Up' node, both node pointers
+node&rsquo;s &lsquo;Previous&rsquo; node is the same as its &lsquo;Up&rsquo; 
node, both node pointers
 name the same node.
 </p>
-<p>Usually, the first node of a Texinfo file is the `Top' node, and its
-`Up' and `Previous' pointers point to the &lsquo;<tt>dir</tt>&rsquo; file, 
which
+<p>Usually, the first node of a Texinfo file is the &lsquo;Top&rsquo; node, 
and its
+&lsquo;Up&rsquo; and &lsquo;Previous&rsquo; pointers point to the 
&lsquo;<tt>dir</tt>&rsquo; file, which
 contains the main menu for all of Info.
 </p>
-<p>The `Top' node itself contains the main or master menu for the manual.
+<p>The &lsquo;Top&rsquo; node itself contains the main or master menu for the 
manual.
 Also, it is helpful to include a brief description of the manual in the
-`Top' node.  See section <a href="First-Node.html#SEC93">The First Node</a>, 
for information on how to write the
+&lsquo;Top&rsquo; node.  See section <a href="First-Node.html#SEC93">The First 
Node</a>, for information on how to write the
 first node of a Texinfo file.
 </p>
 <p>Even when you explicitly specify all pointers, that does not mean you

Index: Tests/nodes_texinfo_res/Other-Info-Directories.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/Other-Info-Directories.html,v
retrieving revision 1.25
retrieving revision 1.26
diff -u -b -r1.25 -r1.26
--- Tests/nodes_texinfo_res/Other-Info-Directories.html 5 Feb 2007 15:30:24 
-0000       1.25
+++ Tests/nodes_texinfo_res/Other-Info-Directories.html 3 Oct 2007 09:34:44 
-0000       1.26
@@ -131,7 +131,7 @@
 &lsquo;<tt>/home/bob/info/info-test</tt>&rsquo; file as a menu entry in the
 &lsquo;<tt>/home/bob/info/dir</tt>&rsquo; file.  Emacs does the merging only 
when
 <kbd>M-x info</kbd> is first run, so if you want to set
-<code>Info-directory-list</code> in an Emacs session where you've already run
+<code>Info-directory-list</code> in an Emacs session where you&rsquo;ve 
already run
 <code>info</code>, you must <code>(setq Info-dir-contents nil)</code> to force 
Emacs
 to recompose the &lsquo;<tt>dir</tt>&rsquo; file.
 </p>
@@ -172,7 +172,7 @@
 </li></ul>
 
 <p>The &lsquo;<samp>.</samp>&rsquo; indicates the current directory as usual.  
Emacs uses the
-<code>INFOPATH</code> environment variable to initialize the value of Emacs's
+<code>INFOPATH</code> environment variable to initialize the value of 
Emacs&rsquo;s
 own <code>Info-directory-list</code> variable.  The stand-alone Info reader
 merges any files named &lsquo;<tt>dir</tt>&rsquo; in any directory listed in 
the
 <code>INFOPATH</code> variable into a single menu presented to you in the node
@@ -194,7 +194,7 @@
 </p>
 <a name="IDX417"></a>
 <p>When you create your own &lsquo;<tt>dir</tt>&rsquo; file for use with
-<code>Info-directory-list</code> or <code>INFOPATH</code>, it's easiest to 
start by
+<code>Info-directory-list</code> or <code>INFOPATH</code>, it&rsquo;s easiest 
to start by
 copying an existing &lsquo;<tt>dir</tt>&rsquo; file and replace all the text 
after the
 &lsquo;<samp>* Menu:</samp>&rsquo; with your desired entries.  That way, the 
punctuation and
 special CTRL-_ characters that Info needs will be present.

Index: Tests/nodes_texinfo_res/Other-Info-Files.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/Other-Info-Files.html,v
retrieving revision 1.22
retrieving revision 1.23
diff -u -b -r1.22 -r1.23
--- Tests/nodes_texinfo_res/Other-Info-Files.html       5 Feb 2007 15:30:24 
-0000       1.22
+++ Tests/nodes_texinfo_res/Other-Info-Files.html       3 Oct 2007 09:34:44 
-0000       1.23
@@ -108,10 +108,10 @@
 </pre></td></tr></table>
 
 <p>If you do not list the node name, but only name the file, then Info
-presumes that you are referring to the `Top' node.
+presumes that you are referring to the &lsquo;Top&rsquo; node.
 </p>
 <p>The &lsquo;<tt>dir</tt>&rsquo; file that contains the main menu for Info 
has menu
-entries that list only file names.  These take you directly to the `Top'
+entries that list only file names.  These take you directly to the 
&lsquo;Top&rsquo;
 nodes of each Info document.  (See section <a 
href="Installing-an-Info-File.html#SEC271">Installing an Info File</a>.)
 </p>
 <p>For example:

Index: Tests/nodes_texinfo_res/Other-Updating-Commands.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/Other-Updating-Commands.html,v
retrieving revision 1.22
retrieving revision 1.23
diff -u -b -r1.22 -r1.23
--- Tests/nodes_texinfo_res/Other-Updating-Commands.html        5 Feb 2007 
15:30:24 -0000       1.22
+++ Tests/nodes_texinfo_res/Other-Updating-Commands.html        3 Oct 2007 
09:34:44 -0000       1.23
@@ -116,7 +116,7 @@
 <p>Update nodes and menus in a document built from several separate files.
 With <kbd>C-u</kbd> as a prefix argument, create and insert a master menu in
 the outer file.  With a numeric prefix argument, such as <kbd>C-u 2</kbd>, 
first
-update all the menus and all the `Next', `Previous', and `Up' pointers
+update all the menus and all the &lsquo;Next&rsquo;, &lsquo;Previous&rsquo;, 
and &lsquo;Up&rsquo; pointers
 of all the included files before creating and inserting a master menu in
 the outer file.  The <code>texinfo-multiple-files-update</code> command is
 described in the appendix on <code>@include</code> files.
@@ -137,8 +137,8 @@
 <dt> <kbd>M-x texinfo-sequential-node-update</kbd></dt>
 <dd><a name="IDX60"></a>
 <p>Insert the names of the nodes immediately following and preceding the
-current node as the `Next' or `Previous' pointers regardless of those
-nodes' hierarchical level.  This means that the `Next' node of a
+current node as the &lsquo;Next&rsquo; or &lsquo;Previous&rsquo; pointers 
regardless of those
+nodes&rsquo; hierarchical level.  This means that the &lsquo;Next&rsquo; node 
of a
 subsection may well be the next chapter.  Sequentially ordered nodes are
 useful for novels and other documents that you read through
 sequentially.  (However, in Info, the <kbd>g *</kbd> command lets

Index: Tests/nodes_texinfo_res/Overfull-hboxes.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/Overfull-hboxes.html,v
retrieving revision 1.22
retrieving revision 1.23
diff -u -b -r1.22 -r1.23
--- Tests/nodes_texinfo_res/Overfull-hboxes.html        5 Feb 2007 15:30:24 
-0000       1.22
+++ Tests/nodes_texinfo_res/Overfull-hboxes.html        3 Oct 2007 09:34:44 
-0000       1.23
@@ -107,7 +107,7 @@
 </p>
 <p>If you have many overfull boxes and/or an antipathy to rewriting, you
 can coerce TeX into greatly increasing the allowable interword
-spacing, thus (if you're lucky) avoiding many of the bad line breaks,
+spacing, thus (if you&rsquo;re lucky) avoiding many of the bad line breaks,
 like this:
 </p>
 <a name="IDX344"></a>

Index: Tests/nodes_texinfo_res/PDF-Output.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/PDF-Output.html,v
retrieving revision 1.21
retrieving revision 1.22
diff -u -b -r1.21 -r1.22
--- Tests/nodes_texinfo_res/PDF-Output.html     5 Feb 2007 15:30:24 -0000       
1.21
+++ Tests/nodes_texinfo_res/PDF-Output.html     3 Oct 2007 09:34:44 -0000       
1.22
@@ -86,7 +86,7 @@
 <code>tex</code>.  Just run &lsquo;<samp>pdftex foo.texi</samp>&rsquo; instead 
of &lsquo;<samp>tex
 foo.texi</samp>&rsquo;, or give the &lsquo;<samp>--pdf</samp>&rsquo; option to 
<code>texi2dvi</code>.
 </p>
-<p><em>PDF</em> stands for `Portable Document Format'. It was invented by
+<p><em>PDF</em> stands for &lsquo;Portable Document Format&rsquo;. It was 
invented by
 Adobe Systems some years ago for document interchange, based on their
 PostScript language.  A <a href="http://www.foolabs.com/xpdf/";>PDF reader</a>
 for the X window system is freely available, as is the
@@ -94,7 +94,7 @@
 &lsquo;<samp>@ifpdf</samp>&rsquo; or &lsquo;<samp>@pdf</samp>&rsquo; commands 
as with the other output
 formats.
 </p>
-<p>Despite the `portable' in the name, PDF files are nowhere near as
+<p>Despite the &lsquo;portable&rsquo; in the name, PDF files are nowhere near 
as
 portable in practice as the plain ASCII formats (Info, HTML) that
 Texinfo supports (DVI portability is arguable).  They also tend to be
 much larger and do not support the bitmap fonts used by TeX (by

Index: Tests/nodes_texinfo_res/Pointer-Validation.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/Pointer-Validation.html,v
retrieving revision 1.24
retrieving revision 1.25
diff -u -b -r1.24 -r1.25
--- Tests/nodes_texinfo_res/Pointer-Validation.html     5 Feb 2007 15:30:24 
-0000       1.24
+++ Tests/nodes_texinfo_res/Pointer-Validation.html     3 Oct 2007 09:34:44 
-0000       1.25
@@ -88,33 +88,33 @@
 </p>
 <ol>
 <li>
-If a `Next', `Previous', or `Up' node reference is a reference to a
+If a &lsquo;Next&rsquo;, &lsquo;Previous&rsquo;, or &lsquo;Up&rsquo; node 
reference is a reference to a
 node in the current file and is not an external reference such as to
 &lsquo;<tt>(dir)</tt>&rsquo;, then the referenced node must exist.
 
 </li><li>
-In every node, if the `Previous' node is different from the `Up' node,
-then the node pointed to by the `Previous' field must have a `Next'
+In every node, if the &lsquo;Previous&rsquo; node is different from the 
&lsquo;Up&rsquo; node,
+then the node pointed to by the &lsquo;Previous&rsquo; field must have a 
&lsquo;Next&rsquo;
 field which points back to this node.
 
 </li><li>
-Every node except the `Top' node must have an `Up' pointer.
+Every node except the &lsquo;Top&rsquo; node must have an &lsquo;Up&rsquo; 
pointer.
 
 </li><li>
-The node referenced by an `Up' pointer must itself reference the current
-node through a menu item, unless the node referenced by `Up'
-has the form `(<var>file</var>)'.
+The node referenced by an &lsquo;Up&rsquo; pointer must itself reference the 
current
+node through a menu item, unless the node referenced by &lsquo;Up&rsquo;
+has the form &lsquo;(<var>file</var>)&rsquo;.
 
 </li><li>
-If the `Next' reference of a node is not the same as the `Next' reference
-of the `Up' reference, then the node referenced by the `Next' pointer
-must have a `Previous' pointer that points back to the current node.
+If the &lsquo;Next&rsquo; reference of a node is not the same as the 
&lsquo;Next&rsquo; reference
+of the &lsquo;Up&rsquo; reference, then the node referenced by the 
&lsquo;Next&rsquo; pointer
+must have a &lsquo;Previous&rsquo; pointer that points back to the current 
node.
 This rule allows the last node in a section to point to the first node
 of the next chapter.
 
 </li><li>
-Every node except `Top' should be referenced by at least one other node,
-either via the `Previous' or `Next' links, or via a menu or a
+Every node except &lsquo;Top&rsquo; should be referenced by at least one other 
node,
+either via the &lsquo;Previous&rsquo; or &lsquo;Next&rsquo; links, or via a 
menu or a
 cross-reference.
 </li></ol>
 

Index: Tests/nodes_texinfo_res/Preparing-for-TeX.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/Preparing-for-TeX.html,v
retrieving revision 1.23
retrieving revision 1.24
diff -u -b -r1.23 -r1.24
--- Tests/nodes_texinfo_res/Preparing-for-TeX.html      5 Feb 2007 15:30:24 
-0000       1.23
+++ Tests/nodes_texinfo_res/Preparing-for-TeX.html      3 Oct 2007 09:34:44 
-0000       1.24
@@ -155,12 +155,12 @@
 </p>
 <p>These settings would cause TeX to look for &lsquo;<tt>\input</tt>&rsquo; 
file first
 in the current directory, indicated by the &lsquo;<samp>.</samp>&rsquo;, then 
in a
-hypothetical user's &lsquo;<tt>me/mylib</tt>&rsquo; directory, and finally in 
a system
+hypothetical user&rsquo;s &lsquo;<tt>me/mylib</tt>&rsquo; directory, and 
finally in a system
 directory &lsquo;<tt>/usr/lib/tex/macros</tt>&rsquo;.
 </p>
 <a name="IDX341"></a>
 <a name="IDX342"></a>
-<p>Finally, you may wish to dump a &lsquo;<tt>.fmt</tt>&rsquo; file (see <a 
href="../web2c/Memory-dumps.html#Memory-dumps">(web2c)Memory dumps</a> section 
`Memory dumps' in <cite>Web2c</cite>) so that TeX can load Texinfo faster.  (The
+<p>Finally, you may wish to dump a &lsquo;<tt>.fmt</tt>&rsquo; file (see <a 
href="../web2c/Memory-dumps.html#Memory-dumps">(web2c)Memory dumps</a> section 
&lsquo;Memory dumps&rsquo; in <cite>Web2c</cite>) so that TeX can load Texinfo 
faster.  (The
 disadvantage is that then updating &lsquo;<tt>texinfo.tex</tt>&rsquo; requires
 redumping.)  You can do this by running this command, assuming
 &lsquo;<tt>epsf.tex</tt>&rsquo; is findable by TeX:

Index: Tests/nodes_texinfo_res/Print-with-lpr.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/Print-with-lpr.html,v
retrieving revision 1.23
retrieving revision 1.24
diff -u -b -r1.23 -r1.24
--- Tests/nodes_texinfo_res/Print-with-lpr.html 5 Feb 2007 15:30:24 -0000       
1.23
+++ Tests/nodes_texinfo_res/Print-with-lpr.html 3 Oct 2007 09:34:44 -0000       
1.24
@@ -110,7 +110,7 @@
 <p><code>lpr</code> is a standard program on Unix systems, but it is usually
 absent on MS-DOS/MS-Windows.  Some network packages come with a
 program named <code>lpr</code>, but these are usually limited to sending files
-to a print server over the network, and generally don't support the
+to a print server over the network, and generally don&rsquo;t support the
 &lsquo;<samp>-d</samp>&rsquo; option.  If you are unfortunate enough to work 
on one of these
 systems, you have several alternative ways of printing DVI files:
 </p>
@@ -130,7 +130,7 @@
 </pre></td></tr></table>
 
 </li><li> Convert the DVI file to a Postscript or PCL file and send it to your
-local printer.  See <a 
href="../dvips/dvips-invocation.html#dvips-invocation">(dvips)dvips 
invocation</a> section `dvips invocation' in <cite>Dvips</cite>, and the man
+local printer.  See <a 
href="../dvips/dvips-invocation.html#dvips-invocation">(dvips)dvips 
invocation</a> section &lsquo;dvips invocation&rsquo; in <cite>Dvips</cite>, 
and the man
 pages for <code>dvilj</code>, for detailed description of these tools.  Once
 the DVI file is converted to the format your local printer understands
 directly, just send it to the appropriate port, usually 
&lsquo;<samp>PRN</samp>&rsquo;.

Index: Tests/nodes_texinfo_res/Printed-Books.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/Printed-Books.html,v
retrieving revision 1.22
retrieving revision 1.23
diff -u -b -r1.22 -r1.23
--- Tests/nodes_texinfo_res/Printed-Books.html  5 Feb 2007 15:30:24 -0000       
1.22
+++ Tests/nodes_texinfo_res/Printed-Books.html  3 Oct 2007 09:34:44 -0000       
1.23
@@ -122,7 +122,7 @@
 <p>TeX is freely distributable.  It is written in a superset of Pascal
 called WEB and can be compiled either in Pascal or (by using a
 conversion program that comes with the TeX distribution) in C.
-(See <a href="../emacs/TeX-Mode.html#TeX-Mode">(emacs)TeX Mode</a> section 
`TeX Mode' in <cite>The GNU Emacs Manual</cite>, for information
+(See <a href="../emacs/TeX-Mode.html#TeX-Mode">(emacs)TeX Mode</a> section 
&lsquo;TeX Mode&rsquo; in <cite>The GNU Emacs Manual</cite>, for information
 about TeX.)
 </p>
 <p>TeX is very powerful and has a great many features.  Because a

Index: Tests/nodes_texinfo_res/Quotations-and-Examples.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/Quotations-and-Examples.html,v
retrieving revision 1.21
retrieving revision 1.22
diff -u -b -r1.21 -r1.22
--- Tests/nodes_texinfo_res/Quotations-and-Examples.html        5 Feb 2007 
15:30:24 -0000       1.21
+++ Tests/nodes_texinfo_res/Quotations-and-Examples.html        3 Oct 2007 
09:34:44 -0000       1.22
@@ -113,7 +113,7 @@
 </td></tr>
 <tr><td align="left" valign="top"><a href="format.html#SEC150">10.9 
<code>@format</code> and 
<code>@smallformat</code></a></td><td>&nbsp;&nbsp;</td><td align="left" 
valign="top">                      Writing an example without narrowed margins.
 </td></tr>
-<tr><td align="left" valign="top"><a href="exdent.html#SEC151">10.10 
<code>@exdent</code>: Undoing a Line's 
Indentation</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">         
             Undo indentation on a line.
+<tr><td align="left" valign="top"><a href="exdent.html#SEC151">10.10 
<code>@exdent</code>: Undoing a Line&rsquo;s 
Indentation</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">         
             Undo indentation on a line.
 </td></tr>
 <tr><td align="left" valign="top"><a 
href="flushleft-_0026-flushright.html#SEC152">10.11 <code>@flushleft</code> and 
<code>@flushright</code></a></td><td>&nbsp;&nbsp;</td><td align="left" 
valign="top">      Pushing text flush left or flush right.
 </td></tr>

Index: Tests/nodes_texinfo_res/Raise_002flower-sections.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/Raise_002flower-sections.html,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -b -r1.9 -r1.10
--- Tests/nodes_texinfo_res/Raise_002flower-sections.html       5 Feb 2007 
15:30:24 -0000       1.9
+++ Tests/nodes_texinfo_res/Raise_002flower-sections.html       3 Oct 2007 
09:34:44 -0000       1.10
@@ -137,8 +137,8 @@
 <p>Repeated use of the commands continue to raise or lower the hierarchical
 level a step at a time.
 </p>
-<p>An attempt to raise above `chapters' reproduces chapter commands; an
-attempt to lower below `subsubsections' reproduces subsubsection
+<p>An attempt to raise above &lsquo;chapters&rsquo; reproduces chapter 
commands; an
+attempt to lower below &lsquo;subsubsections&rsquo; reproduces subsubsection
 commands.
 </p>
 <hr size="1">

Index: Tests/nodes_texinfo_res/Reporting-Bugs.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/Reporting-Bugs.html,v
retrieving revision 1.21
retrieving revision 1.22
diff -u -b -r1.21 -r1.22
--- Tests/nodes_texinfo_res/Reporting-Bugs.html 5 Feb 2007 15:30:24 -0000       
1.21
+++ Tests/nodes_texinfo_res/Reporting-Bugs.html 3 Oct 2007 09:34:44 -0000       
1.22
@@ -99,15 +99,15 @@
 </li><li> anything else that you think would be helpful.
 </li></ul>
 
-<p>When in doubt whether something is needed or not, include it.  It's
+<p>When in doubt whether something is needed or not, include it.  It&rsquo;s
 better to include too much than to leave out something important.
 </p>
 <a name="IDX2"></a>
 <p>Patches are most welcome; if possible, please make them with
-&lsquo;<samp>diff -c</samp>&rsquo; (see <a 
href="../diffutils/index.html#Top">(diffutils)Top</a> section `Overview' in 
<cite>Comparing and Merging Files</cite>) and include 
&lsquo;<tt>ChangeLog</tt>&rsquo; entries (see <a 
href="../emacs/Change-Log.html#Change-Log">(emacs)Change Log</a> section 
`Change Log' in <cite>The GNU Emacs Manual</cite>).
+&lsquo;<samp>diff -c</samp>&rsquo; (see <a 
href="../diffutils/index.html#Top">(diffutils)Top</a> section 
&lsquo;Overview&rsquo; in <cite>Comparing and Merging Files</cite>) and include 
&lsquo;<tt>ChangeLog</tt>&rsquo; entries (see <a 
href="../emacs/Change-Log.html#Change-Log">(emacs)Change Log</a> section 
&lsquo;Change Log&rsquo; in <cite>The GNU Emacs Manual</cite>).
 </p>
 <p>When sending patches, if possible please do not encode or split them in
-any way; it's much easier to deal with one plain text message, however
+any way; it&rsquo;s much easier to deal with one plain text message, however
 large, than many small ones.  <a href="ftp://ftp.gnu.org/gnu/sharutils/";>GNU 
shar</a> is a convenient way of packaging multiple and/or binary files
 for email.
 </p>

Index: Tests/nodes_texinfo_res/Requirements-Summary.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/Requirements-Summary.html,v
retrieving revision 1.20
retrieving revision 1.21
diff -u -b -r1.20 -r1.21
--- Tests/nodes_texinfo_res/Requirements-Summary.html   5 Feb 2007 15:30:24 
-0000       1.20
+++ Tests/nodes_texinfo_res/Requirements-Summary.html   3 Oct 2007 09:34:44 
-0000       1.21
@@ -91,7 +91,7 @@
 <p>The first command instructs TeX to load the macros it needs to
 process a Texinfo file and the second command opens auxiliary files.
 </p>
-<p>Every Texinfo file must end with a line that terminates TeX's
+<p>Every Texinfo file must end with a line that terminates TeX&rsquo;s
 processing and forces out unfinished pages:
 </p>
 <table><tr><td>&nbsp;</td><td><pre class="example">@bye

Index: Tests/nodes_texinfo_res/Running-Info_002dValidate.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/Running-Info_002dValidate.html,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -b -r1.8 -r1.9
--- Tests/nodes_texinfo_res/Running-Info_002dValidate.html      5 Feb 2007 
15:30:24 -0000       1.8
+++ Tests/nodes_texinfo_res/Running-Info_002dValidate.html      3 Oct 2007 
09:34:45 -0000       1.9
@@ -82,7 +82,7 @@
 <h2 class="section"> F.5 Finding Badly Referenced Nodes </h2>
 
 <p>You can use the <code>Info-validate</code> command to check whether any of
-the `Next', `Previous', `Up' or other node pointers fail to point to a
+the &lsquo;Next&rsquo;, &lsquo;Previous&rsquo;, &lsquo;Up&rsquo; or other node 
pointers fail to point to a
 node.  This command checks that every node pointer points to an
 existing node.  The <code>Info-validate</code> command works only on Info
 files, not on Texinfo files.

Index: Tests/nodes_texinfo_res/Sample-Function-Definition.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/Sample-Function-Definition.html,v
retrieving revision 1.21
retrieving revision 1.22
diff -u -b -r1.21 -r1.22
--- Tests/nodes_texinfo_res/Sample-Function-Definition.html     5 Feb 2007 
15:30:24 -0000       1.21
+++ Tests/nodes_texinfo_res/Sample-Function-Definition.html     3 Oct 2007 
09:34:45 -0000       1.22
@@ -86,7 +86,7 @@
 <code>@defun</code> command and it is followed, on the same line, by the
 parameter list.
 </p>
-<p>Here is a definition from <a 
href="../elisp/Calling-Functions.html#Calling-Functions">(elisp)Calling 
Functions</a> section `Calling Functions' in <cite>The GNU Emacs Lisp Reference 
Manual</cite>.
+<p>Here is a definition from <a 
href="../elisp/Calling-Functions.html#Calling-Functions">(elisp)Calling 
Functions</a> section &lsquo;Calling Functions&rsquo; in <cite>The GNU Emacs 
Lisp Reference Manual</cite>.
 </p>
 <blockquote><dl>
 <dt><u>Function:</u> <b>apply</b><i> function &amp;rest arguments</i>

Index: Tests/nodes_texinfo_res/Short-Sample.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/Short-Sample.html,v
retrieving revision 1.23
retrieving revision 1.24
diff -u -b -r1.23 -r1.24
--- Tests/nodes_texinfo_res/Short-Sample.html   5 Feb 2007 15:30:24 -0000       
1.23
+++ Tests/nodes_texinfo_res/Short-Sample.html   3 Oct 2007 09:34:45 -0000       
1.24
@@ -146,9 +146,9 @@
 </pre></td></tr></table>
 
 <a name="SEC16"></a>
-<h3 class="subheading"> Part 4: `Top' Node and Master Menu </h3>
+<h3 class="subheading"> Part 4: &lsquo;Top&rsquo; Node and Master Menu </h3>
 
-<p>The `Top' node contains the master menu for the Info file.  Since a
+<p>The &lsquo;Top&rsquo; node contains the master menu for the Info file.  
Since a
 printed manual uses a table of contents rather than a menu, the master
 menu appears only in online output.  We also include the copying text
 again for the benefit of online readers.  And since the copying text

Index: Tests/nodes_texinfo_res/Showing-the-Structure.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/Showing-the-Structure.html,v
retrieving revision 1.22
retrieving revision 1.23
diff -u -b -r1.22 -r1.23
--- Tests/nodes_texinfo_res/Showing-the-Structure.html  5 Feb 2007 15:30:24 
-0000       1.22
+++ Tests/nodes_texinfo_res/Showing-the-Structure.html  3 Oct 2007 09:34:45 
-0000       1.23
@@ -112,7 +112,7 @@
 typing <kbd>C-u C-c C-s</kbd>, it will list not only those lines with the
 @-commands for <code>@chapter</code>, <code>@section</code>, and the like, but
 also the <code>@node</code> lines.  You can use 
<code>texinfo-show-structure</code>
-with a prefix argument to check whether the `Next', `Previous', and `Up'
+with a prefix argument to check whether the &lsquo;Next&rsquo;, 
&lsquo;Previous&rsquo;, and &lsquo;Up&rsquo;
 pointers of an <code>@node</code> line are correct.
 </p>
 <p>Often, when you are working on a manual, you will be interested only
@@ -121,7 +121,7 @@
 <kbd>C-x n n</kbd> (<code>narrow-to-region</code>) command and
 <code>texinfo-show-structure</code> will work on only that region.  To see
 the whole buffer again, use <kbd>C-x n w</kbd> (<code>widen</code>).
-(See <a href="../emacs/Narrowing.html#Narrowing">(emacs)Narrowing</a> section 
`Narrowing' in <cite>The GNU Emacs Manual</cite>, for more
+(See <a href="../emacs/Narrowing.html#Narrowing">(emacs)Narrowing</a> section 
&lsquo;Narrowing&rsquo; in <cite>The GNU Emacs Manual</cite>, for more
 information about the narrowing commands.)
 </p>
 <a name="IDX50"></a>
@@ -132,7 +132,7 @@
 ]</kbd> (<code>forward-page</code>) and <kbd>C-x [</kbd> 
(<code>backward-page</code>)
 commands to move forward and backward by chapter, and to use the
 <kbd>C-x p</kbd> (<code>narrow-to-page</code>) command to narrow to a chapter.
-See <a href="../emacs/Pages.html#Pages">(emacs)Pages</a> section `Pages' in 
<cite>The GNU Emacs Manual</cite>, for more information
+See <a href="../emacs/Pages.html#Pages">(emacs)Pages</a> section 
&lsquo;Pages&rsquo; in <cite>The GNU Emacs Manual</cite>, for more information
 about the page commands.
 </p>
 <hr size="1">

Index: Tests/nodes_texinfo_res/Six-Parts.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/Six-Parts.html,v
retrieving revision 1.20
retrieving revision 1.21
diff -u -b -r1.20 -r1.21
--- Tests/nodes_texinfo_res/Six-Parts.html      5 Feb 2007 15:30:24 -0000       
1.20
+++ Tests/nodes_texinfo_res/Six-Parts.html      3 Oct 2007 09:34:45 -0000       
1.21
@@ -104,8 +104,8 @@
 copyright page appear only in the printed manual.
 </p>
 </dd>
-<dt> <span class="roman">4. `Top' Node and Master Menu</span></dt>
-<dd><p>The `Top' node starts off the online output; it does not appear in the
+<dt> <span class="roman">4. &lsquo;Top&rsquo; Node and Master Menu</span></dt>
+<dd><p>The &lsquo;Top&rsquo; node starts off the online output; it does not 
appear in the
 printed manual.  We recommend including the copying permissions here as
 well as the segments above.  And it contains at least a top-level menu
 listing the chapters, and possibly a <em>Master Menu</em> listing all the

Index: Tests/nodes_texinfo_res/Smallcaps.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/Smallcaps.html,v
retrieving revision 1.22
retrieving revision 1.23
diff -u -b -r1.22 -r1.23
--- Tests/nodes_texinfo_res/Smallcaps.html      5 Feb 2007 15:30:24 -0000       
1.22
+++ Tests/nodes_texinfo_res/Smallcaps.html      3 Oct 2007 09:34:45 -0000       
1.23
@@ -95,19 +95,19 @@
 </pre></td></tr></table>
 
 <p>TeX typesets the small caps font in a manner that prevents the
-letters from `jumping out at you on the page'.  This makes small caps
-text easier to read than text in all upper case&mdash;but it's usually
+letters from &lsquo;jumping out at you on the page&rsquo;.  This makes small 
caps
+text easier to read than text in all upper case&mdash;but it&rsquo;s usually
 better to use regular mixed case anyway.  The Info formatting commands
 set all small caps text in upper case.  In HTML, the text is upper-cased
 and a smaller font is used to render it.
 </p>
 <p>If the text between the braces of an <code>@sc</code> command is uppercase,
 TeX typesets in FULL-SIZE CAPITALS.  Use full-size capitals
-sparingly, if ever, and since it's redundant to mark all-uppercase text
+sparingly, if ever, and since it&rsquo;s redundant to mark all-uppercase text
 with <code>@sc</code>, <code>makeinfo</code> warns about such usage.
 </p>
 <p>You may also use the small caps font for a jargon word such as
-<small>ATO</small> (a <small>NASA</small> word meaning `abort to orbit').
+<small>ATO</small> (a <small>NASA</small> word meaning &lsquo;abort to 
orbit&rsquo;).
 </p>
 <p>There are subtleties to using the small caps font with a jargon word
 such as <small>CDR</small>, a word used in Lisp programming.  In this case, you

Index: Tests/nodes_texinfo_res/Software-Copying-Permissions.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/Software-Copying-Permissions.html,v
retrieving revision 1.19
retrieving revision 1.20
diff -u -b -r1.19 -r1.20
--- Tests/nodes_texinfo_res/Software-Copying-Permissions.html   5 Feb 2007 
15:30:24 -0000       1.19
+++ Tests/nodes_texinfo_res/Software-Copying-Permissions.html   3 Oct 2007 
09:34:45 -0000       1.20
@@ -84,7 +84,7 @@
 <p>If the Texinfo file has a section containing the &ldquo;General Public
 License&rdquo; and the distribution information and a warranty disclaimer for
 the software that is documented, we recommend placing this right after
-the `Top' node.  The General Public License is very important to Project
+the &lsquo;Top&rsquo; node.  The General Public License is very important to 
Project
 GNU software.  It ensures that you and others will continue to have a
 right to use and share the software.
 </p>

Index: Tests/nodes_texinfo_res/Structuring.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/Structuring.html,v
retrieving revision 1.22
retrieving revision 1.23
diff -u -b -r1.22 -r1.23
--- Tests/nodes_texinfo_res/Structuring.html    5 Feb 2007 15:30:24 -0000       
1.22
+++ Tests/nodes_texinfo_res/Structuring.html    3 Oct 2007 09:34:45 -0000       
1.23
@@ -97,14 +97,14 @@
 <p>It is unlikely that you will ever write a Texinfo file that is
 intended only as an Info file and not as a printable document.  If you
 do, you might still use chapter structuring commands to create a
-heading at the top of each node&mdash;but you don't need to.
+heading at the top of each node&mdash;but you don&rsquo;t need to.
 </p>
 <table class="menu" border="0" cellspacing="0">
 <tr><td align="left" valign="top"><a href="Tree-Structuring.html#SEC73">5.1 
Tree Structure of Sections</a></td><td>&nbsp;&nbsp;</td><td align="left" 
valign="top">            A manual is like an upside down tree &hellip;
 </td></tr>
 <tr><td align="left" valign="top"><a 
href="Structuring-Command-Types.html#SEC74">5.2 Structuring Command 
Types</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">   How to 
divide a manual into parts.
 </td></tr>
-<tr><td align="left" valign="top"><a href="makeinfo-top.html#SEC75">5.3 
<code>@top</code></a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">   
             The <code>@top</code> command, part of the `Top' node.
+<tr><td align="left" valign="top"><a href="makeinfo-top.html#SEC75">5.3 
<code>@top</code></a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">   
             The <code>@top</code> command, part of the &lsquo;Top&rsquo; node.
 </td></tr>
 <tr><td align="left" valign="top"><a href="chapter.html#SEC76">5.4 
<code>@chapter</code></a></td><td>&nbsp;&nbsp;</td><td align="left" 
valign="top">                     
 </td></tr>
@@ -120,9 +120,9 @@
 </td></tr>
 <tr><td align="left" valign="top"><a 
href="unnumberedsubsec-appendixsubsec-subheading.html#SEC82">5.10 The 
<code>@subsection</code>-like Commands</a></td><td>&nbsp;&nbsp;</td><td 
align="left" valign="top">  
 </td></tr>
-<tr><td align="left" valign="top"><a href="subsubsection.html#SEC83">5.11 The 
`subsub' Commands</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">   
            Commands for the lowest level sections.
+<tr><td align="left" valign="top"><a href="subsubsection.html#SEC83">5.11 The 
&lsquo;subsub&rsquo; Commands</a></td><td>&nbsp;&nbsp;</td><td align="left" 
valign="top">               Commands for the lowest level sections.
 </td></tr>
-<tr><td align="left" valign="top"><a 
href="Raise_002flower-sections.html#SEC84">5.12 <code>@raisesections</code> and 
<code>@lowersections</code></a></td><td>&nbsp;&nbsp;</td><td align="left" 
valign="top">        How to change commands' hierarchical level.
+<tr><td align="left" valign="top"><a 
href="Raise_002flower-sections.html#SEC84">5.12 <code>@raisesections</code> and 
<code>@lowersections</code></a></td><td>&nbsp;&nbsp;</td><td align="left" 
valign="top">        How to change commands&rsquo; hierarchical level.
 </td></tr>
 </table>
 

Index: Tests/nodes_texinfo_res/TeX-and-copyright.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/TeX-and-copyright.html,v
retrieving revision 1.22
retrieving revision 1.23
diff -u -b -r1.22 -r1.23
--- Tests/nodes_texinfo_res/TeX-and-copyright.html      5 Feb 2007 15:30:24 
-0000       1.22
+++ Tests/nodes_texinfo_res/TeX-and-copyright.html      3 Oct 2007 09:34:45 
-0000       1.23
@@ -81,8 +81,8 @@
 <hr size="1">
 <h2 class="section"> 13.5 Inserting TeX and the Copyright Symbol </h2>
 
-<p>The logo `TeX' is typeset in a special fashion and it needs an
address@hidden  The copyright symbol, `&copy;', is also special.
+<p>The logo &lsquo;TeX&rsquo; is typeset in a special fashion and it needs an
address@hidden  The copyright symbol, &lsquo;&copy;&rsquo;, is also special.
 Each of these commands is followed by a pair of braces, 
&lsquo;<samp>{}</samp>&rsquo;,
 without any whitespace between the name of the command and the
 braces.

Index: Tests/nodes_texinfo_res/Texinfo-Mode-Printing.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/Texinfo-Mode-Printing.html,v
retrieving revision 1.24
retrieving revision 1.25
diff -u -b -r1.24 -r1.25
--- Tests/nodes_texinfo_res/Texinfo-Mode-Printing.html  5 Feb 2007 15:30:24 
-0000       1.24
+++ Tests/nodes_texinfo_res/Texinfo-Mode-Printing.html  3 Oct 2007 09:34:45 
-0000       1.25
@@ -177,14 +177,14 @@
 </pre></td></tr></table>
 
 <p>You can change the values of these variables with the <kbd>M-x
-edit-options</kbd> command (see <a 
href="../emacs/Edit-Options.html#Edit-Options">(emacs)Edit Options</a> section 
`Editing Variable Values' in <cite>The GNU Emacs Manual</cite>), with the 
<kbd>M-x set-variable</kbd> command
-(see <a href="../emacs/Examining.html#Examining">(emacs)Examining</a> section 
`Examining and Setting Variables' in <cite>The GNU Emacs Manual</cite>), or 
with your &lsquo;<tt>.emacs</tt>&rsquo; initialization file
-(see <a href="../emacs/Init-File.html#Init-File">(emacs)Init File</a> section 
`Init File' in <cite>The GNU Emacs Manual</cite>).
+edit-options</kbd> command (see <a 
href="../emacs/Edit-Options.html#Edit-Options">(emacs)Edit Options</a> section 
&lsquo;Editing Variable Values&rsquo; in <cite>The GNU Emacs Manual</cite>), 
with the <kbd>M-x set-variable</kbd> command
+(see <a href="../emacs/Examining.html#Examining">(emacs)Examining</a> section 
&lsquo;Examining and Setting Variables&rsquo; in <cite>The GNU Emacs 
Manual</cite>), or with your &lsquo;<tt>.emacs</tt>&rsquo; initialization file
+(see <a href="../emacs/Init-File.html#Init-File">(emacs)Init File</a> section 
&lsquo;Init File&rsquo; in <cite>The GNU Emacs Manual</cite>).
 </p>
 <a name="IDX333"></a>
 <p>Beginning with version 20, GNU Emacs offers a user-friendly interface,
 called <em>Customize</em>, for changing values of user-definable variables.
-See <a href="../emacs/Easy-Customization.html#Easy-Customization">(emacs)Easy 
Customization</a> section `Easy Customization Interface' in <cite>The GNU Emacs 
Manual</cite>, for more details about this.  The Texinfo variables can
+See <a href="../emacs/Easy-Customization.html#Easy-Customization">(emacs)Easy 
Customization</a> section &lsquo;Easy Customization Interface&rsquo; in 
<cite>The GNU Emacs Manual</cite>, for more details about this.  The Texinfo 
variables can
 be found in the &lsquo;<samp>Development/Docs/Texinfo</samp>&rsquo; group, 
once you invoke
 the <kbd>M-x customize</kbd> command.
 </p>

Index: Tests/nodes_texinfo_res/Texinfo-Mode-Summary.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/Texinfo-Mode-Summary.html,v
retrieving revision 1.23
retrieving revision 1.24
diff -u -b -r1.23 -r1.24
--- Tests/nodes_texinfo_res/Texinfo-Mode-Summary.html   5 Feb 2007 15:30:24 
-0000       1.23
+++ Tests/nodes_texinfo_res/Texinfo-Mode-Summary.html   3 Oct 2007 09:34:45 
-0000       1.24
@@ -91,7 +91,7 @@
 
 <p>The insert commands are invoked by typing <kbd>C-c</kbd> twice and then the
 first letter of the @-command to be inserted.  (It might make more
-sense mnemonically to use <kbd>C-c C-i</kbd>, for `custom insert', but
+sense mnemonically to use <kbd>C-c C-i</kbd>, for &lsquo;custom insert&rsquo;, 
but
 <kbd>C-c C-c</kbd> is quick to type.)
 </p>
 <table><tr><td>&nbsp;</td><td><pre class="example">C-c C-c c       <span 
class="roman">Insert</span> &lsquo;<samp>@code</samp>&rsquo;.

Index: Tests/nodes_texinfo_res/Texinfo-Mode.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/Texinfo-Mode.html,v
retrieving revision 1.23
retrieving revision 1.24
diff -u -b -r1.23 -r1.24
--- Tests/nodes_texinfo_res/Texinfo-Mode.html   5 Feb 2007 15:30:24 -0000       
1.23
+++ Tests/nodes_texinfo_res/Texinfo-Mode.html   3 Oct 2007 09:34:45 -0000       
1.24
@@ -86,7 +86,7 @@
 comes with a special mode, called Texinfo mode, that provides Emacs
 commands and tools to help ease your work.
 </p>
-<p>This chapter describes features of GNU Emacs' Texinfo mode but not any
+<p>This chapter describes features of GNU Emacs&rsquo; Texinfo mode but not any
 features of the Texinfo formatting language.  So if you are reading this
 manual straight through from the beginning, you may want to skim through
 this chapter briefly and come back to it after reading succeeding
@@ -95,7 +95,7 @@
 <table class="menu" border="0" cellspacing="0">
 <tr><td align="left" valign="top"><a href="#Texinfo-Mode-Overview">&bull; 
Texinfo Mode Overview</a></td><td>&nbsp;&nbsp;</td><td align="left" 
valign="top">       How Texinfo mode can help you.
 </td></tr>
-<tr><td align="left" valign="top"><a href="Emacs-Editing.html#SEC23">2.1 The 
Usual GNU Emacs Editing Commands</a></td><td>&nbsp;&nbsp;</td><td align="left" 
valign="top">               Texinfo mode adds to GNU Emacs' general
+<tr><td align="left" valign="top"><a href="Emacs-Editing.html#SEC23">2.1 The 
Usual GNU Emacs Editing Commands</a></td><td>&nbsp;&nbsp;</td><td align="left" 
valign="top">               Texinfo mode adds to GNU Emacs&rsquo; general
                                   purpose editing features.
 </td></tr>
 <tr><td align="left" valign="top"><a href="Inserting.html#SEC24">2.2 Inserting 
Frequently Used Commands</a></td><td>&nbsp;&nbsp;</td><td align="left" 
valign="top">                   How to insert frequently used @-commands.
@@ -131,8 +131,8 @@
 Show the structure of a Texinfo source file.
 
 </li><li>
-Automatically create or update the `Next',
-`Previous', and `Up' pointers of a node.
+Automatically create or update the &lsquo;Next&rsquo;,
+&lsquo;Previous&rsquo;, and &lsquo;Up&rsquo; pointers of a node.
 
 </li><li>
 Automatically create or update menus.

Index: Tests/nodes_texinfo_res/The-Top-Node.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/The-Top-Node.html,v
retrieving revision 1.19
retrieving revision 1.20
diff -u -b -r1.19 -r1.20
--- Tests/nodes_texinfo_res/The-Top-Node.html   5 Feb 2007 15:30:24 -0000       
1.19
+++ Tests/nodes_texinfo_res/The-Top-Node.html   3 Oct 2007 09:34:45 -0000       
1.20
@@ -79,9 +79,9 @@
 <td valign="middle" align="left">[<a href="texinfo_abt.html#SEC_About" 
title="About (help)"> ? </a>]</td>
 </tr></table>
 <hr size="1">
-<h2 class="section"> 3.5 The `Top' Node and Master Menu </h2>
+<h2 class="section"> 3.5 The &lsquo;Top&rsquo; Node and Master Menu </h2>
 
-<p>The `Top' node is the node in which a reader enters an Info manual.  As
+<p>The &lsquo;Top&rsquo; node is the node in which a reader enters an Info 
manual.  As
 such, it should begin with the <code>@insertcopying</code> command
 (see section <a href="Document-Permissions.html#SEC49">Document 
Permissions</a>) to provide a brief description of the
 manual (including the version number) and copying permissions, and end
@@ -93,7 +93,7 @@
 containing the title of the document immediately after the <code>@node
 Top</code> line (see section <a href="makeinfo-top-command.html#SEC94">The 
<code>@top</code> Sectioning Command</a>).
 </p>
-<p>The contents of the `Top' node should appear only in the online output;
+<p>The contents of the &lsquo;Top&rsquo; node should appear only in the online 
output;
 none of it should appear in printed output, so enclose it between
 <code>@ifnottex</code> and <code>@end ifnottex</code> commands.  (TeX does not
 print either an <code>@node</code> line or a menu; they appear only in Info;

Index: Tests/nodes_texinfo_res/Three-Arguments.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/Three-Arguments.html,v
retrieving revision 1.21
retrieving revision 1.22
diff -u -b -r1.21 -r1.22
--- Tests/nodes_texinfo_res/Three-Arguments.html        5 Feb 2007 15:30:24 
-0000       1.21
+++ Tests/nodes_texinfo_res/Three-Arguments.html        3 Oct 2007 09:34:45 
-0000       1.22
@@ -144,7 +144,7 @@
 same, and with the first and third arguments if the node name and title
 are different.
 </p>
-<p>Here are several examples from <cite>The GNU Awk User's Guide</cite>:
+<p>Here are several examples from <cite>The GNU Awk User&rsquo;s Guide</cite>:
 </p>
 <table><tr><td>&nbsp;</td><td><pre class="smallexample">@xref{Sample Program}.
 @xref{Glossary}.

Index: Tests/nodes_texinfo_res/Tips.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/Tips.html,v
retrieving revision 1.27
retrieving revision 1.28
diff -u -b -r1.27 -r1.28
--- Tests/nodes_texinfo_res/Tips.html   5 Feb 2007 15:30:24 -0000       1.27
+++ Tests/nodes_texinfo_res/Tips.html   3 Oct 2007 09:34:45 -0000       1.28
@@ -284,7 +284,7 @@
 
 <p>so it looks like this:
 </p>
-<blockquote><p>`C-x v' `M-x vc-next-action' Perform the next logical operation 
on the
+<blockquote><p>&lsquo;C-x v&rsquo; &lsquo;M-x vc-next-action&rsquo; Perform 
the next logical operation on the
 version-controlled file corresponding to the current buffer.
 </p></blockquote>
 
@@ -376,14 +376,14 @@
 sections are all different, they are difficult for users to find.
 </p>
 <p>So, there is a convention to name such sections with a phrase beginning
-with the word `Invoking', as in `Invoking Emacs'; this way, users can
+with the word &lsquo;Invoking&rsquo;, as in &lsquo;Invoking Emacs&rsquo;; this 
way, users can
 find the section easily.
 </p>
 
 <a name="SEC291"></a>
 <h4 class="subsubheading"> ANSI C Syntax </h4>
 
-<p>When you use <code>@example</code> to describe a C function's calling
+<p>When you use <code>@example</code> to describe a C function&rsquo;s calling
 conventions, use the ANSI C syntax, like this:
 </p>
 <table><tr><td>&nbsp;</td><td><pre class="example">void dld_init (char 
address@hidden);
@@ -429,10 +429,10 @@
 a unified control mode like this possible).
 </p></blockquote>
 
-<p>And in this example, you should specify what `it' refers to:
+<p>And in this example, you should specify what &lsquo;it&rsquo; refers to:
 </p>
 <blockquote><p>If you are working with other people, it assists in coordinating
-everyone's changes so they do not step on each other.
+everyone&rsquo;s changes so they do not step on each other.
 </p></blockquote>
 
 <a name="SEC293"></a>
@@ -440,8 +440,8 @@
 
 <ul>
 <li>
-Pronounce TeX as if the &lsquo;<samp>X</samp>&rsquo; were a Greek `chi', as 
the last
-sound in the name `Bach'.  But pronounce Texinfo as in `speck':
+Pronounce TeX as if the &lsquo;<samp>X</samp>&rsquo; were a Greek 
&lsquo;chi&rsquo;, as the last
+sound in the name &lsquo;Bach&rsquo;.  But pronounce Texinfo as in 
&lsquo;speck&rsquo;:
 &ldquo;teckinfo&rdquo;.
 
 </li><li>

Index: Tests/nodes_texinfo_res/Titlepage-_0026-Copyright-Page.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/Titlepage-_0026-Copyright-Page.html,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -b -r1.10 -r1.11
--- Tests/nodes_texinfo_res/Titlepage-_0026-Copyright-Page.html 5 Feb 2007 
15:30:24 -0000       1.10
+++ Tests/nodes_texinfo_res/Titlepage-_0026-Copyright-Page.html 3 Oct 2007 
09:34:45 -0000       1.11
@@ -81,7 +81,7 @@
 <hr size="1">
 <h2 class="section"> 3.4 Title and Copyright Pages </h2>
 
-<p>In hard copy output, the manual's name and author are usually printed on
+<p>In hard copy output, the manual&rsquo;s name and author are usually printed 
on
 a title page.  Copyright information is usually printed on the back of
 the title page.
 </p>

Index: Tests/nodes_texinfo_res/Top-Node-Naming.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/Top-Node-Naming.html,v
retrieving revision 1.23
retrieving revision 1.24
diff -u -b -r1.23 -r1.24
--- Tests/nodes_texinfo_res/Top-Node-Naming.html        5 Feb 2007 15:30:24 
-0000       1.23
+++ Tests/nodes_texinfo_res/Top-Node-Naming.html        3 Oct 2007 09:34:45 
-0000       1.24
@@ -79,14 +79,14 @@
 <td valign="middle" align="left">[<a href="texinfo_abt.html#SEC_About" 
title="About (help)"> ? </a>]</td>
 </tr></table>
 <hr size="1">
-<h2 class="section"> 8.4 Naming a `Top' Node </h2>
+<h2 class="section"> 8.4 Naming a &lsquo;Top&rsquo; Node </h2>
 
 <p>In a cross reference, you must always name a node.  This means that in
-order to refer to a whole manual, you must identify the `Top' node by
+order to refer to a whole manual, you must identify the &lsquo;Top&rsquo; node 
by
 writing it as the first argument to the <code>@xref</code> command.  (This
 is different from the way you write a menu entry; see <a 
href="Other-Info-Files.html#SEC103">Referring to Other Info Files</a>.)  At the 
same time, to
 provide a meaningful section topic or title in the printed cross
-reference (instead of the word `Top'), you must write an appropriate
+reference (instead of the word &lsquo;Top&rsquo;), you must write an 
appropriate
 entry for the third argument to the <code>@xref</code> command.
 
 </p>

Index: Tests/nodes_texinfo_res/Two_002dcolumn-Tables.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/Two_002dcolumn-Tables.html,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -b -r1.11 -r1.12
--- Tests/nodes_texinfo_res/Two_002dcolumn-Tables.html  5 Feb 2007 15:30:24 
-0000       1.11
+++ Tests/nodes_texinfo_res/Two_002dcolumn-Tables.html  3 Oct 2007 09:34:45 
-0000       1.12
@@ -111,7 +111,7 @@
 of each item and determines how it will be highlighted.  For example,
 <code>@code</code> will cause the text in the first column to be highlighted
 with an <code>@code</code> command.  (We recommend <code>@code</code> for
-<code>@table</code>'s of command-line options.)
+<code>@table</code>&rsquo;s of command-line options.)
 </p>
 <a name="IDX138"></a>
 <p>You may also choose to use the <code>@asis</code> command as an argument to

Index: Tests/nodes_texinfo_res/Typed-Functions.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/Typed-Functions.html,v
retrieving revision 1.26
retrieving revision 1.27
diff -u -b -r1.26 -r1.27
--- Tests/nodes_texinfo_res/Typed-Functions.html        5 Feb 2007 15:30:24 
-0000       1.26
+++ Tests/nodes_texinfo_res/Typed-Functions.html        3 Oct 2007 09:34:45 
-0000       1.27
@@ -151,7 +151,7 @@
 would be a single line in a real Texinfo file.)
 </p>
 <p>In this instance, the procedure is classified as belonging to the
-package <code>stacks</code> rather than classified as a `procedure' and its
+package <code>stacks</code> rather than classified as a 
&lsquo;procedure&rsquo; and its
 data type is described as <code>private</code>.  (The name of the procedure
 is <code>push</code>, and its arguments are <var>s</var> and <var>n</var>.)
 </p>

Index: Tests/nodes_texinfo_res/Updating-Nodes-and-Menus.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/Updating-Nodes-and-Menus.html,v
retrieving revision 1.27
retrieving revision 1.28
diff -u -b -r1.27 -r1.28
--- Tests/nodes_texinfo_res/Updating-Nodes-and-Menus.html       5 Feb 2007 
15:30:24 -0000       1.27
+++ Tests/nodes_texinfo_res/Updating-Nodes-and-Menus.html       3 Oct 2007 
09:34:45 -0000       1.28
@@ -84,8 +84,8 @@
 <p>Texinfo mode provides commands for automatically creating or updating
 menus and node pointers.  The commands are called &ldquo;update&rdquo; commands
 because their most frequent use is for updating a Texinfo file after you
-have worked on it; but you can use them to insert the `Next',
-`Previous', and `Up' pointers into an <code>@node</code> line that has none
+have worked on it; but you can use them to insert the &lsquo;Next&rsquo;,
+&lsquo;Previous&rsquo;, and &lsquo;Up&rsquo; pointers into an 
<code>@node</code> line that has none
 and to create menus in a file that has none.
 </p>
 <p>If you do not use the updating commands, you need to write menus and
@@ -111,7 +111,7 @@
 </p>
 <ul>
 <li>
-insert or update the `Next', `Previous', and `Up' pointers of a
+insert or update the &lsquo;Next&rsquo;, &lsquo;Previous&rsquo;, and 
&lsquo;Up&rsquo; pointers of a
 node,
 
 </li><li>
@@ -127,7 +127,7 @@
 <p>The updating commands work only with conventional Texinfo files, which
 are structured hierarchically like books.  In such files, a structuring
 command line must follow closely after each <code>@node</code> line, except
-for the `Top' <code>@node</code> line.  (A <em>structuring command line</em> is
+for the &lsquo;Top&rsquo; <code>@node</code> line.  (A <em>structuring command 
line</em> is
 a line beginning with <code>@chapter</code>, <code>@section</code>, or other
 similar command.)
 </p>
@@ -138,12 +138,12 @@
 the <code>@node</code> line and the structuring command line; and you may
 interpose only an <code>@comment</code> line or an <code>@ifinfo</code> line.
 </p>
-<p>Commands which work on a whole buffer require that the `Top' node be
+<p>Commands which work on a whole buffer require that the &lsquo;Top&rsquo; 
node be
 followed by a node with an <code>@chapter</code> or equivalent-level command.
 The menu updating commands will not create a main or master menu for a
 Texinfo file that has only <code>@chapter</code>-level nodes!  The menu
 updating commands only create menus <em>within</em> nodes for lower level
-nodes.  To create a menu of chapters, you must provide a `Top'
+nodes.  To create a menu of chapters, you must provide a &lsquo;Top&rsquo;
 node.
 </p>
 <p>The menu updating commands remove menu entries that refer to other Info
@@ -174,7 +174,7 @@
 constructing the master menu.  (See section <a 
href="The-Top-Node.html#SEC59">The Top Node and Master Menu</a>, for more about 
a master menu.)
 </p>
 <p>For <code>texinfo-master-menu</code> to work, the Texinfo file must have a
-`Top' node and at least one subsequent node.
+&lsquo;Top&rsquo; node and at least one subsequent node.
 </p>
 <p>After extensively editing a Texinfo file, you can type the following:
 </p>
@@ -197,9 +197,9 @@
 <dt> <kbd>C-c C-u C-n</kbd></dt>
 <dt> <kbd>M-x texinfo-update-node</kbd></dt>
 <dd><a name="IDX53"></a>
-<p>Insert the `Next', `Previous', and `Up' pointers for the node that point is
+<p>Insert the &lsquo;Next&rsquo;, &lsquo;Previous&rsquo;, and &lsquo;Up&rsquo; 
pointers for the node that point is
 within (i.e., for the <code>@node</code> line preceding point).  If the
-<code>@node</code> line has pre-existing `Next', `Previous', or `Up'
+<code>@node</code> line has pre-existing &lsquo;Next&rsquo;, 
&lsquo;Previous&rsquo;, or &lsquo;Up&rsquo;
 pointers in it, the old pointers are removed and new ones inserted.
 With an argument (prefix argument, <kbd>C-u</kbd>, if interactive), this 
command
 updates all <code>@node</code> lines in the region (which is the text
@@ -225,7 +225,7 @@
 <dt> <kbd>C-c C-u C-e</kbd></dt>
 <dt> <kbd>M-x texinfo-every-node-update</kbd></dt>
 <dd><a name="IDX55"></a>
-<p>Insert or update the `Next', `Previous', and `Up' pointers for every
+<p>Insert or update the &lsquo;Next&rsquo;, &lsquo;Previous&rsquo;, and 
&lsquo;Up&rsquo; pointers for every
 node in the buffer.
 </p>
 </dd>
@@ -258,7 +258,7 @@
 column to which menu descriptions are indented.  By default, the value
 is 32 although it is often useful to reduce it to as low as 24.  You
 can set the variable with the <kbd>M-x edit-options</kbd> command
-(see <a href="../emacs/Edit-Options.html#Edit-Options">(emacs)Edit Options</a> 
section `Editing Variable Values' in <cite>The GNU Emacs Manual</cite>) or with 
the <kbd>M-x set-variable</kbd> command (see <a 
href="../emacs/Examining.html#Examining">(emacs)Examining</a> section 
`Examining and Setting Variables' in <cite>The GNU Emacs Manual</cite>).
+(see <a href="../emacs/Edit-Options.html#Edit-Options">(emacs)Edit Options</a> 
section &lsquo;Editing Variable Values&rsquo; in <cite>The GNU Emacs 
Manual</cite>) or with the <kbd>M-x set-variable</kbd> command (see <a 
href="../emacs/Examining.html#Examining">(emacs)Examining</a> section 
&lsquo;Examining and Setting Variables&rsquo; in <cite>The GNU Emacs 
Manual</cite>).
 </p>
 <p>Also, the <code>texinfo-indent-menu-description</code> command may be used 
to
 indent existing menu descriptions to a specified column.  Finally, if

Index: Tests/nodes_texinfo_res/Updating-Requirements.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/Updating-Requirements.html,v
retrieving revision 1.24
retrieving revision 1.25
diff -u -b -r1.24 -r1.25
--- Tests/nodes_texinfo_res/Updating-Requirements.html  5 Feb 2007 15:30:24 
-0000       1.24
+++ Tests/nodes_texinfo_res/Updating-Requirements.html  3 Oct 2007 09:34:45 
-0000       1.25
@@ -83,14 +83,14 @@
 
 <p>To use the updating commands, you must organize the Texinfo file
 hierarchically with chapters, sections, subsections, and the like.
-When you construct the hierarchy of the manual, do not `jump down'
-more than one level at a time: you can follow the `Top' node with a
+When you construct the hierarchy of the manual, do not &lsquo;jump down&rsquo;
+more than one level at a time: you can follow the &lsquo;Top&rsquo; node with a
 chapter, but not with a section; you can follow a chapter with a
-section, but not with a subsection.  However, you may `jump up' any
+section, but not with a subsection.  However, you may &lsquo;jump up&rsquo; any
 number of levels at one time&mdash;for example, from a subsection to a
 chapter.
 </p>
-<p>Each <code>@node</code> line, with the exception of the line for the `Top'
+<p>Each <code>@node</code> line, with the exception of the line for the 
&lsquo;Top&rsquo;
 node, must be followed by a line with a structuring command such as
 <code>@chapter</code>, <code>@section</code>, or
 <code>@unnumberedsubsec</code>.
@@ -115,22 +115,22 @@
 @section Comments
 </pre></td></tr></table>
 
-<p>In this example, `Comments' is the name of both the node and the
-section.  The next node is called `Minimum' and the previous node is
-called `Conventions'.  The `Comments' section is within the `Overview'
-node, which is specified by the `Up' pointer.  (Instead of an
+<p>In this example, &lsquo;Comments&rsquo; is the name of both the node and the
+section.  The next node is called &lsquo;Minimum&rsquo; and the previous node 
is
+called &lsquo;Conventions&rsquo;.  The &lsquo;Comments&rsquo; section is 
within the &lsquo;Overview&rsquo;
+node, which is specified by the &lsquo;Up&rsquo; pointer.  (Instead of an
 <code>@comment</code> line, you may also write an <code>@ifinfo</code> line.)
 </p>
-<p>If a file has a `Top' node, it must be called 
&lsquo;<samp>top</samp>&rsquo; or &lsquo;<samp>Top</samp>&rsquo;
+<p>If a file has a &lsquo;Top&rsquo; node, it must be called 
&lsquo;<samp>top</samp>&rsquo; or &lsquo;<samp>Top</samp>&rsquo;
 and be the first node in the file.
 </p>
 <p>The menu updating commands create a menu of sections within a chapter,
 a menu of subsections within a section, and so on.  This means that
-you must have a `Top' node if you want a menu of chapters.
+you must have a &lsquo;Top&rsquo; node if you want a menu of chapters.
 </p>
 <p>Incidentally, the <code>makeinfo</code> command will create an Info file 
for a
-hierarchically organized Texinfo file that lacks `Next', `Previous' and
-`Up' pointers.  Thus, if you can be sure that your Texinfo file will be
+hierarchically organized Texinfo file that lacks &lsquo;Next&rsquo;, 
&lsquo;Previous&rsquo; and
+&lsquo;Up&rsquo; pointers.  Thus, if you can be sure that your Texinfo file 
will be
 formatted with <code>makeinfo</code>, you have no need for the update node
 commands.  (See section <a href="Creating-an-Info-File.html#SEC261">Creating 
an Info File</a>, for more information about
 <code>makeinfo</code>.)  However, both <code>makeinfo</code> and the

Index: Tests/nodes_texinfo_res/Using-Include-Files.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/Using-Include-Files.html,v
retrieving revision 1.21
retrieving revision 1.22
diff -u -b -r1.21 -r1.22
--- Tests/nodes_texinfo_res/Using-Include-Files.html    5 Feb 2007 15:30:25 
-0000       1.21
+++ Tests/nodes_texinfo_res/Using-Include-Files.html    3 Oct 2007 09:34:46 
-0000       1.22
@@ -109,11 +109,11 @@
 and updating commands to create the node pointers and menus within the
 included file.  However, the simple Emacs node and menu creating and
 updating commands do not work with multiple Texinfo files.  Thus you
-cannot use these commands to fill in the `Next', `Previous', and `Up'
+cannot use these commands to fill in the &lsquo;Next&rsquo;, 
&lsquo;Previous&rsquo;, and &lsquo;Up&rsquo;
 pointers of the <code>@node</code> line that begins the included file.  Also,
 you cannot use the regular commands to create a master menu for the
-whole file.  Either you must insert the menus and the `Next',
-`Previous', and `Up' pointers by hand, or you must use the GNU Emacs
+whole file.  Either you must insert the menus and the &lsquo;Next&rsquo;,
+&lsquo;Previous&rsquo;, and &lsquo;Up&rsquo; pointers by hand, or you must use 
the GNU Emacs
 Texinfo mode command, <code>texinfo-multiple-files-update</code>, that is
 designed for <code>@include</code> files.
 </p>

Index: Tests/nodes_texinfo_res/Using-Info_002dvalidate.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/Using-Info_002dvalidate.html,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -b -r1.11 -r1.12
--- Tests/nodes_texinfo_res/Using-Info_002dvalidate.html        5 Feb 2007 
15:30:25 -0000       1.11
+++ Tests/nodes_texinfo_res/Using-Info_002dvalidate.html        3 Oct 2007 
09:34:46 -0000       1.12
@@ -88,7 +88,7 @@
 </pre></td></tr></table>
 
 <p>Note that the <code>Info-validate</code> command requires an upper case
-`I'.  You may also need to create a tag table before running
+&lsquo;I&rsquo;.  You may also need to create a tag table before running
 <code>Info-validate</code>.  See section <a 
href="Tagifying.html#SEC317">Tagifying a File</a>.
 </p>
 <p>If your file is valid, you will receive a message that says &ldquo;File 
appears
@@ -102,19 +102,19 @@
 <table><tr><td>&nbsp;</td><td><pre class="example">In node 
&quot;Overview&quot;, invalid Next: Texinfo Mode
 </pre></td></tr></table>
 
-<p>This meant that the node called &lsquo;<samp>Overview</samp>&rsquo; had a 
`Next' pointer that
+<p>This meant that the node called &lsquo;<samp>Overview</samp>&rsquo; had a 
&lsquo;Next&rsquo; pointer that
 did not point to anything (which was true in this case, since the test file
 had only one node in it).
 </p>
 <p>Now suppose we add a node named &lsquo;<samp>Texinfo Mode</samp>&rsquo; to 
our test case
-but we do not specify a `Previous' for this node.  Then we will get
+but we do not specify a &lsquo;Previous&rsquo; for this node.  Then we will get
 the following error message:
 </p>
 <table><tr><td>&nbsp;</td><td><pre class="example">In node &quot;Texinfo 
Mode&quot;, should have Previous: Overview
 </pre></td></tr></table>
 
-<p>This is because every `Next' pointer should be matched by a
-`Previous' (in the node where the `Next' points) which points back.
+<p>This is because every &lsquo;Next&rsquo; pointer should be matched by a
+&lsquo;Previous&rsquo; (in the node where the &lsquo;Next&rsquo; points) which 
points back.
 </p>
 <p><code>Info-validate</code> also checks that all menu entries and cross 
references
 point to actual nodes.

Index: Tests/nodes_texinfo_res/Using-Texinfo.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/Using-Texinfo.html,v
retrieving revision 1.21
retrieving revision 1.22
diff -u -b -r1.21 -r1.22
--- Tests/nodes_texinfo_res/Using-Texinfo.html  5 Feb 2007 15:30:25 -0000       
1.21
+++ Tests/nodes_texinfo_res/Using-Texinfo.html  3 Oct 2007 09:34:46 -0000       
1.22
@@ -92,13 +92,13 @@
 </p>
 <p>To make a printed document, you process a Texinfo source file with the
 TeX typesetting program (but the Texinfo language is very different
-and much stricter than TeX's usual language, plain TeX).  This
+and much stricter than TeX&rsquo;s usual language, plain TeX).  This
 creates a DVI file that you can typeset and print as a book or report
 (see section <a href="Hardcopy.html#SEC244">Formatting and Printing 
Hardcopy</a>).
 </p>
 <a name="IDX3"></a>
 <p>To output an Info file, process your Texinfo source with the
-<code>makeinfo</code> utility or Emacs's <code>texinfo-format-buffer</code> 
command.
+<code>makeinfo</code> utility or Emacs&rsquo;s 
<code>texinfo-format-buffer</code> command.
 You can install the result in your Info tree (see section <a 
href="Installing-an-Info-File.html#SEC271">Installing an Info File</a>).
 </p>
 <p>To output an HTML file, run <code>makeinfo --html</code> on your Texinfo
@@ -161,7 +161,7 @@
 program <code>help2man</code> may be useful; it generates a traditional man
 page from the &lsquo;<samp>--help</samp>&rsquo; output of a program.  In fact, 
this is
 currently used to generate man pages for the Texinfo programs
-themselves.  It is GNU software written by Brendan O'Dea, available from
+themselves.  It is GNU software written by Brendan O&rsquo;Dea, available from
 <a href="ftp://ftp.gnu.org/gnu/help2man/";>ftp://ftp.gnu.org/gnu/help2man/</a>.
 </p>
 

Index: Tests/nodes_texinfo_res/Using-occur.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/Using-occur.html,v
retrieving revision 1.21
retrieving revision 1.22
diff -u -b -r1.21 -r1.22
--- Tests/nodes_texinfo_res/Using-occur.html    5 Feb 2007 15:30:25 -0000       
1.21
+++ Tests/nodes_texinfo_res/Using-occur.html    3 Oct 2007 09:34:46 -0000       
1.22
@@ -91,7 +91,7 @@
 </pre></td></tr></table>
 
 <p>and then, when prompted, type a <em>regexp</em>, a regular expression for
-the pattern you want to match.  (See <a 
href="../emacs/Regexps.html#Regexps">(emacs)Regexps</a> section `Regular 
Expressions' in <cite>The GNU Emacs Manual</cite>.)  The <code>occur</code> 
command works from
+the pattern you want to match.  (See <a 
href="../emacs/Regexps.html#Regexps">(emacs)Regexps</a> section &lsquo;Regular 
Expressions&rsquo; in <cite>The GNU Emacs Manual</cite>.)  The 
<code>occur</code> command works from
 the current location of the cursor in the buffer to the end of the
 buffer.  If you want to run <code>occur</code> on the whole buffer, place
 the cursor at the beginning of the buffer.
@@ -107,9 +107,9 @@
 or phrase, end the last word with a &lsquo;<samp>$</samp>&rsquo;; for example,
 &lsquo;<samp>catching mistakes$</samp>&rsquo;.  This can be helpful when you 
want to see
 all the nodes that are part of the same chapter or section and
-therefore have the same `Up' pointer.
+therefore have the same &lsquo;Up&rsquo; pointer.
 </p>
-<p>See <a 
href="../emacs/Other-Repeating-Search.html#Other-Repeating-Search">(emacs)Other 
Repeating Search</a> section `Using Occur' in <cite>The GNU Emacs Manual</cite>,
+<p>See <a 
href="../emacs/Other-Repeating-Search.html#Other-Repeating-Search">(emacs)Other 
Repeating Search</a> section &lsquo;Using Occur&rsquo; in <cite>The GNU Emacs 
Manual</cite>,
 for more information.
 </p>
 <hr size="1">

Index: Tests/nodes_texinfo_res/Using-texinfo_002dshow_002dstructure.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/Using-texinfo_002dshow_002dstructure.html,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -b -r1.11 -r1.12
--- Tests/nodes_texinfo_res/Using-texinfo_002dshow_002dstructure.html   5 Feb 
2007 15:30:25 -0000       1.11
+++ Tests/nodes_texinfo_res/Using-texinfo_002dshow_002dstructure.html   3 Oct 
2007 09:34:46 -0000       1.12
@@ -117,20 +117,20 @@
 commands respectively.  If you move your cursor into the 
&lsquo;<samp>*Occur*</samp>&rsquo;
 window, you can position the cursor over one of the lines and use the
 <kbd>C-c C-c</kbd> command (<code>occur-mode-goto-occurrence</code>), to jump 
to
-the corresponding spot in the Texinfo file.  See <a 
href="../emacs/Other-Repeating-Search.html#Other-Repeating-Search">(emacs)Other 
Repeating Search</a> section `Using Occur' in <cite>The GNU Emacs 
Manual</cite>, for more
+the corresponding spot in the Texinfo file.  See <a 
href="../emacs/Other-Repeating-Search.html#Other-Repeating-Search">(emacs)Other 
Repeating Search</a> section &lsquo;Using Occur&rsquo; in <cite>The GNU Emacs 
Manual</cite>, for more
 information about <code>occur-mode-goto-occurrence</code>.
 </p>
 <p>The first line in the &lsquo;<samp>*Occur*</samp>&rsquo; window describes 
the <em>regular
 expression</em> specified by <var>texinfo-heading-pattern</var>.  This regular
 expression is the pattern that <code>texinfo-show-structure</code> looks for.
-See <a href="../emacs/Regexps.html#Regexps">(emacs)Regexps</a> section `Using 
Regular Expressions' in <cite>The GNU Emacs Manual</cite>,
+See <a href="../emacs/Regexps.html#Regexps">(emacs)Regexps</a> section 
&lsquo;Using Regular Expressions&rsquo; in <cite>The GNU Emacs Manual</cite>,
 for more information.
 </p>
 <p>When you invoke the <code>texinfo-show-structure</code> command, Emacs will
 display the structure of the whole buffer.  If you want to see the
 structure of just a part of the buffer, of one chapter, for example,
 use the <kbd>C-x n n</kbd> (<code>narrow-to-region</code>) command to mark the
-region.  (See <a href="../emacs/Narrowing.html#Narrowing">(emacs)Narrowing</a> 
section `Narrowing' in <cite>The GNU Emacs Manual</cite>.)  This is
+region.  (See <a href="../emacs/Narrowing.html#Narrowing">(emacs)Narrowing</a> 
section &lsquo;Narrowing&rsquo; in <cite>The GNU Emacs Manual</cite>.)  This is
 how the example used above was generated.  (To see the whole buffer
 again, use <kbd>C-x n w</kbd> (<code>widen</code>).)
 </p>

Index: Tests/nodes_texinfo_res/Variables-Commands.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/Variables-Commands.html,v
retrieving revision 1.26
retrieving revision 1.27
diff -u -b -r1.26 -r1.27
--- Tests/nodes_texinfo_res/Variables-Commands.html     5 Feb 2007 15:30:25 
-0000       1.26
+++ Tests/nodes_texinfo_res/Variables-Commands.html     3 Oct 2007 09:34:46 
-0000       1.27
@@ -150,7 +150,7 @@
 <dd><a name="IDX273"></a>
 <p>The <code>@defopt</code> command is the definition command for <em>user
 options</em>, i.e., variables intended for users to change according to
-taste; Emacs has many such (see <a 
href="../emacs/Variables.html#Variables">(emacs)Variables</a> section 
`Variables' in <cite>The GNU Emacs Manual</cite>).  <code>@defopt</code> is 
equivalent to &lsquo;<samp>@defvr {User
+taste; Emacs has many such (see <a 
href="../emacs/Variables.html#Variables">(emacs)Variables</a> section 
&lsquo;Variables&rsquo; in <cite>The GNU Emacs Manual</cite>).  
<code>@defopt</code> is equivalent to &lsquo;<samp>@defvr {User
 Option} &hellip;</samp>&rsquo; and works like <code>@defvar</code>.
 </p></dd>
 </dl>

Index: Tests/nodes_texinfo_res/Writing-a-Node.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/Writing-a-Node.html,v
retrieving revision 1.22
retrieving revision 1.23
diff -u -b -r1.22 -r1.23
--- Tests/nodes_texinfo_res/Writing-a-Node.html 5 Feb 2007 15:30:25 -0000       
1.22
+++ Tests/nodes_texinfo_res/Writing-a-Node.html 3 Oct 2007 09:34:46 -0000       
1.23
@@ -93,7 +93,7 @@
 can leave the pointers out of the Texinfo file and let <code>makeinfo</code>
 insert node pointers into the Info file it creates.  (See section <a 
href="Texinfo-Mode.html#SEC21">Using Texinfo Mode</a>, and <a 
href="makeinfo-Pointer-Creation.html#SEC95">Creating Pointers with 
<code>makeinfo</code></a>.)
 </p>
-<p>Alternatively, you can insert the `Next', `Previous', and `Up'
+<p>Alternatively, you can insert the &lsquo;Next&rsquo;, 
&lsquo;Previous&rsquo;, and &lsquo;Up&rsquo;
 pointers yourself.  If you do this, you may find it helpful to use the
 Texinfo mode keyboard command <kbd>C-c C-c n</kbd>.  This command inserts
 &lsquo;<samp>@node</samp>&rsquo; and a comment line listing the names of the 
pointers in
@@ -101,8 +101,8 @@
 arguments are for which pointers.  This comment line is especially useful
 if you are not familiar with Texinfo.
 </p>
-<p>The template for a fully-written-out node line with `Next', `Previous',
-and `Up' pointers looks like this:
+<p>The template for a fully-written-out node line with &lsquo;Next&rsquo;, 
&lsquo;Previous&rsquo;,
+and &lsquo;Up&rsquo; pointers looks like this:
 </p>
 <table><tr><td>&nbsp;</td><td><pre class="example">@node <var>node-name</var>, 
<var>next</var>, <var>previous</var>, <var>up</var>
 </pre></td></tr></table>

Index: Tests/nodes_texinfo_res/_002d-and-hyphenation.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/_002d-and-hyphenation.html,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -b -r1.12 -r1.13
--- Tests/nodes_texinfo_res/_002d-and-hyphenation.html  5 Feb 2007 15:30:25 
-0000       1.12
+++ Tests/nodes_texinfo_res/_002d-and-hyphenation.html  3 Oct 2007 09:34:46 
-0000       1.13
@@ -82,7 +82,7 @@
 <h2 class="section"> 14.2 <code>@-</code> and <code>@hyphenation</code>: 
Helping TeX hyphenate </h2>
 
 
-<p>Although TeX's hyphenation algorithm is generally pretty good, it
+<p>Although TeX&rsquo;s hyphenation algorithm is generally pretty good, it
 does miss useful hyphenation points from time to time.  (Or, far more
 rarely, insert an incorrect hyphenation.)  So, for documents with an
 unusual vocabulary or when fine-tuning for a printed edition, you may

Index: Tests/nodes_texinfo_res/acronym.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/acronym.html,v
retrieving revision 1.20
retrieving revision 1.21
diff -u -b -r1.20 -r1.21
--- Tests/nodes_texinfo_res/acronym.html        5 Feb 2007 15:30:25 -0000       
1.20
+++ Tests/nodes_texinfo_res/acronym.html        3 Oct 2007 09:34:46 -0000       
1.21
@@ -82,7 +82,7 @@
 <h3 class="subsection"> 9.1.13 <code>@acronym</code>{<var>acronym</var>} </h3>
 
 <p>Use the <code>@acronym</code> command for abbreviations written in all
-capital letters, such as `<acronym>NASA</acronym>'.  The abbreviation is given 
as
+capital letters, such as &lsquo;<acronym>NASA</acronym>&rsquo;.  The 
abbreviation is given as
 the single argument in braces, as in 
&lsquo;<samp>@acronym{NASA}</samp>&rsquo;.  As
 a matter of style, or for particular abbreviations, you may prefer to
 use periods, as in &lsquo;<samp>@acronym{F.B.I.}</samp>&rsquo;.

Index: Tests/nodes_texinfo_res/alias.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/alias.html,v
retrieving revision 1.20
retrieving revision 1.21
diff -u -b -r1.20 -r1.21
--- Tests/nodes_texinfo_res/alias.html  5 Feb 2007 15:30:25 -0000       1.20
+++ Tests/nodes_texinfo_res/alias.html  3 Oct 2007 09:34:46 -0000       1.21
@@ -96,7 +96,7 @@
 some other media (movies, for example), you might like to define a
 macro <code>@moviecite{}</code> that does the same thing as an ordinary
 <code>@cite{}</code> but conveys the extra semantic information as well.
-You'd do this as follows:
+You&rsquo;d do this as follows:
 </p>
 <table><tr><td>&nbsp;</td><td><pre class="example">@alias moviecite = cite
 </pre></td></tr></table>

Index: Tests/nodes_texinfo_res/anchor.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/anchor.html,v
retrieving revision 1.20
retrieving revision 1.21
diff -u -b -r1.20 -r1.21
--- Tests/nodes_texinfo_res/anchor.html 5 Feb 2007 15:30:25 -0000       1.20
+++ Tests/nodes_texinfo_res/anchor.html 3 Oct 2007 09:34:46 -0000       1.21
@@ -100,13 +100,13 @@
 </pre></td></tr></table>
 
 <p>As you can see, the <code>@anchor</code> command itself produces no output.
-This example defines an anchor `x-spot' just before the word `spot'.
+This example defines an anchor &lsquo;x-spot&rsquo; just before the word 
&lsquo;spot&rsquo;.
 You can refer to it later with an <code>@xref</code> or other cross-reference
 command, as shown.  See section <a href="Cross-References.html#SEC104">Cross 
References</a>, for details on the
 cross-reference commands.
 </p>
 <p>It is best to put <code>@anchor</code> commands just before the position you
-wish to refer to; that way, the reader's eye is led on to the correct
+wish to refer to; that way, the reader&rsquo;s eye is led on to the correct
 text when they jump to the anchor.  You can put the <code>@anchor</code>
 command on a line by itself if that helps readability of the source.
 Spaces are always ignored after <code>@anchor</code>.
@@ -114,7 +114,7 @@
 <p>Anchor names and node names may not conflict.  Anchors and nodes are
 given similar treatment in some ways; for example, the <code>goto-node</code>
 command in standalone Info takes either an anchor name or a node name as
-an argument.  (See <a 
href="../info-stnd/goto_002dnode.html#goto_002dnode">(info-stnd)goto-node</a> 
section `goto-node' in <cite>GNU Info</cite>.)
+an argument.  (See <a 
href="../info-stnd/goto_002dnode.html#goto_002dnode">(info-stnd)goto-node</a> 
section &lsquo;goto-node&rsquo; in <cite>GNU Info</cite>.)
 </p>
 
 <hr size="1">

Index: Tests/nodes_texinfo_res/command.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/command.html,v
retrieving revision 1.21
retrieving revision 1.22
diff -u -b -r1.21 -r1.22
--- Tests/nodes_texinfo_res/command.html        5 Feb 2007 15:30:25 -0000       
1.21
+++ Tests/nodes_texinfo_res/command.html        3 Oct 2007 09:34:46 -0000       
1.22
@@ -95,7 +95,7 @@
 
 <p>You should write the name of a program in the ordinary text font, rather
 than using <code>@command</code>, if you regard it as a new English word,
-such as `Emacs' or `Bison'.
+such as &lsquo;Emacs&rsquo; or &lsquo;Bison&rsquo;.
 </p>
 <p>When writing an entire shell command invocation, as in &lsquo;<samp>ls 
-l</samp>&rsquo;,
 you should use either <code>@samp</code> or <code>@code</code> at your 
discretion.

Index: Tests/nodes_texinfo_res/copying.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/copying.html,v
retrieving revision 1.22
retrieving revision 1.23
diff -u -b -r1.22 -r1.23
--- Tests/nodes_texinfo_res/copying.html        5 Feb 2007 15:30:25 -0000       
1.22
+++ Tests/nodes_texinfo_res/copying.html        3 Oct 2007 09:34:46 -0000       
1.23
@@ -99,7 +99,7 @@
 @end copying
 </pre></td></tr></table>
 
-<p>The <code>@quotation</code> has no legal significance; it's there to improve
+<p>The <code>@quotation</code> has no legal significance; it&rsquo;s there to 
improve
 readability in some contexts.
 </p>
 <p>See section <a href="GNU-Sample-Texts.html#SEC296">GNU Sample Texts</a>, 
for the full text to be used in GNU manuals.
@@ -108,7 +108,7 @@
 </p>
 <p>The text of <code>@copying</code> is output as a comment at the beginning of
 Info, HTML, and XML output files.  It is <em>not</em> output implicitly in
-plain text or TeX; it's up to you to use <code>@insertcopying</code> to
+plain text or TeX; it&rsquo;s up to you to use <code>@insertcopying</code> to
 emit the copying information.  See the next section for details.
 </p>
 <a name="IDX73"></a>
@@ -121,7 +121,7 @@
 </pre></td></tr></table>
 
 <a name="IDX74"></a>
-<p>The word `Copyright' must always be written in English, even if the
+<p>The word &lsquo;Copyright&rsquo; must always be written in English, even if 
the
 manual is otherwise in another language.  This is due to international
 law.
 </p>
@@ -133,10 +133,10 @@
 </p>
 <a name="IDX76"></a>
 <p>The copyright owner (or owners) is whoever holds legal copyright on the
-work.  In the case of works assigned to the FSF, the owner is `Free
-Software Foundation, Inc.'.
+work.  In the case of works assigned to the FSF, the owner is &lsquo;Free
+Software Foundation, Inc.&rsquo;.
 </p>
-<p>See <a 
href="../maintain/Copyright-Notices.html#Copyright-Notices">(maintain)Copyright 
Notices</a> section `Copyright Notices' in <cite>GNU Maintenance 
Instructions</cite>, for
+<p>See <a 
href="../maintain/Copyright-Notices.html#Copyright-Notices">(maintain)Copyright 
Notices</a> section &lsquo;Copyright Notices&rsquo; in <cite>GNU Maintenance 
Instructions</cite>, for
 additional information.
 </p>
 

Index: Tests/nodes_texinfo_res/copyright-symbol.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/copyright-symbol.html,v
retrieving revision 1.22
retrieving revision 1.23
diff -u -b -r1.22 -r1.23
--- Tests/nodes_texinfo_res/copyright-symbol.html       5 Feb 2007 15:30:25 
-0000       1.22
+++ Tests/nodes_texinfo_res/copyright-symbol.html       3 Oct 2007 09:34:46 
-0000       1.23
@@ -81,7 +81,7 @@
 <hr size="1">
 <h3 class="subsection"> 13.5.2 <code>@copyright</code>{} (&copy;) </h3>
 
-<p>Use the <code>@copyright{}</code> command to generate `&copy;'.  In
+<p>Use the <code>@copyright{}</code> command to generate &lsquo;&copy;&rsquo;. 
 In
 a printed manual, this is a &lsquo;<samp>c</samp>&rsquo; inside a circle, and 
in Info,
 this is &lsquo;<samp>(C)</samp>&rsquo;.
 </p>

Index: Tests/nodes_texinfo_res/deffnx.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/deffnx.html,v
retrieving revision 1.20
retrieving revision 1.21
diff -u -b -r1.20 -r1.21
--- Tests/nodes_texinfo_res/deffnx.html 5 Feb 2007 15:30:25 -0000       1.20
+++ Tests/nodes_texinfo_res/deffnx.html 3 Oct 2007 09:34:46 -0000       1.21
@@ -79,9 +79,9 @@
 <td valign="middle" align="left">[<a href="texinfo_abt.html#SEC_About" 
title="About (help)"> ? </a>]</td>
 </tr></table>
 <hr size="1">
-<h2 class="section"> 15.3 Two or More `First' Lines </h2>
+<h2 class="section"> 15.3 Two or More &lsquo;First&rsquo; Lines </h2>
 
-<p>To create two or more `first' or header lines for a definition, follow
+<p>To create two or more &lsquo;first&rsquo; or header lines for a definition, 
follow
 the first <code>@deffn</code> line by a line beginning with 
<code>@deffnx</code>.
 The <code>@deffnx</code> command works exactly like <code>@deffn</code>
 except that it does not generate extra vertical white space between it
@@ -107,10 +107,10 @@
 <dd><p>These two search commands are similar except &hellip;
 </p></dd></dl>
 
-<p>Each definition command has an `x' form: <code>@defunx</code>,
+<p>Each definition command has an &lsquo;x&rsquo; form: <code>@defunx</code>,
 <code>@defvrx</code>, <code>@deftypefunx</code>, etc.
 </p>
-<p>The `x' forms work just like <code>@itemx</code>; see <a 
href="itemx.html#SEC162"><code>@itemx</code></a>.
+<p>The &lsquo;x&rsquo; forms work just like <code>@itemx</code>; see <a 
href="itemx.html#SEC162"><code>@itemx</code></a>.
 </p>
 <hr size="1">
 <p>

Index: Tests/nodes_texinfo_res/definfoenclose.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/definfoenclose.html,v
retrieving revision 1.20
retrieving revision 1.21
diff -u -b -r1.20 -r1.21
--- Tests/nodes_texinfo_res/definfoenclose.html 5 Feb 2007 15:30:25 -0000       
1.20
+++ Tests/nodes_texinfo_res/definfoenclose.html 3 Oct 2007 09:34:46 -0000       
1.21
@@ -118,9 +118,9 @@
 </pre></td></tr></table>
 
 <p>near the beginning of a Texinfo file to define <code>@phoo</code> as an Info
-formatting command that inserts `//' before and `\\' after the argument
+formatting command that inserts &lsquo;//&rsquo; before and &lsquo;\\&rsquo; 
after the argument
 to <code>@phoo</code>.  You can then write <code>@phoo{bar}</code> wherever you
-want `//bar\\' highlighted in Info.
+want &lsquo;//bar\\&rsquo; highlighted in Info.
 </p>
 <p>Also, for TeX formatting, you could write 
 </p>

Index: Tests/nodes_texinfo_res/documentlanguage.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/documentlanguage.html,v
retrieving revision 1.21
retrieving revision 1.22
diff -u -b -r1.21 -r1.22
--- Tests/nodes_texinfo_res/documentlanguage.html       5 Feb 2007 15:30:25 
-0000       1.21
+++ Tests/nodes_texinfo_res/documentlanguage.html       3 Oct 2007 09:34:46 
-0000       1.22
@@ -93,10 +93,10 @@
 <p>At present, this command is ignored in Info and HTML output.  For
 TeX, it causes the file &lsquo;<tt>txi-<var>cc</var>.tex</tt>&rsquo; to be 
read (if it
 exists).  Such a file appropriately redefines the various English words
-used in TeX output, such as `Chapter', `See', and so on.
+used in TeX output, such as &lsquo;Chapter&rsquo;, &lsquo;See&rsquo;, and so 
on.
 </p>
 <a name="IDX298"></a>
-<p>It would be good if this command also changed TeX's ideas of the
+<p>It would be good if this command also changed TeX&rsquo;s ideas of the
 current hyphenation patterns (via the TeX primitive
 <code>\language</code>), but this is unfortunately not currently implemented.
 </p>

Index: Tests/nodes_texinfo_res/dots.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/dots.html,v
retrieving revision 1.21
retrieving revision 1.22
diff -u -b -r1.21 -r1.22
--- Tests/nodes_texinfo_res/dots.html   30 Sep 2007 12:47:37 -0000      1.21
+++ Tests/nodes_texinfo_res/dots.html   3 Oct 2007 09:34:46 -0000       1.22
@@ -82,7 +82,7 @@
 <h3 class="subsection"> 13.4.1 <code>@dots</code>{} (&hellip;) and 
<code>@enddots</code>{} (<small class="enddots">...</small>) </h3>
 
 <p>Use the <code>@dots{}</code> command to generate an ellipsis, which is
-three dots in a row, appropriately spaced, like this: `&hellip;'.  Do
+three dots in a row, appropriately spaced, like this: &lsquo;&hellip;&rsquo;.  
Do
 not simply write three periods in the input file; that would work for
 the Info file output, but would produce the wrong amount of space
 between the periods in the printed manual.

Index: Tests/nodes_texinfo_res/emph-_0026-strong.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/emph-_0026-strong.html,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -b -r1.11 -r1.12
--- Tests/nodes_texinfo_res/emph-_0026-strong.html      5 Feb 2007 15:30:25 
-0000       1.11
+++ Tests/nodes_texinfo_res/emph-_0026-strong.html      3 Oct 2007 09:34:46 
-0000       1.12
@@ -100,7 +100,7 @@
 </pre></td></tr></table>
 
 <p>The <code>@strong</code> command is seldom used except to mark what is, in
-effect, a typographical element, such as the word `Caution' in the
+effect, a typographical element, such as the word &lsquo;Caution&rsquo; in the
 preceding example.
 </p>
 <p>In the Info output, <code>@emph</code> surrounds the text with underscores

Index: Tests/nodes_texinfo_res/exdent.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/exdent.html,v
retrieving revision 1.20
retrieving revision 1.21
diff -u -b -r1.20 -r1.21
--- Tests/nodes_texinfo_res/exdent.html 5 Feb 2007 15:30:25 -0000       1.20
+++ Tests/nodes_texinfo_res/exdent.html 3 Oct 2007 09:34:46 -0000       1.21
@@ -79,7 +79,7 @@
 <td valign="middle" align="left">[<a href="texinfo_abt.html#SEC_About" 
title="About (help)"> ? </a>]</td>
 </tr></table>
 <hr size="1">
-<h2 class="section"> 10.10 <code>@exdent</code>: Undoing a Line's Indentation 
</h2>
+<h2 class="section"> 10.10 <code>@exdent</code>: Undoing a Line&rsquo;s 
Indentation </h2>
 
 <p>The <code>@exdent</code> command removes any indentation a line might have.
 The command is written at the beginning of a line and applies only to

Index: Tests/nodes_texinfo_res/ifset-ifclear.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/ifset-ifclear.html,v
retrieving revision 1.21
retrieving revision 1.22
diff -u -b -r1.21 -r1.22
--- Tests/nodes_texinfo_res/ifset-ifclear.html  5 Feb 2007 15:30:25 -0000       
1.21
+++ Tests/nodes_texinfo_res/ifset-ifclear.html  3 Oct 2007 09:34:46 -0000       
1.22
@@ -96,7 +96,7 @@
 </pre></td></tr></table>
 
 <p>For example, you can create one document that has two variants, such as
-a manual for a `large' and `small' model:
+a manual for a &lsquo;large&rsquo; and &lsquo;small&rsquo; model:
 </p>
 <a name="IDX295"></a>
 <table><tr><td>&nbsp;</td><td><pre class="example">You can use this machine to 
dig up shrubs

Index: Tests/nodes_texinfo_res/insertcopying.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/insertcopying.html,v
retrieving revision 1.19
retrieving revision 1.20
diff -u -b -r1.19 -r1.20
--- Tests/nodes_texinfo_res/insertcopying.html  5 Feb 2007 15:30:25 -0000       
1.19
+++ Tests/nodes_texinfo_res/insertcopying.html  3 Oct 2007 09:34:46 -0000       
1.20
@@ -91,8 +91,8 @@
 must be used on the copyright page in the printed manual
 (see section <a href="Copyright.html#SEC56">Copyright Page</a>).
 </p>
-<p>Although it's not a legal requirement, we also strongly recommend using
-<code>@insertcopying</code> in the Top node of your manual (see section <a 
href="The-Top-Node.html#SEC59">The `Top' Node and Master Menu</a>).  Here's why:
+<p>Although it&rsquo;s not a legal requirement, we also strongly recommend 
using
+<code>@insertcopying</code> in the Top node of your manual (see section <a 
href="The-Top-Node.html#SEC59">The &lsquo;Top&rsquo; Node and Master Menu</a>). 
 Here&rsquo;s why:
 </p>
 <p>The <code>@copying</code> command itself causes the permissions text to
 appear in an Info file <em>before</em> the first node.  The text is also

Index: Tests/nodes_texinfo_res/itemize.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/itemize.html,v
retrieving revision 1.27
retrieving revision 1.28
diff -u -b -r1.27 -r1.28
--- Tests/nodes_texinfo_res/itemize.html        5 Feb 2007 15:30:25 -0000       
1.27
+++ Tests/nodes_texinfo_res/itemize.html        3 Oct 2007 09:34:47 -0000       
1.28
@@ -91,10 +91,10 @@
 Texinfo command that generates a mark.  Usually, you will write
 <code>@bullet</code> after <code>@itemize</code>, but you can use
 <code>@minus</code>, or any command or character that results in a single
-character in the Info file.  If you don't want any mark at all, use
+character in the Info file.  If you don&rsquo;t want any mark at all, use
 <code>@w</code>.  (When you write the mark command such as
 <code>@bullet</code> after an <code>@itemize</code> command, you may omit the
-&lsquo;<samp>{}</samp>&rsquo;.)  If you don't specify a mark command, the 
default is
+&lsquo;<samp>{}</samp>&rsquo;.)  If you don&rsquo;t specify a mark command, 
the default is
 <code>@bullet</code>.
 </p>
 <p>Write the text of the indented paragraphs themselves after the

Index: Tests/nodes_texinfo_res/key.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/key.html,v
retrieving revision 1.24
retrieving revision 1.25
diff -u -b -r1.24 -r1.25
--- Tests/nodes_texinfo_res/key.html    5 Feb 2007 15:30:25 -0000       1.24
+++ Tests/nodes_texinfo_res/key.html    3 Oct 2007 09:34:47 -0000       1.25
@@ -138,7 +138,7 @@
 </blockquote>
 
 <a name="IDX130"></a>
-<p>There are subtleties to handling words like `meta' or `ctrl' that are
+<p>There are subtleties to handling words like &lsquo;meta&rsquo; or 
&lsquo;ctrl&rsquo; that are
 names of modifier keys.  When mentioning a character in which the
 modifier key is used, such as <kbd>Meta-a</kbd>, use the <code>@kbd</code> 
command
 alone; do not use the <code>@key</code> command; but when you are referring

Index: Tests/nodes_texinfo_res/makeinfo-Pointer-Creation.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/makeinfo-Pointer-Creation.html,v
retrieving revision 1.18
retrieving revision 1.19
diff -u -b -r1.18 -r1.19
--- Tests/nodes_texinfo_res/makeinfo-Pointer-Creation.html      5 Feb 2007 
15:30:25 -0000       1.18
+++ Tests/nodes_texinfo_res/makeinfo-Pointer-Creation.html      3 Oct 2007 
09:34:47 -0000       1.19
@@ -85,18 +85,18 @@
 node pointers for a hierarchically organized file.
 </p>
 <p>When you take advantage of this feature, you do not need to write the
-`Next', `Previous', and `Up' pointers after the name of a node.
+&lsquo;Next&rsquo;, &lsquo;Previous&rsquo;, and &lsquo;Up&rsquo; pointers 
after the name of a node.
 However, you must write a sectioning command, such as <code>@chapter</code>
 or <code>@section</code>, on the line immediately following each truncated
 <code>@node</code> line (except that comment lines may intervene).
 </p>
-<p>In addition, you must follow the `Top' <code>@node</code> line with a line
-beginning with <code>@top</code> to mark the `Top' node in the
+<p>In addition, you must follow the &lsquo;Top&rsquo; <code>@node</code> line 
with a line
+beginning with <code>@top</code> to mark the &lsquo;Top&rsquo; node in the
 file.  See section <a href="makeinfo-top.html#SEC75"><code>@top</code></a>.
 </p>
-<p>Finally, you must write the name of each node (except for the `Top'
+<p>Finally, you must write the name of each node (except for the 
&lsquo;Top&rsquo;
 node) in a menu that is one or more hierarchical levels above the
-node's hierarchical level.
+node&rsquo;s hierarchical level.
 </p>
 <p>This node pointer insertion feature in <code>makeinfo</code> relieves you 
from
 the need to update menus and pointers manually or with Texinfo mode

Index: Tests/nodes_texinfo_res/makeinfo-html.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/makeinfo-html.html,v
retrieving revision 1.20
retrieving revision 1.21
diff -u -b -r1.20 -r1.21
--- Tests/nodes_texinfo_res/makeinfo-html.html  5 Feb 2007 15:30:25 -0000       
1.20
+++ Tests/nodes_texinfo_res/makeinfo-html.html  3 Oct 2007 09:34:47 -0000       
1.21
@@ -94,7 +94,7 @@
 for any reason, then &lsquo;<samp>.html</samp>&rsquo; is appended to the 
directory name, as
 in &lsquo;<samp>emacs.html</samp>&rsquo; (this is necessary because sometimes 
the info file
 is named without an extension, e.g., &lsquo;<samp>texinfo</samp>&rsquo;).  If 
the
-&lsquo;<samp><var>name</var>.html</samp>&rsquo; directory can't be created 
either,
+&lsquo;<samp><var>name</var>.html</samp>&rsquo; directory can&rsquo;t be 
created either,
 <code>makeinfo</code> gives up.  In any case, the top-level output file within
 the directory is always named &lsquo;<samp>index.html</samp>&rsquo;.
 </p>

Index: Tests/nodes_texinfo_res/makeinfo-in-Emacs.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/makeinfo-in-Emacs.html,v
retrieving revision 1.25
retrieving revision 1.26
diff -u -b -r1.25 -r1.26
--- Tests/nodes_texinfo_res/makeinfo-in-Emacs.html      5 Feb 2007 15:30:25 
-0000       1.25
+++ Tests/nodes_texinfo_res/makeinfo-in-Emacs.html      3 Oct 2007 09:34:47 
-0000       1.26
@@ -117,7 +117,7 @@
 <p>You can parse the error messages by typing <kbd>C-x `</kbd>
 (<code>next-error</code>).  This causes Emacs to go to and position the
 cursor on the line in the Texinfo source that <code>makeinfo</code> thinks
-caused the error.  See <a 
href="../emacs/Compilation.html#Compilation">(emacs)Compilation</a> section 
`Running <code>make</code> or Compilers Generally' in <cite>The GNU Emacs 
Manual</cite>, for more
+caused the error.  See <a 
href="../emacs/Compilation.html#Compilation">(emacs)Compilation</a> section 
&lsquo;Running <code>make</code> or Compilers Generally&rsquo; in <cite>The GNU 
Emacs Manual</cite>, for more
 information about using the <code>next-error</code> command.
 </p>
 <p>In addition, you can kill the shell in which the <code>makeinfo</code>
@@ -156,9 +156,9 @@
 </pre></td></tr></table>
 
 <p>For more information, see<br>
-<a href="../emacs/Edit-Options.html#Edit-Options">(emacs)Edit Options</a> 
section `Editing Variable Values' in <cite>The GNU Emacs Manual</cite>,<br>
-<a href="../emacs/Examining.html#Examining">(emacs)Examining</a> section 
`Examining and Setting Variables' in <cite>The GNU Emacs Manual</cite>,<br>
-<a href="../emacs/Init-File.html#Init-File">(emacs)Init File</a> section `Init 
File' in <cite>The GNU Emacs Manual</cite>, and<br>
+<a href="../emacs/Edit-Options.html#Edit-Options">(emacs)Edit Options</a> 
section &lsquo;Editing Variable Values&rsquo; in <cite>The GNU Emacs 
Manual</cite>,<br>
+<a href="../emacs/Examining.html#Examining">(emacs)Examining</a> section 
&lsquo;Examining and Setting Variables&rsquo; in <cite>The GNU Emacs 
Manual</cite>,<br>
+<a href="../emacs/Init-File.html#Init-File">(emacs)Init File</a> section 
&lsquo;Init File&rsquo; in <cite>The GNU Emacs Manual</cite>, and<br>
 <a href="makeinfo-options.html#SEC264">Options for <code>makeinfo</code></a>.
 </p>
 <hr size="1">

Index: Tests/nodes_texinfo_res/makeinfo-top-command.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/makeinfo-top-command.html,v
retrieving revision 1.19
retrieving revision 1.20
diff -u -b -r1.19 -r1.20
--- Tests/nodes_texinfo_res/makeinfo-top-command.html   5 Feb 2007 15:30:25 
-0000       1.19
+++ Tests/nodes_texinfo_res/makeinfo-top-command.html   3 Oct 2007 09:34:47 
-0000       1.20
@@ -83,7 +83,7 @@
 
 <p>A special sectioning command, <code>@top</code> should be used with the
 <code>@node Top</code> line.  The <code>@top</code> sectioning command tells
-<code>makeinfo</code> that it marks the `Top' node in the file.  It provides
+<code>makeinfo</code> that it marks the &lsquo;Top&rsquo; node in the file.  
It provides
 the information that <code>makeinfo</code> needs to insert node pointers
 automatically.  Write the <code>@top</code> command at the beginning of the
 line immediately following the <code>@node Top</code> line.  Write the title

Index: Tests/nodes_texinfo_res/makeinfo-top.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/makeinfo-top.html,v
retrieving revision 1.20
retrieving revision 1.21
diff -u -b -r1.20 -r1.21
--- Tests/nodes_texinfo_res/makeinfo-top.html   5 Feb 2007 15:30:25 -0000       
1.20
+++ Tests/nodes_texinfo_res/makeinfo-top.html   3 Oct 2007 09:34:47 -0000       
1.21
@@ -84,7 +84,7 @@
 <p>The <code>@top</code> command is a special sectioning command that you use
 only after an &lsquo;<samp>@node Top</samp>&rsquo; line at the beginning of a 
Texinfo file.
 The <code>@top</code> command tells the <code>makeinfo</code> formatter which 
node
-is the `Top' node, so it can use it as the root of the node tree if your
+is the &lsquo;Top&rsquo; node, so it can use it as the root of the node tree 
if your
 manual uses implicit pointers.  It has the same typesetting effect as
 <code>@unnumbered</code> (see section <a 
href="unnumbered-_0026-appendix.html#SEC77"><code>@unnumbered</code> and 
<code>@appendix</code></a>).  For detailed information, see <a 
href="makeinfo-top-command.html#SEC94">The <code>@top</code> Command</a>.
 </p>

Index: Tests/nodes_texinfo_res/math.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/math.html,v
retrieving revision 1.21
retrieving revision 1.22
diff -u -b -r1.21 -r1.22
--- Tests/nodes_texinfo_res/math.html   5 Feb 2007 15:30:25 -0000       1.21
+++ Tests/nodes_texinfo_res/math.html   3 Oct 2007 09:34:47 -0000       1.22
@@ -96,7 +96,7 @@
 </p>
 <p><code>@math</code> implies <code>@tex</code>.  This not only makes it 
possible to
 write superscripts and subscripts (as in the above example), but also
-allows you to use any of the plain TeX math control sequences.  It's
+allows you to use any of the plain TeX math control sequences.  It&rsquo;s
 conventional to use &lsquo;<samp>\</samp>&rsquo; instead of 
&lsquo;<samp>@</samp>&rsquo; for these commands.
 As in:
 </p><table><tr><td>&nbsp;</td><td><pre class="example">@math{\sin 2\pi \equiv 
\cos 3\pi}
@@ -109,7 +109,7 @@
 <a name="IDX224"></a>
 <p>Since &lsquo;<samp>\</samp>&rsquo; is an escape character inside 
<code>@math</code>, you can use
 <code>@\</code> to get a literal backslash (<code>\\</code> will work in TeX,
-but you'll get the literal &lsquo;<samp>\\</samp>&rsquo; in Info).  
<code>@\</code> is not
+but you&rsquo;ll get the literal &lsquo;<samp>\\</samp>&rsquo; in Info).  
<code>@\</code> is not
 defined outside of <code>@math</code>, since a &lsquo;<samp>\</samp>&rsquo; 
ordinarily produces a
 literal &lsquo;<samp>\</samp>&rsquo;.
 </p>

Index: Tests/nodes_texinfo_res/node.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/node.html,v
retrieving revision 1.21
retrieving revision 1.22
diff -u -b -r1.21 -r1.22
--- Tests/nodes_texinfo_res/node.html   5 Feb 2007 15:30:25 -0000       1.21
+++ Tests/nodes_texinfo_res/node.html   3 Oct 2007 09:34:47 -0000       1.22
@@ -99,12 +99,12 @@
 line, and follow it with up to four arguments, separated by commas, on
 the rest of the same line.  The first argument is required; it is the
 name of this node.  The subsequent arguments are the names of the
-`Next', `Previous', and `Up' pointers, in that order, and may be omitted
+&lsquo;Next&rsquo;, &lsquo;Previous&rsquo;, and &lsquo;Up&rsquo; pointers, in 
that order, and may be omitted
 if your Texinfo document is hierarchically organized (see section <a 
href="makeinfo-Pointer-Creation.html#SEC95">Creating Pointers with 
<code>makeinfo</code></a>).
 </p>
 <p>You may insert spaces before each name if you wish; the spaces are
 ignored.  You must write the name of the node and the names of the
-`Next', `Previous', and `Up' pointers all on the same line.  Otherwise,
+&lsquo;Next&rsquo;, &lsquo;Previous&rsquo;, and &lsquo;Up&rsquo; pointers all 
on the same line.  Otherwise,
 the formatters fail.  (See <a href="../info/index.html#Top">info: 
(info)Top</a>, for more information
 about nodes in Info.)
 </p>
@@ -133,7 +133,7 @@
 </td></tr>
 <tr><td align="left" valign="top"><a 
href="Node-Line-Requirements.html#SEC92">6.3.4 <code>@node</code> Line 
Requirements</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">      
Keep names unique, without @-commands.
 </td></tr>
-<tr><td align="left" valign="top"><a href="First-Node.html#SEC93">6.3.5 The 
First Node</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">          
        How to write a `Top' node.
+<tr><td align="left" valign="top"><a href="First-Node.html#SEC93">6.3.5 The 
First Node</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">          
        How to write a &lsquo;Top&rsquo; node.
 </td></tr>
 <tr><td align="left" valign="top"><a 
href="makeinfo-top-command.html#SEC94">6.3.6 The <code>@top</code> Sectioning 
Command</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">        How 
to use the <code>@top</code> command.
 </td></tr>

Index: Tests/nodes_texinfo_res/noindent.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/noindent.html,v
retrieving revision 1.20
retrieving revision 1.21
diff -u -b -r1.20 -r1.21
--- Tests/nodes_texinfo_res/noindent.html       5 Feb 2007 15:30:25 -0000       
1.20
+++ Tests/nodes_texinfo_res/noindent.html       3 Oct 2007 09:34:47 -0000       
1.21
@@ -116,7 +116,7 @@
 blank line, and neither does the <code>@end example</code> line.
 </p>
 <p>In the Texinfo source file for this manual, each line that says
-`produces' is preceded by a line containing <code>@noindent</code>.
+&lsquo;produces&rsquo; is preceded by a line containing <code>@noindent</code>.
 </p>
 <p>Do not put braces after an <code>@noindent</code> command; they are not
 necessary, since <code>@noindent</code> is a command used outside of

Index: Tests/nodes_texinfo_res/pounds.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/pounds.html,v
retrieving revision 1.21
retrieving revision 1.22
diff -u -b -r1.21 -r1.22
--- Tests/nodes_texinfo_res/pounds.html 5 Feb 2007 15:30:25 -0000       1.21
+++ Tests/nodes_texinfo_res/pounds.html 3 Oct 2007 09:34:47 -0000       1.22
@@ -81,7 +81,7 @@
 <hr size="1">
 <h2 class="section"> 13.6 <code>@pounds</code>{} (&pound;): Pounds Sterling 
</h2>
 
-<p>Use the <code>@pounds{}</code> command to generate `&pound;'.  In a
+<p>Use the <code>@pounds{}</code> command to generate &lsquo;&pound;&rsquo;.  
In a
 printed manual, this is the symbol for the currency pounds sterling.
 In Info, it is a &lsquo;<samp>#</samp>&rsquo;.  Other currency symbols are 
unfortunately not
 available.

Index: Tests/nodes_texinfo_res/pxref.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/pxref.html,v
retrieving revision 1.23
retrieving revision 1.24
diff -u -b -r1.23 -r1.24
--- Tests/nodes_texinfo_res/pxref.html  5 Feb 2007 15:30:25 -0000       1.23
+++ Tests/nodes_texinfo_res/pxref.html  3 Oct 2007 09:34:47 -0000       1.24
@@ -83,14 +83,14 @@
 
 <p>The parenthetical reference command, <code>@pxref</code>, is nearly the
 same as <code>@xref</code>, but you use it <em>only</em> inside parentheses
-and you do <em>not</em> type a comma or period after the command's
+and you do <em>not</em> type a comma or period after the command&rsquo;s
 closing brace.  The command differs from <code>@xref</code> in two
 ways:
 </p>
 <ol>
 <li>
 TeX typesets the reference for the printed manual with a lower case
-`see' rather than an upper case `See'.
+&lsquo;see&rsquo; rather than an upper case &lsquo;See&rsquo;.
 
 </li><li>
 The Info formatting commands automatically end the reference with a

Index: Tests/nodes_texinfo_res/ref.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/ref.html,v
retrieving revision 1.20
retrieving revision 1.21
diff -u -b -r1.20 -r1.21
--- Tests/nodes_texinfo_res/ref.html    5 Feb 2007 15:30:25 -0000       1.20
+++ Tests/nodes_texinfo_res/ref.html    3 Oct 2007 09:34:47 -0000       1.21
@@ -82,7 +82,7 @@
 <h2 class="section"> 8.5 <code>@ref</code> </h2>
 
 <p><code>@ref</code> is nearly the same as <code>@xref</code> except that it 
does
-not generate a `See' in the printed output, just the reference itself.
+not generate a &lsquo;See&rsquo; in the printed output, just the reference 
itself.
 This makes it useful as the last part of a sentence.
 </p>
 <p>For example,

Index: Tests/nodes_texinfo_res/samp.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/samp.html,v
retrieving revision 1.22
retrieving revision 1.23
diff -u -b -r1.22 -r1.23
--- Tests/nodes_texinfo_res/samp.html   5 Feb 2007 15:30:25 -0000       1.22
+++ Tests/nodes_texinfo_res/samp.html   3 Oct 2007 09:34:47 -0000       1.23
@@ -82,7 +82,7 @@
 <h3 class="subsection"> 9.1.4 <code>@samp</code>{<var>text</var>} </h3>
 
 <p>Use the <code>@samp</code> command to indicate text that is a literal 
example
-or `sample' of a sequence of characters in a file, string, pattern, etc.
+or &lsquo;sample&rsquo; of a sequence of characters in a file, string, 
pattern, etc.
 Enclose the text in braces.  The argument appears within single
 quotation marks in both the Info file and the printed manual; in
 addition, it is printed in a fixed-width font.

Index: Tests/nodes_texinfo_res/setchapternewpage.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/setchapternewpage.html,v
retrieving revision 1.23
retrieving revision 1.24
diff -u -b -r1.23 -r1.24
--- Tests/nodes_texinfo_res/setchapternewpage.html      5 Feb 2007 15:30:25 
-0000       1.23
+++ Tests/nodes_texinfo_res/setchapternewpage.html      3 Oct 2007 09:34:47 
-0000       1.24
@@ -129,7 +129,7 @@
 because there is no printing tradition of starting chapters or books on
 an even-numbered page.
 </p>
-<p>If you don't like the default headers that <code>@setchapternewpage</code>
+<p>If you don&rsquo;t like the default headers that 
<code>@setchapternewpage</code>
 sets, you can explicit control them with the <code>@headings</code> command.
 See section <a href="headings-on-off.html#SEC58">The <code>@headings</code> 
Command</a>.
 </p>
@@ -143,7 +143,7 @@
 </p>
 <p>We recommend not including any <code>@setchapternewpage</code> command in
 your manual sources at all, since the desired output is not intrinsic to
-the document.  For a particular hard copy run, if you don't want the
+the document.  For a particular hard copy run, if you don&rsquo;t want the
 default option (no blank pages, same headers on all pages) use the
 &lsquo;<samp>--texinfo</samp>&rsquo; option to <code>texi2dvi</code> to 
specify the output
 you want.

Index: Tests/nodes_texinfo_res/subsubsection.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/subsubsection.html,v
retrieving revision 1.22
retrieving revision 1.23
diff -u -b -r1.22 -r1.23
--- Tests/nodes_texinfo_res/subsubsection.html  5 Feb 2007 15:30:25 -0000       
1.22
+++ Tests/nodes_texinfo_res/subsubsection.html  3 Oct 2007 09:34:47 -0000       
1.23
@@ -79,10 +79,10 @@
 <td valign="middle" align="left">[<a href="texinfo_abt.html#SEC_About" 
title="About (help)"> ? </a>]</td>
 </tr></table>
 <hr size="1">
-<h2 class="section"> 5.11 The `subsub' Commands </h2>
+<h2 class="section"> 5.11 The &lsquo;subsub&rsquo; Commands </h2>
 
 <p>The fourth and lowest level sectioning commands in Texinfo are the
-`subsub' commands.  They are:
+&lsquo;subsub&rsquo; commands.  They are:
 </p>
 <dl compact="compact">
 <dt> <code>@subsubsection</code></dt>
@@ -114,7 +114,7 @@
 </p></dd>
 </dl>
 
-<p>In Info,  `subsub' titles are underlined with periods.
+<p>In Info,  &lsquo;subsub&rsquo; titles are underlined with periods.
 For example,
 </p>
 <table><tr><td>&nbsp;</td><td><pre class="example">@subsubsection This is a 
subsubsection

Index: Tests/nodes_texinfo_res/syncodeindex.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/syncodeindex.html,v
retrieving revision 1.23
retrieving revision 1.24
diff -u -b -r1.23 -r1.24
--- Tests/nodes_texinfo_res/syncodeindex.html   5 Feb 2007 15:30:25 -0000       
1.23
+++ Tests/nodes_texinfo_res/syncodeindex.html   3 Oct 2007 09:34:47 -0000       
1.24
@@ -140,7 +140,7 @@
 </pre></td></tr></table>
 
 <a name="IDX159"></a>
-<p>The <code>@syncodeindex</code> command puts all the entries from the `from'
+<p>The <code>@syncodeindex</code> command puts all the entries from the 
&lsquo;from&rsquo;
 index (the redirected index) into the <code>@code</code> font, overriding
 whatever default font is used by the index to which the entries are
 now directed.  This way, if you direct function names from a function

Index: Tests/nodes_texinfo_res/synindex.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/synindex.html,v
retrieving revision 1.18
retrieving revision 1.19
diff -u -b -r1.18 -r1.19
--- Tests/nodes_texinfo_res/synindex.html       5 Feb 2007 15:30:25 -0000       
1.18
+++ Tests/nodes_texinfo_res/synindex.html       3 Oct 2007 09:34:47 -0000       
1.19
@@ -83,7 +83,7 @@
 
 <p>The <code>@synindex</code> command is nearly the same as the
 <code>@syncodeindex</code> command, except that it does not put the
-`from' index  entries into the <code>@code</code> font; rather it puts
+&lsquo;from&rsquo; index  entries into the <code>@code</code> font; rather it 
puts
 them in the roman font.  Thus, you use <code>@synindex</code> when you
 merge a concept index into a function index.
 </p>

Index: Tests/nodes_texinfo_res/tex.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/tex.html,v
retrieving revision 1.21
retrieving revision 1.22
diff -u -b -r1.21 -r1.22
--- Tests/nodes_texinfo_res/tex.html    5 Feb 2007 15:30:25 -0000       1.21
+++ Tests/nodes_texinfo_res/tex.html    3 Oct 2007 09:34:47 -0000       1.22
@@ -81,7 +81,7 @@
 <hr size="1">
 <h3 class="subsection"> 13.5.1 <code>@TeX</code>{} (TeX) </h3>
 
-<p>Use the <code>@TeX{}</code> command to generate `TeX'.  In a printed
+<p>Use the <code>@TeX{}</code> command to generate &lsquo;TeX&rsquo;.  In a 
printed
 manual, this is a special logo that is different from three ordinary
 letters.  In Info, it just looks like &lsquo;<samp>TeX</samp>&rsquo;.  The
 <code>@TeX{}</code> command is unique among Texinfo commands in that the

Index: Tests/nodes_texinfo_res/texinfo.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/texinfo.html,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -b -r1.3 -r1.4
--- Tests/nodes_texinfo_res/texinfo.html        30 Sep 2007 12:47:37 -0000      
1.3
+++ Tests/nodes_texinfo_res/texinfo.html        3 Oct 2007 09:34:47 -0000       
1.4
@@ -85,7 +85,7 @@
 and with the Back-Cover Texts as in (a) below.  A copy of the license is
 included in the section entitled &ldquo;GNU Free Documentation License.&rdquo;
 </p>
-<p>(a) The FSF's Back-Cover Text is: &ldquo;You have freedom to copy and modify
+<p>(a) The FSF&rsquo;s Back-Cover Text is: &ldquo;You have freedom to copy and 
modify
 this GNU Manual, like GNU software.  Copies published by the Free
 Software Foundation raise funds for GNU development.&rdquo;
 </p></blockquote>
@@ -198,7 +198,7 @@
 
 </pre></th></tr><tr><td align="left" valign="top"><a 
href="Texinfo-Mode.html#Texinfo-Mode-Overview">&bull; Texinfo Mode 
Overview</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">       How 
Texinfo mode can help you.
 </td></tr>
-<tr><td align="left" valign="top"><a href="Emacs-Editing.html#SEC23">2.1 The 
Usual GNU Emacs Editing Commands</a></td><td>&nbsp;&nbsp;</td><td align="left" 
valign="top">               Texinfo mode adds to GNU Emacs' general
+<tr><td align="left" valign="top"><a href="Emacs-Editing.html#SEC23">2.1 The 
Usual GNU Emacs Editing Commands</a></td><td>&nbsp;&nbsp;</td><td align="left" 
valign="top">               Texinfo mode adds to GNU Emacs&rsquo; general
                                   purpose editing features.
 </td></tr>
 <tr><td align="left" valign="top"><a href="Inserting.html#SEC24">2.2 Inserting 
Frequently Used Commands</a></td><td>&nbsp;&nbsp;</td><td align="left" 
valign="top">                   How to insert frequently used @-commands.
@@ -236,7 +236,7 @@
 </td></tr>
 <tr><td align="left" valign="top"><a 
href="Titlepage-_0026-Copyright-Page.html#SEC52">3.4 Title and Copyright 
Pages</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">  Creating the 
title and copyright pages.
 </td></tr>
-<tr><td align="left" valign="top"><a href="The-Top-Node.html#SEC59">3.5 The 
`Top' Node and Master Menu</a></td><td>&nbsp;&nbsp;</td><td align="left" 
valign="top">                Creating the `Top' node and master menu.
+<tr><td align="left" valign="top"><a href="The-Top-Node.html#SEC59">3.5 The 
&lsquo;Top&rsquo; Node and Master Menu</a></td><td>&nbsp;&nbsp;</td><td 
align="left" valign="top">                Creating the &lsquo;Top&rsquo; node 
and master menu.
 </td></tr>
 <tr><td align="left" valign="top"><a 
href="Global-Document-Commands.html#SEC62">3.6 Global Document 
Commands</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">    
 </td></tr>
@@ -259,7 +259,7 @@
 <tr><th colspan="3" align="left" valign="top"><pre class="menu-comment">
 Document Permissions
 
-</pre></th></tr><tr><td align="left" valign="top"><a 
href="copying.html#SEC50">3.3.1 <code>@copying</code>: Declare copying 
permissions</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">         
            Declare the document's copying permissions.
+</pre></th></tr><tr><td align="left" valign="top"><a 
href="copying.html#SEC50">3.3.1 <code>@copying</code>: Declare copying 
permissions</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">         
            Declare the document&rsquo;s copying permissions.
 </td></tr>
 <tr><td align="left" valign="top"><a href="insertcopying.html#SEC51">3.3.2 
<code>@insertcopying</code>: Include permissions 
text</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">               
Where to insert the permissions.
 </td></tr>
@@ -318,7 +318,7 @@
 </td></tr>
 <tr><td align="left" valign="top"><a 
href="Structuring-Command-Types.html#SEC74">5.2 Structuring Command 
Types</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">   How to 
divide a manual into parts.
 </td></tr>
-<tr><td align="left" valign="top"><a href="makeinfo-top.html#SEC75">5.3 
<code>@top</code></a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">   
             The <code>@top</code> command, part of the `Top' node.
+<tr><td align="left" valign="top"><a href="makeinfo-top.html#SEC75">5.3 
<code>@top</code></a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">   
             The <code>@top</code> command, part of the &lsquo;Top&rsquo; node.
 </td></tr>
 <tr><td align="left" valign="top"><a href="chapter.html#SEC76">5.4 
<code>@chapter</code></a></td><td>&nbsp;&nbsp;</td><td align="left" 
valign="top">                     
 </td></tr>
@@ -334,9 +334,9 @@
 </td></tr>
 <tr><td align="left" valign="top"><a 
href="unnumberedsubsec-appendixsubsec-subheading.html#SEC82">5.10 The 
<code>@subsection</code>-like Commands</a></td><td>&nbsp;&nbsp;</td><td 
align="left" valign="top">  
 </td></tr>
-<tr><td align="left" valign="top"><a href="subsubsection.html#SEC83">5.11 The 
`subsub' Commands</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">   
            Commands for the lowest level sections.
+<tr><td align="left" valign="top"><a href="subsubsection.html#SEC83">5.11 The 
&lsquo;subsub&rsquo; Commands</a></td><td>&nbsp;&nbsp;</td><td align="left" 
valign="top">               Commands for the lowest level sections.
 </td></tr>
-<tr><td align="left" valign="top"><a 
href="Raise_002flower-sections.html#SEC84">5.12 <code>@raisesections</code> and 
<code>@lowersections</code></a></td><td>&nbsp;&nbsp;</td><td align="left" 
valign="top">        How to change commands' hierarchical level.
+<tr><td align="left" valign="top"><a 
href="Raise_002flower-sections.html#SEC84">5.12 <code>@raisesections</code> and 
<code>@lowersections</code></a></td><td>&nbsp;&nbsp;</td><td align="left" 
valign="top">        How to change commands&rsquo; hierarchical level.
 </td></tr>
 <tr><th colspan="3" align="left" valign="top"><pre class="menu-comment">
 Nodes
@@ -363,7 +363,7 @@
 </td></tr>
 <tr><td align="left" valign="top"><a 
href="Node-Line-Requirements.html#SEC92">6.3.4 <code>@node</code> Line 
Requirements</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">      
Keep names unique, without @-commands.
 </td></tr>
-<tr><td align="left" valign="top"><a href="First-Node.html#SEC93">6.3.5 The 
First Node</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">          
        How to write a `Top' node.
+<tr><td align="left" valign="top"><a href="First-Node.html#SEC93">6.3.5 The 
First Node</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">          
        How to write a &lsquo;Top&rsquo; node.
 </td></tr>
 <tr><td align="left" valign="top"><a 
href="makeinfo-top-command.html#SEC94">6.3.6 The <code>@top</code> Sectioning 
Command</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">        How 
to use the <code>@top</code> command.
 </td></tr>
@@ -391,9 +391,9 @@
 </td></tr>
 <tr><td align="left" valign="top"><a 
href="Cross-Reference-Parts.html#SEC107">8.2 Parts of a Cross 
Reference</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">       A 
cross reference has several parts.
 </td></tr>
-<tr><td align="left" valign="top"><a href="xref.html#SEC108">8.3 
<code>@xref</code></a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">  
                      Begin a reference with `See' &hellip;
+<tr><td align="left" valign="top"><a href="xref.html#SEC108">8.3 
<code>@xref</code></a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">  
                      Begin a reference with &lsquo;See&rsquo; &hellip;
 </td></tr>
-<tr><td align="left" valign="top"><a href="Top-Node-Naming.html#SEC114">8.4 
Naming a `Top' Node</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top"> 
            How to refer to the beginning of another file.
+<tr><td align="left" valign="top"><a href="Top-Node-Naming.html#SEC114">8.4 
Naming a &lsquo;Top&rsquo; Node</a></td><td>&nbsp;&nbsp;</td><td align="left" 
valign="top">             How to refer to the beginning of another file.
 </td></tr>
 <tr><td align="left" valign="top"><a href="ref.html#SEC115">8.5 
<code>@ref</code></a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">   
                      A reference for the last part of a sentence.
 </td></tr>
@@ -488,7 +488,7 @@
 </td></tr>
 <tr><td align="left" valign="top"><a href="format.html#SEC150">10.9 
<code>@format</code> and 
<code>@smallformat</code></a></td><td>&nbsp;&nbsp;</td><td align="left" 
valign="top">                      Writing an example without narrowed margins.
 </td></tr>
-<tr><td align="left" valign="top"><a href="exdent.html#SEC151">10.10 
<code>@exdent</code>: Undoing a Line's 
Indentation</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">         
             Undo indentation on a line.
+<tr><td align="left" valign="top"><a href="exdent.html#SEC151">10.10 
<code>@exdent</code>: Undoing a Line&rsquo;s 
Indentation</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">         
             Undo indentation on a line.
 </td></tr>
 <tr><td align="left" valign="top"><a 
href="flushleft-_0026-flushright.html#SEC152">10.11 <code>@flushleft</code> and 
<code>@flushright</code></a></td><td>&nbsp;&nbsp;</td><td align="left" 
valign="top">      Pushing text flush left or flush right.
 </td></tr>
@@ -586,7 +586,7 @@
 <tr><th colspan="3" align="left" valign="top"><pre class="menu-comment">
 Inserting Space
 
-</pre></th></tr><tr><td align="left" valign="top"><a 
href="Not-Ending-a-Sentence.html#SEC179">13.2.1 Not Ending a 
Sentence</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">       
Sometimes a . doesn't end a sentence.
+</pre></th></tr><tr><td align="left" valign="top"><a 
href="Not-Ending-a-Sentence.html#SEC179">13.2.1 Not Ending a 
Sentence</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">       
Sometimes a . doesn&rsquo;t end a sentence.
 </td></tr>
 <tr><td align="left" valign="top"><a 
href="Ending-a-Sentence.html#SEC180">13.2.2 Ending a 
Sentence</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">           
Sometimes it does.
 </td></tr>
@@ -674,7 +674,7 @@
 </td></tr>
 <tr><td align="left" valign="top"><a 
href="Optional-Arguments.html#SEC216">15.2 Optional and Repeated 
Arguments</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">          
How to handle optional and repeated arguments.
 </td></tr>
-<tr><td align="left" valign="top"><a href="deffnx.html#SEC217">15.3 Two or 
More `First' Lines</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">  
                    How to group two or more `first' lines.
+<tr><td align="left" valign="top"><a href="deffnx.html#SEC217">15.3 Two or 
More &lsquo;First&rsquo; Lines</a></td><td>&nbsp;&nbsp;</td><td align="left" 
valign="top">                      How to group two or more &lsquo;first&rsquo; 
lines.
 </td></tr>
 <tr><td align="left" valign="top"><a 
href="Def-Cmds-in-Detail.html#SEC218">15.4 The Definition 
Commands</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">          
All the definition commands.
 </td></tr>
@@ -731,7 +731,7 @@
 
 </pre></th></tr><tr><td align="left" valign="top"><a 
href="Defining-Macros.html#SEC239">18.1 Defining 
Macros</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">             
Defining and undefining new commands.
 </td></tr>
-<tr><td align="left" valign="top"><a href="Invoking-Macros.html#SEC240">18.2 
Invoking Macros</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">     
        Using a macro, once you've defined it.
+<tr><td align="left" valign="top"><a href="Invoking-Macros.html#SEC240">18.2 
Invoking Macros</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">     
        Using a macro, once you&rsquo;ve defined it.
 </td></tr>
 <tr><td align="left" valign="top"><a href="Macro-Details.html#SEC241">18.3 
Macro Details</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">       
        Beyond basic macro usage.
 </td></tr>
@@ -754,7 +754,7 @@
 </td></tr>
 <tr><td align="left" valign="top"><a 
href="Texinfo-Mode-Printing.html#SEC250">19.6 Formatting and Printing in 
Texinfo Mode</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">       
How to format and print in Texinfo mode.
 </td></tr>
-<tr><td align="left" valign="top"><a 
href="Compile_002dCommand.html#SEC251">19.7 Using the Local Variables 
List</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">             
How to print using Emacs's compile command.
+<tr><td align="left" valign="top"><a 
href="Compile_002dCommand.html#SEC251">19.7 Using the Local Variables 
List</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">             
How to print using Emacs&rsquo;s compile command.
 </td></tr>
 <tr><td align="left" valign="top"><a 
href="Requirements-Summary.html#SEC252">19.8 TeX Formatting Requirements 
Summary</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">        TeX 
formatting requirements summary.
 </td></tr>

Index: Tests/nodes_texinfo_res/texinfo_002dmultiple_002dfiles_002dupdate.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/texinfo_002dmultiple_002dfiles_002dupdate.html,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -b -r1.9 -r1.10
--- Tests/nodes_texinfo_res/texinfo_002dmultiple_002dfiles_002dupdate.html      
5 Feb 2007 15:30:25 -0000       1.9
+++ Tests/nodes_texinfo_res/texinfo_002dmultiple_002dfiles_002dupdate.html      
3 Oct 2007 09:34:47 -0000       1.10
@@ -82,7 +82,7 @@
 <h2 class="section"> D.2 <code>texinfo-multiple-files-update</code> </h2>
 
 <p>GNU Emacs Texinfo mode provides the 
<code>texinfo-multiple-files-update</code>
-command.  This command creates or updates `Next', `Previous', and `Up'
+command.  This command creates or updates &lsquo;Next&rsquo;, 
&lsquo;Previous&rsquo;, and &lsquo;Up&rsquo;
 pointers of included files as well as those in the outer or overall
 Texinfo file, and it creates or updates a main menu in the outer file.
 Depending whether you call it with optional arguments, the command
@@ -95,12 +95,12 @@
 </p>
 <ul class="toc">
 <li>-
-Create or update the `Next', `Previous', and `Up' pointers of the
+Create or update the &lsquo;Next&rsquo;, &lsquo;Previous&rsquo;, and 
&lsquo;Up&rsquo; pointers of the
 first <code>@node</code> line in each file included in an outer or overall
 Texinfo file.
 
 </li><li>-
-Create or update the `Top' level node pointers of the outer or
+Create or update the &lsquo;Top&rsquo; level node pointers of the outer or
 overall file.
 
 </li><li>-
@@ -117,7 +117,7 @@
 included file.
 
 </li><li>-
-Create or update the `Top' level node pointers of the outer file.
+Create or update the &lsquo;Top&rsquo; level node pointers of the outer file.
 
 </li><li>-
 Create and insert a master menu in the outer file.  The master menu
@@ -130,7 +130,7 @@
 </p>
 <ul class="toc">
 <li>-
-Create or update <strong>all</strong> the `Next', `Previous', and `Up' pointers
+Create or update <strong>all</strong> the &lsquo;Next&rsquo;, 
&lsquo;Previous&rsquo;, and &lsquo;Up&rsquo; pointers
 of all the included files.
 
 </li><li>-
@@ -138,7 +138,7 @@
 files.
 
 </li><li>-
-Create or update the `Top' level node pointers of the outer or
+Create or update the &lsquo;Top&rsquo; level node pointers of the outer or
 overall file.
 
 </li><li>-

Index: Tests/nodes_texinfo_res/texinfo_285.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/texinfo_285.html,v
retrieving revision 1.25
retrieving revision 1.26
diff -u -b -r1.25 -r1.26
--- Tests/nodes_texinfo_res/texinfo_285.html    5 Feb 2007 15:30:25 -0000       
1.25
+++ Tests/nodes_texinfo_res/texinfo_285.html    3 Oct 2007 09:34:47 -0000       
1.26
@@ -211,8 +211,8 @@
 <tr><td></td><td valign="top"><a 
href="Running-Info_002dValidate.html#SEC314"><code>Info-validate</code></a></td><td
 valign="top"><a href="Running-Info_002dValidate.html#SEC314">F.5 Finding Badly 
Referenced Nodes</a></td></tr>
 <tr><td></td><td valign="top"><a 
href="inforef.html#SEC117"><code>inforef</code></a></td><td valign="top"><a 
href="inforef.html#SEC117">8.7 <code>@inforef</code></a></td></tr>
 <tr><td></td><td valign="top"><a 
href="insertcopying.html#SEC51"><code>insertcopying</code></a></td><td 
valign="top"><a href="insertcopying.html#SEC51">3.3.2 
<code>@insertcopying</code>: Include permissions text</a></td></tr>
-<tr><td></td><td valign="top"><a 
href="deffnx.html#IDX265"><code>isearch-backward</code></a></td><td 
valign="top"><a href="deffnx.html#SEC217">15.3 Two or More `First' 
Lines</a></td></tr>
-<tr><td></td><td valign="top"><a 
href="deffnx.html#IDX264"><code>isearch-forward</code></a></td><td 
valign="top"><a href="deffnx.html#SEC217">15.3 Two or More `First' 
Lines</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="deffnx.html#IDX265"><code>isearch-backward</code></a></td><td 
valign="top"><a href="deffnx.html#SEC217">15.3 Two or More &lsquo;First&rsquo; 
Lines</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="deffnx.html#IDX264"><code>isearch-forward</code></a></td><td 
valign="top"><a href="deffnx.html#SEC217">15.3 Two or More &lsquo;First&rsquo; 
Lines</a></td></tr>
 <tr><td></td><td valign="top"><a 
href="itemize.html#IDX137"><code>item</code></a></td><td valign="top"><a 
href="itemize.html#SEC157">11.1 <code>@itemize</code>: Making an Itemized 
List</a></td></tr>
 <tr><td></td><td valign="top"><a 
href="Two_002dcolumn-Tables.html#IDX139"><code>item</code></a></td><td 
valign="top"><a href="Two_002dcolumn-Tables.html#SEC160">Using the 
<code>@table</code> Command</a></td></tr>
 <tr><td></td><td valign="top"><a 
href="Multitable-Rows.html#SEC165"><code>item</code></a></td><td 
valign="top"><a href="Multitable-Rows.html#SEC165">11.4.2 Multitable 
Rows</a></td></tr>
@@ -311,8 +311,8 @@
 <tr><td></td><td valign="top"><a 
href="emph-_0026-strong.html#SEC138"><code>strong</code></a></td><td 
valign="top"><a href="emph-_0026-strong.html#SEC138">9.2.1 
<code>@emph</code>{<var>text</var>} and 
<code>@strong</code>{<var>text</var>}</a></td></tr>
 <tr><td></td><td valign="top"><a 
href="unnumberedsubsec-appendixsubsec-subheading.html#SEC82"><code>subheading</code></a></td><td
 valign="top"><a 
href="unnumberedsubsec-appendixsubsec-subheading.html#SEC82">5.10 The 
<code>@subsection</code>-like Commands</a></td></tr>
 <tr><td></td><td valign="top"><a 
href="subsection.html#SEC81"><code>subsection</code></a></td><td 
valign="top"><a href="subsection.html#SEC81">5.9 The <code>@subsection</code> 
Command</a></td></tr>
-<tr><td></td><td valign="top"><a 
href="subsubsection.html#SEC83"><code>subsubheading</code></a></td><td 
valign="top"><a href="subsubsection.html#SEC83">5.11 The `subsub' 
Commands</a></td></tr>
-<tr><td></td><td valign="top"><a 
href="subsubsection.html#SEC83"><code>subsubsection</code></a></td><td 
valign="top"><a href="subsubsection.html#SEC83">5.11 The `subsub' 
Commands</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="subsubsection.html#SEC83"><code>subsubheading</code></a></td><td 
valign="top"><a href="subsubsection.html#SEC83">5.11 The &lsquo;subsub&rsquo; 
Commands</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="subsubsection.html#SEC83"><code>subsubsection</code></a></td><td 
valign="top"><a href="subsubsection.html#SEC83">5.11 The &lsquo;subsub&rsquo; 
Commands</a></td></tr>
 <tr><td></td><td valign="top"><a 
href="title-subtitle-author.html#SEC55"><code>subtitle</code></a></td><td 
valign="top"><a href="title-subtitle-author.html#SEC55">3.4.3 
<code>@title</code>, <code>@subtitle</code>, and 
<code>@author</code></a></td></tr>
 <tr><td></td><td valign="top"><a 
href="Contents.html#SEC70"><code>summarycontents</code></a></td><td 
valign="top"><a href="Contents.html#SEC70">4.2 Generating a Table of 
Contents</a></td></tr>
 <tr><td></td><td valign="top"><a 
href="syncodeindex.html#SEC171"><code>syncodeindex</code></a></td><td 
valign="top"><a href="syncodeindex.html#SEC171">12.4.1 
<code>@syncodeindex</code></a></td></tr>

Index: Tests/nodes_texinfo_res/texinfo_286.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/texinfo_286.html,v
retrieving revision 1.19
retrieving revision 1.20
diff -u -b -r1.19 -r1.20
--- Tests/nodes_texinfo_res/texinfo_286.html    5 Feb 2007 15:30:25 -0000       
1.19
+++ Tests/nodes_texinfo_res/texinfo_286.html    3 Oct 2007 09:34:48 -0000       
1.20
@@ -217,7 +217,7 @@
 <tr><td></td><td valign="top"><a 
href="titlefont-center-sp.html#SEC54"><code>titlefont</code></a></td><td 
valign="top"><a href="titlefont-center-sp.html#SEC54">3.4.2 
<code>@titlefont</code>, <code>@center</code>, and 
<code>@sp</code></a></td></tr>
 <tr><td></td><td valign="top"><a 
href="titlepage.html#SEC53"><code>titlepage</code></a></td><td valign="top"><a 
href="titlepage.html#SEC53">3.4.1 <code>@titlepage</code></a></td></tr>
 <tr><td></td><td valign="top"><a 
href="Custom-Headings.html#IDX461"><code>today</code></a></td><td 
valign="top"><a href="Custom-Headings.html#SEC307">E.3 How to Make Your Own 
Headings</a></td></tr>
-<tr><td></td><td valign="top"><a 
href="The-Top-Node.html#IDX85"><code>top</code></a></td><td valign="top"><a 
href="The-Top-Node.html#SEC59">3.5 The `Top' Node and Master Menu</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="The-Top-Node.html#IDX85"><code>top</code></a></td><td valign="top"><a 
href="The-Top-Node.html#SEC59">3.5 The &lsquo;Top&rsquo; Node and Master 
Menu</a></td></tr>
 <tr><td></td><td valign="top"><a 
href="makeinfo-top-command.html#SEC94"><code>top <span 
class="roman">(@-command)</span></code></a></td><td valign="top"><a 
href="makeinfo-top-command.html#SEC94">6.3.6 The <code>@top</code> Sectioning 
Command</a></td></tr>
 <tr><td colspan="3"> <hr></td></tr>
 <tr><th><a name="INDEX1_1">U</a></th><td></td><td></td></tr>
@@ -228,7 +228,7 @@
 <tr><td></td><td valign="top"><a 
href="unnumbered-_0026-appendix.html#SEC77"><code>unnumbered</code></a></td><td 
valign="top"><a href="unnumbered-_0026-appendix.html#SEC77">5.5 
<code>@unnumbered</code> and <code>@appendix</code></a></td></tr>
 <tr><td></td><td valign="top"><a 
href="unnumberedsec-appendixsec-heading.html#SEC80"><code>unnumberedsec</code></a></td><td
 valign="top"><a href="unnumberedsec-appendixsec-heading.html#SEC80">5.8 
<code>@unnumberedsec</code>, <code>@appendixsec</code>, 
<code>@heading</code></a></td></tr>
 <tr><td></td><td valign="top"><a 
href="unnumberedsubsec-appendixsubsec-subheading.html#SEC82"><code>unnumberedsubsec</code></a></td><td
 valign="top"><a 
href="unnumberedsubsec-appendixsubsec-subheading.html#SEC82">5.10 The 
<code>@subsection</code>-like Commands</a></td></tr>
-<tr><td></td><td valign="top"><a 
href="subsubsection.html#SEC83"><code>unnumberedsubsubsec</code></a></td><td 
valign="top"><a href="subsubsection.html#SEC83">5.11 The `subsub' 
Commands</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="subsubsection.html#SEC83"><code>unnumberedsubsubsec</code></a></td><td 
valign="top"><a href="subsubsection.html#SEC83">5.11 The &lsquo;subsub&rsquo; 
Commands</a></td></tr>
 <tr><td></td><td valign="top"><a 
href="Inserting.html#IDX44"><code>up-list</code></a></td><td valign="top"><a 
href="Inserting.html#SEC24">2.2 Inserting Frequently Used Commands</a></td></tr>
 <tr><td></td><td valign="top"><a 
href="uref.html#SEC118"><code>uref</code></a></td><td valign="top"><a 
href="uref.html#SEC118">8.8 <code>@uref{<var>url</var>[, <var>text</var>][, 
<var>replacement</var>]}</code></a></td></tr>
 <tr><td></td><td valign="top"><a 
href="url.html#SEC135"><code>url</code></a></td><td valign="top"><a 
href="url.html#SEC135">9.1.14 
<code>@url</code>{<var>uniform-resource-locator</var>}</a></td></tr>

Index: Tests/nodes_texinfo_res/texinfo_288.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/texinfo_288.html,v
retrieving revision 1.75
retrieving revision 1.76
diff -u -b -r1.75 -r1.76
--- Tests/nodes_texinfo_res/texinfo_288.html    30 Sep 2007 12:47:37 -0000      
1.75
+++ Tests/nodes_texinfo_res/texinfo_288.html    3 Oct 2007 09:34:48 -0000       
1.76
@@ -237,7 +237,7 @@
 <tr><td></td><td valign="top"><a 
href="Definition-Commands.html#SEC214">Definition commands</a></td><td 
valign="top"><a href="Definition-Commands.html#SEC214">15. Definition 
Commands</a></td></tr>
 <tr><td></td><td valign="top"><a 
href="Def-Cmd-Conventions.html#SEC225">Definition conventions</a></td><td 
valign="top"><a href="Def-Cmd-Conventions.html#SEC225">15.5 Conventions for 
Writing Definitions</a></td></tr>
 <tr><td></td><td valign="top"><a 
href="Def-Cmd-Template.html#SEC215">Definition template</a></td><td 
valign="top"><a href="Def-Cmd-Template.html#SEC215">15.1 The Template for a 
Definition</a></td></tr>
-<tr><td></td><td valign="top"><a href="deffnx.html#SEC217">Definitions grouped 
together</a></td><td valign="top"><a href="deffnx.html#SEC217">15.3 Two or More 
`First' Lines</a></td></tr>
+<tr><td></td><td valign="top"><a href="deffnx.html#SEC217">Definitions grouped 
together</a></td><td valign="top"><a href="deffnx.html#SEC217">15.3 Two or More 
&lsquo;First&rsquo; Lines</a></td></tr>
 <tr><td></td><td valign="top"><a href="verb.html#SEC126">Delimiter character, 
for verbatim</a></td><td valign="top"><a href="verb.html#SEC126">9.1.5 
<code>@verb</code>{&lt;char&gt;<var>text</var>&lt;char&gt;}</a></td></tr>
 <tr><td></td><td valign="top"><a href="pagesizes.html#SEC257">Depth of text 
area</a></td><td valign="top"><a href="pagesizes.html#SEC257">19.13 
<code>@pagesizes</code> [<var>width</var>][, <var>height</var>]: Custom page 
sizes</a></td></tr>
 <tr><td></td><td valign="top"><a href="Inserting.html#IDX47">Description for 
menu, start</a></td><td valign="top"><a href="Inserting.html#SEC24">2.2 
Inserting Frequently Used Commands</a></td></tr>

Index: Tests/nodes_texinfo_res/texinfo_289.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/texinfo_289.html,v
retrieving revision 1.21
retrieving revision 1.22
diff -u -b -r1.21 -r1.22
--- Tests/nodes_texinfo_res/texinfo_289.html    5 Feb 2007 15:30:25 -0000       
1.21
+++ Tests/nodes_texinfo_res/texinfo_289.html    3 Oct 2007 09:34:48 -0000       
1.22
@@ -243,10 +243,10 @@
 <tr><td></td><td valign="top"><a href="Texinfo-Mode.html#SEC21">GNU 
Emacs</a></td><td valign="top"><a href="Texinfo-Mode.html#SEC21">2. Using 
Texinfo Mode</a></td></tr>
 <tr><td></td><td valign="top"><a href="Within-Emacs.html#SEC249">GNU Emacs 
shell, format, print from</a></td><td valign="top"><a 
href="Within-Emacs.html#SEC249">19.5 From an Emacs Shell</a></td></tr>
 <tr><td></td><td valign="top"><a href="GNU-Sample-Texts.html#SEC296">GNU 
sample texts</a></td><td valign="top"><a 
href="GNU-Sample-Texts.html#SEC296">C.2 GNU Sample Texts</a></td></tr>
-<tr><td></td><td valign="top"><a href="Other-Info-Files.html#SEC103">Going to 
other Info files' nodes</a></td><td valign="top"><a 
href="Other-Info-Files.html#SEC103">7.5 Referring to Other Info 
Files</a></td></tr>
+<tr><td></td><td valign="top"><a href="Other-Info-Files.html#SEC103">Going to 
other Info files&rsquo; nodes</a></td><td valign="top"><a 
href="Other-Info-Files.html#SEC103">7.5 Referring to Other Info 
Files</a></td></tr>
 <tr><td></td><td valign="top"><a href="Inserting-Accents.html#IDX170">Grave 
accent</a></td><td valign="top"><a href="Inserting-Accents.html#SEC183">13.3 
Inserting Accents</a></td></tr>
 <tr><td></td><td valign="top"><a href="group.html#SEC212">Group (hold text 
together vertically)</a></td><td valign="top"><a href="group.html#SEC212">14.6 
<code>@group</code>: Prevent Page Breaks</a></td></tr>
-<tr><td></td><td valign="top"><a href="deffnx.html#SEC217">Grouping two 
definitions together</a></td><td valign="top"><a href="deffnx.html#SEC217">15.3 
Two or More `First' Lines</a></td></tr>
+<tr><td></td><td valign="top"><a href="deffnx.html#SEC217">Grouping two 
definitions together</a></td><td valign="top"><a href="deffnx.html#SEC217">15.3 
Two or More &lsquo;First&rsquo; Lines</a></td></tr>
 <tr><td colspan="3"> <hr></td></tr>
 <tr><th><a name="INDEX3_3">H</a></th><td></td><td></td></tr>
 <tr><td></td><td valign="top"><a href="Hardcopy.html#SEC244">Hardcopy, 
printing it</a></td><td valign="top"><a href="Hardcopy.html#SEC244">19. 
Formatting and Printing Hardcopy</a></td></tr>

Index: Tests/nodes_texinfo_res/texinfo_290.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/texinfo_290.html,v
retrieving revision 1.24
retrieving revision 1.25
diff -u -b -r1.24 -r1.25
--- Tests/nodes_texinfo_res/texinfo_290.html    30 Sep 2007 12:47:37 -0000      
1.24
+++ Tests/nodes_texinfo_res/texinfo_290.html    3 Oct 2007 09:34:48 -0000       
1.25
@@ -168,7 +168,7 @@
 <tr><td></td><td valign="top"><a 
href="Raise_002flower-sections.html#IDX93">Include files, and section 
levels</a></td><td valign="top"><a 
href="Raise_002flower-sections.html#SEC84">5.12 <code>@raisesections</code> and 
<code>@lowersections</code></a></td></tr>
 <tr><td></td><td valign="top"><a href="verbatiminclude.html#SEC146">Including 
a file verbatim</a></td><td valign="top"><a 
href="verbatiminclude.html#SEC146">10.5 <code>@verbatiminclude</code> 
<var>file</var>: Include a File Verbatim</a></td></tr>
 <tr><td></td><td valign="top"><a href="insertcopying.html#SEC51">Including 
permissions text</a></td><td valign="top"><a 
href="insertcopying.html#SEC51">3.3.2 <code>@insertcopying</code>: Include 
permissions text</a></td></tr>
-<tr><td></td><td valign="top"><a href="exdent.html#SEC151">Indentation 
undoing</a></td><td valign="top"><a href="exdent.html#SEC151">10.10 
<code>@exdent</code>: Undoing a Line's Indentation</a></td></tr>
+<tr><td></td><td valign="top"><a href="exdent.html#SEC151">Indentation 
undoing</a></td><td valign="top"><a href="exdent.html#SEC151">10.10 
<code>@exdent</code>: Undoing a Line&rsquo;s Indentation</a></td></tr>
 <tr><td></td><td valign="top"><a href="exampleindent.html#SEC66">Indenting 
environments</a></td><td valign="top"><a href="exampleindent.html#SEC66">3.6.4 
<code>@exampleindent</code>: Environment Indenting</a></td></tr>
 <tr><td></td><td valign="top"><a href="paragraphindent.html#SEC65">Indenting 
paragraphs, control of</a></td><td valign="top"><a 
href="paragraphindent.html#SEC65">3.6.3 Paragraph Indenting</a></td></tr>
 <tr><td></td><td valign="top"><a href="Indexing-Commands.html#SEC169">Index 
entries</a></td><td valign="top"><a href="Indexing-Commands.html#SEC169">12.3 
Defining the Entries of an Index</a></td></tr>
@@ -198,7 +198,7 @@
 <tr><td></td><td valign="top"><a 
href="Using-Info_002dvalidate.html#SEC315">Info validating a large 
file</a></td><td valign="top"><a 
href="Using-Info_002dvalidate.html#SEC315">F.5.1 Running 
<code>Info-validate</code></a></td></tr>
 <tr><td></td><td valign="top"><a 
href="Creating-an-Info-File.html#SEC261">Info, creating an online 
file</a></td><td valign="top"><a href="Creating-an-Info-File.html#SEC261">20.1 
Creating an Info File</a></td></tr>
 <tr><td></td><td valign="top"><a 
href="Other-Info-Directories.html#IDX413"><code>Info-directory-list</code></a></td><td
 valign="top"><a href="Other-Info-Directories.html#SEC274">20.2.3 Info Files in 
Other Directories</a></td></tr>
-<tr><td></td><td valign="top"><a href="Other-Info-Files.html#SEC103">Info; 
other files' nodes</a></td><td valign="top"><a 
href="Other-Info-Files.html#SEC103">7.5 Referring to Other Info 
Files</a></td></tr>
+<tr><td></td><td valign="top"><a href="Other-Info-Files.html#SEC103">Info; 
other files&rsquo; nodes</a></td><td valign="top"><a 
href="Other-Info-Files.html#SEC103">7.5 Referring to Other Info 
Files</a></td></tr>
 <tr><td></td><td valign="top"><a 
href="Other-Info-Directories.html#IDX414"><code>INFOPATH</code></a></td><td 
valign="top"><a href="Other-Info-Directories.html#SEC274">20.2.3 Info Files in 
Other Directories</a></td></tr>
 <tr><td></td><td valign="top"><a 
href="Preparing-for-TeX.html#SEC253">Initialization file for TeX 
input</a></td><td valign="top"><a href="Preparing-for-TeX.html#SEC253">19.9 
Preparing for TeX</a></td></tr>
 <tr><td></td><td valign="top"><a href="documentencoding.html#SEC237">Input 
encoding, declaring</a></td><td valign="top"><a 
href="documentencoding.html#SEC237">17.2 <code>@documentencoding 
<var>enc</var></code>: Set Input Encoding</a></td></tr>

Index: Tests/nodes_texinfo_res/texinfo_291.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/texinfo_291.html,v
retrieving revision 1.25
retrieving revision 1.26
diff -u -b -r1.25 -r1.26
--- Tests/nodes_texinfo_res/texinfo_291.html    5 Feb 2007 15:30:25 -0000       
1.25
+++ Tests/nodes_texinfo_res/texinfo_291.html    3 Oct 2007 09:34:48 -0000       
1.26
@@ -158,7 +158,7 @@
 <tr><td></td><td valign="top"><a href="syncodeindex.html#IDX158">Names for 
indices</a></td><td valign="top"><a href="syncodeindex.html#SEC171">12.4.1 
<code>@syncodeindex</code></a></td></tr>
 <tr><td></td><td valign="top"><a 
href="Format-with-tex_002ftexindex.html#IDX321">Names of index 
files</a></td><td valign="top"><a 
href="Format-with-tex_002ftexindex.html#SEC246">19.2 Format with 
<code>tex</code> and <code>texindex</code></a></td></tr>
 <tr><td></td><td valign="top"><a href="key.html#IDX128">Names recommended for 
keys</a></td><td valign="top"><a href="key.html#SEC124">9.1.3 
<code>@key</code>{<var>key-name</var>}</a></td></tr>
-<tr><td></td><td valign="top"><a href="Top-Node-Naming.html#SEC114">Naming a 
`Top' Node in references</a></td><td valign="top"><a 
href="Top-Node-Naming.html#SEC114">8.4 Naming a `Top' Node</a></td></tr>
+<tr><td></td><td valign="top"><a href="Top-Node-Naming.html#SEC114">Naming a 
&lsquo;Top&rsquo; Node in references</a></td><td valign="top"><a 
href="Top-Node-Naming.html#SEC114">8.4 Naming a &lsquo;Top&rsquo; 
Node</a></td></tr>
 <tr><td></td><td valign="top"><a href="acronym.html#SEC134">NASA, as 
acronym</a></td><td valign="top"><a href="acronym.html#SEC134">9.1.13 
<code>@acronym</code>{<var>acronym</var>}</a></td></tr>
 <tr><td></td><td valign="top"><a 
href="makeinfo-options.html#IDX380">Navigation links, omitting</a></td><td 
valign="top"><a href="makeinfo-options.html#SEC264">20.1.3 Options for 
<code>makeinfo</code></a></td></tr>
 <tr><td></td><td valign="top"><a href="need.html#SEC213">Need space at page 
bottom</a></td><td valign="top"><a href="need.html#SEC213">14.7 <code>@need 
<var>mils</var></code>: Prevent Page Breaks</a></td></tr>
@@ -172,7 +172,7 @@
 <tr><td></td><td valign="top"><a href="Node-Line-Requirements.html#IDX97">Node 
name, should not contain @-commands</a></td><td valign="top"><a 
href="Node-Line-Requirements.html#SEC92">6.3.4 <code>@node</code> Line 
Requirements</a></td></tr>
 <tr><td></td><td valign="top"><a href="Node-Names.html#SEC89">Node names, 
choosing</a></td><td valign="top"><a href="Node-Names.html#SEC89">6.3.1 
Choosing Node and Pointer Names</a></td></tr>
 <tr><td></td><td valign="top"><a href="makeinfo-options.html#IDX378">Node 
separators, omitting</a></td><td valign="top"><a 
href="makeinfo-options.html#SEC264">20.1.3 Options for 
<code>makeinfo</code></a></td></tr>
-<tr><td></td><td valign="top"><a href="The-Top-Node.html#SEC59">Node, 
`Top'</a></td><td valign="top"><a href="The-Top-Node.html#SEC59">3.5 The `Top' 
Node and Master Menu</a></td></tr>
+<tr><td></td><td valign="top"><a href="The-Top-Node.html#SEC59">Node, 
&lsquo;Top&rsquo;</a></td><td valign="top"><a 
href="The-Top-Node.html#SEC59">3.5 The &lsquo;Top&rsquo; Node and Master 
Menu</a></td></tr>
 <tr><td></td><td valign="top"><a href="node.html#SEC88">Node, 
defined</a></td><td valign="top"><a href="node.html#SEC88">6.3 The 
<code>@node</code> Command</a></td></tr>
 <tr><td></td><td valign="top"><a href="Menus.html#SEC98">Nodes for menus are 
short</a></td><td valign="top"><a href="Menus.html#SEC98">Menus Need Short 
Nodes</a></td></tr>
 <tr><td></td><td valign="top"><a href="Other-Info-Files.html#SEC103">Nodes in 
other Info files</a></td><td valign="top"><a 
href="Other-Info-Files.html#SEC103">7.5 Referring to Other Info 
Files</a></td></tr>
@@ -184,7 +184,7 @@
 <tr><th><a name="INDEX5_1">O</a></th><td></td><td></td></tr>
 <tr><td></td><td valign="top"><a 
href="Inserting-Accents.html#IDX212">&oslash;</a></td><td valign="top"><a 
href="Inserting-Accents.html#SEC183">13.3 Inserting Accents</a></td></tr>
 <tr><td></td><td valign="top"><a 
href="Inserting-Accents.html#IDX214">&Oslash;</a></td><td valign="top"><a 
href="Inserting-Accents.html#SEC183">13.3 Inserting Accents</a></td></tr>
-<tr><td></td><td valign="top"><a href="Using-Texinfo.html#IDX11">O'Dea, 
Brendan</a></td><td valign="top"><a href="Using-Texinfo.html#SEC4">1.2 Using 
Texinfo</a></td></tr>
+<tr><td></td><td valign="top"><a href="Using-Texinfo.html#IDX11">O&rsquo;Dea, 
Brendan</a></td><td valign="top"><a href="Using-Texinfo.html#SEC4">1.2 Using 
Texinfo</a></td></tr>
 <tr><td></td><td valign="top"><a href="Obtaining-TeX.html#SEC321">Obtaining 
TeX</a></td><td valign="top"><a href="Obtaining-TeX.html#SEC321">I. How to 
Obtain TeX</a></td></tr>
 <tr><td></td><td valign="top"><a href="Using-occur.html#SEC313">Occurrences, 
listing with <code>@occur</code></a></td><td valign="top"><a 
href="Using-occur.html#SEC313">F.4 Using <code>occur</code></a></td></tr>
 <tr><td></td><td valign="top"><a 
href="Inserting-Accents.html#IDX216">&oelig;</a></td><td valign="top"><a 
href="Inserting-Accents.html#SEC183">13.3 Inserting Accents</a></td></tr>
@@ -193,7 +193,7 @@
 <tr><td></td><td valign="top"><a href="makeinfo-options.html#SEC264">Options 
for <code>makeinfo</code></a></td><td valign="top"><a 
href="makeinfo-options.html#SEC264">20.1.3 Options for 
<code>makeinfo</code></a></td></tr>
 <tr><td></td><td valign="top"><a 
href="Raw-Formatter-Commands.html#SEC230">Ordinary HTML commands, 
using</a></td><td valign="top"><a 
href="Raw-Formatter-Commands.html#SEC230">16.3 Raw Formatter 
Commands</a></td></tr>
 <tr><td></td><td valign="top"><a 
href="Raw-Formatter-Commands.html#SEC230">Ordinary TeX commands, 
using</a></td><td valign="top"><a 
href="Raw-Formatter-Commands.html#SEC230">16.3 Raw Formatter 
Commands</a></td></tr>
-<tr><td></td><td valign="top"><a href="Other-Info-Files.html#SEC103">Other 
Info files' nodes</a></td><td valign="top"><a 
href="Other-Info-Files.html#SEC103">7.5 Referring to Other Info 
Files</a></td></tr>
+<tr><td></td><td valign="top"><a href="Other-Info-Files.html#SEC103">Other 
Info files&rsquo; nodes</a></td><td valign="top"><a 
href="Other-Info-Files.html#SEC103">7.5 Referring to Other Info 
Files</a></td></tr>
 <tr><td></td><td valign="top"><a 
href="Showing-the-Structure.html#SEC25">Outline of file structure, showing 
it</a></td><td valign="top"><a href="Showing-the-Structure.html#SEC25">2.3 
Showing the Section Structure of a File</a></td></tr>
 <tr><td></td><td valign="top"><a href="makeinfo-options.html#IDX383">Output 
file splitting</a></td><td valign="top"><a 
href="makeinfo-options.html#SEC264">20.1.3 Options for 
<code>makeinfo</code></a></td></tr>
 <tr><td></td><td valign="top"><a href="Using-Texinfo.html#IDX6">Output 
formats, supporting more</a></td><td valign="top"><a 
href="Using-Texinfo.html#SEC4">1.2 Using Texinfo</a></td></tr>

Index: Tests/nodes_texinfo_res/texinfo_292.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/texinfo_292.html,v
retrieving revision 1.74
retrieving revision 1.75
diff -u -b -r1.74 -r1.75
--- Tests/nodes_texinfo_res/texinfo_292.html    5 Feb 2007 15:30:25 -0000       
1.74
+++ Tests/nodes_texinfo_res/texinfo_292.html    3 Oct 2007 09:34:48 -0000       
1.75
@@ -251,7 +251,7 @@
 <tr><td></td><td valign="top"><a 
href="Catching-Mistakes.html#SEC308">Structure, catching mistakes 
in</a></td><td valign="top"><a href="Catching-Mistakes.html#SEC308">F. 
Formatting Mistakes</a></td></tr>
 <tr><td></td><td valign="top"><a href="Structuring.html#SEC72">Structuring of 
chapters</a></td><td valign="top"><a href="Structuring.html#SEC72">5. Chapter 
Structuring</a></td></tr>
 <tr><td></td><td valign="top"><a 
href="unnumberedsubsec-appendixsubsec-subheading.html#SEC82">Subsection-like 
commands</a></td><td valign="top"><a 
href="unnumberedsubsec-appendixsubsec-subheading.html#SEC82">5.10 The 
<code>@subsection</code>-like Commands</a></td></tr>
-<tr><td></td><td valign="top"><a href="subsubsection.html#SEC83">Subsub 
commands</a></td><td valign="top"><a href="subsubsection.html#SEC83">5.11 The 
`subsub' Commands</a></td></tr>
+<tr><td></td><td valign="top"><a href="subsubsection.html#SEC83">Subsub 
commands</a></td><td valign="top"><a href="subsubsection.html#SEC83">5.11 The 
&lsquo;subsub&rsquo; Commands</a></td></tr>
 <tr><td></td><td valign="top"><a href="Reporting-Bugs.html#SEC3">Suggestions 
for Texinfo, making</a></td><td valign="top"><a 
href="Reporting-Bugs.html#SEC3">1.1 Reporting Bugs</a></td></tr>
 <tr><td></td><td valign="top"><a href="documentdescription.html#SEC63">Summary 
of document</a></td><td valign="top"><a 
href="documentdescription.html#SEC63">3.6.1 <code>@documentdescription</code>: 
Summary text</a></td></tr>
 <tr><td></td><td valign="top"><a href="Conventions.html#SEC8">Syntactic 
conventions</a></td><td valign="top"><a href="Conventions.html#SEC8">1.6 
General Syntactic Conventions</a></td></tr>
@@ -266,7 +266,7 @@
 <tr><td></td><td valign="top"><a href="ftable-vtable.html#SEC161">Tables with 
indexes</a></td><td valign="top"><a href="ftable-vtable.html#SEC161">11.3.1 
<code>@ftable</code> and <code>@vtable</code></a></td></tr>
 <tr><td></td><td valign="top"><a 
href="Multi_002dcolumn-Tables.html#SEC163">Tables, making 
multi-column</a></td><td valign="top"><a 
href="Multi_002dcolumn-Tables.html#SEC163">11.4 Multi-column 
Tables</a></td></tr>
 <tr><td></td><td valign="top"><a 
href="Two_002dcolumn-Tables.html#SEC159">Tables, making two-column</a></td><td 
valign="top"><a href="Two_002dcolumn-Tables.html#SEC159">11.3 Making a 
Two-column Table</a></td></tr>
-<tr><td></td><td valign="top"><a href="Conventions.html#IDX15">Tabs; don't 
use!</a></td><td valign="top"><a href="Conventions.html#SEC8">1.6 General 
Syntactic Conventions</a></td></tr>
+<tr><td></td><td valign="top"><a href="Conventions.html#IDX15">Tabs; 
don&rsquo;t use!</a></td><td valign="top"><a href="Conventions.html#SEC8">1.6 
General Syntactic Conventions</a></td></tr>
 <tr><td></td><td valign="top"><a href="Tag-and-Split-Files.html#SEC269">Tag 
table, making automatically</a></td><td valign="top"><a 
href="Tag-and-Split-Files.html#SEC269">20.1.8 Tag Files and Split 
Files</a></td></tr>
 <tr><td></td><td valign="top"><a href="Unsplit.html#IDX463">Tag table, making 
manually</a></td><td valign="top"><a href="Unsplit.html#SEC316">F.5.2 Creating 
an Unsplit File</a></td></tr>
 <tr><td></td><td valign="top"><a href="anchor.html#SEC96">Targets for 
cross-references, arbitrary</a></td><td valign="top"><a 
href="anchor.html#SEC96">6.5 <code>@anchor</code>: Defining Arbitrary 
Cross-reference Targets</a></td></tr>
@@ -310,12 +310,12 @@
 <tr><td></td><td valign="top"><a href="titlepage.html#IDX82">Title page, 
bastard</a></td><td valign="top"><a href="titlepage.html#SEC53">3.4.1 
<code>@titlepage</code></a></td></tr>
 <tr><td></td><td valign="top"><a 
href="Titlepage-_0026-Copyright-Page.html#IDX77">Title page, for plain 
text</a></td><td valign="top"><a 
href="Titlepage-_0026-Copyright-Page.html#SEC52">3.4 Title and Copyright 
Pages</a></td></tr>
 <tr><td></td><td valign="top"><a href="end-titlepage.html#SEC57">Titlepage end 
starts headings</a></td><td valign="top"><a 
href="end-titlepage.html#SEC57">3.4.5 Heading Generation</a></td></tr>
-<tr><td></td><td valign="top"><a href="The-Top-Node.html#SEC59">Top 
node</a></td><td valign="top"><a href="The-Top-Node.html#SEC59">3.5 The `Top' 
Node and Master Menu</a></td></tr>
+<tr><td></td><td valign="top"><a href="The-Top-Node.html#SEC59">Top 
node</a></td><td valign="top"><a href="The-Top-Node.html#SEC59">3.5 The 
&lsquo;Top&rsquo; Node and Master Menu</a></td></tr>
 <tr><td></td><td valign="top"><a href="Top-Node-Example.html#SEC60">Top node 
example</a></td><td valign="top"><a href="Top-Node-Example.html#SEC60">3.5.1 
Top Node Example</a></td></tr>
 <tr><td></td><td valign="top"><a href="First-Node.html#SEC93">Top node is 
first</a></td><td valign="top"><a href="First-Node.html#SEC93">6.3.5 The First 
Node</a></td></tr>
-<tr><td></td><td valign="top"><a 
href="Top-Node-Naming.html#SEC114">&lsquo;<samp><span 
class="roman">Top</span></samp>&rsquo; node naming for references</a></td><td 
valign="top"><a href="Top-Node-Naming.html#SEC114">8.4 Naming a `Top' 
Node</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="Top-Node-Naming.html#SEC114">&lsquo;<samp><span 
class="roman">Top</span></samp>&rsquo; node naming for references</a></td><td 
valign="top"><a href="Top-Node-Naming.html#SEC114">8.4 Naming a 
&lsquo;Top&rsquo; Node</a></td></tr>
 <tr><td></td><td valign="top"><a href="Tree-Structuring.html#SEC73">Tree 
structuring</a></td><td valign="top"><a href="Tree-Structuring.html#SEC73">5.1 
Tree Structure of Sections</a></td></tr>
-<tr><td></td><td valign="top"><a href="deffnx.html#SEC217">Two `First' Lines 
for <code>@deffn</code></a></td><td valign="top"><a 
href="deffnx.html#SEC217">15.3 Two or More `First' Lines</a></td></tr>
+<tr><td></td><td valign="top"><a href="deffnx.html#SEC217">Two 
&lsquo;First&rsquo; Lines for <code>@deffn</code></a></td><td valign="top"><a 
href="deffnx.html#SEC217">15.3 Two or More &lsquo;First&rsquo; 
Lines</a></td></tr>
 <tr><td></td><td valign="top"><a href="syncodeindex.html#IDX156">Two letter 
names for indices</a></td><td valign="top"><a 
href="syncodeindex.html#SEC171">12.4.1 <code>@syncodeindex</code></a></td></tr>
 <tr><td></td><td valign="top"><a href="itemx.html#SEC162">Two named items for 
<code>@table</code></a></td><td valign="top"><a href="itemx.html#SEC162">11.3.2 
<code>@itemx</code></a></td></tr>
 <tr><td></td><td valign="top"><a 
href="Less-Cluttered-Menu-Entry.html#SEC101">Two part menu entry</a></td><td 
valign="top"><a href="Less-Cluttered-Menu-Entry.html#SEC101">7.3 Less Cluttered 
Menu Entry</a></td></tr>

Index: Tests/nodes_texinfo_res/texinfo_fot.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/texinfo_fot.html,v
retrieving revision 1.19
retrieving revision 1.20
diff -u -b -r1.19 -r1.20
--- Tests/nodes_texinfo_res/texinfo_fot.html    5 Feb 2007 15:30:25 -0000       
1.19
+++ Tests/nodes_texinfo_res/texinfo_fot.html    3 Oct 2007 09:34:48 -0000       
1.20
@@ -75,13 +75,13 @@
 but is not the same as, the pronunciation of TeX.  In the word
 TeX, the &lsquo;<samp>X</samp>&rsquo; is actually the Greek letter 
&ldquo;chi&rdquo; rather than
 the English letter &ldquo;ex&rdquo;.  Pronounce TeX as if the 
&lsquo;<samp>X</samp>&rsquo; were the
-last sound in the name `Bach'; but pronounce Texinfo as if the 
&lsquo;<samp>x</samp>&rsquo;
-were a `k'.  Spell &ldquo;Texinfo&rdquo; with a capital &ldquo;T&rdquo; and 
the other
+last sound in the name &lsquo;Bach&rsquo;; but pronounce Texinfo as if the 
&lsquo;<samp>x</samp>&rsquo;
+were a &lsquo;k&rsquo;.  Spell &ldquo;Texinfo&rdquo; with a capital 
&ldquo;T&rdquo; and the other
 letters in lower case.
 </p><h3><a name="FOOT2" href="Info-Files.html#DOCF2">(2)</a></h3>
-<p>In some documents, the first child has no `Previous'
+<p>In some documents, the first child has no &lsquo;Previous&rsquo;
 pointer.  Occasionally, the last child has the node name of the next
-following higher level node as its `Next' pointer.
+following higher level node as its &lsquo;Next&rsquo; pointer.
 </p><h3><a name="FOOT3" href="Printed-Books.html#DOCF3">(3)</a></h3>
 <p>You can also use the
 <a name="IDX13"></a>
@@ -96,15 +96,15 @@
 refer to a dispute between two people; it refers to the information
 presented to the command.  According to the <cite>Oxford English
 Dictionary</cite>, the word derives from the Latin for <em>to make clear,
-prove</em>; thus it came to mean `the evidence offered as proof', which is
-to say, `the information offered', which led to its mathematical
-meaning.  In its other thread of derivation, the word came to mean `to
-assert in a manner against which others may make counter assertions',
-which led to the meaning of `argument' as a dispute.
+prove</em>; thus it came to mean &lsquo;the evidence offered as proof&rsquo;, 
which is
+to say, &lsquo;the information offered&rsquo;, which led to its mathematical
+meaning.  In its other thread of derivation, the word came to mean &lsquo;to
+assert in a manner against which others may make counter assertions&rsquo;,
+which led to the meaning of &lsquo;argument&rsquo; as a dispute.
 </p><h3><a name="FOOT5" href="titlepage.html#DOCF5">(5)</a></h3>
 <p>We have found
 that it is helpful to refer to versions of independent manuals as
-`editions' and versions of programs as `versions'; otherwise, we find we
+&lsquo;editions&rsquo; and versions of programs as &lsquo;versions&rsquo;; 
otherwise, we find we
 are liable to confuse each other in conversation by referring to both
 the documentation and the software with the same words.
 </p><h3><a name="FOOT6" href="Menus.html#DOCF6">(6)</a></h3>

Index: Tests/nodes_texinfo_res/texinfo_toc.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/texinfo_toc.html,v
retrieving revision 1.22
retrieving revision 1.23
diff -u -b -r1.22 -r1.23
--- Tests/nodes_texinfo_res/texinfo_toc.html    30 Sep 2007 12:47:37 -0000      
1.22
+++ Tests/nodes_texinfo_res/texinfo_toc.html    3 Oct 2007 09:34:48 -0000       
1.23
@@ -126,7 +126,7 @@
       <li><a name="TOC40" href="end-titlepage.html#SEC57">3.4.5 Heading 
Generation</a></li>
       <li><a name="TOC41" href="headings-on-off.html#SEC58">3.4.6 The 
<code>@headings</code> Command</a></li>
     </ul></li>
-    <li><a name="TOC42" href="The-Top-Node.html#SEC59">3.5 The `Top' Node and 
Master Menu</a>
+    <li><a name="TOC42" href="The-Top-Node.html#SEC59">3.5 The 
&lsquo;Top&rsquo; Node and Master Menu</a>
     <ul class="toc">
       <li><a name="TOC43" href="Top-Node-Example.html#SEC60">3.5.1 Top Node 
Example</a></li>
       <li><a name="TOC44" href="Master-Menu-Parts.html#SEC61">3.5.2 Parts of a 
Master Menu</a></li>
@@ -158,7 +158,7 @@
     <li><a name="TOC63" 
href="unnumberedsec-appendixsec-heading.html#SEC80">5.8 
<code>@unnumberedsec</code>, <code>@appendixsec</code>, 
<code>@heading</code></a></li>
     <li><a name="TOC64" href="subsection.html#SEC81">5.9 The 
<code>@subsection</code> Command</a></li>
     <li><a name="TOC65" 
href="unnumberedsubsec-appendixsubsec-subheading.html#SEC82">5.10 The 
<code>@subsection</code>-like Commands</a></li>
-    <li><a name="TOC66" href="subsubsection.html#SEC83">5.11 The `subsub' 
Commands</a></li>
+    <li><a name="TOC66" href="subsubsection.html#SEC83">5.11 The 
&lsquo;subsub&rsquo; Commands</a></li>
     <li><a name="TOC67" href="Raise_002flower-sections.html#SEC84">5.12 
<code>@raisesections</code> and <code>@lowersections</code></a></li>
   </ul></li>
   <li><a name="TOC68" href="Nodes.html#SEC85">6. Nodes</a>
@@ -196,7 +196,7 @@
       <li><a name="TOC92" href="Three-Arguments.html#SEC112">8.3.3 
<code>@xref</code> with Three Arguments</a></li>
       <li><a name="TOC93" href="Four-and-Five-Arguments.html#SEC113">8.3.4 
<code>@xref</code> with Four and Five Arguments</a></li>
     </ul></li>
-    <li><a name="TOC94" href="Top-Node-Naming.html#SEC114">8.4 Naming a `Top' 
Node</a></li>
+    <li><a name="TOC94" href="Top-Node-Naming.html#SEC114">8.4 Naming a 
&lsquo;Top&rsquo; Node</a></li>
     <li><a name="TOC95" href="ref.html#SEC115">8.5 <code>@ref</code></a></li>
     <li><a name="TOC96" href="pxref.html#SEC116">8.6 
<code>@pxref</code></a></li>
     <li><a name="TOC97" href="inforef.html#SEC117">8.7 
<code>@inforef</code></a></li>
@@ -241,7 +241,7 @@
     <li><a name="TOC127" href="small.html#SEC148">10.7 
<code>@small&hellip;</code> Block Commands</a></li>
     <li><a name="TOC128" href="display.html#SEC149">10.8 <code>@display</code> 
and <code>@smalldisplay</code></a></li>
     <li><a name="TOC129" href="format.html#SEC150">10.9 <code>@format</code> 
and <code>@smallformat</code></a></li>
-    <li><a name="TOC130" href="exdent.html#SEC151">10.10 <code>@exdent</code>: 
Undoing a Line's Indentation</a></li>
+    <li><a name="TOC130" href="exdent.html#SEC151">10.10 <code>@exdent</code>: 
Undoing a Line&rsquo;s Indentation</a></li>
     <li><a name="TOC131" href="flushleft-_0026-flushright.html#SEC152">10.11 
<code>@flushleft</code> and <code>@flushright</code></a></li>
     <li><a name="TOC132" href="noindent.html#SEC153">10.12 
<code>@noindent</code>: Omitting Indentation</a></li>
     <li><a name="TOC133" href="cartouche.html#SEC154">10.13 
<code>@cartouche</code>: Rounded Rectangles Around Examples</a></li>
@@ -333,7 +333,7 @@
   <ul class="toc">
     <li><a name="TOC191" href="Def-Cmd-Template.html#SEC215">15.1 The Template 
for a Definition</a></li>
     <li><a name="TOC192" href="Optional-Arguments.html#SEC216">15.2 Optional 
and Repeated Arguments</a></li>
-    <li><a name="TOC193" href="deffnx.html#SEC217">15.3 Two or More `First' 
Lines</a></li>
+    <li><a name="TOC193" href="deffnx.html#SEC217">15.3 Two or More 
&lsquo;First&rsquo; Lines</a></li>
     <li><a name="TOC194" href="Def-Cmds-in-Detail.html#SEC218">15.4 The 
Definition Commands</a>
     <ul class="toc">
       <li><a name="TOC195" href="Functions-Commands.html#SEC219">15.4.1 
Functions and Similar Entities</a></li>

Index: Tests/nodes_texinfo_res/titlepage.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/titlepage.html,v
retrieving revision 1.18
retrieving revision 1.19
diff -u -b -r1.18 -r1.19
--- Tests/nodes_texinfo_res/titlepage.html      5 Feb 2007 15:30:25 -0000       
1.18
+++ Tests/nodes_texinfo_res/titlepage.html      3 Oct 2007 09:34:48 -0000       
1.19
@@ -106,8 +106,8 @@
 If the manual changes more frequently than the program or is independent
 of it, you should also include an edition number<a name="DOCF5" 
href="texinfo_fot.html#FOOT5">(5)</a> for the manual.
 This helps readers keep track of which manual is for which version of
-the program.  (The `Top' node should also contain this information; see
-<a href="The-Top-Node.html#SEC59">The `Top' Node and Master Menu</a>.)
+the program.  (The &lsquo;Top&rsquo; node should also contain this 
information; see
+<a href="The-Top-Node.html#SEC59">The &lsquo;Top&rsquo; Node and Master 
Menu</a>.)
 </p>
 <p>Texinfo provides two main methods for creating a title page.  One method
 uses the <code>@titlefont</code>, <code>@sp</code>, and <code>@center</code> 
commands

Index: Tests/nodes_texinfo_res/uref.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/uref.html,v
retrieving revision 1.22
retrieving revision 1.23
diff -u -b -r1.22 -r1.23
--- Tests/nodes_texinfo_res/uref.html   5 Feb 2007 15:30:25 -0000       1.22
+++ Tests/nodes_texinfo_res/uref.html   3 Oct 2007 09:34:48 -0000       1.23
@@ -143,15 +143,15 @@
 <p>To merely indicate a url without creating a link people can follow, use
 <code>@url</code> (see section <a 
href="url.html#SEC135"><code>@url</code></a>).
 </p>
-<p>Some people prefer to display url's in the unambiguous format:
+<p>Some people prefer to display url&rsquo;s in the unambiguous format:
 </p>
 <table><tr><td>&nbsp;</td><td><pre 
class="display">&lt;URL:http://<var>host</var>/<var>path</var>&gt;
 </pre></td></tr></table>
 
 <a name="IDX115"></a>
-<p>You can use this form in the input file if you wish.  We feel it's not
+<p>You can use this form in the input file if you wish.  We feel it&rsquo;s not
 necessary to clutter up the output with the extra 
&lsquo;<samp>&lt;URL:</samp>&rsquo; and
-&lsquo;<samp>&gt;</samp>&rsquo;, since any software that tries to detect url's 
in text already
+&lsquo;<samp>&gt;</samp>&rsquo;, since any software that tries to detect 
url&rsquo;s in text already
 has to detect them without the &lsquo;<samp>&lt;URL:</samp>&rsquo; to be 
useful.
 </p>
 

Index: Tests/nodes_texinfo_res/url.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/url.html,v
retrieving revision 1.19
retrieving revision 1.20
diff -u -b -r1.19 -r1.20
--- Tests/nodes_texinfo_res/url.html    5 Feb 2007 15:30:25 -0000       1.19
+++ Tests/nodes_texinfo_res/url.html    3 Oct 2007 09:34:48 -0000       1.20
@@ -85,7 +85,7 @@
 the World Wide Web.  This is analogous to <code>@file</code>, 
<code>@var</code>,
 etc., and is purely for markup purposes.  It does not produce a link you
 can follow in HTML output (use the <code>@uref</code> command for that,
-see section <a href="uref.html#SEC118"><code>@uref</code></a>).  It is useful 
for url's which do
+see section <a href="uref.html#SEC118"><code>@uref</code></a>).  It is useful 
for url&rsquo;s which do
 not actually exist.  For example:
 </p>
 <table><tr><td>&nbsp;</td><td><pre class="example">For example, the url might 
be @url{http://example.org/path}.

Index: Tests/nodes_texinfo_res/value-Example.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/value-Example.html,v
retrieving revision 1.23
retrieving revision 1.24
diff -u -b -r1.23 -r1.24
--- Tests/nodes_texinfo_res/value-Example.html  5 Feb 2007 15:30:25 -0000       
1.23
+++ Tests/nodes_texinfo_res/value-Example.html  3 Oct 2007 09:34:48 -0000       
1.24
@@ -85,7 +85,7 @@
 you need to change when you record an update to a manual.  See section <a 
href="GNU-Sample-Texts.html#SEC296">GNU Sample Texts</a>, for an example of 
this same principle can work with
 Automake distributions, and full texts.
 </p>
-<p>Here is an example adapted from <a 
href="../make/index.html#Top">(make)Top</a> section `Overview' in <cite>The GNU 
Make Manual</cite>):
+<p>Here is an example adapted from <a 
href="../make/index.html#Top">(make)Top</a> section &lsquo;Overview&rsquo; in 
<cite>The GNU Make Manual</cite>):
 </p>
 <ol>
 <li>

Index: Tests/nodes_texinfo_res/verb.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/nodes_texinfo_res/verb.html,v
retrieving revision 1.19
retrieving revision 1.20
diff -u -b -r1.19 -r1.20
--- Tests/nodes_texinfo_res/verb.html   5 Feb 2007 15:30:25 -0000       1.19
+++ Tests/nodes_texinfo_res/verb.html   3 Oct 2007 09:34:48 -0000       1.20
@@ -84,7 +84,7 @@
 <p>Use the <code>@verb</code> command to print a verbatim sequence of
 characters.
 </p>
-<p>Like LaTeX's <code>\verb</code> command, the verbatim text can be quoted 
using
+<p>Like LaTeX&rsquo;s <code>\verb</code> command, the verbatim text can be 
quoted using
 any unique delimiter character.  Enclose the verbatim text, including the
 delimiters, in braces.  Text is printed in a fixed-width font:
 </p>

Index: Tests/sectionning_res/novalidate.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/sectionning_res/novalidate.html,v
retrieving revision 1.14
retrieving revision 1.15
diff -u -b -r1.14 -r1.15
--- Tests/sectionning_res/novalidate.html       6 May 2007 12:57:07 -0000       
1.14
+++ Tests/sectionning_res/novalidate.html       3 Oct 2007 09:34:48 -0000       
1.15
@@ -54,7 +54,7 @@
 </tr></table>
 <h3 class="node"> first </h3>
 
-<p>See <a href="#it-doesn_0027t-exists">it doesn't exists</a>
+<p>See <a href="#it-doesn_0027t-exists">it doesn&rsquo;t exists</a>
 in first node
 </p><ul>
 <li> <a href="#node-in-menu-before-top"> node in menu before top</a>

Index: Tests/sectionning_res/novalidate_split_0.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/sectionning_res/novalidate_split_0.html,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -b -r1.2 -r1.3
--- Tests/sectionning_res/novalidate_split_0.html       5 Feb 2007 15:30:25 
-0000       1.2
+++ Tests/sectionning_res/novalidate_split_0.html       3 Oct 2007 09:34:48 
-0000       1.3
@@ -55,7 +55,7 @@
 <hr size="1">
 <h3 class="node"> first </h3>
 
-<p>See <a href="it-doesn_0027t-exists.html#it-doesn_0027t-exists">it doesn't 
exists</a>
+<p>See <a href="it-doesn_0027t-exists.html#it-doesn_0027t-exists">it 
doesn&rsquo;t exists</a>
 in first node
 </p><ul>
 <li> <a href="novalidate_split_1.html#node-in-menu-before-top"> node in menu 
before top</a>

Index: Tests/tar_res/tar.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/tar_res/tar.html,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -b -r1.4 -r1.5
--- Tests/tar_res/tar.html      7 May 2007 22:56:03 -0000       1.4
+++ Tests/tar_res/tar.html      3 Oct 2007 09:34:49 -0000       1.5
@@ -86,7 +86,7 @@
 and with the Back-Cover Texts as in (a) below.  A copy of the license
 is included in the section entitled &quot;GNU Free Documentation License&quot;.
 </p>
-<p>(a) The FSF's Back-Cover Text is: &ldquo;You are free to copy and modify
+<p>(a) The FSF&rsquo;s Back-Cover Text is: &ldquo;You are free to copy and 
modify
 this GNU Manual.  Buying copies from GNU Press supports the FSF in
 developing GNU and promoting software freedom.&rdquo;
 </p></blockquote>
@@ -357,7 +357,7 @@
 <tr><th colspan="3" align="left" valign="top"><pre class="menu-comment">
 Choosing Files and Names for <code>tar</code>
 
-</pre></th></tr><tr><td align="left" valign="top"><a href="#SEC98">6.1 
Choosing and Naming Archive Files</a></td><td>&nbsp;&nbsp;</td><td align="left" 
valign="top">                        Choosing the Archive's Name
+</pre></th></tr><tr><td align="left" valign="top"><a href="#SEC98">6.1 
Choosing and Naming Archive Files</a></td><td>&nbsp;&nbsp;</td><td align="left" 
valign="top">                        Choosing the Archive&rsquo;s Name
 </td></tr>
 <tr><td align="left" valign="top"><a href="#SEC99">6.2 Selecting Archive 
Members</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">
 </td></tr>
@@ -671,7 +671,7 @@
 all the members of an archive is often called <em>extracting the
 archive</em>.  The term <em>unpack</em> can also be used to refer to the
 extraction of many or all the members of an archive.  Extracting an
-archive does not destroy the archive's structure, just as creating an
+archive does not destroy the archive&rsquo;s structure, just as creating an
 archive does not destroy the copies of the files that exist outside of
 the archive.  You may also <em>list</em> the members in a given archive
 (this is often thought of as &ldquo;printing&rdquo; them to the standard 
output,
@@ -707,7 +707,7 @@
 </p>
 <p>Initially, <code>tar</code> archives were used to store files conveniently 
on
 magnetic tape.  The name <code>tar</code> comes from this use; it stands for
-<code>t</code>ape <code>ar</code>chiver.  Despite the utility's name, 
<code>tar</code> can
+<code>t</code>ape <code>ar</code>chiver.  Despite the utility&rsquo;s name, 
<code>tar</code> can
 direct its output to available devices, files, or other programs (using
 pipes).  <code>tar</code> may even access remote devices or files (as 
archives).
 </p>
@@ -1024,7 +1024,7 @@
 <p>In the examples, &lsquo;<samp>$</samp>&rsquo; represents a typical shell 
prompt.  It
 precedes lines you should type; to make this more clear, those lines are
 shown in <kbd>this font</kbd>, as opposed to lines which represent the
-computer's response; those lines are shown in <code>this font</code>, or
+computer&rsquo;s response; those lines are shown in <code>this font</code>, or
 sometimes &lsquo;<samp>like this</samp>&rsquo;.
 </p>
 
@@ -1234,7 +1234,7 @@
 that <code>tar</code> will work on.
 </p>
 <a name="IDX13"></a>
-<p>If you don't specify this argument, then <code>tar</code> will examine
+<p>If you don&rsquo;t specify this argument, then <code>tar</code> will examine
 the environment variable <code>TAPE</code>.  If it is set, its value will be
 used as the archive name.  Otherwise, <code>tar</code> will use the
 default archive, determined at the compile time. Usually it is
@@ -1344,7 +1344,7 @@
 <ul>
 <li> File type and permissions in symbolic form.
 These are displayed in the same format as the first column of
-<code>ls -l</code> output (see <a 
href="fileutils.html#What-information-is-listed">format=verbose: 
(fileutils)What information is listed</a> section `Verbose listing' in 
<cite>GNU file utilities</cite>).
+<code>ls -l</code> output (see <a 
href="fileutils.html#What-information-is-listed">format=verbose: 
(fileutils)What information is listed</a> section &lsquo;Verbose listing&rsquo; 
in <cite>GNU file utilities</cite>).
 
 </li><li> Owner name and group separated by a slash character.
 If these data are not available (for example, when listing a 
&lsquo;<samp>v7</samp>&rsquo; format
@@ -1560,11 +1560,11 @@
 <p>In general, you should check that the files to be archived exist where
 you think they do (in the working directory) by running <code>ls</code>.
 Because you just created the directory and the files and have changed to
-that directory, you probably don't need to do that this time.
+that directory, you probably don&rsquo;t need to do that this time.
 </p>
-<p>It is very important to make sure there isn't already a file in the
+<p>It is very important to make sure there isn&rsquo;t already a file in the
 working directory with the archive name you intend to use (in this case,
-&lsquo;<samp>collection.tar</samp>&rsquo;), or that you don't care about its 
contents.
+&lsquo;<samp>collection.tar</samp>&rsquo;), or that you don&rsquo;t care about 
its contents.
 Whenever you use &lsquo;<samp>create</samp>&rsquo;, <code>tar</code> will 
erase the current
 contents of the file named by 
&lsquo;<samp>--file=<var>archive-name</var></samp>&rsquo; (&lsquo;<samp>-f 
<var>archive-name</var></samp>&rsquo;) if it exists.  <code>tar</code>
 will not tell you if you are about to overwrite an archive unless you
@@ -1620,7 +1620,7 @@
 <p>The order of the options becomes more important when you begin to use
 short forms.  With short forms, if you type commands in the wrong order
 (even if you type them correctly in all other ways), you may end up with
-results you don't expect.  For this reason, it is a good idea to get
+results you don&rsquo;t expect.  For this reason, it is a good idea to get
 into the habit of typing options in the order that makes inherent sense.
 See section <a href="#SEC21">Short Forms with 
&lsquo;<samp>create</samp>&rsquo;</a>, for more information on this.
 </p>
@@ -1647,8 +1647,8 @@
 <p>Creating the archive &lsquo;<samp>collection.tar</samp>&rsquo; did not 
destroy the copies of
 the files in the directory.
 </p>
-<p>Keep in mind that if you don't indicate an operation, <code>tar</code> will 
not
-run and will prompt you for one.  If you don't name any files, <code>tar</code>
+<p>Keep in mind that if you don&rsquo;t indicate an operation, 
<code>tar</code> will not
+run and will prompt you for one.  If you don&rsquo;t name any files, 
<code>tar</code>
 will complain.  You must have write access to the working directory,
 or else you will not be able to create an archive in that directory.
 </p>
@@ -2072,7 +2072,7 @@
 
 <a name="IDX27"></a>
 <p>Creating an archive is only half the job&mdash;there is no point in storing
-files in an archive if you can't retrieve them.  The act of retrieving
+files in an archive if you can&rsquo;t retrieve them.  The act of retrieving
 members from an archive so they can be used and manipulated as
 unarchived files again is called <em>extraction</em>.  To extract files
 from an archive, use the &lsquo;<samp>--extract</samp>&rsquo; 
(&lsquo;<samp>--get</samp>&rsquo; or
@@ -2158,7 +2158,7 @@
 arguments, as printed by &lsquo;<samp>--list</samp>&rsquo; 
(&lsquo;<samp>-t</samp>&rsquo;).  If you had
 mistakenly deleted one of the files you had placed in the archive
 &lsquo;<tt>collection.tar</tt>&rsquo; earlier (say, 
&lsquo;<tt>blues</tt>&rsquo;), you can extract it
-from the archive without changing the archive's structure.  Its
+from the archive without changing the archive&rsquo;s structure.  Its
 contents will be identical to the original file &lsquo;<tt>blues</tt>&rsquo; 
that you
 deleted. 
 </p>
@@ -2186,7 +2186,7 @@
 name is important.  <kbd>tar --extract --file=bfiles.tar birds</kbd>
 will fail, because there is no member named &lsquo;<tt>birds</tt>&rsquo;.  To 
extract
 the member named &lsquo;<tt>./birds</tt>&rsquo;, you must specify <kbd>tar
---extract --file=bfiles.tar ./birds</kbd>.  If you don't remember the
+--extract --file=bfiles.tar ./birds</kbd>.  If you don&rsquo;t remember the
 exact member names, use &lsquo;<samp>--list</samp>&rsquo; 
(&lsquo;<samp>-t</samp>&rsquo;) option
 (see section <a href="#SEC23">How to List Archives</a>).  You can also extract 
those members that match a
 specific <em>globbing pattern</em>.  For example, to extract from
@@ -2248,11 +2248,11 @@
 </p>
 <p>We can demonstrate how to use &lsquo;<samp>--extract</samp>&rsquo; to 
extract a directory
 file with an example.  Change to the &lsquo;<tt>practice</tt>&rsquo; directory 
if you
-weren't there, and remove the files &lsquo;<tt>folk</tt>&rsquo; and 
&lsquo;<tt>jazz</tt>&rsquo;.  Then,
+weren&rsquo;t there, and remove the files &lsquo;<tt>folk</tt>&rsquo; and 
&lsquo;<tt>jazz</tt>&rsquo;.  Then,
 go back to the parent directory and extract the archive
 &lsquo;<tt>music.tar</tt>&rsquo;.  You may either extract the entire archive, 
or you may
 extract only the files you just deleted.  To extract the entire archive,
-don't give any file names as arguments after the archive name
+don&rsquo;t give any file names as arguments after the archive name
 &lsquo;<tt>music.tar</tt>&rsquo;.  To extract only the files you deleted, use 
the
 following command:
 </p>
@@ -2298,10 +2298,10 @@
 
 <p>Extracting files from archives can overwrite files that already exist.
 If you receive an archive from an untrusted source, you should make a
-new directory and extract into that directory, so that you don't have
+new directory and extract into that directory, so that you don&rsquo;t have
 to worry about the extraction overwriting one of your existing files.
 For example, if &lsquo;<tt>untrusted.tar</tt>&rsquo; came from somewhere else 
on the
-Internet, and you don't necessarily trust its contents, you can
+Internet, and you don&rsquo;t necessarily trust its contents, you can
 extract it as follows:
 </p>
 <table><tr><td>&nbsp;</td><td><pre class="smallexample">$ <kbd>mkdir 
newdir</kbd>
@@ -2335,7 +2335,7 @@
 <h3 class="subsection"> 2.8.5 Commands That Will Fail </h3>
 
 <p>Here are some sample commands you might try which will not work, and why
-they won't work.
+they won&rsquo;t work.
 </p>
 <p>If you try to use this command,
 </p>
@@ -2549,7 +2549,7 @@
 can also be read from a text file in the file system, using the
 &lsquo;<samp>--files-from=<var>file-of-names</var></samp>&rsquo; 
(&lsquo;<samp>-T <var>file-of-names</var></samp>&rsquo;) option.
 </p>
-<p>If you don't use any file name arguments, 
&lsquo;<samp>--append</samp>&rsquo; (&lsquo;<samp>-r</samp>&rsquo;),
+<p>If you don&rsquo;t use any file name arguments, 
&lsquo;<samp>--append</samp>&rsquo; (&lsquo;<samp>-r</samp>&rsquo;),
 &lsquo;<samp>--delete</samp>&rsquo; and 
&lsquo;<samp>--concatenate</samp>&rsquo; (&lsquo;<samp>--catenate</samp>&rsquo;,
 &lsquo;<samp>-A</samp>&rsquo;) will do nothing, while 
&lsquo;<samp>--create</samp>&rsquo; (&lsquo;<samp>-c</samp>&rsquo;)
 will usually yield a diagnostic and inhibit <code>tar</code> execution.
@@ -2571,7 +2571,7 @@
 clearly diagnosed on <code>stderr</code>, after a line stating the nature of
 the error.
 </p>
-<p><acronym>GNU</acronym> <code>tar</code> returns only a few exit statuses.  
I'm really
+<p><acronym>GNU</acronym> <code>tar</code> returns only a few exit statuses.  
I&rsquo;m really
 aiming simplicity in that area, for now.  If you are not using the
 &lsquo;<samp>--compare</samp>&rsquo; &lsquo;<samp>--diff</samp>&rsquo;, 
&lsquo;<samp>-d</samp>&rsquo;) option, zero means
 that everything went well, besides maybe innocuous warnings.  Nonzero
@@ -2611,7 +2611,7 @@
 looks, or the format of the files that you wish to archive may require
 you to do something special in order to make the archive look right.
 </p>
-<p>You can customize and control <code>tar</code>'s performance by running
+<p>You can customize and control <code>tar</code>&rsquo;s performance by 
running
 <code>tar</code> with one or more options (such as 
&lsquo;<samp>--verbose</samp>&rsquo;
 (&lsquo;<samp>-v</samp>&rsquo;), which we used in the tutorial).  As we said 
in the
 tutorial, <em>options</em> are arguments to <code>tar</code> which are (as
@@ -2733,10 +2733,10 @@
 other long option which begins with &lsquo;<samp>cre</samp>&rsquo;.  (One way 
to find
 this out is by trying it and seeing what happens; if a particular
 abbreviation could represent more than one option, <code>tar</code> will tell
-you that that abbreviation is ambiguous and you'll know that that
-abbreviation won't work.  You may also choose to run &lsquo;<samp>tar 
--help</samp>&rsquo;
+you that that abbreviation is ambiguous and you&rsquo;ll know that that
+abbreviation won&rsquo;t work.  You may also choose to run &lsquo;<samp>tar 
--help</samp>&rsquo;
 to see a list of options.  Be aware that if you run <code>tar</code> with a
-unique abbreviation for the long name of an option you didn't want to
+unique abbreviation for the long name of an option you didn&rsquo;t want to
 use, you are stuck; <code>tar</code> will perform the command as ordered.)
 </p>
 <p>Long options are meant to be obvious and easy to remember, and their
@@ -2804,7 +2804,7 @@
 immediately following the option letter, <em>without any intervening
 white space characters</em>.
 </p>
-<p>Short options' letters may be clumped together, but you are not
+<p>Short options&rsquo; letters may be clumped together, but you are not
 required to do this (as compared to old options; see below).  When
 short options are clumped as a set, use one (single) dash for them
 all, e.g., &lsquo;<samp><code>tar</code> -cvf</samp>&rsquo;.  Only the last 
option in
@@ -2817,7 +2817,7 @@
 <table><tr><td>&nbsp;</td><td><pre class="smallexample">$ <kbd>tar -c -v -b 20 
-f /dev/rmt0</kbd>
 </pre></td></tr></table>
 
-<p>If you reorder short options' locations, be sure to move any arguments
+<p>If you reorder short options&rsquo; locations, be sure to move any arguments
 that belong to them.  If you do not move the arguments properly, you may
 end up overwriting files.
 </p>
@@ -2907,7 +2907,7 @@
 supports them not only for historical reasons, but also because many
 people are used to them.  For compatibility with Unix <code>tar</code>,
 the first argument is always treated as containing command and option
-letters even if it doesn't start with &lsquo;<samp>-</samp>&rsquo;.  Thus, 
&lsquo;<samp>tar c</samp>&rsquo; is
+letters even if it doesn&rsquo;t start with &lsquo;<samp>-</samp>&rsquo;.  
Thus, &lsquo;<samp>tar c</samp>&rsquo; is
 equivalent to &lsquo;<samp>tar -c</samp>&rsquo;: both of them specify the
 &lsquo;<samp>--create</samp>&rsquo; (&lsquo;<samp>-c</samp>&rsquo;) command to 
create an archive.
 </p>
@@ -3101,7 +3101,7 @@
 </p></dd>
 <dt> &lsquo;<samp>--delete</samp>&rsquo;</dt>
 <dd>
-<p>Deletes members from the archive.  Don't try this on a archive on a
+<p>Deletes members from the archive.  Don&rsquo;t try this on a archive on a
 tape!  See section <a href="#SEC58">Removing Archive Members Using 
&lsquo;<samp>--delete</samp>&rsquo;</a>.
 </p>
 <p><a name="g_t_002d_002ddiff"></a>
@@ -3193,7 +3193,7 @@
 <a name="IDX45"></a>
 </p></dd>
 <dt> &lsquo;<samp>--anchored</samp>&rsquo;</dt>
-<dd><p>A pattern must match an initial subsequence of the name's components.
+<dd><p>A pattern must match an initial subsequence of the name&rsquo;s 
components.
 See section <a href="#SEC105">Controlling Pattern-Matching</a>.
 </p>
 <p><a name="g_t_002d_002datime_002dpreserve"></a>
@@ -3289,7 +3289,7 @@
 <p>This option directs <code>tar</code> to print periodic checkpoint
 messages as it reads through the archive.  It is intended for when you
 want a visual indication that <code>tar</code> is still running, but
-don't want to see &lsquo;<samp>--verbose</samp>&rsquo; output.  For a detailed
+don&rsquo;t want to see &lsquo;<samp>--verbose</samp>&rsquo; output.  For a 
detailed
 description, see <a href="#Progress-information">Progress information</a>.
 </p>
 <p><a name="g_t_002d_002dcheck_002dlinks"></a>
@@ -3382,7 +3382,7 @@
 <dt> &lsquo;<samp>-f <var>archive</var></samp>&rsquo;</dt>
 <dd>
 <p><code>tar</code> will use the file <var>archive</var> as the 
<code>tar</code> archive it
-performs operations on, rather than <code>tar</code>'s compilation dependent
+performs operations on, rather than <code>tar</code>&rsquo;s compilation 
dependent
 default.  See section <a href="#SEC14">The &lsquo;<samp>--file</samp>&rsquo; 
Option</a>.
 </p>
 <p><a name="g_t_002d_002dfiles_002dfrom"></a>
@@ -3666,7 +3666,7 @@
 <a name="IDX91"></a>
 </p></dd>
 <dt> &lsquo;<samp>--no-anchored</samp>&rsquo;</dt>
-<dd><p>An exclude pattern can match any subsequence of the name's components.
+<dd><p>An exclude pattern can match any subsequence of the name&rsquo;s 
components.
 See section <a href="#SEC105">Controlling Pattern-Matching</a>.
 </p>
 <p><a name="g_t_002d_002dno_002ddelay_002ddirectory_002drestore"></a>
@@ -3731,7 +3731,7 @@
 </p></dd>
 <dt> &lsquo;<samp>--no-same-permissions</samp>&rsquo;</dt>
 <dd>
-<p>When extracting an archive, subtract the user's umask from files from
+<p>When extracting an archive, subtract the user&rsquo;s umask from files from
 the permissions specified in the archive.  This is the default behavior
 for ordinary users.
 </p>
@@ -3936,7 +3936,7 @@
 <dt> &lsquo;<samp>-p</samp>&rsquo;</dt>
 <dd>
 <p>When <code>tar</code> is extracting an archive, it normally subtracts the
-users' umask from the permissions specified in the archive and uses
+users&rsquo; umask from the permissions specified in the archive and uses
 that number as the permissions to create the destination file.
 Specifying this option instructs <code>tar</code> that it should use the
 permissions directly from the archive.  See section <a href="#SEC75">Setting 
Access Permissions</a>.
@@ -4243,7 +4243,7 @@
 </p></dd>
 <dt> &lsquo;<samp>--version</samp>&rsquo;</dt>
 <dd>
-<p>Print information about the program's name, version, origin and legal
+<p>Print information about the program&rsquo;s name, version, origin and legal
 status, all on standard output, and then exit successfully.
 See section <a href="#SEC44"><acronym>GNU</acronym> <code>tar</code> 
documentation</a>.
 </p>
@@ -4692,7 +4692,7 @@
 <a name="IDX168"></a>
 The &lsquo;<samp>--checkpoint</samp>&rsquo; option prints an occasional message
 as <code>tar</code> reads or writes the archive.  It is designed for
-those who don't need the more detailed (and voluminous) output of
+those who don&rsquo;t need the more detailed (and voluminous) output of
 &lsquo;<samp>--block-number</samp>&rsquo; (&lsquo;<samp>-R</samp>&rsquo;), but 
do want visual confirmation
 that <code>tar</code> is actually making forward progress.  By default it
 prints a message each 10 records read or written.  This can be changed
@@ -4927,7 +4927,7 @@
 people should get used to ISO 8601 dates.  Local American dates should
 be made available again with full date localization support, once
 ready.  In the meantime, programs not being localizable for dates
-should prefer international dates, that's really the way to go.
+should prefer international dates, that&rsquo;s really the way to go.
 </p>
 <p>Look up <a 
href="http://www.cl.cam.ac.uk/~mgk25/iso-time.html";>http://www.cl.cam.ac.uk/~mgk25/iso-time.html</a>
 if you
 are curious, it contains a detailed explanation of the ISO 8601 standard.
@@ -4960,7 +4960,7 @@
 to learn about further ways in which <code>tar</code> can help you.
 </p>
 <p>This chapter presents five, more advanced operations which you probably
-won't use on a daily basis, but which serve more specialized functions.
+won&rsquo;t use on a daily basis, but which serve more specialized functions.
 We also explain the different styles of options and why you might want
 to use one or another, or a combination of them in your <code>tar</code>
 commands.  Additionally, this chapter includes options which allow you to
@@ -5087,7 +5087,7 @@
 
 
 <a name="IDX176"></a>
-<p>If you want to add files to an existing archive, you don't need to
+<p>If you want to add files to an existing archive, you don&rsquo;t need to
 create a new archive; you can use &lsquo;<samp>--append</samp>&rsquo; 
(&lsquo;<samp>-r</samp>&rsquo;).
 The archive must already exist in order to use 
&lsquo;<samp>--append</samp>&rsquo;.  (A
 related operation is the &lsquo;<samp>--update</samp>&rsquo; operation; you 
can use this
@@ -5103,7 +5103,7 @@
 view an archive with &lsquo;<samp>--list</samp>&rsquo; 
(&lsquo;<samp>-t</samp>&rsquo;), you will see all
 of those members listed, with their data modification times, owners, etc.
 </p>
-<p>Other operations don't deal with these members as perfectly as you might
+<p>Other operations don&rsquo;t deal with these members as perfectly as you 
might
 prefer; if you were to use &lsquo;<samp>--extract</samp>&rsquo; to extract the 
archive,
 only the most recently added copy of a member with the same name as four
 other members would end up in the working directory.  This is because
@@ -5368,8 +5368,8 @@
 <h4 class="subsubsection"> 4.2.3.1 How to Update an Archive Using 
&lsquo;<samp>--update</samp>&rsquo; </h4>
 
 <p>You must use file name arguments with the 
&lsquo;<samp>--update</samp>&rsquo;
-(&lsquo;<samp>-u</samp>&rsquo;) operation.  If you don't specify any files,
-<code>tar</code> won't act on any files and won't tell you that it didn't
+(&lsquo;<samp>-u</samp>&rsquo;) operation.  If you don&rsquo;t specify any 
files,
+<code>tar</code> won&rsquo;t act on any files and won&rsquo;t tell you that it 
didn&rsquo;t
 do anything (which may end up confusing you).
 </p>
 
@@ -5709,7 +5709,7 @@
 <var>permissions</var> for the archive members, rather than the permissions
 from the files.  <var>permissions</var> can be specified either as an octal
 number or as symbolic permissions, like with
-<code>chmod</code> (See <a href="fileutils.html#File-permissions">Permissions: 
(fileutils)File permissions</a> section `File permissions' in 
<cite><acronym>GNU</acronym> file utilities</cite>.  This reference
+<code>chmod</code> (See <a href="fileutils.html#File-permissions">Permissions: 
(fileutils)File permissions</a> section &lsquo;File permissions&rsquo; in 
<cite><acronym>GNU</acronym> file utilities</cite>.  This reference
 also has useful information for those not being overly familiar with
 the UNIX permission system).  Using latter syntax allows for
 more flexibility.  For example, the value &lsquo;<samp>a+rw</samp>&rsquo; adds 
read and write
@@ -5894,7 +5894,7 @@
 less than was requested.  If this option were not enabled, <code>tar</code>
 would fail as soon as it read an incomplete record from the pipe.
 </p>
-<p>If you're not sure of the blocking factor of an archive, you can
+<p>If you&rsquo;re not sure of the blocking factor of an archive, you can
 read the archive by specifying &lsquo;<samp>--read-full-records</samp>&rsquo; 
(&lsquo;<samp>-B</samp>&rsquo;) and
 &lsquo;<samp>--blocking-factor=<var>512-size</var></samp>&rsquo; 
(&lsquo;<samp>-b
 <var>512-size</var></samp>&rsquo;), using a blocking factor larger than what 
the archive
@@ -6518,7 +6518,7 @@
 </dl>
 
 <p>This can be useful, for example, if you have a tar archive containing
-a big file and don't want to store the file on disk before processing
+a big file and don&rsquo;t want to store the file on disk before processing
 it.  You can use a command like this:
 </p>
 <table><tr><td>&nbsp;</td><td><pre class="smallexample">tar -xOzf foo.tgz 
bigfile | process
@@ -6876,7 +6876,7 @@
 on systems having file name limitations, making different members appear
 has having similar names through the side-effect of name truncation.
 (This is true only if we have a good scheme for truncated backup names,
-which I'm not sure at all: I suspect work is needed in this area.)
+which I&rsquo;m not sure at all: I suspect work is needed in this area.)
 When any existing file is backed up before being overwritten by extraction,
 then clashing files are automatically be renamed to be unique, and the
 true name is kept for only the last file of a series of clashing files.
@@ -6993,7 +6993,7 @@
 mail).  Both machines do not have to use the same operating system, as
 long as they both support the <code>tar</code> program.
 </p>
-<p>For example, here is how you might copy a directory's contents from
+<p>For example, here is how you might copy a directory&rsquo;s contents from
 one disk to another, while preserving the dates, modes, owners and
 link-structure of all the files therein.  In this case, the transfer
 medium is a <em>pipe</em>, which is one a Unix redirection mechanism:
@@ -7149,7 +7149,7 @@
 <p>Full dumps should only be made when no other people or programs
 are modifying files in the file system.  If files are modified while
 <code>tar</code> is making the backup, they may not be stored properly in
-the archive, in which case you won't be able to restore them if you
+the archive, in which case you won&rsquo;t be able to restore them if you
 have to.  (Files not being modified are written with no trouble, and do
 not corrupt the entire archive.)
 </p>
@@ -7280,7 +7280,7 @@
 </pre></td></tr></table>
 
 <p>Incremental dumps depend crucially on time stamps, so the results are
-unreliable if you modify a file's time stamps during dumping (e.g.,
+unreliable if you modify a file&rsquo;s time stamps during dumping (e.g.,
 with the &lsquo;<samp>--atime-preserve=replace</samp>&rsquo; option), or if 
you set the clock
 backwards.
 </p>
@@ -7458,7 +7458,7 @@
 functions within that script (e.g., see <code>RESTORE_BEGIN</code> below).
 For more information about shell script syntax, please refer to
 <a 
href="http://www.opengroup.org/onlinepubs/009695399/utilities/xcu_chap02.html#ta
 g_02">the definition of the Shell Command Language</a>.  See also
-<a href="bashref.html#Top">(bashref)Top</a> section `Bash Features' in 
<cite>Bash Reference Manual</cite>.
+<a href="bashref.html#Top">(bashref)Top</a> section &lsquo;Bash 
Features&rsquo; in <cite>Bash Reference Manual</cite>.
 </p>
 <p>The shell variables controlling behavior of <code>backup</code> and
 <code>restore</code> are described in the following subsections.
@@ -7650,9 +7650,9 @@
 <dt><u>Backup variable:</u> <b>DUMP_REMIND_SCRIPT</b>
 <a name="IDX277"></a>
 </dt>
-<dd><p>Script to be run when it's time to insert a new tape in for the next
+<dd><p>Script to be run when it&rsquo;s time to insert a new tape in for the 
next
 volume.  Administrators may want to tailor this script for their site.
-If this variable isn't set, <acronym>GNU</acronym> <code>tar</code> will 
display its built-in
+If this variable isn&rsquo;t set, <acronym>GNU</acronym> <code>tar</code> will 
display its built-in
 prompt, and will expect confirmation from the console.  For the
 description of the default prompt, see <a href="#change-volume-prompt">change 
volume prompt</a>.
 </p>
@@ -7960,7 +7960,7 @@
 
 <p>You should start a script with a tape or disk mounted.  Once you
 start a script, it prompts you for new tapes or disks as it
-needs them.  Media volumes don't have to correspond to archive
+needs them.  Media volumes don&rsquo;t have to correspond to archive
 files &mdash; a multi-volume archive can be started in the middle of a
 tape that already contains the end of another multi-volume archive.
 The <code>restore</code> script prompts for media by its archive volume,
@@ -7996,7 +7996,7 @@
 </dd>
 <dt> &lsquo;<samp>-f</samp>&rsquo;</dt>
 <dt> &lsquo;<samp>--force</samp>&rsquo;</dt>
-<dd><p>Force backup even if today's log file already exists.
+<dd><p>Force backup even if today&rsquo;s log file already exists.
 </p>
 </dd>
 <dt> &lsquo;<samp>-v[<var>level</var>]</samp>&rsquo;</dt>
@@ -8018,7 +8018,7 @@
 </dd>
 <dt> &lsquo;<samp>-V</samp>&rsquo;</dt>
 <dt> &lsquo;<samp>--version</samp>&rsquo;</dt>
-<dd><p>Display information about the program's name, version, origin and legal
+<dd><p>Display information about the program&rsquo;s name, version, origin and 
legal
 status, all on standard output, and then exit successfully.
 </p></dd>
 </dl>
@@ -8104,14 +8104,14 @@
 </dd>
 <dt> &lsquo;<samp>-V</samp>&rsquo;</dt>
 <dt> &lsquo;<samp>--version</samp>&rsquo;</dt>
-<dd><p>Display information about the program's name, version, origin and legal
+<dd><p>Display information about the program&rsquo;s name, version, origin and 
legal
 status, all on standard output, and then exit successfully.
 </p></dd>
 </dl>
 
 <p>You should start the restore script with the media containing the
 first volume of the archive mounted.  The script will prompt for other
-volumes as they are needed.  If the archive is on tape, you don't need
+volumes as they are needed.  If the archive is on tape, you don&rsquo;t need
 to rewind the tape to to its beginning&mdash;if the tape head is
 positioned past the beginning of the archive, the script will rewind
 the tape as needed.  See section <a href="#SEC151">Tape Positions and Tape 
Marks</a>, for a discussion of tape
@@ -8151,13 +8151,13 @@
 <p>Certain options to <code>tar</code> enable you to specify a name for your
 archive.  Other options let you decide which files to include or exclude
 from the archive, based on when or whether files were modified, whether
-the file names do or don't match specified patterns, or whether files
+the file names do or don&rsquo;t match specified patterns, or whether files
 are in specified directories.
 </p>
 <p>This chapter discusses these options in detail.
 </p>
 <table class="menu" border="0" cellspacing="0">
-<tr><td align="left" valign="top"><a href="#SEC98">6.1 Choosing and Naming 
Archive Files</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">       
                 Choosing the Archive's Name
+<tr><td align="left" valign="top"><a href="#SEC98">6.1 Choosing and Naming 
Archive Files</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">       
                 Choosing the Archive&rsquo;s Name
 </td></tr>
 <tr><td align="left" valign="top"><a href="#SEC99">6.2 Selecting Archive 
Members</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">
 </td></tr>
@@ -8229,7 +8229,7 @@
 follow the &lsquo;<samp>-f</samp>&rsquo; option, since whatever directly 
follows &lsquo;<samp>-f</samp>&rsquo;
 <em>will</em> end up naming the archive.  If you neglect to specify an
 archive name, you may end up overwriting a file in the working directory
-with the archive you create since <code>tar</code> will use this file's name
+with the archive you create since <code>tar</code> will use this file&rsquo;s 
name
 for the archive name.
 </p>
 <p>An archive can be saved as a file in the file system, sent through a
@@ -8943,7 +8943,7 @@
 names end in &lsquo;<samp>.txt</samp>&rsquo; and the file named 
&lsquo;<tt>[remarks]</tt>&rsquo;.
 </p>
 <p>Normally, a pattern matches a name if an initial subsequence of the
-name's components matches the pattern, where &lsquo;<samp>*</samp>&rsquo;, 
&lsquo;<samp>?</samp>&rsquo;, and
+name&rsquo;s components matches the pattern, where 
&lsquo;<samp>*</samp>&rsquo;, &lsquo;<samp>?</samp>&rsquo;, and
 &lsquo;<samp>[...]</samp>&rsquo; are the usual shell wildcards, 
&lsquo;<samp>\</samp>&rsquo; escapes wildcards,
 and wildcards can match &lsquo;<samp>/</samp>&rsquo;.
 </p>
@@ -8968,7 +8968,7 @@
 <dt> &lsquo;<samp>--anchored</samp>&rsquo;</dt>
 <dt> &lsquo;<samp>--no-anchored</samp>&rsquo;</dt>
 <dd><p>If anchored, a pattern must match an initial subsequence
-of the name's components.  Otherwise, the pattern can match any
+of the name&rsquo;s components.  Otherwise, the pattern can match any
 subsequence.  Default is &lsquo;<samp>--no-anchored</samp>&rsquo; for 
exclusion members
 and &lsquo;<samp>--anchored</samp>&rsquo; inclusion members.
 </p>
@@ -8995,7 +8995,7 @@
 <p>The &lsquo;<samp>--recursion</samp>&rsquo; and 
&lsquo;<samp>--no-recursion</samp>&rsquo; options
 (see section <a href="#SEC109">Descending into Directories</a>) also affect 
how member patterns are interpreted.  If
 recursion is in effect, a pattern matches a name if it matches any of
-the name's parent directories.
+the name&rsquo;s parent directories.
 </p>
 <p>The following table summarizes pattern-matching default values:
 </p>
@@ -9402,7 +9402,7 @@
 <p>where <var>regexp</var> is a <em>regular expression</em>, 
<var>replace</var> is a
 replacement for each file name part that matches <var>regexp</var>.  Both
 <var>regexp</var> and <var>replace</var> are described in detail in
-<a href="sed.html#The-_0022s_0022-Command">The &quot;s&quot; Command: (sed)The 
&quot;s&quot; Command</a> section `The `s' Command' in <cite>GNU sed</cite>.
+<a href="sed.html#The-_0022s_0022-Command">The &quot;s&quot; Command: (sed)The 
&quot;s&quot; Command</a> section &lsquo;The &lsquo;s&rsquo; Command&rsquo; in 
<cite>GNU sed</cite>.
 </p>
 <p>Supported <var>flags</var> are:
 </p>
@@ -9417,7 +9417,7 @@
 </p>
 </dd>
 <dt> &lsquo;<samp>x</samp>&rsquo;</dt>
-<dd><p><var>regexp</var> is an <em>extended regular expression</em> (see <a 
href="sed.html#Extended-regexps">Extended regular expressions: (sed)Extended 
regexps</a> section `Extended regular expressions' in <cite>GNU sed</cite>).
+<dd><p><var>regexp</var> is an <em>extended regular expression</em> (see <a 
href="sed.html#Extended-regexps">Extended regular expressions: (sed)Extended 
regexps</a> section &lsquo;Extended regular expressions&rsquo; in <cite>GNU 
sed</cite>).
 </p>
 </dd>
 <dt> &lsquo;<samp><var>number</var></samp>&rsquo;</dt>
@@ -9529,7 +9529,7 @@
 only extract files newer than the <var>date</var> you specify.
 </p>
 <p>If you only want <code>tar</code> to make the date comparison based on
-modification of the file's data (rather than status
+modification of the file&rsquo;s data (rather than status
 changes), then use the 
&lsquo;<samp>--newer-mtime=<var>date</var></samp>&rsquo; option.
 </p>
 <p>You may use these options with any operation.  Note that these options
@@ -9560,7 +9560,7 @@
 </dl>
 
 <p>These options limit <code>tar</code> to operate only on files which have
-been modified after the date specified.  A file's status is considered to have
+been modified after the date specified.  A file&rsquo;s status is considered 
to have
 changed if its contents have been modified, or if its owner,
 permissions, and so forth, have been changed.  (For more information on
 how to specify a date, see <a href="#SEC113">Date input formats</a>; remember 
that the
@@ -9569,7 +9569,7 @@
 <p>Gurus would say that &lsquo;<samp>--after-date</samp>&rsquo; tests both the 
data
 modification time (<code>mtime</code>, the time the contents of the file
 were last modified) and the status change time (<code>ctime</code>, the time
-the file's status was last changed: owner, permissions, etc.)
+the file&rsquo;s status was last changed: owner, permissions, etc.)
 fields, while &lsquo;<samp>--newer-mtime</samp>&rsquo; tests only the 
<code>mtime</code>
 field.
 </p>
@@ -9642,7 +9642,7 @@
 want <code>tar</code> to act this way.
 </p>
 <a name="IDX341"></a>
-<p>The &lsquo;<samp>--no-recursion</samp>&rsquo; option inhibits 
<code>tar</code>'s recursive descent
+<p>The &lsquo;<samp>--no-recursion</samp>&rsquo; option inhibits 
<code>tar</code>&rsquo;s recursive descent
 into specified directories.  If you specify 
&lsquo;<samp>--no-recursion</samp>&rsquo;, you can
 use the <code>find</code> utility for hunting through levels of directories to
 construct a list of file names which you could then pass to <code>tar</code>.
@@ -9667,7 +9667,7 @@
 recursively.  Many people use <code>find</code> for locating files they
 want to back up, and since <code>tar</code> <em>usually</em> recursively
 descends on directories, they have to use the &lsquo;<samp>-not -type 
d</samp>&rsquo;
-test in their <code>find</code> invocation (see <a href="find.html#Type">Type: 
(find)Type</a> section `Type test' in <cite>Finding Files</cite>), as they 
usually do not want all the files in a
+test in their <code>find</code> invocation (see <a href="find.html#Type">Type: 
(find)Type</a> section &lsquo;Type test&rsquo; in <cite>Finding Files</cite>), 
as they usually do not want all the files in a
 directory. They then use the &lsquo;<samp>--files-from</samp>&rsquo; option to 
archive
 the files located via <code>find</code>.
 </p>
@@ -10381,7 +10381,7 @@
 <p>Time zone items other than &lsquo;<samp>UTC</samp>&rsquo; and 
&lsquo;<samp>Z</samp>&rsquo;
 are obsolescent and are not recommended, because they
 are ambiguous; for example, &lsquo;<samp>EST</samp>&rsquo; has a different 
meaning in
-Australia than in the United States.  Instead, it's better to use
+Australia than in the United States.  Instead, it&rsquo;s better to use
 unambiguous numeric time zone corrections like 
&lsquo;<samp>-0500</samp>&rsquo;, as
 described in the previous section.
 </p>
@@ -10611,7 +10611,7 @@
 to <acronym>POSIX</acronym>, using negative counts, so that 
&lsquo;<samp>@-1</samp>&rsquo;
 represents 1969-12-31 23:59:59 <small>UTC</small>.
 </p>
-<p>Traditional Unix systems count seconds with 32-bit two's-complement
+<p>Traditional Unix systems count seconds with 32-bit two&rsquo;s-complement
 integers and can represent times from 1901-12-13 20:45:52 through
 2038-01-19 03:14:07 <small>UTC</small>.  More modern systems use 64-bit counts
 of seconds with nanosecond subcounts, and can represent all the times
@@ -10686,7 +10686,7 @@
 database, you may need to use a <acronym>POSIX</acronym> rule instead.  Simple
 <acronym>POSIX</acronym> rules like &lsquo;<samp>UTC0</samp>&rsquo; specify a 
time zone without
 daylight saving time; other rules can specify simple daylight saving
-regimes.  See <a href="libc.html#TZ-Variable">(libc)TZ Variable</a> section 
`Specifying the Time Zone with <code>TZ</code>' in <cite>The GNU C 
Library</cite>.
+regimes.  See <a href="libc.html#TZ-Variable">(libc)TZ Variable</a> section 
&lsquo;Specifying the Time Zone with <code>TZ</code>&rsquo; in <cite>The GNU C 
Library</cite>.
 </p>
 <hr size="6">
 <a name="Authors-of-get_005fdate"></a>
@@ -10931,7 +10931,7 @@
 <table><tr><td>&nbsp;</td><td><pre class="smallexample">$ <kbd>tar cfz 
archive.tar.gz .</kbd>
 </pre></td></tr></table>
 
-<p>Reading compressed archive is even simpler: you don't need to specify
+<p>Reading compressed archive is even simpler: you don&rsquo;t need to specify
 any additional options as <acronym>GNU</acronym> <code>tar</code> recognizes 
its format
 automatically.  Thus, the following commands will list and extract the
 archive created in previous example:
@@ -10994,7 +10994,7 @@
 </pre></td></tr></table>
 
 <a name="IDX392"></a>
-<p>About corrupted compressed archives: <code>gzip</code>'ed files have no
+<p>About corrupted compressed archives: <code>gzip</code>&rsquo;ed files have 
no
 redundancy, for maximum compression.  The adaptive nature of the
 compression scheme means that the compression tables are implicitly
 spread all over the archive.  If you lose a few blocks, the dynamic
@@ -11006,7 +11006,7 @@
 contents without decompression, and for resynchronizing decompression at
 every volume or file, in case of corrupted archives.  Doing so, we might
 lose some compressibility.  But this would have make recovering easier.
-So, there are pros and cons.  We'll see!
+So, there are pros and cons.  We&rsquo;ll see!
 </p>
 <a name="IDX393"></a>
 </dd>
@@ -11049,7 +11049,7 @@
 <p>The &lsquo;<samp>--use-compress-program</samp>&rsquo; option, in 
particular, lets you
 implement your own filters, not necessarily dealing with
 compression/decomression.  For example, suppose you wish to implement
-PGP encryption on top of compression, using <code>gpg</code> (see <a 
href="gpg.html#Top">gpg: (gpg)Top</a> section `gpg &mdash;- encryption and 
signing tool' in <cite>GNU Privacy Guard Manual</cite>).  The following script 
does that:  
+PGP encryption on top of compression, using <code>gpg</code> (see <a 
href="gpg.html#Top">gpg: (gpg)Top</a> section &lsquo;gpg &mdash;- encryption 
and signing tool&rsquo; in <cite>GNU Privacy Guard Manual</cite>).  The 
following script does that:  
 </p>
 <table><tr><td>&nbsp;</td><td><pre class="smallexample">#! /bin/sh
 case $1 in
@@ -11094,7 +11094,7 @@
 <h3 class="subsection"> 8.1.2 Archiving Sparse Files </h3>
 
 <p>Files in the file system occasionally have <em>holes</em>.  A <em>hole</em>
-in a file is a section of the file's contents which was never written.
+in a file is a section of the file&rsquo;s contents which was never written.
 The contents of a hole reads as all zeros.  On many operating systems,
 actual disk storage is not allocated for holes, but they are counted
 in the length of the file.  If you archive such a file, <code>tar</code>
@@ -11108,7 +11108,7 @@
 extraction (using &lsquo;<samp>--sparse</samp>&rsquo; is not needed on 
extraction) any
 such files have holes created wherever the continuous stretches of zeros
 were found.  Thus, if you use &lsquo;<samp>--sparse</samp>&rsquo;, 
<code>tar</code> archives
-won't take more space than the original.
+won&rsquo;t take more space than the original.
 </p>
 <dl compact="compact">
 <dd><a name="IDX400"></a>
@@ -11210,7 +11210,7 @@
 </p>
 <p>&lsquo;<samp>--atime-preserve=replace</samp>&rsquo; works on most systems, 
but it also
 restores the data modification time and updates the status change
-time.  Hence it doesn't interact with incremental dumps nicely
+time.  Hence it doesn&rsquo;t interact with incremental dumps nicely
 (see section <a href="#SEC88">Using <code>tar</code> to Perform Incremental 
Dumps</a>), and it can set access or data modification times
 incorrectly if other programs access the file while <code>tar</code> is
 running.
@@ -11218,7 +11218,7 @@
 <p>&lsquo;<samp>--atime-preserve=system</samp>&rsquo; avoids changing the 
access time in
 the first place, if the operating system supports this.
 Unfortunately, this may or may not work on any given operating system
-or file system.  If <code>tar</code> knows for sure it won't work, it
+or file system.  If <code>tar</code> knows for sure it won&rsquo;t work, it
 complains right away.
 </p>
 <p>Currently &lsquo;<samp>--atime-preserve</samp>&rsquo; with no operand 
defaults to
@@ -11252,7 +11252,7 @@
 files are easily and silently lost when files are given away.
 </p>
 <p>When writing an archive, <code>tar</code> writes the user id and user name
-separately.  If it can't find a user name (because the user id is not
+separately.  If it can&rsquo;t find a user name (because the user id is not
 in &lsquo;<tt>/etc/passwd</tt>&rsquo;), then it does not write one.  When 
restoring,
 it tries to look the name (if one was written) up in
 &lsquo;<tt>/etc/passwd</tt>&rsquo;.  If it fails, then it uses the user id 
stored in
@@ -11370,7 +11370,7 @@
 <p>One golden rule is simplicity.  For example, limit your <code>tar</code>
 archives to contain only regular files and directories, avoiding
 other kind of special files.  Do not attempt to save sparse files or
-contiguous files as such.  Let's discuss a few more problems, in turn.
+contiguous files as such.  Let&rsquo;s discuss a few more problems, in turn.
 </p>
 
 
@@ -11424,7 +11424,7 @@
 MSDOS, you should not rely on case distinction for file names, and you
 might use the <acronym>GNU</acronym> <code>doschk</code> program for helping 
you
 further diagnosing illegal MSDOS names, which are even more limited
-than System V's.
+than System V&rsquo;s.
 </p>
 <hr size="6">
 <a name="dereference"></a>
@@ -11513,7 +11513,7 @@
 able to read old format archives, so it might be safer for you to
 always use &lsquo;<samp>--format=v7</samp>&rsquo; for your distributions.  
Notice,
 however, that &lsquo;<samp>ustar</samp>&rsquo; format is a better alternative, 
as it is
-free from many of &lsquo;<samp>v7</samp>&rsquo;'s drawbacks.
+free from many of &lsquo;<samp>v7</samp>&rsquo;&rsquo;s drawbacks.
 </p>
 <hr size="6">
 <a name="ustar"></a>
@@ -11791,7 +11791,7 @@
 reading, <acronym>GNU</acronym> <code>tar</code> computes both checksums and
 accept any.  It is somewhat worrying that a lot of people may go
 around doing backup of their files using faulty (or at least
-non-standard) software, not learning about it until it's time to
+non-standard) software, not learning about it until it&rsquo;s time to
 restore their missing files with an incompatible file extractor, or
 vice versa.
 </p>
@@ -11800,18 +11800,18 @@
 wrong checksums.  <acronym>GNU</acronym> <code>tar</code> produces the standard
 checksum, however, raising incompatibilities with Sun.  That is to
 say, <acronym>GNU</acronym> <code>tar</code> has not been modified to
-<em>produce</em> incorrect archives to be read by buggy <code>tar</code>'s.
-I've been told that more recent Sun <code>tar</code> now read standard
+<em>produce</em> incorrect archives to be read by buggy 
<code>tar</code>&rsquo;s.
+I&rsquo;ve been told that more recent Sun <code>tar</code> now read standard
 archives, so maybe Sun did a similar patch, after all?
 </p>
 <p>The story seems to be that when Sun first imported <code>tar</code>
 sources on their system, they recompiled it without realizing that
 the checksums were computed differently, because of a change in
-the default signing of <code>char</code>'s in their compiler.  So they
+the default signing of <code>char</code>&rsquo;s in their compiler.  So they
 started computing checksums wrongly.  When they later realized their
 mistake, they merely decided to stay compatible with it, and with
 themselves afterwards.  Presumably, but I do not really know, HP-UX
-has chosen that their <code>tar</code> archives to be compatible with Sun's.
+has chosen that their <code>tar</code> archives to be compatible with 
Sun&rsquo;s.
 The current standards do not favor Sun <code>tar</code> format.  In any
 case, it now falls on the shoulders of SunOS and HP-UX users to get
 a <code>tar</code> able to read the good archives they receive.
@@ -11853,11 +11853,11 @@
 12:56:31 <small>UTC</small>, you will have to chose between 
<acronym>GNU</acronym> and
 <acronym>POSIX</acronym> archive formats.  When considering which format to
 choose, bear in mind that the <acronym>GNU</acronym> format uses
-two's-complement base-256 notation to store values that do not fit
+two&rsquo;s-complement base-256 notation to store values that do not fit
 into standard <acronym>ustar</acronym> range.  Such archives can generally be
 read only by a <acronym>GNU</acronym> <code>tar</code> implementation.  
Moreover, they sometimes
 cannot be correctly restored on another hosts even by <acronym>GNU</acronym> 
<code>tar</code>. For
-example, using two's complement representation for negative time
+example, using two&rsquo;s complement representation for negative time
 stamps that assumes a signed 32-bit <code>time_t</code> generates archives
 that are not portable to hosts with differing <code>time_t</code>
 representations.
@@ -12061,7 +12061,7 @@
 <a 
href="http://www.gnu.org/software/tar/utils/xsparse.html";><acronym>GNU</acronym>
 <code>tar</code> home page</a>.
 </p>
 <a name="IDX414"></a>
-<p>Let's begin with archive members in <em>sparse format
+<p>Let&rsquo;s begin with archive members in <em>sparse format
 version 1.0</em><a name="DOCF18" href="#FOOT18">(18)</a>, which are the 
easiest to expand.
 The condensed file will contain both file map and file data, so no
 additional data will be needed to restore it.  If the original file
@@ -12174,7 +12174,7 @@
 <li> 
 Consult the documentation for your <code>tar</code> implementation for an
 option that will print <em>block numbers</em> along with the archive
-listing (analogous to <acronym>GNU</acronym> <code>tar</code>'s 
&lsquo;<samp>-R</samp>&rsquo; option).  For example,
+listing (analogous to <acronym>GNU</acronym> <code>tar</code>&rsquo;s 
&lsquo;<samp>-R</samp>&rsquo; option).  For example,
 <code>star</code> has &lsquo;<samp>-block-number</samp>&rsquo;.
 
 </li><li>
@@ -12272,7 +12272,7 @@
 may crash unexplainedly trying to read them.
 </p>
 <p><code>tar</code> handles symbolic links in the form in which it comes in 
BSD;
-<code>cpio</code> doesn't handle symbolic links in the form in which it comes
+<code>cpio</code> doesn&rsquo;t handle symbolic links in the form in which it 
comes
 in System V prior to SVR4, and some vendors may have added symlinks
 to their system without enhancing <code>cpio</code> to know about them.
 Others may have enhanced it in a way other than the way I did it
@@ -12285,21 +12285,21 @@
 probably handles symbolic links.  They may not have bothered doing
 anything to enhance <code>tar</code> as a result.)
 </p>
-<p><code>cpio</code> handles special files; traditional <code>tar</code> 
doesn't.
+<p><code>cpio</code> handles special files; traditional <code>tar</code> 
doesn&rsquo;t.
 </p>
 <p><code>tar</code> comes with V7, System III, System V, and BSD source;
 <code>cpio</code> comes only with System III, System V, and later BSD
 (4.3-tahoe and later).
 </p>
-<p><code>tar</code>'s way of handling multiple hard links to a file can handle
+<p><code>tar</code>&rsquo;s way of handling multiple hard links to a file can 
handle
 file systems that support 32-bit inumbers (e.g., the BSD file system);
 <code>cpio</code>s way requires you to play some games (in its 
&quot;binary&quot;
 format, i-numbers are only 16 bits, and in its &quot;portable ASCII&quot; 
format,
-they're 18 bits&mdash;it would have to play games with the &quot;file system 
ID&quot;
+they&rsquo;re 18 bits&mdash;it would have to play games with the &quot;file 
system ID&quot;
 field of the header to make sure that the file system ID/i-number pairs
-of different files were always different), and I don't know which
-<code>cpio</code>s, if any, play those games.  Those that don't might get
-confused and think two files are the same file when they're not, and
+of different files were always different), and I don&rsquo;t know which
+<code>cpio</code>s, if any, play those games.  Those that don&rsquo;t might get
+confused and think two files are the same file when they&rsquo;re not, and
 make hard links between them.
 </p>
 <p><code>tar</code>s way of handling multiple hard links to a file places only
@@ -12319,8 +12319,8 @@
 at the unix scene,
 </p></blockquote>
 
-<p>It wasn't.  <code>cpio</code> first showed up in PWB/UNIX 1.0; no
-generally-available version of UNIX had <code>tar</code> at the time.  I don't
+<p>It wasn&rsquo;t.  <code>cpio</code> first showed up in PWB/UNIX 1.0; no
+generally-available version of UNIX had <code>tar</code> at the time.  I 
don&rsquo;t
 know whether any version that was generally available <em>within AT&amp;T</em>
 had <code>tar</code>, or, if so, whether the people within AT&amp;T who did
 <code>cpio</code> knew about it.
@@ -12341,9 +12341,9 @@
 
 <p>Theoretically it should be easier under <code>tar</code> since the blocking
 lets you find a header with some variation of &lsquo;<samp>dd 
skip=<var>nn</var></samp>&rsquo;.
-However, modern <code>cpio</code>'s and variations have an option to just
+However, modern <code>cpio</code>&rsquo;s and variations have an option to just
 search for the next file header after an error with a reasonable chance
-of resyncing.  However, lots of tape driver software won't allow you to
+of resyncing.  However, lots of tape driver software won&rsquo;t allow you to
 continue past a media error which should be the only reason for getting
 out of sync unless a file changed sizes while you were writing the
 archive.
@@ -12486,7 +12486,7 @@
 Naturally, the remote machine must have an executable
 <code>/usr/libexec/rmt</code>.  This program is free software from the
 University of California, and a copy of the source code can be found
-with the sources for <code>tar</code>; it's compiled and installed by default.
+with the sources for <code>tar</code>; it&rsquo;s compiled and installed by 
default.
 The exact path to this utility is determined when configuring the package.
 It is &lsquo;<tt><var>prefix</var>/libexec/rmt</tt>&rsquo;, where 
<var>prefix</var> stands for
 your installation prefix.  This location may also be overridden at
@@ -12819,7 +12819,7 @@
 blocking factor (with &lsquo;<samp>--blocking-factor</samp>&rsquo;) larger 
than the
 actual blocking factor, and then use the 
&lsquo;<samp>--read-full-records</samp>&rsquo;
 (&lsquo;<samp>-B</samp>&rsquo;) option.  (If you specify a blocking factor with
-&lsquo;<samp>--blocking-factor</samp>&rsquo; and don't use the
+&lsquo;<samp>--blocking-factor</samp>&rsquo; and don&rsquo;t use the
 &lsquo;<samp>--read-full-records</samp>&rsquo; option, then <code>tar</code> 
will not
 attempt to figure out the recording size itself.)  On some devices,
 you must always specify the record size exactly with
@@ -12831,7 +12831,7 @@
 <p><code>tar</code> blocks are all fixed size (512 bytes), and its scheme for
 putting them into records is to put a whole number of them (one or
 more) into each record.  <code>tar</code> records are all the same size;
-at the end of the file there's a block containing all zeros, which
+at the end of the file there&rsquo;s a block containing all zeros, which
 is how you tell that the remainder of the last record(s) are garbage.
 </p>
 <p>In a standard <code>tar</code> file (no options), the block size is 512
@@ -12976,7 +12976,7 @@
 can use &lsquo;<samp>--list</samp>&rsquo; (&lsquo;<samp>-t</samp>&rsquo;) 
without specifying a blocking factor&mdash;<code>tar</code>
 reports a non-default record size and then lists the archive members as
 it would normally.  To extract files from an archive with a non-standard
-blocking factor (particularly if you're not sure what the blocking factor
+blocking factor (particularly if you&rsquo;re not sure what the blocking factor
 is), you can usually use the &lsquo;<samp>--read-full-records</samp>&rsquo; 
(&lsquo;<samp>-B</samp>&rsquo;) option while
 specifying a blocking factor larger then the blocking factor of the archive
 (i.e.  &lsquo;<samp>tar --extract --read-full-records 
--blocking-factor=300</samp>&rsquo;.
@@ -13024,7 +13024,7 @@
 <p>Apparently, Exabyte drives have a physical block size of 8K bytes.
 If we choose our blocksize as a multiple of 8k bytes, then the problem
 seems to disappear.  Id est, we are using block size of 112 right
-now, and we haven't had the problem since we switched&hellip;
+now, and we haven&rsquo;t had the problem since we switched&hellip;
 </p>
 <p>With <acronym>GNU</acronym> <code>tar</code> the blocking factor is limited 
only
 by the maximum record size of the device containing the archive, or by
@@ -13058,7 +13058,7 @@
 uncompress a compressed archive on tape, there is an option to turn
 the message off, but it breaks the regularity of simply having to use
 &lsquo;<samp><var>prog</var> -d</samp>&rsquo; for decompression.  It would be 
nice if gzip was
-silently ignoring any number of trailing zeros.  I'll ask Jean-loup
+silently ignoring any number of trailing zeros.  I&rsquo;ll ask Jean-loup
 Gailly, by sending a copy of this message to him.
 
 </li><li>
@@ -13203,7 +13203,7 @@
 
 <p>Most tape devices have two entries in the &lsquo;<tt>/dev</tt>&rsquo; 
directory, or
 entries that come in pairs, which differ only in the minor number for
-this device.  Let's take for example &lsquo;<tt>/dev/tape</tt>&rsquo;, which 
often
+this device.  Let&rsquo;s take for example &lsquo;<tt>/dev/tape</tt>&rsquo;, 
which often
 points to the only or usual tape device of a given system.  There might
 be a corresponding &lsquo;<tt>/dev/nrtape</tt>&rsquo; or 
&lsquo;<tt>/dev/ntape</tt>&rsquo;.  The simpler
 name is the <em>rewinding</em> version of the device, while the name
@@ -13316,8 +13316,8 @@
 archive media.  Tape drives write one tape mark between files,
 two at the end of all the file entries.
 </p>
-<p>If you think of data as a series of records &quot;rrrr&quot;'s, and tape 
marks as
-&quot;*&quot;'s, a tape might look like the following:
+<p>If you think of data as a series of records &quot;rrrr&quot;&rsquo;s, and 
tape marks as
+&quot;*&quot;&rsquo;s, a tape might look like the following:
 </p>
 <table><tr><td>&nbsp;</td><td><pre 
class="smallexample">rrrr*rrrrrr*rrrrr*rr*rrrrr**-------------------------
 </pre></td></tr></table>
@@ -13427,7 +13427,7 @@
 
 
 
-<p>If you don't specify a <var>tapename</var>, <code>mt</code> uses the 
environment
+<p>If you don&rsquo;t specify a <var>tapename</var>, <code>mt</code> uses the 
environment
 variable <code>TAPE</code>; if <code>TAPE</code> is not set, <code>mt</code> 
will use
 the default device specified in your &lsquo;<tt>sys/mtio.h</tt>&rsquo; file
 (<code>DEFTAPE</code> variable).  If this is not defined, the program will
@@ -13643,7 +13643,7 @@
 </dl>
 
 <p>The <var>script-name</var> is executed without any command line
-arguments.  It inherits <code>tar</code>'s shell environment.
+arguments.  It inherits <code>tar</code>&rsquo;s shell environment.
 Additional data is passed to it via the following
 environment variables:
 </p>
@@ -13965,7 +13965,7 @@
 &lsquo;<tt>archive</tt>&rsquo; is not labelled at all.
 </p>
 <p>  Similarly, <code>tar</code> will refuse to list or extract the
-archive if its label doesn't match the <var>archive-label</var>
+archive if its label doesn&rsquo;t match the <var>archive-label</var>
 specified.  In those cases, <var>archive-label</var> argument is interpreted
 as a globbing-style pattern which must match the actual magnetic
 volume label.  See section <a href="#SEC102">Excluding Some Files</a>, for a 
precise description of how match
@@ -14086,7 +14086,7 @@
 <p>Also, since <code>tar</code> normally strips leading 
&lsquo;<samp>/</samp>&rsquo; from file
 names (see section <a href="#SEC112">Absolute File Names</a>), a command like 
&lsquo;<samp>tar --verify -cf
 /tmp/foo.tar /etc</samp>&rsquo; will work as desired only if the working 
directory is
-&lsquo;<tt>/</tt>&rsquo;, as <code>tar</code> uses the archive's relative 
member names
+&lsquo;<tt>/</tt>&rsquo;, as <code>tar</code> uses the archive&rsquo;s 
relative member names
 (e.g., &lsquo;<tt>etc/motd</tt>&rsquo;) when verifying the archive.
 </p>
 <hr size="6">
@@ -14207,7 +14207,7 @@
 
 
 <p>.
-See <a href="automake.html#Options">tar-v7: (automake)Options</a> section 
`Changing Automake's Behavior' in <cite>GNU Automake</cite>, for a description 
on how to use various
+See <a href="automake.html#Options">tar-v7: (automake)Options</a> section 
&lsquo;Changing Automake&rsquo;s Behavior&rsquo; in <cite>GNU Automake</cite>, 
for a description on how to use various
 archive formats with <code>automake</code>.
 </p>
 <p>Future versions of <acronym>GNU</acronym> <code>tar</code> will understand 
&lsquo;<samp>-o</samp>&rsquo; only as a
@@ -14379,7 +14379,7 @@
 <dt><u>Help Output:</u> offset <b>doc-opt-col</b>
 <a name="IDX459"></a>
 </dt>
-<dd><p>Column in which <em>doc options</em> start.  A doc option isn't actually
+<dd><p>Column in which <em>doc options</em> start.  A doc option isn&rsquo;t 
actually
 an option, but rather an arbitrary piece of documentation that is
 displayed in much the same manner as the options.  For example, in
 the description of &lsquo;<samp>--format</samp>&rsquo; option:
@@ -14847,7 +14847,7 @@
 
 <p>The <code>mtime</code> field is the data modification time of the file at
 the time it was archived.  It is the ASCII representation of the octal
-value of the last time the file's contents were modified, represented
+value of the last time the file&rsquo;s contents were modified, represented
 as an integer number of
 seconds since January 1, 1970, 00:00 Coordinated Universal Time.
 </p>
@@ -14864,7 +14864,7 @@
 action occurs, <code>tar</code> issues a warning to the standard error.
 </p>
 <p>The <code>atime</code> and <code>ctime</code> fields are used in making 
incremental
-backups; they store, respectively, the particular file's access and
+backups; they store, respectively, the particular file&rsquo;s access and
 status change times.
 </p>
 <p>The <code>offset</code> is used by the 
&lsquo;<samp>--multi-volume</samp>&rsquo; (&lsquo;<samp>-M</samp>&rsquo;) 
option, when
@@ -16069,7 +16069,7 @@
 copying, no modification, source files not available&mdash;which exclude
 them from the free software world.
 </p>
-<p>That wasn't the first time this sort of thing happened, and it was far
+<p>That wasn&rsquo;t the first time this sort of thing happened, and it was far
 from the last.  Many times we have heard a GNU user eagerly describe a
 manual that he is writing, his intended contribution to the community,
 only to learn that he had ruined everything by signing a publication
@@ -16098,12 +16098,12 @@
 </p>
 <p>Some kinds of limits on the way modification is handled are
 acceptable.  For example, requirements to preserve the original
-author's copyright notice, the distribution terms, or the list of
+author&rsquo;s copyright notice, the distribution terms, or the list of
 authors, are ok.  It is also no problem to require modified versions
 to include notice that they were modified.  Even entire sections that
 may not be deleted or changed are acceptable, as long as they deal
 with nontechnical topics (like this one).  These kinds of restrictions
-are acceptable because they don't obstruct the community's normal use
+are acceptable because they don&rsquo;t obstruct the community&rsquo;s normal 
use
 of the manual.
 </p>
 <p>However, it must be possible to modify all the <em>technical</em>
@@ -16122,11 +16122,11 @@
 <p>If you are writing documentation, please insist on publishing it under
 the GNU Free Documentation License or another free documentation
 license.  Remember that this decision requires your approval&mdash;you
-don't have to let the publisher decide.  Some commercial publishers
+don&rsquo;t have to let the publisher decide.  Some commercial publishers
 will use a free license if you insist, but they will not propose the
 option; it is up to you to raise the issue and say firmly that this is
 what you want.  If the publisher you are dealing with refuses, please
-try other publishers.  If you're not sure whether a proposed license
+try other publishers.  If you&rsquo;re not sure whether a proposed license
 is free, write to <a href="mailto:address@hidden";>address@hidden</a>.
 </p>
 <p>You can encourage commercial publishers to sell more free, copylefted
@@ -16243,7 +16243,7 @@
 </p>
 <p>A &ldquo;Secondary Section&rdquo; is a named appendix or a front-matter 
section
 of the Document that deals exclusively with the relationship of the
-publishers or authors of the Document to the Document's overall
+publishers or authors of the Document to the Document&rsquo;s overall
 subject (or to related matters) and contains nothing that could fall
 directly within that overall subject.  (Thus, if the Document is in
 part a textbook of mathematics, a Secondary Section may not explain
@@ -16295,7 +16295,7 @@
 plus such following pages as are needed to hold, legibly, the material
 this License requires to appear in the title page.  For works in
 formats which do not have any title page as such, &ldquo;Title Page&rdquo; 
means
-the text near the most prominent appearance of the work's title,
+the text near the most prominent appearance of the work&rsquo;s title,
 preceding the beginning of the body of the text.
 </p>
 <p>A section &ldquo;Entitled XYZ&rdquo; means a named subunit of the Document 
whose
@@ -16334,7 +16334,7 @@
 
 <p>If you publish printed copies (or copies in media that commonly have
 printed covers) of the Document, numbering more than 100, and the
-Document's license notice requires Cover Texts, you must enclose the
+Document&rsquo;s license notice requires Cover Texts, you must enclose the
 copies in covers that carry, clearly and legibly, all these Cover
 Texts: Front-Cover Texts on the front cover, and Back-Cover Texts on
 the back cover.  Both covers must also clearly and legibly identify
@@ -16410,7 +16410,7 @@
 
 </li><li>
 Preserve in that license notice the full lists of Invariant Sections
-and required Cover Texts given in the Document's license notice.
+and required Cover Texts given in the Document&rsquo;s license notice.
 
 </li><li>
 Include an unaltered copy of this License.
@@ -16460,7 +16460,7 @@
 appendices that qualify as Secondary Sections and contain no material
 copied from the Document, you may at your option designate some or all
 of these sections as invariant.  To do this, add their titles to the
-list of Invariant Sections in the Modified Version's license notice.
+list of Invariant Sections in the Modified Version&rsquo;s license notice.
 These titles must be distinct from any other section titles.
 </p>
 <p>You may add a section Entitled &ldquo;Endorsements&rdquo;, provided it 
contains
@@ -16529,14 +16529,14 @@
 and independent documents or works, in or on a volume of a storage or
 distribution medium, is called an &ldquo;aggregate&rdquo; if the copyright
 resulting from the compilation is not used to limit the legal rights
-of the compilation's users beyond what the individual works permit.
+of the compilation&rsquo;s users beyond what the individual works permit.
 When the Document is included in an aggregate, this License does not
 apply to the other works in the aggregate which are not themselves
 derivative works of the Document.
 </p>
 <p>If the Cover Text requirement of section 3 is applicable to these
 copies of the Document, then if the Document is less than one half of
-the entire aggregate, the Document's Cover Texts may be placed on
+the entire aggregate, the Document&rsquo;s Cover Texts may be placed on
 covers that bracket the Document within the aggregate, or the
 electronic equivalent of covers if the Document is in electronic form.
 Otherwise they must appear on printed covers that bracket the whole
@@ -17666,7 +17666,7 @@
 </p><h3><a name="FOOT17" href="#DOCF17">(17)</a></h3>
 <p>A side effect of this is that when
 &lsquo;<samp>--create</samp>&rsquo; is used with 
&lsquo;<samp>--verbose</samp>&rsquo; the resulting output
-is not, generally speaking, the same as the one you'd get running
+is not, generally speaking, the same as the one you&rsquo;d get running
 <kbd>tar --list</kbd> command.  This may be important if you use some
 scripts for comparing both outputs.  See <a 
href="#listing-member-and-file-names">listing member and file names</a>,
 for the information on how to handle this case.
@@ -17678,7 +17678,7 @@
 archive (see section <a href="#SEC136">Controlling Extended Header 
Keywords</a>).
 </p><h3><a name="FOOT20" href="#DOCF20">(20)</a></h3>
 <p>If you run <acronym>GNU</acronym> <code>tar</code> under a different 
locale, the
-translation to the locale's language will be used.
+translation to the locale&rsquo;s language will be used.
 </p><h3><a name="FOOT21" href="#DOCF21">(21)</a></h3>
 <p>See <a href="#g_t_002d_002drestrict">&ndash;restrict</a>, for more 
information about
 this option

Index: Tests/texi2html_res/texi2html.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/texi2html_res/texi2html.html,v
retrieving revision 1.30
retrieving revision 1.31
diff -u -b -r1.30 -r1.31
--- Tests/texi2html_res/texi2html.html  6 May 2007 12:57:07 -0000       1.30
+++ Tests/texi2html_res/texi2html.html  3 Oct 2007 09:34:49 -0000       1.31
@@ -100,7 +100,7 @@
 there is so much documentation in Texinfo all over
 the world.
 </p>
-<p>A few time ago <code>makeinfo</code> wasn't able to produce
+<p>A few time ago <code>makeinfo</code> wasn&rsquo;t able to produce
 <acronym>HTML</acronym> output format, but there are needth to have
 <acronym>HTML</acronym>. This was the borning hour for
 <code>texi2html</code>. The basic purpose of &lsquo;<tt>texi2html</tt>&rsquo;
@@ -159,7 +159,7 @@
 <td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? 
</a>]</td>
 </tr></table>
 <h2 class="section"> 1.2 Why &lsquo;<tt>texi2html</tt>&rsquo; and not 
&lsquo;<tt>makeinfo</tt>&rsquo;? </h2>
-<p>The basic idea of <code>makeinfo</code>'s <acronym>HTML</acronym>
+<p>The basic idea of <code>makeinfo</code>&rsquo;s <acronym>HTML</acronym>
 output was to get an readable <acronym>HTML</acronym> output.
 Nothing sophisticated nor good styling just readable.
 </p>
@@ -172,14 +172,14 @@
 possible changings of the initialization file to fit your
 own needs.
 </p>
-<p>The main disadvantage of <acronym>makeinfo</acronym>'s
+<p>The main disadvantage of <acronym>makeinfo</acronym>&rsquo;s
 <acronym>HTML</acronym> output is your getting only one big file.
 This is of course readable but not very usable. The problem
 of this is, while you like to have splitted chapters or
 nodes the Texinfo source has to be read at minimum twice
 times. This makes it impossible to implement this in
 <code>makeinfo</code>. This would result in complete new
-implementation of <code>makeinfo</code>'s source.
+implementation of <code>makeinfo</code>&rsquo;s source.
 </p>
 <p>In contrast to the HTML produced by <code>makeinfo
 --html</code> (the <code>makeinfo</code> program is part of the
@@ -602,8 +602,8 @@
 </tr></table>
 <h1 class="chapter"> 6. Customizing HTML </h1>
 <p>If you like to read the following section, it is assumed
-you are famillar with <acronym>HTML</acronym>. If not, you shouldn't
-read this, cause you don't know what we are talking about.
+you are famillar with <acronym>HTML</acronym>. If not, you shouldn&rsquo;t
+read this, cause you don&rsquo;t know what we are talking about.
 </p>
 <p>Here you can find information how to change the
 <acronym>HTML</acronym> parts of a document. These are the
@@ -1078,7 +1078,7 @@
 <p>used as indentation for block enclosing command
 <code>@example</code>, etc If not empty, must be enclosed in
 <code>&lt;td&gt;&lt;/td&gt;</code>
-<var>$T2H_EXAMPLE_INDENT_CELL</var> = '&lt;td&gt;&amp;nbsp;&lt;/td&gt;';
+<var>$T2H_EXAMPLE_INDENT_CELL</var> = 
&rsquo;&lt;td&gt;&amp;nbsp;&lt;/td&gt;&rsquo;;
 </p>
 <hr size="6">
 <a name="IFOSampleIndentCell"></a>
@@ -1222,7 +1222,7 @@
 <td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? 
</a>]</td>
 </tr></table>
 <h3 class="subsection"> 7.5.10 HREF Dir Instead File. </h3>
-<p>if set (e.g., to &lsquo;<tt>index.html</tt>&rsquo;) replace 
<strong>HREF</strong>'s
+<p>if set (e.g., to &lsquo;<tt>index.html</tt>&rsquo;) replace 
<strong>HREF</strong>&rsquo;s
 to this file  (i.e., to &lsquo;<tt>index.html</tt>&rsquo;) by 
&lsquo;<tt>./</tt>&rsquo;
 </p>
 <p>$T2H_HREF_DIR_INSTEAD_FILE = &quot;&quot;;
@@ -1668,7 +1668,7 @@
 About.  Otherwise, create a monolithic <acronym>HTML</acronym> file that
 contains the whole document.
 </p>
-<p>#$T2H_SPLIT = 'section';
+<p>#$T2H_SPLIT = &rsquo;section&rsquo;;
 $T2H_SPLIT = undef;
 </p>
 <hr size="6">
@@ -1905,7 +1905,7 @@
 and use ISO 639 language codes (see e.g. perl module
 &lsquo;<tt>Locale-Codes-1.02.tar.gz</tt>&rsquo; for definitions).
 </p>
-<p>If you don't give a &lsquo;<samp>-lang</samp>&rsquo; then we got it from the
+<p>If you don&rsquo;t give a &lsquo;<samp>-lang</samp>&rsquo; then we got it 
from the
 Texinfo source file (@documentlanguage
 see <a href="Texinfo.html#documentlanguage">(Texinfo)documentlanguage</a>). If 
there is no
 <code>@documentlanguage</code> we use the default <code>en</code> for

Index: Tests/texinfo_res/Copying-This-Manual.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/texinfo_res/Copying-This-Manual.html,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -b -r1.9 -r1.10
--- Tests/texinfo_res/Copying-This-Manual.html  5 Feb 2007 15:30:26 -0000       
1.9
+++ Tests/texinfo_res/Copying-This-Manual.html  3 Oct 2007 09:34:49 -0000       
1.10
@@ -157,7 +157,7 @@
 </p>
 <p>A &ldquo;Secondary Section&rdquo; is a named appendix or a front-matter 
section of
 the Document that deals exclusively with the relationship of the
-publishers or authors of the Document to the Document's overall subject
+publishers or authors of the Document to the Document&rsquo;s overall subject
 (or to related matters) and contains nothing that could fall directly
 within that overall subject.  (For example, if the Document is in part a
 textbook of mathematics, a Secondary Section may not explain any
@@ -201,7 +201,7 @@
 plus such following pages as are needed to hold, legibly, the material
 this License requires to appear in the title page.  For works in
 formats which do not have any title page as such, &ldquo;Title Page&rdquo; 
means
-the text near the most prominent appearance of the work's title,
+the text near the most prominent appearance of the work&rsquo;s title,
 preceding the beginning of the body of the text.
 </p>
 </li><li>
@@ -224,7 +224,7 @@
 COPYING IN QUANTITY
 
 <p>If you publish printed copies of the Document numbering more than 100,
-and the Document's license notice requires Cover Texts, you must enclose
+and the Document&rsquo;s license notice requires Cover Texts, you must enclose
 the copies in covers that carry, clearly and legibly, all these Cover
 Texts: Front-Cover Texts on the front cover, and Back-Cover Texts on
 the back cover.  Both covers must also clearly and legibly identify
@@ -300,7 +300,7 @@
 
 </li><li>
 Preserve in that license notice the full lists of Invariant Sections
-and required Cover Texts given in the Document's license notice.
+and required Cover Texts given in the Document&rsquo;s license notice.
 
 </li><li>
 Include an unaltered copy of this License.
@@ -325,7 +325,7 @@
 
 </li><li>
 In any section entitled &ldquo;Acknowledgments&rdquo; or 
&ldquo;Dedications&rdquo;,
-preserve the section's title, and preserve in the section all the
+preserve the section&rsquo;s title, and preserve in the section all the
 substance and tone of each of the contributor acknowledgments
 and/or dedications given therein.
 
@@ -347,7 +347,7 @@
 appendices that qualify as Secondary Sections and contain no material
 copied from the Document, you may at your option designate some or all
 of these sections as invariant.  To do this, add their titles to the
-list of Invariant Sections in the Modified Version's license notice.
+list of Invariant Sections in the Modified Version&rsquo;s license notice.
 These titles must be distinct from any other section titles.
 </p>
 <p>You may add a section entitled &ldquo;Endorsements&rdquo;, provided it 
contains
@@ -423,7 +423,7 @@
 </p>
 <p>If the Cover Text requirement of section 3 is applicable to these
 copies of the Document, then if the Document is less than one quarter
-of the entire aggregate, the Document's Cover Texts may be placed on
+of the entire aggregate, the Document&rsquo;s Cover Texts may be placed on
 covers that surround only the Document within the aggregate.
 Otherwise they must appear on covers around the whole aggregate.
 </p>

Index: Tests/texinfo_res/Cursor-Commands.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/texinfo_res/Cursor-Commands.html,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -b -r1.9 -r1.10
--- Tests/texinfo_res/Cursor-Commands.html      5 Feb 2007 15:30:26 -0000       
1.9
+++ Tests/texinfo_res/Cursor-Commands.html      3 Oct 2007 09:34:49 -0000       
1.10
@@ -87,7 +87,7 @@
 Emacs and standalone versions) have several commands which allow you to
 move the cursor about the screen.  The notation used in this manual to
 describe keystrokes is identical to the notation used within the Emacs
-manual, and the GNU Readline manual.  See <a 
href="../emacs/Characters.html#Characters">(emacs)Characters</a> section 
`Character Conventions' in <cite>the GNU Emacs Manual</cite>, if you are 
unfamiliar with the
+manual, and the GNU Readline manual.  See <a 
href="../emacs/Characters.html#Characters">(emacs)Characters</a> section 
&lsquo;Character Conventions&rsquo; in <cite>the GNU Emacs Manual</cite>, if 
you are unfamiliar with the
 notation<a name="DOCF4" href="info-stnd_fot.html#FOOT4">(4)</a>.
 </p>
 <p>The following table lists the basic cursor movement commands in Info.

Index: Tests/texinfo_res/Custom-Key-Bindings.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/texinfo_res/Custom-Key-Bindings.html,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -b -r1.9 -r1.10
--- Tests/texinfo_res/Custom-Key-Bindings.html  5 Feb 2007 15:30:26 -0000       
1.9
+++ Tests/texinfo_res/Custom-Key-Bindings.html  3 Oct 2007 09:34:49 -0000       
1.10
@@ -87,7 +87,7 @@
 Info provides a way to define different key-to-command bindings and
 variable settings from the defaults described in this document.
 </p>
-<p>On startup, GNU Info looks for a configuration file in the invoker's
+<p>On startup, GNU Info looks for a configuration file in the invoker&rsquo;s
 HOME directory called &lsquo;<tt>.info</tt>&rsquo;<a name="DOCF7" 
href="info-stnd_fot.html#FOOT7">(7)</a>.  If it is present, and
 appears to contain Info configuration data, and was created with the
 current version of the <code>infokey</code> command, then Info adopts the
@@ -296,7 +296,7 @@
 the special section header lines.
 </p>
 <p>Key bindings defined in the &lsquo;<tt>.info</tt>&rsquo; file take 
precedence over GNU
-Info's default key bindings, whether or not 
&lsquo;<samp>--vi-keys</samp>&rsquo; is used.  A
+Info&rsquo;s default key bindings, whether or not 
&lsquo;<samp>--vi-keys</samp>&rsquo; is used.  A
 default key binding may be disabled by overriding it in the 
&lsquo;<tt>.info</tt>&rsquo;
 file with the action <code>invalid</code>.  In addition, <em>all</em> default
 key bindings can be disabled by adding this line <em>anywhere</em> in the

Index: Tests/texinfo_res/Invoking-Info.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/texinfo_res/Invoking-Info.html,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -b -r1.9 -r1.10
--- Tests/texinfo_res/Invoking-Info.html        5 Feb 2007 15:30:26 -0000       
1.9
+++ Tests/texinfo_res/Invoking-Info.html        3 Oct 2007 09:34:49 -0000       
1.10
@@ -161,7 +161,7 @@
 <p>In every directory Info tries, if <var>filename</var> is not found, Info
 looks for it with a number of known extensions of Info files<a name="DOCF1" 
href="info-stnd_fot.html#FOOT1">(1)</a>.  For every
 known extension, Info looks for a compressed file, if a regular file
-isn't found.  Info supports files compressed with <code>gzip</code>,
+isn&rsquo;t found.  Info supports files compressed with <code>gzip</code>,
 <code>bzip2</code>, <code>compress</code> and <code>yabba</code> programs; it 
calls
 <code>gunzip</code>, <code>bunzip2</code>, <code>uncompress</code> and 
<code>unyabba</code>,
 accordingly, to decompress such files.  Compressed Info files are
@@ -185,7 +185,7 @@
 rest of the matching entries.  If no such entry exists, print &lsquo;<samp>no
 entries found</samp>&rsquo; and exit with nonzero status.  This can be used 
from
 another program as a way to provide online help, or as a quick way of
-starting to read an Info file at a certain node when you don't know the
+starting to read an Info file at a certain node when you don&rsquo;t know the
 exact name of that node.
 </p>
 <p>This command can also be invoked from inside Info; see <a 
href="Searching-Commands.html#SEC6">Searching an Info File</a>.
@@ -280,7 +280,7 @@
 bindings of <code>vi</code> and Less.  The default key bindings are generally
 modeled after Emacs.
 (See section <a href="Custom-Key-Bindings.html#SEC17">Customizing Key Bindings 
and Variables</a>,
-for a more general way of altering GNU Info's key bindings.)
+for a more general way of altering GNU Info&rsquo;s key bindings.)
 </p>
 </dd>
 <dt> <code><var>menu-item</var></code></dt>
@@ -288,7 +288,7 @@
 <p><a name="command_002dline-menu-items"></a>
 Info treats its remaining arguments as the names of menu items.  The
 first argument is a menu item in the initial node visited (generally
-<code>dir</code>), the second argument is a menu item in the first argument's
+<code>dir</code>), the second argument is a menu item in the first 
argument&rsquo;s
 node, etc.  You can easily move to the node of your choice by specifying
 the menu names which describe the path to that node.  For example,
 </p>
@@ -309,7 +309,7 @@
 the command-line menu items.  Therefore, the Info file searched for the
 index or the invocation node is the file where Info finds itself after
 following all the menu items given on the command line.  This is so
-&lsquo;<samp>info emacs --show-options</samp>&rsquo; does what you'd expect.
+&lsquo;<samp>info emacs --show-options</samp>&rsquo; does what you&rsquo;d 
expect.
 </p>
 
 

Index: Tests/texinfo_res/Miscellaneous-Commands.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/texinfo_res/Miscellaneous-Commands.html,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -b -r1.9 -r1.10
--- Tests/texinfo_res/Miscellaneous-Commands.html       5 Feb 2007 15:30:26 
-0000       1.9
+++ Tests/texinfo_res/Miscellaneous-Commands.html       3 Oct 2007 09:34:49 
-0000       1.10
@@ -186,7 +186,7 @@
 Meta-digit keys after <kbd>-</kbd>, the result is a negative number produced
 by those digits.
 </p>
-<p><kbd>-</kbd> doesn't work when you type in the echo area, because you need 
to
+<p><kbd>-</kbd> doesn&rsquo;t work when you type in the echo area, because you 
need to
 be able to insert the &lsquo;<samp>-</samp>&rsquo; character itself; use 
<kbd>M--</kbd> instead,
 if you need to specify negative arguments in the echo area.
 </p></dd>

Index: Tests/texinfo_res/Node-Commands.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/texinfo_res/Node-Commands.html,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -b -r1.9 -r1.10
--- Tests/texinfo_res/Node-Commands.html        5 Feb 2007 15:30:26 -0000       
1.9
+++ Tests/texinfo_res/Node-Commands.html        3 Oct 2007 09:34:49 -0000       
1.10
@@ -102,7 +102,7 @@
 <a name="IDX112"></a>
 <a name="IDX113"></a>
 <a name="IDX114"></a>
-<p>Select the `Next' node.
+<p>Select the &lsquo;Next&rsquo; node.
 </p>
 <a name="IDX115"></a>
 <p>The &lt;NEXT&gt; key is known as the &lt;PgDn&gt; key on some
@@ -114,7 +114,7 @@
 <dd><a name="IDX116"></a>
 <a name="IDX117"></a>
 <a name="IDX118"></a>
-<p>Select the `Prev' node.
+<p>Select the &lsquo;Prev&rsquo; node.
 </p>
 <a name="IDX119"></a>
 <p>The &lt;PREVIOUS&gt; key is known as the &lt;PgUp&gt; key on some
@@ -128,7 +128,7 @@
 <a name="IDX121"></a>
 <a name="IDX122"></a>
 <a name="IDX123"></a>
-<p>Select the `Up' node.
+<p>Select the &lsquo;Up&rsquo; node.
 </p></dd>
 </dl>
 
@@ -146,7 +146,7 @@
 <dl compact="compact">
 <dt> &lt;l&gt; (<code>history-node</code>)</dt>
 <dt> &lt;C-&lt;CENTER&gt;&gt; (on DOS/Windows only)</dt>
-<dt> &lt;'&gt;, vi-like operation</dt>
+<dt> &lt;&rsquo;&gt;, vi-like operation</dt>
 <dd><a name="IDX124"></a>
 <a name="IDX125"></a>
 <a name="IDX126"></a>
@@ -268,9 +268,9 @@
 in another Info file, you need to visit that file before invoking
 &lsquo;<samp>I</samp>&rsquo;.  For example, if you are reading the Emacs 
manual and want to
 see the command-line options of the <code>makeinfo</code> program, type <kbd>g
-(texinfo) &lt;RET&gt;</kbd> and then <kbd>I makeinfo &lt;RET&gt;</kbd>.  If 
you don't
+(texinfo) &lt;RET&gt;</kbd> and then <kbd>I makeinfo &lt;RET&gt;</kbd>.  If 
you don&rsquo;t
 know what Info file documents the command, or if invoking 
&lsquo;<samp>I</samp>&rsquo;
-doesn't display the right node, go to the &lsquo;<samp>(dir)</samp>&rsquo; 
node (using the
+doesn&rsquo;t display the right node, go to the 
&lsquo;<samp>(dir)</samp>&rsquo; node (using the
 &lsquo;<samp>d</samp>&rsquo; command) and invoke &lsquo;<samp>I</samp>&rsquo; 
from there.
 </p>
 </dd>
@@ -288,13 +288,13 @@
 In other words, you can specify a complete path which descends through
 the menu hierarchy of a particular Info file starting at the
 &lsquo;<samp>(dir)</samp>&rsquo; node.  This has the same effect as if you 
typed the menu
-item sequence on Info's command line, see <a 
href="Invoking-Info.html#command_002dline-menu-items">Info command-line 
arguments processing</a>.  For example,
+item sequence on Info&rsquo;s command line, see <a 
href="Invoking-Info.html#command_002dline-menu-items">Info command-line 
arguments processing</a>.  For example,
 </p>
 <table><tr><td>&nbsp;</td><td><pre class="example"> <kbd>G 
Texinfo,Overview,Reporting Bugs &lt;RET&gt;</kbd>
 </pre></td></tr></table>
 
 <p>displays the node &lsquo;<samp>Reporting Bugs</samp>&rsquo; in the Texinfo 
manual.  (You
-don't actually need to type the menu items in their full length, or in
+don&rsquo;t actually need to type the menu items in their full length, or in
 their exact letter-case.  However, if you do type the menu items
 exactly, Info will find it faster.)
 </p>

Index: Tests/texinfo_res/Printing-Nodes.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/texinfo_res/Printing-Nodes.html,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -b -r1.9 -r1.10
--- Tests/texinfo_res/Printing-Nodes.html       5 Feb 2007 15:30:26 -0000       
1.9
+++ Tests/texinfo_res/Printing-Nodes.html       3 Oct 2007 09:34:49 -0000       
1.10
@@ -84,7 +84,7 @@
 <p>In general, we recommend that you use TeX to format the document and
 print sections of it, by running <code>tex</code> on the Texinfo source file.
 However, you may wish to print out the contents of a node as a quick
-reference document for later use, or if you don't have TeX installed.
+reference document for later use, or if you don&rsquo;t have TeX installed.
 Info provides you with a command for doing this.
 </p>
 <dl compact="compact">

Index: Tests/texinfo_res/Searching-Commands.html
===================================================================
RCS file: 
/cvsroot/texi2html/texi2html/Tests/texinfo_res/Searching-Commands.html,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -b -r1.9 -r1.10
--- Tests/texinfo_res/Searching-Commands.html   5 Feb 2007 15:30:26 -0000       
1.9
+++ Tests/texinfo_res/Searching-Commands.html   3 Oct 2007 09:34:49 -0000       
1.10
@@ -216,7 +216,7 @@
 has all of its important concepts indexed, so the &lsquo;<samp>i</samp>&rsquo; 
command
 lets you use a manual as a reference.
 </p>
-<p>If you don't know what manual documents something, try the <kbd>M-x
+<p>If you don&rsquo;t know what manual documents something, try the <kbd>M-x
 index-apropos</kbd>.  It prompts for a string and then looks up that string
 in all the indices of all the Info documents installed on your system.
 It can also be invoked from the command line; see <a 
href="Invoking-Info.html#g_t_002d_002dapropos">&ndash;apropos</a>.

Index: Tests/texinfo_res/Variables.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/texinfo_res/Variables.html,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -b -r1.9 -r1.10
--- Tests/texinfo_res/Variables.html    5 Feb 2007 15:30:26 -0000       1.9
+++ Tests/texinfo_res/Variables.html    3 Oct 2007 09:34:49 -0000       1.10
@@ -179,7 +179,7 @@
 </p>
 <dl compact="compact">
 <dt> <code>Continuous</code></dt>
-<dd><p>Try to get the first item in this node's menu, or failing that, the
+<dd><p>Try to get the first item in this node&rsquo;s menu, or failing that, 
the
 &lsquo;<samp>Next</samp>&rsquo; node, or failing that, the 
&lsquo;<samp>Next</samp>&rsquo; of the &lsquo;<samp>Up</samp>&rsquo;.
 This behavior is identical to using the &lsquo;<samp>]</samp>&rsquo;
 (<code>global-next-node</code>) and &lsquo;<samp>[</samp>&rsquo; 
(<code>global-prev-node</code>)

Index: Tests/texinfo_res/Window-Commands.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/texinfo_res/Window-Commands.html,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -b -r1.9 -r1.10
--- Tests/texinfo_res/Window-Commands.html      5 Feb 2007 15:30:26 -0000       
1.9
+++ Tests/texinfo_res/Window-Commands.html      3 Oct 2007 09:34:49 -0000       
1.10
@@ -140,7 +140,7 @@
 </pre></td></tr></table>
 
 <p>When a node comes from a file which is compressed on disk, this is
-indicated in the mode line with two small &lsquo;<samp>z</samp>&rsquo;'s.  In 
addition, if
+indicated in the mode line with two small 
&lsquo;<samp>z</samp>&rsquo;&rsquo;s.  In addition, if
 the Info file containing the node has been split into subfiles, the name
 of the subfile containing the node appears in the modeline as well:
 </p>
@@ -427,7 +427,7 @@
 
 <p>The next group of commands deal with <em>killing</em>, and <em>yanking</em>
 text<a name="DOCF6" href="info-stnd_fot.html#FOOT6">(6)</a>.   For an in depth 
discussion of killing and
-yanking, see <a href="../emacs/Killing.html#Killing">(emacs)Killing</a> 
section `Killing and Deleting' in <cite>the GNU Emacs Manual</cite>
+yanking, see <a href="../emacs/Killing.html#Killing">(emacs)Killing</a> 
section &lsquo;Killing and Deleting&rsquo; in <cite>the GNU Emacs Manual</cite>
 </p>
 <dl compact="compact">
 <dt> &lt;M-d&gt; (<code>echo-area-kill-word</code>)</dt>

Index: Tests/texinfo_res/Xref-Commands.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/texinfo_res/Xref-Commands.html,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -b -r1.9 -r1.10
--- Tests/texinfo_res/Xref-Commands.html        5 Feb 2007 15:30:26 -0000       
1.9
+++ Tests/texinfo_res/Xref-Commands.html        3 Oct 2007 09:34:49 -0000       
1.10
@@ -143,7 +143,7 @@
 </p>
 <p>You will normally see two types of cross reference while viewing nodes:
 <em>menu</em> references, and <em>note</em> references.  Menu references
-appear within a node's menu; they begin with a &lsquo;<samp>*</samp>&rsquo; at 
the beginning
+appear within a node&rsquo;s menu; they begin with a 
&lsquo;<samp>*</samp>&rsquo; at the beginning
 of a line, and continue with a label, a target, and a comment which
 describes what the contents of the node pointed to contains.
 </p>
@@ -154,7 +154,7 @@
 can point to any valid node.  They are used to refer you to a place
 where more detailed information can be found on a particular subject.
 Here is a cross reference which points to a node within the Texinfo
-documentation:  See <a href="../texinfo/xref.html#xref">(texinfo)xref</a> 
section `Writing an Xref' in <cite>the Texinfo Manual</cite>, for more 
information on creating your own texinfo cross
+documentation:  See <a href="../texinfo/xref.html#xref">(texinfo)xref</a> 
section &lsquo;Writing an Xref&rsquo; in <cite>the Texinfo Manual</cite>, for 
more information on creating your own texinfo cross
 references.
 </p>
 <hr size="6">
@@ -193,7 +193,7 @@
 <p>Within an Info window, pressing a single digit, (such as 
&lsquo;<samp>1</samp>&rsquo;),
 selects that menu item, and places its node in the current window.
 For convenience, there is one exception; pressing &lsquo;<samp>0</samp>&rsquo; 
selects the
-<em>last</em> item in the node's menu.  When 
&lsquo;<samp>--vi-keys</samp>&rsquo; is in
+<em>last</em> item in the node&rsquo;s menu.  When 
&lsquo;<samp>--vi-keys</samp>&rsquo; is in
 effect, digits set the numeric argument, so these commands are remapped
 to their &lsquo;<samp>M-</samp>&rsquo; varieties.  For example, to select the 
last menu
 item, press &lt;M-0&gt;.
@@ -204,7 +204,7 @@
 <dd><a name="IDX197"></a>
 <a name="IDX198"></a>
 <a name="IDX199"></a>
-<p>Select the last item in the current node's menu.
+<p>Select the last item in the current node&rsquo;s menu.
 </p>
 </dd>
 <dt> &lt;m&gt; (<code>menu-item</code>)</dt>
@@ -216,7 +216,7 @@
 </dd>
 <dt> <kbd>M-x find-menu</kbd></dt>
 <dd><a name="IDX202"></a>
-<p>Move the cursor to the start of this node's menu.
+<p>Move the cursor to the start of this node&rsquo;s menu.
 </p></dd>
 </dl>
 

Index: Tests/texinfo_res/info-stnd.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/texinfo_res/info-stnd.html,v
retrieving revision 1.23
retrieving revision 1.24
diff -u -b -r1.23 -r1.24
--- Tests/texinfo_res/info-stnd.html    5 Feb 2007 15:30:26 -0000       1.23
+++ Tests/texinfo_res/info-stnd.html    3 Oct 2007 09:34:49 -0000       1.24
@@ -86,7 +86,7 @@
 license is included in the section entitled &ldquo;GNU Free Documentation
 License.&rdquo;
 </p>
-<p>(a) The FSF's Back-Cover Text is: &ldquo;You have freedom to copy and modify
+<p>(a) The FSF&rsquo;s Back-Cover Text is: &ldquo;You have freedom to copy and 
modify
 this GNU Manual, like GNU software.  Copies published by the Free
 Software Foundation raise funds for GNU development.&rdquo;
 </p></blockquote>

Index: Tests/texinfo_res/info-stnd_fot.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/texinfo_res/info-stnd_fot.html,v
retrieving revision 1.20
retrieving revision 1.21
diff -u -b -r1.20 -r1.21
--- Tests/texinfo_res/info-stnd_fot.html        5 Feb 2007 15:30:26 -0000       
1.20
+++ Tests/texinfo_res/info-stnd_fot.html        3 Oct 2007 09:34:50 -0000       
1.21
@@ -76,25 +76,25 @@
 <p>The MS-DOS version allows for the Info
 extension, such as <code>.inf</code>, and the short compressed file
 extensions, such as &lsquo;<tt>.z</tt>&rsquo; and &lsquo;<tt>.gz</tt>&rsquo;, 
to be merged into a single
-extension, since DOS doesn't allow more than a single dot in the
+extension, since DOS doesn&rsquo;t allow more than a single dot in the
 basename of a file.  Thus, on MS-DOS, if Info looks for 
&lsquo;<tt>bison</tt>&rsquo;,
 file names like &lsquo;<tt>bison.igz</tt>&rsquo; and 
&lsquo;<tt>bison.inz</tt>&rsquo; will be found and
 decompressed by <code>gunzip</code>.
 </p><h3><a name="FOOT3" href="Invoking-Info.html#DOCF3">(3)</a></h3>
 <p>Of course, you can specify both the file and node
-in a <code>--node</code> command; but don't forget to escape the open and
+in a <code>--node</code> command; but don&rsquo;t forget to escape the open and
 close parentheses and whitespace from the shell as in: <code>info --node
 &quot;(emacs)Buffers&quot;</code>.
 </p><h3><a name="FOOT4" href="Cursor-Commands.html#DOCF4">(4)</a></h3>
 
-<p>Here's a short summary.  <kbd>C-<var>x</var></kbd> means press the 
<kbd>CTRL</kbd> key
+<p>Here&rsquo;s a short summary.  <kbd>C-<var>x</var></kbd> means press the 
<kbd>CTRL</kbd> key
 and the key <var>x</var>.  <kbd>M-<var>x</var></kbd> means press the 
<kbd>META</kbd> key and
 the key <var>x</var>.  On many terminals th <kbd>META</kbd> key is known as the
 <kbd>ALT</kbd> key.  <kbd>SPC</kbd> is the space bar.  The other keys are 
usually
 called by the names imprinted on them.
 </p><h3><a name="FOOT5" href="Cursor-Commands.html#DOCF5">(5)</a></h3>
 <p><code>M-x</code> is also a command; it
-invokes <code>execute-extended-command</code>.  See <a 
href="../emacs/M_002dx.html#M_002dx">(emacs)M-x</a> section `Executing an 
extended command' in <cite>the GNU Emacs Manual</cite>, for more detailed
+invokes <code>execute-extended-command</code>.  See <a 
href="../emacs/M_002dx.html#M_002dx">(emacs)M-x</a> section &lsquo;Executing an 
extended command&rsquo; in <cite>the GNU Emacs Manual</cite>, for more detailed
 information.
 </p><h3><a name="FOOT6" href="Window-Commands.html#DOCF6">(6)</a></h3>
 

Index: Tests/texinfo_res/texinfo.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/texinfo_res/texinfo.html,v
retrieving revision 1.30
retrieving revision 1.31
diff -u -b -r1.30 -r1.31
--- Tests/texinfo_res/texinfo.html      30 Sep 2007 12:47:39 -0000      1.30
+++ Tests/texinfo_res/texinfo.html      3 Oct 2007 09:34:50 -0000       1.31
@@ -84,7 +84,7 @@
 and with the Back-Cover Texts as in (a) below.  A copy of the license is
 included in the section entitled &ldquo;GNU Free Documentation License.&rdquo;
 </p>
-<p>(a) The FSF's Back-Cover Text is: &ldquo;You have freedom to copy and modify
+<p>(a) The FSF&rsquo;s Back-Cover Text is: &ldquo;You have freedom to copy and 
modify
 this GNU Manual, like GNU software.  Copies published by the Free
 Software Foundation raise funds for GNU development.&rdquo;
 </p></blockquote>
@@ -197,7 +197,7 @@
 
 </pre></th></tr><tr><td align="left" valign="top"><a 
href="texinfo_3.html#Texinfo-Mode-Overview">&bull; Texinfo Mode 
Overview</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">       How 
Texinfo mode can help you.
 </td></tr>
-<tr><td align="left" valign="top"><a href="texinfo_3.html#SEC23">2.1 The Usual 
GNU Emacs Editing Commands</a></td><td>&nbsp;&nbsp;</td><td align="left" 
valign="top">               Texinfo mode adds to GNU Emacs' general
+<tr><td align="left" valign="top"><a href="texinfo_3.html#SEC23">2.1 The Usual 
GNU Emacs Editing Commands</a></td><td>&nbsp;&nbsp;</td><td align="left" 
valign="top">               Texinfo mode adds to GNU Emacs&rsquo; general
                                   purpose editing features.
 </td></tr>
 <tr><td align="left" valign="top"><a href="texinfo_3.html#SEC24">2.2 Inserting 
Frequently Used Commands</a></td><td>&nbsp;&nbsp;</td><td align="left" 
valign="top">                   How to insert frequently used @-commands.
@@ -235,7 +235,7 @@
 </td></tr>
 <tr><td align="left" valign="top"><a href="texinfo_4.html#SEC52">3.4 Title and 
Copyright Pages</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">  
Creating the title and copyright pages.
 </td></tr>
-<tr><td align="left" valign="top"><a href="texinfo_4.html#SEC59">3.5 The `Top' 
Node and Master Menu</a></td><td>&nbsp;&nbsp;</td><td align="left" 
valign="top">                Creating the `Top' node and master menu.
+<tr><td align="left" valign="top"><a href="texinfo_4.html#SEC59">3.5 The 
&lsquo;Top&rsquo; Node and Master Menu</a></td><td>&nbsp;&nbsp;</td><td 
align="left" valign="top">                Creating the &lsquo;Top&rsquo; node 
and master menu.
 </td></tr>
 <tr><td align="left" valign="top"><a href="texinfo_4.html#SEC62">3.6 Global 
Document Commands</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">   
 
 </td></tr>
@@ -258,7 +258,7 @@
 <tr><th colspan="3" align="left" valign="top"><pre class="menu-comment">
 Document Permissions
 
-</pre></th></tr><tr><td align="left" valign="top"><a 
href="texinfo_4.html#SEC50">3.3.1 <code>@copying</code>: Declare copying 
permissions</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">         
            Declare the document's copying permissions.
+</pre></th></tr><tr><td align="left" valign="top"><a 
href="texinfo_4.html#SEC50">3.3.1 <code>@copying</code>: Declare copying 
permissions</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">         
            Declare the document&rsquo;s copying permissions.
 </td></tr>
 <tr><td align="left" valign="top"><a href="texinfo_4.html#SEC51">3.3.2 
<code>@insertcopying</code>: Include permissions 
text</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">               
Where to insert the permissions.
 </td></tr>
@@ -317,7 +317,7 @@
 </td></tr>
 <tr><td align="left" valign="top"><a href="texinfo_6.html#SEC74">5.2 
Structuring Command Types</a></td><td>&nbsp;&nbsp;</td><td align="left" 
valign="top">   How to divide a manual into parts.
 </td></tr>
-<tr><td align="left" valign="top"><a href="texinfo_6.html#SEC75">5.3 
<code>@top</code></a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">   
             The <code>@top</code> command, part of the `Top' node.
+<tr><td align="left" valign="top"><a href="texinfo_6.html#SEC75">5.3 
<code>@top</code></a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">   
             The <code>@top</code> command, part of the &lsquo;Top&rsquo; node.
 </td></tr>
 <tr><td align="left" valign="top"><a href="texinfo_6.html#SEC76">5.4 
<code>@chapter</code></a></td><td>&nbsp;&nbsp;</td><td align="left" 
valign="top">                     
 </td></tr>
@@ -333,9 +333,9 @@
 </td></tr>
 <tr><td align="left" valign="top"><a href="texinfo_6.html#SEC82">5.10 The 
<code>@subsection</code>-like Commands</a></td><td>&nbsp;&nbsp;</td><td 
align="left" valign="top">  
 </td></tr>
-<tr><td align="left" valign="top"><a href="texinfo_6.html#SEC83">5.11 The 
`subsub' Commands</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">   
            Commands for the lowest level sections.
+<tr><td align="left" valign="top"><a href="texinfo_6.html#SEC83">5.11 The 
&lsquo;subsub&rsquo; Commands</a></td><td>&nbsp;&nbsp;</td><td align="left" 
valign="top">               Commands for the lowest level sections.
 </td></tr>
-<tr><td align="left" valign="top"><a href="texinfo_6.html#SEC84">5.12 
<code>@raisesections</code> and 
<code>@lowersections</code></a></td><td>&nbsp;&nbsp;</td><td align="left" 
valign="top">        How to change commands' hierarchical level.
+<tr><td align="left" valign="top"><a href="texinfo_6.html#SEC84">5.12 
<code>@raisesections</code> and 
<code>@lowersections</code></a></td><td>&nbsp;&nbsp;</td><td align="left" 
valign="top">        How to change commands&rsquo; hierarchical level.
 </td></tr>
 <tr><th colspan="3" align="left" valign="top"><pre class="menu-comment">
 Nodes
@@ -362,7 +362,7 @@
 </td></tr>
 <tr><td align="left" valign="top"><a href="texinfo_7.html#SEC92">6.3.4 
<code>@node</code> Line Requirements</a></td><td>&nbsp;&nbsp;</td><td 
align="left" valign="top">      Keep names unique, without @-commands.
 </td></tr>
-<tr><td align="left" valign="top"><a href="texinfo_7.html#SEC93">6.3.5 The 
First Node</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">          
        How to write a `Top' node.
+<tr><td align="left" valign="top"><a href="texinfo_7.html#SEC93">6.3.5 The 
First Node</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">          
        How to write a &lsquo;Top&rsquo; node.
 </td></tr>
 <tr><td align="left" valign="top"><a href="texinfo_7.html#SEC94">6.3.6 The 
<code>@top</code> Sectioning Command</a></td><td>&nbsp;&nbsp;</td><td 
align="left" valign="top">        How to use the <code>@top</code> command.
 </td></tr>
@@ -390,9 +390,9 @@
 </td></tr>
 <tr><td align="left" valign="top"><a href="texinfo_9.html#SEC107">8.2 Parts of 
a Cross Reference</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">   
    A cross reference has several parts.
 </td></tr>
-<tr><td align="left" valign="top"><a href="texinfo_9.html#SEC108">8.3 
<code>@xref</code></a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">  
                      Begin a reference with `See' &hellip;
+<tr><td align="left" valign="top"><a href="texinfo_9.html#SEC108">8.3 
<code>@xref</code></a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">  
                      Begin a reference with &lsquo;See&rsquo; &hellip;
 </td></tr>
-<tr><td align="left" valign="top"><a href="texinfo_9.html#SEC114">8.4 Naming a 
`Top' Node</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">          
   How to refer to the beginning of another file.
+<tr><td align="left" valign="top"><a href="texinfo_9.html#SEC114">8.4 Naming a 
&lsquo;Top&rsquo; Node</a></td><td>&nbsp;&nbsp;</td><td align="left" 
valign="top">             How to refer to the beginning of another file.
 </td></tr>
 <tr><td align="left" valign="top"><a href="texinfo_9.html#SEC115">8.5 
<code>@ref</code></a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">   
                      A reference for the last part of a sentence.
 </td></tr>
@@ -487,7 +487,7 @@
 </td></tr>
 <tr><td align="left" valign="top"><a href="texinfo_11.html#SEC150">10.9 
<code>@format</code> and 
<code>@smallformat</code></a></td><td>&nbsp;&nbsp;</td><td align="left" 
valign="top">                      Writing an example without narrowed margins.
 </td></tr>
-<tr><td align="left" valign="top"><a href="texinfo_11.html#SEC151">10.10 
<code>@exdent</code>: Undoing a Line's 
Indentation</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">         
             Undo indentation on a line.
+<tr><td align="left" valign="top"><a href="texinfo_11.html#SEC151">10.10 
<code>@exdent</code>: Undoing a Line&rsquo;s 
Indentation</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">         
             Undo indentation on a line.
 </td></tr>
 <tr><td align="left" valign="top"><a href="texinfo_11.html#SEC152">10.11 
<code>@flushleft</code> and 
<code>@flushright</code></a></td><td>&nbsp;&nbsp;</td><td align="left" 
valign="top">      Pushing text flush left or flush right.
 </td></tr>
@@ -585,7 +585,7 @@
 <tr><th colspan="3" align="left" valign="top"><pre class="menu-comment">
 Inserting Space
 
-</pre></th></tr><tr><td align="left" valign="top"><a 
href="texinfo_14.html#SEC179">13.2.1 Not Ending a 
Sentence</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">       
Sometimes a . doesn't end a sentence.
+</pre></th></tr><tr><td align="left" valign="top"><a 
href="texinfo_14.html#SEC179">13.2.1 Not Ending a 
Sentence</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">       
Sometimes a . doesn&rsquo;t end a sentence.
 </td></tr>
 <tr><td align="left" valign="top"><a href="texinfo_14.html#SEC180">13.2.2 
Ending a Sentence</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">   
        Sometimes it does.
 </td></tr>
@@ -673,7 +673,7 @@
 </td></tr>
 <tr><td align="left" valign="top"><a href="texinfo_16.html#SEC216">15.2 
Optional and Repeated Arguments</a></td><td>&nbsp;&nbsp;</td><td align="left" 
valign="top">          How to handle optional and repeated arguments.
 </td></tr>
-<tr><td align="left" valign="top"><a href="texinfo_16.html#SEC217">15.3 Two or 
More `First' Lines</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">  
                    How to group two or more `first' lines.
+<tr><td align="left" valign="top"><a href="texinfo_16.html#SEC217">15.3 Two or 
More &lsquo;First&rsquo; Lines</a></td><td>&nbsp;&nbsp;</td><td align="left" 
valign="top">                      How to group two or more &lsquo;first&rsquo; 
lines.
 </td></tr>
 <tr><td align="left" valign="top"><a href="texinfo_16.html#SEC218">15.4 The 
Definition Commands</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top"> 
         All the definition commands.
 </td></tr>
@@ -730,7 +730,7 @@
 
 </pre></th></tr><tr><td align="left" valign="top"><a 
href="texinfo_19.html#SEC239">18.1 Defining 
Macros</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">             
Defining and undefining new commands.
 </td></tr>
-<tr><td align="left" valign="top"><a href="texinfo_19.html#SEC240">18.2 
Invoking Macros</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">     
        Using a macro, once you've defined it.
+<tr><td align="left" valign="top"><a href="texinfo_19.html#SEC240">18.2 
Invoking Macros</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">     
        Using a macro, once you&rsquo;ve defined it.
 </td></tr>
 <tr><td align="left" valign="top"><a href="texinfo_19.html#SEC241">18.3 Macro 
Details</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">             
  Beyond basic macro usage.
 </td></tr>
@@ -753,7 +753,7 @@
 </td></tr>
 <tr><td align="left" valign="top"><a href="texinfo_20.html#SEC250">19.6 
Formatting and Printing in Texinfo Mode</a></td><td>&nbsp;&nbsp;</td><td 
align="left" valign="top">       How to format and print in Texinfo mode.
 </td></tr>
-<tr><td align="left" valign="top"><a href="texinfo_20.html#SEC251">19.7 Using 
the Local Variables List</a></td><td>&nbsp;&nbsp;</td><td align="left" 
valign="top">             How to print using Emacs's compile command.
+<tr><td align="left" valign="top"><a href="texinfo_20.html#SEC251">19.7 Using 
the Local Variables List</a></td><td>&nbsp;&nbsp;</td><td align="left" 
valign="top">             How to print using Emacs&rsquo;s compile command.
 </td></tr>
 <tr><td align="left" valign="top"><a href="texinfo_20.html#SEC252">19.8 TeX 
Formatting Requirements Summary</a></td><td>&nbsp;&nbsp;</td><td align="left" 
valign="top">        TeX formatting requirements summary.
 </td></tr>

Index: Tests/texinfo_res/texinfo_10.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/texinfo_res/texinfo_10.html,v
retrieving revision 1.31
retrieving revision 1.32
diff -u -b -r1.31 -r1.32
--- Tests/texinfo_res/texinfo_10.html   5 Feb 2007 15:30:26 -0000       1.31
+++ Tests/texinfo_res/texinfo_10.html   3 Oct 2007 09:34:50 -0000       1.32
@@ -520,7 +520,7 @@
 </blockquote>
 
 <a name="IDX130"></a>
-<p>There are subtleties to handling words like `meta' or `ctrl' that are
+<p>There are subtleties to handling words like &lsquo;meta&rsquo; or 
&lsquo;ctrl&rsquo; that are
 names of modifier keys.  When mentioning a character in which the
 modifier key is used, such as <kbd>Meta-a</kbd>, use the <code>@kbd</code> 
command
 alone; do not use the <code>@key</code> command; but when you are referring
@@ -551,7 +551,7 @@
 <h3 class="subsection"> 9.1.4 <code>@samp</code>{<var>text</var>} </h3>
 
 <p>Use the <code>@samp</code> command to indicate text that is a literal 
example
-or `sample' of a sequence of characters in a file, string, pattern, etc.
+or &lsquo;sample&rsquo; of a sequence of characters in a file, string, 
pattern, etc.
 Enclose the text in braces.  The argument appears within single
 quotation marks in both the Info file and the printed manual; in
 addition, it is printed in a fixed-width font.
@@ -616,7 +616,7 @@
 <p>Use the <code>@verb</code> command to print a verbatim sequence of
 characters.
 </p>
-<p>Like LaTeX's <code>\verb</code> command, the verbatim text can be quoted 
using
+<p>Like LaTeX&rsquo;s <code>\verb</code> command, the verbatim text can be 
quoted using
 any unique delimiter character.  Enclose the verbatim text, including the
 delimiters, in braces.  Text is printed in a fixed-width font:
 </p>
@@ -829,7 +829,7 @@
 
 <p>You should write the name of a program in the ordinary text font, rather
 than using <code>@command</code>, if you regard it as a new English word,
-such as `Emacs' or `Bison'.
+such as &lsquo;Emacs&rsquo; or &lsquo;Bison&rsquo;.
 </p>
 <p>When writing an entire shell command invocation, as in &lsquo;<samp>ls 
-l</samp>&rsquo;,
 you should use either <code>@samp</code> or <code>@code</code> at your 
discretion.
@@ -968,7 +968,7 @@
 <h3 class="subsection"> 9.1.13 <code>@acronym</code>{<var>acronym</var>} </h3>
 
 <p>Use the <code>@acronym</code> command for abbreviations written in all
-capital letters, such as `<acronym>NASA</acronym>'.  The abbreviation is given 
as
+capital letters, such as &lsquo;<acronym>NASA</acronym>&rsquo;.  The 
abbreviation is given as
 the single argument in braces, as in 
&lsquo;<samp>@acronym{NASA}</samp>&rsquo;.  As
 a matter of style, or for particular abbreviations, you may prefer to
 use periods, as in &lsquo;<samp>@acronym{F.B.I.}</samp>&rsquo;.
@@ -1002,7 +1002,7 @@
 the World Wide Web.  This is analogous to <code>@file</code>, 
<code>@var</code>,
 etc., and is purely for markup purposes.  It does not produce a link you
 can follow in HTML output (use the <code>@uref</code> command for that,
-see section <a href="texinfo_9.html#SEC118"><code>@uref</code></a>).  It is 
useful for url's which do
+see section <a href="texinfo_9.html#SEC118"><code>@uref</code></a>).  It is 
useful for url&rsquo;s which do
 not actually exist.  For example:
 </p>
 <table><tr><td>&nbsp;</td><td><pre class="example">For example, the url might 
be @url{http://example.org/path}.
@@ -1133,7 +1133,7 @@
 </pre></td></tr></table>
 
 <p>The <code>@strong</code> command is seldom used except to mark what is, in
-effect, a typographical element, such as the word `Caution' in the
+effect, a typographical element, such as the word &lsquo;Caution&rsquo; in the
 preceding example.
 </p>
 <p>In the Info output, <code>@emph</code> surrounds the text with underscores
@@ -1180,19 +1180,19 @@
 </pre></td></tr></table>
 
 <p>TeX typesets the small caps font in a manner that prevents the
-letters from `jumping out at you on the page'.  This makes small caps
-text easier to read than text in all upper case&mdash;but it's usually
+letters from &lsquo;jumping out at you on the page&rsquo;.  This makes small 
caps
+text easier to read than text in all upper case&mdash;but it&rsquo;s usually
 better to use regular mixed case anyway.  The Info formatting commands
 set all small caps text in upper case.  In HTML, the text is upper-cased
 and a smaller font is used to render it.
 </p>
 <p>If the text between the braces of an <code>@sc</code> command is uppercase,
 TeX typesets in FULL-SIZE CAPITALS.  Use full-size capitals
-sparingly, if ever, and since it's redundant to mark all-uppercase text
+sparingly, if ever, and since it&rsquo;s redundant to mark all-uppercase text
 with <code>@sc</code>, <code>makeinfo</code> warns about such usage.
 </p>
 <p>You may also use the small caps font for a jargon word such as
-<small>ATO</small> (a <small>NASA</small> word meaning `abort to orbit').
+<small>ATO</small> (a <small>NASA</small> word meaning &lsquo;abort to 
orbit&rsquo;).
 </p>
 <p>There are subtleties to using the small caps font with a jargon word
 such as <small>CDR</small>, a word used in Lisp programming.  In this case, you

Index: Tests/texinfo_res/texinfo_11.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/texinfo_res/texinfo_11.html,v
retrieving revision 1.28
retrieving revision 1.29
diff -u -b -r1.28 -r1.29
--- Tests/texinfo_res/texinfo_11.html   5 Feb 2007 15:30:26 -0000       1.28
+++ Tests/texinfo_res/texinfo_11.html   3 Oct 2007 09:34:50 -0000       1.29
@@ -112,7 +112,7 @@
 </td></tr>
 <tr><td align="left" valign="top"><a href="#SEC150">10.9 <code>@format</code> 
and <code>@smallformat</code></a></td><td>&nbsp;&nbsp;</td><td align="left" 
valign="top">                      Writing an example without narrowed margins.
 </td></tr>
-<tr><td align="left" valign="top"><a href="#SEC151">10.10 
<code>@exdent</code>: Undoing a Line's 
Indentation</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">         
             Undo indentation on a line.
+<tr><td align="left" valign="top"><a href="#SEC151">10.10 
<code>@exdent</code>: Undoing a Line&rsquo;s 
Indentation</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">         
             Undo indentation on a line.
 </td></tr>
 <tr><td align="left" valign="top"><a href="#SEC152">10.11 
<code>@flushleft</code> and 
<code>@flushright</code></a></td><td>&nbsp;&nbsp;</td><td align="left" 
valign="top">      Pushing text flush left or flush right.
 </td></tr>
@@ -642,7 +642,7 @@
 <td valign="middle" align="left">[<a href="texinfo_32.html#SEC325" 
title="Index">Index</a>]</td>
 <td valign="middle" align="left">[<a href="texinfo_abt.html#SEC_About" 
title="About (help)"> ? </a>]</td>
 </tr></table>
-<h2 class="section"> 10.10 <code>@exdent</code>: Undoing a Line's Indentation 
</h2>
+<h2 class="section"> 10.10 <code>@exdent</code>: Undoing a Line&rsquo;s 
Indentation </h2>
 
 <p>The <code>@exdent</code> command removes any indentation a line might have.
 The command is written at the beginning of a line and applies only to
@@ -791,7 +791,7 @@
 blank line, and neither does the <code>@end example</code> line.
 </p>
 <p>In the Texinfo source file for this manual, each line that says
-`produces' is preceded by a line containing <code>@noindent</code>.
+&lsquo;produces&rsquo; is preceded by a line containing <code>@noindent</code>.
 </p>
 <p>Do not put braces after an <code>@noindent</code> command; they are not
 necessary, since <code>@noindent</code> is a command used outside of

Index: Tests/texinfo_res/texinfo_12.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/texinfo_res/texinfo_12.html,v
retrieving revision 1.33
retrieving revision 1.34
diff -u -b -r1.33 -r1.34
--- Tests/texinfo_res/texinfo_12.html   5 Feb 2007 15:30:26 -0000       1.33
+++ Tests/texinfo_res/texinfo_12.html   3 Oct 2007 09:34:50 -0000       1.34
@@ -201,10 +201,10 @@
 Texinfo command that generates a mark.  Usually, you will write
 <code>@bullet</code> after <code>@itemize</code>, but you can use
 <code>@minus</code>, or any command or character that results in a single
-character in the Info file.  If you don't want any mark at all, use
+character in the Info file.  If you don&rsquo;t want any mark at all, use
 <code>@w</code>.  (When you write the mark command such as
 <code>@bullet</code> after an <code>@itemize</code> command, you may omit the
-&lsquo;<samp>{}</samp>&rsquo;.)  If you don't specify a mark command, the 
default is
+&lsquo;<samp>{}</samp>&rsquo;.)  If you don&rsquo;t specify a mark command, 
the default is
 <code>@bullet</code>.
 </p>
 <p>Write the text of the indented paragraphs themselves after the
@@ -460,7 +460,7 @@
 of each item and determines how it will be highlighted.  For example,
 <code>@code</code> will cause the text in the first column to be highlighted
 with an <code>@code</code> command.  (We recommend <code>@code</code> for
-<code>@table</code>'s of command-line options.)
+<code>@table</code>&rsquo;s of command-line options.)
 </p>
 <a name="IDX138"></a>
 <p>You may also choose to use the <code>@asis</code> command as an argument to
@@ -695,8 +695,8 @@
 <table><tr><td>&nbsp;</td><td><pre class="example">@multitable {some text for 
column one} {for column two}
 </pre></td></tr></table>
 
-<p>The first column will then have the width of the typeset `some text for
-column one', and the second column the width of `for column two'.
+<p>The first column will then have the width of the typeset &lsquo;some text 
for
+column one&rsquo;, and the second column the width of &lsquo;for column 
two&rsquo;.
 </p>
 <p>The prototype entries need not appear in the table itself.
 </p>
@@ -735,7 +735,7 @@
 input lines in your source file as necessary.
 </p>
 <p>Here is a complete example of a multi-column table (the text is from
-<cite>The GNU Emacs Manual</cite>, see <a 
href="../emacs/Split-Window.html#Split-Window">(emacs)Split Window</a> section 
`Splitting Windows' in <cite>The GNU Emacs Manual</cite>):
+<cite>The GNU Emacs Manual</cite>, see <a 
href="../emacs/Split-Window.html#Split-Window">(emacs)Split Window</a> section 
&lsquo;Splitting Windows&rsquo; in <cite>The GNU Emacs Manual</cite>):
 </p>
 <table><tr><td>&nbsp;</td><td><pre class="example">@multitable 
@columnfractions .15 .45 .4
 @item Key @tab Command @tab Description

Index: Tests/texinfo_res/texinfo_13.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/texinfo_res/texinfo_13.html,v
retrieving revision 1.27
retrieving revision 1.28
diff -u -b -r1.27 -r1.28
--- Tests/texinfo_res/texinfo_13.html   5 Feb 2007 15:30:26 -0000       1.27
+++ Tests/texinfo_res/texinfo_13.html   3 Oct 2007 09:34:50 -0000       1.28
@@ -249,10 +249,10 @@
 the index often looks better if the entries are not capitalized, but
 written just as they would appear in the middle of a sentence.
 (Capitalize proper names and acronyms that always call for upper case
-letters.)  This is the case convention we use in most GNU manuals'
+letters.)  This is the case convention we use in most GNU manuals&rsquo;
 indices.
 </p>
-<p>If you don't see how to make an entry terse yet clear, make it longer
+<p>If you don&rsquo;t see how to make an entry terse yet clear, make it longer
 and clear&mdash;not terse and confusing.  If many of the entries are several
 words long, the index may look better if you use a different convention:
 to capitalize the first word of each entry.  But do not capitalize a
@@ -318,7 +318,7 @@
 preprocessor macros.  You could put them in the function index along
 with actual functions, just by writing <code>@findex</code> commands for
 them; then, when you print the &ldquo;Function Index&rdquo; as an unnumbered
-chapter, you could give it the title `Function and Macro Index' and
+chapter, you could give it the title &lsquo;Function and Macro Index&rsquo; and
 all will be consistent for the reader.  Or you could put the macros in
 with the data types by writing <code>@tindex</code> commands for them, and
 give that index a suitable title so the reader will understand.
@@ -352,8 +352,8 @@
 <p>You could put functions into the concept index by writing
 <code>@cindex</code> commands for them instead of <code>@findex</code> 
commands,
 and produce a consistent manual by printing the concept index with the
-title `Function and Concept Index' and not printing the `Function
-Index' at all; but this is not a robust procedure.  It works only if
+title &lsquo;Function and Concept Index&rsquo; and not printing the 
&lsquo;Function
+Index&rsquo; at all; but this is not a robust procedure.  It works only if
 your document is never included as part of another
 document that is designed to have a separate function index; if your
 document were to be included with such a document, the functions from
@@ -451,7 +451,7 @@
 </pre></td></tr></table>
 
 <a name="IDX159"></a>
-<p>The <code>@syncodeindex</code> command puts all the entries from the `from'
+<p>The <code>@syncodeindex</code> command puts all the entries from the 
&lsquo;from&rsquo;
 index (the redirected index) into the <code>@code</code> font, overriding
 whatever default font is used by the index to which the entries are
 now directed.  This way, if you direct function names from a function
@@ -481,7 +481,7 @@
 
 <p>The <code>@synindex</code> command is nearly the same as the
 <code>@syncodeindex</code> command, except that it does not put the
-`from' index  entries into the <code>@code</code> font; rather it puts
+&lsquo;from&rsquo; index  entries into the <code>@code</code> font; rather it 
puts
 them in the roman font.  Thus, you use <code>@synindex</code> when you
 merge a concept index into a function index.
 </p>

Index: Tests/texinfo_res/texinfo_14.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/texinfo_res/texinfo_14.html,v
retrieving revision 1.31
retrieving revision 1.32
diff -u -b -r1.31 -r1.32
--- Tests/texinfo_res/texinfo_14.html   30 Sep 2007 12:47:40 -0000      1.31
+++ Tests/texinfo_res/texinfo_14.html   3 Oct 2007 09:34:50 -0000       1.32
@@ -233,7 +233,7 @@
 kinds within and after sentences.
 </p>
 <table class="menu" border="0" cellspacing="0">
-<tr><td align="left" valign="top"><a href="#SEC179">13.2.1 Not Ending a 
Sentence</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">       
Sometimes a . doesn't end a sentence.
+<tr><td align="left" valign="top"><a href="#SEC179">13.2.1 Not Ending a 
Sentence</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">       
Sometimes a . doesn&rsquo;t end a sentence.
 </td></tr>
 <tr><td align="left" valign="top"><a href="#SEC180">13.2.2 Ending a 
Sentence</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">           
Sometimes it does.
 </td></tr>
@@ -342,7 +342,7 @@
 &lsquo;<samp>.</samp>&rsquo;; likewise for <code>@!</code> and <code>@?</code>.
 </p>
 <p>The meanings of <code>@:</code> and <code>@.</code> in Texinfo are designed 
to
-work well with the Emacs sentence motion commands (see <a 
href="../emacs/Sentences.html#Sentences">(emacs)Sentences</a> section 
`Sentences' in <cite>The GNU Emacs Manual</cite>).
+work well with the Emacs sentence motion commands (see <a 
href="../emacs/Sentences.html#Sentences">(emacs)Sentences</a> section 
&lsquo;Sentences&rsquo; in <cite>The GNU Emacs Manual</cite>).
 </p>
 <p>Do not put braces after any of these commands.
 </p>
@@ -517,7 +517,7 @@
 </p></td></tr>
 <tr><td><p> <tt>@&quot;o</tt>              </p></td><td><p> &ouml;            
</p></td><td><p> umlaut accent
 </p></td></tr>
-<tr><td><p> <tt>@'o</tt>              </p></td><td><p> &oacute;            
</p></td><td><p> acute accent
+<tr><td><p> <tt>@&rsquo;o</tt>              </p></td><td><p> &oacute;          
  </p></td><td><p> acute accent
 </p></td></tr>
 <tr><td><p> <tt>@,{c}</tt>          </p></td><td><p> &ccedil;          
</p></td><td><p> cedilla accent
 </p></td></tr>
@@ -525,7 +525,7 @@
 </p></td></tr>
 <tr><td><p> <tt>@^o</tt>              </p></td><td><p> &ocirc;            
</p></td><td><p> circumflex accent
 </p></td></tr>
-<tr><td><p> <tt>@`o</tt>              </p></td><td><p> &ograve;            
</p></td><td><p> grave accent
+<tr><td><p> <tt>@&lsquo;o</tt>              </p></td><td><p> &ograve;          
  </p></td><td><p> grave accent
 </p></td></tr>
 <tr><td><p> <tt>@~o</tt>              </p></td><td><p> &otilde;            
</p></td><td><p> tilde accent
 </p></td></tr>
@@ -666,7 +666,7 @@
 <h3 class="subsection"> 13.4.1 <code>@dots</code>{} (&hellip;) and 
<code>@enddots</code>{} (<small class="enddots">...</small>) </h3>
 
 <p>Use the <code>@dots{}</code> command to generate an ellipsis, which is
-three dots in a row, appropriately spaced, like this: `&hellip;'.  Do
+three dots in a row, appropriately spaced, like this: &lsquo;&hellip;&rsquo;.  
Do
 not simply write three periods in the input file; that would work for
 the Info file output, but would produce the wrong amount of space
 between the periods in the printed manual.
@@ -728,8 +728,8 @@
 </tr></table>
 <h2 class="section"> 13.5 Inserting TeX and the Copyright Symbol </h2>
 
-<p>The logo `TeX' is typeset in a special fashion and it needs an
address@hidden  The copyright symbol, `&copy;', is also special.
+<p>The logo &lsquo;TeX&rsquo; is typeset in a special fashion and it needs an
address@hidden  The copyright symbol, &lsquo;&copy;&rsquo;, is also special.
 Each of these commands is followed by a pair of braces, 
&lsquo;<samp>{}</samp>&rsquo;,
 without any whitespace between the name of the command and the
 braces.
@@ -763,7 +763,7 @@
 </tr></table>
 <h3 class="subsection"> 13.5.1 <code>@TeX</code>{} (TeX) </h3>
 
-<p>Use the <code>@TeX{}</code> command to generate `TeX'.  In a printed
+<p>Use the <code>@TeX{}</code> command to generate &lsquo;TeX&rsquo;.  In a 
printed
 manual, this is a special logo that is different from three ordinary
 letters.  In Info, it just looks like &lsquo;<samp>TeX</samp>&rsquo;.  The
 <code>@TeX{}</code> command is unique among Texinfo commands in that the
@@ -791,7 +791,7 @@
 </tr></table>
 <h3 class="subsection"> 13.5.2 <code>@copyright</code>{} (&copy;) </h3>
 
-<p>Use the <code>@copyright{}</code> command to generate `&copy;'.  In
+<p>Use the <code>@copyright{}</code> command to generate &lsquo;&copy;&rsquo;. 
 In
 a printed manual, this is a &lsquo;<samp>c</samp>&rsquo; inside a circle, and 
in Info,
 this is &lsquo;<samp>(C)</samp>&rsquo;.
 </p>
@@ -817,7 +817,7 @@
 </tr></table>
 <h2 class="section"> 13.6 <code>@pounds</code>{} (&pound;): Pounds Sterling 
</h2>
 
-<p>Use the <code>@pounds{}</code> command to generate `&pound;'.  In a
+<p>Use the <code>@pounds{}</code> command to generate &lsquo;&pound;&rsquo;.  
In a
 printed manual, this is the symbol for the currency pounds sterling.
 In Info, it is a &lsquo;<samp>#</samp>&rsquo;.  Other currency symbols are 
unfortunately not
 available.
@@ -904,7 +904,7 @@
 </p>
 <p><code>@math</code> implies <code>@tex</code>.  This not only makes it 
possible to
 write superscripts and subscripts (as in the above example), but also
-allows you to use any of the plain TeX math control sequences.  It's
+allows you to use any of the plain TeX math control sequences.  It&rsquo;s
 conventional to use &lsquo;<samp>\</samp>&rsquo; instead of 
&lsquo;<samp>@</samp>&rsquo; for these commands.
 As in:
 </p><table><tr><td>&nbsp;</td><td><pre class="example">@math{\sin 2\pi \equiv 
\cos 3\pi}
@@ -917,7 +917,7 @@
 <a name="IDX224"></a>
 <p>Since &lsquo;<samp>\</samp>&rsquo; is an escape character inside 
<code>@math</code>, you can use
 <code>@\</code> to get a literal backslash (<code>\\</code> will work in TeX,
-but you'll get the literal &lsquo;<samp>\\</samp>&rsquo; in Info).  
<code>@\</code> is not
+but you&rsquo;ll get the literal &lsquo;<samp>\\</samp>&rsquo; in Info).  
<code>@\</code> is not
 defined outside of <code>@math</code>, since a &lsquo;<samp>\</samp>&rsquo; 
ordinarily produces a
 literal &lsquo;<samp>\</samp>&rsquo;.
 </p>
@@ -1211,7 +1211,7 @@
 designate the error message with the <code>@error{}</code> command.
 </p>
 <p>The <code>@error{}</code> command is displayed as 
&lsquo;<samp>error--&gt;</samp>&rsquo; in Info
-and as the word `error' in a box in the printed output.
+and as the word &lsquo;error&rsquo; in a box in the printed output.
 </p>
 <p>Thus,
 </p>
@@ -1422,7 +1422,7 @@
 <p>As you can see, the source includes two punctuation marks next to each
 other; in this case, &lsquo;<samp>.};</samp>&rsquo; is the sequence.  This is 
normal (the
 first ends the footnote and the second belongs to the sentence being
-footnoted), so don't worry that it looks odd.
+footnoted), so don&rsquo;t worry that it looks odd.
 </p>
 <p>In a printed manual or book, the reference mark for a footnote is a
 small, superscripted number; the text of the footnote appears at the
@@ -1430,7 +1430,7 @@
 </p>
 <p>In Info, the reference mark for a footnote is a pair of parentheses
 with the footnote number between them, like this: 
&lsquo;<samp>(1)</samp>&rsquo;.  The
-reference mark is followed by a cross-reference link to the footnote's
+reference mark is followed by a cross-reference link to the footnote&rsquo;s
 text.
 </p>
 <p>In the HTML output, footnote references are marked with a small,
@@ -1469,7 +1469,7 @@
 <ul>
 <li><a name="IDX227"></a>
 </li><li>
-In the `End' node style, all the footnotes for a single node
+In the &lsquo;End&rsquo; node style, all the footnotes for a single node
 are placed at the end of that node.  The footnotes are separated from
 the rest of the node by a line of dashes with the word
 &lsquo;<samp>Footnotes</samp>&rsquo; within it.  Each footnote begins with an
@@ -1484,7 +1484,7 @@
 
 <a name="IDX228"></a>
 </li><li>
-In the `Separate' node style, all the footnotes for a single
+In the &lsquo;Separate&rsquo; node style, all the footnotes for a single
 node are placed in an automatically constructed node of
 their own.  In this style, a &ldquo;footnote reference&rdquo; follows
 each &lsquo;<samp>(<var>n</var>)</samp>&rsquo; reference mark in the body of 
the
@@ -1493,10 +1493,10 @@
 
 <p>The name of the node with the footnotes is constructed
 by appending &lsquo;<samp>-Footnotes</samp>&rsquo; to the name of the node
-that contains the footnotes. (Consequently, the footnotes'
+that contains the footnotes. (Consequently, the footnotes&rsquo;
 node for the &lsquo;<tt>Footnotes</tt>&rsquo; node is
-&lsquo;<tt>Footnotes-Footnotes</tt>&rsquo;!)  The footnotes' node has an
-`Up' node pointer that leads back to its parent node.
+&lsquo;<tt>Footnotes-Footnotes</tt>&rsquo;!)  The footnotes&rsquo; node has an
+&lsquo;Up&rsquo; node pointer that leads back to its parent node.
 </p>
 <p>Here is how the first footnote in this manual looks after being
 formatted for Info in the separate node style:
@@ -1512,7 +1512,7 @@
 style.
 </p>
 <a name="IDX229"></a>
-<p>Use the <code>@footnotestyle</code> command to specify an Info file's
+<p>Use the <code>@footnotestyle</code> command to specify an Info file&rsquo;s
 footnote style.  Write this command at the beginning of a line followed
 by an argument, either &lsquo;<samp>end</samp>&rsquo; for the end node style or
 &lsquo;<samp>separate</samp>&rsquo; for the separate node style.
@@ -1533,8 +1533,8 @@
 </p>
 <p>If you do not specify a footnote style, the formatting commands use
 their default style.  Currently, <code>texinfo-format-buffer</code> and
-<code>texinfo-format-region</code> use the `separate' style and
-<code>makeinfo</code> uses the `end' style.
+<code>texinfo-format-region</code> use the &lsquo;separate&rsquo; style and
+<code>makeinfo</code> uses the &lsquo;end&rsquo; style.
 </p>
 <p>This chapter contains two footnotes.
 </p>
@@ -1577,7 +1577,7 @@
 format).
 </li><li>
 <a name="IDX232"></a>
-PDFTeX reads &lsquo;<tt><var>filename</var>.pdf</tt>&rsquo; (Adobe's Portable 
Document Format).
+PDFTeX reads &lsquo;<tt><var>filename</var>.pdf</tt>&rsquo; (Adobe&rsquo;s 
Portable Document Format).
 </li><li>
 <code>makeinfo</code> uses &lsquo;<tt><var>filename</var>.txt</tt>&rsquo; 
verbatim for
 Info output (more or less as if it was an <code>@example</code>).

Index: Tests/texinfo_res/texinfo_15.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/texinfo_res/texinfo_15.html,v
retrieving revision 1.29
retrieving revision 1.30
diff -u -b -r1.29 -r1.30
--- Tests/texinfo_res/texinfo_15.html   5 Feb 2007 15:30:26 -0000       1.29
+++ Tests/texinfo_res/texinfo_15.html   3 Oct 2007 09:34:50 -0000       1.30
@@ -82,7 +82,7 @@
 
 <p>Usually, a Texinfo file is processed both by TeX and by one of the
 Info formatting commands.  Line, paragraph, or page breaks sometimes
-occur in the `wrong' place in one or other form of output.  You must
+occur in the &lsquo;wrong&rsquo; place in one or other form of output.  You 
must
 ensure that text looks right both in the printed manual and in the
 Info file.
 </p>
@@ -205,7 +205,7 @@
 <p>(Note that the space after the first <code>@*</code> command is faithfully
 carried down to the next line.)
 </p>
-<p>The <code>@*</code> command is often used in a file's copyright page:
+<p>The <code>@*</code> command is often used in a file&rsquo;s copyright page:
 </p>
 <table><tr><td>&nbsp;</td><td><pre class="example">This is edition 2.0 of the 
Texinfo documentation,@*
 and is for &hellip;
@@ -246,7 +246,7 @@
 <h2 class="section"> 14.2 <code>@-</code> and <code>@hyphenation</code>: 
Helping TeX hyphenate </h2>
 
 
-<p>Although TeX's hyphenation algorithm is generally pretty good, it
+<p>Although TeX&rsquo;s hyphenation algorithm is generally pretty good, it
 does miss useful hyphenation points from time to time.  (Or, far more
 rarely, insert an incorrect hyphenation.)  So, for documents with an
 unusual vocabulary or when fine-tuning for a printed edition, you may

Index: Tests/texinfo_res/texinfo_16.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/texinfo_res/texinfo_16.html,v
retrieving revision 1.28
retrieving revision 1.29
diff -u -b -r1.28 -r1.29
--- Tests/texinfo_res/texinfo_16.html   5 Feb 2007 15:30:26 -0000       1.28
+++ Tests/texinfo_res/texinfo_16.html   3 Oct 2007 09:34:50 -0000       1.29
@@ -86,10 +86,10 @@
 format.
 </p>
 <p>In the Info file, a definition causes the entity
-category&mdash;`Function', `Variable', or whatever&mdash;to appear at the
+category&mdash;&lsquo;Function&rsquo;, &lsquo;Variable&rsquo;, or 
whatever&mdash;to appear at the
 beginning of the first line of the definition, followed by the
-entity's name and arguments.  In the printed manual, the command
-causes TeX to print the entity's name and its arguments on the left
+entity&rsquo;s name and arguments.  In the printed manual, the command
+causes TeX to print the entity&rsquo;s name and its arguments on the left
 margin and print the category next to the right margin.  In both
 output formats, the body of the definition is indented.  Also, the
 name of the entity is entered into the appropriate index:
@@ -107,7 +107,7 @@
 </td></tr>
 <tr><td align="left" valign="top"><a href="#SEC216">15.2 Optional and Repeated 
Arguments</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">          
How to handle optional and repeated arguments.
 </td></tr>
-<tr><td align="left" valign="top"><a href="#SEC217">15.3 Two or More `First' 
Lines</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">               
       How to group two or more `first' lines.
+<tr><td align="left" valign="top"><a href="#SEC217">15.3 Two or More 
&lsquo;First&rsquo; Lines</a></td><td>&nbsp;&nbsp;</td><td align="left" 
valign="top">                      How to group two or more &lsquo;first&rsquo; 
lines.
 </td></tr>
 <tr><td align="left" valign="top"><a href="#SEC218">15.4 The Definition 
Commands</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">          
All the definition commands.
 </td></tr>
@@ -175,7 +175,7 @@
 </blockquote>
 
 <p>Capitalize the category name like a title.  If the name of the
-category contains spaces, as in the phrase `Interactive Command',
+category contains spaces, as in the phrase &lsquo;Interactive Command&rsquo;,
 write braces around it.  For example:
 </p>
 <table><tr><td>&nbsp;</td><td><pre class="example">@deffn {Interactive 
Command} isearch-forward
@@ -319,9 +319,9 @@
 <td valign="middle" align="left">[<a href="texinfo_32.html#SEC325" 
title="Index">Index</a>]</td>
 <td valign="middle" align="left">[<a href="texinfo_abt.html#SEC_About" 
title="About (help)"> ? </a>]</td>
 </tr></table>
-<h2 class="section"> 15.3 Two or More `First' Lines </h2>
+<h2 class="section"> 15.3 Two or More &lsquo;First&rsquo; Lines </h2>
 
-<p>To create two or more `first' or header lines for a definition, follow
+<p>To create two or more &lsquo;first&rsquo; or header lines for a definition, 
follow
 the first <code>@deffn</code> line by a line beginning with 
<code>@deffnx</code>.
 The <code>@deffnx</code> command works exactly like <code>@deffn</code>
 except that it does not generate extra vertical white space between it
@@ -347,10 +347,10 @@
 <dd><p>These two search commands are similar except &hellip;
 </p></dd></dl>
 
-<p>Each definition command has an `x' form: <code>@defunx</code>,
+<p>Each definition command has an &lsquo;x&rsquo; form: <code>@defunx</code>,
 <code>@defvrx</code>, <code>@deftypefunx</code>, etc.
 </p>
-<p>The `x' forms work just like <code>@itemx</code>; see <a 
href="texinfo_12.html#SEC162"><code>@itemx</code></a>.
+<p>The &lsquo;x&rsquo; forms work just like <code>@itemx</code>; see <a 
href="texinfo_12.html#SEC162"><code>@itemx</code></a>.
 </p>
 <hr size="6">
 <a name="Def-Cmds-in-Detail"></a>
@@ -504,7 +504,7 @@
 <dt> <code>@defspec <var>name</var> <var>arguments</var>&hellip;</code></dt>
 <dd><p>The <code>@defspec</code> command is the definition command for special
 forms.  (In Lisp, a special form is an entity much like a function,
-see <a href="../elisp/Special-Forms.html#Special-Forms">(elisp)Special 
Forms</a> section `Special Forms' in <cite>GNU Emacs Lisp Reference 
Manual</cite>.)
+see <a href="../elisp/Special-Forms.html#Special-Forms">(elisp)Special 
Forms</a> section &lsquo;Special Forms&rsquo; in <cite>GNU Emacs Lisp Reference 
Manual</cite>.)
 <code>@defspec</code> is equivalent to &lsquo;<samp>@deffn {Special Form}
 &hellip;</samp>&rsquo; and works like <code>@defun</code>.
 </p></dd>
@@ -600,7 +600,7 @@
 <dd><a name="IDX273"></a>
 <p>The <code>@defopt</code> command is the definition command for <em>user
 options</em>, i.e., variables intended for users to change according to
-taste; Emacs has many such (see <a 
href="../emacs/Variables.html#Variables">(emacs)Variables</a> section 
`Variables' in <cite>The GNU Emacs Manual</cite>).  <code>@defopt</code> is 
equivalent to &lsquo;<samp>@defvr {User
+taste; Emacs has many such (see <a 
href="../emacs/Variables.html#Variables">(emacs)Variables</a> section 
&lsquo;Variables&rsquo; in <cite>The GNU Emacs Manual</cite>).  
<code>@defopt</code> is equivalent to &lsquo;<samp>@defvr {User
 Option} &hellip;</samp>&rsquo; and works like <code>@defvar</code>.
 </p></dd>
 </dl>
@@ -697,7 +697,7 @@
 would be a single line in a real Texinfo file.)
 </p>
 <p>In this instance, the procedure is classified as belonging to the
-package <code>stacks</code> rather than classified as a `procedure' and its
+package <code>stacks</code> rather than classified as a 
&lsquo;procedure&rsquo; and its
 data type is described as <code>private</code>.  (The name of the procedure
 is <code>push</code>, and its arguments are <var>s</var> and <var>n</var>.)
 </p>
@@ -960,8 +960,8 @@
 @end defop
 </pre></td></tr></table>
 
-<p><code>@defop</code> creates an entry, such as `<code>expose</code> on
-<code>windows</code>', in the index of functions.
+<p><code>@defop</code> creates an entry, such as &lsquo;<code>expose</code> on
+<code>windows</code>&rsquo;, in the index of functions.
 </p>
 <a name="IDX282"></a>
 </dd>
@@ -1001,8 +1001,8 @@
 @end defmethod
 </pre></td></tr></table>
 
-<p><code>@defmethod</code> creates an entry, such as `<code>bar-method</code> 
on
-<code>bar-class</code>', in the index of functions.
+<p><code>@defmethod</code> creates an entry, such as 
&lsquo;<code>bar-method</code> on
+<code>bar-class</code>&rsquo;, in the index of functions.
 </p>
 
 </dd>
@@ -1129,7 +1129,7 @@
 <code>@defun</code> command and it is followed, on the same line, by the
 parameter list.
 </p>
-<p>Here is a definition from <a 
href="../elisp/Calling-Functions.html#Calling-Functions">(elisp)Calling 
Functions</a> section `Calling Functions' in <cite>The GNU Emacs Lisp Reference 
Manual</cite>.
+<p>Here is a definition from <a 
href="../elisp/Calling-Functions.html#Calling-Functions">(elisp)Calling 
Functions</a> section &lsquo;Calling Functions&rsquo; in <cite>The GNU Emacs 
Lisp Reference Manual</cite>.
 </p>
 <blockquote><dl>
 <dt><u>Function:</u> <b>apply</b><i> function &amp;rest arguments</i>

Index: Tests/texinfo_res/texinfo_17.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/texinfo_res/texinfo_17.html,v
retrieving revision 1.29
retrieving revision 1.30
diff -u -b -r1.29 -r1.30
--- Tests/texinfo_res/texinfo_17.html   5 Feb 2007 15:30:26 -0000       1.29
+++ Tests/texinfo_res/texinfo_17.html   3 Oct 2007 09:34:50 -0000       1.30
@@ -470,7 +470,7 @@
 </pre></td></tr></table>
 
 <p>For example, you can create one document that has two variants, such as
-a manual for a `large' and `small' model:
+a manual for a &lsquo;large&rsquo; and &lsquo;small&rsquo; model:
 </p>
 <a name="IDX295"></a>
 <table><tr><td>&nbsp;</td><td><pre class="example">You can use this machine to 
dig up shrubs
@@ -541,7 +541,7 @@
 you need to change when you record an update to a manual.  See section <a 
href="texinfo_24.html#SEC296">GNU Sample Texts</a>, for an example of this same 
principle can work with
 Automake distributions, and full texts.
 </p>
-<p>Here is an example adapted from <a 
href="../make/index.html#Top">(make)Top</a> section `Overview' in <cite>The GNU 
Make Manual</cite>):
+<p>Here is an example adapted from <a 
href="../make/index.html#Top">(make)Top</a> section &lsquo;Overview&rsquo; in 
<cite>The GNU Make Manual</cite>):
 </p>
 <ol>
 <li>

Index: Tests/texinfo_res/texinfo_18.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/texinfo_res/texinfo_18.html,v
retrieving revision 1.23
retrieving revision 1.24
diff -u -b -r1.23 -r1.24
--- Tests/texinfo_res/texinfo_18.html   5 Feb 2007 15:30:26 -0000       1.23
+++ Tests/texinfo_res/texinfo_18.html   3 Oct 2007 09:34:50 -0000       1.24
@@ -127,10 +127,10 @@
 <p>At present, this command is ignored in Info and HTML output.  For
 TeX, it causes the file &lsquo;<tt>txi-<var>cc</var>.tex</tt>&rsquo; to be 
read (if it
 exists).  Such a file appropriately redefines the various English words
-used in TeX output, such as `Chapter', `See', and so on.
+used in TeX output, such as &lsquo;Chapter&rsquo;, &lsquo;See&rsquo;, and so 
on.
 </p>
 <a name="IDX298"></a>
-<p>It would be good if this command also changed TeX's ideas of the
+<p>It would be good if this command also changed TeX&rsquo;s ideas of the
 current hyphenation patterns (via the TeX primitive
 <code>\language</code>), but this is unfortunately not currently implemented.
 </p>

Index: Tests/texinfo_res/texinfo_19.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/texinfo_res/texinfo_19.html,v
retrieving revision 1.27
retrieving revision 1.28
diff -u -b -r1.27 -r1.28
--- Tests/texinfo_res/texinfo_19.html   5 Feb 2007 15:30:26 -0000       1.27
+++ Tests/texinfo_res/texinfo_19.html   3 Oct 2007 09:34:50 -0000       1.28
@@ -106,7 +106,7 @@
 <table class="menu" border="0" cellspacing="0">
 <tr><td align="left" valign="top"><a href="#SEC239">18.1 Defining 
Macros</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">             
Defining and undefining new commands.
 </td></tr>
-<tr><td align="left" valign="top"><a href="#SEC240">18.2 Invoking 
Macros</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">             
Using a macro, once you've defined it.
+<tr><td align="left" valign="top"><a href="#SEC240">18.2 Invoking 
Macros</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">             
Using a macro, once you&rsquo;ve defined it.
 </td></tr>
 <tr><td align="left" valign="top"><a href="#SEC241">18.3 Macro 
Details</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">             
  Beyond basic macro usage.
 </td></tr>
@@ -194,7 +194,7 @@
 @address@hidden
 </pre></td></tr></table>
 
-<p>This produces the output `a1atextb2b'.  With 
&lsquo;<samp>@macro</samp>&rsquo; instead of
+<p>This produces the output &lsquo;a1atextb2b&rsquo;.  With 
&lsquo;<samp>@macro</samp>&rsquo; instead of
 &lsquo;<samp>@rmacro</samp>&rsquo;, an error message is given.
 </p>
 <a name="IDX312"></a>
@@ -345,7 +345,7 @@
 conditional, cannot be invoked in the middle of a line.
 
 </li><li>
-Commas in macro arguments, even if escaped by a backslash, don't
+Commas in macro arguments, even if escaped by a backslash, don&rsquo;t
 always work.
 
 </li><li>
@@ -411,7 +411,7 @@
 some other media (movies, for example), you might like to define a
 macro <code>@moviecite{}</code> that does the same thing as an ordinary
 <code>@cite{}</code> but conveys the extra semantic information as well.
-You'd do this as follows:
+You&rsquo;d do this as follows:
 </p>
 <table><tr><td>&nbsp;</td><td><pre class="example">@alias moviecite = cite
 </pre></td></tr></table>
@@ -480,9 +480,9 @@
 </pre></td></tr></table>
 
 <p>near the beginning of a Texinfo file to define <code>@phoo</code> as an Info
-formatting command that inserts `//' before and `\\' after the argument
+formatting command that inserts &lsquo;//&rsquo; before and &lsquo;\\&rsquo; 
after the argument
 to <code>@phoo</code>.  You can then write <code>@phoo{bar}</code> wherever you
-want `//bar\\' highlighted in Info.
+want &lsquo;//bar\\&rsquo; highlighted in Info.
 </p>
 <p>Also, for TeX formatting, you could write 
 </p>

Index: Tests/texinfo_res/texinfo_2.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/texinfo_res/texinfo_2.html,v
retrieving revision 1.31
retrieving revision 1.32
diff -u -b -r1.31 -r1.32
--- Tests/texinfo_res/texinfo_2.html    5 Feb 2007 15:30:26 -0000       1.31
+++ Tests/texinfo_res/texinfo_2.html    3 Oct 2007 09:34:50 -0000       1.32
@@ -152,15 +152,15 @@
 </li><li> anything else that you think would be helpful.
 </li></ul>
 
-<p>When in doubt whether something is needed or not, include it.  It's
+<p>When in doubt whether something is needed or not, include it.  It&rsquo;s
 better to include too much than to leave out something important.
 </p>
 <a name="IDX2"></a>
 <p>Patches are most welcome; if possible, please make them with
-&lsquo;<samp>diff -c</samp>&rsquo; (see <a 
href="../diffutils/index.html#Top">(diffutils)Top</a> section `Overview' in 
<cite>Comparing and Merging Files</cite>) and include 
&lsquo;<tt>ChangeLog</tt>&rsquo; entries (see <a 
href="../emacs/Change-Log.html#Change-Log">(emacs)Change Log</a> section 
`Change Log' in <cite>The GNU Emacs Manual</cite>).
+&lsquo;<samp>diff -c</samp>&rsquo; (see <a 
href="../diffutils/index.html#Top">(diffutils)Top</a> section 
&lsquo;Overview&rsquo; in <cite>Comparing and Merging Files</cite>) and include 
&lsquo;<tt>ChangeLog</tt>&rsquo; entries (see <a 
href="../emacs/Change-Log.html#Change-Log">(emacs)Change Log</a> section 
&lsquo;Change Log&rsquo; in <cite>The GNU Emacs Manual</cite>).
 </p>
 <p>When sending patches, if possible please do not encode or split them in
-any way; it's much easier to deal with one plain text message, however
+any way; it&rsquo;s much easier to deal with one plain text message, however
 large, than many small ones.  <a href="ftp://ftp.gnu.org/gnu/sharutils/";>GNU 
shar</a> is a convenient way of packaging multiple and/or binary files
 for email.
 </p>
@@ -197,13 +197,13 @@
 </p>
 <p>To make a printed document, you process a Texinfo source file with the
 TeX typesetting program (but the Texinfo language is very different
-and much stricter than TeX's usual language, plain TeX).  This
+and much stricter than TeX&rsquo;s usual language, plain TeX).  This
 creates a DVI file that you can typeset and print as a book or report
 (see section <a href="texinfo_20.html#SEC244">Formatting and Printing 
Hardcopy</a>).
 </p>
 <a name="IDX3"></a>
 <p>To output an Info file, process your Texinfo source with the
-<code>makeinfo</code> utility or Emacs's <code>texinfo-format-buffer</code> 
command.
+<code>makeinfo</code> utility or Emacs&rsquo;s 
<code>texinfo-format-buffer</code> command.
 You can install the result in your Info tree (see section <a 
href="texinfo_21.html#SEC271">Installing an Info File</a>).
 </p>
 <p>To output an HTML file, run <code>makeinfo --html</code> on your Texinfo
@@ -266,7 +266,7 @@
 program <code>help2man</code> may be useful; it generates a traditional man
 page from the &lsquo;<samp>--help</samp>&rsquo; output of a program.  In fact, 
this is
 currently used to generate man pages for the Texinfo programs
-themselves.  It is GNU software written by Brendan O'Dea, available from
+themselves.  It is GNU software written by Brendan O&rsquo;Dea, available from
 <a href="ftp://ftp.gnu.org/gnu/help2man/";>ftp://ftp.gnu.org/gnu/help2man/</a>.
 </p>
 
@@ -306,7 +306,7 @@
 <p>See <a href="../info/index.html#Top">info: (info)Top</a>, for more 
information about using Info.
 </p>
 <p>Each node of an Info file may have any number of child nodes that
-describe subtopics of the node's topic.  The names of child
+describe subtopics of the node&rsquo;s topic.  The names of child
 nodes are listed in a <em>menu</em> within the parent node; this
 allows you to use certain Info commands to move to one of the child
 nodes.  Generally, an Info file is organized like a book.  If a node
@@ -315,25 +315,25 @@
 of subsections.
 </p>
 <p>All the children of any one parent are linked together in a
-bidirectional chain of `Next' and `Previous' pointers.  The `Next'
-pointer provides a link to the next section, and the `Previous' pointer
+bidirectional chain of &lsquo;Next&rsquo; and &lsquo;Previous&rsquo; pointers. 
 The &lsquo;Next&rsquo;
+pointer provides a link to the next section, and the &lsquo;Previous&rsquo; 
pointer
 provides a link to the previous section.  This means that all the nodes
 that are at the level of sections within a chapter are linked together.
 Normally the order in this chain is the same as the order of the
-children in the parent's menu.  Each child node records the parent node
-name as its `Up' pointer.  The last child has no `Next' pointer, and the
-first child has the parent both as its `Previous' and as its `Up'
+children in the parent&rsquo;s menu.  Each child node records the parent node
+name as its &lsquo;Up&rsquo; pointer.  The last child has no 
&lsquo;Next&rsquo; pointer, and the
+first child has the parent both as its &lsquo;Previous&rsquo; and as its 
&lsquo;Up&rsquo;
 pointer.<a name="DOCF2" href="texinfo_fot.html#FOOT2">(2)</a>
 </p>
 <p>The book-like structuring of an Info file into nodes that correspond
 to chapters, sections, and the like is a matter of convention, not a
-requirement.  The `Up', `Previous', and `Next' pointers of a node can
+requirement.  The &lsquo;Up&rsquo;, &lsquo;Previous&rsquo;, and 
&lsquo;Next&rsquo; pointers of a node can
 point to any other nodes, and a menu can contain any other nodes.
 Thus, the node structure can be any directed graph.  But it is usually
 more comprehensible to follow a structure that corresponds to the
 structure of chapters and sections in a printed book or report.
 </p>
-<p>In addition to menus and to `Next', `Previous', and `Up' pointers, Info
+<p>In addition to menus and to &lsquo;Next&rsquo;, &lsquo;Previous&rsquo;, and 
&lsquo;Up&rsquo; pointers, Info
 provides pointers of another kind, called references, that can be
 sprinkled throughout the text.  This is usually the best way to
 represent links that do not fit a hierarchical structure.
@@ -346,14 +346,14 @@
 printed output.
 </p>
 <p>Generally, you enter an Info file through a node that by convention is
-named `Top'.  This node normally contains just a brief summary of the
-file's purpose, and a large menu through which the rest of the file is
+named &lsquo;Top&rsquo;.  This node normally contains just a brief summary of 
the
+file&rsquo;s purpose, and a large menu through which the rest of the file is
 reached.  From this node, you can either traverse the file
 systematically by going from node to node, or you can go to a specific
 node listed in the main menu, or you can search the index menus and then
 go directly to the node that has the information you want.  Alternatively,
 with the standalone Info program, you can specify specific menu items on
-the command line (see <a href="../info/index.html#Top">(info)Top</a> section 
`Top' in <cite>Info</cite>).
+the command line (see <a href="../info/index.html#Top">(info)Top</a> section 
&lsquo;Top&rsquo; in <cite>Info</cite>).
 </p>
 <p>If you want to read through an Info file in sequence, as if it were a
 printed manual, you can hit &lt;SPC&gt; repeatedly, or you get the whole
@@ -361,7 +361,7 @@
 </p>
 <p>The &lsquo;<tt>dir</tt>&rsquo; file in the &lsquo;<tt>info</tt>&rsquo; 
directory serves as the
 departure point for the whole Info system.  From it, you can reach the
-`Top' nodes of each of the documents in a complete Info system.
+&lsquo;Top&rsquo; nodes of each of the documents in a complete Info system.
 </p>
 <a name="IDX12"></a>
 <p>If you wish to refer to an Info file in a URI, you can use the
@@ -372,7 +372,7 @@
 info://localhost/usr/info/emacs#Dissociated%20Press
 </pre></td></tr></table>
 
-<p>The <code>info</code> program itself does not follow URI's of any kind.
+<p>The <code>info</code> program itself does not follow URI&rsquo;s of any 
kind.
 </p>
 
 <hr size="6">
@@ -437,7 +437,7 @@
 <p>TeX is freely distributable.  It is written in a superset of Pascal
 called WEB and can be compiled either in Pascal or (by using a
 conversion program that comes with the TeX distribution) in C.
-(See <a href="../emacs/TeX-Mode.html#TeX-Mode">(emacs)TeX Mode</a> section 
`TeX Mode' in <cite>The GNU Emacs Manual</cite>, for information
+(See <a href="../emacs/TeX-Mode.html#TeX-Mode">(emacs)TeX Mode</a> section 
&lsquo;TeX Mode&rsquo; in <cite>The GNU Emacs Manual</cite>, for information
 about TeX.)
 </p>
 <p>TeX is very powerful and has a great many features.  Because a
@@ -501,7 +501,7 @@
 
 </li><li>
 Write a command such as <code>@chapter</code> at the beginning of a line
-followed by the command's arguments, in this case the chapter title, on
+followed by the command&rsquo;s arguments, in this case the chapter title, on
 the rest of the line.  (<code>@chapter</code> creates chapter titles.)
 
 </li><li>
@@ -519,7 +519,7 @@
 body-text on following lines; and write the matching <code>@end</code>
 command, <code>@end example</code> in this case, at the on a line of its own
 after the body-text. (<code>@example</code> &hellip; <code>@end example</code>
-indents and typesets body-text as an example.)  It's usually ok to
+indents and typesets body-text as an example.)  It&rsquo;s usually ok to
 indent environment commands like this, but in complicated and
 hard-to-define circumstances the extra spaces cause extra space to
 appear in the output, so beware.
@@ -573,12 +573,12 @@
 
 </li><li>
 It is customary in TeX to use doubled single-quote characters to
-begin and end quotations: <tt>``&hellip;''</tt>.  This
+begin and end quotations: <tt>&lsquo;&lsquo;&hellip;&rsquo;&rsquo;</tt>.  This
 convention should be followed in Texinfo files.  TeX converts
 two single quotes to left- and right-hand doubled
 quotation marks, 
 and Info converts doubled single-quote characters to <small>ASCII</small>
-double-quotes: <tt>``&hellip;''</tt> becomes <tt>&quot;&hellip;&quot;</tt>.
+double-quotes: <tt>&lsquo;&lsquo;&hellip;&rsquo;&rsquo;</tt> becomes 
<tt>&quot;&hellip;&quot;</tt>.
 
 </li><li>
 Use three hyphens in a row, &lsquo;<samp>---</samp>&rsquo;, for a 
dash&mdash;like this.  In
@@ -719,7 +719,7 @@
 </pre></td></tr></table>
 
 <a name="IDX19"></a>
-<p>Here's an explanation:
+<p>Here&rsquo;s an explanation:
 </p>
 <ul>
 <li>
@@ -737,7 +737,7 @@
 The <code>@settitle</code> line specifies a title for the page headers (or
 footers) of the printed manual, and the default document description for
 the &lsquo;<samp>&lt;head&gt;</samp>&rsquo; in HTML format.  Strictly 
speaking, <code>@settitle</code>
-is optional&mdash;if you don't mind your document being titled `Untitled'.
+is optional&mdash;if you don&rsquo;t mind your document being titled 
&lsquo;Untitled&rsquo;.
 
 </li><li>
 The <code>@bye</code> line at the end of the file on a line of its own tells
@@ -813,8 +813,8 @@
 copyright page appear only in the printed manual.
 </p>
 </dd>
-<dt> <span class="roman">4. `Top' Node and Master Menu</span></dt>
-<dd><p>The `Top' node starts off the online output; it does not appear in the
+<dt> <span class="roman">4. &lsquo;Top&rsquo; Node and Master Menu</span></dt>
+<dd><p>The &lsquo;Top&rsquo; node starts off the online output; it does not 
appear in the
 printed manual.  We recommend including the copying permissions here as
 well as the segments above.  And it contains at least a top-level menu
 listing the chapters, and possibly a <em>Master Menu</em> listing all the
@@ -920,9 +920,9 @@
 </pre></td></tr></table>
 
 <a name="SEC16"></a>
-<h3 class="subheading"> Part 4: `Top' Node and Master Menu </h3>
+<h3 class="subheading"> Part 4: &lsquo;Top&rsquo; Node and Master Menu </h3>
 
-<p>The `Top' node contains the master menu for the Info file.  Since a
+<p>The &lsquo;Top&rsquo; node contains the master menu for the Info file.  
Since a
 printed manual uses a table of contents rather than a menu, the master
 menu appears only in online output.  We also include the copying text
 again for the benefit of online readers.  And since the copying text
@@ -1055,7 +1055,7 @@
 <a name="IDX27"></a>
 <a name="IDX28"></a>
 <a name="IDX29"></a>
-<p>A bit of history: in the 1970's at CMU, Brian Reid developed a program
+<p>A bit of history: in the 1970&rsquo;s at CMU, Brian Reid developed a program
 and format named Scribe to mark up documents for printing.  It used the
 <code>@</code> character to introduce commands, as Texinfo does.  Much more
 consequentially, it strived to describe document contents rather than

Index: Tests/texinfo_res/texinfo_20.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/texinfo_res/texinfo_20.html,v
retrieving revision 1.31
retrieving revision 1.32
diff -u -b -r1.31 -r1.32
--- Tests/texinfo_res/texinfo_20.html   5 Feb 2007 15:30:26 -0000       1.31
+++ Tests/texinfo_res/texinfo_20.html   3 Oct 2007 09:34:50 -0000       1.32
@@ -106,7 +106,7 @@
 </td></tr>
 <tr><td align="left" valign="top"><a href="#SEC250">19.6 Formatting and 
Printing in Texinfo Mode</a></td><td>&nbsp;&nbsp;</td><td align="left" 
valign="top">       How to format and print in Texinfo mode.
 </td></tr>
-<tr><td align="left" valign="top"><a href="#SEC251">19.7 Using the Local 
Variables List</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">      
       How to print using Emacs's compile command.
+<tr><td align="left" valign="top"><a href="#SEC251">19.7 Using the Local 
Variables List</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">      
       How to print using Emacs&rsquo;s compile command.
 </td></tr>
 <tr><td align="left" valign="top"><a href="#SEC252">19.8 TeX Formatting 
Requirements Summary</a></td><td>&nbsp;&nbsp;</td><td align="left" 
valign="top">        TeX formatting requirements summary.
 </td></tr>
@@ -203,7 +203,7 @@
 <a name="IDX322"></a>
 <p>The <code>tex</code> formatting command outputs unsorted index files under
 names that obey a standard convention: the name of your main input file
-with any &lsquo;<samp>.tex</samp>&rsquo; (or similar, see <a 
href="../web2c/tex-invocation.html#tex-invocation">(web2c)tex invocation</a> 
section `tex invocation' in <cite>Web2c</cite>) extension removed, followed by 
the two letter names of indices.
+with any &lsquo;<samp>.tex</samp>&rsquo; (or similar, see <a 
href="../web2c/tex-invocation.html#tex-invocation">(web2c)tex invocation</a> 
section &lsquo;tex invocation&rsquo; in <cite>Web2c</cite>) extension removed, 
followed by the two letter names of indices.
 For example, the raw index output files for the input file
 &lsquo;<tt>foo.texinfo</tt>&rsquo; would be &lsquo;<tt>foo.cp</tt>&rsquo;, 
&lsquo;<tt>foo.vr</tt>&rsquo;, &lsquo;<tt>foo.fn</tt>&rsquo;,
 &lsquo;<tt>foo.tp</tt>&rsquo;, &lsquo;<tt>foo.pg</tt>&rsquo; and 
&lsquo;<tt>foo.ky</tt>&rsquo;.  Those are exactly the
@@ -264,7 +264,7 @@
 </li></ol>
 
 <a name="IDX325"></a>
-<p>Alternatively, it's a one-step process: run <code>texi2dvi</code>
+<p>Alternatively, it&rsquo;s a one-step process: run <code>texi2dvi</code>
 (see section <a href="#SEC247">Format with <code>texi2dvi</code></a>).
 </p>
 <p>You need not run <code>texindex</code> each time after you run 
<code>tex</code>.  If
@@ -398,7 +398,7 @@
 <p><code>lpr</code> is a standard program on Unix systems, but it is usually
 absent on MS-DOS/MS-Windows.  Some network packages come with a
 program named <code>lpr</code>, but these are usually limited to sending files
-to a print server over the network, and generally don't support the
+to a print server over the network, and generally don&rsquo;t support the
 &lsquo;<samp>-d</samp>&rsquo; option.  If you are unfortunate enough to work 
on one of these
 systems, you have several alternative ways of printing DVI files:
 </p>
@@ -418,7 +418,7 @@
 </pre></td></tr></table>
 
 </li><li> Convert the DVI file to a Postscript or PCL file and send it to your
-local printer.  See <a 
href="../dvips/dvips-invocation.html#dvips-invocation">(dvips)dvips 
invocation</a> section `dvips invocation' in <cite>Dvips</cite>, and the man
+local printer.  See <a 
href="../dvips/dvips-invocation.html#dvips-invocation">(dvips)dvips 
invocation</a> section &lsquo;dvips invocation&rsquo; in <cite>Dvips</cite>, 
and the man
 pages for <code>dvilj</code>, for detailed description of these tools.  Once
 the DVI file is converted to the format your local printer understands
 directly, just send it to the appropriate port, usually 
&lsquo;<samp>PRN</samp>&rsquo;.
@@ -583,14 +583,14 @@
 </pre></td></tr></table>
 
 <p>You can change the values of these variables with the <kbd>M-x
-edit-options</kbd> command (see <a 
href="../emacs/Edit-Options.html#Edit-Options">(emacs)Edit Options</a> section 
`Editing Variable Values' in <cite>The GNU Emacs Manual</cite>), with the 
<kbd>M-x set-variable</kbd> command
-(see <a href="../emacs/Examining.html#Examining">(emacs)Examining</a> section 
`Examining and Setting Variables' in <cite>The GNU Emacs Manual</cite>), or 
with your &lsquo;<tt>.emacs</tt>&rsquo; initialization file
-(see <a href="../emacs/Init-File.html#Init-File">(emacs)Init File</a> section 
`Init File' in <cite>The GNU Emacs Manual</cite>).
+edit-options</kbd> command (see <a 
href="../emacs/Edit-Options.html#Edit-Options">(emacs)Edit Options</a> section 
&lsquo;Editing Variable Values&rsquo; in <cite>The GNU Emacs Manual</cite>), 
with the <kbd>M-x set-variable</kbd> command
+(see <a href="../emacs/Examining.html#Examining">(emacs)Examining</a> section 
&lsquo;Examining and Setting Variables&rsquo; in <cite>The GNU Emacs 
Manual</cite>), or with your &lsquo;<tt>.emacs</tt>&rsquo; initialization file
+(see <a href="../emacs/Init-File.html#Init-File">(emacs)Init File</a> section 
&lsquo;Init File&rsquo; in <cite>The GNU Emacs Manual</cite>).
 </p>
 <a name="IDX333"></a>
 <p>Beginning with version 20, GNU Emacs offers a user-friendly interface,
 called <em>Customize</em>, for changing values of user-definable variables.
-See <a href="../emacs/Easy-Customization.html#Easy-Customization">(emacs)Easy 
Customization</a> section `Easy Customization Interface' in <cite>The GNU Emacs 
Manual</cite>, for more details about this.  The Texinfo variables can
+See <a href="../emacs/Easy-Customization.html#Easy-Customization">(emacs)Easy 
Customization</a> section &lsquo;Easy Customization Interface&rsquo; in 
<cite>The GNU Emacs Manual</cite>, for more details about this.  The Texinfo 
variables can
 be found in the &lsquo;<samp>Development/Docs/Texinfo</samp>&rsquo; group, 
once you invoke
 the <kbd>M-x customize</kbd> command.
 </p>
@@ -631,7 +631,7 @@
 </pre></td></tr></table>
 
 <p>This technique is most often used by programmers who also compile programs
-this way; see <a 
href="../emacs/Compilation.html#Compilation">(emacs)Compilation</a> section 
`Compilation' in <cite>The GNU Emacs Manual</cite>.
+this way; see <a 
href="../emacs/Compilation.html#Compilation">(emacs)Compilation</a> section 
&lsquo;Compilation&rsquo; in <cite>The GNU Emacs Manual</cite>.
 </p>
 
 <hr size="6">
@@ -665,7 +665,7 @@
 <p>The first command instructs TeX to load the macros it needs to
 process a Texinfo file and the second command opens auxiliary files.
 </p>
-<p>Every Texinfo file must end with a line that terminates TeX's
+<p>Every Texinfo file must end with a line that terminates TeX&rsquo;s
 processing and forces out unfinished pages:
 </p>
 <table><tr><td>&nbsp;</td><td><pre class="example">@bye
@@ -786,12 +786,12 @@
 </p>
 <p>These settings would cause TeX to look for &lsquo;<tt>\input</tt>&rsquo; 
file first
 in the current directory, indicated by the &lsquo;<samp>.</samp>&rsquo;, then 
in a
-hypothetical user's &lsquo;<tt>me/mylib</tt>&rsquo; directory, and finally in 
a system
+hypothetical user&rsquo;s &lsquo;<tt>me/mylib</tt>&rsquo; directory, and 
finally in a system
 directory &lsquo;<tt>/usr/lib/tex/macros</tt>&rsquo;.
 </p>
 <a name="IDX341"></a>
 <a name="IDX342"></a>
-<p>Finally, you may wish to dump a &lsquo;<tt>.fmt</tt>&rsquo; file (see <a 
href="../web2c/Memory-dumps.html#Memory-dumps">(web2c)Memory dumps</a> section 
`Memory dumps' in <cite>Web2c</cite>) so that TeX can load Texinfo faster.  (The
+<p>Finally, you may wish to dump a &lsquo;<tt>.fmt</tt>&rsquo; file (see <a 
href="../web2c/Memory-dumps.html#Memory-dumps">(web2c)Memory dumps</a> section 
&lsquo;Memory dumps&rsquo; in <cite>Web2c</cite>) so that TeX can load Texinfo 
faster.  (The
 disadvantage is that then updating &lsquo;<tt>texinfo.tex</tt>&rsquo; requires
 redumping.)  You can do this by running this command, assuming
 &lsquo;<tt>epsf.tex</tt>&rsquo; is findable by TeX:
@@ -851,7 +851,7 @@
 </p>
 <p>If you have many overfull boxes and/or an antipathy to rewriting, you
 can coerce TeX into greatly increasing the allowable interword
-spacing, thus (if you're lucky) avoiding many of the bad line breaks,
+spacing, thus (if you&rsquo;re lucky) avoiding many of the bad line breaks,
 like this:
 </p>
 <a name="IDX344"></a>
@@ -971,7 +971,7 @@
 <a name="IDX350"></a>
 <a name="IDX351"></a>
 <p>You may or may not prefer the formatting that results from the command
-<code>@afourlatex</code>.  There's also <code>@afourwide</code> for A4 paper in
+<code>@afourlatex</code>.  There&rsquo;s also <code>@afourwide</code> for A4 
paper in
 wide format.
 </p>
 <hr size="6">
@@ -1120,7 +1120,7 @@
 <code>tex</code>.  Just run &lsquo;<samp>pdftex foo.texi</samp>&rsquo; instead 
of &lsquo;<samp>tex
 foo.texi</samp>&rsquo;, or give the &lsquo;<samp>--pdf</samp>&rsquo; option to 
<code>texi2dvi</code>.
 </p>
-<p><em>PDF</em> stands for `Portable Document Format'. It was invented by
+<p><em>PDF</em> stands for &lsquo;Portable Document Format&rsquo;. It was 
invented by
 Adobe Systems some years ago for document interchange, based on their
 PostScript language.  A <a href="http://www.foolabs.com/xpdf/";>PDF reader</a>
 for the X window system is freely available, as is the
@@ -1128,7 +1128,7 @@
 &lsquo;<samp>@ifpdf</samp>&rsquo; or &lsquo;<samp>@pdf</samp>&rsquo; commands 
as with the other output
 formats.
 </p>
-<p>Despite the `portable' in the name, PDF files are nowhere near as
+<p>Despite the &lsquo;portable&rsquo; in the name, PDF files are nowhere near 
as
 portable in practice as the plain ASCII formats (Info, HTML) that
 Texinfo supports (DVI portability is arguable).  They also tend to be
 much larger and do not support the bitmap fonts used by TeX (by

Index: Tests/texinfo_res/texinfo_21.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/texinfo_res/texinfo_21.html,v
retrieving revision 1.30
retrieving revision 1.31
diff -u -b -r1.30 -r1.31
--- Tests/texinfo_res/texinfo_21.html   5 Feb 2007 15:30:26 -0000       1.30
+++ Tests/texinfo_res/texinfo_21.html   3 Oct 2007 09:34:50 -0000       1.31
@@ -536,33 +536,33 @@
 </p>
 <ol>
 <li>
-If a `Next', `Previous', or `Up' node reference is a reference to a
+If a &lsquo;Next&rsquo;, &lsquo;Previous&rsquo;, or &lsquo;Up&rsquo; node 
reference is a reference to a
 node in the current file and is not an external reference such as to
 &lsquo;<tt>(dir)</tt>&rsquo;, then the referenced node must exist.
 
 </li><li>
-In every node, if the `Previous' node is different from the `Up' node,
-then the node pointed to by the `Previous' field must have a `Next'
+In every node, if the &lsquo;Previous&rsquo; node is different from the 
&lsquo;Up&rsquo; node,
+then the node pointed to by the &lsquo;Previous&rsquo; field must have a 
&lsquo;Next&rsquo;
 field which points back to this node.
 
 </li><li>
-Every node except the `Top' node must have an `Up' pointer.
+Every node except the &lsquo;Top&rsquo; node must have an &lsquo;Up&rsquo; 
pointer.
 
 </li><li>
-The node referenced by an `Up' pointer must itself reference the current
-node through a menu item, unless the node referenced by `Up'
-has the form `(<var>file</var>)'.
+The node referenced by an &lsquo;Up&rsquo; pointer must itself reference the 
current
+node through a menu item, unless the node referenced by &lsquo;Up&rsquo;
+has the form &lsquo;(<var>file</var>)&rsquo;.
 
 </li><li>
-If the `Next' reference of a node is not the same as the `Next' reference
-of the `Up' reference, then the node referenced by the `Next' pointer
-must have a `Previous' pointer that points back to the current node.
+If the &lsquo;Next&rsquo; reference of a node is not the same as the 
&lsquo;Next&rsquo; reference
+of the &lsquo;Up&rsquo; reference, then the node referenced by the 
&lsquo;Next&rsquo; pointer
+must have a &lsquo;Previous&rsquo; pointer that points back to the current 
node.
 This rule allows the last node in a section to point to the first node
 of the next chapter.
 
 </li><li>
-Every node except `Top' should be referenced by at least one other node,
-either via the `Previous' or `Next' links, or via a menu or a
+Every node except &lsquo;Top&rsquo; should be referenced by at least one other 
node,
+either via the &lsquo;Previous&rsquo; or &lsquo;Next&rsquo; links, or via a 
menu or a
 cross-reference.
 </li></ol>
 
@@ -666,7 +666,7 @@
 <p>You can parse the error messages by typing <kbd>C-x `</kbd>
 (<code>next-error</code>).  This causes Emacs to go to and position the
 cursor on the line in the Texinfo source that <code>makeinfo</code> thinks
-caused the error.  See <a 
href="../emacs/Compilation.html#Compilation">(emacs)Compilation</a> section 
`Running <code>make</code> or Compilers Generally' in <cite>The GNU Emacs 
Manual</cite>, for more
+caused the error.  See <a 
href="../emacs/Compilation.html#Compilation">(emacs)Compilation</a> section 
&lsquo;Running <code>make</code> or Compilers Generally&rsquo; in <cite>The GNU 
Emacs Manual</cite>, for more
 information about using the <code>next-error</code> command.
 </p>
 <p>In addition, you can kill the shell in which the <code>makeinfo</code>
@@ -705,9 +705,9 @@
 </pre></td></tr></table>
 
 <p>For more information, see<br>
-<a href="../emacs/Edit-Options.html#Edit-Options">(emacs)Edit Options</a> 
section `Editing Variable Values' in <cite>The GNU Emacs Manual</cite>,<br>
-<a href="../emacs/Examining.html#Examining">(emacs)Examining</a> section 
`Examining and Setting Variables' in <cite>The GNU Emacs Manual</cite>,<br>
-<a href="../emacs/Init-File.html#Init-File">(emacs)Init File</a> section `Init 
File' in <cite>The GNU Emacs Manual</cite>, and<br>
+<a href="../emacs/Edit-Options.html#Edit-Options">(emacs)Edit Options</a> 
section &lsquo;Editing Variable Values&rsquo; in <cite>The GNU Emacs 
Manual</cite>,<br>
+<a href="../emacs/Examining.html#Examining">(emacs)Examining</a> section 
&lsquo;Examining and Setting Variables&rsquo; in <cite>The GNU Emacs 
Manual</cite>,<br>
+<a href="../emacs/Init-File.html#Init-File">(emacs)Init File</a> section 
&lsquo;Init File&rsquo; in <cite>The GNU Emacs Manual</cite>, and<br>
 <a href="#SEC264">Options for <code>makeinfo</code></a>.
 </p>
 <hr size="6">
@@ -787,7 +787,7 @@
 
 <p>You can format Texinfo files for Info using 
<code>batch-texinfo-format</code>
 and Emacs Batch mode.  You can run Emacs in Batch mode from any shell,
-including a shell inside of Emacs.  (See <a 
href="../emacs/Command-Switches.html#Command-Switches">(emacs)Command 
Switches</a> section `Command Line Switches and Arguments' in <cite>The GNU 
Emacs Manual</cite>.)
+including a shell inside of Emacs.  (See <a 
href="../emacs/Command-Switches.html#Command-Switches">(emacs)Command 
Switches</a> section &lsquo;Command Line Switches and Arguments&rsquo; in 
<cite>The GNU Emacs Manual</cite>.)
 </p>
 <p>Here is a shell command to format all the files that end in
 &lsquo;<tt>.texinfo</tt>&rsquo; in the current directory:
@@ -938,7 +938,7 @@
 for any reason, then &lsquo;<samp>.html</samp>&rsquo; is appended to the 
directory name, as
 in &lsquo;<samp>emacs.html</samp>&rsquo; (this is necessary because sometimes 
the info file
 is named without an extension, e.g., &lsquo;<samp>texinfo</samp>&rsquo;).  If 
the
-&lsquo;<samp><var>name</var>.html</samp>&rsquo; directory can't be created 
either,
+&lsquo;<samp><var>name</var>.html</samp>&rsquo; directory can&rsquo;t be 
created either,
 <code>makeinfo</code> gives up.  In any case, the top-level output file within
 the directory is always named &lsquo;<samp>index.html</samp>&rsquo;.
 </p>
@@ -1055,17 +1055,17 @@
 &hellip;
 </pre></td></tr></table>
 
-<p>Each of these menu entries points to the `Top' node of the Info file
+<p>Each of these menu entries points to the &lsquo;Top&rsquo; node of the Info 
file
 that is named in parentheses.  (The menu entry does not need to
-specify the `Top' node, since Info goes to the `Top' node if no node
+specify the &lsquo;Top&rsquo; node, since Info goes to the &lsquo;Top&rsquo; 
node if no node
 name is mentioned.  See section <a href="texinfo_8.html#SEC103">Nodes in Other 
Info Files</a>.)
 </p>
-<p>Thus, the &lsquo;<samp>Info</samp>&rsquo; entry points to the `Top' node of 
the
-&lsquo;<tt>info</tt>&rsquo; file and the &lsquo;<samp>Emacs</samp>&rsquo; 
entry points to the `Top' node
+<p>Thus, the &lsquo;<samp>Info</samp>&rsquo; entry points to the 
&lsquo;Top&rsquo; node of the
+&lsquo;<tt>info</tt>&rsquo; file and the &lsquo;<samp>Emacs</samp>&rsquo; 
entry points to the &lsquo;Top&rsquo; node
 of the &lsquo;<tt>emacs</tt>&rsquo; file.
 </p>
-<p>In each of the Info files, the `Up' pointer of the `Top' node refers
-back to the <code>dir</code> file.  For example, the line for the `Top'
+<p>In each of the Info files, the &lsquo;Up&rsquo; pointer of the 
&lsquo;Top&rsquo; node refers
+back to the <code>dir</code> file.  For example, the line for the 
&lsquo;Top&rsquo;
 node of the Emacs manual looks like this in Info:
 </p>
 <table><tr><td>&nbsp;</td><td><pre class="example">File: emacs  Node: Top, Up: 
(DIR), Next: Distrib
@@ -1189,7 +1189,7 @@
 &lsquo;<tt>/home/bob/info/info-test</tt>&rsquo; file as a menu entry in the
 &lsquo;<tt>/home/bob/info/dir</tt>&rsquo; file.  Emacs does the merging only 
when
 <kbd>M-x info</kbd> is first run, so if you want to set
-<code>Info-directory-list</code> in an Emacs session where you've already run
+<code>Info-directory-list</code> in an Emacs session where you&rsquo;ve 
already run
 <code>info</code>, you must <code>(setq Info-dir-contents nil)</code> to force 
Emacs
 to recompose the &lsquo;<tt>dir</tt>&rsquo; file.
 </p>
@@ -1230,7 +1230,7 @@
 </li></ul>
 
 <p>The &lsquo;<samp>.</samp>&rsquo; indicates the current directory as usual.  
Emacs uses the
-<code>INFOPATH</code> environment variable to initialize the value of Emacs's
+<code>INFOPATH</code> environment variable to initialize the value of 
Emacs&rsquo;s
 own <code>Info-directory-list</code> variable.  The stand-alone Info reader
 merges any files named &lsquo;<tt>dir</tt>&rsquo; in any directory listed in 
the
 <code>INFOPATH</code> variable into a single menu presented to you in the node
@@ -1252,7 +1252,7 @@
 </p>
 <a name="IDX417"></a>
 <p>When you create your own &lsquo;<tt>dir</tt>&rsquo; file for use with
-<code>Info-directory-list</code> or <code>INFOPATH</code>, it's easiest to 
start by
+<code>Info-directory-list</code> or <code>INFOPATH</code>, it&rsquo;s easiest 
to start by
 copying an existing &lsquo;<tt>dir</tt>&rsquo; file and replace all the text 
after the
 &lsquo;<samp>* Menu:</samp>&rsquo; with your desired entries.  That way, the 
punctuation and
 special CTRL-_ characters that Info needs will be present.
@@ -1302,7 +1302,7 @@
 @end direntry
 </pre></td></tr></table>
 
-<p>Here's what this produces in the Info file:
+<p>Here&rsquo;s what this produces in the Info file:
 </p>
 <table><tr><td>&nbsp;</td><td><pre class="smallexample">INFO-DIR-SECTION 
Texinfo documentation system
 START-INFO-DIR-ENTRY
@@ -1321,7 +1321,7 @@
 will not notice them.
 </p>
 <p>If you use <code>@dircategory</code> more than once in the Texinfo source,
-each usage specifies the `current' category; any subsequent
+each usage specifies the &lsquo;current&rsquo; category; any subsequent
 <code>@direntry</code> commands will add to that category.  
 </p>
 <p>Here are some recommended <code>@dircategory</code> categories:
@@ -1335,8 +1335,8 @@
 Individual utilities
 </pre></td></tr></table>
 
-<p>The idea is to include the `Invoking' node for every program installed
-by a package under `Individual utilities', and an entry for the manual
+<p>The idea is to include the &lsquo;Invoking&rsquo; node for every program 
installed
+by a package under &lsquo;Individual utilities&rsquo;, and an entry for the 
manual
 as a whole in the appropriate other category.
 </p>
 
@@ -1364,7 +1364,7 @@
 
 <p><code>install-info</code> inserts menu entries from an Info file into the
 top-level &lsquo;<tt>dir</tt>&rsquo; file in the Info system (see the previous 
sections
-for an explanation of how the &lsquo;<tt>dir</tt>&rsquo; file works).  It's 
most often
+for an explanation of how the &lsquo;<tt>dir</tt>&rsquo; file works).  
It&rsquo;s most often
 run as part of software installation, or when constructing a 
&lsquo;<tt>dir</tt>&rsquo; file
 for all manuals on a system.  Synopsis:
 </p>
@@ -1382,7 +1382,7 @@
 </p>
 <a name="IDX421"></a>
 <a name="IDX422"></a>
-<p>If any input file is compressed with <code>gzip</code> (see <a 
href="../gzip/Invoking-gzip.html#Invoking-gzip">(gzip)Invoking gzip</a> section 
`Invoking gzip' in <cite>Gzip</cite>), <code>install-info</code> automatically 
uncompresses it
+<p>If any input file is compressed with <code>gzip</code> (see <a 
href="../gzip/Invoking-gzip.html#Invoking-gzip">(gzip)Invoking gzip</a> section 
&lsquo;Invoking gzip&rsquo; in <cite>Gzip</cite>), <code>install-info</code> 
automatically uncompresses it
 for reading.  And if <var>dir-file</var> is compressed, 
<code>install-info</code>
 also automatically leaves it compressed after writing any changes.
 If <var>dir-file</var> itself does not exist, <code>install-info</code> tries 
to
@@ -1395,7 +1395,7 @@
 <dd><a name="IDX423"></a>
 <p>Delete the entries in <var>info-file</var> from <var>dir-file</var>.  The 
file
 name in the entry in <var>dir-file</var> must be <var>info-file</var> (except 
for
-an optional &lsquo;<samp>.info</samp>&rsquo; in either one).  Don't insert any 
new entries.
+an optional &lsquo;<samp>.info</samp>&rsquo; in either one).  Don&rsquo;t 
insert any new entries.
 </p>
 </dd>
 <dt> <code>--dir-file=<var>name</var></code></dt>
@@ -1413,7 +1413,7 @@
 <p>Insert <var>text</var> as an Info directory entry; <var>text</var> should 
have the
 form of an Info menu item line plus zero or more extra lines starting
 with whitespace.  If you specify more than one entry, they are all
-added.  If you don't specify any entries, they are determined from
+added.  If you don&rsquo;t specify any entries, they are determined from
 information in the Info file itself.
 </p>
 </dd>
@@ -1463,9 +1463,9 @@
 <dt> <code>-s <var>sec</var></code></dt>
 <dd><a name="IDX438"></a>
 <a name="IDX439"></a>
-<p>Put this file's entries in section <var>sec</var> of the directory.  If you
+<p>Put this file&rsquo;s entries in section <var>sec</var> of the directory.  
If you
 specify more than one section, all the entries are added in each of the
-sections.  If you don't specify any sections, they are determined from
+sections.  If you don&rsquo;t specify any sections, they are determined from
 information in the Info file itself.
 </p>
 </dd>

Index: Tests/texinfo_res/texinfo_22.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/texinfo_res/texinfo_22.html,v
retrieving revision 1.26
retrieving revision 1.27
diff -u -b -r1.26 -r1.27
--- Tests/texinfo_res/texinfo_22.html   30 Sep 2007 12:47:40 -0000      1.26
+++ Tests/texinfo_res/texinfo_22.html   3 Oct 2007 09:34:50 -0000       1.27
@@ -178,7 +178,7 @@
 </dd>
 <dt> <code>@acronym{<var>abbrev</var>}</code></dt>
 <dd><p>Tag <var>abbrev</var> as an acronym, that is, an abbreviation written 
in all
-capital letters, such as `NASA'.  See section <a 
href="texinfo_10.html#SEC134"><code>acronym</code></a>.
+capital letters, such as &lsquo;NASA&rsquo;.  See section <a 
href="texinfo_10.html#SEC134"><code>acronym</code></a>.
 </p>
 </dd>
 <dt> <code>@AE{}</code></dt>
@@ -230,12 +230,12 @@
 <dt> <code>@appendixsubsubsec <var>title</var></code></dt>
 <dd><p>Begin an appendix subsubsection within an appendix subsection.  The
 title appears in the table of contents of a printed manual.  In Info,
-the title is underlined with periods.  See section <a 
href="texinfo_6.html#SEC83">The `subsub' Commands</a>.
+the title is underlined with periods.  See section <a 
href="texinfo_6.html#SEC83">The &lsquo;subsub&rsquo; Commands</a>.
 </p>
 </dd>
 <dt> <code>@asis</code></dt>
 <dd><p>Used following <code>@table</code>, <code>@ftable</code>, and 
<code>@vtable</code> to
-print the table's first column without highlighting (&ldquo;as is&rdquo;).
+print the table&rsquo;s first column without highlighting (&ldquo;as 
is&rdquo;).
 See section <a href="texinfo_12.html#SEC159">Making a Two-column Table</a>.
 </p>
 </dd>
@@ -501,7 +501,7 @@
 </p>
 </dd>
 <dt> <code>@dircategory <var>dirpart</var></code></dt>
-<dd><p>Specify a part of the Info directory menu where this file's entry should
+<dd><p>Specify a part of the Info directory menu where this file&rsquo;s entry 
should
 go.  See section <a href="texinfo_21.html#SEC275">Installing Info Directory 
Files</a>.
 </p>
 </dd>
@@ -646,12 +646,12 @@
 </dd>
 <dt> <code>@footnote{<var>text-of-footnote</var>}</code></dt>
 <dd><p>Enter a footnote.  Footnote text is printed at the bottom of the page
-by TeX; Info may format in either `End' node or `Separate' node style.
+by TeX; Info may format in either &lsquo;End&rsquo; node or 
&lsquo;Separate&rsquo; node style.
 See section <a href="texinfo_14.html#SEC201">Footnotes</a>.
 </p>
 </dd>
 <dt> <code>@footnotestyle <var>style</var></code></dt>
-<dd><p>Specify an Info file's footnote style, either 
&lsquo;<samp>end</samp>&rsquo; for the end
+<dd><p>Specify an Info file&rsquo;s footnote style, either 
&lsquo;<samp>end</samp>&rsquo; for the end
 node style or &lsquo;<samp>separate</samp>&rsquo; for the separate node style.
 See section <a href="texinfo_14.html#SEC201">Footnotes</a>.
 </p>
@@ -856,7 +856,7 @@
 </p>
 </dd>
 <dt> <code>@minus{}</code></dt>
-<dd><p>Generate a minus sign, `-'.  See section <a 
href="texinfo_14.html#SEC191"><code>@minus</code></a>.
+<dd><p>Generate a minus sign, &lsquo;-&rsquo;.  See section <a 
href="texinfo_14.html#SEC191"><code>@minus</code></a>.
 </p>
 </dd>
 <dt> <code>@multitable <var>column-width-spec</var></code></dt>
@@ -947,7 +947,7 @@
 </p>
 </dd>
 <dt> <code>@pxref{<var>node-name</var>, [<var>entry</var>], 
[<var>topic-or-title</var>], [<var>info-file</var>], 
[<var>manual</var>]}</code></dt>
-<dd><p>Make a reference that starts with a lower case `see' in a printed
+<dd><p>Make a reference that starts with a lower case &lsquo;see&rsquo; in a 
printed
 manual.  Use within parentheses only.  Do not follow command with a
 punctuation mark&mdash;the Info formatting commands automatically insert
 terminating punctuation as needed.  Only the first argument is mandatory.
@@ -976,7 +976,7 @@
 </dd>
 <dt> <code>@ref{<var>node-name</var>, [<var>entry</var>], 
[<var>topic-or-title</var>], [<var>info-file</var>], 
[<var>manual</var>]}</code></dt>
 <dd><p>Make a reference.  In a printed manual, the reference does not start
-with a `See'.  Follow command with a punctuation mark.  Only the first
+with a &lsquo;See&rsquo;.  Follow command with a punctuation mark.  Only the 
first
 argument is mandatory.  See section <a 
href="texinfo_9.html#SEC115"><code>@ref</code></a>.
 </p>
 </dd>
@@ -1118,14 +1118,14 @@
 <dt> <code>@subsubheading <var>title</var></code></dt>
 <dd><p>Print an unnumbered subsubsection-like heading in the text, but not in
 the table of contents of a printed manual.  In Info, the title is
-underlined with periods.  See section <a href="texinfo_6.html#SEC83">The 
`subsub' Commands</a>.
+underlined with periods.  See section <a href="texinfo_6.html#SEC83">The 
&lsquo;subsub&rsquo; Commands</a>.
 </p>
 </dd>
 <dt> <code>@subsubsection <var>title</var></code></dt>
 <dd><p>Begin a subsubsection within a subsection.  In a printed manual,
 the subsubsection title is numbered and appears in the table of
 contents.  In Info, the title is underlined with periods.
-See section <a href="texinfo_6.html#SEC83">The `subsub' Commands</a>.
+See section <a href="texinfo_6.html#SEC83">The &lsquo;subsub&rsquo; 
Commands</a>.
 </p>
 </dd>
 <dt> <code>@subtitle <var>title</var></code></dt>
@@ -1185,14 +1185,14 @@
 <dt> <code>@thispage</code></dt>
 <dt> <code>@thistitle</code></dt>
 <dd><p>Only allowed in a heading or footing.  Stands for the number and name of
-the current chapter (in the format `Chapter 1: Title'), the chapter name
+the current chapter (in the format &lsquo;Chapter 1: Title&rsquo;), the 
chapter name
 only, the filename, the current page number, and the title of the
 document, respectively.  See section <a href="texinfo_26.html#SEC307">How to 
Make Your Own Headings</a>.
 </p>
 </dd>
 <dt> <code>@tieaccent{<var>cc</var>}</code></dt>
 <dd><p>Generate a tie-after accent over the next two characters <var>cc</var>, 
as in
-`oo['.  See section <a href="texinfo_14.html#SEC183">Inserting Accents</a>.
+&lsquo;oo[&rsquo;.  See section <a href="texinfo_14.html#SEC183">Inserting 
Accents</a>.
 </p>
 </dd>
 <dt> <code>@tindex <var>entry</var></code></dt>
@@ -1219,14 +1219,14 @@
 </p>
 </dd>
 <dt> <code>@today{}</code></dt>
-<dd><p>Insert the current date, in `1 Jan 1900' style.  See section <a 
href="texinfo_26.html#SEC307">How to Make Your Own Headings</a>.
+<dd><p>Insert the current date, in &lsquo;1 Jan 1900&rsquo; style.  See 
section <a href="texinfo_26.html#SEC307">How to Make Your Own Headings</a>.
 </p>
 </dd>
 <dt> <code>@top <var>title</var></code></dt>
 <dd><p>In a Texinfo file to be formatted with <code>makeinfo</code>, identify 
the
 topmost <code>@node</code> in the file, which must be written on the line
 immediately preceding the <code>@top</code> command.  Used for
-<code>makeinfo</code>'s node pointer insertion feature.  The title is
+<code>makeinfo</code>&rsquo;s node pointer insertion feature.  The title is
 underlined with asterisks.  Both the <code>@node</code> line and the 
<code>@top</code>
 line normally should be enclosed by <code>@ifnottex</code> and <code>@end
 ifnottex</code>.  In TeX and <code>texinfo-format-buffer</code>, the 
<code>@top</code>
@@ -1266,7 +1266,7 @@
 <dd><p>In a printed manual, begin an unnumbered subsubsection within a
 chapter.  The title appears in the table of contents of a printed
 manual.  In Info, the title is underlined with periods.
-See section <a href="texinfo_6.html#SEC83">The `subsub' Commands</a>.
+See section <a href="texinfo_6.html#SEC83">The &lsquo;subsub&rsquo; 
Commands</a>.
 </p>
 </dd>
 <dt> <code>@uref{<var>url</var>[, <var>displayed-text</var>][, 
<var>replacement</var>}</code></dt>
@@ -1337,7 +1337,7 @@
 </p>
 </dd>
 <dt> <code>@xref{<var>node-name</var>, [<var>entry</var>], 
[<var>topic-or-title</var>], [<var>info-file</var>], 
[<var>manual</var>]}</code></dt>
-<dd><p>Make a reference that starts with `See' in a printed manual.  Follow
+<dd><p>Make a reference that starts with &lsquo;See&rsquo; in a printed 
manual.  Follow
 command with a punctuation mark.  Only the first argument is
 mandatory.  See section <a href="texinfo_9.html#SEC108"><code>@xref</code></a>.
 </p></dd>

Index: Tests/texinfo_res/texinfo_23.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/texinfo_res/texinfo_23.html,v
retrieving revision 1.27
retrieving revision 1.28
diff -u -b -r1.27 -r1.28
--- Tests/texinfo_res/texinfo_23.html   5 Feb 2007 15:30:26 -0000       1.27
+++ Tests/texinfo_res/texinfo_23.html   3 Oct 2007 09:34:51 -0000       1.28
@@ -283,7 +283,7 @@
 
 <p>so it looks like this:
 </p>
-<blockquote><p>`C-x v' `M-x vc-next-action' Perform the next logical operation 
on the
+<blockquote><p>&lsquo;C-x v&rsquo; &lsquo;M-x vc-next-action&rsquo; Perform 
the next logical operation on the
 version-controlled file corresponding to the current buffer.
 </p></blockquote>
 
@@ -375,14 +375,14 @@
 sections are all different, they are difficult for users to find.
 </p>
 <p>So, there is a convention to name such sections with a phrase beginning
-with the word `Invoking', as in `Invoking Emacs'; this way, users can
+with the word &lsquo;Invoking&rsquo;, as in &lsquo;Invoking Emacs&rsquo;; this 
way, users can
 find the section easily.
 </p>
 
 <a name="SEC291"></a>
 <h4 class="subsubheading"> ANSI C Syntax </h4>
 
-<p>When you use <code>@example</code> to describe a C function's calling
+<p>When you use <code>@example</code> to describe a C function&rsquo;s calling
 conventions, use the ANSI C syntax, like this:
 </p>
 <table><tr><td>&nbsp;</td><td><pre class="example">void dld_init (char 
address@hidden);
@@ -428,10 +428,10 @@
 a unified control mode like this possible).
 </p></blockquote>
 
-<p>And in this example, you should specify what `it' refers to:
+<p>And in this example, you should specify what &lsquo;it&rsquo; refers to:
 </p>
 <blockquote><p>If you are working with other people, it assists in coordinating
-everyone's changes so they do not step on each other.
+everyone&rsquo;s changes so they do not step on each other.
 </p></blockquote>
 
 <a name="SEC293"></a>
@@ -439,8 +439,8 @@
 
 <ul>
 <li>
-Pronounce TeX as if the &lsquo;<samp>X</samp>&rsquo; were a Greek `chi', as 
the last
-sound in the name `Bach'.  But pronounce Texinfo as in `speck':
+Pronounce TeX as if the &lsquo;<samp>X</samp>&rsquo; were a Greek 
&lsquo;chi&rsquo;, as the last
+sound in the name &lsquo;Bach&rsquo;.  But pronounce Texinfo as in 
&lsquo;speck&rsquo;:
 &ldquo;teckinfo&rdquo;.
 
 </li><li>

Index: Tests/texinfo_res/texinfo_24.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/texinfo_res/texinfo_24.html,v
retrieving revision 1.78
retrieving revision 1.79
diff -u -b -r1.78 -r1.79
--- Tests/texinfo_res/texinfo_24.html   5 Feb 2007 15:30:26 -0000       1.78
+++ Tests/texinfo_res/texinfo_24.html   3 Oct 2007 09:34:51 -0000       1.79
@@ -211,10 +211,10 @@
 used in GNU manuals.
 </p>
 <p>As well as the legal texts, it also serves as a practical example of how
-many elements in a GNU system can affect the manual.  If you're not
-familiar with all these different elements, don't worry.  They're not
+many elements in a GNU system can affect the manual.  If you&rsquo;re not
+familiar with all these different elements, don&rsquo;t worry.  They&rsquo;re 
not
 required and a perfectly good manual can be written without them.
-They're included here nonetheless because many manuals do (or could)
+They&rsquo;re included here nonetheless because many manuals do (or could)
 benefit from them.
 </p>
 <p>See section <a href="texinfo_2.html#SEC12">A Short Sample Texinfo File</a>, 
for a minimal example of a Texinfo file.
@@ -228,7 +228,7 @@
 <a name="IDX446"></a>
 <a name="IDX447"></a>
 <a name="IDX448"></a>
-The &lsquo;<samp>Id: texinfo.txi,v 1.2 2003/02/24 18:17:06 pertusus Exp 
$</samp>&rsquo; comment is for CVS (see <a 
href="../cvs/index.html#Top">(cvs)Top</a> section `Overview' in 
<cite>Concurrent Versions System</cite>) or RCS (see rcsintro(1)) version 
control
+The &lsquo;<samp>Id: texinfo.txi,v 1.2 2003/02/24 18:17:06 pertusus Exp 
$</samp>&rsquo; comment is for CVS (see <a 
href="../cvs/index.html#Top">(cvs)Top</a> section &lsquo;Overview&rsquo; in 
<cite>Concurrent Versions System</cite>) or RCS (see rcsintro(1)) version 
control
 systems, which expand it into a string such as:
 <table><tr><td>&nbsp;</td><td><pre class="example">Id: texinfo.txi,v 1.2 
2003/02/24 18:17:06 pertusus Exp $
 </pre></td></tr></table>
@@ -237,8 +237,8 @@
 </li><li>
 <a name="IDX449"></a>
 The &lsquo;<tt>version.texi</tt>&rsquo; in the <code>@include</code> command 
is maintained
-automatically by Automake (see <a 
href="../automake/index.html#Top">(automake)Top</a> section `Introduction' in 
<cite>GNU Automake</cite>).  It sets the &lsquo;<samp>VERSION</samp>&rsquo; and 
&lsquo;<samp>UPDATED</samp>&rsquo; values used
-elsewhere.  If your distribution doesn't use Automake, you can mimic
+automatically by Automake (see <a 
href="../automake/index.html#Top">(automake)Top</a> section 
&lsquo;Introduction&rsquo; in <cite>GNU Automake</cite>).  It sets the 
&lsquo;<samp>VERSION</samp>&rsquo; and &lsquo;<samp>UPDATED</samp>&rsquo; 
values used
+elsewhere.  If your distribution doesn&rsquo;t use Automake, you can mimic
 these or equivalent settings.
 
 </li><li>
@@ -251,8 +251,8 @@
 category names.
 
 </li><li>
-The `Invoking' node is a GNU standard to help users find the basic
-information about command-line usage of a given program.  See <a 
href="../standards/Manual-Structure-Details.html#Manual-Structure-Details">(standards)Manual
 Structure Details</a> section `Manual Structure Details' in <cite>GNU Coding 
Standards</cite>.
+The &lsquo;Invoking&rsquo; node is a GNU standard to help users find the basic
+information about command-line usage of a given program.  See <a 
href="../standards/Manual-Structure-Details.html#Manual-Structure-Details">(standards)Manual
 Structure Details</a> section &lsquo;Manual Structure Details&rsquo; in 
<cite>GNU Coding Standards</cite>.
 
 </li><li>
 It is best to include the entire GNU Free Documentation License in a GNU
@@ -267,7 +267,7 @@
 </p>
 </li><li>
 If your manual has invariant sections (again, see the license itself for
-details), then don't forget to include them.
+details), then don&rsquo;t forget to include them.
 </li></ul>
 
 <p>Here is the sample document:

Index: Tests/texinfo_res/texinfo_25.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/texinfo_res/texinfo_25.html,v
retrieving revision 1.30
retrieving revision 1.31
diff -u -b -r1.30 -r1.31
--- Tests/texinfo_res/texinfo_25.html   5 Feb 2007 15:30:26 -0000       1.30
+++ Tests/texinfo_res/texinfo_25.html   3 Oct 2007 09:34:51 -0000       1.31
@@ -154,11 +154,11 @@
 and updating commands to create the node pointers and menus within the
 included file.  However, the simple Emacs node and menu creating and
 updating commands do not work with multiple Texinfo files.  Thus you
-cannot use these commands to fill in the `Next', `Previous', and `Up'
+cannot use these commands to fill in the &lsquo;Next&rsquo;, 
&lsquo;Previous&rsquo;, and &lsquo;Up&rsquo;
 pointers of the <code>@node</code> line that begins the included file.  Also,
 you cannot use the regular commands to create a master menu for the
-whole file.  Either you must insert the menus and the `Next',
-`Previous', and `Up' pointers by hand, or you must use the GNU Emacs
+whole file.  Either you must insert the menus and the &lsquo;Next&rsquo;,
+&lsquo;Previous&rsquo;, and &lsquo;Up&rsquo; pointers by hand, or you must use 
the GNU Emacs
 Texinfo mode command, <code>texinfo-multiple-files-update</code>, that is
 designed for <code>@include</code> files.
 </p>
@@ -184,7 +184,7 @@
 <h2 class="section"> D.2 <code>texinfo-multiple-files-update</code> </h2>
 
 <p>GNU Emacs Texinfo mode provides the 
<code>texinfo-multiple-files-update</code>
-command.  This command creates or updates `Next', `Previous', and `Up'
+command.  This command creates or updates &lsquo;Next&rsquo;, 
&lsquo;Previous&rsquo;, and &lsquo;Up&rsquo;
 pointers of included files as well as those in the outer or overall
 Texinfo file, and it creates or updates a main menu in the outer file.
 Depending whether you call it with optional arguments, the command
@@ -197,12 +197,12 @@
 </p>
 <ul class="toc">
 <li>-
-Create or update the `Next', `Previous', and `Up' pointers of the
+Create or update the &lsquo;Next&rsquo;, &lsquo;Previous&rsquo;, and 
&lsquo;Up&rsquo; pointers of the
 first <code>@node</code> line in each file included in an outer or overall
 Texinfo file.
 
 </li><li>-
-Create or update the `Top' level node pointers of the outer or
+Create or update the &lsquo;Top&rsquo; level node pointers of the outer or
 overall file.
 
 </li><li>-
@@ -219,7 +219,7 @@
 included file.
 
 </li><li>-
-Create or update the `Top' level node pointers of the outer file.
+Create or update the &lsquo;Top&rsquo; level node pointers of the outer file.
 
 </li><li>-
 Create and insert a master menu in the outer file.  The master menu
@@ -232,7 +232,7 @@
 </p>
 <ul class="toc">
 <li>-
-Create or update <strong>all</strong> the `Next', `Previous', and `Up' pointers
+Create or update <strong>all</strong> the &lsquo;Next&rsquo;, 
&lsquo;Previous&rsquo;, and &lsquo;Up&rsquo; pointers
 of all the included files.
 
 </li><li>-
@@ -240,7 +240,7 @@
 files.
 
 </li><li>-
-Create or update the `Top' level node pointers of the outer or
+Create or update the &lsquo;Top&rsquo; level node pointers of the outer or
 overall file.
 
 </li><li>-
@@ -296,8 +296,8 @@
 <code>@unnumbered</code> node.  Thus, normally, each included file contains
 one, and only one, chapter or equivalent-level node.
 </p>
-<p>The outer file should contain only <em>one</em> node, the `Top' node.  It
-should <em>not</em> contain any nodes besides the single `Top' node.  The
+<p>The outer file should contain only <em>one</em> node, the &lsquo;Top&rsquo; 
node.  It
+should <em>not</em> contain any nodes besides the single &lsquo;Top&rsquo; 
node.  The
 <code>texinfo-multiple-files-update</code> command will not process
 them.
 </p>
@@ -414,7 +414,7 @@
 <p>Include files were designed primarily as a way to create a single,
 large printed manual out of several smaller Info files.  In a printed
 manual, all the references were within the same document, so TeX
-could automatically determine the references' page numbers.  The Info
+could automatically determine the references&rsquo; page numbers.  The Info
 formatting commands used include files only for creating joint
 indices; each of the individual Texinfo files had to be formatted for
 Info individually.  (Each, therefore, required its own

Index: Tests/texinfo_res/texinfo_26.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/texinfo_res/texinfo_26.html,v
retrieving revision 1.30
retrieving revision 1.31
diff -u -b -r1.30 -r1.31
--- Tests/texinfo_res/texinfo_26.html   5 Feb 2007 15:30:26 -0000       1.30
+++ Tests/texinfo_res/texinfo_26.html   3 Oct 2007 09:34:51 -0000       1.31
@@ -337,7 +337,7 @@
 <dt> <code>@everyheading <var>left</var> @| <var>center</var> @| 
<var>right</var></code></dt>
 <dt> <code>@everyfooting <var>left</var> @| <var>center</var> @| 
<var>right</var></code></dt>
 <dd>
-<p>The `every' commands specify the format for both even- and odd-numbered
+<p>The &lsquo;every&rsquo; commands specify the format for both even- and 
odd-numbered
 pages.  These commands are for documents that are printed on one side
 of each sheet of paper, or for documents in which you want symmetrical
 headers or footers.
@@ -352,7 +352,7 @@
 <dt> <code>@evenfooting <var>left</var> @| <var>center</var> @| 
<var>right</var></code></dt>
 <dt> <code>@oddfooting  <var>left</var> @| <var>center</var> @| 
<var>right</var></code></dt>
 <dd>
-<p>The `even' and `odd' commands specify the format for even-numbered
+<p>The &lsquo;even&rsquo; and &lsquo;odd&rsquo; commands specify the format 
for even-numbered
 pages and odd-numbered pages.  These commands are for books and
 manuals that are printed on both sides of each sheet of paper.
 </p></dd>
@@ -382,7 +382,7 @@
 </dd>
 <dt> <code>@thischapter</code></dt>
 <dd><p>Expands to the number and name of the current
-chapter, in the format `Chapter 1: Title'.
+chapter, in the format &lsquo;Chapter 1: Title&rsquo;.
 </p>
 <a name="IDX459"></a>
 </dd>
@@ -403,7 +403,7 @@
 </dl>
 
 <p>You can also use the <code>@today{}</code> command, which expands to the
-current date, in `1 Jan 1900' format.
+current date, in &lsquo;1 Jan 1900&rsquo; format.
 <a name="IDX461"></a>
 </p>
 <p>Other @-commands and text are printed in a header or footer just as

Index: Tests/texinfo_res/texinfo_27.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/texinfo_res/texinfo_27.html,v
retrieving revision 1.31
retrieving revision 1.32
diff -u -b -r1.31 -r1.32
--- Tests/texinfo_res/texinfo_27.html   5 Feb 2007 15:30:26 -0000       1.31
+++ Tests/texinfo_res/texinfo_27.html   3 Oct 2007 09:34:51 -0000       1.32
@@ -168,7 +168,7 @@
 occurred (or more precisely, where it was detected).
 </p>
 <p>For example, if you accidentally end a menu with the command <code>@end
-menus</code> with an `s' on the end, instead of with <code>@end menu</code>, 
you
+menus</code> with an &lsquo;s&rsquo; on the end, instead of with <code>@end 
menu</code>, you
 will see an error message that says:
 </p>
 <table><tr><td>&nbsp;</td><td><pre class="example">@end menus is not handled 
by texinfo
@@ -231,8 +231,8 @@
 after typing the Info <kbd>f</kbd> command, Info will attempt to go to the
 referenced node.  If you type <kbd>f catch &lt;TAB&gt; &lt;RET&gt;</kbd>, Info
 will complete the node name of the correctly written example and take
-you to the `Catching Mistakes' node.  (If you try this, you can return
-from the `Catching Mistakes' node by typing <kbd>l</kbd>
+you to the &lsquo;Catching Mistakes&rsquo; node.  (If you try this, you can 
return
+from the &lsquo;Catching Mistakes&rsquo; node by typing <kbd>l</kbd>
 (<code>Info-last</code>).)
 </p>
 
@@ -427,20 +427,20 @@
 commands respectively.  If you move your cursor into the 
&lsquo;<samp>*Occur*</samp>&rsquo;
 window, you can position the cursor over one of the lines and use the
 <kbd>C-c C-c</kbd> command (<code>occur-mode-goto-occurrence</code>), to jump 
to
-the corresponding spot in the Texinfo file.  See <a 
href="../emacs/Other-Repeating-Search.html#Other-Repeating-Search">(emacs)Other 
Repeating Search</a> section `Using Occur' in <cite>The GNU Emacs 
Manual</cite>, for more
+the corresponding spot in the Texinfo file.  See <a 
href="../emacs/Other-Repeating-Search.html#Other-Repeating-Search">(emacs)Other 
Repeating Search</a> section &lsquo;Using Occur&rsquo; in <cite>The GNU Emacs 
Manual</cite>, for more
 information about <code>occur-mode-goto-occurrence</code>.
 </p>
 <p>The first line in the &lsquo;<samp>*Occur*</samp>&rsquo; window describes 
the <em>regular
 expression</em> specified by <var>texinfo-heading-pattern</var>.  This regular
 expression is the pattern that <code>texinfo-show-structure</code> looks for.
-See <a href="../emacs/Regexps.html#Regexps">(emacs)Regexps</a> section `Using 
Regular Expressions' in <cite>The GNU Emacs Manual</cite>,
+See <a href="../emacs/Regexps.html#Regexps">(emacs)Regexps</a> section 
&lsquo;Using Regular Expressions&rsquo; in <cite>The GNU Emacs Manual</cite>,
 for more information.
 </p>
 <p>When you invoke the <code>texinfo-show-structure</code> command, Emacs will
 display the structure of the whole buffer.  If you want to see the
 structure of just a part of the buffer, of one chapter, for example,
 use the <kbd>C-x n n</kbd> (<code>narrow-to-region</code>) command to mark the
-region.  (See <a href="../emacs/Narrowing.html#Narrowing">(emacs)Narrowing</a> 
section `Narrowing' in <cite>The GNU Emacs Manual</cite>.)  This is
+region.  (See <a href="../emacs/Narrowing.html#Narrowing">(emacs)Narrowing</a> 
section &lsquo;Narrowing&rsquo; in <cite>The GNU Emacs Manual</cite>.)  This is
 how the example used above was generated.  (To see the whole buffer
 again, use <kbd>C-x n w</kbd> (<code>widen</code>).)
 </p>
@@ -484,7 +484,7 @@
 </pre></td></tr></table>
 
 <p>and then, when prompted, type a <em>regexp</em>, a regular expression for
-the pattern you want to match.  (See <a 
href="../emacs/Regexps.html#Regexps">(emacs)Regexps</a> section `Regular 
Expressions' in <cite>The GNU Emacs Manual</cite>.)  The <code>occur</code> 
command works from
+the pattern you want to match.  (See <a 
href="../emacs/Regexps.html#Regexps">(emacs)Regexps</a> section &lsquo;Regular 
Expressions&rsquo; in <cite>The GNU Emacs Manual</cite>.)  The 
<code>occur</code> command works from
 the current location of the cursor in the buffer to the end of the
 buffer.  If you want to run <code>occur</code> on the whole buffer, place
 the cursor at the beginning of the buffer.
@@ -500,9 +500,9 @@
 or phrase, end the last word with a &lsquo;<samp>$</samp>&rsquo;; for example,
 &lsquo;<samp>catching mistakes$</samp>&rsquo;.  This can be helpful when you 
want to see
 all the nodes that are part of the same chapter or section and
-therefore have the same `Up' pointer.
+therefore have the same &lsquo;Up&rsquo; pointer.
 </p>
-<p>See <a 
href="../emacs/Other-Repeating-Search.html#Other-Repeating-Search">(emacs)Other 
Repeating Search</a> section `Using Occur' in <cite>The GNU Emacs Manual</cite>,
+<p>See <a 
href="../emacs/Other-Repeating-Search.html#Other-Repeating-Search">(emacs)Other 
Repeating Search</a> section &lsquo;Using Occur&rsquo; in <cite>The GNU Emacs 
Manual</cite>,
 for more information.
 </p>
 <hr size="6">
@@ -527,7 +527,7 @@
 <h2 class="section"> F.5 Finding Badly Referenced Nodes </h2>
 
 <p>You can use the <code>Info-validate</code> command to check whether any of
-the `Next', `Previous', `Up' or other node pointers fail to point to a
+the &lsquo;Next&rsquo;, &lsquo;Previous&rsquo;, &lsquo;Up&rsquo; or other node 
pointers fail to point to a
 node.  This command checks that every node pointer points to an
 existing node.  The <code>Info-validate</code> command works only on Info
 files, not on Texinfo files.
@@ -578,7 +578,7 @@
 </pre></td></tr></table>
 
 <p>Note that the <code>Info-validate</code> command requires an upper case
-`I'.  You may also need to create a tag table before running
+&lsquo;I&rsquo;.  You may also need to create a tag table before running
 <code>Info-validate</code>.  See section <a href="#SEC317">Tagifying a 
File</a>.
 </p>
 <p>If your file is valid, you will receive a message that says &ldquo;File 
appears
@@ -592,19 +592,19 @@
 <table><tr><td>&nbsp;</td><td><pre class="example">In node 
&quot;Overview&quot;, invalid Next: Texinfo Mode
 </pre></td></tr></table>
 
-<p>This meant that the node called &lsquo;<samp>Overview</samp>&rsquo; had a 
`Next' pointer that
+<p>This meant that the node called &lsquo;<samp>Overview</samp>&rsquo; had a 
&lsquo;Next&rsquo; pointer that
 did not point to anything (which was true in this case, since the test file
 had only one node in it).
 </p>
 <p>Now suppose we add a node named &lsquo;<samp>Texinfo Mode</samp>&rsquo; to 
our test case
-but we do not specify a `Previous' for this node.  Then we will get
+but we do not specify a &lsquo;Previous&rsquo; for this node.  Then we will get
 the following error message:
 </p>
 <table><tr><td>&nbsp;</td><td><pre class="example">In node &quot;Texinfo 
Mode&quot;, should have Previous: Overview
 </pre></td></tr></table>
 
-<p>This is because every `Next' pointer should be matched by a
-`Previous' (in the node where the `Next' points) which points back.
+<p>This is because every &lsquo;Next&rsquo; pointer should be matched by a
+&lsquo;Previous&rsquo; (in the node where the &lsquo;Next&rsquo; points) which 
points back.
 </p>
 <p><code>Info-validate</code> also checks that all menu entries and cross 
references
 point to actual nodes.

Index: Tests/texinfo_res/texinfo_29.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/texinfo_res/texinfo_29.html,v
retrieving revision 1.23
retrieving revision 1.24
diff -u -b -r1.23 -r1.24
--- Tests/texinfo_res/texinfo_29.html   5 Feb 2007 15:30:26 -0000       1.23
+++ Tests/texinfo_res/texinfo_29.html   3 Oct 2007 09:34:51 -0000       1.24
@@ -101,7 +101,7 @@
 right-hand braces.  These commands insert special symbols in the
 document; they do not require arguments.  For example,
 <code>@dots{}</code> &rArr; &lsquo;<samp>&hellip;</samp>&rsquo;, 
<code>@equiv{}</code>
-&rArr; &lsquo;<samp>&equiv;</samp>&rsquo;, <code>@TeX{}</code> &rArr; `TeX',
+&rArr; &lsquo;<samp>&equiv;</samp>&rsquo;, <code>@TeX{}</code> &rArr; 
&lsquo;TeX&rsquo;,
 and <code>@bullet{}</code> &rArr; &lsquo;<samp>&bull;</samp>&rsquo;.
 </p>
 </dd>
@@ -125,7 +125,7 @@
 <p>Thus, the alphabetic commands fall into classes that have
 different argument syntaxes.  You cannot tell to which class a command
 belongs by the appearance of its name, but you can tell by the
-command's meaning: if the command stands for a glyph, it is in
+command&rsquo;s meaning: if the command stands for a glyph, it is in
 class 2 and does not require an argument; if it makes sense to use the
 command together with other text as part of a paragraph, the command
 is in class 3 and must be followed by an argument in braces;

Index: Tests/texinfo_res/texinfo_3.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/texinfo_res/texinfo_3.html,v
retrieving revision 1.32
retrieving revision 1.33
diff -u -b -r1.32 -r1.33
--- Tests/texinfo_res/texinfo_3.html    5 Feb 2007 15:30:26 -0000       1.32
+++ Tests/texinfo_res/texinfo_3.html    3 Oct 2007 09:34:51 -0000       1.33
@@ -85,7 +85,7 @@
 comes with a special mode, called Texinfo mode, that provides Emacs
 commands and tools to help ease your work.
 </p>
-<p>This chapter describes features of GNU Emacs' Texinfo mode but not any
+<p>This chapter describes features of GNU Emacs&rsquo; Texinfo mode but not any
 features of the Texinfo formatting language.  So if you are reading this
 manual straight through from the beginning, you may want to skim through
 this chapter briefly and come back to it after reading succeeding
@@ -94,7 +94,7 @@
 <table class="menu" border="0" cellspacing="0">
 <tr><td align="left" valign="top"><a href="#Texinfo-Mode-Overview">&bull; 
Texinfo Mode Overview</a></td><td>&nbsp;&nbsp;</td><td align="left" 
valign="top">       How Texinfo mode can help you.
 </td></tr>
-<tr><td align="left" valign="top"><a href="#SEC23">2.1 The Usual GNU Emacs 
Editing Commands</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">    
           Texinfo mode adds to GNU Emacs' general
+<tr><td align="left" valign="top"><a href="#SEC23">2.1 The Usual GNU Emacs 
Editing Commands</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">    
           Texinfo mode adds to GNU Emacs&rsquo; general
                                   purpose editing features.
 </td></tr>
 <tr><td align="left" valign="top"><a href="#SEC24">2.2 Inserting Frequently 
Used Commands</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">       
            How to insert frequently used @-commands.
@@ -130,8 +130,8 @@
 Show the structure of a Texinfo source file.
 
 </li><li>
-Automatically create or update the `Next',
-`Previous', and `Up' pointers of a node.
+Automatically create or update the &lsquo;Next&rsquo;,
+&lsquo;Previous&rsquo;, and &lsquo;Up&rsquo; pointers of a node.
 
 </li><li>
 Automatically create or update menus.
@@ -172,7 +172,7 @@
 
 <p>In most cases, the usual Text mode commands work the same in Texinfo
 mode as they do in Text mode.  Texinfo mode adds new editing commands
-and tools to GNU Emacs' general purpose editing features.  The major
+and tools to GNU Emacs&rsquo; general purpose editing features.  The major
 difference concerns filling.  In Texinfo mode, the paragraph
 separation variable and syntax table are redefined so that Texinfo
 commands that should be on lines of their own are not inadvertently
@@ -187,7 +187,7 @@
 delimiter, you can jump from chapter title to chapter title with the
 <kbd>C-x ]</kbd> (<code>forward-page</code>) and <kbd>C-x [</kbd>
 (<code>backward-page</code>) commands and narrow to a chapter with the
-<kbd>C-x p</kbd> (<code>narrow-to-page</code>) command.  (See <a 
href="../emacs/Pages.html#Pages">(emacs)Pages</a> section `Pages' in <cite>The 
GNU Emacs Manual</cite>, for details about the page commands.)
+<kbd>C-x p</kbd> (<code>narrow-to-page</code>) command.  (See <a 
href="../emacs/Pages.html#Pages">(emacs)Pages</a> section &lsquo;Pages&rsquo; 
in <cite>The GNU Emacs Manual</cite>, for details about the page commands.)
 </p>
 <p>You may name a Texinfo file however you wish, but the convention is to
 end a Texinfo file name with one of the extensions
@@ -277,8 +277,8 @@
 <dt> <kbd>M-x address@hidden</kbd></dt>
 <dd><a name="IDX37"></a>
 <p>Insert <code>@node</code> and a comment line
-listing the sequence for the `Next',
-`Previous', and `Up' nodes.
+listing the sequence for the &lsquo;Next&rsquo;,
+&lsquo;Previous&rsquo;, and &lsquo;Up&rsquo; nodes.
 Leave point after the <code>@node</code>.
 </p>
 </dd>
@@ -356,7 +356,7 @@
 <a name="IDX47"></a>
 <p><kbd>C-c C-c C-d</kbd> (<code>texinfo-start-menu-description</code>) is an 
insert
 command that works differently from the other insert commands.  It
-inserts a node's section or chapter title in the space for the
+inserts a node&rsquo;s section or chapter title in the space for the
 description in a menu entry line.  (A menu entry has three parts, the
 entry name, the node name, and the description.  Only the node name is
 required, but a description helps explain what the node is about.
@@ -426,7 +426,7 @@
 typing <kbd>C-u C-c C-s</kbd>, it will list not only those lines with the
 @-commands for <code>@chapter</code>, <code>@section</code>, and the like, but
 also the <code>@node</code> lines.  You can use 
<code>texinfo-show-structure</code>
-with a prefix argument to check whether the `Next', `Previous', and `Up'
+with a prefix argument to check whether the &lsquo;Next&rsquo;, 
&lsquo;Previous&rsquo;, and &lsquo;Up&rsquo;
 pointers of an <code>@node</code> line are correct.
 </p>
 <p>Often, when you are working on a manual, you will be interested only
@@ -435,7 +435,7 @@
 <kbd>C-x n n</kbd> (<code>narrow-to-region</code>) command and
 <code>texinfo-show-structure</code> will work on only that region.  To see
 the whole buffer again, use <kbd>C-x n w</kbd> (<code>widen</code>).
-(See <a href="../emacs/Narrowing.html#Narrowing">(emacs)Narrowing</a> section 
`Narrowing' in <cite>The GNU Emacs Manual</cite>, for more
+(See <a href="../emacs/Narrowing.html#Narrowing">(emacs)Narrowing</a> section 
&lsquo;Narrowing&rsquo; in <cite>The GNU Emacs Manual</cite>, for more
 information about the narrowing commands.)
 </p>
 <a name="IDX50"></a>
@@ -446,7 +446,7 @@
 ]</kbd> (<code>forward-page</code>) and <kbd>C-x [</kbd> 
(<code>backward-page</code>)
 commands to move forward and backward by chapter, and to use the
 <kbd>C-x p</kbd> (<code>narrow-to-page</code>) command to narrow to a chapter.
-See <a href="../emacs/Pages.html#Pages">(emacs)Pages</a> section `Pages' in 
<cite>The GNU Emacs Manual</cite>, for more information
+See <a href="../emacs/Pages.html#Pages">(emacs)Pages</a> section 
&lsquo;Pages&rsquo; in <cite>The GNU Emacs Manual</cite>, for more information
 about the page commands.
 </p>
 <hr size="6">
@@ -473,8 +473,8 @@
 <p>Texinfo mode provides commands for automatically creating or updating
 menus and node pointers.  The commands are called &ldquo;update&rdquo; commands
 because their most frequent use is for updating a Texinfo file after you
-have worked on it; but you can use them to insert the `Next',
-`Previous', and `Up' pointers into an <code>@node</code> line that has none
+have worked on it; but you can use them to insert the &lsquo;Next&rsquo;,
+&lsquo;Previous&rsquo;, and &lsquo;Up&rsquo; pointers into an 
<code>@node</code> line that has none
 and to create menus in a file that has none.
 </p>
 <p>If you do not use the updating commands, you need to write menus and
@@ -500,7 +500,7 @@
 </p>
 <ul>
 <li>
-insert or update the `Next', `Previous', and `Up' pointers of a
+insert or update the &lsquo;Next&rsquo;, &lsquo;Previous&rsquo;, and 
&lsquo;Up&rsquo; pointers of a
 node,
 
 </li><li>
@@ -516,7 +516,7 @@
 <p>The updating commands work only with conventional Texinfo files, which
 are structured hierarchically like books.  In such files, a structuring
 command line must follow closely after each <code>@node</code> line, except
-for the `Top' <code>@node</code> line.  (A <em>structuring command line</em> is
+for the &lsquo;Top&rsquo; <code>@node</code> line.  (A <em>structuring command 
line</em> is
 a line beginning with <code>@chapter</code>, <code>@section</code>, or other
 similar command.)
 </p>
@@ -527,12 +527,12 @@
 the <code>@node</code> line and the structuring command line; and you may
 interpose only an <code>@comment</code> line or an <code>@ifinfo</code> line.
 </p>
-<p>Commands which work on a whole buffer require that the `Top' node be
+<p>Commands which work on a whole buffer require that the &lsquo;Top&rsquo; 
node be
 followed by a node with an <code>@chapter</code> or equivalent-level command.
 The menu updating commands will not create a main or master menu for a
 Texinfo file that has only <code>@chapter</code>-level nodes!  The menu
 updating commands only create menus <em>within</em> nodes for lower level
-nodes.  To create a menu of chapters, you must provide a `Top'
+nodes.  To create a menu of chapters, you must provide a &lsquo;Top&rsquo;
 node.
 </p>
 <p>The menu updating commands remove menu entries that refer to other Info
@@ -563,7 +563,7 @@
 constructing the master menu.  (See section <a href="texinfo_4.html#SEC59">The 
Top Node and Master Menu</a>, for more about a master menu.)
 </p>
 <p>For <code>texinfo-master-menu</code> to work, the Texinfo file must have a
-`Top' node and at least one subsequent node.
+&lsquo;Top&rsquo; node and at least one subsequent node.
 </p>
 <p>After extensively editing a Texinfo file, you can type the following:
 </p>
@@ -586,9 +586,9 @@
 <dt> <kbd>C-c C-u C-n</kbd></dt>
 <dt> <kbd>M-x texinfo-update-node</kbd></dt>
 <dd><a name="IDX53"></a>
-<p>Insert the `Next', `Previous', and `Up' pointers for the node that point is
+<p>Insert the &lsquo;Next&rsquo;, &lsquo;Previous&rsquo;, and &lsquo;Up&rsquo; 
pointers for the node that point is
 within (i.e., for the <code>@node</code> line preceding point).  If the
-<code>@node</code> line has pre-existing `Next', `Previous', or `Up'
+<code>@node</code> line has pre-existing &lsquo;Next&rsquo;, 
&lsquo;Previous&rsquo;, or &lsquo;Up&rsquo;
 pointers in it, the old pointers are removed and new ones inserted.
 With an argument (prefix argument, <kbd>C-u</kbd>, if interactive), this 
command
 updates all <code>@node</code> lines in the region (which is the text
@@ -614,7 +614,7 @@
 <dt> <kbd>C-c C-u C-e</kbd></dt>
 <dt> <kbd>M-x texinfo-every-node-update</kbd></dt>
 <dd><a name="IDX55"></a>
-<p>Insert or update the `Next', `Previous', and `Up' pointers for every
+<p>Insert or update the &lsquo;Next&rsquo;, &lsquo;Previous&rsquo;, and 
&lsquo;Up&rsquo; pointers for every
 node in the buffer.
 </p>
 </dd>
@@ -647,7 +647,7 @@
 column to which menu descriptions are indented.  By default, the value
 is 32 although it is often useful to reduce it to as low as 24.  You
 can set the variable with the <kbd>M-x edit-options</kbd> command
-(see <a href="../emacs/Edit-Options.html#Edit-Options">(emacs)Edit Options</a> 
section `Editing Variable Values' in <cite>The GNU Emacs Manual</cite>) or with 
the <kbd>M-x set-variable</kbd> command (see <a 
href="../emacs/Examining.html#Examining">(emacs)Examining</a> section 
`Examining and Setting Variables' in <cite>The GNU Emacs Manual</cite>).
+(see <a href="../emacs/Edit-Options.html#Edit-Options">(emacs)Edit Options</a> 
section &lsquo;Editing Variable Values&rsquo; in <cite>The GNU Emacs 
Manual</cite>) or with the <kbd>M-x set-variable</kbd> command (see <a 
href="../emacs/Examining.html#Examining">(emacs)Examining</a> section 
&lsquo;Examining and Setting Variables&rsquo; in <cite>The GNU Emacs 
Manual</cite>).
 </p>
 <p>Also, the <code>texinfo-indent-menu-description</code> command may be used 
to
 indent existing menu descriptions to a specified column.  Finally, if
@@ -677,14 +677,14 @@
 
 <p>To use the updating commands, you must organize the Texinfo file
 hierarchically with chapters, sections, subsections, and the like.
-When you construct the hierarchy of the manual, do not `jump down'
-more than one level at a time: you can follow the `Top' node with a
+When you construct the hierarchy of the manual, do not &lsquo;jump down&rsquo;
+more than one level at a time: you can follow the &lsquo;Top&rsquo; node with a
 chapter, but not with a section; you can follow a chapter with a
-section, but not with a subsection.  However, you may `jump up' any
+section, but not with a subsection.  However, you may &lsquo;jump up&rsquo; any
 number of levels at one time&mdash;for example, from a subsection to a
 chapter.
 </p>
-<p>Each <code>@node</code> line, with the exception of the line for the `Top'
+<p>Each <code>@node</code> line, with the exception of the line for the 
&lsquo;Top&rsquo;
 node, must be followed by a line with a structuring command such as
 <code>@chapter</code>, <code>@section</code>, or
 <code>@unnumberedsubsec</code>.
@@ -709,22 +709,22 @@
 @section Comments
 </pre></td></tr></table>
 
-<p>In this example, `Comments' is the name of both the node and the
-section.  The next node is called `Minimum' and the previous node is
-called `Conventions'.  The `Comments' section is within the `Overview'
-node, which is specified by the `Up' pointer.  (Instead of an
+<p>In this example, &lsquo;Comments&rsquo; is the name of both the node and the
+section.  The next node is called &lsquo;Minimum&rsquo; and the previous node 
is
+called &lsquo;Conventions&rsquo;.  The &lsquo;Comments&rsquo; section is 
within the &lsquo;Overview&rsquo;
+node, which is specified by the &lsquo;Up&rsquo; pointer.  (Instead of an
 <code>@comment</code> line, you may also write an <code>@ifinfo</code> line.)
 </p>
-<p>If a file has a `Top' node, it must be called 
&lsquo;<samp>top</samp>&rsquo; or &lsquo;<samp>Top</samp>&rsquo;
+<p>If a file has a &lsquo;Top&rsquo; node, it must be called 
&lsquo;<samp>top</samp>&rsquo; or &lsquo;<samp>Top</samp>&rsquo;
 and be the first node in the file.
 </p>
 <p>The menu updating commands create a menu of sections within a chapter,
 a menu of subsections within a section, and so on.  This means that
-you must have a `Top' node if you want a menu of chapters.
+you must have a &lsquo;Top&rsquo; node if you want a menu of chapters.
 </p>
 <p>Incidentally, the <code>makeinfo</code> command will create an Info file 
for a
-hierarchically organized Texinfo file that lacks `Next', `Previous' and
-`Up' pointers.  Thus, if you can be sure that your Texinfo file will be
+hierarchically organized Texinfo file that lacks &lsquo;Next&rsquo;, 
&lsquo;Previous&rsquo; and
+&lsquo;Up&rsquo; pointers.  Thus, if you can be sure that your Texinfo file 
will be
 formatted with <code>makeinfo</code>, you have no need for the update node
 commands.  (See section <a href="texinfo_21.html#SEC261">Creating an Info 
File</a>, for more information about
 <code>makeinfo</code>.)  However, both <code>makeinfo</code> and the
@@ -788,7 +788,7 @@
 <p>Update nodes and menus in a document built from several separate files.
 With <kbd>C-u</kbd> as a prefix argument, create and insert a master menu in
 the outer file.  With a numeric prefix argument, such as <kbd>C-u 2</kbd>, 
first
-update all the menus and all the `Next', `Previous', and `Up' pointers
+update all the menus and all the &lsquo;Next&rsquo;, &lsquo;Previous&rsquo;, 
and &lsquo;Up&rsquo; pointers
 of all the included files before creating and inserting a master menu in
 the outer file.  The <code>texinfo-multiple-files-update</code> command is
 described in the appendix on <code>@include</code> files.
@@ -809,8 +809,8 @@
 <dt> <kbd>M-x texinfo-sequential-node-update</kbd></dt>
 <dd><a name="IDX60"></a>
 <p>Insert the names of the nodes immediately following and preceding the
-current node as the `Next' or `Previous' pointers regardless of those
-nodes' hierarchical level.  This means that the `Next' node of a
+current node as the &lsquo;Next&rsquo; or &lsquo;Previous&rsquo; pointers 
regardless of those
+nodes&rsquo; hierarchical level.  This means that the &lsquo;Next&rsquo; node 
of a
 subsection may well be the next chapter.  Sequentially ordered nodes are
 useful for novels and other documents that you read through
 sequentially.  (However, in Info, the <kbd>g *</kbd> command lets
@@ -1005,7 +1005,7 @@
 
 <p>The insert commands are invoked by typing <kbd>C-c</kbd> twice and then the
 first letter of the @-command to be inserted.  (It might make more
-sense mnemonically to use <kbd>C-c C-i</kbd>, for `custom insert', but
+sense mnemonically to use <kbd>C-c C-i</kbd>, for &lsquo;custom insert&rsquo;, 
but
 <kbd>C-c C-c</kbd> is quick to type.)
 </p>
 <table><tr><td>&nbsp;</td><td><pre class="example">C-c C-c c       <span 
class="roman">Insert</span> &lsquo;<samp>@code</samp>&rsquo;.

Index: Tests/texinfo_res/texinfo_31.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/texinfo_res/texinfo_31.html,v
retrieving revision 1.25
retrieving revision 1.26
diff -u -b -r1.25 -r1.26
--- Tests/texinfo_res/texinfo_31.html   5 Feb 2007 15:30:26 -0000       1.25
+++ Tests/texinfo_res/texinfo_31.html   3 Oct 2007 09:34:51 -0000       1.26
@@ -156,7 +156,7 @@
 </p>
 <p>A &ldquo;Secondary Section&rdquo; is a named appendix or a front-matter 
section of
 the Document that deals exclusively with the relationship of the
-publishers or authors of the Document to the Document's overall subject
+publishers or authors of the Document to the Document&rsquo;s overall subject
 (or to related matters) and contains nothing that could fall directly
 within that overall subject.  (For example, if the Document is in part a
 textbook of mathematics, a Secondary Section may not explain any
@@ -200,7 +200,7 @@
 plus such following pages as are needed to hold, legibly, the material
 this License requires to appear in the title page.  For works in
 formats which do not have any title page as such, &ldquo;Title Page&rdquo; 
means
-the text near the most prominent appearance of the work's title,
+the text near the most prominent appearance of the work&rsquo;s title,
 preceding the beginning of the body of the text.
 </p>
 </li><li>
@@ -223,7 +223,7 @@
 COPYING IN QUANTITY
 
 <p>If you publish printed copies of the Document numbering more than 100,
-and the Document's license notice requires Cover Texts, you must enclose
+and the Document&rsquo;s license notice requires Cover Texts, you must enclose
 the copies in covers that carry, clearly and legibly, all these Cover
 Texts: Front-Cover Texts on the front cover, and Back-Cover Texts on
 the back cover.  Both covers must also clearly and legibly identify
@@ -299,7 +299,7 @@
 
 </li><li>
 Preserve in that license notice the full lists of Invariant Sections
-and required Cover Texts given in the Document's license notice.
+and required Cover Texts given in the Document&rsquo;s license notice.
 
 </li><li>
 Include an unaltered copy of this License.
@@ -324,7 +324,7 @@
 
 </li><li>
 In any section entitled &ldquo;Acknowledgments&rdquo; or 
&ldquo;Dedications&rdquo;,
-preserve the section's title, and preserve in the section all the
+preserve the section&rsquo;s title, and preserve in the section all the
 substance and tone of each of the contributor acknowledgments
 and/or dedications given therein.
 
@@ -346,7 +346,7 @@
 appendices that qualify as Secondary Sections and contain no material
 copied from the Document, you may at your option designate some or all
 of these sections as invariant.  To do this, add their titles to the
-list of Invariant Sections in the Modified Version's license notice.
+list of Invariant Sections in the Modified Version&rsquo;s license notice.
 These titles must be distinct from any other section titles.
 </p>
 <p>You may add a section entitled &ldquo;Endorsements&rdquo;, provided it 
contains
@@ -422,7 +422,7 @@
 </p>
 <p>If the Cover Text requirement of section 3 is applicable to these
 copies of the Document, then if the Document is less than one quarter
-of the entire aggregate, the Document's Cover Texts may be placed on
+of the entire aggregate, the Document&rsquo;s Cover Texts may be placed on
 covers that surround only the Document within the aggregate.
 Otherwise they must appear on covers around the whole aggregate.
 </p>

Index: Tests/texinfo_res/texinfo_32.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/texinfo_res/texinfo_32.html,v
retrieving revision 1.28
retrieving revision 1.29
diff -u -b -r1.28 -r1.29
--- Tests/texinfo_res/texinfo_32.html   30 Sep 2007 12:47:40 -0000      1.28
+++ Tests/texinfo_res/texinfo_32.html   3 Oct 2007 09:34:51 -0000       1.29
@@ -245,7 +245,7 @@
 <tr><td></td><td valign="top"><a 
href="texinfo_6.html#SEC80"><code>appendixsec</code></a></td><td 
valign="top"><a href="texinfo_6.html#SEC80">5.8 <code>@unnumberedsec</code>, 
<code>@appendixsec</code>, <code>@heading</code></a></td></tr>
 <tr><td></td><td valign="top"><a 
href="texinfo_6.html#IDX92"><code>appendixsection</code></a></td><td 
valign="top"><a href="texinfo_6.html#SEC80">5.8 <code>@unnumberedsec</code>, 
<code>@appendixsec</code>, <code>@heading</code></a></td></tr>
 <tr><td></td><td valign="top"><a 
href="texinfo_6.html#SEC82"><code>appendixsubsec</code></a></td><td 
valign="top"><a href="texinfo_6.html#SEC82">5.10 The 
<code>@subsection</code>-like Commands</a></td></tr>
-<tr><td></td><td valign="top"><a 
href="texinfo_6.html#SEC83"><code>appendixsubsubsec</code></a></td><td 
valign="top"><a href="texinfo_6.html#SEC83">5.11 The `subsub' 
Commands</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="texinfo_6.html#SEC83"><code>appendixsubsubsec</code></a></td><td 
valign="top"><a href="texinfo_6.html#SEC83">5.11 The &lsquo;subsub&rsquo; 
Commands</a></td></tr>
 <tr><td></td><td valign="top"><a 
href="texinfo_16.html#IDX286"><code>apply</code></a></td><td valign="top"><a 
href="texinfo_16.html#SEC226">15.6 A Sample Function Definition</a></td></tr>
 <tr><td></td><td valign="top"><a 
href="texinfo_12.html#IDX138"><code>asis</code></a></td><td valign="top"><a 
href="texinfo_12.html#SEC160">Using the <code>@table</code> 
Command</a></td></tr>
 <tr><td></td><td valign="top"><a 
href="texinfo_4.html#SEC55"><code>author</code></a></td><td valign="top"><a 
href="texinfo_4.html#SEC55">3.4.3 <code>@title</code>, <code>@subtitle</code>, 
and <code>@author</code></a></td></tr>
@@ -280,7 +280,7 @@
 <tr><td></td><td valign="top"><a 
href="texinfo_13.html#SEC173"><code>defcodeindex</code></a></td><td 
valign="top"><a href="texinfo_13.html#SEC173">12.5 Defining New 
Indices</a></td></tr>
 <tr><td></td><td valign="top"><a 
href="texinfo_16.html#IDX278"><code>defcv</code></a></td><td valign="top"><a 
href="texinfo_16.html#SEC223">15.4.5 Object-Oriented Programming</a></td></tr>
 <tr><td></td><td valign="top"><a 
href="texinfo_16.html#IDX266"><code>deffn</code></a></td><td valign="top"><a 
href="texinfo_16.html#SEC219">15.4.1 Functions and Similar 
Entities</a></td></tr>
-<tr><td></td><td valign="top"><a 
href="texinfo_16.html#SEC217"><code>deffnx</code></a></td><td valign="top"><a 
href="texinfo_16.html#SEC217">15.3 Two or More `First' Lines</a></td></tr>
+<tr><td></td><td valign="top"><a 
href="texinfo_16.html#SEC217"><code>deffnx</code></a></td><td valign="top"><a 
href="texinfo_16.html#SEC217">15.3 Two or More &lsquo;First&rsquo; 
Lines</a></td></tr>
 <tr><td></td><td valign="top"><a 
href="texinfo_13.html#SEC173"><code>defindex</code></a></td><td valign="top"><a 
href="texinfo_13.html#SEC173">12.5 Defining New Indices</a></td></tr>
 <tr><td></td><td valign="top"><a 
href="texinfo_19.html#SEC243"><code>definfoenclose</code></a></td><td 
valign="top"><a href="texinfo_19.html#SEC243"