[Top][All Lists]
[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 á </h2>
-<p>With brace á. Testing ' " ` ^.
+<p>With brace á. Testing ’ " ‘ ^.
</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 á </h2>
-<p>With brace á. Testing ' " ` ^.
+<p>With brace á. Testing ’ " ‘ ^.
</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> </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> </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> </td><td align="left" valign="top">
Problems <small>CVS</small> doesn’t try to solve
</td></tr>
<tr><td align="left" valign="top"><a href="#SEC4">1.3 A sample
session</a></td><td> </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’ 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’t, <small>CVS</small> can’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 ‘<tt>A</tt>’. At the same time,
someone edits file ‘<tt>B</tt>’, 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>’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’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 ‘<tt>commitinfo</tt>’,
+In some cases you’ll want to use the ‘<tt>commitinfo</tt>’,
‘<tt>loginfo</tt>’, ‘<tt>rcsinfo</tt>’, or
‘<tt>verifymsg</tt>’
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’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’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—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’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 ‘<samp>>>>>>>> </samp>’ at
the start of a
-line that don't mark a conflict), the current
+line that don’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’t running a cvs
command, look in the repository directory mentioned in
the message and remove files which they own whose names
start with ‘<tt>#cvs.rfl</tt>’,
‘<tt>#cvs.wfl</tt>’, or ‘<tt>#cvs.lock</tt>’.
</p>
-<p>Note that these locks are to protect <small>CVS</small>'s
+<p>Note that these locks are to protect <small>CVS</small>’s
internal data structures and have no relationship to
the word <em>lock</em> in the sense used by
<small>RCS</small>—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—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—Indicate that a Module is no longer in
use</a>) to the file’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’ 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> ‘<samp>-kkvl</samp>’</dt>
-<dd><p>Like ‘<samp>-kkv</samp>’, except that a locker's name is
always
+<dd><p>Like ‘<samp>-kkv</samp>’, except that a locker’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’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 ‘<samp>-kv</samp>’ with <code>cvs
-export</code>—see section <a
href="cvs_16.html#SEC135">export—Export sources from CVS, similar to
checkout</a>. But be aware that doesn't
+export</code>—see section <a
href="cvs_16.html#SEC135">export—Export sources from CVS, similar to
checkout</a>. But be aware that doesn’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 ‘head’ 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 ‘head’
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’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 ‘head’
revision back to the vendor branch on all files. For
example, if you have a checked-out copy of the sources
in ‘<tt>~/work.d/wdiff</tt>’, and you want to revert to the
-vendor's version for all the files in that directory,
+vendor’s version for all the files in that directory,
you would type:
</p>
<table><tr><td> </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’ll have to think about what you want
and use the ‘<samp>-k</samp>’ 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’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’s efforts to branch 1.1.3 and use the
vendor tag BLUE. So the commands you might use are:
</p>
<table><tr><td> </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’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’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> </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> </td><td align="left" valign="top">
Indicating CVS's success or failure
+<tr><td align="left" valign="top"><a href="#SEC116">A.2 CVS’s exit
status</a></td><td> </td><td align="left" valign="top">
Indicating CVS’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> </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—Print out
log information for files</a></td><td> </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—'patch'
format diffs between releases</a></td><td> </td><td align="left"
valign="top"> 'patch' format diffs between releases
+<tr><td align="left" valign="top"><a href="#SEC146">A.14
rdiff—’patch’ format diffs between
releases</a></td><td> </td><td align="left" valign="top">
’patch’ format diffs between releases
</td></tr>
<tr><td align="left" valign="top"><a href="#SEC149">A.15
release—Indicate that a Module is no longer in
use</a></td><td> </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’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’s
‘<tt>~/.cvsrc</tt>’ file:
</p>
<table><tr><td> </td><td><pre class="example">log -N
@@ -267,7 +267,7 @@
diff foobar</samp>’ will be in unidiff format. ‘<samp>cvs diff
-c foobar</samp>’ will provide context diffs, as usual.
Getting "old" format diffs would be slightly more
-complicated, because <code>diff</code> doesn't have an option
+complicated, because <code>diff</code> doesn’t have an option
to specify use of the "old" format, so you would need
‘<samp>cvs -f diff foobar</samp>’.
</p>
@@ -375,7 +375,7 @@
<dt> <code>-H</code></dt>
<dt> <code>--help</code></dt>
<dd><p>Display usage information about the specified
‘<samp>cvs_command</samp>’
-(but do not actually execute the command). If you don't specify
+(but do not actually execute the command). If you don’t specify
a command name, ‘<samp>cvs -H</samp>’ 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 ‘<samp>-R</samp>’ can also considerably
-speed up checkout's over NFS.
+speed up checkout’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’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 ‘<samp>-D</samp>’
-flag so that your shell doesn't interpret spaces as
+flag so that your shell doesn’t interpret spaces as
argument separators. A command using the ‘<samp>-D</samp>’
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’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 ‘<samp>-b</samp>’ 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’t very useful, in the future it may
change to be like the ‘<samp>::</samp>’ 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’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’t contain empty
intermediate directories. In this case <em>only</em>,
<small>CVS</small> tries to “shorten” pathnames to avoid those
empty
directories.
@@ -1458,7 +1458,7 @@
<ul>
<li>
-Synopsis: commit [-lnRf] [-m 'log_message' |
+Synopsis: commit [-lnRf] [-m ’log_message’ |
-F file] [-r revision] [files…]
</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’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 ‘<samp>-f</samp>’ 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’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’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> </td><td align="left" valign="top"></td></tr>
@@ -2245,7 +2245,7 @@
</dd>
<dt> ‘<samp><var>F</var><var>n</var></samp>’</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>’s value formatted with
<var>F</var>.
</p>
<dl compact="compact">
<dt> ‘<samp>e</samp>’</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>’s value equals <var>B</var>’s; otherwise it is
equivalent to <var>E</var>.
</p>
<p>For example, ‘<samp>%(N=0?no:%dN) line%(N=1?:s)</samp>’ is
equivalent to
‘<samp>no lines</samp>’ 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>’s normal format. You can tailor this
command
+to get fine control over <code>diff</code>’s output.
</p>
<table><tr><td> </td><td><pre class="example">cvs diff \
--old-line-format='< %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’t handle an export containing binary
files correctly. Also be aware that after having used
‘<samp>-kv</samp>’, one can no longer use the <code>ident</code>
command (which is part of the <small>RCS</small> suite—see
@@ -2697,7 +2697,7 @@
‘<samp>-e</samp>’ 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 ‘<samp>-x</samp>’.
+types, you’ll want to specify ‘<samp>-x</samp>’.
</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 ‘-I !’.
</p>
<p><var>name</var> can be a file name pattern of the same type
that you can specify in the ‘<tt>.cvsignore</tt>’ 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 "more"'ing over 3 pages of tag
+tags, so rather than "more"’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’s
login is assumed. There can be no space between the
‘<samp>-w</samp>’ 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—'patch' format diffs between
releases </h2>
+<h2 class="appendixsec"> A.14 rdiff—’patch’ 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’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’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’t handle the unidiff
format, so if you plan to post this patch to the net
you should probably not use ‘<samp>-u</samp>’.
</p>
@@ -3555,12 +3555,12 @@
</li></ul>
<p>This command is meant to safely cancel the effect of
-‘<samp>cvs checkout</samp>’. Since <small>CVS</small> doesn't
lock files, it
-isn't strictly necessary to use this command. You can
+‘<samp>cvs checkout</samp>’. Since <small>CVS</small>
doesn’t lock files, it
+isn’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’ve abandoned your
checkout.
</p>
<p>Use ‘<samp>cvs release</samp>’ 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’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’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’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>‘<samp>M</samp>’ can indicate one of two states for a file
-you're working on: either there were no modifications
+you’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 “shorten” module paths if -d specified. See
+<dd><p>Don’t “shorten” 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 “shorten” module paths if -d specified. See
+<dd><p>Don’t “shorten” 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’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’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>…</code></dt>
-<dd><p>Show differences between releases. See <a
href="cvs_16.html#SEC146">rdiff—'patch' format diffs between releases</a>.
+<dd><p>Show differences between releases. See <a
href="cvs_16.html#SEC146">rdiff—’patch’ 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’s standards for coding practice.
</p>
<p>As mentioned earlier, each line in the
‘<tt>commitinfo</tt>’ file consists of a regular expression
@@ -863,13 +863,13 @@
that is run by ‘<tt>verifymsg</tt>’.
</p>
<p>An example of an update might be to change all
-occurrences of 'BugId:' to be 'DefectId:' (which can be
+occurrences of ’BugId:’ to be ’DefectId:’ (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 ’BugID: none’ 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>"</tt>).
-Any embedded dollar signs (<tt>$</tt>), backticks (<tt>`</tt>),
+Any embedded dollar signs (<tt>$</tt>), backticks (<tt>‘</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’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 ‘<samp>cvs update</samp>’, it prints a
-line for each file it encounters that it doesn't know
+line for each file it encounters that it doesn’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 ‘<tt>checkoutlist</tt>’ in this fashion,
the files listed there will function just like
-<small>CVS</small>'s built-in administrative files. For example,
+<small>CVS</small>’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 @@
‘<samp>~</samp>’ followed by ‘<samp>/</samp>’ or the
end of the line.
Likewise for the home directory of <var>user</var>, use
‘<samp>~<var>user</var></samp>’. These variables are expanded on
-the server machine, and don't get any reasonable
+the server machine, and don’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 ‘<samp>yes</samp>’, then pserver
should check
-for users in the system's user database if not found in
+for users in the system’s user database if not found in
‘<tt>CVSROOT/passwd</tt>’. If it is
‘<samp>no</samp>’, then all
pserver users must exist in ‘<tt>CVSROOT/passwd</tt>’.
The default is ‘<samp>yes</samp>’. 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 ‘<tt>CVS</tt>’ directory created there
-will mean you don't have to specify <code>CVSROOT</code> for
+will mean you don’t have to specify <code>CVSROOT</code> for
each command. It also provides a place for the
‘<tt>CVS/Template</tt>’ 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’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 @@
‘<samp>stat()</samp>’ function to see if it has changed (see
warning below)
before rereading. The default value is ‘<samp>always</samp>’.
</p>
-<p><strong>Note: the `stat' mode can cause CVS to pause for up to
+<p><strong>Note: the ‘stat’ 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 ‘<samp>d:</samp>’ and
<code>HOMEPATH</code>,
-for example to ‘<tt>\joe</tt>’. On Windows 95, you'll
+for example to ‘<tt>\joe</tt>’. On Windows 95, you’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>’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’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’ve checked a working copy out from the
repository, it will remember where its repository is
(the information is recorded in the
‘<tt>CVS/Root</tt>’ 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’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>’s
rules see <a href="cvs_4.html#SEC48">Tags–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’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’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, ‘<samp>=</samp>’ in <var>attrname</var>,
‘<samp>;</samp>’ in <var>attrval</var>, etc. Note: some
implementations also
-don't handle a NUL character in any of the fields, but
+don’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
‘<samp>_</samp>’ is for an attribute given
@@ -803,9 +803,9 @@
<p>By default, the ‘<tt>modules</tt>’ 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’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’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’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’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’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’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’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’t lose any
changes. If you really do want to reuse the existing
working directory, it should be possible with manual
surgery on the ‘<tt>CVS/Repository</tt>’ files. You can
see <a href="#SEC19">How data is stored in the working directory</a>, for
information on
the ‘<tt>CVS/Repository</tt>’ and ‘<tt>CVS/Root</tt>’
files, but
unless you are sure you want to bother, it probably
-isn't worth it.
+isn’t worth it.
</p>
<hr size="6">
<a name="Remote-repositories"></a>
@@ -1613,7 +1613,7 @@
the local machine ‘<samp>toe.example.com</samp>’, and the
server machine is ‘<samp>faun.example.org</samp>’. On
faun, put the following line into the file
-‘<tt>.rhosts</tt>’ in ‘<samp>bach</samp>’'s home
directory:
+‘<tt>.rhosts</tt>’ in ‘<samp>bach</samp>’’s home
directory:
</p>
<table><tr><td> </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—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’t compromise
their regular passwords when they access the
repository. This file is
‘<tt>$CVSROOT/CVSROOT/passwd</tt>’ (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’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’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> ‘<tt>passwd</tt>’ 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’s
user-lookup routines (this "fallback" behavior can be
disabled by setting <code>SystemAuth=no</code> in the
<small>CVS</small> ‘<tt>config</tt>’ 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’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 ‘<tt>passwd</tt>’ file in-place,
rather than via <small>CVS</small>. This is because of the
possible security risks of having the ‘<tt>passwd</tt>’
-file checked out to people's working copies. If you do
+file checked out to people’s working copies. If you do
want to include the ‘<tt>passwd</tt>’ file in checkouts of
‘<tt>$CVSROOT/CVSROOT</tt>’, 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’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.
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’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
<var>$CVSROOT</var>:
</p>
<table><tr><td> </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’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
-‘<tt>$HOME/.cvspass</tt>’. That file's format is
+‘<tt>$HOME/.cvspass</tt>’. That file’s format is
human-readable, and to a degree human-editable, but
note that the passwords are not stored in
cleartext—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’ll have to re-run
<code>cvs login</code>).
</p>
<p>Note that if the ‘<samp>:pserver:</samp>’ 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 ‘<tt>CVS</tt>’ subdirectory.
+from the working copy’s ‘<tt>CVS</tt>’ 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’t forget the newline after the last user.)
</p>
<p> "Exclusion" means explicitly listing everyone
who has <em>write</em> access—if the file
@@ -2454,7 +2454,7 @@
‘<tt>writers</tt>’ 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’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 ‘<samp>cvs add <var>file</var></samp>’. 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’s modification to decide whether you
+still want to remove it. If you don’t want to remove
it, stop here. If you do want to remove it, proceed
with ‘<samp>cvs remove <var>file</var></samp>’ 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’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’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 ‘<samp>-t</samp>’ global option. It
-was fixed by Andy Piper's 14 Nov 1997 change to
+was fixed by Andy Piper’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’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—we haven't tracked it down yet!). It seems to
+bug in <small>CVS</small> or the systems it runs on (we don’t
+know—we haven’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
‘<tt>log.pl</tt>’ from <small>CVS</small> 1.5 and newer expects the
logfile to be specified with a ‘<samp>-f</samp>’ option. Of
-course, if you don't need ‘<tt>log.pl</tt>’ you can just
+course, if you don’t need ‘<tt>log.pl</tt>’ you can just
comment it out of ‘<tt>loginfo</tt>’.
</p>
</dd>
@@ -530,13 +530,13 @@
<dt> <code>:ext:</code></dt>
<dd><p>Try running the rsh program from the command line. For
example: "rsh servername cvs -v" should print <small>CVS</small>
-version information. If this doesn't work, you need to
+version information. If this doesn’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’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 "connection refused" typically
indicate
-that inetd isn't even listening for connections on port 2401
+that inetd isn’t even listening for connections on port 2401
whereas errors like "connection reset by peer",
"received broken pipe signal", "recv() from server: EOF",
or "end of file from server"
@@ -573,9 +573,9 @@
...
</pre></td></tr></table>
-<p>then you're missing the ‘<samp>pserver</samp>’ command at the
end of the
+<p>then you’re missing the ‘<samp>pserver</samp>’ command at
the end of the
line in ‘<tt>inetd.conf</tt>’; check to make sure that the entire
command
-is on one line and that it's complete.
+is on one line and that it’s complete.
</p>
<p>Likewise, if you get something like:
</p>
@@ -586,7 +586,7 @@
...
</pre></td></tr></table>
-<p>then you've misspelled ‘<samp>pserver</samp>’ in some way. If
it isn't
+<p>then you’ve misspelled ‘<samp>pserver</samp>’ in some
way. If it isn’t
obvious, check for invisible control characters (particularly
carriage returns) in ‘<tt>inetd.conf</tt>’.
</p>
@@ -600,12 +600,12 @@
<p>After making that change and instructing inetd to
re-read its configuration file, "telnet servername
2401" 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’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’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 ‘<samp>-f</samp>’ in
‘<tt>inetd.conf</tt>’.
+<p>then you probably haven’t specified ‘<samp>-f</samp>’ in
‘<tt>inetd.conf</tt>’.
(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’t,
+you’ve probably hit inetd’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’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’ve made:
</p>
<table><tr><td> </td><td><pre class="display">Roxanne Brunskill
<<tt>address@hidden</tt>>,
Kathy Dyer <<tt>address@hidden</tt>>,
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’t like this, don’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’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’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
‘<tt>verifymsg</tt>’</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—'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—’patch’ 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’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’t changed),
you might invoke:
</p>
<table><tr><td> </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’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 ‘<samp>.</samp>’ changed to
‘<samp>-</samp>’, 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’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’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’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’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 ‘<samp>-a</samp>’,
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’t think this is
necessary if ‘<samp>-r</samp>’ 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’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 ‘<samp>checkout -D</samp>’
@@ -701,8 +701,8 @@
working copy – 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’t need to think about. However,
+even if you don’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’t the easiest way, if you are asking
how to undo a previous checkin (in this example, put
‘<tt>file1</tt>’ 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’re in a working copy:
</p>
<table><tr><td> </td><td><pre class="example">$ cvs tag -b rel-1-0-patches
</pre></td></tr></table>
@@ -176,7 +176,7 @@
<p>‘<samp>-r rel-1-0</samp>’ says that this branch should be
rooted at the revision that
corresponds to the tag ‘<samp>rel-1-0</samp>’. It need not
-be the most recent revision – it's often useful to
+be the most recent revision – it’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 ‘<samp>status</samp>’ command. In its output, look for
the field named ‘<samp>Sticky tag</samp>’ (see section <a
href="cvs_4.html#SEC53">Sticky tags</a>)
-– that's <small>CVS</small>'s way of telling you the branch, if
+– that’s <small>CVS</small>’s way of telling you the branch,
if
any, of the current working files:
</p>
<table><tr><td> </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’t be confused by the fact that the branch numbers
for each file are different (‘<samp>1.7.2</samp>’ and
‘<samp>1.4.2</samp>’ respectively). The branch tag is the
same, ‘<samp>rel-1-0-patches</samp>’, 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’s revision history at which the
branch was made. In the above example, one can deduce
that ‘<samp>driver.c</samp>’ had been through more changes than
‘<samp>backend.c</samp>’ 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’s revision history is a linear
series of increments (see section <a href="cvs_4.html#SEC45">Revision
numbers</a>):
</p>
<table><tr><td> </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’t remove the directory
itself; there is no way to do that.
Instead you specify the ‘<samp>-P</samp>’ 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’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—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’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—'patch'
format diffs between releases</a>
+ <li><a name="TOC146" href="cvs_16.html#SEC146">A.14
rdiff—’patch’ 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è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’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écédente dans l'ordre de lecture"> < </a>]</td>
-<td valign="middle" align="left">[<a href="#SEC2" title="Section suivante dans
l'ordre de lecture"> > </a>]</td>
+<tr><td valign="middle" align="left">[<a href="#SEC_Top" title="Section
précédente dans l’ordre de lecture"> < </a>]</td>
+<td valign="middle" align="left">[<a href="#SEC2" title="Section suivante dans
l’ordre de lecture"> > </a>]</td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left">[ << ]</td>
<td valign="middle" align="left">[<a href="#SEC_Top" title="Section
supé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è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’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écédente dans l'ordre de lecture"> < </a>]</td>
-<td valign="middle" align="left">[<a href="#SEC3" title="Section suivante dans
l'ordre de lecture"> > </a>]</td>
+<tr><td valign="middle" align="left">[<a href="#SEC1" title="Section
précédente dans l’ordre de lecture"> < </a>]</td>
+<td valign="middle" align="left">[<a href="#SEC3" title="Section suivante dans
l’ordre de lecture"> > </a>]</td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left">[<a href="#SEC1" title="Début de ce
chapitre ou chapitre précédent"> << </a>]</td>
<td valign="middle" align="left">[<a href="#SEC1" title="Section
supé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è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’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 ‘title’ 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"> !_"#$%&'()*+-./;<=>?[\]^_`|~ </h3>
+<h3 class="node"> !_"#$%&’()*+-./;<=>?[\]^_‘|~ </h3>
<table><tr><td> </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>!_"#$%&'()*+-./;<=>?[\]^_`|~</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">!_"#$%&'()*+-./;<=>?[\]^_`|~</a><br>
+<p><tt>!_"#$%&'()*+-./;<=>?[\]^_`|~</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">!_"#$%&’()*+-./;<=>?[\]^_‘|~</a><br>
</p><table><tr><td> </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">•
!_"#$%&'()*+-./;<=>?[\]^_`|~</a></td><td> </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">•
!_"#$%&’()*+-./;<=>?[\]^_‘|~</a></td><td> </td><td
align="left" valign="top">
</td></tr>
<tr><td align="left" valign="top"><a href="#local-node">• local
node</a></td><td> </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 @@
@"{U} Ü
@~n ñ
@^a â
-@'e é
+@’e é
@=o ō
address@hidden ì
-@'address@hidden í
+@‘i ì
+@’address@hidden í
@dotless{i} i
</p>
<p>@* <br>
@@ -782,9 +782,9 @@
<dd><p>d–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
‘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>
<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 ‘chapter’ 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 ‘node’ 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
‘chapter’ 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 ‘node’ 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
‘title’ 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
‘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{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 ‘title’ 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 ‘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>
</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 @@
@"{U} Ü
@~n ñ
@^a â
-@'e é
+@’e é
@=o ō
address@hidden ì
-@'address@hidden í
+@‘i ì
+@’address@hidden í
@dotless{i} i
</p>
<p>@* <br>
@@ -1211,9 +1211,9 @@
<dd><p>d–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
‘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>
<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 ‘chapter’ 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 ‘node’ 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
‘chapter’ 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 ‘node’ 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
‘title’ 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
‘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{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 ‘title’ 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 ‘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>
</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’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’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’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’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>“simple-double–three—four—-”</strong> <br>
kbd: <kbd>``simple-double--three---four----''</kbd> <br>
</p>
-<p>``simple-double--three—four—-''<br>
+<p>‘‘simple-double--three—four—-’’<br>
</p>
<a name="IDX1"></a>
<a name="IDX2"></a>
@@ -556,16 +556,16 @@
@"{U} Ü
@~n ñ
@^a â
-@'e é
+@’e é
@=o ō
address@hidden ì
-@'{e} é
-@'address@hidden í
+@‘i ì
+@’{e} é
+@’address@hidden í
@dotless{i} i
@dotless{ij} ij
address@hidden@=E} Ē`
+@‘address@hidden Ē`
@l{} ł
-@,{@'C} Ć,
+@,{@’C} Ć,
@,c ç
@,c@"u çü <br>
</p>
@@ -574,10 +574,10 @@
<br>
@,@"u ,ü
</p>
-<p>Invalid use of @':<br>
-@' '
+<p>Invalid use of @’:<br>
+@’ ’
<br>
-@'@"u @'"u
+@’@"u @'"u
</p>
<p>@dotless{truc} truc
</p>
@@ -1174,9 +1174,9 @@
<tr><td colspan="2"><p>d–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—ef name@: (file n—ame@)c—hapter@</a> section
`t—itle@' in <cite>ma—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—ef name@: (file n—ame@)c—hapter@</a> section
‘t—itle@’ in <cite>ma—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>
<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 ‘chapter’ 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 ‘node’ 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
‘chapter’ 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 ‘node’ 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
‘title’ 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
‘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{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 ‘title’ 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 ‘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{,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 ‘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{,,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 ‘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{,,,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–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–ect,ion</a> section ‘a comma, in title’ in
<cite>a , in manual name</cite>
</p>
<p><code>@address@hidden</code> <a
href="exotic_formatting_3.html#SEC2">s–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>“simple-double–three—four—-”</strong> <br>
kbd: <kbd>``simple-double--three---four----''</kbd> <br>
</p>
-<p>``simple-double--three—four—-''<br>
+<p>‘‘simple-double--three—four—-’’<br>
</p>
<a name="IDX1"></a>
<a name="IDX2"></a>
@@ -555,16 +555,16 @@
@"{U} Ü
@~n ñ
@^a â
-@'e é
+@’e é
@=o ō
address@hidden ì
-@'{e} é
-@'address@hidden í
+@‘i ì
+@’{e} é
+@’address@hidden í
@dotless{i} i
@dotless{ij} ij
address@hidden@=E} Ē`
+@‘address@hidden Ē`
@l{} ł
-@,{@'C} Ć,
+@,{@’C} Ć,
@,c ç
@,c@"u çü <br>
</p>
@@ -573,10 +573,10 @@
<br>
@,@"u ,ü
</p>
-<p>Invalid use of @':<br>
-@' '
+<p>Invalid use of @’:<br>
+@’ ’
<br>
-@'@"u @'"u
+@’@"u @'"u
</p>
<p>@dotless{truc} truc
</p>
@@ -1029,9 +1029,9 @@
<dd><p>d–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—ef name@: (file
n—ame@)c—hapter@</a> section `t—itle@' in
<cite>ma—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—ef name@: (file
n—ame@)c—hapter@</a> section ‘t—itle@’ in
<cite>ma—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>
<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 ‘chapter’ 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 ‘node’ 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
‘chapter’ 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 ‘node’ 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
‘title’ 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
‘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{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 ‘title’ 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 ‘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{,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 ‘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{,,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 ‘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{,,,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–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–ect,ion</a> section ‘a comma, in
title’ 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ères">Table des matiè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’aide)"> ? </a>]</td>
</tr></table>
<table class="menu" border="0" cellspacing="0">
@@ -544,7 +544,7 @@
strong:
<strong>“simple-double–three—four—-”</strong> <br>
kbd: <kbd>``simple-double--three---four----''</kbd> <br>
</p>
-<p>``simple-double--three—four—-''<br>
+<p>‘‘simple-double--three—four—-’’<br>
</p>
<a name="IDX1"></a>
<a name="IDX2"></a>
@@ -555,16 +555,16 @@
@"{U} Ü
@~n ñ
@^a â
-@'e é
+@’e é
@=o ō
address@hidden ì
-@'{e} é
-@'address@hidden í
+@‘i ì
+@’{e} é
+@’address@hidden í
@dotless{i} i
@dotless{ij} ij
address@hidden@=E} Ē`
+@‘address@hidden Ē`
@l{} ł
-@,{@'C} Ć,
+@,{@’C} Ć,
@,c ç
@,c@"u çü <br>
</p>
@@ -573,10 +573,10 @@
<br>
@,@"u ,ü
</p>
-<p>Invalid use of @':<br>
-@' '
+<p>Invalid use of @’:<br>
+@’ ’
<br>
-@'@"u @'"u
+@’@"u @'"u
</p>
<p>@dotless{truc} truc
</p>
@@ -1029,9 +1029,9 @@
<dd><p>d–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—ef name@: (file
n—ame@)c—hapter@</a> section `t—itle@' dans
<cite>ma—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—ef name@: (file
n—ame@)c—hapter@</a> section ‘t—itle@’ dans
<cite>ma—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>
<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 ‘chapter’ 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 ‘node’ 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
‘chapter’ 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 ‘node’
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
‘title’ 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
‘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{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 ‘title’ 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 ‘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{,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 ‘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{,,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 ‘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{,,,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–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–ect,ion</a> section ‘a comma, in
title’ dans <cite>a , in manual name</cite>
</p>
<p><code>@address@hidden</code> <a href="#SEC2">A section</a>
</p>
@@ -1727,7 +1727,7 @@
</td></tr></table>
<table border="0" class="index-cp">
-<tr><td></td><th align="left">Entrée d'index</th><th align="left">
Section</th></tr>
+<tr><td></td><th align="left">Entrée d’index</th><th
align="left"> Section</th></tr>
<tr><td colspan="3"> <hr></td></tr>
<tr><th><a name="SEC_Top_0">"</a></th><td></td><td></td></tr>
<tr><td></td><td valign="top"><a href="#SEC_Top">“</a></td><td
valign="top"><a href="#SEC_Top">Top section</a></td></tr>
@@ -1796,7 +1796,7 @@
</td></tr></table>
<table border="0" class="index-fn">
-<tr><td></td><th align="left">Entrée d'index</th><th align="left">
Section</th></tr>
+<tr><td></td><th align="left">Entrée d’index</th><th
align="left"> Section</th></tr>
<tr><td colspan="3"> <hr></td></tr>
<tr><th><a name="SEC_Top_0">"</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 @@
</td></tr></table>
<table border="0" class="index-vr">
-<tr><td></td><th align="left">Entrée d'index</th><th align="left">
Section</th></tr>
+<tr><td></td><th align="left">Entrée d’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 @@
</td></tr></table>
<table border="0" class="index-tp">
-<tr><td></td><th align="left">Entrée d'index</th><th align="left">
Section</th></tr>
+<tr><td></td><th align="left">Entrée d’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écédente dans l'ordre de lecture"> < </a>]</td>
-<td valign="middle" align="left">[<a href="#SEC2" title="Section suivante dans
l'ordre de lecture"> > </a>]</td>
+<tr><td valign="middle" align="left">[<a href="#SEC_Top" title="Section
précédente dans l’ordre de lecture"> < </a>]</td>
+<td valign="middle" align="left">[<a href="#SEC2" title="Section suivante dans
l’ordre de lecture"> > </a>]</td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left">[ << ]</td>
<td valign="middle" align="left">[<a href="#SEC_Top" title="Section
supé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ères">Table des matiè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’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écédente dans l'ordre de lecture"> < </a>]</td>
-<td valign="middle" align="left">[<a href="#SEC3" title="Section suivante dans
l'ordre de lecture"> > </a>]</td>
+<tr><td valign="middle" align="left">[<a href="#SEC1" title="Section
précédente dans l’ordre de lecture"> < </a>]</td>
+<td valign="middle" align="left">[<a href="#SEC3" title="Section suivante dans
l’ordre de lecture"> > </a>]</td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left">[<a href="#SEC1" title="Début de ce
chapitre ou chapitre précédent"> << </a>]</td>
<td valign="middle" align="left">[<a href="#SEC1" title="Section
supé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ères">Table des matiè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’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écédente dans l'ordre de lecture"> < </a>]</td>
-<td valign="middle" align="left">[<a href="#SEC4" title="Section suivante dans
l'ordre de lecture"> > </a>]</td>
+<tr><td valign="middle" align="left">[<a href="#SEC2" title="Section
précédente dans l’ordre de lecture"> < </a>]</td>
+<td valign="middle" align="left">[<a href="#SEC4" title="Section suivante dans
l’ordre de lecture"> > </a>]</td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left">[<a href="#SEC1" title="Début de ce
chapitre ou chapitre précédent"> << </a>]</td>
<td valign="middle" align="left">[<a href="#SEC2" title="Section
supé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ères">Table des matiè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’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écédente dans l'ordre de lecture"> < </a>]</td>
-<td valign="middle" align="left">[<a href="#SEC5" title="Section suivante dans
l'ordre de lecture"> > </a>]</td>
+<tr><td valign="middle" align="left">[<a href="#SEC3" title="Section
précédente dans l’ordre de lecture"> < </a>]</td>
+<td valign="middle" align="left">[<a href="#SEC5" title="Section suivante dans
l’ordre de lecture"> > </a>]</td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left">[<a href="#SEC1" title="Début de ce
chapitre ou chapitre précédent"> << </a>]</td>
<td valign="middle" align="left">[<a href="#SEC3" title="Section
supé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ères">Table des matiè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’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écédente dans l'ordre de lecture"> < </a>]</td>
+<tr><td valign="middle" align="left">[<a href="#SEC4" title="Section
précédente dans l’ordre de lecture"> < </a>]</td>
<td valign="middle" align="left">[ > ]</td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left">[<a href="#SEC1" title="Début de ce
chapitre ou chapitre précédent"> << </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ères">Table des matiè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’aide)"> ? </a>]</td>
</tr></table>
<h1 class="centerchap" align="center"> 2. chapter 2 </h1>
@@ -2171,7 +2171,7 @@
</td></tr></table>
<table border="0" class="index-cp">
-<tr><td></td><th align="left">Entrée d'index</th><th align="left">
Section</th></tr>
+<tr><td></td><th align="left">Entrée d’index</th><th
align="left"> Section</th></tr>
<tr><td colspan="3"> <hr></td></tr>
<tr><th><a name="SEC5_0">"</a></th><td></td><td></td></tr>
<tr><td></td><td valign="top"><a href="#SEC_Top">“</a></td><td
valign="top"><a href="#SEC_Top">Top section</a></td></tr>
@@ -2238,7 +2238,7 @@
</td></tr></table>
<table border="0" class="index-fn">
-<tr><td></td><th align="left">Entrée d'index</th><th align="left">
Section</th></tr>
+<tr><td></td><th align="left">Entrée d’index</th><th
align="left"> Section</th></tr>
<tr><td colspan="3"> <hr></td></tr>
<tr><th><a name="SEC5_0">"</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ères">Table des matiè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’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ères">Table des matiè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’aide)"> ? </a>]</td>
</tr></table>
<h1>Table des matiè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ères">Table des matiè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’aide)"> ? </a>]</td>
</tr></table>
<h1>Résumé 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ères">Table des matiè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’aide)"> ? </a>]</td>
</tr></table>
<h1>A propos de ce document</h1>
<p>
@@ -2485,13 +2485,13 @@
<tr>
<td align="center"> [ < ] </td>
<td align="center">Retour</td>
- <td>Section précédente dans l'ordre de lecture</td>
+ <td>Section précédente dans l’ordre de lecture</td>
<td>1.2.2</td>
</tr>
<tr>
<td align="center"> [ > ] </td>
<td align="center">Avant</td>
- <td>Section suivante dans l'ordre de lecture</td>
+ <td>Section suivante dans l’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’aide)</td>
<td> </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ères"><img src="a_tableofcon.png" border="0" alt="Table des
matières: Table des matiè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’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>“simple-double–three—four—-”</strong> <br>
kbd: <kbd>``simple-double--three---four----''</kbd> <br>
</p>
-<p>``simple-double--three—four—-''<br>
+<p>‘‘simple-double--three—four—-’’<br>
</p>
<a name="IDX1"></a>
<a name="IDX2"></a>
@@ -555,16 +555,16 @@
@"{U} Ü
@~n ñ
@^a â
-@'e é
+@’e é
@=o ō
address@hidden ì
-@'{e} é
-@'address@hidden í
+@‘i ì
+@’{e} é
+@’address@hidden í
@dotless{i} i
@dotless{ij} ij
address@hidden@=E} Ē`
+@‘address@hidden Ē`
@l{} ł
-@,{@'C} Ć,
+@,{@’C} Ć,
@,c ç
@,c@"u çü <br>
</p>
@@ -573,10 +573,10 @@
<br>
@,@"u ,ü
</p>
-<p>Invalid use of @':<br>
-@' '
+<p>Invalid use of @’:<br>
+@’ ’
<br>
-@'@"u @'"u
+@’@"u @'"u
</p>
<p>@dotless{truc} truc
</p>
@@ -1029,9 +1029,9 @@
<dd><p>d–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—ef name@: (file
n—ame@)c—hapter@</a> section `t—itle@' dans
<cite>ma—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—ef name@: (file
n—ame@)c—hapter@</a> section ‘t—itle@’ dans
<cite>ma—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>
<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 ‘chapter’ 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 ‘node’ 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
‘chapter’ 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 ‘node’
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
‘title’ 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
‘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{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 ‘title’ 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 ‘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{,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 ‘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{,,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 ‘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{,,,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–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–ect,ion</a> section ‘a comma, in
title’ dans <cite>a , in manual name</cite>
</p>
<p><code>@address@hidden</code> <a href="#SEC2">A section</a>
</p>
@@ -1727,7 +1727,7 @@
</td></tr></table>
<table border="0" class="index-cp">
-<tr><td></td><th align="left">Entrée d'index</th><th align="left">
Section</th></tr>
+<tr><td></td><th align="left">Entrée d’index</th><th
align="left"> Section</th></tr>
<tr><td colspan="3"> <hr></td></tr>
<tr><th><a name="SEC_Top_0">"</a></th><td></td><td></td></tr>
<tr><td></td><td valign="top"><a href="#SEC_Top">“</a></td><td
valign="top"><a href="#SEC_Top">Top section</a></td></tr>
@@ -1796,7 +1796,7 @@
</td></tr></table>
<table border="0" class="index-fn">
-<tr><td></td><th align="left">Entrée d'index</th><th align="left">
Section</th></tr>
+<tr><td></td><th align="left">Entrée d’index</th><th
align="left"> Section</th></tr>
<tr><td colspan="3"> <hr></td></tr>
<tr><th><a name="SEC_Top_0">"</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 @@
</td></tr></table>
<table border="0" class="index-vr">
-<tr><td></td><th align="left">Entrée d'index</th><th align="left">
Section</th></tr>
+<tr><td></td><th align="left">Entrée d’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 @@
</td></tr></table>
<table border="0" class="index-tp">
-<tr><td></td><th align="left">Entrée d'index</th><th align="left">
Section</th></tr>
+<tr><td></td><th align="left">Entrée d’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écé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écé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>
<td valign="middle" align="left"> </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é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ères"><img src="a_tableofcon.png" border="0" alt="Table des
matières: Table des matiè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’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écé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écé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>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"><a href="#SEC1" title="Début de ce
chapitre ou chapitre précé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é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ères"><img src="a_tableofcon.png" border="0" alt="Table des
matières: Table des matiè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’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écé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écé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>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"><a href="#SEC1" title="Début de ce
chapitre ou chapitre précé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é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ères"><img src="a_tableofcon.png" border="0" alt="Table des
matières: Table des matiè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’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écé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écé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>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"><a href="#SEC1" title="Début de ce
chapitre ou chapitre précé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é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ères"><img src="a_tableofcon.png" border="0" alt="Table des
matières: Table des matiè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’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écé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écédente dans l’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"> </td>
<td valign="middle" align="left"><a href="#SEC1" title="Début de ce
chapitre ou chapitre précé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ères"><img src="a_tableofcon.png" border="0" alt="Table des
matières: Table des matiè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’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 @@
</td></tr></table>
<table border="0" class="index-cp">
-<tr><td></td><th align="left">Entrée d'index</th><th align="left">
Section</th></tr>
+<tr><td></td><th align="left">Entrée d’index</th><th
align="left"> Section</th></tr>
<tr><td colspan="3"> <hr></td></tr>
<tr><th><a name="SEC5_0">"</a></th><td></td><td></td></tr>
<tr><td></td><td valign="top"><a href="#SEC_Top">“</a></td><td
valign="top"><a href="#SEC_Top">Top section</a></td></tr>
@@ -2238,7 +2238,7 @@
</td></tr></table>
<table border="0" class="index-fn">
-<tr><td></td><th align="left">Entrée d'index</th><th align="left">
Section</th></tr>
+<tr><td></td><th align="left">Entrée d’index</th><th
align="left"> Section</th></tr>
<tr><td colspan="3"> <hr></td></tr>
<tr><th><a name="SEC5_0">"</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ères"><img src="a_tableofcon.png" border="0" alt="Table des
matières: Table des matiè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’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ères"><img src="a_tableofcon.png" border="0" alt="Table des
matières: Table des matiè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’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è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ères"><img src="a_tableofcon.png" border="0" alt="Table des
matières: Table des matiè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’aide)"><img src="a_help.png" border="0" alt="A propos: A propos de ce
document" align="middle"></a></td>
</tr></table>
<h1>Résumé 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ères"><img src="a_tableofcon.png" border="0" alt="Table des
matières: Table des matiè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’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écédente dans l'ordre de lecture</td>
+ <td>Section précédente dans l’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’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’aide)</td>
<td> </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’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
‘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>
</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 á </h2>
-<p>With brace á. Testing ' " ` ^.
+<p>With brace á. Testing ’ " ‘ ^.
</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 á </h2>
-<p>With brace á. Testing ' " ` ^.
+<p>With brace á. Testing ’ " ‘ ^.
</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 á </h2>
-<p>With brace á. Testing ' " ` ^.
+<p>With brace á. Testing ’ " ‘ ^.
</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>!_"#$%&'()*+-./;<=>?[\]^_`|~</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">!_"#$%&'()*+-./;<=>?[\]^_`|~</a><br>
+<p><tt>!_"#$%&'()*+-./;<=>?[\]^_`|~</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">!_"#$%&’()*+-./;<=>?[\]^_‘|~</a><br>
</p><table><tr><td> </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 á </h2>
-<p>With brace á. Testing ' " ` ^.
+<p>With brace á. Testing ’ " ‘ ^.
</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 á </h2>
-<p>With brace á. Testing ' " ` ^.
+<p>With brace á. Testing ’ " ‘ ^.
</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 á </h2>
-<p>With brace á. Testing ' " ` ^.
+<p>With brace á. Testing ’ " ‘ ^.
</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">•
!_"#$%&'()*+-./;<=>?[\]^_`|~</a></td><td> </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">•
!_"#$%&’()*+-./;<=>?[\]^_‘|~</a></td><td> </td><td
align="left" valign="top">
</td></tr>
<tr><td align="left" valign="top"><a href="local-node.html#local-node">•
local node</a></td><td> </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>“simple-double–three—four—-” `simple'
quotedblleft: “ <br>
+<p>“simple-double–three—four—-”
‘simple’ quotedblleft: “ <br>
code: <code>``simple-double--three---four----'' `simple' quotedblleft:
“</code> <br>
-asis: “simple-double–three—four—-” `simple'
quotedblleft: “ <br>
-strong: <strong>“simple-double–three—four—-”
`simple' quotedblleft: “</strong> <br>
+asis: “simple-double–three—four—-”
‘simple’ quotedblleft: “ <br>
+strong: <strong>“simple-double–three—four—-”
‘simple’ quotedblleft: “</strong> <br>
kbd: <kbd>``simple-double--three---four----'' `simple' quotedblleft:
“</kbd> <br>
samp: ‘<samp>``simple-double--three---four----'' `simple' quotedblleft:
“</samp>’ <br>
</p>
<table><tr><td> </td><td><pre class="example">@set txicodequoteundirected
@set txicodequotebacktick
</pre></td></tr></table>
-<p>“simple-double–three—four—-” `simple'
quotedblleft: “ <br>
+<p>“simple-double–three—four—-”
‘simple’ quotedblleft: “ <br>
code: <code>``simple-double--three---four----'' `simple' quotedblleft:
“</code> <br>
-asis: “simple-double–three—four—-” `simple'
quotedblleft: “ <br>
-strong: <strong>“simple-double–three—four—-”
`simple' quotedblleft: “</strong> <br>
+asis: “simple-double–three—four—-”
‘simple’ quotedblleft: “ <br>
+strong: <strong>“simple-double–three—four—-”
‘simple’ quotedblleft: “</strong> <br>
kbd: <kbd>``simple-double--three---four----'' `simple' quotedblleft:
“</kbd> <br>
samp: ‘<samp>``simple-double--three---four----'' `simple' quotedblleft:
“</samp>’ <br>
</p>
<table><tr><td> </td><td><pre class="example">@clear
txicodequoteundirected
@clear txicodequotebacktick
</pre></td></tr></table>
-<p>“simple-double–three—four—-” `simple'
quotedblleft: “ <br>
+<p>“simple-double–three—four—-”
‘simple’ quotedblleft: “ <br>
code: <code>``simple-double--three---four----'' `simple' quotedblleft:
“</code> <br>
-asis: “simple-double–three—four—-” `simple'
quotedblleft: “ <br>
-strong: <strong>“simple-double–three—four—-”
`simple' quotedblleft: “</strong> <br>
+asis: “simple-double–three—four—-”
‘simple’ quotedblleft: “ <br>
+strong: <strong>“simple-double–three—four—-”
‘simple’ quotedblleft: “</strong> <br>
kbd: <kbd>``simple-double--three---four----'' `simple' quotedblleft:
“</kbd> <br>
samp: ‘<samp>``simple-double--three---four----'' `simple' quotedblleft:
“</samp>’ <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>!_"#$%&'()*+-./;<=>?[\]^_`|~</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">!_"#$%&'()*+-./;<=>?[\]^_`|~</a><br>
+<p><tt>!_"#$%&'()*+-./;<=>?[\]^_`|~</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">!_"#$%&’()*+-./;<=>?[\]^_‘|~</a><br>
</p><table><tr><td> </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">•
!_"#$%&'()*+-./;<=>?[\]^_`|~</a></td><td> </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">•
!_"#$%&’()*+-./;<=>?[\]^_‘|~</a></td><td> </td><td
align="left" valign="top">
</td></tr>
<tr><td align="left" valign="top"><a href="#local-node">• local
node</a></td><td> </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>
ō
</p>
-<p>I don't know any invalid macron:<br>
+<p>I don’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> </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> </td><td align="left" valign="top"> node with
braces
+<tr><td align="left" valign="top"><a href="#SEC2">2. node ’a with
braces</a></td><td> </td><td align="left" valign="top"> node with
braces
</td></tr>
<tr><td align="left" valign="top"><a href="manual.html#A-node">• node:
(manual)A node</a></td><td> </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> </td><td align="left" valign="top">
node without braces
+</pre></th></tr><tr><td align="left" valign="top"><a href="#SEC3">3. node
’a without braces</a></td><td> </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’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’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’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’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 ’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’t 2 paragraphes in the
footnote
+in that case in info. tex doesn’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 ’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> </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 ’a with braces</a></li>
+ <li><a name="TOC3" href="#SEC3">3. node ’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>“simple-double–three—four—-”</strong> <br>
kbd: <kbd>``simple-double--three---four----''</kbd> <br>
</p>
-<p>``simple-double--three—four—-''<br>
+<p>‘‘simple-double--three—four—-’’<br>
</p>
<a name="IDX1"></a>
<a name="IDX2"></a>
@@ -555,16 +555,16 @@
@"{U} Ü
@~n ñ
@^a â
-@'e é
+@’e é
@=o ō
address@hidden ì
-@'{e} é
-@'address@hidden í
+@‘i ì
+@’{e} é
+@’address@hidden í
@dotless{i} i
@dotless{ij} ij
address@hidden@=E} Ē`
+@‘address@hidden Ē`
@l{} ł
-@,{@'C} Ć,
+@,{@’C} Ć,
@,c ç
@,c@"u çü <br>
</p>
@@ -573,10 +573,10 @@
<br>
@,@"u ,ü
</p>
-<p>Invalid use of @':<br>
-@' '
+<p>Invalid use of @’:<br>
+@’ ’
<br>
-@'@"u @'"u
+@’@"u @'"u
</p>
<p>@dotless{truc} truc
</p>
@@ -1029,9 +1029,9 @@
<dd><p>d–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—ef name@: (file
n—ame@)c—hapter@</a> section `t—itle@' in
<cite>ma—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—ef name@: (file
n—ame@)c—hapter@</a> section ‘t—itle@’ in
<cite>ma—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>
<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 ‘chapter’ 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 ‘node’ 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
‘chapter’ 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 ‘node’ 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
‘title’ 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
‘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{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 ‘title’ 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 ‘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{,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 ‘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{,,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 ‘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{,,,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–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–ect,ion</a> section ‘a comma, in
title’ 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"> !_"#$%&'()*+-./;<=>?[\]^_`|~ </h3>
+<h3 class="node"> !_"#$%&’()*+-./;<=>?[\]^_‘|~ </h3>
<table><tr><td> </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>!_"#$%&'()*+-./;<=>?[\]^_`|~</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">!_"#$%&'()*+-./;<=>?[\]^_`|~</a><br>
+<p><tt>!_"#$%&'()*+-./;<=>?[\]^_`|~</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">!_"#$%&’()*+-./;<=>?[\]^_‘|~</a><br>
</p><table><tr><td> </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">•
!_"#$%&'()*+-./;<=>?[\]^_`|~</a></td><td> </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">•
!_"#$%&’()*+-./;<=>?[\]^_‘|~</a></td><td> </td><td
align="left" valign="top">
</td></tr>
<tr><td align="left" valign="top"><a href="#local-node">• local
node</a></td><td> </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">•
!_"#$%&'()*+-./;<=>?[\]^_`|~</a></td><td> </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">•
!_"#$%&’()*+-./;<=>?[\]^_‘|~</a></td><td> </td><td
align="left" valign="top">
</td></tr>
<tr><td align="left" valign="top"><a href="local-node.html#local-node">•
local node</a></td><td> </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>!_"#$%&'()*+-./;<=>?[\]^_`|~</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">!_"#$%&'()*+-./;<=>?[\]^_`|~</a><br>
+<p><tt>!_"#$%&'()*+-./;<=>?[\]^_`|~</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">!_"#$%&’()*+-./;<=>?[\]^_‘|~</a><br>
</p><table><tr><td> </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"> !_"#$%&'()*+-./;<=>?[\]^_`|~ </h3>
+<h3 class="node"> !_"#$%&’()*+-./;<=>?[\]^_‘|~ </h3>
<table><tr><td> </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>!_"#$%&'()*+-./;<=>?[\]^_`|~</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">!_"#$%&'()*+-./;<=>?[\]^_`|~</a><br>
+<p><tt>!_"#$%&'()*+-./;<=>?[\]^_`|~</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">!_"#$%&’()*+-./;<=>?[\]^_‘|~</a><br>
</p><table><tr><td> </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">•
!_"#$%&'()*+-./;<=>?[\]^_`|~</a></td><td> </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">•
!_"#$%&’()*+-./;<=>?[\]^_‘|~</a></td><td> </td><td
align="left" valign="top">
</td></tr>
<tr><td align="left" valign="top"><a href="#local-node">• local
node</a></td><td> </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">•
!_"#$%&'()*+-./;<=>?[\]^_`|~</a></td><td> </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">•
!_"#$%&’()*+-./;<=>?[\]^_‘|~</a></td><td> </td><td
align="left" valign="top">
</td></tr>
<tr><td align="left" valign="top"><a href="local-node.html#local-node">•
local node</a></td><td> </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>!_"#$%&'()*+-./;<=>?[\]^_`|~</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">!_"#$%&'()*+-./;<=>?[\]^_`|~</a><br>
+<p><tt>!_"#$%&'()*+-./;<=>?[\]^_`|~</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">!_"#$%&’()*+-./;<=>?[\]^_‘|~</a><br>
</p><table><tr><td> </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"> !_"#$%&'()*+-./;<=>?[\]^_`|~ </h3>
+<h3 class="node"> !_"#$%&’()*+-./;<=>?[\]^_‘|~ </h3>
<table><tr><td> </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>!_"#$%&'()*+-./;<=>?[\]^_`|~</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">!_"#$%&'()*+-./;<=>?[\]^_`|~</a><br>
+<p><tt>!_"#$%&'()*+-./;<=>?[\]^_`|~</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">!_"#$%&’()*+-./;<=>?[\]^_‘|~</a><br>
</p><table><tr><td> </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">•
!_"#$%&'()*+-./;<=>?[\]^_`|~</a></td><td> </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">•
!_"#$%&’()*+-./;<=>?[\]^_‘|~</a></td><td> </td><td
align="left" valign="top">
</td></tr>
<tr><td align="left" valign="top"><a href="#local-node">• local
node</a></td><td> </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">•
!_"#$%&'()*+-./;<=>?[\]^_`|~</a></td><td> </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">•
!_"#$%&’()*+-./;<=>?[\]^_‘|~</a></td><td> </td><td
align="left" valign="top">
</td></tr>
<tr><td align="left" valign="top"><a href="local-node.html#local-node">•
local node</a></td><td> </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>!_"#$%&'()*+-./;<=>?[\]^_`|~</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">!_"#$%&'()*+-./;<=>?[\]^_`|~</a><br>
+<p><tt>!_"#$%&'()*+-./;<=>?[\]^_`|~</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">!_"#$%&’()*+-./;<=>?[\]^_‘|~</a><br>
</p><table><tr><td> </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’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’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 of the line
</p>
-<p> now a bad accent `
+<p> now a bad accent ‘
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>—————————————
</p>
-<p>makeinfo result (the comma don't separate args ; the value is expanded after
+<p>makeinfo result (the comma don’t separate args ; the value is
expanded after
arguments parsing):
</p>
<p>result: <em>arg1 , arg2 </em> protected \ -> \arg1\ <em></em>
@@ -245,8 +245,8 @@
</p>
<p>———————————-
</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’t expanded
+when the body is expanded; it is kept, but the second \ isn’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 á </h2>
-<p>With brace á. Testing ' " ` ^.
+<p>With brace á. Testing ’ " ‘ ^.
</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 á </h2>
-<p>With brace á. Testing ' " ` ^.
+<p>With brace á. Testing ’ " ‘ ^.
</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 á </h2>
-<p>With brace á. Testing ' " ` ^.
+<p>With brace á. Testing ’ " ‘ ^.
</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 á </h2>
-<p>With brace á. Testing ' " ` ^.
+<p>With brace á. Testing ’ " ‘ ^.
</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 á </h2>
-<p>With brace á. Testing ' " ` ^.
+<p>With brace á. Testing ’ " ‘ ^.
</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’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 ‘<code>expose</code> on
+<code>windows</code>’, 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
‘<code>bar-method</code> on
+<code>bar-class</code>’, 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 ‘Command Line Switches and Arguments’ in
<cite>The GNU Emacs Manual</cite>.)
</p>
<p>Here is a shell command to format all the files that end in
‘<tt>.texinfo</tt>’ 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> </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> </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
‘Top’ Node and Master Menu</a></td><td> </td><td
align="left" valign="top"> Creating the ‘Top’ 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> </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 ‘wrong’ 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 ‘Function and Concept Index’ and not printing the
‘Function
+Index’ 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 ‘NASA’. 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 ‘subsub’ 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 (“as is”).
+print the table’s first column without highlighting (“as
is”).
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’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 ‘End’ node or
‘Separate’ 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
‘<samp>end</samp>’ for the end
+<dd><p>Specify an Info file’s footnote style, either
‘<samp>end</samp>’ for the end
node style or ‘<samp>separate</samp>’ 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, ‘-’. 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 ‘see’ in a
printed
manual. Use within parentheses only. Do not follow command with a
punctuation mark—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 ‘See’. 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
‘subsub’ 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 ‘subsub’
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 ‘Chapter 1: Title’), 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>.
+‘oo[’. 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 ‘1 Jan 1900’ 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>’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 ‘subsub’
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 ‘See’ 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> ⇒ ‘<samp>…</samp>’,
<code>@equiv{}</code>
-⇒ ‘<samp>≡</samp>’, <code>@TeX{}</code> ⇒ `TeX',
+⇒ ‘<samp>≡</samp>’, <code>@TeX{}</code> ⇒
‘TeX’,
and <code>@bullet{}</code> ⇒ ‘<samp>•</samp>’.
</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’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 ‘subsub’
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 ‘First’
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
‘<samp>definfoenclose</samp>’: 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’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> (→):
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
‘Compilation’ 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’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>``…''</tt>. This
+begin and end quotations: <tt>‘‘…’’</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>``…''</tt> becomes <tt>"…"</tt>.
+double-quotes: <tt>‘‘…’’</tt> becomes
<tt>"…"</tt>.
</li><li>
Use three hyphens in a row, ‘<samp>---</samp>’, for a
dash—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 …'
+<dd><p>Used to start a sentence in the printed manual saying ‘See
…’
or an Info cross-reference saying ‘<samp>*Note <var>name</var>:
<var>node</var>.</samp>’.
</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 ‘See’.
</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. (‘<samp>p</samp>’ is for `parenthesis'.)
+file and a printed book. Starts with a lower case ‘see’ within the
+printed manual. (‘<samp>p</samp>’ is for
‘parenthesis’.)
</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> </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> </td><td align="left" valign="top">
Begin a reference with `See' …
+<tr><td align="left" valign="top"><a href="xref.html#SEC108">8.3
<code>@xref</code></a></td><td> </td><td align="left" valign="top">
Begin a reference with ‘See’ …
</td></tr>
-<tr><td align="left" valign="top"><a href="Top-Node-Naming.html#SEC114">8.4
Naming a `Top' Node</a></td><td> </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 ‘Top’ Node</a></td><td> </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> </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’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 ‘every’ 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 ‘even’ and ‘odd’ 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 ‘Chapter 1: Title’.
</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 ‘1 Jan 1900’ 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 ‘s’ on the end, instead of with <code>@end
menu</code>, you
will see an error message that says:
</p>
<table><tr><td> </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 <TAB> <RET></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 ‘Catching Mistakes’ node. (If you try this, you can
return
+from the ‘Catching Mistakes’ 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 ‘Interactive Command’,
write braces around it. For example:
</p>
<table><tr><td> </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
‘<samp>@macro</samp>’ instead of
+<p>This produces the output ‘a1atextb2b’. With
‘<samp>@macro</samp>’ instead of
‘<samp>@rmacro</samp>’, 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> </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> </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> </td><td align="left" valign="top">
Using a macro, once you’ve defined it.
</td></tr>
<tr><td align="left" valign="top"><a href="Macro-Details.html#SEC241">18.3
Macro Details</a></td><td> </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—`Function', `Variable', or whatever—to appear at the
+category—‘Function’, ‘Variable’, or
whatever—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’s name and arguments. In the printed manual, the command
+causes TeX to print the entity’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> </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> </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 ‘First’ Lines</a></td><td> </td><td align="left"
valign="top"> How to group two or more ‘first’
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> </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 @@
…
</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 ‘Top’ 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 ‘Top’ node, since Info goes to the ‘Top’
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 ‘<samp>Info</samp>’ entry points to the `Top' node of
the
-‘<tt>info</tt>’ file and the ‘<samp>Emacs</samp>’
entry points to the `Top' node
+<p>Thus, the ‘<samp>Info</samp>’ entry points to the
‘Top’ node of the
+‘<tt>info</tt>’ file and the ‘<samp>Emacs</samp>’
entry points to the ‘Top’ node
of the ‘<tt>emacs</tt>’ 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 ‘Up’ pointer of the
‘Top’ node refers
+back to the <code>dir</code> file. For example, the line for the
‘Top’
node of the Emacs manual looks like this in Info:
</p>
<table><tr><td> </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> </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> </td><td align="left" valign="top">
Declare the document’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> </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’ 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 ‘Pages’
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 @@
‘<samp>.</samp>’; 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
‘Sentences’ 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
‘<samp>error--></samp>’ in Info
-and as the word `error' in a box in the printed output.
+and as the word ‘error’ 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 ‘Top’ 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 ‘<samp>top</samp>’ or
‘<samp>Top</samp>’) should have
-as its `Up' node the name of a node in another file, where there is a
+as its ‘Up’ 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 ‘Previous’ node of the Top
node to
be ‘<samp>(dir)</samp>’, as it causes confusing behavior for
users: if you are
in the Top node and hits <DEL> to go backwards, you wind up in the
middle of the some other entry in the ‘<tt>dir</tt>’ 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 ‘Next’ 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, ‘<samp>.};</samp>’ 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’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:
‘<samp>(1)</samp>’. 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’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 ‘End’ 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
‘<samp>Footnotes</samp>’ 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 ‘Separate’ node style, all the footnotes for a single
node are placed in an automatically constructed node of
their own. In this style, a “footnote reference” follows
each ‘<samp>(<var>n</var>)</samp>’ reference mark in the body of
the
@@ -111,10 +111,10 @@
<p>The name of the node with the footnotes is constructed
by appending ‘<samp>-Footnotes</samp>’ to the name of the node
-that contains the footnotes. (Consequently, the footnotes'
+that contains the footnotes. (Consequently, the footnotes’
node for the ‘<tt>Footnotes</tt>’ node is
-‘<tt>Footnotes-Footnotes</tt>’!) The footnotes' node has an
-`Up' node pointer that leads back to its parent node.
+‘<tt>Footnotes-Footnotes</tt>’!) The footnotes’ node has an
+‘Up’ 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’s
footnote style. Write this command at the beginning of a line followed
by an argument, either ‘<samp>end</samp>’ for the end node style or
‘<samp>separate</samp>’ 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 ‘separate’ style and
+<code>makeinfo</code> uses the ‘end’ 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 ‘<samp>.tex</samp>’ (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 ‘<samp>.tex</samp>’ (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.
For example, the raw index output files for the input file
‘<tt>foo.texinfo</tt>’ would be ‘<tt>foo.cp</tt>’,
‘<tt>foo.vr</tt>’, ‘<tt>foo.fn</tt>’,
‘<tt>foo.tp</tt>’, ‘<tt>foo.pg</tt>’ and
‘<tt>foo.ky</tt>’. 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’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’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> … <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’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>…</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 ‘Special Forms’ in <cite>GNU Emacs Lisp Reference
Manual</cite>.)
<code>@defspec</code> is equivalent to ‘<samp>@deffn {Special Form}
…</samp>’ 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 “Secondary Section” 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’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, “Title Page”
means
-the text near the most prominent appearance of the work's title,
+the text near the most prominent appearance of the work’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’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’s license notice.
</li><li>
Include an unaltered copy of this License.
@@ -298,7 +298,7 @@
</li><li>
In any section entitled “Acknowledgments” or
“Dedications”,
-preserve the section's title, and preserve in the section all the
+preserve the section’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’s license notice.
These titles must be distinct from any other section titles.
</p>
<p>You may add a section entitled “Endorsements”, 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’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’re not
+familiar with all these different elements, don’t worry. They’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’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 ‘<samp>Id: texinfo.txi,v 1.2 2003/02/24 18:17:06 pertusus Exp
$</samp>’ 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 ‘<samp>Id: texinfo.txi,v 1.2 2003/02/24 18:17:06 pertusus Exp
$</samp>’ 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
systems, which expand it into a string such as:
<table><tr><td> </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 ‘<tt>version.texi</tt>’ 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 ‘<samp>VERSION</samp>’ and
‘<samp>UPDATED</samp>’ 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
‘Introduction’ in <cite>GNU Automake</cite>). It sets the
‘<samp>VERSION</samp>’ and ‘<samp>UPDATED</samp>’
values used
+elsewhere. If your distribution doesn’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 ‘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>.
</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’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> </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> </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> </td><td align="left" valign="top">
How to print using Emacs’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> </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’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 ‘<tt><var>filename</var>.pdf</tt>’ (Adobe's Portable
Document Format).
+PDFTeX reads ‘<tt><var>filename</var>.pdf</tt>’ (Adobe’s
Portable Document Format).
</li><li>
<code>makeinfo</code> uses ‘<tt><var>filename</var>.txt</tt>’
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 ‘Top’
node. It
+should <em>not</em> contain any nodes besides the single ‘Top’
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’ 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’
indices.
</p>
-<p>If you don't see how to make an entry terse yet clear, make it longer
+<p>If you don’t see how to make an entry terse yet clear, make it longer
and clear—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 “Function Index” as an unnumbered
-chapter, you could give it the title `Function and Macro Index' and
+chapter, you could give it the title ‘Function and Macro Index’ 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’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 ‘Next’ and ‘Previous’ pointers.
The ‘Next’
+pointer provides a link to the next section, and the ‘Previous’
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’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’
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 ‘Up’, ‘Previous’, and
‘Next’ 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 ‘Next’, ‘Previous’, and
‘Up’ 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 ‘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
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
‘Top’ 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 <SPC> repeatedly, or you get the whole
@@ -151,7 +151,7 @@
</p>
<p>The ‘<tt>dir</tt>’ file in the ‘<tt>info</tt>’
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.
+‘Top’ 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’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>@"o</tt> </p></td><td><p> ö
</p></td><td><p> umlaut accent
</p></td></tr>
-<tr><td><p> <tt>@'o</tt> </p></td><td><p> ó
</p></td><td><p> acute accent
+<tr><td><p> <tt>@’o</tt> </p></td><td><p> ó
</p></td><td><p> acute accent
</p></td></tr>
<tr><td><p> <tt>@,{c}</tt> </p></td><td><p> ç
</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> ô
</p></td><td><p> circumflex accent
</p></td></tr>
-<tr><td><p> <tt>@`o</tt> </p></td><td><p> ò
</p></td><td><p> grave accent
+<tr><td><p> <tt>@‘o</tt> </p></td><td><p> ò
</p></td><td><p> grave accent
</p></td></tr>
<tr><td><p> <tt>@~o</tt> </p></td><td><p> õ
</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> </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> </td><td align="left" valign="top">
Sometimes a . doesn’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> </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 ‘Next’,
+‘Previous’, and ‘Up’ 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’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’s what this produces in the Info file:
</p>
<table><tr><td> </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 ‘current’ 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 ‘Invoking’ node for every program
installed
+by a package under ‘Individual utilities’, 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 ‘<tt>dir</tt>’ file in the Info system (see the previous
sections
-for an explanation of how the ‘<tt>dir</tt>’ file works). It's
most often
+for an explanation of how the ‘<tt>dir</tt>’ file works).
It’s most often
run as part of software installation, or when constructing a
‘<tt>dir</tt>’ 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
‘Invoking gzip’ 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 ‘<samp>.info</samp>’ in either one). Don't insert any
new entries.
+an optional ‘<samp>.info</samp>’ in either one). Don’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’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’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’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’s copyright page:
</p>
<table><tr><td> </td><td><pre class="example">This is edition 2.0 of the
Texinfo documentation,@*
and is for …
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’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’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’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 ‘<samp><head></samp>’ in HTML format. Strictly
speaking, <code>@settitle</code>
-is optional—if you don't mind your document being titled `Untitled'.
+is optional—if you don’t mind your document being titled
‘Untitled’.
</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> </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 ‘some text
for
+column one’, and the second column the width of ‘for column
two’.
</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
‘Splitting Windows’ in <cite>The GNU Emacs Manual</cite>):
</p>
<table><tr><td> </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 “root” is at the top of the diagram and the
“leaves” 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 ‘Top’ node, and ‘Up’ node pointers carry
you closer to the
root.
</p>
<table><tr><td> </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
“Chapter
-2”, the name of the `Next' node is “Chapter 3”, the name of
the
-`Previous' node is “Chapter 1”, and the name of the `Up' node is
+2”, the name of the ‘Next’ node is “Chapter 3”,
the name of the
+‘Previous’ node is “Chapter 1”, and the name of the
‘Up’ node is
“Top”. 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> ‘Next’ 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—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. ‘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
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 ‘Next’ and ‘Previous’ pointers
of a node usually
lead to other nodes at the same level—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 ‘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;
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’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
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’s ‘Previous’ node is the same as its ‘Up’
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 ‘<tt>dir</tt>’ file,
which
+<p>Usually, the first node of a Texinfo file is the ‘Top’ node,
and its
+‘Up’ and ‘Previous’ pointers point to the
‘<tt>dir</tt>’ 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 ‘Top’ 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
+‘Top’ 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 @@
‘<tt>/home/bob/info/info-test</tt>’ file as a menu entry in the
‘<tt>/home/bob/info/dir</tt>’ 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’ve
already run
<code>info</code>, you must <code>(setq Info-dir-contents nil)</code> to force
Emacs
to recompose the ‘<tt>dir</tt>’ file.
</p>
@@ -172,7 +172,7 @@
</li></ul>
<p>The ‘<samp>.</samp>’ 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’s
own <code>Info-directory-list</code> variable. The stand-alone Info reader
merges any files named ‘<tt>dir</tt>’ 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 ‘<tt>dir</tt>’ 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’s easiest
to start by
copying an existing ‘<tt>dir</tt>’ file and replace all the text
after the
‘<samp>* Menu:</samp>’ 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 ‘Top’ node.
</p>
<p>The ‘<tt>dir</tt>’ 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
‘Top’
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 ‘Next’, ‘Previous’,
and ‘Up’ 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 ‘Next’ or ‘Previous’ pointers
regardless of those
+nodes’ hierarchical level. This means that the ‘Next’ 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’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 ‘<samp>pdftex foo.texi</samp>’ instead
of ‘<samp>tex
foo.texi</samp>’, or give the ‘<samp>--pdf</samp>’ 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 ‘Portable Document Format’. 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 @@
‘<samp>@ifpdf</samp>’ or ‘<samp>@pdf</samp>’ commands
as with the other output
formats.
</p>
-<p>Despite the `portable' in the name, PDF files are nowhere near as
+<p>Despite the ‘portable’ 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 ‘Next’, ‘Previous’, or ‘Up’ node
reference is a reference to a
node in the current file and is not an external reference such as to
‘<tt>(dir)</tt>’, 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 ‘Previous’ node is different from the
‘Up’ node,
+then the node pointed to by the ‘Previous’ field must have a
‘Next’
field which points back to this node.
</li><li>
-Every node except the `Top' node must have an `Up' pointer.
+Every node except the ‘Top’ node must have an ‘Up’
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 ‘Up’ pointer must itself reference the
current
+node through a menu item, unless the node referenced by ‘Up’
+has the form ‘(<var>file</var>)’.
</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 ‘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.
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 ‘Top’ should be referenced by at least one other
node,
+either via the ‘Previous’ or ‘Next’ 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 ‘<tt>\input</tt>’
file first
in the current directory, indicated by the ‘<samp>.</samp>’, then
in a
-hypothetical user's ‘<tt>me/mylib</tt>’ directory, and finally in
a system
+hypothetical user’s ‘<tt>me/mylib</tt>’ directory, and
finally in a system
directory ‘<tt>/usr/lib/tex/macros</tt>’.
</p>
<a name="IDX341"></a>
<a name="IDX342"></a>
-<p>Finally, you may wish to dump a ‘<tt>.fmt</tt>’ 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 ‘<tt>.fmt</tt>’ 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
disadvantage is that then updating ‘<tt>texinfo.tex</tt>’ requires
redumping.) You can do this by running this command, assuming
‘<tt>epsf.tex</tt>’ 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’t support the
‘<samp>-d</samp>’ 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 ‘dvips invocation’ 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
‘<samp>PRN</samp>’.
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
‘TeX Mode’ 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> </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> </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’s
Indentation</a></td><td> </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> </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 ‘chapters’ reproduces chapter
commands; an
+attempt to lower below ‘subsubsections’ 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’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
-‘<samp>diff -c</samp>’ (see <a
href="../diffutils/index.html#Top">(diffutils)Top</a> section `Overview' in
<cite>Comparing and Merging Files</cite>) and include
‘<tt>ChangeLog</tt>’ entries (see <a
href="../emacs/Change-Log.html#Change-Log">(emacs)Change Log</a> section
`Change Log' in <cite>The GNU Emacs Manual</cite>).
+‘<samp>diff -c</samp>’ (see <a
href="../diffutils/index.html#Top">(diffutils)Top</a> section
‘Overview’ in <cite>Comparing and Merging Files</cite>) and include
‘<tt>ChangeLog</tt>’ entries (see <a
href="../emacs/Change-Log.html#Change-Log">(emacs)Change Log</a> section
‘Change Log’ 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’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’s
processing and forces out unfinished pages:
</p>
<table><tr><td> </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 ‘Next’, ‘Previous’, ‘Up’ 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 ‘Calling Functions’ in <cite>The GNU Emacs
Lisp Reference Manual</cite>.
</p>
<blockquote><dl>
<dt><u>Function:</u> <b>apply</b><i> function &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: ‘Top’ Node and Master Menu </h3>
-<p>The `Top' node contains the master menu for the Info file. Since a
+<p>The ‘Top’ 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 ‘Next’,
‘Previous’, and ‘Up’
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
‘Narrowing’ 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
‘Pages’ 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. ‘Top’ Node and Master Menu</span></dt>
+<dd><p>The ‘Top’ 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—but it's usually
+letters from ‘jumping out at you on the page’. This makes small
caps
+text easier to read than text in all upper case—but it’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’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 ‘abort to
orbit’).
</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 “General Public
License” 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 ‘Top’ 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—but you don't need to.
+heading at the top of each node—but you don’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> </td><td align="left"
valign="top"> A manual is like an upside down tree …
</td></tr>
<tr><td align="left" valign="top"><a
href="Structuring-Command-Types.html#SEC74">5.2 Structuring Command
Types</a></td><td> </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> </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> </td><td align="left" valign="top">
The <code>@top</code> command, part of the ‘Top’ node.
</td></tr>
<tr><td align="left" valign="top"><a href="chapter.html#SEC76">5.4
<code>@chapter</code></a></td><td> </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> </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> </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
‘subsub’ Commands</a></td><td> </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> </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> </td><td align="left"
valign="top"> How to change commands’ 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, `©', is also special.
+<p>The logo ‘TeX’ is typeset in a special fashion and it needs an
address@hidden The copyright symbol, ‘©’, is also special.
Each of these commands is followed by a pair of braces,
‘<samp>{}</samp>’,
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 ‘<tt>.emacs</tt>’ 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
‘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 ‘<tt>.emacs</tt>’ 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>).
</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 ‘Easy Customization Interface’ in
<cite>The GNU Emacs Manual</cite>, for more details about this. The Texinfo
variables can
be found in the ‘<samp>Development/Docs/Texinfo</samp>’ 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 ‘custom insert’,
but
<kbd>C-c C-c</kbd> is quick to type.)
</p>
<table><tr><td> </td><td><pre class="example">C-c C-c c <span
class="roman">Insert</span> ‘<samp>@code</samp>’.
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’ 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">•
Texinfo Mode Overview</a></td><td> </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> </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> </td><td align="left"
valign="top"> Texinfo mode adds to GNU Emacs’ 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> </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 ‘Next’,
+‘Previous’, and ‘Up’ 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 ‘Top’ Node and Master Menu </h2>
-<p>The `Top' node is the node in which a reader enters an Info manual. As
+<p>The ‘Top’ 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 ‘Top’ 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’s Guide</cite>:
</p>
<table><tr><td> </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>‘C-x v’ ‘M-x vc-next-action’ 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 ‘Invoking’, as in ‘Invoking Emacs’; 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’s calling
conventions, use the ANSI C syntax, like this:
</p>
<table><tr><td> </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 ‘it’ 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’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 ‘<samp>X</samp>’ were a Greek `chi', as
the last
-sound in the name `Bach'. But pronounce Texinfo as in `speck':
+Pronounce TeX as if the ‘<samp>X</samp>’ were a Greek
‘chi’, as the last
+sound in the name ‘Bach’. But pronounce Texinfo as in
‘speck’:
“teckinfo”.
</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’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 ‘Top’ 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 ‘Top’ 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 ‘Top’), 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>’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
‘procedure’ 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 “update” 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 ‘Next’,
+‘Previous’, and ‘Up’ 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 ‘Next’, ‘Previous’, and
‘Up’ 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 ‘Top’ <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 ‘Top’
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 ‘Top’
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.
+‘Top’ 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 ‘Next’, ‘Previous’, and ‘Up’
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 ‘Next’,
‘Previous’, or ‘Up’
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 ‘Next’, ‘Previous’, and
‘Up’ 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 ‘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>).
</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 ‘jump down’
+more than one level at a time: you can follow the ‘Top’ 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 ‘jump up’ any
number of levels at one time—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
‘Top’
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, ‘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
<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
‘<samp>top</samp>’ or ‘<samp>Top</samp>’
+<p>If a file has a ‘Top’ node, it must be called
‘<samp>top</samp>’ or ‘<samp>Top</samp>’
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 ‘Top’ 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 ‘Next’,
‘Previous’ and
+‘Up’ 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 ‘Next’,
‘Previous’, and ‘Up’
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 ‘Next’,
+‘Previous’, and ‘Up’ 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
+‘I’. 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 “File
appears
@@ -102,19 +102,19 @@
<table><tr><td> </td><td><pre class="example">In node
"Overview", invalid Next: Texinfo Mode
</pre></td></tr></table>
-<p>This meant that the node called ‘<samp>Overview</samp>’ had a
`Next' pointer that
+<p>This meant that the node called ‘<samp>Overview</samp>’ had a
‘Next’ 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 ‘<samp>Texinfo Mode</samp>’ to
our test case
-but we do not specify a `Previous' for this node. Then we will get
+but we do not specify a ‘Previous’ for this node. Then we will get
the following error message:
</p>
<table><tr><td> </td><td><pre class="example">In node "Texinfo
Mode", 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 ‘Next’ pointer should be matched by a
+‘Previous’ (in the node where the ‘Next’ 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’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’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 ‘<samp>--help</samp>’ 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’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 ‘Regular
Expressions’ 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 ‘<samp>$</samp>’; for example,
‘<samp>catching mistakes$</samp>’. 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 ‘Up’ 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 ‘Using Occur’ 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
‘<samp>*Occur*</samp>’
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 ‘Using Occur’ in <cite>The GNU Emacs
Manual</cite>, for more
information about <code>occur-mode-goto-occurrence</code>.
</p>
<p>The first line in the ‘<samp>*Occur*</samp>’ 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
‘Using Regular Expressions’ 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 ‘Narrowing’ 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 ‘<samp>@defvr {User
+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 ‘<samp>@defvr {User
Option} …</samp>’ 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 ‘Next’,
‘Previous’, and ‘Up’
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
‘<samp>@node</samp>’ 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 ‘Next’,
‘Previous’,
+and ‘Up’ pointers looks like this:
</p>
<table><tr><td> </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’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 ‘<acronym>NASA</acronym>’. The
abbreviation is given as
the single argument in braces, as in
‘<samp>@acronym{NASA}</samp>’. As
a matter of style, or for particular abbreviations, you may prefer to
use periods, as in ‘<samp>@acronym{F.B.I.}</samp>’.
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’d do this as follows:
</p>
<table><tr><td> </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 ‘x-spot’ just before the word
‘spot’.
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’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 ‘goto-node’ 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 ‘Emacs’ or ‘Bison’.
</p>
<p>When writing an entire shell command invocation, as in ‘<samp>ls
-l</samp>’,
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’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’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 ‘Copyright’ 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 ‘Free
+Software Foundation, Inc.’.
</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 ‘Copyright Notices’ 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>{} (©) </h3>
-<p>Use the <code>@copyright{}</code> command to generate `©'. In
+<p>Use the <code>@copyright{}</code> command to generate ‘©’.
In
a printed manual, this is a ‘<samp>c</samp>’ inside a circle, and
in Info,
this is ‘<samp>(C)</samp>’.
</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 ‘First’ Lines </h2>
-<p>To create two or more `first' or header lines for a definition, follow
+<p>To create two or more ‘first’ 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 …
</p></dd></dl>
-<p>Each definition command has an `x' form: <code>@defunx</code>,
+<p>Each definition command has an ‘x’ 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 ‘x’ 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 ‘//’ before and ‘\\’
after the argument
to <code>@phoo</code>. You can then write <code>@phoo{bar}</code> wherever you
-want `//bar\\' highlighted in Info.
+want ‘//bar\\’ 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 ‘<tt>txi-<var>cc</var>.tex</tt>’ 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 ‘Chapter’, ‘See’, 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’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>{} (…) 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: `…'. Do
+three dots in a row, appropriately spaced, like this: ‘…’.
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 ‘Caution’ 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’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 ‘large’ and ‘small’ model:
</p>
<a name="IDX295"></a>
<table><tr><td> </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’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>
<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’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
-‘<samp>{}</samp>’.) If you don't specify a mark command, the
default is
+‘<samp>{}</samp>’.) If you don’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 ‘meta’ or
‘ctrl’ 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.
+‘Next’, ‘Previous’, and ‘Up’ 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 ‘Top’ <code>@node</code> line
with a line
+beginning with <code>@top</code> to mark the ‘Top’ 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
‘Top’
node) in a menu that is one or more hierarchical levels above the
-node's hierarchical level.
+node’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 ‘<samp>.html</samp>’ is appended to the
directory name, as
in ‘<samp>emacs.html</samp>’ (this is necessary because sometimes
the info file
is named without an extension, e.g., ‘<samp>texinfo</samp>’). If
the
-‘<samp><var>name</var>.html</samp>’ directory can't be created
either,
+‘<samp><var>name</var>.html</samp>’ directory can’t be
created either,
<code>makeinfo</code> gives up. In any case, the top-level output file within
the directory is always named ‘<samp>index.html</samp>’.
</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
‘Running <code>make</code> or Compilers Generally’ 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 ‘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="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 ‘Top’ 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 ‘<samp>@node Top</samp>’ 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 ‘Top’ 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’s
conventional to use ‘<samp>\</samp>’ instead of
‘<samp>@</samp>’ for these commands.
As in:
</p><table><tr><td> </td><td><pre class="example">@math{\sin 2\pi \equiv
\cos 3\pi}
@@ -109,7 +109,7 @@
<a name="IDX224"></a>
<p>Since ‘<samp>\</samp>’ 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 ‘<samp>\\</samp>’ in Info).
<code>@\</code> is not
+but you’ll get the literal ‘<samp>\\</samp>’ in Info).
<code>@\</code> is not
defined outside of <code>@math</code>, since a ‘<samp>\</samp>’
ordinarily produces a
literal ‘<samp>\</samp>’.
</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
+‘Next’, ‘Previous’, and ‘Up’ 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,
+‘Next’, ‘Previous’, and ‘Up’ 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> </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> </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> </td><td align="left" valign="top">
How to write a ‘Top’ 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> </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>.
+‘produces’ 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>{} (£): Pounds Sterling
</h2>
-<p>Use the <code>@pounds{}</code> command to generate `£'. In a
+<p>Use the <code>@pounds{}</code> command to generate ‘£’.
In a
printed manual, this is the symbol for the currency pounds sterling.
In Info, it is a ‘<samp>#</samp>’. 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’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'.
+‘see’ rather than an upper case ‘See’.
</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 ‘See’ 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 ‘sample’ 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’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’t want the
default option (no blank pages, same headers on all pages) use the
‘<samp>--texinfo</samp>’ 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 ‘subsub’ Commands </h2>
<p>The fourth and lowest level sectioning commands in Texinfo are the
-`subsub' commands. They are:
+‘subsub’ 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, ‘subsub’ titles are underlined with periods.
For example,
</p>
<table><tr><td> </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
‘from’
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
+‘from’ 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 ‘TeX’. In a
printed
manual, this is a special logo that is different from three ordinary
letters. In Info, it just looks like ‘<samp>TeX</samp>’. 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 “GNU Free Documentation License.”
</p>
-<p>(a) The FSF's Back-Cover Text is: “You have freedom to copy and modify
+<p>(a) The FSF’s Back-Cover Text is: “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.”
</p></blockquote>
@@ -198,7 +198,7 @@
</pre></th></tr><tr><td align="left" valign="top"><a
href="Texinfo-Mode.html#Texinfo-Mode-Overview">• Texinfo Mode
Overview</a></td><td> </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> </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> </td><td align="left"
valign="top"> Texinfo mode adds to GNU Emacs’ 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> </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> </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> </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
‘Top’ Node and Master Menu</a></td><td> </td><td
align="left" valign="top"> Creating the ‘Top’ 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> </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> </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> </td><td align="left" valign="top">
Declare the document’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> </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> </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> </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> </td><td align="left" valign="top">
The <code>@top</code> command, part of the ‘Top’ node.
</td></tr>
<tr><td align="left" valign="top"><a href="chapter.html#SEC76">5.4
<code>@chapter</code></a></td><td> </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> </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> </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
‘subsub’ Commands</a></td><td> </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> </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> </td><td align="left"
valign="top"> How to change commands’ 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> </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> </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> </td><td align="left" valign="top">
How to write a ‘Top’ 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> </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> </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> </td><td align="left" valign="top">
Begin a reference with `See' …
+<tr><td align="left" valign="top"><a href="xref.html#SEC108">8.3
<code>@xref</code></a></td><td> </td><td align="left" valign="top">
Begin a reference with ‘See’ …
</td></tr>
-<tr><td align="left" valign="top"><a href="Top-Node-Naming.html#SEC114">8.4
Naming a `Top' Node</a></td><td> </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 ‘Top’ Node</a></td><td> </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> </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> </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> </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’s
Indentation</a></td><td> </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> </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> </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> </td><td align="left" valign="top">
Sometimes a . doesn’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> </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> </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> </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 ‘First’ Lines</a></td><td> </td><td align="left"
valign="top"> How to group two or more ‘first’
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> </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> </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> </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> </td><td align="left" valign="top">
Using a macro, once you’ve defined it.
</td></tr>
<tr><td align="left" valign="top"><a href="Macro-Details.html#SEC241">18.3
Macro Details</a></td><td> </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> </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> </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> </td><td align="left" valign="top">
How to print using Emacs’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> </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 ‘Next’,
‘Previous’, and ‘Up’
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 ‘Next’, ‘Previous’, and
‘Up’ 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 ‘Top’ 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 ‘Top’ 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 ‘Next’,
‘Previous’, and ‘Up’ 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 ‘Top’ 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 ‘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="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 ‘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="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 ‘Top’ 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 ‘subsub’
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
‘First’ 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>{<char><var>text</var><char>}</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’ 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 ‘First’ 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’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’ 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
‘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="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,
‘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="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">ø</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">Ø</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’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">œ</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’ 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
‘subsub’ 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’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
‘Top’ 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">‘<samp><span
class="roman">Top</span></samp>’ 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">‘<samp><span
class="roman">Top</span></samp>’ 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="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
‘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="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 ‘<samp>X</samp>’ is actually the Greek letter
“chi” rather than
the English letter “ex”. Pronounce TeX as if the
‘<samp>X</samp>’ were the
-last sound in the name `Bach'; but pronounce Texinfo as if the
‘<samp>x</samp>’
-were a `k'. Spell “Texinfo” with a capital “T” and
the other
+last sound in the name ‘Bach’; but pronounce Texinfo as if the
‘<samp>x</samp>’
+were a ‘k’. Spell “Texinfo” with a capital
“T” 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 ‘Previous’
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 ‘Next’ 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 ‘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.
</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
+‘editions’ and versions of programs as ‘versions’;
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
‘Top’ 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
‘subsub’ 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
‘Top’ 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…</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’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
‘First’ 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 ‘Top’ node should also contain this
information; see
+<a href="The-Top-Node.html#SEC59">The ‘Top’ 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’s in the unambiguous format:
</p>
<table><tr><td> </td><td><pre
class="display"><URL:http://<var>host</var>/<var>path</var>>
</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’s not
necessary to clutter up the output with the extra
‘<samp><URL:</samp>’ and
-‘<samp>></samp>’, since any software that tries to detect url's
in text already
+‘<samp>></samp>’, since any software that tries to detect
url’s in text already
has to detect them without the ‘<samp><URL:</samp>’ 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’s which do
not actually exist. For example:
</p>
<table><tr><td> </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 ‘Overview’ 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’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’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’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 "GNU Free Documentation License".
</p>
-<p>(a) The FSF's Back-Cover Text is: “You are free to copy and modify
+<p>(a) The FSF’s Back-Cover Text is: “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.”
</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> </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> </td><td align="left"
valign="top"> Choosing the Archive’s Name
</td></tr>
<tr><td align="left" valign="top"><a href="#SEC99">6.2 Selecting Archive
Members</a></td><td> </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’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 “printing” 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’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, ‘<samp>$</samp>’ 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’s response; those lines are shown in <code>this font</code>, or
sometimes ‘<samp>like this</samp>’.
</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’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 ‘Verbose listing’
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
‘<samp>v7</samp>’ 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’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’t already a file in the
working directory with the archive name you intend to use (in this case,
-‘<samp>collection.tar</samp>’), or that you don't care about its
contents.
+‘<samp>collection.tar</samp>’), or that you don’t care about
its contents.
Whenever you use ‘<samp>create</samp>’, <code>tar</code> will
erase the current
contents of the file named by
‘<samp>--file=<var>archive-name</var></samp>’ (‘<samp>-f
<var>archive-name</var></samp>’) 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’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
‘<samp>create</samp>’</a>, for more information on this.
</p>
@@ -1647,8 +1647,8 @@
<p>Creating the archive ‘<samp>collection.tar</samp>’ 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’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>
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—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’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 ‘<samp>--extract</samp>’
(‘<samp>--get</samp>’ or
@@ -2158,7 +2158,7 @@
arguments, as printed by ‘<samp>--list</samp>’
(‘<samp>-t</samp>’). If you had
mistakenly deleted one of the files you had placed in the archive
‘<tt>collection.tar</tt>’ earlier (say,
‘<tt>blues</tt>’), you can extract it
-from the archive without changing the archive's structure. Its
+from the archive without changing the archive’s structure. Its
contents will be identical to the original file ‘<tt>blues</tt>’
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 ‘<tt>birds</tt>’. To
extract
the member named ‘<tt>./birds</tt>’, 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’t remember the
exact member names, use ‘<samp>--list</samp>’
(‘<samp>-t</samp>’) 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 ‘<samp>--extract</samp>’ to
extract a directory
file with an example. Change to the ‘<tt>practice</tt>’ directory
if you
-weren't there, and remove the files ‘<tt>folk</tt>’ and
‘<tt>jazz</tt>’. Then,
+weren’t there, and remove the files ‘<tt>folk</tt>’ and
‘<tt>jazz</tt>’. Then,
go back to the parent directory and extract the archive
‘<tt>music.tar</tt>’. 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’t give any file names as arguments after the archive name
‘<tt>music.tar</tt>’. 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’t have
to worry about the extraction overwriting one of your existing files.
For example, if ‘<tt>untrusted.tar</tt>’ came from somewhere else
on the
-Internet, and you don't necessarily trust its contents, you can
+Internet, and you don’t necessarily trust its contents, you can
extract it as follows:
</p>
<table><tr><td> </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’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
‘<samp>--files-from=<var>file-of-names</var></samp>’
(‘<samp>-T <var>file-of-names</var></samp>’) option.
</p>
-<p>If you don't use any file name arguments,
‘<samp>--append</samp>’ (‘<samp>-r</samp>’),
+<p>If you don’t use any file name arguments,
‘<samp>--append</samp>’ (‘<samp>-r</samp>’),
‘<samp>--delete</samp>’ and
‘<samp>--concatenate</samp>’ (‘<samp>--catenate</samp>’,
‘<samp>-A</samp>’) will do nothing, while
‘<samp>--create</samp>’ (‘<samp>-c</samp>’)
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’m really
aiming simplicity in that area, for now. If you are not using the
‘<samp>--compare</samp>’ ‘<samp>--diff</samp>’,
‘<samp>-d</samp>’) 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>’s performance by
running
<code>tar</code> with one or more options (such as
‘<samp>--verbose</samp>’
(‘<samp>-v</samp>’), 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 ‘<samp>cre</samp>’. (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 ‘<samp>tar
--help</samp>’
+you that that abbreviation is ambiguous and you’ll know that that
+abbreviation won’t work. You may also choose to run ‘<samp>tar
--help</samp>’
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’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’ 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., ‘<samp><code>tar</code> -cvf</samp>’. Only the last
option in
@@ -2817,7 +2817,7 @@
<table><tr><td> </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’ 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 ‘<samp>-</samp>’. Thus,
‘<samp>tar c</samp>’ is
+letters even if it doesn’t start with ‘<samp>-</samp>’.
Thus, ‘<samp>tar c</samp>’ is
equivalent to ‘<samp>tar -c</samp>’: both of them specify the
‘<samp>--create</samp>’ (‘<samp>-c</samp>’) command to
create an archive.
</p>
@@ -3101,7 +3101,7 @@
</p></dd>
<dt> ‘<samp>--delete</samp>’</dt>
<dd>
-<p>Deletes members from the archive. Don't try this on a archive on a
+<p>Deletes members from the archive. Don’t try this on a archive on a
tape! See section <a href="#SEC58">Removing Archive Members Using
‘<samp>--delete</samp>’</a>.
</p>
<p><a name="g_t_002d_002ddiff"></a>
@@ -3193,7 +3193,7 @@
<a name="IDX45"></a>
</p></dd>
<dt> ‘<samp>--anchored</samp>’</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’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 ‘<samp>--verbose</samp>’ output. For a detailed
+don’t want to see ‘<samp>--verbose</samp>’ 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> ‘<samp>-f <var>archive</var></samp>’</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>’s compilation
dependent
default. See section <a href="#SEC14">The ‘<samp>--file</samp>’
Option</a>.
</p>
<p><a name="g_t_002d_002dfiles_002dfrom"></a>
@@ -3666,7 +3666,7 @@
<a name="IDX91"></a>
</p></dd>
<dt> ‘<samp>--no-anchored</samp>’</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’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> ‘<samp>--no-same-permissions</samp>’</dt>
<dd>
-<p>When extracting an archive, subtract the user's umask from files from
+<p>When extracting an archive, subtract the user’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> ‘<samp>-p</samp>’</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’ 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> ‘<samp>--version</samp>’</dt>
<dd>
-<p>Print information about the program's name, version, origin and legal
+<p>Print information about the program’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 ‘<samp>--checkpoint</samp>’ 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’t need the more detailed (and voluminous) output of
‘<samp>--block-number</samp>’ (‘<samp>-R</samp>’), 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’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’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’t need to
create a new archive; you can use ‘<samp>--append</samp>’
(‘<samp>-r</samp>’).
The archive must already exist in order to use
‘<samp>--append</samp>’. (A
related operation is the ‘<samp>--update</samp>’ operation; you
can use this
@@ -5103,7 +5103,7 @@
view an archive with ‘<samp>--list</samp>’
(‘<samp>-t</samp>’), 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’t deal with these members as perfectly as you
might
prefer; if you were to use ‘<samp>--extract</samp>’ 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
‘<samp>--update</samp>’ </h4>
<p>You must use file name arguments with the
‘<samp>--update</samp>’
-(‘<samp>-u</samp>’) 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
+(‘<samp>-u</samp>’) 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
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 ‘File permissions’ 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 ‘<samp>a+rw</samp>’ 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’re not sure of the blocking factor of an archive, you can
read the archive by specifying ‘<samp>--read-full-records</samp>’
(‘<samp>-B</samp>’) and
‘<samp>--blocking-factor=<var>512-size</var></samp>’
(‘<samp>-b
<var>512-size</var></samp>’), 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’t want to store the file on disk before processing
it. You can use a command like this:
</p>
<table><tr><td> </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’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’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’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’s time stamps during dumping (e.g.,
with the ‘<samp>--atime-preserve=replace</samp>’ 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 ‘Bash
Features’ 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’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’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’t have to correspond to archive
files — 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> ‘<samp>-f</samp>’</dt>
<dt> ‘<samp>--force</samp>’</dt>
-<dd><p>Force backup even if today's log file already exists.
+<dd><p>Force backup even if today’s log file already exists.
</p>
</dd>
<dt> ‘<samp>-v[<var>level</var>]</samp>’</dt>
@@ -8018,7 +8018,7 @@
</dd>
<dt> ‘<samp>-V</samp>’</dt>
<dt> ‘<samp>--version</samp>’</dt>
-<dd><p>Display information about the program's name, version, origin and legal
+<dd><p>Display information about the program’s name, version, origin and
legal
status, all on standard output, and then exit successfully.
</p></dd>
</dl>
@@ -8104,14 +8104,14 @@
</dd>
<dt> ‘<samp>-V</samp>’</dt>
<dt> ‘<samp>--version</samp>’</dt>
-<dd><p>Display information about the program's name, version, origin and legal
+<dd><p>Display information about the program’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’t need
to rewind the tape to to its beginning—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’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> </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> </td><td align="left" valign="top">
Choosing the Archive’s Name
</td></tr>
<tr><td align="left" valign="top"><a href="#SEC99">6.2 Selecting Archive
Members</a></td><td> </td><td align="left" valign="top">
</td></tr>
@@ -8229,7 +8229,7 @@
follow the ‘<samp>-f</samp>’ option, since whatever directly
follows ‘<samp>-f</samp>’
<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’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 ‘<samp>.txt</samp>’ and the file named
‘<tt>[remarks]</tt>’.
</p>
<p>Normally, a pattern matches a name if an initial subsequence of the
-name's components matches the pattern, where ‘<samp>*</samp>’,
‘<samp>?</samp>’, and
+name’s components matches the pattern, where
‘<samp>*</samp>’, ‘<samp>?</samp>’, and
‘<samp>[...]</samp>’ are the usual shell wildcards,
‘<samp>\</samp>’ escapes wildcards,
and wildcards can match ‘<samp>/</samp>’.
</p>
@@ -8968,7 +8968,7 @@
<dt> ‘<samp>--anchored</samp>’</dt>
<dt> ‘<samp>--no-anchored</samp>’</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’s components. Otherwise, the pattern can match any
subsequence. Default is ‘<samp>--no-anchored</samp>’ for
exclusion members
and ‘<samp>--anchored</samp>’ inclusion members.
</p>
@@ -8995,7 +8995,7 @@
<p>The ‘<samp>--recursion</samp>’ and
‘<samp>--no-recursion</samp>’ 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’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 "s" Command: (sed)The
"s" Command</a> section `The `s' Command' in <cite>GNU sed</cite>.
+<a href="sed.html#The-_0022s_0022-Command">The "s" Command: (sed)The
"s" Command</a> section ‘The ‘s’ Command’ in
<cite>GNU sed</cite>.
</p>
<p>Supported <var>flags</var> are:
</p>
@@ -9417,7 +9417,7 @@
</p>
</dd>
<dt> ‘<samp>x</samp>’</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 ‘Extended regular expressions’ in <cite>GNU
sed</cite>).
</p>
</dd>
<dt> ‘<samp><var>number</var></samp>’</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’s data (rather than status
changes), then use the
‘<samp>--newer-mtime=<var>date</var></samp>’ 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’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 ‘<samp>--after-date</samp>’ 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’s status was last changed: owner, permissions, etc.)
fields, while ‘<samp>--newer-mtime</samp>’ 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 ‘<samp>--no-recursion</samp>’ option inhibits
<code>tar</code>'s recursive descent
+<p>The ‘<samp>--no-recursion</samp>’ option inhibits
<code>tar</code>’s recursive descent
into specified directories. If you specify
‘<samp>--no-recursion</samp>’, 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 ‘<samp>-not -type
d</samp>’
-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 ‘Type test’ in <cite>Finding Files</cite>),
as they usually do not want all the files in a
directory. They then use the ‘<samp>--files-from</samp>’ option to
archive
the files located via <code>find</code>.
</p>
@@ -10381,7 +10381,7 @@
<p>Time zone items other than ‘<samp>UTC</samp>’ and
‘<samp>Z</samp>’
are obsolescent and are not recommended, because they
are ambiguous; for example, ‘<samp>EST</samp>’ 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’s better to use
unambiguous numeric time zone corrections like
‘<samp>-0500</samp>’, as
described in the previous section.
</p>
@@ -10611,7 +10611,7 @@
to <acronym>POSIX</acronym>, using negative counts, so that
‘<samp>@-1</samp>’
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’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 ‘<samp>UTC0</samp>’ 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
‘Specifying the Time Zone with <code>TZ</code>’ 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> </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’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>’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’ll see!
</p>
<a name="IDX393"></a>
</dd>
@@ -11049,7 +11049,7 @@
<p>The ‘<samp>--use-compress-program</samp>’ 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 —- 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 ‘gpg —- encryption
and signing tool’ in <cite>GNU Privacy Guard Manual</cite>). The
following script does that:
</p>
<table><tr><td> </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’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 ‘<samp>--sparse</samp>’ is not needed on
extraction) any
such files have holes created wherever the continuous stretches of zeros
were found. Thus, if you use ‘<samp>--sparse</samp>’,
<code>tar</code> archives
-won't take more space than the original.
+won’t take more space than the original.
</p>
<dl compact="compact">
<dd><a name="IDX400"></a>
@@ -11210,7 +11210,7 @@
</p>
<p>‘<samp>--atime-preserve=replace</samp>’ 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’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>‘<samp>--atime-preserve=system</samp>’ 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’t work, it
complains right away.
</p>
<p>Currently ‘<samp>--atime-preserve</samp>’ 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’t find a user name (because the user id is not
in ‘<tt>/etc/passwd</tt>’), then it does not write one. When
restoring,
it tries to look the name (if one was written) up in
‘<tt>/etc/passwd</tt>’. 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’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’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 ‘<samp>--format=v7</samp>’ for your distributions.
Notice,
however, that ‘<samp>ustar</samp>’ format is a better alternative,
as it is
-free from many of ‘<samp>v7</samp>’'s drawbacks.
+free from many of ‘<samp>v7</samp>’’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’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>’s.
+I’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>’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’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’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’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’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
‘<samp>-R</samp>’ option). For example,
+listing (analogous to <acronym>GNU</acronym> <code>tar</code>’s
‘<samp>-R</samp>’ option). For example,
<code>star</code> has ‘<samp>-block-number</samp>’.
</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’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’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>’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
"binary"
format, i-numbers are only 16 bits, and in its "portable ASCII"
format,
-they're 18 bits—it would have to play games with the "file system
ID"
+they’re 18 bits—it would have to play games with the "file
system ID"
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’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
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’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
know whether any version that was generally available <em>within AT&T</em>
had <code>tar</code>, or, if so, whether the people within AT&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 ‘<samp>dd
skip=<var>nn</var></samp>’.
-However, modern <code>cpio</code>'s and variations have an option to just
+However, modern <code>cpio</code>’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’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’s compiled and installed by
default.
The exact path to this utility is determined when configuring the package.
It is ‘<tt><var>prefix</var>/libexec/rmt</tt>’, where
<var>prefix</var> stands for
your installation prefix. This location may also be overridden at
@@ -12819,7 +12819,7 @@
blocking factor (with ‘<samp>--blocking-factor</samp>’) larger
than the
actual blocking factor, and then use the
‘<samp>--read-full-records</samp>’
(‘<samp>-B</samp>’) option. (If you specify a blocking factor with
-‘<samp>--blocking-factor</samp>’ and don't use the
+‘<samp>--blocking-factor</samp>’ and don’t use the
‘<samp>--read-full-records</samp>’ 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’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 ‘<samp>--list</samp>’ (‘<samp>-t</samp>’)
without specifying a blocking factor—<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’re not sure what the blocking factor
is), you can usually use the ‘<samp>--read-full-records</samp>’
(‘<samp>-B</samp>’) option while
specifying a blocking factor larger then the blocking factor of the archive
(i.e. ‘<samp>tar --extract --read-full-records
--blocking-factor=300</samp>’.
@@ -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…
+now, and we haven’t had the problem since we switched…
</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
‘<samp><var>prog</var> -d</samp>’ 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’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 ‘<tt>/dev</tt>’
directory, or
entries that come in pairs, which differ only in the minor number for
-this device. Let's take for example ‘<tt>/dev/tape</tt>’, which
often
+this device. Let’s take for example ‘<tt>/dev/tape</tt>’,
which often
points to the only or usual tape device of a given system. There might
be a corresponding ‘<tt>/dev/nrtape</tt>’ or
‘<tt>/dev/ntape</tt>’. 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 "rrrr"'s, and tape
marks as
-"*"'s, a tape might look like the following:
+<p>If you think of data as a series of records "rrrr"’s, and
tape marks as
+"*"’s, a tape might look like the following:
</p>
<table><tr><td> </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’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 ‘<tt>sys/mtio.h</tt>’ 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>’s shell environment.
Additional data is passed to it via the following
environment variables:
</p>
@@ -13965,7 +13965,7 @@
‘<tt>archive</tt>’ 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’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
‘<samp>/</samp>’ from file
names (see section <a href="#SEC112">Absolute File Names</a>), a command like
‘<samp>tar --verify -cf
/tmp/foo.tar /etc</samp>’ will work as desired only if the working
directory is
-‘<tt>/</tt>’, as <code>tar</code> uses the archive's relative
member names
+‘<tt>/</tt>’, as <code>tar</code> uses the archive’s
relative member names
(e.g., ‘<tt>etc/motd</tt>’) 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
‘Changing Automake’s Behavior’ 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
‘<samp>-o</samp>’ 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’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 ‘<samp>--format</samp>’ 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’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’s access and
status change times.
</p>
<p>The <code>offset</code> is used by the
‘<samp>--multi-volume</samp>’ (‘<samp>-M</samp>’)
option, when
@@ -16069,7 +16069,7 @@
copying, no modification, source files not available—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’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’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’t obstruct the community’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—you
-don't have to let the publisher decide. Some commercial publishers
+don’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’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 “Secondary Section” 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’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, “Title Page”
means
-the text near the most prominent appearance of the work's title,
+the text near the most prominent appearance of the work’s title,
preceding the beginning of the body of the text.
</p>
<p>A section “Entitled XYZ” 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’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’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’s license notice.
These titles must be distinct from any other section titles.
</p>
<p>You may add a section Entitled “Endorsements”, 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 “aggregate” 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’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’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
‘<samp>--create</samp>’ is used with
‘<samp>--verbose</samp>’ 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’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’s language will be used.
</p><h3><a name="FOOT21" href="#DOCF21">(21)</a></h3>
<p>See <a href="#g_t_002d_002drestrict">–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’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 ‘<tt>texi2html</tt>’
@@ -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 ‘<tt>texi2html</tt>’ and not
‘<tt>makeinfo</tt>’? </h2>
-<p>The basic idea of <code>makeinfo</code>'s <acronym>HTML</acronym>
+<p>The basic idea of <code>makeinfo</code>’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>’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>’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’t
+read this, cause you don’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><td></td></code>
-<var>$T2H_EXAMPLE_INDENT_CELL</var> = '<td>&nbsp;</td>';
+<var>$T2H_EXAMPLE_INDENT_CELL</var> =
’<td>&nbsp;</td>’;
</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 ‘<tt>index.html</tt>’) replace
<strong>HREF</strong>'s
+<p>if set (e.g., to ‘<tt>index.html</tt>’) replace
<strong>HREF</strong>’s
to this file (i.e., to ‘<tt>index.html</tt>’) by
‘<tt>./</tt>’
</p>
<p>$T2H_HREF_DIR_INSTEAD_FILE = "";
@@ -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 = ’section’;
$T2H_SPLIT = undef;
</p>
<hr size="6">
@@ -1905,7 +1905,7 @@
and use ISO 639 language codes (see e.g. perl module
‘<tt>Locale-Codes-1.02.tar.gz</tt>’ for definitions).
</p>
-<p>If you don't give a ‘<samp>-lang</samp>’ then we got it from the
+<p>If you don’t give a ‘<samp>-lang</samp>’ 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 “Secondary Section” 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’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, “Title Page”
means
-the text near the most prominent appearance of the work's title,
+the text near the most prominent appearance of the work’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’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’s license notice.
</li><li>
Include an unaltered copy of this License.
@@ -325,7 +325,7 @@
</li><li>
In any section entitled “Acknowledgments” or
“Dedications”,
-preserve the section's title, and preserve in the section all the
+preserve the section’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’s license notice.
These titles must be distinct from any other section titles.
</p>
<p>You may add a section entitled “Endorsements”, 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’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
‘Character Conventions’ 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’s
HOME directory called ‘<tt>.info</tt>’<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 ‘<tt>.info</tt>’ file take
precedence over GNU
-Info's default key bindings, whether or not
‘<samp>--vi-keys</samp>’ is used. A
+Info’s default key bindings, whether or not
‘<samp>--vi-keys</samp>’ is used. A
default key binding may be disabled by overriding it in the
‘<tt>.info</tt>’
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’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 ‘<samp>no
entries found</samp>’ 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’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’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’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
-‘<samp>info emacs --show-options</samp>’ does what you'd expect.
+‘<samp>info emacs --show-options</samp>’ does what you’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’t work when you type in the echo area, because you
need to
be able to insert the ‘<samp>-</samp>’ 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 ‘Next’ node.
</p>
<a name="IDX115"></a>
<p>The <NEXT> key is known as the <PgDn> 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 ‘Prev’ node.
</p>
<a name="IDX119"></a>
<p>The <PREVIOUS> key is known as the <PgUp> 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 ‘Up’ node.
</p></dd>
</dl>
@@ -146,7 +146,7 @@
<dl compact="compact">
<dt> <l> (<code>history-node</code>)</dt>
<dt> <C-<CENTER>> (on DOS/Windows only)</dt>
-<dt> <'>, vi-like operation</dt>
+<dt> <’>, 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
‘<samp>I</samp>’. 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) <RET></kbd> and then <kbd>I makeinfo <RET></kbd>. If
you don't
+(texinfo) <RET></kbd> and then <kbd>I makeinfo <RET></kbd>. If
you don’t
know what Info file documents the command, or if invoking
‘<samp>I</samp>’
-doesn't display the right node, go to the ‘<samp>(dir)</samp>’
node (using the
+doesn’t display the right node, go to the
‘<samp>(dir)</samp>’ node (using the
‘<samp>d</samp>’ command) and invoke ‘<samp>I</samp>’
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
‘<samp>(dir)</samp>’ 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’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> </td><td><pre class="example"> <kbd>G
Texinfo,Overview,Reporting Bugs <RET></kbd>
</pre></td></tr></table>
<p>displays the node ‘<samp>Reporting Bugs</samp>’ in the Texinfo
manual. (You
-don't actually need to type the menu items in their full length, or in
+don’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’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 ‘<samp>i</samp>’
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’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">–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’s menu, or failing that,
the
‘<samp>Next</samp>’ node, or failing that, the
‘<samp>Next</samp>’ of the ‘<samp>Up</samp>’.
This behavior is identical to using the ‘<samp>]</samp>’
(<code>global-next-node</code>) and ‘<samp>[</samp>’
(<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 ‘<samp>z</samp>’'s. In
addition, if
+indicated in the mode line with two small
‘<samp>z</samp>’’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 ‘Killing and Deleting’ in <cite>the GNU Emacs Manual</cite>
</p>
<dl compact="compact">
<dt> <M-d> (<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 ‘<samp>*</samp>’ at
the beginning
+appear within a node’s menu; they begin with a
‘<samp>*</samp>’ 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 ‘Writing an Xref’ 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
‘<samp>1</samp>’),
selects that menu item, and places its node in the current window.
For convenience, there is one exception; pressing ‘<samp>0</samp>’
selects the
-<em>last</em> item in the node's menu. When
‘<samp>--vi-keys</samp>’ is in
+<em>last</em> item in the node’s menu. When
‘<samp>--vi-keys</samp>’ is in
effect, digits set the numeric argument, so these commands are remapped
to their ‘<samp>M-</samp>’ varieties. For example, to select the
last menu
item, press <M-0>.
@@ -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’s menu.
</p>
</dd>
<dt> <m> (<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’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 “GNU Free Documentation
License.”
</p>
-<p>(a) The FSF's Back-Cover Text is: “You have freedom to copy and modify
+<p>(a) The FSF’s Back-Cover Text is: “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.”
</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 ‘<tt>.z</tt>’ and ‘<tt>.gz</tt>’,
to be merged into a single
-extension, since DOS doesn't allow more than a single dot in the
+extension, since DOS doesn’t allow more than a single dot in the
basename of a file. Thus, on MS-DOS, if Info looks for
‘<tt>bison</tt>’,
file names like ‘<tt>bison.igz</tt>’ and
‘<tt>bison.inz</tt>’ 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’t forget to escape the open and
close parentheses and whitespace from the shell as in: <code>info --node
"(emacs)Buffers"</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’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 ‘Executing an
extended command’ 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 “GNU Free Documentation License.”
</p>
-<p>(a) The FSF's Back-Cover Text is: “You have freedom to copy and modify
+<p>(a) The FSF’s Back-Cover Text is: “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.”
</p></blockquote>
@@ -197,7 +197,7 @@
</pre></th></tr><tr><td align="left" valign="top"><a
href="texinfo_3.html#Texinfo-Mode-Overview">• Texinfo Mode
Overview</a></td><td> </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> </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> </td><td align="left"
valign="top"> Texinfo mode adds to GNU Emacs’ 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> </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> </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> </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
‘Top’ Node and Master Menu</a></td><td> </td><td
align="left" valign="top"> Creating the ‘Top’ 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> </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> </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> </td><td align="left" valign="top">
Declare the document’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> </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> </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> </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> </td><td align="left" valign="top">
The <code>@top</code> command, part of the ‘Top’ node.
</td></tr>
<tr><td align="left" valign="top"><a href="texinfo_6.html#SEC76">5.4
<code>@chapter</code></a></td><td> </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> </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> </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
‘subsub’ Commands</a></td><td> </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> </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> </td><td align="left"
valign="top"> How to change commands’ 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> </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> </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> </td><td align="left" valign="top">
How to write a ‘Top’ 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> </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> </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> </td><td align="left" valign="top">
Begin a reference with `See' …
+<tr><td align="left" valign="top"><a href="texinfo_9.html#SEC108">8.3
<code>@xref</code></a></td><td> </td><td align="left" valign="top">
Begin a reference with ‘See’ …
</td></tr>
-<tr><td align="left" valign="top"><a href="texinfo_9.html#SEC114">8.4 Naming a
`Top' Node</a></td><td> </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
‘Top’ Node</a></td><td> </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> </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> </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> </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’s
Indentation</a></td><td> </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> </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> </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> </td><td align="left" valign="top">
Sometimes a . doesn’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> </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> </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> </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 ‘First’ Lines</a></td><td> </td><td align="left"
valign="top"> How to group two or more ‘first’
lines.
</td></tr>
<tr><td align="left" valign="top"><a href="texinfo_16.html#SEC218">15.4 The
Definition Commands</a></td><td> </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> </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> </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> </td><td align="left" valign="top">
Using a macro, once you’ve defined it.
</td></tr>
<tr><td align="left" valign="top"><a href="texinfo_19.html#SEC241">18.3 Macro
Details</a></td><td> </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> </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> </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> </td><td align="left"
valign="top"> How to print using Emacs’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> </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 ‘meta’ or
‘ctrl’ 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 ‘sample’ 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’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 ‘Emacs’ or ‘Bison’.
</p>
<p>When writing an entire shell command invocation, as in ‘<samp>ls
-l</samp>’,
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 ‘<acronym>NASA</acronym>’. The
abbreviation is given as
the single argument in braces, as in
‘<samp>@acronym{NASA}</samp>’. As
a matter of style, or for particular abbreviations, you may prefer to
use periods, as in ‘<samp>@acronym{F.B.I.}</samp>’.
@@ -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’s which do
not actually exist. For example:
</p>
<table><tr><td> </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 ‘Caution’ 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—but it's usually
+letters from ‘jumping out at you on the page’. This makes small
caps
+text easier to read than text in all upper case—but it’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’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 ‘abort to
orbit’).
</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> </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> </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’s
Indentation</a></td><td> </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> </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’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>.
+‘produces’ 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’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
-‘<samp>{}</samp>’.) If you don't specify a mark command, the
default is
+‘<samp>{}</samp>’.) If you don’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>’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> </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 ‘some text
for
+column one’, and the second column the width of ‘for column
two’.
</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
‘Splitting Windows’ in <cite>The GNU Emacs Manual</cite>):
</p>
<table><tr><td> </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’
indices.
</p>
-<p>If you don't see how to make an entry terse yet clear, make it longer
+<p>If you don’t see how to make an entry terse yet clear, make it longer
and clear—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 “Function Index” as an unnumbered
-chapter, you could give it the title `Function and Macro Index' and
+chapter, you could give it the title ‘Function and Macro Index’ 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 ‘Function and Concept Index’ and not printing the
‘Function
+Index’ 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
‘from’
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
+‘from’ 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> </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> </td><td align="left" valign="top">
Sometimes a . doesn’t end a sentence.
</td></tr>
<tr><td align="left" valign="top"><a href="#SEC180">13.2.2 Ending a
Sentence</a></td><td> </td><td align="left" valign="top">
Sometimes it does.
</td></tr>
@@ -342,7 +342,7 @@
‘<samp>.</samp>’; 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
‘Sentences’ 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>@"o</tt> </p></td><td><p> ö
</p></td><td><p> umlaut accent
</p></td></tr>
-<tr><td><p> <tt>@'o</tt> </p></td><td><p> ó
</p></td><td><p> acute accent
+<tr><td><p> <tt>@’o</tt> </p></td><td><p> ó
</p></td><td><p> acute accent
</p></td></tr>
<tr><td><p> <tt>@,{c}</tt> </p></td><td><p> ç
</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> ô
</p></td><td><p> circumflex accent
</p></td></tr>
-<tr><td><p> <tt>@`o</tt> </p></td><td><p> ò
</p></td><td><p> grave accent
+<tr><td><p> <tt>@‘o</tt> </p></td><td><p> ò
</p></td><td><p> grave accent
</p></td></tr>
<tr><td><p> <tt>@~o</tt> </p></td><td><p> õ
</p></td><td><p> tilde accent
</p></td></tr>
@@ -666,7 +666,7 @@
<h3 class="subsection"> 13.4.1 <code>@dots</code>{} (…) 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: `…'. Do
+three dots in a row, appropriately spaced, like this: ‘…’.
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, `©', is also special.
+<p>The logo ‘TeX’ is typeset in a special fashion and it needs an
address@hidden The copyright symbol, ‘©’, is also special.
Each of these commands is followed by a pair of braces,
‘<samp>{}</samp>’,
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 ‘TeX’. In a
printed
manual, this is a special logo that is different from three ordinary
letters. In Info, it just looks like ‘<samp>TeX</samp>’. 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>{} (©) </h3>
-<p>Use the <code>@copyright{}</code> command to generate `©'. In
+<p>Use the <code>@copyright{}</code> command to generate ‘©’.
In
a printed manual, this is a ‘<samp>c</samp>’ inside a circle, and
in Info,
this is ‘<samp>(C)</samp>’.
</p>
@@ -817,7 +817,7 @@
</tr></table>
<h2 class="section"> 13.6 <code>@pounds</code>{} (£): Pounds Sterling
</h2>
-<p>Use the <code>@pounds{}</code> command to generate `£'. In a
+<p>Use the <code>@pounds{}</code> command to generate ‘£’.
In a
printed manual, this is the symbol for the currency pounds sterling.
In Info, it is a ‘<samp>#</samp>’. 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’s
conventional to use ‘<samp>\</samp>’ instead of
‘<samp>@</samp>’ for these commands.
As in:
</p><table><tr><td> </td><td><pre class="example">@math{\sin 2\pi \equiv
\cos 3\pi}
@@ -917,7 +917,7 @@
<a name="IDX224"></a>
<p>Since ‘<samp>\</samp>’ 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 ‘<samp>\\</samp>’ in Info).
<code>@\</code> is not
+but you’ll get the literal ‘<samp>\\</samp>’ in Info).
<code>@\</code> is not
defined outside of <code>@math</code>, since a ‘<samp>\</samp>’
ordinarily produces a
literal ‘<samp>\</samp>’.
</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
‘<samp>error--></samp>’ in Info
-and as the word `error' in a box in the printed output.
+and as the word ‘error’ 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, ‘<samp>.};</samp>’ 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’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:
‘<samp>(1)</samp>’. 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’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 ‘End’ 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
‘<samp>Footnotes</samp>’ 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 ‘Separate’ node style, all the footnotes for a single
node are placed in an automatically constructed node of
their own. In this style, a “footnote reference” follows
each ‘<samp>(<var>n</var>)</samp>’ reference mark in the body of
the
@@ -1493,10 +1493,10 @@
<p>The name of the node with the footnotes is constructed
by appending ‘<samp>-Footnotes</samp>’ to the name of the node
-that contains the footnotes. (Consequently, the footnotes'
+that contains the footnotes. (Consequently, the footnotes’
node for the ‘<tt>Footnotes</tt>’ node is
-‘<tt>Footnotes-Footnotes</tt>’!) The footnotes' node has an
-`Up' node pointer that leads back to its parent node.
+‘<tt>Footnotes-Footnotes</tt>’!) The footnotes’ node has an
+‘Up’ 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’s
footnote style. Write this command at the beginning of a line followed
by an argument, either ‘<samp>end</samp>’ for the end node style or
‘<samp>separate</samp>’ 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 ‘separate’ style and
+<code>makeinfo</code> uses the ‘end’ style.
</p>
<p>This chapter contains two footnotes.
</p>
@@ -1577,7 +1577,7 @@
format).
</li><li>
<a name="IDX232"></a>
-PDFTeX reads ‘<tt><var>filename</var>.pdf</tt>’ (Adobe's Portable
Document Format).
+PDFTeX reads ‘<tt><var>filename</var>.pdf</tt>’ (Adobe’s
Portable Document Format).
</li><li>
<code>makeinfo</code> uses ‘<tt><var>filename</var>.txt</tt>’
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 ‘wrong’ 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’s copyright page:
</p>
<table><tr><td> </td><td><pre class="example">This is edition 2.0 of the
Texinfo documentation,@*
and is for …
@@ -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’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—`Function', `Variable', or whatever—to appear at the
+category—‘Function’, ‘Variable’, or
whatever—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’s name and arguments. In the printed manual, the command
+causes TeX to print the entity’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> </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> </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
‘First’ Lines</a></td><td> </td><td align="left"
valign="top"> How to group two or more ‘first’
lines.
</td></tr>
<tr><td align="left" valign="top"><a href="#SEC218">15.4 The Definition
Commands</a></td><td> </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 ‘Interactive Command’,
write braces around it. For example:
</p>
<table><tr><td> </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 ‘First’ Lines </h2>
-<p>To create two or more `first' or header lines for a definition, follow
+<p>To create two or more ‘first’ 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 …
</p></dd></dl>
-<p>Each definition command has an `x' form: <code>@defunx</code>,
+<p>Each definition command has an ‘x’ 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 ‘x’ 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>…</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 ‘Special Forms’ in <cite>GNU Emacs Lisp Reference
Manual</cite>.)
<code>@defspec</code> is equivalent to ‘<samp>@deffn {Special Form}
…</samp>’ 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 ‘<samp>@defvr {User
+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 ‘<samp>@defvr {User
Option} …</samp>’ 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
‘procedure’ 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 ‘<code>expose</code> on
+<code>windows</code>’, 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
‘<code>bar-method</code> on
+<code>bar-class</code>’, 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 ‘Calling Functions’ in <cite>The GNU Emacs
Lisp Reference Manual</cite>.
</p>
<blockquote><dl>
<dt><u>Function:</u> <b>apply</b><i> function &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 ‘large’ and ‘small’ model:
</p>
<a name="IDX295"></a>
<table><tr><td> </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 ‘Overview’ 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 ‘<tt>txi-<var>cc</var>.tex</tt>’ 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 ‘Chapter’, ‘See’, 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’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> </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> </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> </td><td align="left" valign="top">
Using a macro, once you’ve defined it.
</td></tr>
<tr><td align="left" valign="top"><a href="#SEC241">18.3 Macro
Details</a></td><td> </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
‘<samp>@macro</samp>’ instead of
+<p>This produces the output ‘a1atextb2b’. With
‘<samp>@macro</samp>’ instead of
‘<samp>@rmacro</samp>’, 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’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’d do this as follows:
</p>
<table><tr><td> </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 ‘//’ before and ‘\\’
after the argument
to <code>@phoo</code>. You can then write <code>@phoo{bar}</code> wherever you
-want `//bar\\' highlighted in Info.
+want ‘//bar\\’ 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’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
-‘<samp>diff -c</samp>’ (see <a
href="../diffutils/index.html#Top">(diffutils)Top</a> section `Overview' in
<cite>Comparing and Merging Files</cite>) and include
‘<tt>ChangeLog</tt>’ entries (see <a
href="../emacs/Change-Log.html#Change-Log">(emacs)Change Log</a> section
`Change Log' in <cite>The GNU Emacs Manual</cite>).
+‘<samp>diff -c</samp>’ (see <a
href="../diffutils/index.html#Top">(diffutils)Top</a> section
‘Overview’ in <cite>Comparing and Merging Files</cite>) and include
‘<tt>ChangeLog</tt>’ entries (see <a
href="../emacs/Change-Log.html#Change-Log">(emacs)Change Log</a> section
‘Change Log’ 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’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’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’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 ‘<samp>--help</samp>’ 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’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’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 ‘Next’ and ‘Previous’ pointers.
The ‘Next’
+pointer provides a link to the next section, and the ‘Previous’
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’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’
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 ‘Up’, ‘Previous’, and
‘Next’ 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 ‘Next’, ‘Previous’, and
‘Up’ 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 ‘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
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
‘Top’ 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 <SPC> repeatedly, or you get the whole
@@ -361,7 +361,7 @@
</p>
<p>The ‘<tt>dir</tt>’ file in the ‘<tt>info</tt>’
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.
+‘Top’ 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’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
‘TeX Mode’ 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’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> … <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’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>``…''</tt>. This
+begin and end quotations: <tt>‘‘…’’</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>``…''</tt> becomes <tt>"…"</tt>.
+double-quotes: <tt>‘‘…’’</tt> becomes
<tt>"…"</tt>.
</li><li>
Use three hyphens in a row, ‘<samp>---</samp>’, for a
dash—like this. In
@@ -719,7 +719,7 @@
</pre></td></tr></table>
<a name="IDX19"></a>
-<p>Here's an explanation:
+<p>Here’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 ‘<samp><head></samp>’ in HTML format. Strictly
speaking, <code>@settitle</code>
-is optional—if you don't mind your document being titled `Untitled'.
+is optional—if you don’t mind your document being titled
‘Untitled’.
</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. ‘Top’ Node and Master Menu</span></dt>
+<dd><p>The ‘Top’ 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: ‘Top’ Node and Master Menu </h3>
-<p>The `Top' node contains the master menu for the Info file. Since a
+<p>The ‘Top’ 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’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> </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> </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> </td><td align="left" valign="top">
How to print using Emacs’s compile command.
</td></tr>
<tr><td align="left" valign="top"><a href="#SEC252">19.8 TeX Formatting
Requirements Summary</a></td><td> </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 ‘<samp>.tex</samp>’ (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 ‘<samp>.tex</samp>’ (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.
For example, the raw index output files for the input file
‘<tt>foo.texinfo</tt>’ would be ‘<tt>foo.cp</tt>’,
‘<tt>foo.vr</tt>’, ‘<tt>foo.fn</tt>’,
‘<tt>foo.tp</tt>’, ‘<tt>foo.pg</tt>’ and
‘<tt>foo.ky</tt>’. 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’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’t support the
‘<samp>-d</samp>’ 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 ‘dvips invocation’ 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
‘<samp>PRN</samp>’.
@@ -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 ‘<tt>.emacs</tt>’ 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
‘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 ‘<tt>.emacs</tt>’ 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>).
</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 ‘Easy Customization Interface’ in
<cite>The GNU Emacs Manual</cite>, for more details about this. The Texinfo
variables can
be found in the ‘<samp>Development/Docs/Texinfo</samp>’ 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
‘Compilation’ 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’s
processing and forces out unfinished pages:
</p>
<table><tr><td> </td><td><pre class="example">@bye
@@ -786,12 +786,12 @@
</p>
<p>These settings would cause TeX to look for ‘<tt>\input</tt>’
file first
in the current directory, indicated by the ‘<samp>.</samp>’, then
in a
-hypothetical user's ‘<tt>me/mylib</tt>’ directory, and finally in
a system
+hypothetical user’s ‘<tt>me/mylib</tt>’ directory, and
finally in a system
directory ‘<tt>/usr/lib/tex/macros</tt>’.
</p>
<a name="IDX341"></a>
<a name="IDX342"></a>
-<p>Finally, you may wish to dump a ‘<tt>.fmt</tt>’ 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 ‘<tt>.fmt</tt>’ 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
disadvantage is that then updating ‘<tt>texinfo.tex</tt>’ requires
redumping.) You can do this by running this command, assuming
‘<tt>epsf.tex</tt>’ 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’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’s also <code>@afourwide</code> for A4
paper in
wide format.
</p>
<hr size="6">
@@ -1120,7 +1120,7 @@
<code>tex</code>. Just run ‘<samp>pdftex foo.texi</samp>’ instead
of ‘<samp>tex
foo.texi</samp>’, or give the ‘<samp>--pdf</samp>’ 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 ‘Portable Document Format’. 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 @@
‘<samp>@ifpdf</samp>’ or ‘<samp>@pdf</samp>’ commands
as with the other output
formats.
</p>
-<p>Despite the `portable' in the name, PDF files are nowhere near as
+<p>Despite the ‘portable’ 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 ‘Next’, ‘Previous’, or ‘Up’ node
reference is a reference to a
node in the current file and is not an external reference such as to
‘<tt>(dir)</tt>’, 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 ‘Previous’ node is different from the
‘Up’ node,
+then the node pointed to by the ‘Previous’ field must have a
‘Next’
field which points back to this node.
</li><li>
-Every node except the `Top' node must have an `Up' pointer.
+Every node except the ‘Top’ node must have an ‘Up’
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 ‘Up’ pointer must itself reference the
current
+node through a menu item, unless the node referenced by ‘Up’
+has the form ‘(<var>file</var>)’.
</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 ‘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.
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 ‘Top’ should be referenced by at least one other
node,
+either via the ‘Previous’ or ‘Next’ 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
‘Running <code>make</code> or Compilers Generally’ 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 ‘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="#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 ‘Command Line Switches and Arguments’ in
<cite>The GNU Emacs Manual</cite>.)
</p>
<p>Here is a shell command to format all the files that end in
‘<tt>.texinfo</tt>’ in the current directory:
@@ -938,7 +938,7 @@
for any reason, then ‘<samp>.html</samp>’ is appended to the
directory name, as
in ‘<samp>emacs.html</samp>’ (this is necessary because sometimes
the info file
is named without an extension, e.g., ‘<samp>texinfo</samp>’). If
the
-‘<samp><var>name</var>.html</samp>’ directory can't be created
either,
+‘<samp><var>name</var>.html</samp>’ directory can’t be
created either,
<code>makeinfo</code> gives up. In any case, the top-level output file within
the directory is always named ‘<samp>index.html</samp>’.
</p>
@@ -1055,17 +1055,17 @@
…
</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 ‘Top’ 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 ‘Top’ node, since Info goes to the ‘Top’
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 ‘<samp>Info</samp>’ entry points to the `Top' node of
the
-‘<tt>info</tt>’ file and the ‘<samp>Emacs</samp>’
entry points to the `Top' node
+<p>Thus, the ‘<samp>Info</samp>’ entry points to the
‘Top’ node of the
+‘<tt>info</tt>’ file and the ‘<samp>Emacs</samp>’
entry points to the ‘Top’ node
of the ‘<tt>emacs</tt>’ 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 ‘Up’ pointer of the
‘Top’ node refers
+back to the <code>dir</code> file. For example, the line for the
‘Top’
node of the Emacs manual looks like this in Info:
</p>
<table><tr><td> </td><td><pre class="example">File: emacs Node: Top, Up:
(DIR), Next: Distrib
@@ -1189,7 +1189,7 @@
‘<tt>/home/bob/info/info-test</tt>’ file as a menu entry in the
‘<tt>/home/bob/info/dir</tt>’ 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’ve
already run
<code>info</code>, you must <code>(setq Info-dir-contents nil)</code> to force
Emacs
to recompose the ‘<tt>dir</tt>’ file.
</p>
@@ -1230,7 +1230,7 @@
</li></ul>
<p>The ‘<samp>.</samp>’ 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’s
own <code>Info-directory-list</code> variable. The stand-alone Info reader
merges any files named ‘<tt>dir</tt>’ 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 ‘<tt>dir</tt>’ 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’s easiest
to start by
copying an existing ‘<tt>dir</tt>’ file and replace all the text
after the
‘<samp>* Menu:</samp>’ 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’s what this produces in the Info file:
</p>
<table><tr><td> </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 ‘current’ 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 ‘Invoking’ node for every program
installed
+by a package under ‘Individual utilities’, 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 ‘<tt>dir</tt>’ file in the Info system (see the previous
sections
-for an explanation of how the ‘<tt>dir</tt>’ file works). It's
most often
+for an explanation of how the ‘<tt>dir</tt>’ file works).
It’s most often
run as part of software installation, or when constructing a
‘<tt>dir</tt>’ 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
‘Invoking gzip’ 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 ‘<samp>.info</samp>’ in either one). Don't insert any
new entries.
+an optional ‘<samp>.info</samp>’ in either one). Don’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’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’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’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 ‘NASA’. 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 ‘subsub’ 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 (“as is”).
+print the table’s first column without highlighting (“as
is”).
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’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 ‘End’ node or
‘Separate’ 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
‘<samp>end</samp>’ for the end
+<dd><p>Specify an Info file’s footnote style, either
‘<samp>end</samp>’ for the end
node style or ‘<samp>separate</samp>’ 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, ‘-’. 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 ‘see’ in a
printed
manual. Use within parentheses only. Do not follow command with a
punctuation mark—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 ‘See’. 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
‘subsub’ 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 ‘subsub’
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 ‘Chapter 1: Title’), 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>.
+‘oo[’. 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 ‘1 Jan 1900’ 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>’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 ‘subsub’
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 ‘See’ 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>‘C-x v’ ‘M-x vc-next-action’ 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 ‘Invoking’, as in ‘Invoking Emacs’; 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’s calling
conventions, use the ANSI C syntax, like this:
</p>
<table><tr><td> </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 ‘it’ 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’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 ‘<samp>X</samp>’ were a Greek `chi', as
the last
-sound in the name `Bach'. But pronounce Texinfo as in `speck':
+Pronounce TeX as if the ‘<samp>X</samp>’ were a Greek
‘chi’, as the last
+sound in the name ‘Bach’. But pronounce Texinfo as in
‘speck’:
“teckinfo”.
</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’re not
+familiar with all these different elements, don’t worry. They’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’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 ‘<samp>Id: texinfo.txi,v 1.2 2003/02/24 18:17:06 pertusus Exp
$</samp>’ 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 ‘<samp>Id: texinfo.txi,v 1.2 2003/02/24 18:17:06 pertusus Exp
$</samp>’ 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
systems, which expand it into a string such as:
<table><tr><td> </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 ‘<tt>version.texi</tt>’ 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 ‘<samp>VERSION</samp>’ and
‘<samp>UPDATED</samp>’ 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
‘Introduction’ in <cite>GNU Automake</cite>). It sets the
‘<samp>VERSION</samp>’ and ‘<samp>UPDATED</samp>’
values used
+elsewhere. If your distribution doesn’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 ‘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>.
</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’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 ‘Next’,
‘Previous’, and ‘Up’
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 ‘Next’,
+‘Previous’, and ‘Up’ 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 ‘Next’,
‘Previous’, and ‘Up’
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 ‘Next’, ‘Previous’, and
‘Up’ 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 ‘Top’ 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 ‘Top’ 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 ‘Next’,
‘Previous’, and ‘Up’ 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 ‘Top’ 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 ‘Top’
node. It
+should <em>not</em> contain any nodes besides the single ‘Top’
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’ 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 ‘every’ 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 ‘even’ and ‘odd’ 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 ‘Chapter 1: Title’.
</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 ‘1 Jan 1900’ 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 ‘s’ on the end, instead of with <code>@end
menu</code>, you
will see an error message that says:
</p>
<table><tr><td> </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 <TAB> <RET></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 ‘Catching Mistakes’ node. (If you try this, you can
return
+from the ‘Catching Mistakes’ node by typing <kbd>l</kbd>
(<code>Info-last</code>).)
</p>
@@ -427,20 +427,20 @@
commands respectively. If you move your cursor into the
‘<samp>*Occur*</samp>’
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 ‘Using Occur’ in <cite>The GNU Emacs
Manual</cite>, for more
information about <code>occur-mode-goto-occurrence</code>.
</p>
<p>The first line in the ‘<samp>*Occur*</samp>’ 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
‘Using Regular Expressions’ 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 ‘Narrowing’ 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 ‘Regular
Expressions’ 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 ‘<samp>$</samp>’; for example,
‘<samp>catching mistakes$</samp>’. 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 ‘Up’ 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 ‘Using Occur’ 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 ‘Next’, ‘Previous’, ‘Up’ 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
+‘I’. 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 “File
appears
@@ -592,19 +592,19 @@
<table><tr><td> </td><td><pre class="example">In node
"Overview", invalid Next: Texinfo Mode
</pre></td></tr></table>
-<p>This meant that the node called ‘<samp>Overview</samp>’ had a
`Next' pointer that
+<p>This meant that the node called ‘<samp>Overview</samp>’ had a
‘Next’ 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 ‘<samp>Texinfo Mode</samp>’ to
our test case
-but we do not specify a `Previous' for this node. Then we will get
+but we do not specify a ‘Previous’ for this node. Then we will get
the following error message:
</p>
<table><tr><td> </td><td><pre class="example">In node "Texinfo
Mode", 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 ‘Next’ pointer should be matched by a
+‘Previous’ (in the node where the ‘Next’ 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> ⇒ ‘<samp>…</samp>’,
<code>@equiv{}</code>
-⇒ ‘<samp>≡</samp>’, <code>@TeX{}</code> ⇒ `TeX',
+⇒ ‘<samp>≡</samp>’, <code>@TeX{}</code> ⇒
‘TeX’,
and <code>@bullet{}</code> ⇒ ‘<samp>•</samp>’.
</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’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’ 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">•
Texinfo Mode Overview</a></td><td> </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> </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> </td><td align="left" valign="top">
Texinfo mode adds to GNU Emacs’ general
purpose editing features.
</td></tr>
<tr><td align="left" valign="top"><a href="#SEC24">2.2 Inserting Frequently
Used Commands</a></td><td> </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 ‘Next’,
+‘Previous’, and ‘Up’ 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’ 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 ‘Pages’
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 ‘Next’,
+‘Previous’, and ‘Up’ 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’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 ‘Next’,
‘Previous’, and ‘Up’
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
‘Narrowing’ 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
‘Pages’ 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 “update” 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 ‘Next’,
+‘Previous’, and ‘Up’ 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 ‘Next’, ‘Previous’, and
‘Up’ 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 ‘Top’ <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 ‘Top’
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 ‘Top’
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.
+‘Top’ 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 ‘Next’, ‘Previous’, and ‘Up’
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 ‘Next’,
‘Previous’, or ‘Up’
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 ‘Next’, ‘Previous’, and
‘Up’ 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 ‘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>).
</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 ‘jump down’
+more than one level at a time: you can follow the ‘Top’ 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 ‘jump up’ any
number of levels at one time—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
‘Top’
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, ‘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
<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
‘<samp>top</samp>’ or ‘<samp>Top</samp>’
+<p>If a file has a ‘Top’ node, it must be called
‘<samp>top</samp>’ or ‘<samp>Top</samp>’
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 ‘Top’ 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 ‘Next’,
‘Previous’ and
+‘Up’ 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 ‘Next’, ‘Previous’,
and ‘Up’ 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 ‘Next’ or ‘Previous’ pointers
regardless of those
+nodes’ hierarchical level. This means that the ‘Next’ 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 ‘custom insert’,
but
<kbd>C-c C-c</kbd> is quick to type.)
</p>
<table><tr><td> </td><td><pre class="example">C-c C-c c <span
class="roman">Insert</span> ‘<samp>@code</samp>’.
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 “Secondary Section” 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’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, “Title Page”
means
-the text near the most prominent appearance of the work's title,
+the text near the most prominent appearance of the work’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’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’s license notice.
</li><li>
Include an unaltered copy of this License.
@@ -324,7 +324,7 @@
</li><li>
In any section entitled “Acknowledgments” or
“Dedications”,
-preserve the section's title, and preserve in the section all the
+preserve the section’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’s license notice.
These titles must be distinct from any other section titles.
</p>
<p>You may add a section entitled “Endorsements”, 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’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 ‘subsub’
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 ‘First’
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">18.5
‘<samp>definfoenclose</samp>’: Customized Highlighting</a></td></tr>
<tr><td></td><td valign="top"><a
href="texinfo_16.html#IDX279"><code>defivar</code></a></td><td valign="top"><a
href="texinfo_16.html#SEC223">15.4.5 Object-Oriented Programming</a></td></tr>
@@ -330,7 +330,7 @@
<tr><td></td><td valign="top"><a
href="texinfo_11.html#SEC144"><code>example</code></a></td><td valign="top"><a
href="texinfo_11.html#SEC144">10.3 <code>@example</code>: Example
Text</a></td></tr>
<tr><td></td><td valign="top"><a
href="texinfo_4.html#SEC66"><code>exampleindent</code></a></td><td
valign="top"><a href="texinfo_4.html#SEC66">3.6.4 <code>@exampleindent</code>:
Environment Indenting</a></td></tr>
<tr><td></td><td valign="top"><a
href="texinfo_14.html#IDX193"><code>exclamdown</code></a></td><td
valign="top"><a href="texinfo_14.html#SEC183">13.3 Inserting
Accents</a></td></tr>
-<tr><td></td><td valign="top"><a
href="texinfo_11.html#SEC151"><code>exdent</code></a></td><td valign="top"><a
href="texinfo_11.html#SEC151">10.10 <code>@exdent</code>: Undoing a Line's
Indentation</a></td></tr>
+<tr><td></td><td valign="top"><a
href="texinfo_11.html#SEC151"><code>exdent</code></a></td><td valign="top"><a
href="texinfo_11.html#SEC151">10.10 <code>@exdent</code>: Undoing a
Line’s Indentation</a></td></tr>
<tr><td></td><td valign="top"><a
href="texinfo_14.html#SEC196"><code>expansion</code></a></td><td
valign="top"><a href="texinfo_14.html#SEC196">13.9.3 <code>@expansion{}</code>
(→): Indicating an Expansion</a></td></tr>
<tr><td colspan="3"> <hr></td></tr>
</table>
Index: Tests/texinfo_res/texinfo_33.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/texinfo_res/texinfo_33.html,v
retrieving revision 1.26
retrieving revision 1.27
diff -u -b -r1.26 -r1.27
--- Tests/texinfo_res/texinfo_33.html 5 Feb 2007 15:30:26 -0000 1.26
+++ Tests/texinfo_res/texinfo_33.html 3 Oct 2007 09:34:51 -0000 1.27
@@ -210,8 +210,8 @@
<tr><td></td><td valign="top"><a
href="texinfo_27.html#SEC314"><code>Info-validate</code></a></td><td
valign="top"><a href="texinfo_27.html#SEC314">F.5 Finding Badly Referenced
Nodes</a></td></tr>
<tr><td></td><td valign="top"><a
href="texinfo_9.html#SEC117"><code>inforef</code></a></td><td valign="top"><a
href="texinfo_9.html#SEC117">8.7 <code>@inforef</code></a></td></tr>
<tr><td></td><td valign="top"><a
href="texinfo_4.html#SEC51"><code>insertcopying</code></a></td><td
valign="top"><a href="texinfo_4.html#SEC51">3.3.2 <code>@insertcopying</code>:
Include permissions text</a></td></tr>
-<tr><td></td><td valign="top"><a
href="texinfo_16.html#IDX265"><code>isearch-backward</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#IDX264"><code>isearch-forward</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#IDX265"><code>isearch-backward</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#IDX264"><code>isearch-forward</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_12.html#IDX137"><code>item</code></a></td><td valign="top"><a
href="texinfo_12.html#SEC157">11.1 <code>@itemize</code>: Making an Itemized
List</a></td></tr>
<tr><td></td><td valign="top"><a
href="texinfo_12.html#IDX139"><code>item</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_12.html#SEC165"><code>item</code></a></td><td valign="top"><a
href="texinfo_12.html#SEC165">11.4.2 Multitable Rows</a></td></tr>
@@ -310,8 +310,8 @@
<tr><td></td><td valign="top"><a
href="texinfo_10.html#SEC138"><code>strong</code></a></td><td valign="top"><a
href="texinfo_10.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="texinfo_6.html#SEC82"><code>subheading</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#SEC81"><code>subsection</code></a></td><td valign="top"><a
href="texinfo_6.html#SEC81">5.9 The <code>@subsection</code>
Command</a></td></tr>
-<tr><td></td><td valign="top"><a
href="texinfo_6.html#SEC83"><code>subsubheading</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>subsubsection</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>subsubheading</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>subsubsection</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_4.html#SEC55"><code>subtitle</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>
<tr><td></td><td valign="top"><a
href="texinfo_5.html#SEC70"><code>summarycontents</code></a></td><td
valign="top"><a href="texinfo_5.html#SEC70">4.2 Generating a Table of
Contents</a></td></tr>
<tr><td></td><td valign="top"><a
href="texinfo_13.html#SEC171"><code>syncodeindex</code></a></td><td
valign="top"><a href="texinfo_13.html#SEC171">12.4.1
<code>@syncodeindex</code></a></td></tr>
Index: Tests/texinfo_res/texinfo_34.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/texinfo_res/texinfo_34.html,v
retrieving revision 1.18
retrieving revision 1.19
diff -u -b -r1.18 -r1.19
--- Tests/texinfo_res/texinfo_34.html 5 Feb 2007 15:30:26 -0000 1.18
+++ Tests/texinfo_res/texinfo_34.html 3 Oct 2007 09:34:51 -0000 1.19
@@ -216,7 +216,7 @@
<tr><td></td><td valign="top"><a
href="texinfo_4.html#SEC54"><code>titlefont</code></a></td><td valign="top"><a
href="texinfo_4.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="texinfo_4.html#SEC53"><code>titlepage</code></a></td><td valign="top"><a
href="texinfo_4.html#SEC53">3.4.1 <code>@titlepage</code></a></td></tr>
<tr><td></td><td valign="top"><a
href="texinfo_26.html#IDX461"><code>today</code></a></td><td valign="top"><a
href="texinfo_26.html#SEC307">E.3 How to Make Your Own Headings</a></td></tr>
-<tr><td></td><td valign="top"><a
href="texinfo_4.html#IDX85"><code>top</code></a></td><td valign="top"><a
href="texinfo_4.html#SEC59">3.5 The `Top' Node and Master Menu</a></td></tr>
+<tr><td></td><td valign="top"><a
href="texinfo_4.html#IDX85"><code>top</code></a></td><td valign="top"><a
href="texinfo_4.html#SEC59">3.5 The ‘Top’ Node and Master
Menu</a></td></tr>
<tr><td></td><td valign="top"><a href="texinfo_7.html#SEC94"><code>top <span
class="roman">(@-command)</span></code></a></td><td valign="top"><a
href="texinfo_7.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>
@@ -227,7 +227,7 @@
<tr><td></td><td valign="top"><a
href="texinfo_6.html#SEC77"><code>unnumbered</code></a></td><td valign="top"><a
href="texinfo_6.html#SEC77">5.5 <code>@unnumbered</code> and
<code>@appendix</code></a></td></tr>
<tr><td></td><td valign="top"><a
href="texinfo_6.html#SEC80"><code>unnumberedsec</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>unnumberedsubsec</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>unnumberedsubsubsec</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>unnumberedsubsubsec</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_3.html#IDX44"><code>up-list</code></a></td><td valign="top"><a
href="texinfo_3.html#SEC24">2.2 Inserting Frequently Used Commands</a></td></tr>
<tr><td></td><td valign="top"><a
href="texinfo_9.html#SEC118"><code>uref</code></a></td><td valign="top"><a
href="texinfo_9.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="texinfo_10.html#SEC135"><code>url</code></a></td><td valign="top"><a
href="texinfo_10.html#SEC135">9.1.14
<code>@url</code>{<var>uniform-resource-locator</var>}</a></td></tr>
Index: Tests/texinfo_res/texinfo_36.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/texinfo_res/texinfo_36.html,v
retrieving revision 1.79
retrieving revision 1.80
diff -u -b -r1.79 -r1.80
--- Tests/texinfo_res/texinfo_36.html 30 Sep 2007 12:47:40 -0000 1.79
+++ Tests/texinfo_res/texinfo_36.html 3 Oct 2007 09:34:51 -0000 1.80
@@ -236,7 +236,7 @@
<tr><td></td><td valign="top"><a href="texinfo_16.html#SEC214">Definition
commands</a></td><td valign="top"><a href="texinfo_16.html#SEC214">15.
Definition Commands</a></td></tr>
<tr><td></td><td valign="top"><a href="texinfo_16.html#SEC225">Definition
conventions</a></td><td valign="top"><a href="texinfo_16.html#SEC225">15.5
Conventions for Writing Definitions</a></td></tr>
<tr><td></td><td valign="top"><a href="texinfo_16.html#SEC215">Definition
template</a></td><td valign="top"><a href="texinfo_16.html#SEC215">15.1 The
Template for a Definition</a></td></tr>
-<tr><td></td><td valign="top"><a href="texinfo_16.html#SEC217">Definitions
grouped together</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">Definitions
grouped together</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_10.html#SEC126">Delimiter
character, for verbatim</a></td><td valign="top"><a
href="texinfo_10.html#SEC126">9.1.5
<code>@verb</code>{<char><var>text</var><char>}</a></td></tr>
<tr><td></td><td valign="top"><a href="texinfo_20.html#SEC257">Depth of text
area</a></td><td valign="top"><a href="texinfo_20.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="texinfo_3.html#IDX47">Description for
menu, start</a></td><td valign="top"><a href="texinfo_3.html#SEC24">2.2
Inserting Frequently Used Commands</a></td></tr>
Index: Tests/texinfo_res/texinfo_37.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/texinfo_res/texinfo_37.html,v
retrieving revision 1.21
retrieving revision 1.22
diff -u -b -r1.21 -r1.22
--- Tests/texinfo_res/texinfo_37.html 5 Feb 2007 15:30:26 -0000 1.21
+++ Tests/texinfo_res/texinfo_37.html 3 Oct 2007 09:34:51 -0000 1.22
@@ -242,10 +242,10 @@
<tr><td></td><td valign="top"><a href="texinfo_3.html#SEC21">GNU
Emacs</a></td><td valign="top"><a href="texinfo_3.html#SEC21">2. Using Texinfo
Mode</a></td></tr>
<tr><td></td><td valign="top"><a href="texinfo_20.html#SEC249">GNU Emacs
shell, format, print from</a></td><td valign="top"><a
href="texinfo_20.html#SEC249">19.5 From an Emacs Shell</a></td></tr>
<tr><td></td><td valign="top"><a href="texinfo_24.html#SEC296">GNU sample
texts</a></td><td valign="top"><a href="texinfo_24.html#SEC296">C.2 GNU Sample
Texts</a></td></tr>
-<tr><td></td><td valign="top"><a href="texinfo_8.html#SEC103">Going to other
Info files' nodes</a></td><td valign="top"><a href="texinfo_8.html#SEC103">7.5
Referring to Other Info Files</a></td></tr>
+<tr><td></td><td valign="top"><a href="texinfo_8.html#SEC103">Going to other
Info files’ nodes</a></td><td valign="top"><a
href="texinfo_8.html#SEC103">7.5 Referring to Other Info Files</a></td></tr>
<tr><td></td><td valign="top"><a href="texinfo_14.html#IDX170">Grave
accent</a></td><td valign="top"><a href="texinfo_14.html#SEC183">13.3 Inserting
Accents</a></td></tr>
<tr><td></td><td valign="top"><a href="texinfo_15.html#SEC212">Group (hold
text together vertically)</a></td><td valign="top"><a
href="texinfo_15.html#SEC212">14.6 <code>@group</code>: Prevent Page
Breaks</a></td></tr>
-<tr><td></td><td valign="top"><a href="texinfo_16.html#SEC217">Grouping two
definitions together</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">Grouping two
definitions together</a></td><td valign="top"><a
href="texinfo_16.html#SEC217">15.3 Two or More ‘First’
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="texinfo_20.html#SEC244">Hardcopy,
printing it</a></td><td valign="top"><a href="texinfo_20.html#SEC244">19.
Formatting and Printing Hardcopy</a></td></tr>
Index: Tests/texinfo_res/texinfo_38.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/texinfo_res/texinfo_38.html,v
retrieving revision 1.24
retrieving revision 1.25
diff -u -b -r1.24 -r1.25
--- Tests/texinfo_res/texinfo_38.html 30 Sep 2007 12:47:40 -0000 1.24
+++ Tests/texinfo_res/texinfo_38.html 3 Oct 2007 09:34:51 -0000 1.25
@@ -167,7 +167,7 @@
<tr><td></td><td valign="top"><a href="texinfo_6.html#IDX93">Include files,
and section levels</a></td><td valign="top"><a href="texinfo_6.html#SEC84">5.12
<code>@raisesections</code> and <code>@lowersections</code></a></td></tr>
<tr><td></td><td valign="top"><a href="texinfo_11.html#SEC146">Including a
file verbatim</a></td><td valign="top"><a href="texinfo_11.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="texinfo_4.html#SEC51">Including
permissions text</a></td><td valign="top"><a href="texinfo_4.html#SEC51">3.3.2
<code>@insertcopying</code>: Include permissions text</a></td></tr>
-<tr><td></td><td valign="top"><a href="texinfo_11.html#SEC151">Indentation
undoing</a></td><td valign="top"><a href="texinfo_11.html#SEC151">10.10
<code>@exdent</code>: Undoing a Line's Indentation</a></td></tr>
+<tr><td></td><td valign="top"><a href="texinfo_11.html#SEC151">Indentation
undoing</a></td><td valign="top"><a href="texinfo_11.html#SEC151">10.10
<code>@exdent</code>: Undoing a Line’s Indentation</a></td></tr>
<tr><td></td><td valign="top"><a href="texinfo_4.html#SEC66">Indenting
environments</a></td><td valign="top"><a href="texinfo_4.html#SEC66">3.6.4
<code>@exampleindent</code>: Environment Indenting</a></td></tr>
<tr><td></td><td valign="top"><a href="texinfo_4.html#SEC65">Indenting
paragraphs, control of</a></td><td valign="top"><a
href="texinfo_4.html#SEC65">3.6.3 Paragraph Indenting</a></td></tr>
<tr><td></td><td valign="top"><a href="texinfo_13.html#SEC169">Index
entries</a></td><td valign="top"><a href="texinfo_13.html#SEC169">12.3 Defining
the Entries of an Index</a></td></tr>
@@ -197,7 +197,7 @@
<tr><td></td><td valign="top"><a href="texinfo_27.html#SEC315">Info validating
a large file</a></td><td valign="top"><a href="texinfo_27.html#SEC315">F.5.1
Running <code>Info-validate</code></a></td></tr>
<tr><td></td><td valign="top"><a href="texinfo_21.html#SEC261">Info, creating
an online file</a></td><td valign="top"><a href="texinfo_21.html#SEC261">20.1
Creating an Info File</a></td></tr>
<tr><td></td><td valign="top"><a
href="texinfo_21.html#IDX413"><code>Info-directory-list</code></a></td><td
valign="top"><a href="texinfo_21.html#SEC274">20.2.3 Info Files in Other
Directories</a></td></tr>
-<tr><td></td><td valign="top"><a href="texinfo_8.html#SEC103">Info; other
files' nodes</a></td><td valign="top"><a href="texinfo_8.html#SEC103">7.5
Referring to Other Info Files</a></td></tr>
+<tr><td></td><td valign="top"><a href="texinfo_8.html#SEC103">Info; other
files’ nodes</a></td><td valign="top"><a href="texinfo_8.html#SEC103">7.5
Referring to Other Info Files</a></td></tr>
<tr><td></td><td valign="top"><a
href="texinfo_21.html#IDX414"><code>INFOPATH</code></a></td><td valign="top"><a
href="texinfo_21.html#SEC274">20.2.3 Info Files in Other
Directories</a></td></tr>
<tr><td></td><td valign="top"><a href="texinfo_20.html#SEC253">Initialization
file for TeX input</a></td><td valign="top"><a
href="texinfo_20.html#SEC253">19.9 Preparing for TeX</a></td></tr>
<tr><td></td><td valign="top"><a href="texinfo_18.html#SEC237">Input encoding,
declaring</a></td><td valign="top"><a href="texinfo_18.html#SEC237">17.2
<code>@documentencoding <var>enc</var></code>: Set Input Encoding</a></td></tr>
Index: Tests/texinfo_res/texinfo_39.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/texinfo_res/texinfo_39.html,v
retrieving revision 1.25
retrieving revision 1.26
diff -u -b -r1.25 -r1.26
--- Tests/texinfo_res/texinfo_39.html 5 Feb 2007 15:30:26 -0000 1.25
+++ Tests/texinfo_res/texinfo_39.html 3 Oct 2007 09:34:52 -0000 1.26
@@ -157,7 +157,7 @@
<tr><td></td><td valign="top"><a href="texinfo_13.html#IDX158">Names for
indices</a></td><td valign="top"><a href="texinfo_13.html#SEC171">12.4.1
<code>@syncodeindex</code></a></td></tr>
<tr><td></td><td valign="top"><a href="texinfo_20.html#IDX321">Names of index
files</a></td><td valign="top"><a href="texinfo_20.html#SEC246">19.2 Format
with <code>tex</code> and <code>texindex</code></a></td></tr>
<tr><td></td><td valign="top"><a href="texinfo_10.html#IDX128">Names
recommended for keys</a></td><td valign="top"><a
href="texinfo_10.html#SEC124">9.1.3
<code>@key</code>{<var>key-name</var>}</a></td></tr>
-<tr><td></td><td valign="top"><a href="texinfo_9.html#SEC114">Naming a `Top'
Node in references</a></td><td valign="top"><a href="texinfo_9.html#SEC114">8.4
Naming a `Top' Node</a></td></tr>
+<tr><td></td><td valign="top"><a href="texinfo_9.html#SEC114">Naming a
‘Top’ Node in references</a></td><td valign="top"><a
href="texinfo_9.html#SEC114">8.4 Naming a ‘Top’ Node</a></td></tr>
<tr><td></td><td valign="top"><a href="texinfo_10.html#SEC134">NASA, as
acronym</a></td><td valign="top"><a href="texinfo_10.html#SEC134">9.1.13
<code>@acronym</code>{<var>acronym</var>}</a></td></tr>
<tr><td></td><td valign="top"><a href="texinfo_21.html#IDX380">Navigation
links, omitting</a></td><td valign="top"><a
href="texinfo_21.html#SEC264">20.1.3 Options for
<code>makeinfo</code></a></td></tr>
<tr><td></td><td valign="top"><a href="texinfo_15.html#SEC213">Need space at
page bottom</a></td><td valign="top"><a href="texinfo_15.html#SEC213">14.7
<code>@need <var>mils</var></code>: Prevent Page Breaks</a></td></tr>
@@ -171,7 +171,7 @@
<tr><td></td><td valign="top"><a href="texinfo_7.html#IDX97">Node name, should
not contain @-commands</a></td><td valign="top"><a
href="texinfo_7.html#SEC92">6.3.4 <code>@node</code> Line
Requirements</a></td></tr>
<tr><td></td><td valign="top"><a href="texinfo_7.html#SEC89">Node names,
choosing</a></td><td valign="top"><a href="texinfo_7.html#SEC89">6.3.1 Choosing
Node and Pointer Names</a></td></tr>
<tr><td></td><td valign="top"><a href="texinfo_21.html#IDX378">Node
separators, omitting</a></td><td valign="top"><a
href="texinfo_21.html#SEC264">20.1.3 Options for
<code>makeinfo</code></a></td></tr>
-<tr><td></td><td valign="top"><a href="texinfo_4.html#SEC59">Node,
`Top'</a></td><td valign="top"><a href="texinfo_4.html#SEC59">3.5 The `Top'
Node and Master Menu</a></td></tr>
+<tr><td></td><td valign="top"><a href="texinfo_4.html#SEC59">Node,
‘Top’</a></td><td valign="top"><a href="texinfo_4.html#SEC59">3.5
The ‘Top’ Node and Master Menu</a></td></tr>
<tr><td></td><td valign="top"><a href="texinfo_7.html#SEC88">Node,
defined</a></td><td valign="top"><a href="texinfo_7.html#SEC88">6.3 The
<code>@node</code> Command</a></td></tr>
<tr><td></td><td valign="top"><a href="texinfo_8.html#SEC98">Nodes for menus
are short</a></td><td valign="top"><a href="texinfo_8.html#SEC98">Menus Need
Short Nodes</a></td></tr>
<tr><td></td><td valign="top"><a href="texinfo_8.html#SEC103">Nodes in other
Info files</a></td><td valign="top"><a href="texinfo_8.html#SEC103">7.5
Referring to Other Info Files</a></td></tr>
@@ -183,7 +183,7 @@
<tr><th><a name="INDEX5_1">O</a></th><td></td><td></td></tr>
<tr><td></td><td valign="top"><a
href="texinfo_14.html#IDX212">ø</a></td><td valign="top"><a
href="texinfo_14.html#SEC183">13.3 Inserting Accents</a></td></tr>
<tr><td></td><td valign="top"><a
href="texinfo_14.html#IDX214">Ø</a></td><td valign="top"><a
href="texinfo_14.html#SEC183">13.3 Inserting Accents</a></td></tr>
-<tr><td></td><td valign="top"><a href="texinfo_2.html#IDX11">O'Dea,
Brendan</a></td><td valign="top"><a href="texinfo_2.html#SEC4">1.2 Using
Texinfo</a></td></tr>
+<tr><td></td><td valign="top"><a href="texinfo_2.html#IDX11">O’Dea,
Brendan</a></td><td valign="top"><a href="texinfo_2.html#SEC4">1.2 Using
Texinfo</a></td></tr>
<tr><td></td><td valign="top"><a href="texinfo_30.html#SEC321">Obtaining
TeX</a></td><td valign="top"><a href="texinfo_30.html#SEC321">I. How to Obtain
TeX</a></td></tr>
<tr><td></td><td valign="top"><a href="texinfo_27.html#SEC313">Occurrences,
listing with <code>@occur</code></a></td><td valign="top"><a
href="texinfo_27.html#SEC313">F.4 Using <code>occur</code></a></td></tr>
<tr><td></td><td valign="top"><a
href="texinfo_14.html#IDX216">œ</a></td><td valign="top"><a
href="texinfo_14.html#SEC183">13.3 Inserting Accents</a></td></tr>
@@ -192,7 +192,7 @@
<tr><td></td><td valign="top"><a href="texinfo_21.html#SEC264">Options for
<code>makeinfo</code></a></td><td valign="top"><a
href="texinfo_21.html#SEC264">20.1.3 Options for
<code>makeinfo</code></a></td></tr>
<tr><td></td><td valign="top"><a href="texinfo_17.html#SEC230">Ordinary HTML
commands, using</a></td><td valign="top"><a href="texinfo_17.html#SEC230">16.3
Raw Formatter Commands</a></td></tr>
<tr><td></td><td valign="top"><a href="texinfo_17.html#SEC230">Ordinary TeX
commands, using</a></td><td valign="top"><a href="texinfo_17.html#SEC230">16.3
Raw Formatter Commands</a></td></tr>
-<tr><td></td><td valign="top"><a href="texinfo_8.html#SEC103">Other Info
files' nodes</a></td><td valign="top"><a href="texinfo_8.html#SEC103">7.5
Referring to Other Info Files</a></td></tr>
+<tr><td></td><td valign="top"><a href="texinfo_8.html#SEC103">Other Info
files’ nodes</a></td><td valign="top"><a href="texinfo_8.html#SEC103">7.5
Referring to Other Info Files</a></td></tr>
<tr><td></td><td valign="top"><a href="texinfo_3.html#SEC25">Outline of file
structure, showing it</a></td><td valign="top"><a
href="texinfo_3.html#SEC25">2.3 Showing the Section Structure of a
File</a></td></tr>
<tr><td></td><td valign="top"><a href="texinfo_21.html#IDX383">Output file
splitting</a></td><td valign="top"><a href="texinfo_21.html#SEC264">20.1.3
Options for <code>makeinfo</code></a></td></tr>
<tr><td></td><td valign="top"><a href="texinfo_2.html#IDX6">Output formats,
supporting more</a></td><td valign="top"><a href="texinfo_2.html#SEC4">1.2
Using Texinfo</a></td></tr>
Index: Tests/texinfo_res/texinfo_4.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/texinfo_res/texinfo_4.html,v
retrieving revision 1.29
retrieving revision 1.30
diff -u -b -r1.29 -r1.30
--- Tests/texinfo_res/texinfo_4.html 5 Feb 2007 15:30:26 -0000 1.29
+++ Tests/texinfo_res/texinfo_4.html 3 Oct 2007 09:34:52 -0000 1.30
@@ -96,7 +96,7 @@
</td></tr>
<tr><td align="left" valign="top"><a href="#SEC52">3.4 Title and Copyright
Pages</a></td><td> </td><td align="left" valign="top"> Creating the
title and copyright pages.
</td></tr>
-<tr><td align="left" valign="top"><a href="#SEC59">3.5 The `Top' Node and
Master Menu</a></td><td> </td><td align="left" valign="top">
Creating the `Top' node and master menu.
+<tr><td align="left" valign="top"><a href="#SEC59">3.5 The ‘Top’
Node and Master Menu</a></td><td> </td><td align="left"
valign="top"> Creating the ‘Top’ node and master
menu.
</td></tr>
<tr><td align="left" valign="top"><a href="#SEC62">3.6 Global Document
Commands</a></td><td> </td><td align="left" valign="top">
Affecting formatting throughout.
</td></tr>
@@ -541,7 +541,7 @@
insert the text at appropriate points.
</p>
<table class="menu" border="0" cellspacing="0">
-<tr><td align="left" valign="top"><a href="#SEC50">3.3.1
<code>@copying</code>: Declare copying
permissions</a></td><td> </td><td align="left" valign="top">
Declare the document's copying permissions.
+<tr><td align="left" valign="top"><a href="#SEC50">3.3.1
<code>@copying</code>: Declare copying
permissions</a></td><td> </td><td align="left" valign="top">
Declare the document’s copying permissions.
</td></tr>
<tr><td align="left" valign="top"><a href="#SEC51">3.3.2
<code>@insertcopying</code>: Include permissions
text</a></td><td> </td><td align="left" valign="top">
Where to insert the permissions.
</td></tr>
@@ -587,7 +587,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’s there to
improve
readability in some contexts.
</p>
<p>See section <a href="texinfo_24.html#SEC296">GNU Sample Texts</a>, for the
full text to be used in GNU manuals.
@@ -596,7 +596,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’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>
@@ -609,7 +609,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 ‘Copyright’ must always be written in English, even if
the
manual is otherwise in another language. This is due to international
law.
</p>
@@ -621,10 +621,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 ‘Free
+Software Foundation, Inc.’.
</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 ‘Copyright Notices’ in <cite>GNU Maintenance
Instructions</cite>, for
additional information.
</p>
@@ -659,8 +659,8 @@
must be used on the copyright page in the printed manual
(see section <a href="#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="#SEC59">The `Top' Node and Master Menu</a>). Here's why:
+<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="#SEC59">The ‘Top’ Node and Master Menu</a>). Here’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
@@ -702,7 +702,7 @@
</tr></table>
<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’s name and author are usually printed
on
a title page. Copyright information is usually printed on the back of
the title page.
</p>
@@ -787,8 +787,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="#SEC59">The `Top' Node and Master Menu</a>.)
+the program. (The ‘Top’ node should also contain this
information; see
+<a href="#SEC59">The ‘Top’ 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
@@ -1201,9 +1201,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"> 3.5 The `Top' Node and Master Menu </h2>
+<h2 class="section"> 3.5 The ‘Top’ Node and Master Menu </h2>
-<p>The `Top' node is the node in which a reader enters an Info manual. As
+<p>The ‘Top’ 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="#SEC49">Document Permissions</a>) to provide a brief
description of the
manual (including the version number) and copying permissions, and end
@@ -1215,7 +1215,7 @@
containing the title of the document immediately after the <code>@node
Top</code> line (see section <a href="texinfo_7.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 ‘Top’ 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;
@@ -1500,7 +1500,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’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="#SEC58">The <code>@headings</code> Command</a>.
</p>
@@ -1514,7 +1514,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’t want the
default option (no blank pages, same headers on all pages) use the
‘<samp>--texinfo</samp>’ option to <code>texi2dvi</code> to
specify the output
you want.
@@ -1661,7 +1661,7 @@
<p>If the Texinfo file has a section containing the “General Public
License” 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 ‘Top’ 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/texinfo_res/texinfo_40.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/texinfo_res/texinfo_40.html,v
retrieving revision 1.78
retrieving revision 1.79
diff -u -b -r1.78 -r1.79
--- Tests/texinfo_res/texinfo_40.html 5 Feb 2007 15:30:26 -0000 1.78
+++ Tests/texinfo_res/texinfo_40.html 3 Oct 2007 09:34:52 -0000 1.79
@@ -250,7 +250,7 @@
<tr><td></td><td valign="top"><a href="texinfo_27.html#SEC308">Structure,
catching mistakes in</a></td><td valign="top"><a
href="texinfo_27.html#SEC308">F. Formatting Mistakes</a></td></tr>
<tr><td></td><td valign="top"><a href="texinfo_6.html#SEC72">Structuring of
chapters</a></td><td valign="top"><a href="texinfo_6.html#SEC72">5. Chapter
Structuring</a></td></tr>
<tr><td></td><td valign="top"><a href="texinfo_6.html#SEC82">Subsection-like
commands</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">Subsub
commands</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">Subsub
commands</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_2.html#SEC3">Suggestions for
Texinfo, making</a></td><td valign="top"><a href="texinfo_2.html#SEC3">1.1
Reporting Bugs</a></td></tr>
<tr><td></td><td valign="top"><a href="texinfo_4.html#SEC63">Summary of
document</a></td><td valign="top"><a href="texinfo_4.html#SEC63">3.6.1
<code>@documentdescription</code>: Summary text</a></td></tr>
<tr><td></td><td valign="top"><a href="texinfo_2.html#SEC8">Syntactic
conventions</a></td><td valign="top"><a href="texinfo_2.html#SEC8">1.6 General
Syntactic Conventions</a></td></tr>
@@ -265,7 +265,7 @@
<tr><td></td><td valign="top"><a href="texinfo_12.html#SEC161">Tables with
indexes</a></td><td valign="top"><a href="texinfo_12.html#SEC161">11.3.1
<code>@ftable</code> and <code>@vtable</code></a></td></tr>
<tr><td></td><td valign="top"><a href="texinfo_12.html#SEC163">Tables, making
multi-column</a></td><td valign="top"><a href="texinfo_12.html#SEC163">11.4
Multi-column Tables</a></td></tr>
<tr><td></td><td valign="top"><a href="texinfo_12.html#SEC159">Tables, making
two-column</a></td><td valign="top"><a href="texinfo_12.html#SEC159">11.3
Making a Two-column Table</a></td></tr>
-<tr><td></td><td valign="top"><a href="texinfo_2.html#IDX15">Tabs; don't
use!</a></td><td valign="top"><a href="texinfo_2.html#SEC8">1.6 General
Syntactic Conventions</a></td></tr>
+<tr><td></td><td valign="top"><a href="texinfo_2.html#IDX15">Tabs; don’t
use!</a></td><td valign="top"><a href="texinfo_2.html#SEC8">1.6 General
Syntactic Conventions</a></td></tr>
<tr><td></td><td valign="top"><a href="texinfo_21.html#SEC269">Tag table,
making automatically</a></td><td valign="top"><a
href="texinfo_21.html#SEC269">20.1.8 Tag Files and Split Files</a></td></tr>
<tr><td></td><td valign="top"><a href="texinfo_27.html#IDX463">Tag table,
making manually</a></td><td valign="top"><a href="texinfo_27.html#SEC316">F.5.2
Creating an Unsplit File</a></td></tr>
<tr><td></td><td valign="top"><a href="texinfo_7.html#SEC96">Targets for
cross-references, arbitrary</a></td><td valign="top"><a
href="texinfo_7.html#SEC96">6.5 <code>@anchor</code>: Defining Arbitrary
Cross-reference Targets</a></td></tr>
@@ -309,12 +309,12 @@
<tr><td></td><td valign="top"><a href="texinfo_4.html#IDX82">Title page,
bastard</a></td><td valign="top"><a href="texinfo_4.html#SEC53">3.4.1
<code>@titlepage</code></a></td></tr>
<tr><td></td><td valign="top"><a href="texinfo_4.html#IDX77">Title page, for
plain text</a></td><td valign="top"><a href="texinfo_4.html#SEC52">3.4 Title
and Copyright Pages</a></td></tr>
<tr><td></td><td valign="top"><a href="texinfo_4.html#SEC57">Titlepage end
starts headings</a></td><td valign="top"><a href="texinfo_4.html#SEC57">3.4.5
Heading Generation</a></td></tr>
-<tr><td></td><td valign="top"><a href="texinfo_4.html#SEC59">Top
node</a></td><td valign="top"><a href="texinfo_4.html#SEC59">3.5 The `Top' Node
and Master Menu</a></td></tr>
+<tr><td></td><td valign="top"><a href="texinfo_4.html#SEC59">Top
node</a></td><td valign="top"><a href="texinfo_4.html#SEC59">3.5 The
‘Top’ Node and Master Menu</a></td></tr>
<tr><td></td><td valign="top"><a href="texinfo_4.html#SEC60">Top node
example</a></td><td valign="top"><a href="texinfo_4.html#SEC60">3.5.1 Top Node
Example</a></td></tr>
<tr><td></td><td valign="top"><a href="texinfo_7.html#SEC93">Top node is
first</a></td><td valign="top"><a href="texinfo_7.html#SEC93">6.3.5 The First
Node</a></td></tr>
-<tr><td></td><td valign="top"><a
href="texinfo_9.html#SEC114">‘<samp><span
class="roman">Top</span></samp>’ node naming for references</a></td><td
valign="top"><a href="texinfo_9.html#SEC114">8.4 Naming a `Top'
Node</a></td></tr>
+<tr><td></td><td valign="top"><a
href="texinfo_9.html#SEC114">‘<samp><span
class="roman">Top</span></samp>’ node naming for references</a></td><td
valign="top"><a href="texinfo_9.html#SEC114">8.4 Naming a ‘Top’
Node</a></td></tr>
<tr><td></td><td valign="top"><a href="texinfo_6.html#SEC73">Tree
structuring</a></td><td valign="top"><a href="texinfo_6.html#SEC73">5.1 Tree
Structure of Sections</a></td></tr>
-<tr><td></td><td valign="top"><a href="texinfo_16.html#SEC217">Two `First'
Lines for <code>@deffn</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">Two
‘First’ Lines for <code>@deffn</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_13.html#IDX156">Two letter
names for indices</a></td><td valign="top"><a
href="texinfo_13.html#SEC171">12.4.1 <code>@syncodeindex</code></a></td></tr>
<tr><td></td><td valign="top"><a href="texinfo_12.html#SEC162">Two named items
for <code>@table</code></a></td><td valign="top"><a
href="texinfo_12.html#SEC162">11.3.2 <code>@itemx</code></a></td></tr>
<tr><td></td><td valign="top"><a href="texinfo_8.html#SEC101">Two part menu
entry</a></td><td valign="top"><a href="texinfo_8.html#SEC101">7.3 Less
Cluttered Menu Entry</a></td></tr>
Index: Tests/texinfo_res/texinfo_5.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/texinfo_res/texinfo_5.html,v
retrieving revision 1.25
retrieving revision 1.26
diff -u -b -r1.25 -r1.26
--- Tests/texinfo_res/texinfo_5.html 5 Feb 2007 15:30:26 -0000 1.25
+++ Tests/texinfo_res/texinfo_5.html 3 Oct 2007 09:34:52 -0000 1.26
@@ -248,7 +248,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’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/texinfo_res/texinfo_6.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/texinfo_res/texinfo_6.html,v
retrieving revision 1.28
retrieving revision 1.29
diff -u -b -r1.28 -r1.29
--- Tests/texinfo_res/texinfo_6.html 5 Feb 2007 15:30:26 -0000 1.28
+++ Tests/texinfo_res/texinfo_6.html 3 Oct 2007 09:34:52 -0000 1.29
@@ -96,14 +96,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—but you don't need to.
+heading at the top of each node—but you don’t need to.
</p>
<table class="menu" border="0" cellspacing="0">
<tr><td align="left" valign="top"><a href="#SEC73">5.1 Tree Structure of
Sections</a></td><td> </td><td align="left" valign="top">
A manual is like an upside down tree …
</td></tr>
<tr><td align="left" valign="top"><a href="#SEC74">5.2 Structuring Command
Types</a></td><td> </td><td align="left" valign="top"> How to
divide a manual into parts.
</td></tr>
-<tr><td align="left" valign="top"><a href="#SEC75">5.3
<code>@top</code></a></td><td> </td><td align="left" valign="top">
The <code>@top</code> command, part of the `Top' node.
+<tr><td align="left" valign="top"><a href="#SEC75">5.3
<code>@top</code></a></td><td> </td><td align="left" valign="top">
The <code>@top</code> command, part of the ‘Top’ node.
</td></tr>
<tr><td align="left" valign="top"><a href="#SEC76">5.4
<code>@chapter</code></a></td><td> </td><td align="left"
valign="top">
</td></tr>
@@ -119,9 +119,9 @@
</td></tr>
<tr><td align="left" valign="top"><a href="#SEC82">5.10 The
<code>@subsection</code>-like Commands</a></td><td> </td><td
align="left" valign="top">
</td></tr>
-<tr><td align="left" valign="top"><a href="#SEC83">5.11 The `subsub'
Commands</a></td><td> </td><td align="left" valign="top">
Commands for the lowest level sections.
+<tr><td align="left" valign="top"><a href="#SEC83">5.11 The
‘subsub’ Commands</a></td><td> </td><td align="left"
valign="top"> Commands for the lowest level sections.
</td></tr>
-<tr><td align="left" valign="top"><a href="#SEC84">5.12
<code>@raisesections</code> and
<code>@lowersections</code></a></td><td> </td><td align="left"
valign="top"> How to change commands' hierarchical level.
+<tr><td align="left" valign="top"><a href="#SEC84">5.12
<code>@raisesections</code> and
<code>@lowersections</code></a></td><td> </td><td align="left"
valign="top"> How to change commands’ hierarchical level.
</td></tr>
</table>
@@ -292,7 +292,7 @@
<p>The <code>@top</code> command is a special sectioning command that you use
only after an ‘<samp>@node Top</samp>’ 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 ‘Top’ 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="#SEC77"><code>@unnumbered</code> and <code>@appendix</code></a>). For
detailed information, see <a href="texinfo_7.html#SEC94">The <code>@top</code>
Command</a>.
</p>
@@ -614,10 +614,10 @@
<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"> 5.11 The `subsub' Commands </h2>
+<h2 class="section"> 5.11 The ‘subsub’ Commands </h2>
<p>The fourth and lowest level sectioning commands in Texinfo are the
-`subsub' commands. They are:
+‘subsub’ commands. They are:
</p>
<dl compact="compact">
<dt> <code>@subsubsection</code></dt>
@@ -649,7 +649,7 @@
</p></dd>
</dl>
-<p>In Info, `subsub' titles are underlined with periods.
+<p>In Info, ‘subsub’ titles are underlined with periods.
For example,
</p>
<table><tr><td> </td><td><pre class="example">@subsubsection This is a
subsubsection
@@ -738,8 +738,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 ‘chapters’ reproduces chapter
commands; an
+attempt to lower below ‘subsubsections’ reproduces subsubsection
commands.
</p>
<hr size="6">
Index: Tests/texinfo_res/texinfo_7.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/texinfo_res/texinfo_7.html,v
retrieving revision 1.30
retrieving revision 1.31
diff -u -b -r1.30 -r1.31
--- Tests/texinfo_res/texinfo_7.html 5 Feb 2007 15:30:26 -0000 1.30
+++ Tests/texinfo_res/texinfo_7.html 3 Oct 2007 09:34:52 -0000 1.31
@@ -181,7 +181,7 @@
<p>The “root” is at the top of the diagram and the
“leaves” 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 ‘Top’ node, and ‘Up’ node pointers carry
you closer to the
root.
</p>
<table><tr><td> </td><td><pre class="example">
Top
@@ -203,20 +203,20 @@
</pre></td></tr></table>
<p>This <code>@node</code> line says that the name of this node is
“Chapter
-2”, the name of the `Next' node is “Chapter 3”, the name of
the
-`Previous' node is “Chapter 1”, and the name of the `Up' node is
+2”, the name of the ‘Next’ node is “Chapter 3”,
the name of the
+‘Previous’ node is “Chapter 1”, and the name of the
‘Up’ node is
“Top”. You can omit writing out these node names if your document
is
hierarchically organized (see section <a href="#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> ‘Next’ 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—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. ‘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
a chapter or chapter-level node.)
</p></blockquote>
@@ -236,12 +236,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 ‘Next’ and ‘Previous’ pointers
of a node usually
lead to other nodes at the same level—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 ‘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;
see <a href="texinfo_9.html#SEC104">Cross References</a>.)
</p>
<p>Usually, an <code>@node</code> command and a chapter structuring command are
@@ -301,12 +301,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
+‘Next’, ‘Previous’, and ‘Up’ pointers, in
that order, and may be omitted
if your Texinfo document is hierarchically organized (see section <a
href="#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,
+‘Next’, ‘Previous’, and ‘Up’ 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>
@@ -335,7 +335,7 @@
</td></tr>
<tr><td align="left" valign="top"><a href="#SEC92">6.3.4 <code>@node</code>
Line Requirements</a></td><td> </td><td align="left" valign="top">
Keep names unique, without @-commands.
</td></tr>
-<tr><td align="left" valign="top"><a href="#SEC93">6.3.5 The First
Node</a></td><td> </td><td align="left" valign="top">
How to write a `Top' node.
+<tr><td align="left" valign="top"><a href="#SEC93">6.3.5 The First
Node</a></td><td> </td><td align="left" valign="top">
How to write a ‘Top’ node.
</td></tr>
<tr><td align="left" valign="top"><a href="#SEC94">6.3.6 The <code>@top</code>
Sectioning Command</a></td><td> </td><td align="left" valign="top">
How to use the <code>@top</code> command.
</td></tr>
@@ -366,20 +366,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’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
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’s ‘Previous’ node is the same as its ‘Up’
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 ‘<tt>dir</tt>’ file,
which
+<p>Usually, the first node of a Texinfo file is the ‘Top’ node,
and its
+‘Up’ and ‘Previous’ pointers point to the
‘<tt>dir</tt>’ 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 ‘Top’ 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="#SEC93">The First Node</a>, for information
on how to write the
+‘Top’ node. See section <a href="#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
@@ -422,7 +422,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_3.html#SEC21">Using Texinfo Mode</a>, and <a
href="#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 ‘Next’,
‘Previous’, and ‘Up’
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
‘<samp>@node</samp>’ and a comment line listing the names of the
pointers in
@@ -430,8 +430,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 ‘Next’,
‘Previous’,
+and ‘Up’ pointers looks like this:
</p>
<table><tr><td> </td><td><pre class="example">@node <var>node-name</var>,
<var>next</var>, <var>previous</var>, <var>up</var>
</pre></td></tr></table>
@@ -611,7 +611,7 @@
<p>The first node of a Texinfo file is the <em>Top</em> node, except in an
included file (see section <a href="texinfo_25.html#SEC297">Include
Files</a>). The Top node should contain a
-short summary, copying permissions, and a master menu. See section <a
href="texinfo_4.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="texinfo_4.html#SEC59">The ‘Top’ 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>
@@ -620,7 +620,7 @@
<a name="IDX106"></a>
<a name="IDX107"></a>
The Top node (which must be named ‘<samp>top</samp>’ or
‘<samp>Top</samp>’) should have
-as its `Up' node the name of a node in another file, where there is a
+as its ‘Up’ 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;
@@ -630,7 +630,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 ‘Previous’ node of the Top
node to
be ‘<samp>(dir)</samp>’, as it causes confusing behavior for
users: if you are
in the Top node and hits <DEL> to go backwards, you wind up in the
middle of the some other entry in the ‘<tt>dir</tt>’ file, which
has nothing
@@ -638,7 +638,7 @@
</li><li>
<a name="IDX109"></a>
-The `Next' node of the Top node should be the first chapter in your
+The ‘Next’ node of the Top node should be the first chapter in your
document.
</li></ul>
@@ -679,7 +679,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 ‘Top’ 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
@@ -730,18 +730,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.
+‘Next’, ‘Previous’, and ‘Up’ 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 ‘Top’ <code>@node</code> line
with a line
+beginning with <code>@top</code> to mark the ‘Top’ node in the
file. See section <a href="texinfo_6.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
‘Top’
node) in a menu that is one or more hierarchical levels above the
-node's hierarchical level.
+node’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
@@ -794,13 +794,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 ‘x-spot’ just before the word
‘spot’.
You can refer to it later with an <code>@xref</code> or other cross-reference
command, as shown. See section <a href="texinfo_9.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’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>.
@@ -808,7 +808,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 ‘goto-node’ in <cite>GNU Info</cite>.)
</p>
<hr size="6">
Index: Tests/texinfo_res/texinfo_8.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/texinfo_res/texinfo_8.html,v
retrieving revision 1.28
retrieving revision 1.29
diff -u -b -r1.28 -r1.29
--- Tests/texinfo_res/texinfo_8.html 5 Feb 2007 15:30:26 -0000 1.28
+++ Tests/texinfo_res/texinfo_8.html 3 Oct 2007 09:34:52 -0000 1.29
@@ -243,7 +243,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’s up to you.
</p>
<hr size="6">
@@ -400,10 +400,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 ‘Top’ node.
</p>
<p>The ‘<tt>dir</tt>’ 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
‘Top’
nodes of each Info document. (See section <a
href="texinfo_21.html#SEC271">Installing an Info File</a>.)
</p>
<p>For example:
Index: Tests/texinfo_res/texinfo_9.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/texinfo_res/texinfo_9.html,v
retrieving revision 1.31
retrieving revision 1.32
diff -u -b -r1.31 -r1.32
--- Tests/texinfo_res/texinfo_9.html 5 Feb 2007 15:30:26 -0000 1.31
+++ Tests/texinfo_res/texinfo_9.html 3 Oct 2007 09:34:52 -0000 1.32
@@ -91,9 +91,9 @@
</td></tr>
<tr><td align="left" valign="top"><a href="#SEC107">8.2 Parts of a Cross
Reference</a></td><td> </td><td align="left" valign="top"> A
cross reference has several parts.
</td></tr>
-<tr><td align="left" valign="top"><a href="#SEC108">8.3
<code>@xref</code></a></td><td> </td><td align="left" valign="top">
Begin a reference with `See' …
+<tr><td align="left" valign="top"><a href="#SEC108">8.3
<code>@xref</code></a></td><td> </td><td align="left" valign="top">
Begin a reference with ‘See’ …
</td></tr>
-<tr><td align="left" valign="top"><a href="#SEC114">8.4 Naming a `Top'
Node</a></td><td> </td><td align="left" valign="top">
How to refer to the beginning of another file.
+<tr><td align="left" valign="top"><a href="#SEC114">8.4 Naming a
‘Top’ Node</a></td><td> </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="#SEC115">8.5
<code>@ref</code></a></td><td> </td><td align="left" valign="top">
A reference for the last part of a sentence.
</td></tr>
@@ -135,7 +135,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’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
@@ -166,20 +166,20 @@
</p>
<dl compact="compact">
<dt> <code>@xref</code></dt>
-<dd><p>Used to start a sentence in the printed manual saying `See …'
+<dd><p>Used to start a sentence in the printed manual saying ‘See
…’
or an Info cross-reference saying ‘<samp>*Note <var>name</var>:
<var>node</var>.</samp>’.
</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 ‘See’.
</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. (‘<samp>p</samp>’ is for `parenthesis'.)
+file and a printed book. Starts with a lower case ‘see’ within the
+printed manual. (‘<samp>p</samp>’ is for
‘parenthesis’.)
</p>
</dd>
<dt> <code>@inforef</code></dt>
@@ -606,7 +606,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’s Guide</cite>:
</p>
<table><tr><td> </td><td><pre class="smallexample">@xref{Sample Program}.
@xref{Glossary}.
@@ -738,14 +738,14 @@
<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"> 8.4 Naming a `Top' Node </h2>
+<h2 class="section"> 8.4 Naming a ‘Top’ 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 ‘Top’ 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="texinfo_8.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 ‘Top’), you must write an
appropriate
entry for the third argument to the <code>@xref</code> command.
</p>
@@ -789,7 +789,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 ‘See’ in the printed output, just the reference
itself.
This makes it useful as the last part of a sentence.
</p>
<p>For example,
@@ -861,14 +861,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’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'.
+‘see’ rather than an upper case ‘See’.
</li><li>
The Info formatting commands automatically end the reference with a
@@ -1104,15 +1104,15 @@
<p>To merely indicate a url without creating a link people can follow, use
<code>@url</code> (see section <a
href="texinfo_10.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’s in the unambiguous format:
</p>
<table><tr><td> </td><td><pre
class="display"><URL:http://<var>host</var>/<var>path</var>>
</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’s not
necessary to clutter up the output with the extra
‘<samp><URL:</samp>’ and
-‘<samp>></samp>’, since any software that tries to detect url's
in text already
+‘<samp>></samp>’, since any software that tries to detect
url’s in text already
has to detect them without the ‘<samp><URL:</samp>’ to be
useful.
</p>
Index: Tests/texinfo_res/texinfo_fot.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/texinfo_res/texinfo_fot.html,v
retrieving revision 1.18
retrieving revision 1.19
diff -u -b -r1.18 -r1.19
--- Tests/texinfo_res/texinfo_fot.html 5 Feb 2007 15:30:26 -0000 1.18
+++ Tests/texinfo_res/texinfo_fot.html 3 Oct 2007 09:34:52 -0000 1.19
@@ -74,13 +74,13 @@
but is not the same as, the pronunciation of TeX. In the word
TeX, the ‘<samp>X</samp>’ is actually the Greek letter
“chi” rather than
the English letter “ex”. Pronounce TeX as if the
‘<samp>X</samp>’ were the
-last sound in the name `Bach'; but pronounce Texinfo as if the
‘<samp>x</samp>’
-were a `k'. Spell “Texinfo” with a capital “T” and
the other
+last sound in the name ‘Bach’; but pronounce Texinfo as if the
‘<samp>x</samp>’
+were a ‘k’. Spell “Texinfo” with a capital
“T” and the other
letters in lower case.
</p><h3><a name="FOOT2" href="texinfo_2.html#DOCF2">(2)</a></h3>
-<p>In some documents, the first child has no `Previous'
+<p>In some documents, the first child has no ‘Previous’
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 ‘Next’ pointer.
</p><h3><a name="FOOT3" href="texinfo_2.html#DOCF3">(3)</a></h3>
<p>You can also use the
<a name="IDX13"></a>
@@ -95,15 +95,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 ‘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.
</p><h3><a name="FOOT5" href="texinfo_4.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
+‘editions’ and versions of programs as ‘versions’;
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="texinfo_8.html#DOCF6">(6)</a></h3>
Index: Tests/texinfo_res/texinfo_toc.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/texinfo_res/texinfo_toc.html,v
retrieving revision 1.21
retrieving revision 1.22
diff -u -b -r1.21 -r1.22
--- Tests/texinfo_res/texinfo_toc.html 30 Sep 2007 12:47:40 -0000 1.21
+++ Tests/texinfo_res/texinfo_toc.html 3 Oct 2007 09:34:52 -0000 1.22
@@ -125,7 +125,7 @@
<li><a name="TOC40" href="texinfo_4.html#SEC57">3.4.5 Heading
Generation</a></li>
<li><a name="TOC41" href="texinfo_4.html#SEC58">3.4.6 The
<code>@headings</code> Command</a></li>
</ul></li>
- <li><a name="TOC42" href="texinfo_4.html#SEC59">3.5 The `Top' Node and
Master Menu</a>
+ <li><a name="TOC42" href="texinfo_4.html#SEC59">3.5 The ‘Top’
Node and Master Menu</a>
<ul class="toc">
<li><a name="TOC43" href="texinfo_4.html#SEC60">3.5.1 Top Node
Example</a></li>
<li><a name="TOC44" href="texinfo_4.html#SEC61">3.5.2 Parts of a Master
Menu</a></li>
@@ -157,7 +157,7 @@
<li><a name="TOC63" href="texinfo_6.html#SEC80">5.8
<code>@unnumberedsec</code>, <code>@appendixsec</code>,
<code>@heading</code></a></li>
<li><a name="TOC64" href="texinfo_6.html#SEC81">5.9 The
<code>@subsection</code> Command</a></li>
<li><a name="TOC65" href="texinfo_6.html#SEC82">5.10 The
<code>@subsection</code>-like Commands</a></li>
- <li><a name="TOC66" href="texinfo_6.html#SEC83">5.11 The `subsub'
Commands</a></li>
+ <li><a name="TOC66" href="texinfo_6.html#SEC83">5.11 The
‘subsub’ Commands</a></li>
<li><a name="TOC67" href="texinfo_6.html#SEC84">5.12
<code>@raisesections</code> and <code>@lowersections</code></a></li>
</ul></li>
<li><a name="TOC68" href="texinfo_7.html#SEC85">6. Nodes</a>
@@ -195,7 +195,7 @@
<li><a name="TOC92" href="texinfo_9.html#SEC112">8.3.3
<code>@xref</code> with Three Arguments</a></li>
<li><a name="TOC93" href="texinfo_9.html#SEC113">8.3.4
<code>@xref</code> with Four and Five Arguments</a></li>
</ul></li>
- <li><a name="TOC94" href="texinfo_9.html#SEC114">8.4 Naming a `Top'
Node</a></li>
+ <li><a name="TOC94" href="texinfo_9.html#SEC114">8.4 Naming a
‘Top’ Node</a></li>
<li><a name="TOC95" href="texinfo_9.html#SEC115">8.5
<code>@ref</code></a></li>
<li><a name="TOC96" href="texinfo_9.html#SEC116">8.6
<code>@pxref</code></a></li>
<li><a name="TOC97" href="texinfo_9.html#SEC117">8.7
<code>@inforef</code></a></li>
@@ -240,7 +240,7 @@
<li><a name="TOC127" href="texinfo_11.html#SEC148">10.7
<code>@small…</code> Block Commands</a></li>
<li><a name="TOC128" href="texinfo_11.html#SEC149">10.8
<code>@display</code> and <code>@smalldisplay</code></a></li>
<li><a name="TOC129" href="texinfo_11.html#SEC150">10.9
<code>@format</code> and <code>@smallformat</code></a></li>
- <li><a name="TOC130" href="texinfo_11.html#SEC151">10.10
<code>@exdent</code>: Undoing a Line's Indentation</a></li>
+ <li><a name="TOC130" href="texinfo_11.html#SEC151">10.10
<code>@exdent</code>: Undoing a Line’s Indentation</a></li>
<li><a name="TOC131" href="texinfo_11.html#SEC152">10.11
<code>@flushleft</code> and <code>@flushright</code></a></li>
<li><a name="TOC132" href="texinfo_11.html#SEC153">10.12
<code>@noindent</code>: Omitting Indentation</a></li>
<li><a name="TOC133" href="texinfo_11.html#SEC154">10.13
<code>@cartouche</code>: Rounded Rectangles Around Examples</a></li>
@@ -332,7 +332,7 @@
<ul class="toc">
<li><a name="TOC191" href="texinfo_16.html#SEC215">15.1 The Template for a
Definition</a></li>
<li><a name="TOC192" href="texinfo_16.html#SEC216">15.2 Optional and
Repeated Arguments</a></li>
- <li><a name="TOC193" href="texinfo_16.html#SEC217">15.3 Two or More
`First' Lines</a></li>
+ <li><a name="TOC193" href="texinfo_16.html#SEC217">15.3 Two or More
‘First’ Lines</a></li>
<li><a name="TOC194" href="texinfo_16.html#SEC218">15.4 The Definition
Commands</a>
<ul class="toc">
<li><a name="TOC195" href="texinfo_16.html#SEC219">15.4.1 Functions and
Similar Entities</a></li>
Index: Tests/viper_monolithic_res/viper.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/viper_monolithic_res/viper.html,v
retrieving revision 1.38
retrieving revision 1.39
diff -u -b -r1.38 -r1.39
--- Tests/viper_monolithic_res/viper.html 6 May 2007 12:57:08 -0000
1.38
+++ Tests/viper_monolithic_res/viper.html 3 Oct 2007 09:34:52 -0000
1.39
@@ -70,7 +70,7 @@
license is included in the section entitled “GNU Free Documentation
License” in the Emacs manual.
</p>
-<p>(a) The FSF's Back-Cover Text is: “You have freedom to copy and modify
+<p>(a) The FSF’s Back-Cover Text is: “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.”
</p>
@@ -246,7 +246,7 @@
<p>Emacs can edit several files at once. A file in Emacs is placed in a
<em>buffer</em> that usually has the same name as the file. Buffers are also
used
for other purposes, such as shell interfaces, directory editing, etc.
-See <a href="emacs.html#Dired">(emacs)Dired</a> section `Directory Editor' in
<cite>The Gnu Emacs Manual</cite>, for an example.
+See <a href="emacs.html#Dired">(emacs)Dired</a> section ‘Directory
Editor’ in <cite>The Gnu Emacs Manual</cite>, for an example.
</p>
<p>A buffer has a distinguished position called the <em>point</em>.
A <em>point</em> is always between 2 characters, and is <em>looking at</em>
@@ -258,12 +258,12 @@
<p>The default settings of Viper try to mimic the behavior of Vi, preventing
the cursor from going beyond the last character on the line. By using
Emacs commands directly (such as those bound to arrow keys), it is possible
-to get the cursor beyond the end-of-line. However, this won't (or
-shouldn't) happen if you restrict yourself to standard Vi keys, unless you
+to get the cursor beyond the end-of-line. However, this won’t (or
+shouldn’t) happen if you restrict yourself to standard Vi keys, unless
you
modify the default editing style. See section <a
href="#SEC25">Customization</a>.
</p>
<p>In addition to the <em>point</em>, there is another distinguished buffer
-position called the <em>mark</em>. See <a
href="emacs.html#Mark">(emacs)Mark</a> section `Mark' in <cite>The GNU Emacs
manual</cite>, for more info on the mark. The text between the <em>point</em>
and
+position called the <em>mark</em>. See <a
href="emacs.html#Mark">(emacs)Mark</a> section ‘Mark’ in <cite>The
GNU Emacs manual</cite>, for more info on the mark. The text between the
<em>point</em> and
the <em>mark</em> is called the <em>region</em> of the buffer. For the Viper
user, this simply means that in addition to the Vi textmarkers a–z, there
is another marker called <em>mark</em>. This is similar to the unnamed Vi
@@ -322,14 +322,14 @@
keymap then that function will be executed when you type the key.
If no function is bound to a key in the
local map, however, the function bound to the key in the global map
-will be executed. See <a href="emacs.html#Major-Modes">Major Modes:
(emacs)Major Modes</a> section `Major Modes' in <cite>The GNU Emacs
Manual</cite>, for more information.
+will be executed. See <a href="emacs.html#Major-Modes">Major Modes:
(emacs)Major Modes</a> section ‘Major Modes’ in <cite>The GNU Emacs
Manual</cite>, for more information.
</p>
<p>A buffer can also have a <em>minor mode</em>. Minor modes are options that
you can use or not. A buffer in <code>text-mode</code> can have
<code>auto-fill-mode</code> as minor mode, which can be turned off or on at
any time. In Emacs, a minor mode may have it own keymap,
which overrides the local keymap when the minor mode is turned on. For
-more information, see <a href="emacs.html#Minor-Modes">Minor Modes:
(emacs)Minor Modes</a> section `Minor Modes' in <cite>The GNU Emacs
Manual</cite>
+more information, see <a href="emacs.html#Minor-Modes">Minor Modes:
(emacs)Minor Modes</a> section ‘Minor Modes’ in <cite>The GNU Emacs
Manual</cite>
</p>
<a name="IDX13"></a>
<a name="IDX14"></a>
@@ -397,7 +397,7 @@
<p>The latest versions of Emacs have an interactive customization facility,
which allows you to (mostly) bypass the use of the
‘<tt>.emacs</tt>’ and
‘<tt>.viper</tt>’ files. You can reach this customization
-facility from within Viper's VI state by executing the Ex command
+facility from within Viper’s VI state by executing the Ex command
<kbd>:customize</kbd>.
</p>
<p>Once invoked, Viper will arrange to bring up Emacs buffers in Vi state
@@ -517,7 +517,7 @@
</p>
<p>If you switch to Vi in Dired or similar modes—no harm is done. It is
just
that the special key bindings provided by those modes will be temporarily
-overshadowed by Viper's bindings. Switching back to Viper's Emacs state
+overshadowed by Viper’s bindings. Switching back to Viper’s Emacs
state
will revive the environment provided by the current major mode.
</p>
<p>States in Viper are orthogonal to Emacs major modes, such as C mode or Dired
@@ -591,7 +591,7 @@
</p>
<p>There is also a key that lets you temporarily escape to Vi command state
from Emacs or Insert states: typing <kbd>C-c \</kbd> will let you execute a
-single Vi command while staying in Viper's Emacs or Insert state.
+single Vi command while staying in Viper’s Emacs or Insert state.
In Insert state, the same can also be achieved by typing <kbd>C-z</kbd>.
</p>
@@ -649,7 +649,7 @@
‘<samp>Recursive Edits</samp>’ in Emacs for which there is no
comparable Vi
functionality and no key-binding. Recursive edits are indicated by
‘<samp>[]</samp>’ brackets framing the modes on the mode line.
-See <a href="emacs.html#Recursive-Edit">Recursive Edit: (emacs)Recursive
Edit</a> section `Recursive Edit' in <cite>The GNU Emacs Manual</cite>.
+See <a href="emacs.html#Recursive-Edit">Recursive Edit: (emacs)Recursive
Edit</a> section ‘Recursive Edit’ in <cite>The GNU Emacs
Manual</cite>.
At user level 1, <kbd>C-g</kbd> is bound to <code>viper-info-on-file</code>
function instead.
@@ -661,7 +661,7 @@
<p>Viper uses <ESC> as a switch between Insert and Vi states. Emacs uses
<ESC> for Meta. The Meta key is very important in Emacs since many
functions are accessible only via that key as <kbd>M-x function-name</kbd>.
-Therefore, we need to simulate it somehow. In Viper's Vi, Insert, and
+Therefore, we need to simulate it somehow. In Viper’s Vi, Insert, and
Replace states, the meta key is set to be <kbd>C-\</kbd>. Thus, to get
<kbd>M-x</kbd>, you should type <kbd>C-\ x</kbd> (if the keyboard has no Meta
key,
which is rare these days).
@@ -699,7 +699,7 @@
<dd><p>Viper uses Emacs Regular Expressions for searches. These are a
superset of
Vi regular
expressions, excepting the change-of-case escapes
‘<samp>\u</samp>’, ‘<samp>\L</samp>’,
-…, etc. See <a href="emacs.html#Regular-Expressions">(emacs)Regular
Expressions</a> section `Regular Expressions' in <cite>The GNU Emacs
Manual</cite>, for details.
+…, etc. See <a href="emacs.html#Regular-Expressions">(emacs)Regular
Expressions</a> section ‘Regular Expressions’ in <cite>The GNU
Emacs Manual</cite>, for details.
Files specified to <kbd>:e</kbd> use <code>csh</code> regular expressions
(globbing, wildcards, what have you).
However, the function <code>viper-toggle-search-style</code>, bound to
<kbd>C-c /</kbd>,
@@ -723,7 +723,7 @@
need for deleting file names that Emacs provides in its prompts. (This is
usually convenient, but occasionally the prompt may suggest a wrong file
name for you.) If you see a prompt <kbd>/usr/foo/</kbd> and you wish to edit
the
-file <kbd>~/.viper</kbd>, you don't have to erase the prompt. Instead, simply
+file <kbd>~/.viper</kbd>, you don’t have to erase the prompt. Instead,
simply
continue typing what you need. Emacs will interpret
<kbd>/usr/foo/~/.viper</kbd>
correctly. Similarly, if the prompt is <kbd>~/foo/</kbd> and you need to get
to
<kbd>/bar/file</kbd>, keep typing. Emacs interprets <kbd>~/foo//bar/</kbd> as
@@ -768,11 +768,11 @@
</p></dd>
</dl>
-<p>As Vi, Viper's destructive commands can be re-executed by typing
`<kbd>.</kbd>'.
+<p>As Vi, Viper’s destructive commands can be re-executed by typing
‘<kbd>.</kbd>’.
However, in addition, Viper keeps track of the history of such commands. This
history can be perused by typing <kbd>C-c M-p</kbd> and <kbd>C-c M-n</kbd>.
Having found the appropriate command, it can be then executed by typing
-`<kbd>.</kbd>'.
+‘<kbd>.</kbd>’.
See section <a href="#SEC14">Improvements over Vi</a>, for more information.
</p>
<hr size="6">
@@ -807,14 +807,14 @@
</p>
<p>Once this is done, it is possible to do quite a bit of editing in
Insert state. For instance, Emacs has a <em>yank</em> command, <kbd>C-y</kbd>,
-which is similar to Vi's <kbd>p</kbd>. However, unlike <kbd>p</kbd>,
<kbd>C-y</kbd> can be
+which is similar to Vi’s <kbd>p</kbd>. However, unlike <kbd>p</kbd>,
<kbd>C-y</kbd> can be
used in Insert state of Viper. Emacs also has a kill ring where it keeps
pieces of text you deleted while editing buffers. The command <kbd>M-y</kbd>
is
-used to delete the text previously put back by Emacs' <kbd>C-y</kbd> or by Vi's
+used to delete the text previously put back by Emacs’ <kbd>C-y</kbd> or
by Vi’s
<kbd>p</kbd> command and reinsert text that was placed on the kill-ring
earlier.
</p>
<p>This works both in Vi and Insert states.
-In Vi state, <kbd>M-y</kbd> is a much better alternative to the usual Vi's way
+In Vi state, <kbd>M-y</kbd> is a much better alternative to the usual
Vi’s way
of recovering the 10 previously deleted chunks of text. In Insert state,
you can
use this as follows. Suppose you deleted a piece of text and now you need
@@ -954,7 +954,7 @@
</dl>
<p>Most of the Emacs keys are functional in the Minibuffer. While in the
-Minibuffer, Viper tries to make editing resemble Vi's behavior when the
+Minibuffer, Viper tries to make editing resemble Vi’s behavior when the
latter is waiting for the user to type an Ex command. In particular, you
can use the regular Vi commands to edit the Minibuffer. You can switch
between the Vi state and Insert state at will, and even use the replace mode.
@@ -1062,7 +1062,7 @@
<p>Currently undisplayed files can be listed using the <kbd>:ar</kbd> command.
The
command <kbd>:n</kbd> can be given counts from the <kbd>:ar</kbd> list to
switch to
-other files. For example, use `:n3' to move to the third file in that list.
+other files. For example, use ‘:n3’ to move to the third file in
that list.
</p>
<hr size="6">
<a name="Unimplemented-Features"></a>
@@ -1260,7 +1260,7 @@
<h2 class="section"> 2.2 Undo and Backups </h2>
-<p>Viper provides multiple undo. The number of undo's and the size is limited
+<p>Viper provides multiple undo. The number of undo’s and the size is
limited
by the machine. The Viper command <kbd>u</kbd> does an undo. Undo can be
repeated by typing <kbd>.</kbd> (a period). Another <kbd>u</kbd> will undo
the undo,
and further
@@ -1272,7 +1272,7 @@
<p>Since the undo size is limited, Viper can create backup files and
auto-save files. It will normally do this automatically. It is possible
-to have numbered backups, etc. For details, see <a
href="emacs.html#Backup">(emacs)Backup</a> section `Backup and Auto-Save' in
<cite>The GNU Emacs Manual</cite>
+to have numbered backups, etc. For details, see <a
href="emacs.html#Backup">(emacs)Backup</a> section ‘Backup and
Auto-Save’ in <cite>The GNU Emacs Manual</cite>
</p>
<a name="IDX47"></a>
<a name="IDX48"></a>
@@ -1395,7 +1395,7 @@
<kbd>*</kbd>, and it can be yanked into a register using <kbd>@!register</kbd>.
This is useful for Emacs style keyboard macros defined using <kbd>C-x(</kbd>
and <kbd>C-x)</kbd>. Emacs keyboard macros have more capabilities.
-See <a href="emacs.html#Keyboard-Macros">(emacs)Keyboard Macros</a> section
`Keyboard Macros' in <cite>The GNU Emacs Manual</cite>, for
+See <a href="emacs.html#Keyboard-Macros">(emacs)Keyboard Macros</a> section
‘Keyboard Macros’ in <cite>The GNU Emacs Manual</cite>, for
details.
</p>
<p>Keyboard Macros allow an interesting form of Query-Replace:
@@ -1480,7 +1480,7 @@
as you go along. Incremental Search is normally bound to <kbd>C-s</kbd> and
<kbd>C-r</kbd>. See section <a href="#SEC25">Customization</a>, to find out
how to change the bindings
of <kbd>C-r or C-s</kbd>.
-For details, see <a href="emacs.html#Incremental-Search">(emacs)Incremental
Search</a> section `Incremental Search' in <cite>The GNU Emacs Manual</cite>
+For details, see <a href="emacs.html#Incremental-Search">(emacs)Incremental
Search</a> section ‘Incremental Search’ in <cite>The GNU Emacs
Manual</cite>
</p>
<a name="IDX54"></a>
@@ -1495,7 +1495,7 @@
<p>Finally, on a window display, Viper highlights search patterns as it finds
them. This is done through what is known as <em>faces</em> in Emacs. The
variable that controls how search patterns are highlighted is
-<code>viper-search-face</code>. If you don't want any highlighting at all, put
+<code>viper-search-face</code>. If you don’t want any highlighting at
all, put
</p><table><tr><td> </td><td><pre class="example">(copy-face 'default
'viper-search-face)
</pre></td></tr></table>
<a name="IDX56"></a>
@@ -1505,7 +1505,7 @@
from the menubar. Viper customization group is located under the
<em>Emulations</em> customization group, which in turn is under the
<em>Editing</em> group (or simply by typing <kbd>:customize</kbd>). All Viper
-faces are grouped together under Viper's
+faces are grouped together under Viper’s
<em>Highlighting</em> group.
</p>
<p>Try it: it is really simple!
@@ -1535,7 +1535,7 @@
<p>It is possible in Emacs to define abbrevs based on the contents of the
buffer.
Sophisticated templates can be defined using the Emacs abbreviation
-facilities. See <a href="emacs.html#Abbrevs">(emacs)Abbrevs</a> section
`Abbreviations' in <cite>The GNU Emacs Manual</cite>, for
+facilities. See <a href="emacs.html#Abbrevs">(emacs)Abbrevs</a> section
‘Abbreviations’ in <cite>The GNU Emacs Manual</cite>, for
details.
</p>
<a name="IDX57"></a>
@@ -1549,7 +1549,7 @@
keystroke, which appears earlier in the text. Emacs binds this to
<kbd><ESC> /</kbd>, so you will have to find a key and bind the function
<code>dabbrev-expand</code> to that key.
-Facilities like this make Vi's <kbd>:ab</kbd> command obsolete.
+Facilities like this make Vi’s <kbd>:ab</kbd> command obsolete.
</p>
<hr size="6">
<a name="Movement-and-Markers"></a>
@@ -1597,7 +1597,7 @@
Vi. However, if the value is <code>reformed-vi</code> (the default) then the
alphanumeric symbols will be those specified by the current Emacs syntax
table (which may be different for different major modes) plus the
-underscore symbol <kbd>_</kbd>, minus some non-word symbols, like '.;,|, etc.
+underscore symbol <kbd>_</kbd>, minus some non-word symbols, like ’.;,|,
etc.
Both <code>strict-vi</code> and <code>reformed-vi</code> work close to Vi in
traditional cases, but <code>reformed-vi</code> does a better job when editing
text in non-Latin alphabets.
@@ -1625,11 +1625,11 @@
<a name="IDX60"></a>
-<p>The above discussion of the meaning of Viper's words concerns only Viper's
+<p>The above discussion of the meaning of Viper’s words concerns only
Viper’s
movement commands. In regular expressions, words remain the same as in
Emacs. That is, the expressions <code>\w</code>, <code>\></code>,
<code>\<</code>, etc., use
-Emacs' idea of what is a word, and they don't look into the value of
-variable <code>viper-syntax-preference</code>. This is because Viper doesn't
change
+Emacs’ idea of what is a word, and they don’t look into the value
of
+variable <code>viper-syntax-preference</code>. This is because Viper
doesn’t change
syntax tables in fear of upsetting the various major modes that set these
tables.
</p>
@@ -1754,7 +1754,7 @@
<dd><p>Set mark at beginning and end of buffer, respectively.
</p></dd>
<dt> <kbd>m,</kbd></dt>
-<dd><p>Jump to mark and pop mark off the ring. See <a
href="emacs.html#Mark">(emacs)Mark</a> section `Mark' in <cite>The GNU Emacs
Manual</cite>, for more info.
+<dd><p>Jump to mark and pop mark off the ring. See <a
href="emacs.html#Mark">(emacs)Mark</a> section ‘Mark’ in <cite>The
GNU Emacs Manual</cite>, for more info.
</p></dd>
<dt> <kbd>] register</kbd></dt>
<dd><a name="IDX79"></a>
@@ -1836,7 +1836,7 @@
By repeatedly typing <kbd>C-c M-p</kbd> or <kbd>C-c M-n</kbd> you will cycle
Viper
through the recent history of Vi commands, displaying the commands one by
one. Once
-an appropriate command is found, it can be executed by typing `<kbd>.</kbd>'.
+an appropriate command is found, it can be executed by typing
‘<kbd>.</kbd>’.
</p>
<p>Since typing <kbd>C-c M-p</kbd> is tedious, it is more convenient to bind an
appropriate function to a function key on the keyboard and use that key.
@@ -2069,7 +2069,7 @@
<p>Viper supports both the abbreviated Vi variable names and their full
names. Variable completion is done on full names only. <TAB> and
<SPC> complete
-variable names. Typing `=' will complete the name and then will prompt for
+variable names. Typing ‘=’ will complete the name and then will
prompt for
a value, if applicable. For instance, <kbd>:se au <SPC></kbd> will
complete the
command to <kbd>:set autoindent</kbd>; <kbd>:se ta <SPC></kbd> will
complete the command
and prompt further like this: <kbd>:set tabstop = </kbd>.
@@ -2142,12 +2142,12 @@
including the new buffers.
</p>
<p>Note that typing <TAB> normally
-doesn't insert the tab, since this key is usually bound to
+doesn’t insert the tab, since this key is usually bound to
a text-formatting function, <code>indent-for-tab-command</code> (which
facilitates
programming and document writing). Instead, the tab is inserted via the
command <code>viper-insert-tab</code>, which is bound to <kbd>S-tab</kbd>
(shift + tab).
</p>
-<p>On some non-windowing terminals, Shift doesn't modify the <TAB> key,
so
+<p>On some non-windowing terminals, Shift doesn’t modify the <TAB>
key, so
<kbd>S-tab</kbd> behaves as if it were <TAB>. In such a case, you will
have
to bind <code>viper-insert-tab</code> to some other convenient key.
</p>
@@ -2163,7 +2163,7 @@
<dt> <code>viper-search-scroll-threshold 2</code></dt>
<dd><p>If search lands within this many lines of the window top or bottom, the
window will be scrolled up or down by about 1/7-th of its size, to reveal
-the context. If the value is negative—don't scroll.
+the context. If the value is negative—don’t scroll.
</p></dd>
<dt> <code>viper-tags-file-name "TAGS"</code></dt>
<dd><p>The name of the file used as the tag table.
@@ -2194,7 +2194,7 @@
is extremely slow, you might want to increase this slightly. You will know
if your terminal is slow if the <ESC> key sequences emitted by the
arrow keys are interpreted as separately typed characters (and thus the
-arrow keys won't work). Making this value too large will slow you down, so
+arrow keys won’t work). Making this value too large will slow you down,
so
exercise restraint.
</p></dd>
<dt> <code>viper-fast-keyseq-timeout 200</code></dt>
@@ -2256,12 +2256,12 @@
<dd><p>The value of this variable is the function symbol used to expand
wildcard
symbols. This is platform-dependent. The default tries to set this variable
to work with most shells, MS Windows, OS/2, etc. However, if it
-doesn't work the way you expect, you should write your own.
+doesn’t work the way you expect, you should write your own.
Use <code>viper-glob-unix-files</code> and
<code>viper-glob-mswindows-files</code> in
‘<tt>viper-util.el</tt>’ as examples.
</p>
<p>This feature is used to expand wildcards in the Ex command <kbd>:e</kbd>.
-Note that Viper doesn't support wildcards in the <kbd>:r</kbd> and
<kbd>:w</kbd>
+Note that Viper doesn’t support wildcards in the <kbd>:r</kbd> and
<kbd>:w</kbd>
commands, because file completion is a better mechanism.
<a name="IDX133"></a>
</p>
@@ -2294,7 +2294,7 @@
</p></dd>
<dt> <code>viper-keep-point-on-repeat t</code></dt>
<dd><p>If not <code>nil</code>, point is not moved when the user repeats the
previous
-command by typing `.' This is very useful for doing repeated changes with
+command by typing ‘.’ This is very useful for doing repeated
changes with
the <kbd>.</kbd> key.
</p></dd>
<dt> <code>viper-repeat-from-history-key 'f12</code></dt>
@@ -2328,7 +2328,7 @@
monochrome displays and also lays a stipple over them. On color displays,
replacement regions are highlighted with color.
</p>
-<p>If you know something about Emacs faces and don't like how Viper highlights
+<p>If you know something about Emacs faces and don’t like how Viper
highlights
replacement regions, you can change <code>viper-replace-overlay-face</code> by
specifying a new face. (Emacs faces are described in the Emacs Lisp
reference.) On a color display, the following customization method is
@@ -2375,7 +2375,7 @@
</p></dd>
<dt> <code>viper-toggle-key "\C-z"</code></dt>
<dd><p>Specifies the key used to switch from Emacs to Vi and back.
-Must be set in ‘<tt>.viper</tt>’. This variable can't be
+Must be set in ‘<tt>.viper</tt>’. This variable can’t be
changed interactively after Viper is loaded.
</p>
<p>In Insert state, this key acts as a temporary escape to Vi state, i.e., it
@@ -2491,7 +2491,7 @@
<p>Viper lets you define hot keys, i.e., you can associate keyboard keys
such as F1, Help, PgDn, etc., with Emacs Lisp functions (that may already
exist or that you will write). Each key has a "preferred form" in
-Emacs. For instance, the Up key's preferred form is [up], the Help key's
+Emacs. For instance, the Up key’s preferred form is [up], the Help
key’s
preferred form is [help], and the Undo key has the preferred form [f14].
You can find out the preferred form of a key by typing <kbd>M-x
describe-key-briefly</kbd> and then typing the key you want to know about.
@@ -2540,7 +2540,7 @@
<code>define-key</code> command, to modify
<code>viper-vi-global-user-map</code>,
<code>viper-insert-global-user-map</code>, and
<code>viper-emacs-global-user-map</code>, as
explained below. Each of these key maps affects the corresponding Viper state.
-The keymap <code>viper-insert-global-user-map</code> also affects Viper's
Replace
+The keymap <code>viper-insert-global-user-map</code> also affects
Viper’s Replace
state.
</p>
<p>If you want to
@@ -2631,7 +2631,7 @@
avoid this, one should add <code>viper-change-state-to-emacs</code> to an
appropriate hook of that major mode. (Check the function
<code>viper-set-hooks</code> in ‘<tt>viper.el</tt>’ for examples.)
However, if you
-did not set <code>viper-always</code> to <code>nil</code>, chances are that
you won't
+did not set <code>viper-always</code> to <code>nil</code>, chances are that
you won’t
need to perform the above procedure, because Viper will take care of most
useful defaults.
</p>
@@ -2680,12 +2680,12 @@
<p>On rare occasions, local keys may be added by mistake. Usually this is done
indirectly, by invoking a major mode that adds local keys (e.g.,
<code>shell-mode</code> redefines <RET>). In such a case, exiting the
wrong
-major mode won't rid you from unwanted local keys, since these keys are
+major mode won’t rid you from unwanted local keys, since these keys are
local to Viper state and the current buffer, not to the major mode.
In such situations, the remedy is to type <kbd>M-x viper-zap-local-keys</kbd>.
</p>
<p>So much about Viper-specific bindings.
-See <a href="emacs.html#Customization">(emacs)Customization</a> section
`Customization' in <cite>The GNU Emacs Manual</cite>, and the Emacs quick
reference card for the general info on key
+See <a href="emacs.html#Customization">(emacs)Customization</a> section
‘Customization’ in <cite>The GNU Emacs Manual</cite>, and the Emacs
quick reference card for the general info on key
bindings in Emacs.
</p>
<a name="IDX180"></a>
@@ -2748,12 +2748,12 @@
<kbd>)</kbd> or a <kbd>"</kbd> is missing somewhere above the current
line, <TAB> is likely to mis-indent the line.
</p>
-<p>For this reason, Viper doesn't change the standard Emacs binding of
+<p>For this reason, Viper doesn’t change the standard Emacs binding of
<TAB>, thereby sacrificing Vi compatibility
(except for users at level 1). Instead, in Viper, the key
-<kbd>S-tab</kbd> (shift+ tab) is chosen to emulate Vi's <TAB>.
+<kbd>S-tab</kbd> (shift+ tab) is chosen to emulate Vi’s <TAB>.
</p>
-<p>We should note that on some non-windowing terminals, Shift doesn't modify
+<p>We should note that on some non-windowing terminals, Shift doesn’t
modify
the <TAB> key, so <kbd>S-tab</kbd> behaves as if it were <TAB>.
In such
a case, you will have to bind <code>viper-insert-tab</code> to some other
convenient key.
@@ -2764,7 +2764,7 @@
packages. Fortunately, these modes operate on read-only buffers and are
designed not for editing files, but for special-purpose browsing, reading
news, mail, etc., and Vi commands are meaningless in these situations. For
-this reason, Viper doesn't force Vi state on such major modes—it
+this reason, Viper doesn’t force Vi state on such major modes—it
brings them in Emacs state. You can switch to Vi state by typing
<kbd>C-z</kbd>
if, for instance, you want to do Vi-style search in a buffer (although,
usually, incremental search, which is bound to <kbd>C-s</kbd>, is sufficient in
@@ -2778,7 +2778,7 @@
Vi state (but Viper thinks otherwise), you should put these major modes
on the <code>viper-emacs-state-mode-list</code> list and delete them from
<code>viper-vi-state-mode-list</code>.
-Likewise, you can force Viper's Insert state on a major mode by putting it
+Likewise, you can force Viper’s Insert state on a major mode by putting
it
in <code>viper-insert-state-mode-list</code>.
<a name="IDX186"></a>
<a name="IDX187"></a>
@@ -2813,7 +2813,7 @@
<p>that binds the misbehaving
keys. If so, use the above line to harness <code>nasty-mode</code>. If your
suspicion is wrong, no harm is done if you harness a minor mode that
-doesn't need to be harnessed.
+doesn’t need to be harnessed.
</p>
<a name="IDX189"></a>
<a name="IDX190"></a>
@@ -2847,7 +2847,7 @@
<p>Viper extends Vi with a number of useful features. This includes various
search functions, histories of search strings, Ex commands, insertions, and
-Vi's destructive commands. In addition, Viper supports file name completion
+Vi’s destructive commands. In addition, Viper supports file name
completion
and history, completion of Ex commands and variables, and many other
features. Some of these features are explained in detail elsewhere in this
document. Other features are explained here.
@@ -2879,10 +2879,10 @@
restore the original state. Likewise, quickly hitting <kbd>/</kbd> three times
will switch you from vanilla-style search to search via regular expressions.
If you hit something other than <kbd>/</kbd> after the first <kbd>/</kbd> or
if the
-second <kbd>/</kbd> doesn't follow quickly enough, then Viper will issue the
+second <kbd>/</kbd> doesn’t follow quickly enough, then Viper will issue
the
usual prompt <kbd>/</kbd> and will wait for input, as usual in Vi.
-If you don't like this behavior, you can “unrecord” these macros
in your
-‘<tt>~/.viper</tt>’ file. For instance, if you don't like the
above feature, put
+If you don’t like this behavior, you can “unrecord” these
macros in your
+‘<tt>~/.viper</tt>’ file. For instance, if you don’t like
the above feature, put
this in ‘<tt>~/.viper</tt>’:
</p><table><tr><td> </td><td><pre
class="example">(viper-set-searchstyle-toggling-macros 'undefine)
</pre></td></tr></table>
@@ -2890,23 +2890,23 @@
</dd>
<dt> <code>Vi-isms in Emacs state</code></dt>
-<dd><p>Some people find it useful to use the Vi-style search key, `/', to
invoke
+<dd><p>Some people find it useful to use the Vi-style search key,
‘/’, to invoke
search in modes which Viper leaves in emacs-state. These modes are:
<code>dired-mode</code>, <code>mh-folder-mode</code>,
<code>gnus-group-mode</code>,
<code>gnus-summary-mode</code>, <code>Info-mode</code>, and
<code>Buffer-menu-mode</code>
-(more may be added in the future). So, in the above modes, Viper binds `/'
+(more may be added in the future). So, in the above modes, Viper binds
‘/’
so that it will behave Vi-style. Furthermore, in those major modes, Viper
-binds `:' to invoke ex-style commands, like in vi-state. And, as described
-above, `//' and `///' get bound to Vi-style macros that toggle
+binds ‘:’ to invoke ex-style commands, like in vi-state. And, as
described
+above, ‘//’ and ‘///’ get bound to Vi-style macros
that toggle
case-insensitivity and regexp-search.
</p>
-<p>If you don't like these features—which I don't really
understand—you
-can unbind `/' and `:' in <code>viper-dired-modifier-map</code> (for Dired) or
in
+<p>If you don’t like these features—which I don’t really
understand—you
+can unbind ‘/’ and ‘:’ in
<code>viper-dired-modifier-map</code> (for Dired) or in
<code>viper-slash-and-colon-map</code>, for other modes.
<a name="IDX200"></a>
<a name="IDX201"></a>
</p>
-<p>To unbind the macros `//' and `///' for a major mode where you feel they
+<p>To unbind the macros ‘//’ and ‘///’ for a major
mode where you feel they
are undesirable, execute <code>viper-set-emacs-state-searchstyle-macros</code>
with a
non-nil argument. This can be done either interactively, by supplying a
prefix argument, or by placing
@@ -2924,7 +2924,7 @@
<a name="IDX205"></a>
<a name="IDX206"></a>
<p>Regular Expressions for <kbd>[[</kbd> and <kbd>]]</kbd>. Note that Emacs
defines
-Regexps for paragraphs and sentences. See <a
href="emacs.html#Paragraphs">(emacs)Paragraphs</a> section `Paragraphs and
Sentences' in <cite>The GNU Emacs Manual</cite>, for details.
+Regexps for paragraphs and sentences. See <a
href="emacs.html#Paragraphs">(emacs)Paragraphs</a> section ‘Paragraphs
and Sentences’ in <cite>The GNU Emacs Manual</cite>, for details.
</p></dd>
<dt> <code>M-x viper-set-expert-level</code></dt>
<dd><a name="IDX207"></a>
@@ -2935,16 +2935,16 @@
<p>Viper supports Emacs-style file completion when it prompts the user for a
file name. However, in many cases, the same directory may contain files
with identical prefix but different suffixes, e.g., prog.c, prog.o,
-paper.tex, paper.dvi. In such cases, completion will stop at the `.'.
+paper.tex, paper.dvi. In such cases, completion will stop at the
‘.’.
If the above variable is a list of strings representing suffixes, Viper will
try these suffixes
in the order listed and will check if the corresponding file exists.
</p>
-<p>For instance, if completion stopped at `paper.' and the user typed
+<p>For instance, if completion stopped at ‘paper.’ and the user
typed
<RET>,
-then Viper will check if the files `paper.', `paper.tex', `paper.c', etc.,
exist.
+then Viper will check if the files ‘paper.’,
‘paper.tex’, ‘paper.c’, etc., exist.
It will take the first such file. If no file exists, Viper will give a chance
-to complete the file name by typing the appropriate suffix. If `paper.' was
+to complete the file name by typing the appropriate suffix. If
‘paper.’ was
the intended file name, hitting return will accept it.
</p>
<p>To turn this feature off, set the above variable to <code>nil</code>.
@@ -2990,9 +2990,9 @@
<p>Viper keeps track of the recent history of destructive
commands, such as <kbd>dw</kbd>, <kbd>i</kbd>, etc.
In Vi state,
-the most recent command can be re-executed by hitting `<kbd>.</kbd>', as in Vi.
+the most recent command can be re-executed by hitting
‘<kbd>.</kbd>’, as in Vi.
However, repeated typing <kbd>C-c M-p</kbd> will cause Viper to show the
-previous destructive commands in the minibuffer. Subsequent hitting
`<kbd>.</kbd>'
+previous destructive commands in the minibuffer. Subsequent hitting
‘<kbd>.</kbd>’
will execute the command that was displayed last.
The key <kbd>C-c M-n</kbd> will cycle through the command history in the
opposite direction.
@@ -3018,12 +3018,12 @@
<dt> <code>viper-minibuffer-emacs-face
'viper-minibuffer-emacs-face</code></dt>
<dd><p>These faces control the appearance of the minibuffer text in the
corresponding Viper states. You can change the appearance of these faces
-through Emacs' customization widget, which is accessible through the
+through Emacs’ customization widget, which is accessible through the
menubar.
</p>
<p>Viper is located in this widget under the <em>Emulations</em> customization
subgroup of the <em>Editing</em> group. All Viper faces are grouped together
-in Viper's <em>Highlighting</em> customization subgroup.
+in Viper’s <em>Highlighting</em> customization subgroup.
</p>
<p>Note that only the text you type in is affected by the above faces.
Prompts and Minibuffer messages are not affected.
@@ -3081,8 +3081,8 @@
above block should be commented out.
</p>
<p>Even though these commands are sometimes useful, they are no substitute for
-the powerful <em>tag table</em> facility of Emacs. Viper's <kbd>:tag</kbd>
command
-in a primitive interface to Emacs tags. See <a href="emacs.html#Tags">Tags:
(emacs)Tags</a> section `Tags' in <cite>The Gnu Emacs Manual</cite>, for more
information on tags.
+the powerful <em>tag table</em> facility of Emacs. Viper’s
<kbd>:tag</kbd> command
+in a primitive interface to Emacs tags. See <a href="emacs.html#Tags">Tags:
(emacs)Tags</a> section ‘Tags’ in <cite>The Gnu Emacs
Manual</cite>, for more information on tags.
</p>
<p>The following two commands are normally bound to a mouse click and are part
of Viper. They work only if Emacs runs as an application under X
@@ -3114,8 +3114,8 @@
<p>This would bind mouse search to the action invoked by pressing the
Meta key and clicking mouse button 1. The allowed values of
<code>viper-mouse-search-key</code> are lists that contain a mouse-button
number
-(1,2, or 3) and any combination of the words `control', `meta', and
-`shift'.
+(1,2, or 3) and any combination of the words ‘control’,
‘meta’, and
+‘shift’.
</p>
<p>If the requested mouse action (e.g., (meta 1)) is already taken for other
purposes then you have to confirm your intention by placing the following
@@ -3130,16 +3130,16 @@
follows. If search is invoked via a single click, Viper chooses the region
that lies between the beginning of the “word” under the pointer
(“word”
is understood in Vi sense) and the end of that word. The only difference
-with Vi's words is that in Lisp major modes `-' is considered an
+with Vi’s words is that in Lisp major modes ‘-’ is
considered an
alphanumeric symbol. This is done for the convenience of working with Lisp
-symbols, which often have an `-' in them. Also, if you click on a
+symbols, which often have an ‘-’ in them. Also, if you click on a
non-alphanumeric character that is not a word separator (in Vi sense) then
this character will also be considered alphanumeric, provided that it is
adjacent (from either side) to an alphanumeric character. This useful
feature gives added control over the patterns selected by the mouse click.
</p>
<p>On a double-click, the region is determined by the beginning of the current
-Vi's “Word” (i.e., the largest non-separator chunk of text) and
the End
+Vi’s “Word” (i.e., the largest non-separator chunk of text)
and the End
of that “Word” (as determined by the <kbd>E</kbd> command).
</p>
<p>On a triple-click, the region consists of the entire line where the click
@@ -3198,11 +3198,11 @@
instance, if you are typing in a frame, A, and then move the mouse to frame
B and click to invoke mouse search, search (or insertion) will be performed
in frame A. To perform search/insertion in frame B, you will first have to
-shift focus there, which doesn't happen until you type a character or
-perform some other action in frame B—mouse search doesn't shift focus.
+shift focus there, which doesn’t happen until you type a character or
+perform some other action in frame B—mouse search doesn’t shift
focus.
</p>
-<p>If you decide that you don't like the above feature and always want
-search/insertion be performed in the frame where the click occurs, don't
+<p>If you decide that you don’t like the above feature and always want
+search/insertion be performed in the frame where the click occurs, don’t
bind (and unbind, if necessary) <code>viper-mouse-catch-frame-switch</code>
from
the mouse event it is bound to.
</p>
@@ -3257,9 +3257,9 @@
</p>
<p>If, however, you need to use a macro regularly, it must be given a
permanent name and saved. Emacs manual explains how to do this, but
-invocation of named Emacs macros is quite different from Vi's. First,
+invocation of named Emacs macros is quite different from Vi’s. First,
invocation of permanent Emacs macros takes time because it requires typing
-too many keys (to a Vi user's taste, anyway).
+too many keys (to a Vi user’s taste, anyway).
Second, binding such macros to function keys, for
fast access, hogs valuable real estate on the keyboard.
</p>
@@ -3283,7 +3283,7 @@
command history and in the startup file, for future use).
</p>
<p>Macros defined by mixing Vi and Emacs commands are represented as
-vectors. So, don't be confused when you see one (usually through the
+vectors. So, don’t be confused when you see one (usually through the
history of Ex commands). For instance, if <kbd>gg</kbd> is defined by typing
<kbd>l</kbd>, the up-arrow key and <kbd>M-x next-line</kbd>, its definition
will look
as follows in Emacs (in XEmacs, it looks slightly different, see below):
@@ -3297,11 +3297,11 @@
not just to printable keys. For instance, one can define a macro that will
be invoked by hitting <kbd>f3</kbd> then <kbd>f2</kbd> function keys. (The
keys
<kbd>delete</kbd> and <kbd>backspace</kbd> are excluded; also, a macro
invocation
-sequence can't start with <ESC>. Some other keys, such as <kbd>f1</kbd>
and
-<kbd>help</kbd>, can't be bound to macros under Emacs, since they
+sequence can’t start with <ESC>. Some other keys, such as
<kbd>f1</kbd> and
+<kbd>help</kbd>, can’t be bound to macros under Emacs, since they
are bound in <code>key-translation-map</code>, which overrides any other
binding
the user gives to keys. In general, keys that have a binding in
-<code>key-translation-map</code> can't be bound to a macro.)
+<code>key-translation-map</code> can’t be bound to a macro.)
</p>
<p>Fourth, in Viper, one can define macros that are specific to a given
buffer, a given major mode, or macros that are defined for all buffers. In
@@ -3315,7 +3315,7 @@
macros) lets the user define keyboard macros that ask for confirmation or
even prompt the user for input and then continue. To do this, one should
type <kbd>C-x q</kbd> (for confirmation) or <kbd>C-u C-x q</kbd> (for prompt).
-For details, see <a href="emacs.html#Kbd-Macro-Query">(emacs)Kbd Macro
Query</a> section `Customization' in <cite>The GNU Emacs Manual</cite>
+For details, see <a href="emacs.html#Kbd-Macro-Query">(emacs)Kbd Macro
Query</a> section ‘Customization’ in <cite>The GNU Emacs
Manual</cite>
</p>
<p>When the user finishes defining a macro (which is done by typing
<kbd>C-x)</kbd> —
a departure from Vi), you will be asked whether you want this
@@ -3324,7 +3324,7 @@
This is the easiest way to save a macro and make
it permanently available. If you work your startup files with bare hands,
here is how Viper saves the above macro so that it will be
-available in Viper's Insert state (and Replace state) in buffer
<code>my-buf</code>
+available in Viper’s Insert state (and Replace state) in buffer
<code>my-buf</code>
only:
</p>
<table><tr><td> </td><td><pre class="example">(viper-record-kbd-macro
"gg" 'insert-state
@@ -3385,7 +3385,7 @@
</p>
<p>If an error occurs during macro definition, Emacs
aborts the process, and it must be repeated. This is analogous to Vi,
-except that in Vi the user doesn't know there is an error until the macro is
+except that in Vi the user doesn’t know there is an error until the
macro is
actually run. All that means that in order for a definition to be
successful, the user must do some simple planning of the process in
advance, to avoid errors. For instance, if you want to map <kbd>gg</kbd> to
@@ -3414,7 +3414,7 @@
<p>binds the key f13 to the Emacs function that repeats the last minibuffer
command. Under Viper, however, you may still use this key for additional
purposes, if you bind, say, a double-hitting action for that key to some
-other function. Emacs doesn't allow the user to do that, but Viper does
+other function. Emacs doesn’t allow the user to do that, but Viper does
this through its keyboard macro facility. To do this, type <kbd>:map </kbd>
first. When you are asked to enter a macro name, hit f13 twice, followed by
<RET> or <SPC>.
@@ -3424,7 +3424,7 @@
macro is executed. Suppose now we wanted to bind the key sequence
<kbd>f13 f13</kbd> to the command <code>eval-last-sexp</code>. To accomplish
this, we
can type <kbd>M-x eval-last-sexp</kbd> followed by <kbd>C-x )</kbd>.
-If you answer positively to Viper's offer to save this macro in
‘<tt>~/.viper</tt>’
+If you answer positively to Viper’s offer to save this macro in
‘<tt>~/.viper</tt>’
for future uses, the following will be inserted in that file:
</p>
<table><tr><td> </td><td><pre class="example">(viper-record-kbd-macro
[f16 f16] 'vi-state
@@ -3435,7 +3435,7 @@
<p>To illustrate the above point, Viper provides two canned macros, which, by
default, are bound to <kbd>[f12 \1]</kbd> and <kbd>[f12 \2]</kbd> (invoked by
typing
<kbd>f12</kbd> then <kbd>1</kbd> and <kbd>2</kbd>, respectively). These
macros are useful
-shortcuts to Viper's command ring history. The first macro will execute the
+shortcuts to Viper’s command ring history. The first macro will execute
the
second-last destructive command (the last one is executed by <kbd>.</kbd>, as
usual). The second macro executes the third-last command.
</p>
@@ -3457,7 +3457,7 @@
<p>Viper allows the user to define macro names that are prefixes of other
macros.
For instance, one can define <kbd>[[</kbd> and <kbd>[[[[</kbd> to be macros.
If you type the exact sequence of such keys and then pause, Viper will
-execute the right macro. However, if you don't pause and, say, type
+execute the right macro. However, if you don’t pause and, say, type
<kbd>[[[[text</kbd> then the conflict is resolved as follows. If only one of
the
key sequences, <kbd>[[</kbd> or <kbd>[[[[</kbd> has a definition applicable to
the
current buffer, then, in fact, there is no conflict and the right macro
@@ -3474,7 +3474,7 @@
f7 a]</code>). The same holds for unmapping. Hitting <TAB> while
typing a macro name in the <kbd>:unmap</kbd> or <kbd>:unmap!</kbd> command will
cause name completion. Completions are displayed as strings or
-vectors. However, as before, you don't actually type
‘<samp>"</samp>’,
+vectors. However, as before, you don’t actually type
‘<samp>"</samp>’,
‘<samp>[</samp>’, or ‘<samp>]</samp>’ that appear in
the completions. These are
meta-symbols that indicate whether the corresponding macro name is a
vector or a string.
@@ -3484,7 +3484,7 @@
More precisely, while defining or executing a macro, the special meaning
of key sequences (as Vi macros) is ignored.
This is because it is all too easy to create an infinite loop in this way.
-Since Viper macros are much more powerful than Vi's it is impossible to
+Since Viper macros are much more powerful than Vi’s it is impossible to
detect such loops. In practice, this is not really a limitation but,
rather, a feature.
</p>
@@ -3498,7 +3498,7 @@
<p>For the most part, Viper macros defined in ‘<tt>~/.viper</tt>’
can be shared
between Emacs, XEmacs, and X and TTY modes. However, macros defined via
function keys may need separate definitions when XEmacs and Emacs have
-different names for the same keyboard key. For instance, the `Page Up' key
+different names for the same keyboard key. For instance, the ‘Page
Up’ key
may be known in Emacs as <kbd>prior</kbd> and in XEmacs as <kbd>pgup</kbd>.
The problem with TTY may be that the function keys there generate sequences
of events instead of a single event (as under a window system).
@@ -3506,7 +3506,7 @@
(e.g., the sequences generated by the arrow keys are mapped to <kbd>up</kbd>,
<kbd>left</kbd>, etc.). However, not all function keys are mapped in this way.
Macros that are bound to key sequences that contain such unmapped function
-keys have to be redefined for TTY's (and possibly for every type of TTY you
+keys have to be redefined for TTY’s (and possibly for every type of TTY
you
may be using). To do this, start Emacs on an appropriate TTY device and
define the macro using <kbd>:map</kbd>, as usual.
</p>
@@ -3672,7 +3672,7 @@
<p>Note that ‘<samp>%</samp>’ is used in Ex commands <kbd>:e</kbd>
and <kbd>:r <shell-cmd></kbd>
to mean current file. If you want a ‘<samp>%</samp>’ in your
command, it must be
escaped as ‘<samp>\%</samp>’. Note that <kbd>:w</kbd> and the
regular <kbd>:r <file></kbd>
-command doesn't support the meta symbols ‘<samp>%</samp>’ and
‘<samp>#</samp>’, because
+command doesn’t support the meta symbols ‘<samp>%</samp>’
and ‘<samp>#</samp>’, because
file history is a better mechanism.
<a name="IDX246"></a>
Similarly, ‘<samp>#</samp>’ expands to the previous file. The
previous file is
@@ -3723,13 +3723,13 @@
optional, usually defaulting to 1. Brackets are elided for
‘<samp><count></samp>’ to eschew obfuscation.
</p>
-<p>Viper's idea of Vi's words is slightly different from Vi. First, Viper
+<p>Viper’s idea of Vi’s words is slightly different from Vi.
First, Viper
words understand Emacs symbol tables. Therefore, all symbols declared to be
alphanumeric in a symbol table can automatically be made part of the Viper
word. This is useful when, for instance, editing text containing European,
Cyrillic, Japanese, etc., texts.
</p>
-<p>Second, Viper lets you depart from Vi's idea of a word by changing the a
+<p>Second, Viper lets you depart from Vi’s idea of a word by changing
the a
syntax preference via the customization widget (the variable
<code>viper-syntax-preference</code>) or by executing
<code>viper-set-syntax-preference</code> interactively.
@@ -3738,7 +3738,7 @@
Viper considers only those symbols to be part of a word that are specified
as word-symbols by the current Emacs syntax table (which may be different
for different major modes) plus the underscore symbol <kbd>_</kbd>, minus the
-symbols that are not considered words in Vi (e.g., `,',;, etc.), but may be
+symbols that are not considered words in Vi (e.g., ‘,’,;, etc.),
but may be
considered as word-symbols by various Emacs major modes. Reformed-Vi works
very close to Vi, and it also recognizes words in other
alphabets. Therefore, this is the most appropriate mode for editing text
@@ -3776,8 +3776,8 @@
<p>The above discussion concerns only the movement commands. In regular
expressions, words remain the same as in Emacs. That is, the expressions
-<code>\w</code>, <code>\></code>, <code>\<</code>, etc., use Emacs' idea
of what is a word,
-and they don't look into the value of variable
+<code>\w</code>, <code>\></code>, <code>\<</code>, etc., use
Emacs’ idea of what is a word,
+and they don’t look into the value of variable
<code>viper-syntax-preference</code>. This is because Viper avoids changing
syntax tables in order to not thwart the various major modes that set these
tables.
@@ -3788,7 +3788,7 @@
C, -, h!!!</em> The <kbd>^</kbd> is itself, never used to indicate a
Control character.
</p>
-<p>Finally, we note that Viper's Ex-style commands can be made to work on the
+<p>Finally, we note that Viper’s Ex-style commands can be made to work
on the
current Emacs region. This is done by typing a digit argument before
<kbd>:</kbd>. For instance, typing <kbd>1:</kbd> will propmt you with
something like
<em>:123,135</em>, assuming that the current region starts at line 123 and
@@ -4022,7 +4022,7 @@
This option can also be toggled interactively if you quickly hit
<kbd>%%%</kbd>.
</p>
<p>This latter feature is implemented as a vi-style keyboard macro. If you
-don't want this macro, put
+don’t want this macro, put
</p>
<table><tr><td> </td><td><pre
class="example">(viper-set-parsing-style-toggling-macro 'undefine)
</pre></td></tr></table>
@@ -4111,7 +4111,7 @@
<p>Emacs mark is referred to in the region specifiers <kbd>r</kbd> and
<kbd>R</kbd>.
See section <a href="#SEC4">Emacs Preliminaries</a>, and See section <a
href="#SEC15">Basics</a>, for explanation. Also
-see <a href="emacs.html#Mark">(emacs)Mark</a> section `Mark' in <cite>The GNU
Emacs manual</cite>, for an explanation of
+see <a href="emacs.html#Mark">(emacs)Mark</a> section ‘Mark’ in
<cite>The GNU Emacs manual</cite>, for an explanation of
the Emacs mark ring.
</p>
<a name="IDX323"></a>
@@ -4127,7 +4127,7 @@
<dd><p>Set the Emacs mark (see section <a href="#SEC4">Emacs
Preliminaries</a>) back to where it was last
set with the <kbd>m.</kbd> command. This is useful when you set the mark with
<kbd>m.</kbd>, but then some other command (such as <kbd>L</kbd> or
<kbd>G</kbd>) changes
-it in a way that you didn't like.
+it in a way that you didn’t like.
</p></dd>
<dt> <kbd>m <</kbd></dt>
<dd><p>Set the Emacs mark at beginning of buffer.
@@ -4255,13 +4255,13 @@
</p></dd>
<dt> <kbd>C-c M-p and C-c M-n</kbd></dt>
<dd><p>In Vi state,
-these commands help peruse the history of Vi's destructive commands.
+these commands help peruse the history of Vi’s destructive commands.
Successive typing of <kbd>C-c M-p</kbd> causes Viper to search the history in
the direction
of older commands, while hitting <kbd>C-c M-n</kbd> does so in reverse
order. Each command in the history is displayed in the Minibuffer. The
displayed command can
-then be executed by typing `<kbd>.</kbd>'.
+then be executed by typing ‘<kbd>.</kbd>’.
</p>
<p>Since typing the above sequences of keys may be tedious, the
functions doing the perusing can be bound to unused keyboard keys in the
@@ -4467,7 +4467,7 @@
</p>
<p>In Emacs, ‘<samp>\&</samp>’ stands for the last matched
expression, so
<kbd>s/[ab]+/\&\&/</kbd> will double the string matched by
<kbd>[ab]</kbd>.
-Viper doesn't treat ‘<samp>&</samp>’ specially, unlike Vi: use
‘<samp>\&</samp>’ instead.
+Viper doesn’t treat ‘<samp>&</samp>’ specially, unlike
Vi: use ‘<samp>\&</samp>’ instead.
</p>
<p>Viper does not parse search patterns and does not expand special symbols
found there (e.g., ‘<samp>~</samp>’ is not expanded to the result
of the previous
@@ -4602,7 +4602,7 @@
and execute the Ex <cmd> on each occurrence.
</p></dd>
<dt> <kbd>:[x,y]v/<string>/<cmd></kbd></dt>
-<dd><p>Execute <cmd> on the lines that don't match.
+<dd><p>Execute <cmd> on the lines that don’t match.
</p></dd>
<dt> <kbd>#g<move></kbd></dt>
<dd><p>Execute the last keyboard macro for each line in the region.
@@ -4886,7 +4886,7 @@
<p>In all file handling commands, space should be typed before entering the
file
-name. If you need to type a modifier, such as <kbd>>></kbd> or
<kbd>!</kbd>, don't
+name. If you need to type a modifier, such as <kbd>>></kbd> or
<kbd>!</kbd>, don’t
put any space between the command and the modifier.
</p>
<p>Note that many Ex commands, e.g., <kbd>:w</kbd>, accept command arguments.
The
@@ -4910,7 +4910,7 @@
<dt> <kbd>:[x,y] w</kbd></dt>
<dd><p>Write the file. Viper makes sure that a final newline is always added
to
any file where this newline is missing. This is done by setting Emacs
-variable <code>require-final-newline</code> to <code>t</code>. If you don't
like this
+variable <code>require-final-newline</code> to <code>t</code>. If you
don’t like this
feature, use <code>setq-default</code> to set
<code>require-final-newline</code> to
<code>nil</code>. This must be done in ‘<tt>.viper</tt>’ file.
</p></dd>
@@ -5196,7 +5196,7 @@
</p>
<p>Symbols ‘<samp>%</samp>’ and ‘<samp>#</samp>’ are
also used in the Ex commands <kbd>:e</kbd> and
<kbd>:r <shell-cmd></kbd>. The commands <kbd>:w</kbd> and the regular
<kbd>:r
-<file></kbd> command don't support these meta symbols, because file
history is a
+<file></kbd> command don’t support these meta symbols, because
file history is a
better mechanism.
</p>
<a name="IDX494"></a>
@@ -5289,7 +5289,7 @@
</p></dd>
<dt> <kbd>autoindent-global</kbd></dt>
<dt> <kbd>ai-global</kbd></dt>
-<dd><p>Same as `autoindent', but affects all buffers.
+<dd><p>Same as ‘autoindent’, but affects all buffers.
</p></dd>
<dt> <kbd>noautoindent</kbd></dt>
<dt> <kbd>noai</kbd></dt>
@@ -5344,8 +5344,8 @@
<dd><a name="IDX513"></a>
<a name="IDX514"></a>
<p>showmatch – Whenever you append a <kbd>)</kbd>, Vi shows
-its match if it's on the same page; also with
-<kbd>{</kbd> and <kbd>}</kbd>. If there's no match, Vi will beep.
+its match if it’s on the same page; also with
+<kbd>{</kbd> and <kbd>}</kbd>. If there’s no match, Vi will beep.
</p></dd>
<dt> <kbd>noshowmatch</kbd></dt>
<dt> <kbd>nosm</kbd></dt>
@@ -5362,7 +5362,7 @@
</p></dd>
<dt> <kbd>tabstop-global</kbd></dt>
<dt> <kbd>ts-g</kbd></dt>
-<dd><p>Same as `tabstop', but affects all buffers.
+<dd><p>Same as ‘tabstop’, but affects all buffers.
</p></dd>
<dt> <kbd>wrapmargin=<count></kbd></dt>
<dt> <kbd>wm=<count></kbd></dt>
@@ -5473,8 +5473,8 @@
<dd><p>Emacs find-file, useful in Insert state
</p></dd>
<dt> <kbd>C-y</kbd></dt>
-<dd><p>Put back the last killed text. Similar to Vi's <kbd>p</kbd>, but also
works in
-Insert and Replace state. This command doesn't work in Vi command state,
+<dd><p>Put back the last killed text. Similar to Vi’s <kbd>p</kbd>, but
also works in
+Insert and Replace state. This command doesn’t work in Vi command state,
since this binding is taken for something else.
</p></dd>
<dt> <kbd>M-y</kbd></dt>
@@ -5569,7 +5569,7 @@
<p>Viper, formerly known as VIP-19, was written by Michael Kifer. Viper is
based on the original VIP package by Masahiko Sato and on its enhancement,
VIP 4.4, by Aamod Sane. This manual is an adaptation of the manual for VIP
-4.4, which, in turn, was based on Sato's manual for VIP 3.5.
+4.4, which, in turn, was based on Sato’s manual for VIP 3.5.
</p>
<p>Many contributors on the Net pointed out bugs and suggested a number of
useful features. Scott Bronson and Samuel Padgett contributed patches that
Index: Tests/viper_res/viper_0.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/viper_res/viper_0.html,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -b -r1.16 -r1.17
--- Tests/viper_res/viper_0.html 5 Feb 2007 15:30:26 -0000 1.16
+++ Tests/viper_res/viper_0.html 3 Oct 2007 09:34:53 -0000 1.17
@@ -70,7 +70,7 @@
license is included in the section entitled “GNU Free Documentation
License” in the Emacs manual.
</p>
-<p>(a) The FSF's Back-Cover Text is: “You have freedom to copy and modify
+<p>(a) The FSF’s Back-Cover Text is: “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.”
</p>
Index: Tests/viper_res/viper_2.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/viper_res/viper_2.html,v
retrieving revision 1.29
retrieving revision 1.30
diff -u -b -r1.29 -r1.30
--- Tests/viper_res/viper_2.html 5 Feb 2007 15:30:26 -0000 1.29
+++ Tests/viper_res/viper_2.html 3 Oct 2007 09:34:53 -0000 1.30
@@ -119,7 +119,7 @@
<p>Emacs can edit several files at once. A file in Emacs is placed in a
<em>buffer</em> that usually has the same name as the file. Buffers are also
used
for other purposes, such as shell interfaces, directory editing, etc.
-See <a href="../emacs/Dired.html#Dired">(emacs)Dired</a> section `Directory
Editor' in <cite>The Gnu Emacs Manual</cite>, for an example.
+See <a href="../emacs/Dired.html#Dired">(emacs)Dired</a> section
‘Directory Editor’ in <cite>The Gnu Emacs Manual</cite>, for an
example.
</p>
<p>A buffer has a distinguished position called the <em>point</em>.
A <em>point</em> is always between 2 characters, and is <em>looking at</em>
@@ -131,12 +131,12 @@
<p>The default settings of Viper try to mimic the behavior of Vi, preventing
the cursor from going beyond the last character on the line. By using
Emacs commands directly (such as those bound to arrow keys), it is possible
-to get the cursor beyond the end-of-line. However, this won't (or
-shouldn't) happen if you restrict yourself to standard Vi keys, unless you
+to get the cursor beyond the end-of-line. However, this won’t (or
+shouldn’t) happen if you restrict yourself to standard Vi keys, unless
you
modify the default editing style. See section <a
href="viper_4.html#SEC25">Customization</a>.
</p>
<p>In addition to the <em>point</em>, there is another distinguished buffer
-position called the <em>mark</em>. See <a
href="../emacs/Mark.html#Mark">(emacs)Mark</a> section `Mark' in <cite>The GNU
Emacs manual</cite>, for more info on the mark. The text between the
<em>point</em> and
+position called the <em>mark</em>. See <a
href="../emacs/Mark.html#Mark">(emacs)Mark</a> section ‘Mark’ in
<cite>The GNU Emacs manual</cite>, for more info on the mark. The text between
the <em>point</em> and
the <em>mark</em> is called the <em>region</em> of the buffer. For the Viper
user, this simply means that in addition to the Vi textmarkers a–z, there
is another marker called <em>mark</em>. This is similar to the unnamed Vi
@@ -195,14 +195,14 @@
keymap then that function will be executed when you type the key.
If no function is bound to a key in the
local map, however, the function bound to the key in the global map
-will be executed. See <a href="../emacs/Major-Modes.html#Major-Modes">Major
Modes: (emacs)Major Modes</a> section `Major Modes' in <cite>The GNU Emacs
Manual</cite>, for more information.
+will be executed. See <a href="../emacs/Major-Modes.html#Major-Modes">Major
Modes: (emacs)Major Modes</a> section ‘Major Modes’ in <cite>The
GNU Emacs Manual</cite>, for more information.
</p>
<p>A buffer can also have a <em>minor mode</em>. Minor modes are options that
you can use or not. A buffer in <code>text-mode</code> can have
<code>auto-fill-mode</code> as minor mode, which can be turned off or on at
any time. In Emacs, a minor mode may have it own keymap,
which overrides the local keymap when the minor mode is turned on. For
-more information, see <a href="../emacs/Minor-Modes.html#Minor-Modes">Minor
Modes: (emacs)Minor Modes</a> section `Minor Modes' in <cite>The GNU Emacs
Manual</cite>
+more information, see <a href="../emacs/Minor-Modes.html#Minor-Modes">Minor
Modes: (emacs)Minor Modes</a> section ‘Minor Modes’ in <cite>The
GNU Emacs Manual</cite>
</p>
<a name="IDX13"></a>
<a name="IDX14"></a>
@@ -270,7 +270,7 @@
<p>The latest versions of Emacs have an interactive customization facility,
which allows you to (mostly) bypass the use of the
‘<tt>.emacs</tt>’ and
‘<tt>.viper</tt>’ files. You can reach this customization
-facility from within Viper's VI state by executing the Ex command
+facility from within Viper’s VI state by executing the Ex command
<kbd>:customize</kbd>.
</p>
<p>Once invoked, Viper will arrange to bring up Emacs buffers in Vi state
@@ -390,7 +390,7 @@
</p>
<p>If you switch to Vi in Dired or similar modes—no harm is done. It is
just
that the special key bindings provided by those modes will be temporarily
-overshadowed by Viper's bindings. Switching back to Viper's Emacs state
+overshadowed by Viper’s bindings. Switching back to Viper’s Emacs
state
will revive the environment provided by the current major mode.
</p>
<p>States in Viper are orthogonal to Emacs major modes, such as C mode or Dired
@@ -464,7 +464,7 @@
</p>
<p>There is also a key that lets you temporarily escape to Vi command state
from Emacs or Insert states: typing <kbd>C-c \</kbd> will let you execute a
-single Vi command while staying in Viper's Emacs or Insert state.
+single Vi command while staying in Viper’s Emacs or Insert state.
In Insert state, the same can also be achieved by typing <kbd>C-z</kbd>.
</p>
@@ -522,7 +522,7 @@
‘<samp>Recursive Edits</samp>’ in Emacs for which there is no
comparable Vi
functionality and no key-binding. Recursive edits are indicated by
‘<samp>[]</samp>’ brackets framing the modes on the mode line.
-See <a href="../emacs/Recursive-Edit.html#Recursive-Edit">Recursive Edit:
(emacs)Recursive Edit</a> section `Recursive Edit' in <cite>The GNU Emacs
Manual</cite>.
+See <a href="../emacs/Recursive-Edit.html#Recursive-Edit">Recursive Edit:
(emacs)Recursive Edit</a> section ‘Recursive Edit’ in <cite>The GNU
Emacs Manual</cite>.
At user level 1, <kbd>C-g</kbd> is bound to <code>viper-info-on-file</code>
function instead.
@@ -534,7 +534,7 @@
<p>Viper uses <ESC> as a switch between Insert and Vi states. Emacs uses
<ESC> for Meta. The Meta key is very important in Emacs since many
functions are accessible only via that key as <kbd>M-x function-name</kbd>.
-Therefore, we need to simulate it somehow. In Viper's Vi, Insert, and
+Therefore, we need to simulate it somehow. In Viper’s Vi, Insert, and
Replace states, the meta key is set to be <kbd>C-\</kbd>. Thus, to get
<kbd>M-x</kbd>, you should type <kbd>C-\ x</kbd> (if the keyboard has no Meta
key,
which is rare these days).
@@ -572,7 +572,7 @@
<dd><p>Viper uses Emacs Regular Expressions for searches. These are a
superset of
Vi regular
expressions, excepting the change-of-case escapes
‘<samp>\u</samp>’, ‘<samp>\L</samp>’,
-…, etc. See <a
href="../emacs/Regular-Expressions.html#Regular-Expressions">(emacs)Regular
Expressions</a> section `Regular Expressions' in <cite>The GNU Emacs
Manual</cite>, for details.
+…, etc. See <a
href="../emacs/Regular-Expressions.html#Regular-Expressions">(emacs)Regular
Expressions</a> section ‘Regular Expressions’ in <cite>The GNU
Emacs Manual</cite>, for details.
Files specified to <kbd>:e</kbd> use <code>csh</code> regular expressions
(globbing, wildcards, what have you).
However, the function <code>viper-toggle-search-style</code>, bound to
<kbd>C-c /</kbd>,
@@ -596,7 +596,7 @@
need for deleting file names that Emacs provides in its prompts. (This is
usually convenient, but occasionally the prompt may suggest a wrong file
name for you.) If you see a prompt <kbd>/usr/foo/</kbd> and you wish to edit
the
-file <kbd>~/.viper</kbd>, you don't have to erase the prompt. Instead, simply
+file <kbd>~/.viper</kbd>, you don’t have to erase the prompt. Instead,
simply
continue typing what you need. Emacs will interpret
<kbd>/usr/foo/~/.viper</kbd>
correctly. Similarly, if the prompt is <kbd>~/foo/</kbd> and you need to get
to
<kbd>/bar/file</kbd>, keep typing. Emacs interprets <kbd>~/foo//bar/</kbd> as
@@ -641,11 +641,11 @@
</p></dd>
</dl>
-<p>As Vi, Viper's destructive commands can be re-executed by typing
`<kbd>.</kbd>'.
+<p>As Vi, Viper’s destructive commands can be re-executed by typing
‘<kbd>.</kbd>’.
However, in addition, Viper keeps track of the history of such commands. This
history can be perused by typing <kbd>C-c M-p</kbd> and <kbd>C-c M-n</kbd>.
Having found the appropriate command, it can be then executed by typing
-`<kbd>.</kbd>'.
+‘<kbd>.</kbd>’.
See section <a href="viper_3.html#SEC14">Improvements over Vi</a>, for more
information.
</p>
<hr size="6">
@@ -680,14 +680,14 @@
</p>
<p>Once this is done, it is possible to do quite a bit of editing in
Insert state. For instance, Emacs has a <em>yank</em> command, <kbd>C-y</kbd>,
-which is similar to Vi's <kbd>p</kbd>. However, unlike <kbd>p</kbd>,
<kbd>C-y</kbd> can be
+which is similar to Vi’s <kbd>p</kbd>. However, unlike <kbd>p</kbd>,
<kbd>C-y</kbd> can be
used in Insert state of Viper. Emacs also has a kill ring where it keeps
pieces of text you deleted while editing buffers. The command <kbd>M-y</kbd>
is
-used to delete the text previously put back by Emacs' <kbd>C-y</kbd> or by Vi's
+used to delete the text previously put back by Emacs’ <kbd>C-y</kbd> or
by Vi’s
<kbd>p</kbd> command and reinsert text that was placed on the kill-ring
earlier.
</p>
<p>This works both in Vi and Insert states.
-In Vi state, <kbd>M-y</kbd> is a much better alternative to the usual Vi's way
+In Vi state, <kbd>M-y</kbd> is a much better alternative to the usual
Vi’s way
of recovering the 10 previously deleted chunks of text. In Insert state,
you can
use this as follows. Suppose you deleted a piece of text and now you need
@@ -827,7 +827,7 @@
</dl>
<p>Most of the Emacs keys are functional in the Minibuffer. While in the
-Minibuffer, Viper tries to make editing resemble Vi's behavior when the
+Minibuffer, Viper tries to make editing resemble Vi’s behavior when the
latter is waiting for the user to type an Ex command. In particular, you
can use the regular Vi commands to edit the Minibuffer. You can switch
between the Vi state and Insert state at will, and even use the replace mode.
@@ -935,7 +935,7 @@
<p>Currently undisplayed files can be listed using the <kbd>:ar</kbd> command.
The
command <kbd>:n</kbd> can be given counts from the <kbd>:ar</kbd> list to
switch to
-other files. For example, use `:n3' to move to the third file in that list.
+other files. For example, use ‘:n3’ to move to the third file in
that list.
</p>
<hr size="6">
<a name="Unimplemented-Features"></a>
Index: Tests/viper_res/viper_3.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/viper_res/viper_3.html,v
retrieving revision 1.28
retrieving revision 1.29
diff -u -b -r1.28 -r1.29
--- Tests/viper_res/viper_3.html 5 Feb 2007 15:30:26 -0000 1.28
+++ Tests/viper_res/viper_3.html 3 Oct 2007 09:34:53 -0000 1.29
@@ -197,7 +197,7 @@
<h2 class="section"> 2.2 Undo and Backups </h2>
-<p>Viper provides multiple undo. The number of undo's and the size is limited
+<p>Viper provides multiple undo. The number of undo’s and the size is
limited
by the machine. The Viper command <kbd>u</kbd> does an undo. Undo can be
repeated by typing <kbd>.</kbd> (a period). Another <kbd>u</kbd> will undo
the undo,
and further
@@ -209,7 +209,7 @@
<p>Since the undo size is limited, Viper can create backup files and
auto-save files. It will normally do this automatically. It is possible
-to have numbered backups, etc. For details, see <a
href="../emacs/Backup.html#Backup">(emacs)Backup</a> section `Backup and
Auto-Save' in <cite>The GNU Emacs Manual</cite>
+to have numbered backups, etc. For details, see <a
href="../emacs/Backup.html#Backup">(emacs)Backup</a> section ‘Backup and
Auto-Save’ in <cite>The GNU Emacs Manual</cite>
</p>
<a name="IDX47"></a>
<a name="IDX48"></a>
@@ -332,7 +332,7 @@
<kbd>*</kbd>, and it can be yanked into a register using <kbd>@!register</kbd>.
This is useful for Emacs style keyboard macros defined using <kbd>C-x(</kbd>
and <kbd>C-x)</kbd>. Emacs keyboard macros have more capabilities.
-See <a href="../emacs/Keyboard-Macros.html#Keyboard-Macros">(emacs)Keyboard
Macros</a> section `Keyboard Macros' in <cite>The GNU Emacs Manual</cite>, for
+See <a href="../emacs/Keyboard-Macros.html#Keyboard-Macros">(emacs)Keyboard
Macros</a> section ‘Keyboard Macros’ in <cite>The GNU Emacs
Manual</cite>, for
details.
</p>
<p>Keyboard Macros allow an interesting form of Query-Replace:
@@ -417,7 +417,7 @@
as you go along. Incremental Search is normally bound to <kbd>C-s</kbd> and
<kbd>C-r</kbd>. See section <a href="viper_4.html#SEC25">Customization</a>,
to find out how to change the bindings
of <kbd>C-r or C-s</kbd>.
-For details, see <a
href="../emacs/Incremental-Search.html#Incremental-Search">(emacs)Incremental
Search</a> section `Incremental Search' in <cite>The GNU Emacs Manual</cite>
+For details, see <a
href="../emacs/Incremental-Search.html#Incremental-Search">(emacs)Incremental
Search</a> section ‘Incremental Search’ in <cite>The GNU Emacs
Manual</cite>
</p>
<a name="IDX54"></a>
@@ -432,7 +432,7 @@
<p>Finally, on a window display, Viper highlights search patterns as it finds
them. This is done through what is known as <em>faces</em> in Emacs. The
variable that controls how search patterns are highlighted is
-<code>viper-search-face</code>. If you don't want any highlighting at all, put
+<code>viper-search-face</code>. If you don’t want any highlighting at
all, put
</p><table><tr><td> </td><td><pre class="example">(copy-face 'default
'viper-search-face)
</pre></td></tr></table>
<a name="IDX56"></a>
@@ -442,7 +442,7 @@
from the menubar. Viper customization group is located under the
<em>Emulations</em> customization group, which in turn is under the
<em>Editing</em> group (or simply by typing <kbd>:customize</kbd>). All Viper
-faces are grouped together under Viper's
+faces are grouped together under Viper’s
<em>Highlighting</em> group.
</p>
<p>Try it: it is really simple!
@@ -472,7 +472,7 @@
<p>It is possible in Emacs to define abbrevs based on the contents of the
buffer.
Sophisticated templates can be defined using the Emacs abbreviation
-facilities. See <a href="../emacs/Abbrevs.html#Abbrevs">(emacs)Abbrevs</a>
section `Abbreviations' in <cite>The GNU Emacs Manual</cite>, for
+facilities. See <a href="../emacs/Abbrevs.html#Abbrevs">(emacs)Abbrevs</a>
section ‘Abbreviations’ in <cite>The GNU Emacs Manual</cite>, for
details.
</p>
<a name="IDX57"></a>
@@ -486,7 +486,7 @@
keystroke, which appears earlier in the text. Emacs binds this to
<kbd><ESC> /</kbd>, so you will have to find a key and bind the function
<code>dabbrev-expand</code> to that key.
-Facilities like this make Vi's <kbd>:ab</kbd> command obsolete.
+Facilities like this make Vi’s <kbd>:ab</kbd> command obsolete.
</p>
<hr size="6">
<a name="Movement-and-Markers"></a>
@@ -534,7 +534,7 @@
Vi. However, if the value is <code>reformed-vi</code> (the default) then the
alphanumeric symbols will be those specified by the current Emacs syntax
table (which may be different for different major modes) plus the
-underscore symbol <kbd>_</kbd>, minus some non-word symbols, like '.;,|, etc.
+underscore symbol <kbd>_</kbd>, minus some non-word symbols, like ’.;,|,
etc.
Both <code>strict-vi</code> and <code>reformed-vi</code> work close to Vi in
traditional cases, but <code>reformed-vi</code> does a better job when editing
text in non-Latin alphabets.
@@ -562,11 +562,11 @@
<a name="IDX60"></a>
-<p>The above discussion of the meaning of Viper's words concerns only Viper's
+<p>The above discussion of the meaning of Viper’s words concerns only
Viper’s
movement commands. In regular expressions, words remain the same as in
Emacs. That is, the expressions <code>\w</code>, <code>\></code>,
<code>\<</code>, etc., use
-Emacs' idea of what is a word, and they don't look into the value of
-variable <code>viper-syntax-preference</code>. This is because Viper doesn't
change
+Emacs’ idea of what is a word, and they don’t look into the value
of
+variable <code>viper-syntax-preference</code>. This is because Viper
doesn’t change
syntax tables in fear of upsetting the various major modes that set these
tables.
</p>
@@ -691,7 +691,7 @@
<dd><p>Set mark at beginning and end of buffer, respectively.
</p></dd>
<dt> <kbd>m,</kbd></dt>
-<dd><p>Jump to mark and pop mark off the ring. See <a
href="../emacs/Mark.html#Mark">(emacs)Mark</a> section `Mark' in <cite>The GNU
Emacs Manual</cite>, for more info.
+<dd><p>Jump to mark and pop mark off the ring. See <a
href="../emacs/Mark.html#Mark">(emacs)Mark</a> section ‘Mark’ in
<cite>The GNU Emacs Manual</cite>, for more info.
</p></dd>
<dt> <kbd>] register</kbd></dt>
<dd><a name="IDX79"></a>
@@ -773,7 +773,7 @@
By repeatedly typing <kbd>C-c M-p</kbd> or <kbd>C-c M-n</kbd> you will cycle
Viper
through the recent history of Vi commands, displaying the commands one by
one. Once
-an appropriate command is found, it can be executed by typing `<kbd>.</kbd>'.
+an appropriate command is found, it can be executed by typing
‘<kbd>.</kbd>’.
</p>
<p>Since typing <kbd>C-c M-p</kbd> is tedious, it is more convenient to bind an
appropriate function to a function key on the keyboard and use that key.
Index: Tests/viper_res/viper_4.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/viper_res/viper_4.html,v
retrieving revision 1.28
retrieving revision 1.29
diff -u -b -r1.28 -r1.29
--- Tests/viper_res/viper_4.html 5 Feb 2007 15:30:26 -0000 1.28
+++ Tests/viper_res/viper_4.html 3 Oct 2007 09:34:53 -0000 1.29
@@ -138,7 +138,7 @@
<p>Viper supports both the abbreviated Vi variable names and their full
names. Variable completion is done on full names only. <TAB> and
<SPC> complete
-variable names. Typing `=' will complete the name and then will prompt for
+variable names. Typing ‘=’ will complete the name and then will
prompt for
a value, if applicable. For instance, <kbd>:se au <SPC></kbd> will
complete the
command to <kbd>:set autoindent</kbd>; <kbd>:se ta <SPC></kbd> will
complete the command
and prompt further like this: <kbd>:set tabstop = </kbd>.
@@ -211,12 +211,12 @@
including the new buffers.
</p>
<p>Note that typing <TAB> normally
-doesn't insert the tab, since this key is usually bound to
+doesn’t insert the tab, since this key is usually bound to
a text-formatting function, <code>indent-for-tab-command</code> (which
facilitates
programming and document writing). Instead, the tab is inserted via the
command <code>viper-insert-tab</code>, which is bound to <kbd>S-tab</kbd>
(shift + tab).
</p>
-<p>On some non-windowing terminals, Shift doesn't modify the <TAB> key,
so
+<p>On some non-windowing terminals, Shift doesn’t modify the <TAB>
key, so
<kbd>S-tab</kbd> behaves as if it were <TAB>. In such a case, you will
have
to bind <code>viper-insert-tab</code> to some other convenient key.
</p>
@@ -232,7 +232,7 @@
<dt> <code>viper-search-scroll-threshold 2</code></dt>
<dd><p>If search lands within this many lines of the window top or bottom, the
window will be scrolled up or down by about 1/7-th of its size, to reveal
-the context. If the value is negative—don't scroll.
+the context. If the value is negative—don’t scroll.
</p></dd>
<dt> <code>viper-tags-file-name "TAGS"</code></dt>
<dd><p>The name of the file used as the tag table.
@@ -263,7 +263,7 @@
is extremely slow, you might want to increase this slightly. You will know
if your terminal is slow if the <ESC> key sequences emitted by the
arrow keys are interpreted as separately typed characters (and thus the
-arrow keys won't work). Making this value too large will slow you down, so
+arrow keys won’t work). Making this value too large will slow you down,
so
exercise restraint.
</p></dd>
<dt> <code>viper-fast-keyseq-timeout 200</code></dt>
@@ -325,12 +325,12 @@
<dd><p>The value of this variable is the function symbol used to expand
wildcard
symbols. This is platform-dependent. The default tries to set this variable
to work with most shells, MS Windows, OS/2, etc. However, if it
-doesn't work the way you expect, you should write your own.
+doesn’t work the way you expect, you should write your own.
Use <code>viper-glob-unix-files</code> and
<code>viper-glob-mswindows-files</code> in
‘<tt>viper-util.el</tt>’ as examples.
</p>
<p>This feature is used to expand wildcards in the Ex command <kbd>:e</kbd>.
-Note that Viper doesn't support wildcards in the <kbd>:r</kbd> and
<kbd>:w</kbd>
+Note that Viper doesn’t support wildcards in the <kbd>:r</kbd> and
<kbd>:w</kbd>
commands, because file completion is a better mechanism.
<a name="IDX133"></a>
</p>
@@ -363,7 +363,7 @@
</p></dd>
<dt> <code>viper-keep-point-on-repeat t</code></dt>
<dd><p>If not <code>nil</code>, point is not moved when the user repeats the
previous
-command by typing `.' This is very useful for doing repeated changes with
+command by typing ‘.’ This is very useful for doing repeated
changes with
the <kbd>.</kbd> key.
</p></dd>
<dt> <code>viper-repeat-from-history-key 'f12</code></dt>
@@ -397,7 +397,7 @@
monochrome displays and also lays a stipple over them. On color displays,
replacement regions are highlighted with color.
</p>
-<p>If you know something about Emacs faces and don't like how Viper highlights
+<p>If you know something about Emacs faces and don’t like how Viper
highlights
replacement regions, you can change <code>viper-replace-overlay-face</code> by
specifying a new face. (Emacs faces are described in the Emacs Lisp
reference.) On a color display, the following customization method is
@@ -444,7 +444,7 @@
</p></dd>
<dt> <code>viper-toggle-key "\C-z"</code></dt>
<dd><p>Specifies the key used to switch from Emacs to Vi and back.
-Must be set in ‘<tt>.viper</tt>’. This variable can't be
+Must be set in ‘<tt>.viper</tt>’. This variable can’t be
changed interactively after Viper is loaded.
</p>
<p>In Insert state, this key acts as a temporary escape to Vi state, i.e., it
@@ -560,7 +560,7 @@
<p>Viper lets you define hot keys, i.e., you can associate keyboard keys
such as F1, Help, PgDn, etc., with Emacs Lisp functions (that may already
exist or that you will write). Each key has a "preferred form" in
-Emacs. For instance, the Up key's preferred form is [up], the Help key's
+Emacs. For instance, the Up key’s preferred form is [up], the Help
key’s
preferred form is [help], and the Undo key has the preferred form [f14].
You can find out the preferred form of a key by typing <kbd>M-x
describe-key-briefly</kbd> and then typing the key you want to know about.
@@ -609,7 +609,7 @@
<code>define-key</code> command, to modify
<code>viper-vi-global-user-map</code>,
<code>viper-insert-global-user-map</code>, and
<code>viper-emacs-global-user-map</code>, as
explained below. Each of these key maps affects the corresponding Viper state.
-The keymap <code>viper-insert-global-user-map</code> also affects Viper's
Replace
+The keymap <code>viper-insert-global-user-map</code> also affects
Viper’s Replace
state.
</p>
<p>If you want to
@@ -700,7 +700,7 @@
avoid this, one should add <code>viper-change-state-to-emacs</code> to an
appropriate hook of that major mode. (Check the function
<code>viper-set-hooks</code> in ‘<tt>viper.el</tt>’ for examples.)
However, if you
-did not set <code>viper-always</code> to <code>nil</code>, chances are that
you won't
+did not set <code>viper-always</code> to <code>nil</code>, chances are that
you won’t
need to perform the above procedure, because Viper will take care of most
useful defaults.
</p>
@@ -749,12 +749,12 @@
<p>On rare occasions, local keys may be added by mistake. Usually this is done
indirectly, by invoking a major mode that adds local keys (e.g.,
<code>shell-mode</code> redefines <RET>). In such a case, exiting the
wrong
-major mode won't rid you from unwanted local keys, since these keys are
+major mode won’t rid you from unwanted local keys, since these keys are
local to Viper state and the current buffer, not to the major mode.
In such situations, the remedy is to type <kbd>M-x viper-zap-local-keys</kbd>.
</p>
<p>So much about Viper-specific bindings.
-See <a
href="../emacs/Customization.html#Customization">(emacs)Customization</a>
section `Customization' in <cite>The GNU Emacs Manual</cite>, and the Emacs
quick reference card for the general info on key
+See <a
href="../emacs/Customization.html#Customization">(emacs)Customization</a>
section ‘Customization’ in <cite>The GNU Emacs Manual</cite>, and
the Emacs quick reference card for the general info on key
bindings in Emacs.
</p>
<a name="IDX180"></a>
@@ -817,12 +817,12 @@
<kbd>)</kbd> or a <kbd>"</kbd> is missing somewhere above the current
line, <TAB> is likely to mis-indent the line.
</p>
-<p>For this reason, Viper doesn't change the standard Emacs binding of
+<p>For this reason, Viper doesn’t change the standard Emacs binding of
<TAB>, thereby sacrificing Vi compatibility
(except for users at level 1). Instead, in Viper, the key
-<kbd>S-tab</kbd> (shift+ tab) is chosen to emulate Vi's <TAB>.
+<kbd>S-tab</kbd> (shift+ tab) is chosen to emulate Vi’s <TAB>.
</p>
-<p>We should note that on some non-windowing terminals, Shift doesn't modify
+<p>We should note that on some non-windowing terminals, Shift doesn’t
modify
the <TAB> key, so <kbd>S-tab</kbd> behaves as if it were <TAB>.
In such
a case, you will have to bind <code>viper-insert-tab</code> to some other
convenient key.
@@ -833,7 +833,7 @@
packages. Fortunately, these modes operate on read-only buffers and are
designed not for editing files, but for special-purpose browsing, reading
news, mail, etc., and Vi commands are meaningless in these situations. For
-this reason, Viper doesn't force Vi state on such major modes—it
+this reason, Viper doesn’t force Vi state on such major modes—it
brings them in Emacs state. You can switch to Vi state by typing
<kbd>C-z</kbd>
if, for instance, you want to do Vi-style search in a buffer (although,
usually, incremental search, which is bound to <kbd>C-s</kbd>, is sufficient in
@@ -847,7 +847,7 @@
Vi state (but Viper thinks otherwise), you should put these major modes
on the <code>viper-emacs-state-mode-list</code> list and delete them from
<code>viper-vi-state-mode-list</code>.
-Likewise, you can force Viper's Insert state on a major mode by putting it
+Likewise, you can force Viper’s Insert state on a major mode by putting
it
in <code>viper-insert-state-mode-list</code>.
<a name="IDX186"></a>
<a name="IDX187"></a>
@@ -882,7 +882,7 @@
<p>that binds the misbehaving
keys. If so, use the above line to harness <code>nasty-mode</code>. If your
suspicion is wrong, no harm is done if you harness a minor mode that
-doesn't need to be harnessed.
+doesn’t need to be harnessed.
</p>
<a name="IDX189"></a>
<a name="IDX190"></a>
@@ -916,7 +916,7 @@
<p>Viper extends Vi with a number of useful features. This includes various
search functions, histories of search strings, Ex commands, insertions, and
-Vi's destructive commands. In addition, Viper supports file name completion
+Vi’s destructive commands. In addition, Viper supports file name
completion
and history, completion of Ex commands and variables, and many other
features. Some of these features are explained in detail elsewhere in this
document. Other features are explained here.
@@ -948,10 +948,10 @@
restore the original state. Likewise, quickly hitting <kbd>/</kbd> three times
will switch you from vanilla-style search to search via regular expressions.
If you hit something other than <kbd>/</kbd> after the first <kbd>/</kbd> or
if the
-second <kbd>/</kbd> doesn't follow quickly enough, then Viper will issue the
+second <kbd>/</kbd> doesn’t follow quickly enough, then Viper will issue
the
usual prompt <kbd>/</kbd> and will wait for input, as usual in Vi.
-If you don't like this behavior, you can “unrecord” these macros
in your
-‘<tt>~/.viper</tt>’ file. For instance, if you don't like the
above feature, put
+If you don’t like this behavior, you can “unrecord” these
macros in your
+‘<tt>~/.viper</tt>’ file. For instance, if you don’t like
the above feature, put
this in ‘<tt>~/.viper</tt>’:
</p><table><tr><td> </td><td><pre
class="example">(viper-set-searchstyle-toggling-macros 'undefine)
</pre></td></tr></table>
@@ -959,23 +959,23 @@
</dd>
<dt> <code>Vi-isms in Emacs state</code></dt>
-<dd><p>Some people find it useful to use the Vi-style search key, `/', to
invoke
+<dd><p>Some people find it useful to use the Vi-style search key,
‘/’, to invoke
search in modes which Viper leaves in emacs-state. These modes are:
<code>dired-mode</code>, <code>mh-folder-mode</code>,
<code>gnus-group-mode</code>,
<code>gnus-summary-mode</code>, <code>Info-mode</code>, and
<code>Buffer-menu-mode</code>
-(more may be added in the future). So, in the above modes, Viper binds `/'
+(more may be added in the future). So, in the above modes, Viper binds
‘/’
so that it will behave Vi-style. Furthermore, in those major modes, Viper
-binds `:' to invoke ex-style commands, like in vi-state. And, as described
-above, `//' and `///' get bound to Vi-style macros that toggle
+binds ‘:’ to invoke ex-style commands, like in vi-state. And, as
described
+above, ‘//’ and ‘///’ get bound to Vi-style macros
that toggle
case-insensitivity and regexp-search.
</p>
-<p>If you don't like these features—which I don't really
understand—you
-can unbind `/' and `:' in <code>viper-dired-modifier-map</code> (for Dired) or
in
+<p>If you don’t like these features—which I don’t really
understand—you
+can unbind ‘/’ and ‘:’ in
<code>viper-dired-modifier-map</code> (for Dired) or in
<code>viper-slash-and-colon-map</code>, for other modes.
<a name="IDX200"></a>
<a name="IDX201"></a>
</p>
-<p>To unbind the macros `//' and `///' for a major mode where you feel they
+<p>To unbind the macros ‘//’ and ‘///’ for a major
mode where you feel they
are undesirable, execute <code>viper-set-emacs-state-searchstyle-macros</code>
with a
non-nil argument. This can be done either interactively, by supplying a
prefix argument, or by placing
@@ -993,7 +993,7 @@
<a name="IDX205"></a>
<a name="IDX206"></a>
<p>Regular Expressions for <kbd>[[</kbd> and <kbd>]]</kbd>. Note that Emacs
defines
-Regexps for paragraphs and sentences. See <a
href="../emacs/Paragraphs.html#Paragraphs">(emacs)Paragraphs</a> section
`Paragraphs and Sentences' in <cite>The GNU Emacs Manual</cite>, for details.
+Regexps for paragraphs and sentences. See <a
href="../emacs/Paragraphs.html#Paragraphs">(emacs)Paragraphs</a> section
‘Paragraphs and Sentences’ in <cite>The GNU Emacs Manual</cite>,
for details.
</p></dd>
<dt> <code>M-x viper-set-expert-level</code></dt>
<dd><a name="IDX207"></a>
@@ -1004,16 +1004,16 @@
<p>Viper supports Emacs-style file completion when it prompts the user for a
file name. However, in many cases, the same directory may contain files
with identical prefix but different suffixes, e.g., prog.c, prog.o,
-paper.tex, paper.dvi. In such cases, completion will stop at the `.'.
+paper.tex, paper.dvi. In such cases, completion will stop at the
‘.’.
If the above variable is a list of strings representing suffixes, Viper will
try these suffixes
in the order listed and will check if the corresponding file exists.
</p>
-<p>For instance, if completion stopped at `paper.' and the user typed
+<p>For instance, if completion stopped at ‘paper.’ and the user
typed
<RET>,
-then Viper will check if the files `paper.', `paper.tex', `paper.c', etc.,
exist.
+then Viper will check if the files ‘paper.’,
‘paper.tex’, ‘paper.c’, etc., exist.
It will take the first such file. If no file exists, Viper will give a chance
-to complete the file name by typing the appropriate suffix. If `paper.' was
+to complete the file name by typing the appropriate suffix. If
‘paper.’ was
the intended file name, hitting return will accept it.
</p>
<p>To turn this feature off, set the above variable to <code>nil</code>.
@@ -1059,9 +1059,9 @@
<p>Viper keeps track of the recent history of destructive
commands, such as <kbd>dw</kbd>, <kbd>i</kbd>, etc.
In Vi state,
-the most recent command can be re-executed by hitting `<kbd>.</kbd>', as in Vi.
+the most recent command can be re-executed by hitting
‘<kbd>.</kbd>’, as in Vi.
However, repeated typing <kbd>C-c M-p</kbd> will cause Viper to show the
-previous destructive commands in the minibuffer. Subsequent hitting
`<kbd>.</kbd>'
+previous destructive commands in the minibuffer. Subsequent hitting
‘<kbd>.</kbd>’
will execute the command that was displayed last.
The key <kbd>C-c M-n</kbd> will cycle through the command history in the
opposite direction.
@@ -1087,12 +1087,12 @@
<dt> <code>viper-minibuffer-emacs-face
'viper-minibuffer-emacs-face</code></dt>
<dd><p>These faces control the appearance of the minibuffer text in the
corresponding Viper states. You can change the appearance of these faces
-through Emacs' customization widget, which is accessible through the
+through Emacs’ customization widget, which is accessible through the
menubar.
</p>
<p>Viper is located in this widget under the <em>Emulations</em> customization
subgroup of the <em>Editing</em> group. All Viper faces are grouped together
-in Viper's <em>Highlighting</em> customization subgroup.
+in Viper’s <em>Highlighting</em> customization subgroup.
</p>
<p>Note that only the text you type in is affected by the above faces.
Prompts and Minibuffer messages are not affected.
@@ -1150,8 +1150,8 @@
above block should be commented out.
</p>
<p>Even though these commands are sometimes useful, they are no substitute for
-the powerful <em>tag table</em> facility of Emacs. Viper's <kbd>:tag</kbd>
command
-in a primitive interface to Emacs tags. See <a
href="../emacs/Tags.html#Tags">Tags: (emacs)Tags</a> section `Tags' in
<cite>The Gnu Emacs Manual</cite>, for more information on tags.
+the powerful <em>tag table</em> facility of Emacs. Viper’s
<kbd>:tag</kbd> command
+in a primitive interface to Emacs tags. See <a
href="../emacs/Tags.html#Tags">Tags: (emacs)Tags</a> section ‘Tags’
in <cite>The Gnu Emacs Manual</cite>, for more information on tags.
</p>
<p>The following two commands are normally bound to a mouse click and are part
of Viper. They work only if Emacs runs as an application under X
@@ -1183,8 +1183,8 @@
<p>This would bind mouse search to the action invoked by pressing the
Meta key and clicking mouse button 1. The allowed values of
<code>viper-mouse-search-key</code> are lists that contain a mouse-button
number
-(1,2, or 3) and any combination of the words `control', `meta', and
-`shift'.
+(1,2, or 3) and any combination of the words ‘control’,
‘meta’, and
+‘shift’.
</p>
<p>If the requested mouse action (e.g., (meta 1)) is already taken for other
purposes then you have to confirm your intention by placing the following
@@ -1199,16 +1199,16 @@
follows. If search is invoked via a single click, Viper chooses the region
that lies between the beginning of the “word” under the pointer
(“word”
is understood in Vi sense) and the end of that word. The only difference
-with Vi's words is that in Lisp major modes `-' is considered an
+with Vi’s words is that in Lisp major modes ‘-’ is
considered an
alphanumeric symbol. This is done for the convenience of working with Lisp
-symbols, which often have an `-' in them. Also, if you click on a
+symbols, which often have an ‘-’ in them. Also, if you click on a
non-alphanumeric character that is not a word separator (in Vi sense) then
this character will also be considered alphanumeric, provided that it is
adjacent (from either side) to an alphanumeric character. This useful
feature gives added control over the patterns selected by the mouse click.
</p>
<p>On a double-click, the region is determined by the beginning of the current
-Vi's “Word” (i.e., the largest non-separator chunk of text) and
the End
+Vi’s “Word” (i.e., the largest non-separator chunk of text)
and the End
of that “Word” (as determined by the <kbd>E</kbd> command).
</p>
<p>On a triple-click, the region consists of the entire line where the click
@@ -1267,11 +1267,11 @@
instance, if you are typing in a frame, A, and then move the mouse to frame
B and click to invoke mouse search, search (or insertion) will be performed
in frame A. To perform search/insertion in frame B, you will first have to
-shift focus there, which doesn't happen until you type a character or
-perform some other action in frame B—mouse search doesn't shift focus.
+shift focus there, which doesn’t happen until you type a character or
+perform some other action in frame B—mouse search doesn’t shift
focus.
</p>
-<p>If you decide that you don't like the above feature and always want
-search/insertion be performed in the frame where the click occurs, don't
+<p>If you decide that you don’t like the above feature and always want
+search/insertion be performed in the frame where the click occurs, don’t
bind (and unbind, if necessary) <code>viper-mouse-catch-frame-switch</code>
from
the mouse event it is bound to.
</p>
@@ -1326,9 +1326,9 @@
</p>
<p>If, however, you need to use a macro regularly, it must be given a
permanent name and saved. Emacs manual explains how to do this, but
-invocation of named Emacs macros is quite different from Vi's. First,
+invocation of named Emacs macros is quite different from Vi’s. First,
invocation of permanent Emacs macros takes time because it requires typing
-too many keys (to a Vi user's taste, anyway).
+too many keys (to a Vi user’s taste, anyway).
Second, binding such macros to function keys, for
fast access, hogs valuable real estate on the keyboard.
</p>
@@ -1352,7 +1352,7 @@
command history and in the startup file, for future use).
</p>
<p>Macros defined by mixing Vi and Emacs commands are represented as
-vectors. So, don't be confused when you see one (usually through the
+vectors. So, don’t be confused when you see one (usually through the
history of Ex commands). For instance, if <kbd>gg</kbd> is defined by typing
<kbd>l</kbd>, the up-arrow key and <kbd>M-x next-line</kbd>, its definition
will look
as follows in Emacs (in XEmacs, it looks slightly different, see below):
@@ -1366,11 +1366,11 @@
not just to printable keys. For instance, one can define a macro that will
be invoked by hitting <kbd>f3</kbd> then <kbd>f2</kbd> function keys. (The
keys
<kbd>delete</kbd> and <kbd>backspace</kbd> are excluded; also, a macro
invocation
-sequence can't start with <ESC>. Some other keys, such as <kbd>f1</kbd>
and
-<kbd>help</kbd>, can't be bound to macros under Emacs, since they
+sequence can’t start with <ESC>. Some other keys, such as
<kbd>f1</kbd> and
+<kbd>help</kbd>, can’t be bound to macros under Emacs, since they
are bound in <code>key-translation-map</code>, which overrides any other
binding
the user gives to keys. In general, keys that have a binding in
-<code>key-translation-map</code> can't be bound to a macro.)
+<code>key-translation-map</code> can’t be bound to a macro.)
</p>
<p>Fourth, in Viper, one can define macros that are specific to a given
buffer, a given major mode, or macros that are defined for all buffers. In
@@ -1384,7 +1384,7 @@
macros) lets the user define keyboard macros that ask for confirmation or
even prompt the user for input and then continue. To do this, one should
type <kbd>C-x q</kbd> (for confirmation) or <kbd>C-u C-x q</kbd> (for prompt).
-For details, see <a
href="../emacs/Kbd-Macro-Query.html#Kbd-Macro-Query">(emacs)Kbd Macro Query</a>
section `Customization' in <cite>The GNU Emacs Manual</cite>
+For details, see <a
href="../emacs/Kbd-Macro-Query.html#Kbd-Macro-Query">(emacs)Kbd Macro Query</a>
section ‘Customization’ in <cite>The GNU Emacs Manual</cite>
</p>
<p>When the user finishes defining a macro (which is done by typing
<kbd>C-x)</kbd> —
a departure from Vi), you will be asked whether you want this
@@ -1393,7 +1393,7 @@
This is the easiest way to save a macro and make
it permanently available. If you work your startup files with bare hands,
here is how Viper saves the above macro so that it will be
-available in Viper's Insert state (and Replace state) in buffer
<code>my-buf</code>
+available in Viper’s Insert state (and Replace state) in buffer
<code>my-buf</code>
only:
</p>
<table><tr><td> </td><td><pre class="example">(viper-record-kbd-macro
"gg" 'insert-state
@@ -1454,7 +1454,7 @@
</p>
<p>If an error occurs during macro definition, Emacs
aborts the process, and it must be repeated. This is analogous to Vi,
-except that in Vi the user doesn't know there is an error until the macro is
+except that in Vi the user doesn’t know there is an error until the
macro is
actually run. All that means that in order for a definition to be
successful, the user must do some simple planning of the process in
advance, to avoid errors. For instance, if you want to map <kbd>gg</kbd> to
@@ -1483,7 +1483,7 @@
<p>binds the key f13 to the Emacs function that repeats the last minibuffer
command. Under Viper, however, you may still use this key for additional
purposes, if you bind, say, a double-hitting action for that key to some
-other function. Emacs doesn't allow the user to do that, but Viper does
+other function. Emacs doesn’t allow the user to do that, but Viper does
this through its keyboard macro facility. To do this, type <kbd>:map </kbd>
first. When you are asked to enter a macro name, hit f13 twice, followed by
<RET> or <SPC>.
@@ -1493,7 +1493,7 @@
macro is executed. Suppose now we wanted to bind the key sequence
<kbd>f13 f13</kbd> to the command <code>eval-last-sexp</code>. To accomplish
this, we
can type <kbd>M-x eval-last-sexp</kbd> followed by <kbd>C-x )</kbd>.
-If you answer positively to Viper's offer to save this macro in
‘<tt>~/.viper</tt>’
+If you answer positively to Viper’s offer to save this macro in
‘<tt>~/.viper</tt>’
for future uses, the following will be inserted in that file:
</p>
<table><tr><td> </td><td><pre class="example">(viper-record-kbd-macro
[f16 f16] 'vi-state
@@ -1504,7 +1504,7 @@
<p>To illustrate the above point, Viper provides two canned macros, which, by
default, are bound to <kbd>[f12 \1]</kbd> and <kbd>[f12 \2]</kbd> (invoked by
typing
<kbd>f12</kbd> then <kbd>1</kbd> and <kbd>2</kbd>, respectively). These
macros are useful
-shortcuts to Viper's command ring history. The first macro will execute the
+shortcuts to Viper’s command ring history. The first macro will execute
the
second-last destructive command (the last one is executed by <kbd>.</kbd>, as
usual). The second macro executes the third-last command.
</p>
@@ -1526,7 +1526,7 @@
<p>Viper allows the user to define macro names that are prefixes of other
macros.
For instance, one can define <kbd>[[</kbd> and <kbd>[[[[</kbd> to be macros.
If you type the exact sequence of such keys and then pause, Viper will
-execute the right macro. However, if you don't pause and, say, type
+execute the right macro. However, if you don’t pause and, say, type
<kbd>[[[[text</kbd> then the conflict is resolved as follows. If only one of
the
key sequences, <kbd>[[</kbd> or <kbd>[[[[</kbd> has a definition applicable to
the
current buffer, then, in fact, there is no conflict and the right macro
@@ -1543,7 +1543,7 @@
f7 a]</code>). The same holds for unmapping. Hitting <TAB> while
typing a macro name in the <kbd>:unmap</kbd> or <kbd>:unmap!</kbd> command will
cause name completion. Completions are displayed as strings or
-vectors. However, as before, you don't actually type
‘<samp>"</samp>’,
+vectors. However, as before, you don’t actually type
‘<samp>"</samp>’,
‘<samp>[</samp>’, or ‘<samp>]</samp>’ that appear in
the completions. These are
meta-symbols that indicate whether the corresponding macro name is a
vector or a string.
@@ -1553,7 +1553,7 @@
More precisely, while defining or executing a macro, the special meaning
of key sequences (as Vi macros) is ignored.
This is because it is all too easy to create an infinite loop in this way.
-Since Viper macros are much more powerful than Vi's it is impossible to
+Since Viper macros are much more powerful than Vi’s it is impossible to
detect such loops. In practice, this is not really a limitation but,
rather, a feature.
</p>
@@ -1567,7 +1567,7 @@
<p>For the most part, Viper macros defined in ‘<tt>~/.viper</tt>’
can be shared
between Emacs, XEmacs, and X and TTY modes. However, macros defined via
function keys may need separate definitions when XEmacs and Emacs have
-different names for the same keyboard key. For instance, the `Page Up' key
+different names for the same keyboard key. For instance, the ‘Page
Up’ key
may be known in Emacs as <kbd>prior</kbd> and in XEmacs as <kbd>pgup</kbd>.
The problem with TTY may be that the function keys there generate sequences
of events instead of a single event (as under a window system).
@@ -1575,7 +1575,7 @@
(e.g., the sequences generated by the arrow keys are mapped to <kbd>up</kbd>,
<kbd>left</kbd>, etc.). However, not all function keys are mapped in this way.
Macros that are bound to key sequences that contain such unmapped function
-keys have to be redefined for TTY's (and possibly for every type of TTY you
+keys have to be redefined for TTY’s (and possibly for every type of TTY
you
may be using). To do this, start Emacs on an appropriate TTY device and
define the macro using <kbd>:map</kbd>, as usual.
</p>
Index: Tests/viper_res/viper_5.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/viper_res/viper_5.html,v
retrieving revision 1.27
retrieving revision 1.28
diff -u -b -r1.27 -r1.28
--- Tests/viper_res/viper_5.html 5 Feb 2007 15:30:26 -0000 1.27
+++ Tests/viper_res/viper_5.html 3 Oct 2007 09:34:54 -0000 1.28
@@ -197,7 +197,7 @@
<p>Note that ‘<samp>%</samp>’ is used in Ex commands <kbd>:e</kbd>
and <kbd>:r <shell-cmd></kbd>
to mean current file. If you want a ‘<samp>%</samp>’ in your
command, it must be
escaped as ‘<samp>\%</samp>’. Note that <kbd>:w</kbd> and the
regular <kbd>:r <file></kbd>
-command doesn't support the meta symbols ‘<samp>%</samp>’ and
‘<samp>#</samp>’, because
+command doesn’t support the meta symbols ‘<samp>%</samp>’
and ‘<samp>#</samp>’, because
file history is a better mechanism.
<a name="IDX246"></a>
Similarly, ‘<samp>#</samp>’ expands to the previous file. The
previous file is
@@ -248,13 +248,13 @@
optional, usually defaulting to 1. Brackets are elided for
‘<samp><count></samp>’ to eschew obfuscation.
</p>
-<p>Viper's idea of Vi's words is slightly different from Vi. First, Viper
+<p>Viper’s idea of Vi’s words is slightly different from Vi.
First, Viper
words understand Emacs symbol tables. Therefore, all symbols declared to be
alphanumeric in a symbol table can automatically be made part of the Viper
word. This is useful when, for instance, editing text containing European,
Cyrillic, Japanese, etc., texts.
</p>
-<p>Second, Viper lets you depart from Vi's idea of a word by changing the a
+<p>Second, Viper lets you depart from Vi’s idea of a word by changing
the a
syntax preference via the customization widget (the variable
<code>viper-syntax-preference</code>) or by executing
<code>viper-set-syntax-preference</code> interactively.
@@ -263,7 +263,7 @@
Viper considers only those symbols to be part of a word that are specified
as word-symbols by the current Emacs syntax table (which may be different
for different major modes) plus the underscore symbol <kbd>_</kbd>, minus the
-symbols that are not considered words in Vi (e.g., `,',;, etc.), but may be
+symbols that are not considered words in Vi (e.g., ‘,’,;, etc.),
but may be
considered as word-symbols by various Emacs major modes. Reformed-Vi works
very close to Vi, and it also recognizes words in other
alphabets. Therefore, this is the most appropriate mode for editing text
@@ -301,8 +301,8 @@
<p>The above discussion concerns only the movement commands. In regular
expressions, words remain the same as in Emacs. That is, the expressions
-<code>\w</code>, <code>\></code>, <code>\<</code>, etc., use Emacs' idea
of what is a word,
-and they don't look into the value of variable
+<code>\w</code>, <code>\></code>, <code>\<</code>, etc., use
Emacs’ idea of what is a word,
+and they don’t look into the value of variable
<code>viper-syntax-preference</code>. This is because Viper avoids changing
syntax tables in order to not thwart the various major modes that set these
tables.
@@ -313,7 +313,7 @@
C, -, h!!!</em> The <kbd>^</kbd> is itself, never used to indicate a
Control character.
</p>
-<p>Finally, we note that Viper's Ex-style commands can be made to work on the
+<p>Finally, we note that Viper’s Ex-style commands can be made to work
on the
current Emacs region. This is done by typing a digit argument before
<kbd>:</kbd>. For instance, typing <kbd>1:</kbd> will propmt you with
something like
<em>:123,135</em>, assuming that the current region starts at line 123 and
@@ -547,7 +547,7 @@
This option can also be toggled interactively if you quickly hit
<kbd>%%%</kbd>.
</p>
<p>This latter feature is implemented as a vi-style keyboard macro. If you
-don't want this macro, put
+don’t want this macro, put
</p>
<table><tr><td> </td><td><pre
class="example">(viper-set-parsing-style-toggling-macro 'undefine)
</pre></td></tr></table>
@@ -636,7 +636,7 @@
<p>Emacs mark is referred to in the region specifiers <kbd>r</kbd> and
<kbd>R</kbd>.
See section <a href="viper_2.html#SEC4">Emacs Preliminaries</a>, and See
section <a href="viper_3.html#SEC15">Basics</a>, for explanation. Also
-see <a href="../emacs/Mark.html#Mark">(emacs)Mark</a> section `Mark' in
<cite>The GNU Emacs manual</cite>, for an explanation of
+see <a href="../emacs/Mark.html#Mark">(emacs)Mark</a> section
‘Mark’ in <cite>The GNU Emacs manual</cite>, for an explanation of
the Emacs mark ring.
</p>
<a name="IDX323"></a>
@@ -652,7 +652,7 @@
<dd><p>Set the Emacs mark (see section <a href="viper_2.html#SEC4">Emacs
Preliminaries</a>) back to where it was last
set with the <kbd>m.</kbd> command. This is useful when you set the mark with
<kbd>m.</kbd>, but then some other command (such as <kbd>L</kbd> or
<kbd>G</kbd>) changes
-it in a way that you didn't like.
+it in a way that you didn’t like.
</p></dd>
<dt> <kbd>m <</kbd></dt>
<dd><p>Set the Emacs mark at beginning of buffer.
@@ -780,13 +780,13 @@
</p></dd>
<dt> <kbd>C-c M-p and C-c M-n</kbd></dt>
<dd><p>In Vi state,
-these commands help peruse the history of Vi's destructive commands.
+these commands help peruse the history of Vi’s destructive commands.
Successive typing of <kbd>C-c M-p</kbd> causes Viper to search the history in
the direction
of older commands, while hitting <kbd>C-c M-n</kbd> does so in reverse
order. Each command in the history is displayed in the Minibuffer. The
displayed command can
-then be executed by typing `<kbd>.</kbd>'.
+then be executed by typing ‘<kbd>.</kbd>’.
</p>
<p>Since typing the above sequences of keys may be tedious, the
functions doing the perusing can be bound to unused keyboard keys in the
@@ -992,7 +992,7 @@
</p>
<p>In Emacs, ‘<samp>\&</samp>’ stands for the last matched
expression, so
<kbd>s/[ab]+/\&\&/</kbd> will double the string matched by
<kbd>[ab]</kbd>.
-Viper doesn't treat ‘<samp>&</samp>’ specially, unlike Vi: use
‘<samp>\&</samp>’ instead.
+Viper doesn’t treat ‘<samp>&</samp>’ specially, unlike
Vi: use ‘<samp>\&</samp>’ instead.
</p>
<p>Viper does not parse search patterns and does not expand special symbols
found there (e.g., ‘<samp>~</samp>’ is not expanded to the result
of the previous
@@ -1127,7 +1127,7 @@
and execute the Ex <cmd> on each occurrence.
</p></dd>
<dt> <kbd>:[x,y]v/<string>/<cmd></kbd></dt>
-<dd><p>Execute <cmd> on the lines that don't match.
+<dd><p>Execute <cmd> on the lines that don’t match.
</p></dd>
<dt> <kbd>#g<move></kbd></dt>
<dd><p>Execute the last keyboard macro for each line in the region.
@@ -1411,7 +1411,7 @@
<p>In all file handling commands, space should be typed before entering the
file
-name. If you need to type a modifier, such as <kbd>>></kbd> or
<kbd>!</kbd>, don't
+name. If you need to type a modifier, such as <kbd>>></kbd> or
<kbd>!</kbd>, don’t
put any space between the command and the modifier.
</p>
<p>Note that many Ex commands, e.g., <kbd>:w</kbd>, accept command arguments.
The
@@ -1435,7 +1435,7 @@
<dt> <kbd>:[x,y] w</kbd></dt>
<dd><p>Write the file. Viper makes sure that a final newline is always added
to
any file where this newline is missing. This is done by setting Emacs
-variable <code>require-final-newline</code> to <code>t</code>. If you don't
like this
+variable <code>require-final-newline</code> to <code>t</code>. If you
don’t like this
feature, use <code>setq-default</code> to set
<code>require-final-newline</code> to
<code>nil</code>. This must be done in ‘<tt>.viper</tt>’ file.
</p></dd>
@@ -1721,7 +1721,7 @@
</p>
<p>Symbols ‘<samp>%</samp>’ and ‘<samp>#</samp>’ are
also used in the Ex commands <kbd>:e</kbd> and
<kbd>:r <shell-cmd></kbd>. The commands <kbd>:w</kbd> and the regular
<kbd>:r
-<file></kbd> command don't support these meta symbols, because file
history is a
+<file></kbd> command don’t support these meta symbols, because
file history is a
better mechanism.
</p>
<a name="IDX494"></a>
@@ -1814,7 +1814,7 @@
</p></dd>
<dt> <kbd>autoindent-global</kbd></dt>
<dt> <kbd>ai-global</kbd></dt>
-<dd><p>Same as `autoindent', but affects all buffers.
+<dd><p>Same as ‘autoindent’, but affects all buffers.
</p></dd>
<dt> <kbd>noautoindent</kbd></dt>
<dt> <kbd>noai</kbd></dt>
@@ -1869,8 +1869,8 @@
<dd><a name="IDX513"></a>
<a name="IDX514"></a>
<p>showmatch – Whenever you append a <kbd>)</kbd>, Vi shows
-its match if it's on the same page; also with
-<kbd>{</kbd> and <kbd>}</kbd>. If there's no match, Vi will beep.
+its match if it’s on the same page; also with
+<kbd>{</kbd> and <kbd>}</kbd>. If there’s no match, Vi will beep.
</p></dd>
<dt> <kbd>noshowmatch</kbd></dt>
<dt> <kbd>nosm</kbd></dt>
@@ -1887,7 +1887,7 @@
</p></dd>
<dt> <kbd>tabstop-global</kbd></dt>
<dt> <kbd>ts-g</kbd></dt>
-<dd><p>Same as `tabstop', but affects all buffers.
+<dd><p>Same as ‘tabstop’, but affects all buffers.
</p></dd>
<dt> <kbd>wrapmargin=<count></kbd></dt>
<dt> <kbd>wm=<count></kbd></dt>
@@ -1998,8 +1998,8 @@
<dd><p>Emacs find-file, useful in Insert state
</p></dd>
<dt> <kbd>C-y</kbd></dt>
-<dd><p>Put back the last killed text. Similar to Vi's <kbd>p</kbd>, but also
works in
-Insert and Replace state. This command doesn't work in Vi command state,
+<dd><p>Put back the last killed text. Similar to Vi’s <kbd>p</kbd>, but
also works in
+Insert and Replace state. This command doesn’t work in Vi command state,
since this binding is taken for something else.
</p></dd>
<dt> <kbd>M-y</kbd></dt>
Index: Tests/viper_res/viper_6.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/viper_res/viper_6.html,v
retrieving revision 1.17
retrieving revision 1.18
diff -u -b -r1.17 -r1.18
--- Tests/viper_res/viper_6.html 5 Feb 2007 15:30:26 -0000 1.17
+++ Tests/viper_res/viper_6.html 3 Oct 2007 09:34:54 -0000 1.18
@@ -64,7 +64,7 @@
<p>Viper, formerly known as VIP-19, was written by Michael Kifer. Viper is
based on the original VIP package by Masahiko Sato and on its enhancement,
VIP 4.4, by Aamod Sane. This manual is an adaptation of the manual for VIP
-4.4, which, in turn, was based on Sato's manual for VIP 3.5.
+4.4, which, in turn, was based on Sato’s manual for VIP 3.5.
</p>
<p>Many contributors on the Net pointed out bugs and suggested a number of
useful features. Scott Bronson and Samuel Padgett contributed patches that
Index: Tests/xemacs_frame_res/xemacs.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/xemacs_frame_res/xemacs.html,v
retrieving revision 1.22
retrieving revision 1.23
diff -u -b -r1.22 -r1.23
--- Tests/xemacs_frame_res/xemacs.html 5 Feb 2007 15:30:26 -0000 1.22
+++ Tests/xemacs_frame_res/xemacs.html 3 Oct 2007 09:34:54 -0000 1.23
@@ -82,7 +82,7 @@
corresponds to XEmacs version 21.0.
</p>
<p>This manual is intended as a detailed reference to XEmacs. If
-you are looking for an introductory manual, see the New User's
+you are looking for an introductory manual, see the New User’s
Guide.
</p>
<table class="menu" border="0" cellspacing="0">
@@ -96,7 +96,7 @@
</td></tr>
<tr><td align="left" valign="top"><a
href="xemacs_31.html#SEC403">Glossary</a></td><td> </td><td
align="left" valign="top"> The glossary.
</td></tr>
-<tr><td align="left" valign="top"><a href="xemacs_32.html#SEC404">The GNU
Manifesto</a></td><td> </td><td align="left" valign="top"> What's
GNU? Gnu's Not Unix!
+<tr><td align="left" valign="top"><a href="xemacs_32.html#SEC404">The GNU
Manifesto</a></td><td> </td><td align="left" valign="top">
What’s GNU? Gnu’s Not Unix!
</td></tr>
<tr><th colspan="3" align="left" valign="top"><pre class="menu-comment">
Indices, nodes containing large menus
@@ -216,7 +216,7 @@
<tr><td align="left" valign="top"><a href="xemacs_29.html#SEC346">26.10
Recursive Editing Levels</a></td><td> </td><td align="left"
valign="top">
A command can allow you to do editing
"within the command". This is called a
- `recursive editing level'.
+ ‘recursive editing level’.
</td></tr>
<tr><td align="left" valign="top"><a href="xemacs_29.html#SEC347">26.11
Dissociated Press</a></td><td> </td><td align="left" valign="top">
Dissociating text for fun.
</td></tr>
@@ -808,11 +808,11 @@
<tr><th colspan="3" align="left" valign="top"><pre class="menu-comment">
Variables
-</pre></th></tr><tr><td align="left" valign="top"><a
href="xemacs_30.html#SEC354">27.2.1 Examining and Setting
Variables</a></td><td> </td><td align="left" valign="top">
Examining or setting one variable's value.
+</pre></th></tr><tr><td align="left" valign="top"><a
href="xemacs_30.html#SEC354">27.2.1 Examining and Setting
Variables</a></td><td> </td><td align="left" valign="top">
Examining or setting one variable’s value.
</td></tr>
<tr><td align="left" valign="top"><a href="xemacs_30.html#SEC355">27.2.2 Easy
Customization Interface</a></td><td> </td><td align="left"
valign="top"> Convenient and easy customization of variables.
</td></tr>
-<tr><td align="left" valign="top"><a href="xemacs_30.html#SEC360">27.2.3
Editing Variable Values</a></td><td> </td><td align="left"
valign="top"> Examining or editing list of all variables' values.
+<tr><td align="left" valign="top"><a href="xemacs_30.html#SEC360">27.2.3
Editing Variable Values</a></td><td> </td><td align="left"
valign="top"> Examining or editing list of all variables’ values.
</td></tr>
<tr><td align="left" valign="top"><a href="xemacs_30.html#SEC361">27.2.4 Local
Variables</a></td><td> </td><td align="left" valign="top">
Per-buffer values of variables.
</td></tr>
@@ -831,9 +831,9 @@
Customizing Key Bindings
</pre></th></tr><tr><td align="left" valign="top"><a
href="xemacs_30.html#SEC368">27.4.1 Keymaps</a></td><td> </td><td
align="left" valign="top"> Definition of the keymap data structure.
- Names of XEmacs's standard keymaps.
+ Names of XEmacs’s standard keymaps.
</td></tr>
-<tr><td align="left" valign="top"><a href="xemacs_30.html#SEC369">27.4.2
Changing Key Bindings</a></td><td> </td><td align="left"
valign="top"> How to redefine one key's meaning conveniently.
+<tr><td align="left" valign="top"><a href="xemacs_30.html#SEC369">27.4.2
Changing Key Bindings</a></td><td> </td><td align="left"
valign="top"> How to redefine one key’s meaning conveniently.
</td></tr>
<tr><td align="left" valign="top"><a href="xemacs_30.html#SEC373">27.4.3
Disabling Commands</a></td><td> </td><td align="left" valign="top">
Disabling a command means confirmation is required
before it can be executed. This is done to protect
@@ -858,7 +858,7 @@
<tr><th colspan="3" align="left" valign="top"><pre class="menu-comment">
Dealing with XEmacs Trouble
-</pre></th></tr><tr><td align="left" valign="top"><a
href="xemacs_30.html#SEC394">27.12.1 Recursive Editing
Levels</a></td><td> </td><td align="left" valign="top"> `[...]'
in mode line around the parentheses.
+</pre></th></tr><tr><td align="left" valign="top"><a
href="xemacs_30.html#SEC394">27.12.1 Recursive Editing
Levels</a></td><td> </td><td align="left" valign="top">
‘[...]’ in mode line around the parentheses.
</td></tr>
<tr><td align="left" valign="top"><a href="xemacs_30.html#SEC395">27.12.2
Garbage on the Screen</a></td><td> </td><td align="left"
valign="top"> Garbage on the screen.
</td></tr>
@@ -869,7 +869,7 @@
<tr><td align="left" valign="top"><a href="xemacs_30.html#SEC398">27.12.5
Emergency Escape</a></td><td> </td><td align="left" valign="top">
Emergency escape—
What to do if XEmacs stops responding.
</td></tr>
-<tr><td align="left" valign="top"><a href="xemacs_30.html#SEC399">27.12.6 Help
for Total Frustration</a></td><td> </td><td align="left"
valign="top"> When you are at your wits' end.
+<tr><td align="left" valign="top"><a href="xemacs_30.html#SEC399">27.12.6 Help
for Total Frustration</a></td><td> </td><td align="left"
valign="top"> When you are at your wits’ end.
</td></tr>
<tr><th colspan="3" align="left" valign="top"><pre class="menu-comment">
</pre></th></tr></table>
Index: Tests/xemacs_frame_res/xemacs_1.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/xemacs_frame_res/xemacs_1.html,v
retrieving revision 1.21
retrieving revision 1.22
diff -u -b -r1.21 -r1.22
--- Tests/xemacs_frame_res/xemacs_1.html 5 Feb 2007 15:30:26 -0000
1.21
+++ Tests/xemacs_frame_res/xemacs_1.html 3 Oct 2007 09:34:54 -0000
1.22
@@ -95,7 +95,7 @@
at the mercy of those companies. By contrast, our General Public
License is intended to guarantee your freedom to share and change free
software—to make sure the software is free for all its users. The
-General Public License applies to the Free Software Foundation's
+General Public License applies to the Free Software Foundation’s
software and to any other program whose authors commit to using it.
You can use it for your programs, too.
</p>
@@ -120,12 +120,12 @@
(2) offer you this license which gives you legal permission to copy,
distribute and/or modify the software.
</p>
-<p> Also, for each author's protection and ours, we want to make certain
+<p> Also, for each author’s protection and ours, we want to make certain
that everyone understands that there is no warranty for this free
software. If the software is modified by someone else and passed on, we
want its recipients to know that what they have is not the original, so
that any problems introduced by others will not reflect on the original
-authors' reputations.
+authors’ reputations.
</p>
<p> The precise terms and conditions for copying, distribution and
modification follow.
@@ -144,7 +144,7 @@
</li><li>
<a name="IDX3"></a>
-You may copy and distribute verbatim copies of the Program's source
+You may copy and distribute verbatim copies of the Program’s source
code as you receive it, in any medium, provided that you conspicuously and
appropriately publish on each copy an appropriate copyright notice and
disclaimer of warranty; keep intact all the notices that refer to this
@@ -244,7 +244,7 @@
Program), the recipient automatically receives a license from the original
licensor to copy, distribute or modify the Program subject to these
terms and conditions. You may not impose any further restrictions on the
-recipients' exercise of the rights granted herein.
+recipients’ exercise of the rights granted herein.
</li><li>
@@ -357,10 +357,10 @@
under certain conditions; type `show c' for details.
</pre></td></tr></table>
-<p>The hypothetical commands `show w' and `show c' should show the
+<p>The hypothetical commands ‘show w’ and ‘show c’
should show the
appropriate parts of the General Public License. Of course, the
-commands you use may be called something other than `show w' and `show
-c'; they could even be mouse-clicks or menu items—whatever suits your
+commands you use may be called something other than ‘show w’ and
‘show
+c’; they could even be mouse-clicks or menu items—whatever suits
your
program.
</p>
@@ -376,7 +376,7 @@
Ty Coon, President of Vice
</pre></td></tr></table>
-<p>That's all there is to it!
+<p>That’s all there is to it!
</p>
<hr size="6">
<table cellpadding="1" cellspacing="1" border="0">
Index: Tests/xemacs_frame_res/xemacs_11.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/xemacs_frame_res/xemacs_11.html,v
retrieving revision 1.24
retrieving revision 1.25
diff -u -b -r1.24 -r1.25
--- Tests/xemacs_frame_res/xemacs_11.html 5 Feb 2007 15:30:26 -0000
1.24
+++ Tests/xemacs_frame_res/xemacs_11.html 3 Oct 2007 09:34:54 -0000
1.25
@@ -141,7 +141,7 @@
</p></dd>
<dt> <kbd>C-h c <var>key</var></kbd></dt>
<dd><p>Print the name of the command that <var>key</var> runs
-(<code>describe-key-briefly</code>). Here <kbd>c</kbd> stands for
`character'. For more
+(<code>describe-key-briefly</code>). Here <kbd>c</kbd> stands for
‘character’. For more
extensive information on <var>key</var>, use <kbd>C-h k</kbd>.
</p></dd>
<dt> <kbd>C-h d <var>function</var> <RET></kbd></dt>
@@ -278,7 +278,7 @@
<h2 class="section"> 8.3 Help by Command or Variable Name </h2>
<p> <kbd>C-h f</kbd> (<code>describe-function</code>) reads the name of a Lisp
-function using the minibuffer, then displays that function's
+function using the minibuffer, then displays that function’s
documentation string in a window. Since commands are Lisp functions,
you can use the argument <var>function</var> to get the documentation of a
command that you know by name. For example,
@@ -299,7 +299,7 @@
<code>make-vector</code> properly, type <kbd>C-h f make-vector
<RET></kbd>.
Because <kbd>C-h f</kbd> allows all function names, not just command names,
you may find that some of your favorite abbreviations that work in
-<kbd>M-x</kbd> don't work in <kbd>C-h f</kbd>. An abbreviation may be unique
+<kbd>M-x</kbd> don’t work in <kbd>C-h f</kbd>. An abbreviation may be
unique
among command names, yet fail to be unique when other function names are
allowed.
</p>
@@ -373,7 +373,7 @@
so on. With each command name appears a brief description of how to use
the command, and what keys you can currently invoke it with. For
example, it would say that you can invoke <code>find-file</code> by typing
-<kbd>C-x C-f</kbd>. The <kbd>A</kbd> in <kbd>C-h A</kbd> stands for `Apropos';
+<kbd>C-x C-f</kbd>. The <kbd>A</kbd> in <kbd>C-h A</kbd> stands for
‘Apropos’;
<kbd>C-h A</kbd> runs the command <code>command-apropos</code>. This command
normally checks only commands (interactive functions); if you specify a
prefix argument, it checks noninteractive functions as well.
@@ -381,7 +381,7 @@
<p> Because <kbd>C-h A</kbd> looks only for functions whose names contain the
string you specify, you must use ingenuity in choosing the string. If
you are looking for commands for killing backwards and <kbd>C-h a
-kill-backwards <RET></kbd> doesn't reveal any, don't give up. Try just
+kill-backwards <RET></kbd> doesn’t reveal any, don’t give
up. Try just
<kbd>kill</kbd>, or just <kbd>backwards</kbd>, or just <kbd>back</kbd>. Be
persistent.
Pretend you are playing Adventure. Also note that you can use a regular
expression as the argument, for more flexibility (see section <a
href="xemacs_15.html#SEC121">Syntax of Regular Expressions</a>).
@@ -412,7 +412,7 @@
</p>
<a name="IDX260"></a>
<p> The <code>apropos-value</code> command is like <code>apropos</code>
except that it
-searches symbols' values for matches for the specified regular
+searches symbols’ values for matches for the specified regular
expression. This command does not check function definitions or
property lists by default; specify a numeric argument if you want it to
check them.
@@ -553,7 +553,7 @@
a tutorial on using Info.
</p>
<p> If you specify a numeric argument, <kbd>C-h i</kbd> prompts for the name
of
-a documentation file. This way, you can browse a file which doesn't
+a documentation file. This way, you can browse a file which doesn’t
have an entry in the top-level Info menu. It is also handy when you
need to get to the documentation quickly, and you know the exact name of
the file.
@@ -574,7 +574,7 @@
<a name="IDX267"></a>
<p> If something surprising happens, and you are not sure what commands you
typed, use <kbd>C-h l</kbd> (<code>view-lossage</code>). <kbd>C-h l</kbd>
prints the last
-100 command characters you typed in. If you see commands that you don't
+100 command characters you typed in. If you see commands that you don’t
know, you can use <kbd>C-h c</kbd> to find out what they do.
</p>
<a name="IDX268"></a>
@@ -591,7 +591,7 @@
mode that is not covered by <kbd>C-h m</kbd>. <kbd>C-h b</kbd> displays a
list of
all the key bindings currently in effect, with the local bindings of the
current major mode first, followed by the global bindings (see section <a
href="xemacs_30.html#SEC367">Customizing Key Bindings</a>). <kbd>C-h s</kbd>
displays the contents of the syntax table with
-explanations of each character's syntax (see section <a
href="xemacs_30.html#SEC374">The Syntax Table</a>).
+explanations of each character’s syntax (see section <a
href="xemacs_30.html#SEC374">The Syntax Table</a>).
</p>
<p> You can get a similar list for a particular prefix key by typing
<kbd>C-h</kbd> after the prefix key. (There are a few prefix keys for which
Index: Tests/xemacs_frame_res/xemacs_12.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/xemacs_frame_res/xemacs_12.html,v
retrieving revision 1.26
retrieving revision 1.27
diff -u -b -r1.26 -r1.27
--- Tests/xemacs_frame_res/xemacs_12.html 5 Feb 2007 15:30:26 -0000
1.26
+++ Tests/xemacs_frame_res/xemacs_12.html 3 Oct 2007 09:34:54 -0000
1.27
@@ -95,7 +95,7 @@
<p> To specify the text for a command to operate on, set <em>the
mark</em> at one end of it, and move point to the other end. The text
between point and the mark is called <em>the region</em>. You can move
-point or the mark to adjust the boundaries of the region. It doesn't
+point or the mark to adjust the boundaries of the region. It doesn’t
matter which one is set first chronologically, or which one comes
earlier in the text.
</p>
@@ -375,7 +375,7 @@
The marks you have seen go to the end of the ring, so no marks are lost.
</p>
<p> Each buffer has its own mark ring. All editing commands use the current
-buffer's mark ring. In particular, <kbd>C-u C-<SPC></kbd> always stays
in
+buffer’s mark ring. In particular, <kbd>C-u C-<SPC></kbd> always
stays in
the same buffer.
</p>
<p> Many commands that can move long distances, such as <kbd>M-<</kbd>
@@ -639,7 +639,7 @@
text but do not save it; they are known as <em>delete</em> commands. (This
distinction is made only for erasing text in the buffer.)
</p>
-<p>The commands' names and individual descriptions use the words
+<p>The commands’ names and individual descriptions use the words
‘<samp>kill</samp>’ and ‘<samp>delete</samp>’ to
indicate what they do. If you perform
a kill or delete command by mistake, use the <kbd>C-x u</kbd>
(<code>undo</code>)
command to undo it (see section <a href="xemacs_8.html#SEC59">Undoing
Changes</a>). The delete commands include <kbd>C-d</kbd>
@@ -694,10 +694,10 @@
<p> The most basic delete commands are <kbd>C-d</kbd>
(<code>delete-char</code>) and
<DEL> (<code>delete-backward-char</code>). <kbd>C-d</kbd> deletes the
character after point, the one the cursor is “on top of”. Point
-doesn't move. <DEL> deletes the character before the cursor, and
+doesn’t move. <DEL> deletes the character before the cursor, and
moves point back. You can delete newlines like any other characters in
the buffer; deleting a newline joins two lines. Actually, <kbd>C-d</kbd> and
-<DEL> aren't always delete commands; if you give them an argument,
+<DEL> aren’t always delete commands; if you give them an argument,
they kill instead, since they can erase more than one character this
way.
</p>
@@ -770,7 +770,7 @@
before point is not killed). With a negative argument, <kbd>C-k</kbd> kills
back to a number of line beginnings. An argument of -2 means
kill back to the second line beginning. If point is at the beginning of
-a line, that line beginning doesn't count, so <kbd>C-u - 2 C-k</kbd> with
+a line, that line beginning doesn’t count, so <kbd>C-u - 2 C-k</kbd> with
point at the front of a line kills the two previous lines.
</p>
<p> <kbd>C-k</kbd> with an argument of zero kills all the text before point
on the
@@ -970,7 +970,7 @@
<p> Normally, each kill command pushes a new block onto the kill ring.
However, two or more kill commands in a row combine their text into a
single entry, so that a single <kbd>C-y</kbd> yanks it all back. This means
-you don't have to kill all the text you want to yank in one command; you
+you don’t have to kill all the text you want to yank in one command; you
can kill line after line, or word after word, until you have killed what
you want, then get it all back at once using <kbd>C-y</kbd>. (Thus we join
television in leading people to kill thoughtlessly.)
@@ -1057,7 +1057,7 @@
<p> Once the text you are looking for is brought into the buffer, you can
stop doing <kbd>M-y</kbd> commands and the text will stay there. Since the
text is just a copy of the kill ring item, editing it in the buffer does
-not change what's in the ring. As long you don't kill additional text,
+not change what’s in the ring. As long you don’t kill additional
text,
the “last yank” pointer remains at the same place in the kill ring:
repeating <kbd>C-y</kbd> will yank another copy of the same old kill.
</p>
@@ -1161,7 +1161,7 @@
</p>
<p>Warning: If you use the ‘<tt>xclipboard</tt>’ application,
remember that it
maintains a list of all things that have been pasted to the clipboard (that
-is, copied with the <b>Copy</b> command). If you don't manually delete
elements
+is, copied with the <b>Copy</b> command). If you don’t manually delete
elements
from this list by clicking on the <b>Delete</b> button in the
<code>xclipboard</code>
window, the clipboard will eventually consume a lot of memory.
</p>
@@ -1281,7 +1281,7 @@
application asks the X server for the value of the selection, the X
server requests the information from the owner. When you use
selections, the selection data is not actually transferred unless
-someone wants it; the act of making a selection doesn't transfer data.
+someone wants it; the act of making a selection doesn’t transfer data.
Cut buffers are different: when you "own" a cut buffer, the data is
actually transferred to the X server immediately, and survives the
lifetime of the application.
@@ -1455,7 +1455,7 @@
<dd><p>Prepend region to contents of specified buffer.
</p></dd>
<dt> <kbd>M-x copy-to-buffer</kbd></dt>
-<dd><p>Copy region into specified buffer, deleting that buffer's old contents.
+<dd><p>Copy region into specified buffer, deleting that buffer’s old
contents.
</p></dd>
<dt> <kbd>M-x insert-buffer</kbd></dt>
<dd><p>Insert contents of specified buffer into current buffer at point.
@@ -1498,7 +1498,7 @@
end of the specified file. The file is changed immediately on disk.
This command is normally used with files that are <i>not</i> being visited
in Emacs. Using it on a file that Emacs is visiting can produce
-confusing results, because the file's text inside Emacs does not change
+confusing results, because the file’s text inside Emacs does not change
while the file itself changes.
</p>
<hr size="6">
@@ -1567,7 +1567,7 @@
the text (delete it) or save it as the “last killed” rectangle.
The
commands for these two ways are <kbd>M-x delete-rectangle</kbd> and <kbd>M-x
kill-rectangle</kbd>. In either case, the portion of each line that falls
inside
-the rectangle's boundaries is deleted, causing following text (if any) on
+the rectangle’s boundaries is deleted, causing following text (if any) on
the line to move left.
</p>
<p> Note that “killing” a rectangle is not killing in the usual
sense; the
@@ -1580,7 +1580,7 @@
</p>
<p> Inserting a rectangle is the opposite of deleting one. You specify
where to put the upper left corner by putting point there. The
-rectangle's first line is inserted at point, the rectangle's second line
+rectangle’s first line is inserted at point, the rectangle’s
second line
is inserted at a point one line vertically down, and so on. The number
of lines affected is determined by the height of the saved rectangle.
</p>
Index: Tests/xemacs_frame_res/xemacs_13.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/xemacs_frame_res/xemacs_13.html,v
retrieving revision 1.23
retrieving revision 1.24
diff -u -b -r1.23 -r1.24
--- Tests/xemacs_frame_res/xemacs_13.html 5 Feb 2007 15:30:26 -0000
1.23
+++ Tests/xemacs_frame_res/xemacs_13.html 3 Oct 2007 09:34:54 -0000
1.24
@@ -284,7 +284,7 @@
</p>
<dl compact="compact">
<dt> <kbd>C-x r w <var>r</var></kbd></dt>
-<dd><p>Save the state of the selected frame's windows in register <var>r</var>
+<dd><p>Save the state of the selected frame’s windows in register
<var>r</var>
(<code>window-configuration-to-register</code>).
</p></dd>
<dt> <kbd>M-x frame-configuration-to-register <RET>
<var>r</var></kbd></dt>
@@ -366,7 +366,7 @@
<h2 class="section"> 10.6 Keeping File Names in Registers </h2>
<p> If you visit certain file names frequently, you can visit them more
-conveniently if you put their names in registers. Here's the Lisp code
+conveniently if you put their names in registers. Here’s the Lisp code
used to put a file name in a register:
</p>
<table><tr><td> </td><td><pre class="smallexample">(set-register
?<var>r</var> '(file . <var>name</var>))
@@ -467,7 +467,7 @@
<a name="IDX376"></a>
<p> If you set the variable <code>bookmark-save-flag</code> to 1, then each
command that sets a bookmark will also save your bookmarks; this way,
-you don't lose any bookmark values even if XEmacs crashes. (The value,
+you don’t lose any bookmark values even if XEmacs crashes. (The value,
if a number, says how many bookmark modifications should go by between
saving.)
</p>
@@ -475,7 +475,7 @@
<p> Bookmark position values are saved with surrounding context, so that
<code>bookmark-jump</code> can find the proper position even if the file is
modified slightly. The variable <code>bookmark-search-size</code> says how
-many characters of context to record, on each side of the bookmark's
+many characters of context to record, on each side of the bookmark’s
position.
</p>
<p> Here are some additional commands for working with bookmarks:
Index: Tests/xemacs_frame_res/xemacs_14.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/xemacs_frame_res/xemacs_14.html,v
retrieving revision 1.23
retrieving revision 1.24
diff -u -b -r1.23 -r1.24
--- Tests/xemacs_frame_res/xemacs_14.html 5 Feb 2007 15:30:26 -0000
1.23
+++ Tests/xemacs_frame_res/xemacs_14.html 3 Oct 2007 09:34:54 -0000
1.24
@@ -285,7 +285,7 @@
less, to be precise). <kbd>C-x ></kbd> (<code>scroll-right</code>) scrolls
similarly to the right. The window cannot be scrolled any farther to
the right once it is displaying normally (with each line starting at the
-window's left margin); attempting to do so has no effect.
+window’s left margin); attempting to do so has no effect.
</p>
<hr size="6">
<a name="Selective-Display"></a>
@@ -369,7 +369,7 @@
<a name="IDX403"></a>
<p> The variable <code>echo-keystrokes</code> controls the echoing of
multi-character
keys; its value is the number of seconds of pause required to cause echoing
-to start, or zero, meaning don't echo at all. See section <a
href="xemacs_4.html#SEC9">The Echo Area</a>.
+to start, or zero, meaning don’t echo at all. See section <a
href="xemacs_4.html#SEC9">The Echo Area</a>.
</p>
<a name="IDX404"></a>
<p> If the variable <code>ctl-arrow</code> is <code>nil</code>, control
characters in the
Index: Tests/xemacs_frame_res/xemacs_15.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/xemacs_frame_res/xemacs_15.html,v
retrieving revision 1.28
retrieving revision 1.29
diff -u -b -r1.28 -r1.29
--- Tests/xemacs_frame_res/xemacs_15.html 5 Feb 2007 15:30:26 -0000
1.28
+++ Tests/xemacs_frame_res/xemacs_15.html 3 Oct 2007 09:34:54 -0000
1.29
@@ -443,7 +443,7 @@
there are multiple spaces, newlines or other punctuation between the words.
</p>
<p> Word search is useful in editing documents formatted by text formatters.
-If you edit while looking at the printed, formatted version, you can't tell
+If you edit while looking at the printed, formatted version, you can’t
tell
where the line breaks are in the source file. Word search, allows you
to search without having to know the line breaks.
</p>
@@ -500,8 +500,8 @@
</p>
<p> To gain a thorough understanding of regular expressions and how to use
them to best advantage, we recommend that you study <cite>Mastering
-Regular Expressions, by Jeffrey E.F. Friedl, O'Reilly and Associates,
-1997</cite>. (It's known as the "Hip Owls" book, because of the
picture on its
+Regular Expressions, by Jeffrey E.F. Friedl, O’Reilly and Associates,
+1997</cite>. (It’s known as the "Hip Owls" book, because of
the picture on its
cover.) You might also read the manuals to <a
href="../gawk/index.html#Top">(gawk)Top</a>,
<a href="../ed/index.html#Top">(ed)Top</a>, <cite>sed</cite>,
<cite>grep</cite>, <a href="../perl/index.html#Top">(perl)Top</a>,
<a href="../regex/index.html#Top">(regex)Top</a>, <a
href="../rx/index.html#Top">(rx)Top</a>, <cite>pcre</cite>, and <a
href="../flex/index.html#Top">(flex)Top</a>, which
@@ -509,7 +509,7 @@
</p>
<p> The XEmacs regular expression syntax most closely resembles that of
<cite>ed</cite>, or <cite>grep</cite>, the GNU versions of which all utilize
the GNU
-<cite>regex</cite> library. XEmacs' version of <cite>regex</cite> has
recently been
+<cite>regex</cite> library. XEmacs’ version of <cite>regex</cite> has
recently been
extended with some Perl–like capabilities, described in the next
section.
</p>
@@ -627,7 +627,7 @@
backtracking loops. For example, it could take hours for the regular
expression ‘<samp>\(x+y*\)*a</samp>’ to match the sequence
‘<samp>xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxz</samp>’. The slowness
is because
-Emacs must try each imaginable way of grouping the 35
‘<samp>x</samp>’'s before
+Emacs must try each imaginable way of grouping the 35
‘<samp>x</samp>’’s before
concluding that none of them can work. To make sure your regular
expressions run fast, check nested repetitions carefully.
</p>
@@ -861,7 +861,7 @@
the groupings at the end.
</p>
<p>Using ‘<samp>\(?: … \)</samp>’ rather than
‘<samp>\( … \)</samp>’ when you
-don't need the captured substrings ought to speed up your programs some,
+don’t need the captured substrings ought to speed up your programs some,
since it shortens the code path followed by the regular expression
engine, as well as the amount of memory allocation and string copying it
must do. The actual performance gain to be observed has not been
@@ -898,7 +898,7 @@
</dl>
<p> The following regular expression constructs match the empty
string—that is,
-they don't use up any characters—but whether they match depends on the
+they don’t use up any characters—but whether they match depends on
the
context.
</p>
<dl compact="compact">
@@ -1115,7 +1115,7 @@
can refer to all or part of what is matched by the <var>regexp</var>.
‘<samp>\&</samp>’
in <var>newstring</var> stands for the entire text being replaced.
‘<samp>\<var>d</var></samp>’ in <var>newstring</var>, where
<var>d</var> is a digit, stands for
-whatever matched the <var>d</var>'th parenthesized grouping in
<var>regexp</var>.
+whatever matched the <var>d</var>’th parenthesized grouping in
<var>regexp</var>.
For example,
</p>
<table><tr><td> </td><td><pre class="example">M-x replace-regexp
<RET> c[ad]+r <RET> \&-safe <RET>
Index: Tests/xemacs_frame_res/xemacs_16.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/xemacs_frame_res/xemacs_16.html,v
retrieving revision 1.22
retrieving revision 1.23
diff -u -b -r1.22 -r1.23
--- Tests/xemacs_frame_res/xemacs_16.html 5 Feb 2007 15:30:26 -0000
1.22
+++ Tests/xemacs_frame_res/xemacs_16.html 3 Oct 2007 09:34:54 -0000
1.23
@@ -129,7 +129,7 @@
<kbd>C-y</kbd> and <kbd>M-y</kbd> to retrieve. See section <a
href="xemacs_12.html#SEC91">Yanking</a>.
</p>
<p> <kbd>M-<DEL></kbd> is often useful even when you have typed only a
few
-characters wrong, if you know you are confused in your typing and aren't
+characters wrong, if you know you are confused in your typing and aren’t
sure exactly what you typed. At such a time, you cannot correct with
<DEL> except by looking at the screen to see what you did. It requires
less thought to kill the whole word and start over.
Index: Tests/xemacs_frame_res/xemacs_17.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/xemacs_frame_res/xemacs_17.html,v
retrieving revision 1.25
retrieving revision 1.26
diff -u -b -r1.25 -r1.26
--- Tests/xemacs_frame_res/xemacs_17.html 5 Feb 2007 15:30:26 -0000
1.25
+++ Tests/xemacs_frame_res/xemacs_17.html 3 Oct 2007 09:34:54 -0000
1.26
@@ -63,7 +63,7 @@
<p> The basic unit of stored data in Unix is the <em>file</em>. To edit a
file,
you must tell Emacs to examine the file and prepare a buffer containing a
-copy of the file's text. This is called <em>visiting</em> the file. Editing
+copy of the file’s text. This is called <em>visiting</em> the file.
Editing
commands apply directly to text in the buffer; that is, to the copy inside
Emacs. Your changes appear in the file itself only when you <em>save</em> the
buffer back into the file.
@@ -149,7 +149,7 @@
</p>
<p> In both cases the ‘<samp><var>user</var>@</samp>’ portion is
optional (it defaults
to your local user name). <var>path-on-remote-host</var> may use the
-‘<samp>~</samp>’ notation to indicate <var>user</var>'s home
directory on the remote
+‘<samp>~</samp>’ notation to indicate <var>user</var>’s home
directory on the remote
host. The default file name will reflect the remote host information.
</p>
<a name="IDX529"></a>
@@ -191,10 +191,10 @@
Removing a directory is similar to creating one. To remove a directory,
use <code>remove-directory</code>; it takes one argument, a file name string.
</p>
-<p> The command <kbd>M-x pwd</kbd> prints the current buffer's default
directory,
+<p> The command <kbd>M-x pwd</kbd> prints the current buffer’s default
directory,
and the command <kbd>M-x cd</kbd> sets it (to a value read using the
-minibuffer). A buffer's default directory changes only when the
<code>cd</code>
-command is used. A file-visiting buffer's default directory is initialized
+minibuffer). A buffer’s default directory changes only when the
<code>cd</code>
+command is used. A file-visiting buffer’s default directory is
initialized
to the directory of the file that is visited there. If a buffer is created
with <kbd>C-x b</kbd>, its default directory is copied from that of the
buffer that was current at the time.
@@ -258,11 +258,11 @@
(<code>find-alternate-file</code>).
</p></dd>
<dt> <kbd>C-x 4 C-f</kbd></dt>
-<dd><p>Visit a file, in another window (<code>find-file-other-window</code>).
Don't
+<dd><p>Visit a file, in another window (<code>find-file-other-window</code>).
Don’t
change this window.
</p></dd>
<dt> <kbd>C-x 5 C-f</kbd></dt>
-<dd><p>Visit a file, in another frame (<code>find-file-other-frame</code>).
Don't
+<dd><p>Visit a file, in another frame (<code>find-file-other-frame</code>).
Don’t
change this window or frame.
</p></dd>
</dl>
@@ -280,7 +280,7 @@
name is constructed by appending ‘<samp><2></samp>’,
‘<samp><3></samp>’,and so on, using
the lowest number that makes a name that is not already in use.
</p>
-<p> Each window's mode line shows the name of the buffer that is being
displayed
+<p> Each window’s mode line shows the name of the buffer that is being
displayed
in that window, so you can always tell what buffer you are editing.
</p>
<p> The changes you make with Emacs are made in the Emacs buffer. They do
@@ -331,8 +331,8 @@
</p>
<a name="IDX544"></a>
<a name="IDX545"></a>
-<p>If the variable <code>find-file-use-truenames</code>'s value is
-non-<code>nil</code>, a buffer's visited filename will always be traced back
+<p>If the variable <code>find-file-use-truenames</code>’s value is
+non-<code>nil</code>, a buffer’s visited filename will always be traced
back
to the real file. The filename will never be a symbolic link, and there
will never be a symbolic link anywhere in its directory path. In other
words, the <code>buffer-file-name</code> and <code>buffer-file-truename</code>
will
@@ -348,7 +348,7 @@
a symbolic link to a file that is already in a buffer, the existing
buffer will be found instead of a newly created one. This works if any
component of the pathname (including a non-terminal component) is a
-symbolic link as well, but doesn't work with hard links (nothing does).
+symbolic link as well, but doesn’t work with hard links (nothing does).
</p>
<a name="IDX548"></a>
<p> If you want to create a file, just visit it. Emacs prints
@@ -484,7 +484,7 @@
(<code>not-modified</code>), which removes the indication that the buffer
is modified. If you do this, none of the save commands will believe
that the buffer needs to be saved. (‘<samp>~</samp>’ is often
used as a
-mathematical symbol for `not'; thus <kbd>Meta-~</kbd> is `not', metafied.)
+mathematical symbol for ‘not’; thus <kbd>Meta-~</kbd> is
‘not’, metafied.)
You could also use <code>set-visited-file-name</code> (see below) to mark the
buffer as visiting a different file name, not in use for
anything important.
@@ -499,7 +499,7 @@
<p> <kbd>M-x set-visited-file-name</kbd> alters the name of the file that the
current buffer is visiting. It prompts you for the new file name in the
minibuffer. You can also use <code>set-visited-file-name</code> on a buffer
-that is not visiting a file. The buffer's name is changed to correspond
+that is not visiting a file. The buffer’s name is changed to correspond
to the file it is now visiting unless the new name is already used by a
different buffer; in that case, the buffer name is not changed.
<code>set-visited-file-name</code> does not save the buffer in the newly
@@ -516,7 +516,7 @@
same effect as <kbd>C-x C-w</kbd>; that is, it reads a file name, marks the
buffer as visiting that file, and saves it there. The default file name in
a buffer that is not visiting a file is made by combining the buffer name
-with the buffer's default directory.
+with the buffer’s default directory.
</p>
<p> If Emacs is about to save a file and sees that the date of the latest
version on disk does not match what Emacs last read or wrote, Emacs
@@ -526,7 +526,7 @@
</p>
<a name="IDX568"></a>
<p> If the variable <code>require-final-newline</code> is
non-<code>nil</code>, Emacs
-puts a newline at the end of any file that doesn't already end in one,
+puts a newline at the end of any file that doesn’t already end in one,
every time a file is saved or written.
</p>
<a name="IDX569"></a>
@@ -620,7 +620,7 @@
<h4 class="subsubsection"> 14.3.1.1 Single or Numbered Backups </h4>
<p> If you choose to have a single backup file (the default),
-the backup file's name is constructed by appending
‘<samp>~</samp>’ to the
+the backup file’s name is constructed by appending
‘<samp>~</samp>’ to the
file name being edited; thus, the backup file for
‘<tt>eval.c</tt>’ is
‘<tt>eval.c~</tt>’.
</p>
@@ -653,7 +653,7 @@
</dl>
<p><code>version-control</code> may be set locally in an individual buffer to
-control the making of backups for that buffer's file. For example,
+control the making of backups for that buffer’s file. For example,
Rmail mode locally sets <code>version-control</code> to <code>never</code> to
make sure
that there is only one backup for an Rmail file. See section <a
href="xemacs_30.html#SEC361">Local Variables</a>.
</p>
@@ -695,7 +695,7 @@
default, you are asked whether the excess middle versions should
really be deleted.
</p>
-<p> You can also use Dired's <kbd>.</kbd> (Period) command to delete old
versions.
+<p> You can also use Dired’s <kbd>.</kbd> (Period) command to delete
old versions.
See section <a href="#SEC163">Dired, the Directory Editor</a>.
</p>
<hr size="6">
@@ -726,9 +726,9 @@
the alternate names remain names for the file that you are editing,
and the contents accessed by those names will be the new contents.
</p>
-<p> How you make a backup file may also affect the file's owner
+<p> How you make a backup file may also affect the file’s owner
and group. If you use copying, they do not change. If renaming is used,
-you become the file's owner, and the file's group becomes the default
+you become the file’s owner, and the file’s group becomes the
default
(different operating systems have different defaults for the group).
</p>
<p> Having the owner change is usually a good idea, because then the owner
@@ -748,7 +748,7 @@
done for files that have multiple names, but renaming may still be done when
the file being edited has only one name. If the variable
<code>backup-by-copying-when-mismatch</code> is non-<code>nil</code>, copying
is
-done if renaming would cause the file's owner or group to change.
+done if renaming would cause the file’s owner or group to change.
</p>
<hr size="6">
<a name="Interlocking"></a>
@@ -779,7 +779,7 @@
warning. When this is not possible, or if the second user has started
to change the file despite the warning, Emacs checks when the file is
saved, and issues a second warning when a user is about to overwrite a
-file containing another user's changes. If you are the user editing the
+file containing another user’s changes. If you are the user editing the
file, you can take corrective action at this point and prevent actual
loss of work.
</p>
@@ -817,7 +817,7 @@
</p>
<p> Some systems are not configured to allow Emacs to make locks. On
these systems, Emacs cannot detect trouble in advance, but it can still
-detect it in time to prevent you from overwriting someone else's changes.
+detect it in time to prevent you from overwriting someone else’s changes.
</p>
<p> Every time Emacs saves a buffer, it first checks the last-modification
date of the existing file on disk to see that it has not changed since the
@@ -831,7 +831,7 @@
</p>
<p> The first thing you should do when notified that simultaneous editing
has already taken place is to list the directory with <kbd>C-u C-x C-d</kbd>
-(see section <a href="#SEC161">Directory Listing</a>). This will show the
file's current
+(see section <a href="#SEC161">Directory Listing</a>). This will show the
file’s current
author. You should attempt to contact that person and ask him not to
continue editing. Often the next step is to save the contents of your
Emacs buffer under a different name, and use <code>diff</code> to compare the
@@ -899,7 +899,7 @@
reversion.
</p>
<p>A buffer reverted from its visited file is marked “not
modified” until
-you make a change. The buffer's modes will also be recalculated, by
+you make a change. The buffer’s modes will also be recalculated, by
<code>normal-mode</code>.
</p>
<p> Some kinds of buffers whose contents reflect data bases other than files,
@@ -999,7 +999,7 @@
there is really no difference between auto-saving and explicit saving.
</p>
<a name="IDX580"></a>
-<p> Emacs deletes a buffer's auto-save file when you explicitly save the
+<p> Emacs deletes a buffer’s auto-save file when you explicitly save the
buffer. To inhibit the deletion, set the variable
<code>delete-auto-save-files</code> to <code>nil</code>. Changing the visited
file
name with <kbd>C-x C-w</kbd> or <code>set-visited-file-name</code> renames any
@@ -1026,7 +1026,7 @@
</tr></table>
<h3 class="subsection"> 14.5.2 Controlling Auto-Saving </h3>
-<p> Each time you visit a file, auto-saving is turned on for that file's
+<p> Each time you visit a file, auto-saving is turned on for that file’s
buffer if the variable <code>auto-save-default</code> is non-<code>nil</code>
(but
not in batch mode; see section <a href="xemacs_6.html#SEC39">Entering and
Exiting Emacs</a>). The default for this
variable is <code>t</code>, so Emacs auto-saves buffers that visit files by
@@ -1194,7 +1194,7 @@
<p> When a file is under version control, we also say that it is
<em>registered</em> in the version control system. Each registered file
-has a corresponding <em>master file</em> which represents the file's
+has a corresponding <em>master file</em> which represents the file’s
present state plus its change history, so that you can reconstruct from
it either the current version or any specified earlier version. Usually
the master file also records a <em>log entry</em> for each version describing
@@ -1323,10 +1323,10 @@
This cancels your last check-out, leaving the file unlocked. If you want
to make a different set of changes, you must first check the file out
again. <kbd>C-x v u</kbd> requires confirmation, unless it sees that
-you haven't made any changes since the last checked-in version.
+you haven’t made any changes since the last checked-in version.
</p>
<p> <kbd>C-x v u</kbd> is also the command to use if you lock a file and then
-don't actually change it.
+don’t actually change it.
</p>
<a name="IDX593"></a>
<a name="IDX594"></a>
@@ -1424,7 +1424,7 @@
</p>
<p> If you find that the file permissions of work files are changed
erroneously, set <code>vc-mistrust-permissions</code> to <code>t</code>. Then
VC
-always checks the master file to determine the file's status.
+always checks the master file to determine the file’s status.
</p>
<a name="IDX603"></a>
<p> You can specify additional directories to search for version control
@@ -1453,7 +1453,7 @@
</tr></table>
<h3 class="subsection"> 14.6.4 Log Entries </h3>
-<p> When you're editing an initial comment or log entry for inclusion in a
+<p> When you’re editing an initial comment or log entry for inclusion
in a
master file, finish your entry by typing <kbd>C-c C-c</kbd>.
</p>
<dl compact="compact">
@@ -1463,8 +1463,8 @@
</p></dd>
</dl>
-<p> To abort check-in, just don't type <kbd>C-c C-c</kbd> in that buffer. You
-can switch buffers and do other editing. As long as you don't try to
+<p> To abort check-in, just don’t type <kbd>C-c C-c</kbd> in that
buffer. You
+can switch buffers and do other editing. As long as you don’t try to
check in another file, the entry you were editing remains in its
buffer, and you can go back to that buffer at any time to complete the
check-in.
@@ -1510,7 +1510,7 @@
<dt> <kbd>C-x v a</kbd></dt>
<dd><a name="IDX605"></a>
<a name="IDX606"></a>
-<p>Visit the current directory's change log file and create new entries for
+<p>Visit the current directory’s change log file and create new entries
for
versions checked in since the most recent entry in the change log file
(<code>vc-update-change-log</code>).
</p>
@@ -1695,7 +1695,7 @@
</p>
<a name="IDX611"></a>
<a name="IDX612"></a>
-<p> When you are working on a large program, it's often useful to find all
+<p> When you are working on a large program, it’s often useful to find
all
the files that are currently locked, or all the files maintained in
version control at all. You can use <kbd>C-x v d</kbd>
(<code>vc-directory</code>)
to show all the locked files in or beneath the current directory. This
@@ -1860,8 +1860,8 @@
</tr></table>
<h4 class="subsubsection"> 14.6.9.2 Snapshot Caveats </h4>
-<p> VC's snapshot facilities are modeled on RCS's named-configuration
-support. They use RCS's native facilities for this, so under VC
+<p> VC’s snapshot facilities are modeled on RCS’s
named-configuration
+support. They use RCS’s native facilities for this, so under VC
snapshots made using RCS are visible even when you bypass VC.
</p>
<p> For SCCS, VC implements snapshots itself. The files it uses contain
@@ -1890,7 +1890,7 @@
least, the makefile probably mentions the file that you renamed. If you
retrieve an old snapshot, the renamed file is retrieved under its new
name, which is not the name that the makefile expects. So the program
-won't really work as retrieved.
+won’t really work as retrieved.
</p>
<hr size="6">
<a name="Version-Headers"></a>
@@ -1933,7 +1933,7 @@
<p> The default header string is ‘<samp>\$Id\$</samp>’ for RCS
and ‘<samp>\%W\%</samp>’
for SCCS. (The actual strings inserted do not have the backslashes
in them. They were placed in the Info source file so that the
-strings don't get interpreted as version-control headers when the
+strings don’t get interpreted as version-control headers when the
Info source files are maintained under version control.) You can
specify other headers to insert by setting the variable
<code>vc-header-alist</code>. Its value is a list of elements of the form
@@ -2050,7 +2050,7 @@
<code>(FROM . TO)</code>, each meaning to replace <code>FROM</code> with
<code>TO</code>
when it appears in a directory name. This replacement is done when
setting up the default directory of a newly visited file. Every
<code>FROM</code>
-string should start with `‘<samp>^</samp>’'.
+string should start with ‘‘<samp>^</samp>’’.
</p>
<p>Use this feature when you have directories which you normally refer to
via absolute symbolic links. Make <code>TO</code> the name of the link, and
@@ -2213,7 +2213,7 @@
that point is on. Some commands perform operations immediately; others
“flag” a file to be operated on later.
</p>
-<p> Most Dired commands that operate on the current line's file also treat a
+<p> Most Dired commands that operate on the current line’s file also
treat a
numeric argument as a repeat count, meaning to act on the files of the
next few lines. A negative argument means to operate on the files of the
preceding lines, and leave point on the first of those lines.
@@ -2365,7 +2365,7 @@
subdirectory. See section <a href="#SEC136">Visiting Files</a>.
</p></dd>
<dt> <kbd>o</kbd></dt>
-<dd><p>Like <kbd>f</kbd>, but uses another window to display the file's
buffer. The
+<dd><p>Like <kbd>f</kbd>, but uses another window to display the file’s
buffer. The
Dired buffer remains visible in the first window. This is like using
<kbd>C-x 4 C-f</kbd> to visit the file. See section <a
href="xemacs_19.html#SEC175">Multiple Windows</a>.
</p></dd>
Index: Tests/xemacs_frame_res/xemacs_18.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/xemacs_frame_res/xemacs_18.html,v
retrieving revision 1.22
retrieving revision 1.23
diff -u -b -r1.22 -r1.23
--- Tests/xemacs_frame_res/xemacs_18.html 5 Feb 2007 15:30:26 -0000
1.22
+++ Tests/xemacs_frame_res/xemacs_18.html 3 Oct 2007 09:34:54 -0000
1.23
@@ -63,10 +63,10 @@
<p> Text you are editing in Emacs resides in an object called a
<em>buffer</em>. Each time you visit a file, Emacs creates a buffer to
-hold the file's text. Each time you invoke Dired, Emacs creates a buffer
+hold the file’s text. Each time you invoke Dired, Emacs creates a buffer
to hold the directory listing. If you send a message with <kbd>C-x m</kbd>,
a buffer named ‘<samp>*mail*</samp>’ is used to hold the text of
the message.
-When you ask for a command's documentation, it appears in a buffer
+When you ask for a command’s documentation, it appears in a buffer
called ‘<samp>*Help*</samp>’.
</p>
<a name="IDX644"></a>
@@ -78,13 +78,13 @@
</p>
<p> When Emacs creates multiple windows, each window has a chosen buffer which
is displayed there, but at any time only one of the windows is selected and
-its chosen buffer is the selected buffer. Each window's mode line displays
+its chosen buffer is the selected buffer. Each window’s mode line
displays
the name of the buffer the window is displaying (see section <a
href="xemacs_19.html#SEC175">Multiple Windows</a>).
</p>
<p> Each buffer has a name which can be of any length but is
case-sensitive. You can select a buffer using its name. Most
buffers are created when you visit files; their names are derived from
-the files' names. You can also create an empty buffer with any name you
+the files’ names. You can also create an empty buffer with any name you
want. A newly started Emacs has a buffer named
‘<samp>*scratch*</samp>’ which
you can use for evaluating Lisp expressions in Emacs.
</p>
@@ -159,7 +159,7 @@
that display text. You can also create a buffer explicitly by typing
<kbd>C-x b <var>bufname</var> <RET></kbd>, which creates a new, empty
buffer
that is not visiting any file, and selects it for editing. The new
-buffer's major mode is determined by the value of
+buffer’s major mode is determined by the value of
<code>default-major-mode</code> (see section <a
href="xemacs_21.html#SEC190">Major Modes</a>). Buffers not visiting
files are usually used for making notes to yourself. If you try to save
one, you are asked for the file name to use.
@@ -207,7 +207,7 @@
<a name="IDX653"></a>
<a name="IDX654"></a>
<p> To print a list of all existing buffers, type <kbd>C-x C-b</kbd>. Each
-line in the list shows one buffer's name, major mode, and visited file.
+line in the list shows one buffer’s name, major mode, and visited file.
A ‘<samp>*</samp>’ at the beginning of a line indicates the buffer
has been
“modified”. If several buffers are modified, it may be time to
save
some with <kbd>C-x s</kbd> (see section <a href="xemacs_17.html#SEC137">Saving
Files</a>). A ‘<samp>%</samp>’ indicates a read-only
Index: Tests/xemacs_frame_res/xemacs_19.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/xemacs_frame_res/xemacs_19.html,v
retrieving revision 1.21
retrieving revision 1.22
diff -u -b -r1.21 -r1.22
--- Tests/xemacs_frame_res/xemacs_19.html 5 Feb 2007 15:30:26 -0000
1.21
+++ Tests/xemacs_frame_res/xemacs_19.html 3 Oct 2007 09:34:54 -0000
1.22
@@ -229,7 +229,7 @@
<dl compact="compact">
<dt> <kbd>C-x o</kbd></dt>
-<dd><p>Select another window (<code>other-window</code>). That is the letter
`o', not zero.
+<dd><p>Select another window (<code>other-window</code>). That is the letter
‘o’, not zero.
</p></dd>
<dt> <kbd>M-C-v</kbd></dt>
<dd><p>Scroll the next window (<code>scroll-other-window</code>).
@@ -246,7 +246,7 @@
<a name="IDX673"></a>
<a name="IDX674"></a>
<p> To select a different window, use <kbd>C-x o</kbd>
(<code>other-window</code>).
-That is an `o', for `other', not a zero. When there are more than
+That is an ‘o’, for ‘other’, not a zero. When there
are more than
two windows, the command moves through all the windows in a cyclic
order, generally top to bottom and left to right. From the rightmost
and bottommost window, it goes back to the one at the upper left corner.
Index: Tests/xemacs_frame_res/xemacs_2.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/xemacs_frame_res/xemacs_2.html,v
retrieving revision 1.17
retrieving revision 1.18
diff -u -b -r1.17 -r1.18
--- Tests/xemacs_frame_res/xemacs_2.html 5 Feb 2007 15:30:26 -0000
1.17
+++ Tests/xemacs_frame_res/xemacs_2.html 3 Oct 2007 09:34:54 -0000
1.18
@@ -102,7 +102,7 @@
</tr></table>
<h2 class="unnumberedsec"> Getting Other Versions of Emacs </h2>
-<p>The Free Software Foundation's version of Emacs (called <em>FSF Emacs</em>
+<p>The Free Software Foundation’s version of Emacs (called <em>FSF
Emacs</em>
in this manual and often referred to as <em>GNU Emacs</em>) is available
by anonymous FTP from ‘<tt>prep.ai.mit.edu</tt>’.
</p>
Index: Tests/xemacs_frame_res/xemacs_20.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/xemacs_frame_res/xemacs_20.html,v
retrieving revision 1.27
retrieving revision 1.28
diff -u -b -r1.27 -r1.28
--- Tests/xemacs_frame_res/xemacs_20.html 5 Feb 2007 15:30:26 -0000
1.27
+++ Tests/xemacs_frame_res/xemacs_20.html 3 Oct 2007 09:34:54 -0000
1.28
@@ -128,7 +128,7 @@
languages (French, Spanish, German) require more than 96 code positions
for accented characters. In fact, even with 8 bits to represent 96 more
character (including accented characters and symbols such as currency
-symbols), some languages' alphabets remain incomplete (Croatian,
+symbols), some languages’ alphabets remain incomplete (Croatian,
Polish). (The 64 "missing characters" are reserved for control
characters.) Furthermore, many European languages have their own
alphabets, which must conflict with the accented characters since the
@@ -141,12 +141,12 @@
character. However, many Asian languages have thousands of characters
and require two or more octets per character. For multilingual
purposes, the ISO 2022 standard establishes escape codes that allow
-switching encodings in midstream. (It's also ISO 2022 that establishes
+switching encodings in midstream. (It’s also ISO 2022 that establishes
the standard that code points 0-31 and 128-159 are control codes.)
</p>
<p>However, this is error-prone and complex for internal processing. For
this reason XEmacs uses an internal coding system which can encode all
-of the world's scripts. Unfortunately, for historical reasons, this
+of the world’s scripts. Unfortunately, for historical reasons, this
code is not Unicode, although we are moving in that direction.
</p>
<p>XEmacs translates between the internal character encoding and various
@@ -159,7 +159,7 @@
European use prior to the introduction of the Euro currency), 1-octet
ISO-8859-15 (which substitutes the Euro for the rarely used "generic
currency" symbol), 1-octet ISO-8859-5 (Cyrillic), or multioctet EUC-JP
-(Japanese). There's no way to tell without being able to read!
+(Japanese). There’s no way to tell without being able to read!
</p>
<p>A number of heuristics are incorporated in Mule for automatic
recognition, there are facilities for the user to set defaults, and
@@ -172,7 +172,7 @@
This illustrates various scripts.
</p>
<p> Keyboards, even in the countries where these character sets are used,
-generally don't have keys for all the characters in them. So XEmacs
+generally don’t have keys for all the characters in them. So XEmacs
supports various <em>input methods</em>, typically one for each script or
language, to make it convenient to type them.
</p>
@@ -313,7 +313,7 @@
<p> One way is to type the accent twice; that is a special feature for
entering the separate letter and accent. For example, <kbd>e ' '</kbd> gives
you the two characters ‘<samp>e'</samp>’. Another way is to type
another letter
-after the <kbd>e</kbd>—something that won't combine with that—and
+after the <kbd>e</kbd>—something that won’t combine with
that—and
immediately delete it. For example, you could type <kbd>e e <DEL>
'</kbd> to get separate ‘<samp>e</samp>’ and
‘<samp>'</samp>’.
</p>
@@ -480,7 +480,7 @@
text in buffer. Returning to the above example, we need to somehow tell
XEmacs that we have different encodings of fonts and text and so it
needs to convert characters between those encodings when displaying.
-That's what ‘<samp>set-charset-ccl-program</samp>’ function is
used for. There
+That’s what ‘<samp>set-charset-ccl-program</samp>’ function
is used for. There
are quite a few various CCL programs defined within XEmacs, and there is
no comprehensive list of them, so you currently have to consult sources.
</p>
@@ -582,7 +582,7 @@
</p>
<dl compact="compact">
<dt> <code>…-unix</code></dt>
-<dd><p>Don't do any end-of-line conversion; assume the file uses
+<dd><p>Don’t do any end-of-line conversion; assume the file uses
newline to separate lines. (This is the convention normally used
on Unix and GNU systems.)
</p>
Index: Tests/xemacs_frame_res/xemacs_21.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/xemacs_frame_res/xemacs_21.html,v
retrieving revision 1.19
retrieving revision 1.20
diff -u -b -r1.19 -r1.20
--- Tests/xemacs_frame_res/xemacs_21.html 5 Feb 2007 15:30:27 -0000
1.19
+++ Tests/xemacs_frame_res/xemacs_21.html 3 Oct 2007 09:34:55 -0000
1.20
@@ -85,7 +85,7 @@
several variants), C mode, and Muddle mode are for specific programming
languages. Text mode, Nroff mode, TeX mode, and Outline mode are for
editing English text. The remaining major modes are not intended for use
-on users' files; they are used in buffers created by Emacs for specific
+on users’ files; they are used in buffers created by Emacs for specific
purposes and include Dired mode for buffers made by Dired (see section <a
href="xemacs_17.html#SEC163">Dired, the Directory Editor</a>),
Mail mode for buffers made by <kbd>C-x m</kbd> (see section <a
href="xemacs_28.html#SEC296">Sending Mail</a>), and Shell
mode for buffers used for communicating with an inferior shell process
@@ -134,7 +134,7 @@
</p>
<a name="IDX736"></a>
<p> When you visit a file, Emacs usually chooses the right major mode
-based on the file's name. For example, files whose names end in
+based on the file’s name. For example, files whose names end in
<code>.c</code> are edited in C mode. The variable
<code>auto-mode-alist</code>
controls the correspondence between file names and major mode. Its value
is a list in which each element has the form:
Index: Tests/xemacs_frame_res/xemacs_22.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/xemacs_frame_res/xemacs_22.html,v
retrieving revision 1.23
retrieving revision 1.24
diff -u -b -r1.23 -r1.24
--- Tests/xemacs_frame_res/xemacs_22.html 5 Feb 2007 15:30:27 -0000
1.23
+++ Tests/xemacs_frame_res/xemacs_22.html 3 Oct 2007 09:34:55 -0000
1.24
@@ -228,7 +228,7 @@
</tr></table>
<h2 class="section"> 19.2 Tab Stops </h2>
-<p> For typing in tables, you can use Text mode's definition of <TAB>,
+<p> For typing in tables, you can use Text mode’s definition of
<TAB>,
<code>tab-to-tab-stop</code>. This command inserts indentation before point,
enough to reach the next tab stop column. Even if you are not in Text mode,
this function is associated with <kbd>M-i</kbd> anyway.
Index: Tests/xemacs_frame_res/xemacs_23.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/xemacs_frame_res/xemacs_23.html,v
retrieving revision 1.24
retrieving revision 1.25
diff -u -b -r1.24 -r1.25
--- Tests/xemacs_frame_res/xemacs_23.html 5 Feb 2007 15:30:27 -0000
1.24
+++ Tests/xemacs_frame_res/xemacs_23.html 3 Oct 2007 09:34:55 -0000
1.25
@@ -211,7 +211,7 @@
<a name="IDX767"></a>
<dl compact="compact">
<dt> <kbd>M-n</kbd></dt>
-<dd><p>Move to the beginning of the next line that isn't an nroff command
+<dd><p>Move to the beginning of the next line that isn’t an nroff command
(<code>forward-text-line</code>). An argument is a repeat count.
</p></dd>
<dt> <kbd>M-p</kbd></dt>
@@ -274,7 +274,7 @@
modes are designed for editing the two different input formats. The
command <kbd>M-x tex-mode</kbd> looks at the contents of a buffer to
determine whether it appears to be LaTeX input or not; it then
-selects the appropriate mode. If it can't tell which is right (e.g.,
+selects the appropriate mode. If it can’t tell which is right (e.g.,
the buffer is empty), the variable <code>tex-default-mode</code> controls
which mode is used.
</p>
@@ -447,7 +447,7 @@
</p>
<dl compact="compact">
<dt> <kbd>C-c C-r</kbd></dt>
-<dd><p>Invoke TeX on the current region, plus the buffer's header
+<dd><p>Invoke TeX on the current region, plus the buffer’s header
(<code>tex-region</code>).
</p></dd>
<dt> <kbd>C-c C-b</kbd></dt>
@@ -517,7 +517,7 @@
</p>
<p> In LaTeX mode, the header begins with
‘<samp>\documentstyle</samp>’ and ends
with <br>‘<samp>\begin{document}</samp>’. These are commands that
LaTeX requires
-you to use, so you don't need to do anything special to identify the
+you to use, so you don’t need to do anything special to identify the
header.
</p>
<a name="IDX794"></a>
@@ -790,10 +790,10 @@
visible (<code>show-children</code>).
</p></dd>
<dt> <kbd>M-x hide-entry</kbd></dt>
-<dd><p>Make this heading line's body invisible.
+<dd><p>Make this heading line’s body invisible.
</p></dd>
<dt> <kbd>M-x show-entry</kbd></dt>
-<dd><p>Make this heading line's body visible.
+<dd><p>Make this heading line’s body visible.
</p></dd>
</dl>
@@ -811,7 +811,7 @@
<a name="IDX815"></a>
<p> Two more powerful opposites are <kbd>C-c C-d</kbd>
(<code>hide-subtree</code>) and
<kbd>C-c C-s</kbd> (<code>show-subtree</code>). Both should be used when
point is
-on a heading line, and both apply to all the lines of that heading's
+on a heading line, and both apply to all the lines of that heading’s
<em>subtree</em>: its body, all its subheadings, both direct and indirect, and
all of their bodies. In other words, the subtree contains everything
following this heading line, up to and not including the next heading of
@@ -947,7 +947,7 @@
to. It can be given arguments just like <kbd>Meta-f</kbd>.
</p>
<a name="IDX836"></a>
-<p> The word commands' understanding of syntax is completely controlled by
+<p> The word commands’ understanding of syntax is completely controlled
by
the syntax table. For example, any character can be declared to be a word
delimiter. See section <a href="xemacs_30.html#SEC374">The Syntax Table</a>.
</p>
@@ -1000,7 +1000,7 @@
<kbd>Control-e</kbd>, which move to the beginning and end of a line. Unlike
their counterparts, <kbd>Meta-a</kbd> and <kbd>Meta-e</kbd> move over
successive
sentences if repeated or given numeric arguments. Emacs assumes
-the typist's convention is followed, and thus considers a sentence to
+the typist’s convention is followed, and thus considers a sentence to
end wherever there is a ‘<samp>.</samp>’,
‘<samp>?</samp>’, or ‘<samp>!</samp>’ followed by the
end of a line or two spaces, with any number of ‘<samp>)</samp>’,
‘<samp>]</samp>’,
‘<samp>'</samp>’, or ‘<samp>"</samp>’ characters
allowed in between. A sentence also
@@ -1081,7 +1081,7 @@
be useful even though there are no paragraphs per se.
</p>
<p> When there is a fill prefix, paragraphs are delimited by all lines
-which don't start with the fill prefix. See section <a href="#SEC210">Filling
Text</a>.
+which don’t start with the fill prefix. See section <a
href="#SEC210">Filling Text</a>.
</p>
<a name="IDX846"></a>
<a name="IDX847"></a>
@@ -1437,7 +1437,7 @@
<a name="IDX874"></a>
<p> To specify a fill prefix, move to a line that starts with the desired
prefix, put point at the end of the prefix, and give the command
-<kbd>C-x .</kbd> (<code>set-fill-prefix</code>). That's a period after the
+<kbd>C-x .</kbd> (<code>set-fill-prefix</code>). That’s a period after
the
<kbd>C-x</kbd>. To turn off the fill prefix, specify an empty prefix: type
<kbd>C-x .</kbd> with point at the beginning of a line.
</p>
Index: Tests/xemacs_frame_res/xemacs_24.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/xemacs_frame_res/xemacs_24.html,v
retrieving revision 1.27
retrieving revision 1.28
diff -u -b -r1.27 -r1.28
--- Tests/xemacs_frame_res/xemacs_24.html 5 Feb 2007 15:30:27 -0000
1.27
+++ Tests/xemacs_frame_res/xemacs_24.html 3 Oct 2007 09:34:55 -0000
1.28
@@ -159,7 +159,7 @@
</p>
<p> Each of the programming language modes defines the <TAB> key to run
an indentation function that knows the indentation conventions of that
-language and updates the current line's indentation accordingly. For
+language and updates the current line’s indentation accordingly. For
example, in C mode <TAB> is bound to <code>c-indent-line</code>.
<LFD>
is normally defined to do <RET> followed by <TAB>; thus it, too,
indents in a mode-specific fashion.
@@ -232,9 +232,9 @@
language you are working with), and escape characters that might be used
to quote those.
</p>
-<p> The other commands deal with expressions or <em>sexps</em>. The word
`sexp'
+<p> The other commands deal with expressions or <em>sexps</em>. The word
‘sexp’
is derived from <em>s-expression</em>, the term for a symbolic expression in
-Lisp. In Emacs, the notion of `sexp' is not limited to Lisp. It
+Lisp. In Emacs, the notion of ‘sexp’ is not limited to Lisp. It
refers to an expression in the language your program is written in.
Each programming language has its own major mode, which customizes the
syntax tables so that expressions in that language count as sexps.
@@ -365,7 +365,7 @@
<kbd>C-M-f</kbd>. In particular, a negative argument is useful for putting
the mark at the beginning of the previous sexp.
</p>
-<p> The list and sexp commands' understanding of syntax is completely
+<p> The list and sexp commands’ understanding of syntax is completely
controlled by the syntax table. Any character can, for example, be
declared to be an opening delimiter and act like an open parenthesis.
See section <a href="xemacs_30.html#SEC374">The Syntax Table</a>.
@@ -546,7 +546,7 @@
</p>
<p> <TAB> indents the second and following lines of the body of a
parenthetical grouping each under the preceding one; therefore, if you
-alter one line's indentation to be nonstandard, the lines below tend
+alter one line’s indentation to be nonstandard, the lines below tend
to follow it. This is the right behavior in cases where the standard
result of <TAB> does not look good.
</p>
@@ -750,7 +750,7 @@
<a name="IDX941"></a>
<p> If <code>c-tab-always-indent</code> is non-<code>nil</code>, the
<TAB> command
in C mode does indentation only if point is at the left margin or within
-the line's indentation. If there is non-whitespace to the left of point,
+the line’s indentation. If there is non-whitespace to the left of point,
<TAB> just inserts a tab character in the buffer. Normally,
this variable is <code>nil</code>, and <TAB> always reindents the
current line.
</p>
@@ -765,7 +765,7 @@
<dl compact="compact">
<dt> <code>c-indent-level</code></dt>
<dd><p>Indentation of C statements within surrounding block. The surrounding
-block's indentation is the indentation of the line on which the
+block’s indentation is the indentation of the line on which the
open-brace appears.
</p></dd>
<dt> <code>c-continued-statement-offset</code></dt>
@@ -825,7 +825,7 @@
<p> When <code>c-indent-level</code> is zero, the statements inside most
braces
line up exactly under the open brace. An exception are braces in column
-zero, like those surrounding a function's body. The statements inside
+zero, like those surrounding a function’s body. The statements inside
those braces are not placed at column zero. Instead,
<code>c-brace-offset</code> and <code>c-continued-statement-offset</code> (see
below) are added to produce a typical offset between brace levels, and
@@ -1098,7 +1098,7 @@
(<code>set-comment-column</code>) sets the comment column to the column point
is
at. <kbd>C-u C-x ;</kbd> sets the comment column to match the last comment
before point in the buffer, and then calls <kbd>Meta-;</kbd> to align the
-current line's comment under the previous one. Note that <kbd>C-u - C-x
;</kbd>
+current line’s comment under the previous one. Note that <kbd>C-u - C-x
;</kbd>
runs the function <code>kill-comment</code> as described above.
</p>
<p> <code>comment-column</code> is a per-buffer variable; altering the
variable
@@ -1311,7 +1311,7 @@
change log starts with a tab. One entry can describe several changes;
each change starts with a line starting with a tab and a star. <kbd>M-x
add-change-log-entry</kbd> visits the change log file and creates a new entry
-unless the most recent entry is for today's date and your name. In
+unless the most recent entry is for today’s date and your name. In
either case, it adds a new line to start the description of another
change just after the header line of the entry. When <kbd>M-x
add-change-log-entry</kbd> is finished, all is prepared for you to edit in
@@ -1382,7 +1382,7 @@
</p>
<p> Each entry in the tags table records the name of one tag, the name of the
file that the tag is defined in (implicitly), and the position in that file
-of the tag's definition.
+of the tag’s definition.
</p>
<p> Just what names from the described files are recorded in the tags table
depends on the programming language of the described file. They
@@ -1395,7 +1395,7 @@
<a name="IDX966"></a>
<a name="IDX967"></a>
<p>The Ebrowse is a separate facility tailored for C++, with tags and a
-class browser. See <a href="../ebrowse/index.html#Top">(ebrowse)Top</a>
section `Top' in <cite>Ebrowse User's Manual</cite>.
+class browser. See <a href="../ebrowse/index.html#Top">(ebrowse)Top</a>
section ‘Top’ in <cite>Ebrowse User’s Manual</cite>.
</p>
<table class="menu" border="0" cellspacing="0">
<tr><td align="left" valign="top"><a href="#SEC233">21.11.1 Source File Tag
Syntax</a></td><td> </td><td align="left" valign="top"> Tag
syntax for various types of code and text files.
@@ -1809,7 +1809,7 @@
</pre></td></tr></table>
<p>Note that tags are not generated for scripts so that you have to add a
-line by yourself of the form `###key <script-name>' if you want to jump
+line by yourself of the form ‘###key <script-name>’ if you
want to jump
to it.
</p>
</li><li>
@@ -1993,7 +1993,7 @@
that the specified substring appears in. To find other tags that match
the substring, give <code>find-tag</code> a numeric argument, as in <kbd>C-u
M-.</kbd>. This does not read a tag name, but continues searching the tag
-table's text for another tag containing the same substring last used.
+table’s text for another tag containing the same substring last used.
If your keyboard has a real <META> key, <kbd>M-0 M-.</kbd> is an easier
alternative to <kbd>C-u M-.</kbd>.
</p>
Index: Tests/xemacs_frame_res/xemacs_25.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/xemacs_frame_res/xemacs_25.html,v
retrieving revision 1.30
retrieving revision 1.31
diff -u -b -r1.30 -r1.31
--- Tests/xemacs_frame_res/xemacs_25.html 5 Feb 2007 15:30:27 -0000
1.30
+++ Tests/xemacs_frame_res/xemacs_25.html 3 Oct 2007 09:34:55 -0000
1.31
@@ -134,7 +134,7 @@
<p> To run <code>make</code> or another compiler, type <kbd>M-x
compile</kbd>. This
command reads a shell command line using the minibuffer, then executes
the specified command line in an inferior shell with output going to the
-buffer named ‘<samp>*compilation*</samp>’. By default, the
current buffer's
+buffer named ‘<samp>*compilation*</samp>’. By default, the
current buffer’s
default directory is used as the working directory for the execution of
the command; therefore, the makefile comes from this directory.
</p>
@@ -192,7 +192,7 @@
lines on which matches were found. To do this, type <kbd>M-x grep</kbd> with
an argument line that contains the same arguments you would give to
<code>grep</code>: a <code>grep</code>-style regexp (usually in single quotes
to
-quote the shell's special characters) followed by filenames, which may
+quote the shell’s special characters) followed by filenames, which may
use wildcard characters. The output from <code>grep</code> goes in the
‘<samp>*compilation*</samp>’ buffer. You can use <kbd>C-x `</kbd>
to find the lines that
match as if they were compilation errors.
@@ -201,10 +201,10 @@
run in interactive mode. In particular, this means that the shell starts
up with no prompt. If you find your usual shell prompt making an
unsightly appearance in the ‘<samp>*compilation*</samp>’ buffer,
it means you
-have made a mistake in your shell's initialization file
(‘<tt>.cshrc</tt>’
+have made a mistake in your shell’s initialization file
(‘<tt>.cshrc</tt>’
or ‘<tt>.shrc</tt>’ or …) by setting the prompt
unconditionally. The
shell initialization file should set the prompt only if there already is
-a prompt. Here's how to do it in <code>csh</code>:
+a prompt. Here’s how to do it in <code>csh</code>:
</p>
<table><tr><td> </td><td><pre class="example">if ($?prompt) set prompt =
...
</pre></td></tr></table>
@@ -374,7 +374,7 @@
<p>The variable is initialized by the <b>EMACSLOADPATH</b> environment
variable. If no value is specified, the variable takes the default value
specified in the file ‘<tt>paths.h</tt>’ when Emacs was built. If
a path
-isn't specified in ‘<tt>paths.h</tt>’, a default value is obtained
from the
+isn’t specified in ‘<tt>paths.h</tt>’, a default value is
obtained from the
file system, near the directory in which the Emacs executable resides.
</p>
<a name="IDX1030"></a>
@@ -536,7 +536,7 @@
</p>
<p> You cannot currently byte-compile converted Mocklisp code.
The reason is that converted Mocklisp code uses some special Lisp features
-to deal with Mocklisp's incompatible ideas of how arguments are evaluated
+to deal with Mocklisp’s incompatible ideas of how arguments are evaluated
and which values signify “true” or “false”.
</p>
<hr size="6">
@@ -696,7 +696,7 @@
you can switch buffers, visit files, and perform any other editing
operations. However, the debugger is a recursive editing level
(see section <a href="xemacs_29.html#SEC346">Recursive Editing Levels</a>); it
is a good idea to return to the backtrace
-buffer and explicitly exit the debugger when you don't want to use it any
+buffer and explicitly exit the debugger when you don’t want to use it any
more. Exiting the debugger kills the backtrace buffer.
</p>
<a name="IDX1051"></a>
@@ -733,7 +733,7 @@
that invoke the debugger on exit are flagged with stars.
</p></dd>
<dt> <kbd>u</kbd></dt>
-<dd><p>Don't enter the debugger when the current frame is exited. This
+<dd><p>Don’t enter the debugger when the current frame is exited. This
cancels a <kbd>b</kbd> command on a frame.
</p></dd>
<dt> <kbd>e</kbd></dt>
@@ -756,12 +756,12 @@
then the value specified in the <kbd>r</kbd> command is used as the value of
that frame.
</p>
-<p>The debugger's return value also matters with many errors. For example,
-<code>wrong-type-argument</code> errors will use the debugger's return value
+<p>The debugger’s return value also matters with many errors. For
example,
+<code>wrong-type-argument</code> errors will use the debugger’s return
value
instead of the invalid argument; <code>no-catch</code> errors will use the
debugger value as a throw tag instead of the tag that was not found.
If an error was signaled by calling the Lisp function <code>signal</code>,
-the debugger's return value is returned as the value of <code>signal</code>.
+the debugger’s return value is returned as the value of
<code>signal</code>.
</p></dd>
</dl>
@@ -790,7 +790,7 @@
provided for evaluating Lisp expressions interactively inside Emacs. Both
the expressions you evaluate and their output goes in the buffer.
</p>
-<p> The ‘<samp>*scratch*</samp>’ buffer's major mode is Lisp
Interaction mode, which
+<p> The ‘<samp>*scratch*</samp>’ buffer’s major mode is
Lisp Interaction mode, which
is the same as Emacs-Lisp mode except for one command, <LFD>. In
Emacs-Lisp mode, <LFD> is an indentation command. In Lisp
Interaction mode, <LFD> is bound to <code>eval-print-last-sexp</code>.
This
@@ -953,7 +953,7 @@
related but otherwise independent lisp files. These files are bundled
together for download convenience and individual files may be deleted at
will without any loss of functionality. However, we would recommend
-that you follow this rule of thumb: "When in doubt, don't delete".
+that you follow this rule of thumb: "When in doubt, don’t
delete".
</li></ul>
<hr size="6">
@@ -1022,7 +1022,7 @@
<td valign="middle" align="left">[<a href="xemacs_abt.html#SEC_About"
title="About (help)"> ? </a>]</td>
</tr></table>
<h3 class="subsection"> 22.8.4 Source Packages </h3>
-<p>Source packages contain all of the Package author's (where appropriate
+<p>Source packages contain all of the Package author’s (where appropriate
in regular packages) source code plus all of the files necessary to
build distribution tarballs (Unix Tar format files, gzipped for space
savings).
@@ -1110,7 +1110,7 @@
idea to install all packages and not interfere with the wishes of your
users.
</p>
-<p>If you can't find which package provides the feature you require, try
+<p>If you can’t find which package provides the feature you require, try
using the <code>package-get-package-provider</code> function. Eg., if you know
that you need <code>thingatpt</code>, type:
</p>
@@ -1143,7 +1143,7 @@
<p>There are three main ways to install packages:
</p>
<table class="menu" border="0" cellspacing="0">
-<tr><td align="left" valign="top"><a href="#Sumo">•
Sumo</a></td><td> </td><td align="left" valign="top">
All at once, using the 'Sumo Tarball'.
+<tr><td align="left" valign="top"><a href="#Sumo">•
Sumo</a></td><td> </td><td align="left" valign="top">
All at once, using the ’Sumo Tarball’.
</td></tr>
<tr><td align="left" valign="top"><a href="#Manually">•
Manually</a></td><td> </td><td align="left" valign="top">
Using individual package tarballs.
</td></tr>
@@ -1167,7 +1167,7 @@
</p>
<p>For an XEmacs compiled with Mule you also need:
‘<tt>xemacs-mule-sumo.tar.gz</tt>’
</p>
-<p>N.B. They are called 'Sumo Tarballs' for good reason. They are
+<p>N.B. They are called ’Sumo Tarballs’ for good reason. They are
currently about 19MB and 4.5MB (gzipped) respectively.
</p>
<p>Install them by:
@@ -1190,7 +1190,7 @@
a fresh install it is sufficient to untar the file at the top of the
package hierarchy.
</p>
-<p>Note: If you are upgrading packages already installed, it's best to
+<p>Note: If you are upgrading packages already installed, it’s best to
remove the old package first <a href="#Removing-Packages">Removing
Packages</a>.
</p>
<p>For example if we are installing the ‘<tt>xemacs-base</tt>’
@@ -1287,7 +1287,7 @@
<p>From here, you can select or unselect packages for installation using
the <RET> key, the <kbd>Mouse-2</kbd> button or selecting
"Select" from
the (Popup) Menu.
-Once you've finished selecting the packages, you can
+Once you’ve finished selecting the packages, you can
press the <kbd>x</kbd> key (or use the menu) to actually install the
packages. Note that you will have to restart XEmacs for XEmacs to
recognize any new packages.
@@ -1340,7 +1340,7 @@
those packages also.
</p>
<p>For novices and gurus alike, this step can save your bacon.
-It's easy to forget to install a critical package.
+It’s easy to forget to install a critical package.
</p>
</li><li>
Download and install the packages.
@@ -1368,7 +1368,7 @@
edit-utils, fsf-compat, mail-lib, net-utils, os-utils, prog-modes,
text-modes, time
</p>
-<p>If you are using the XEmacs package tools, don't forget to do:
+<p>If you are using the XEmacs package tools, don’t forget to do:
</p>
<p> Packages -> Add Required
</p>
@@ -1387,7 +1387,7 @@
‘<tt>pgkinfo/MANIFEST.pkgname</tt>’ file which list all the files
belonging
to the package.
</p>
-<p>No need to panic, you don't have to go through the
+<p>No need to panic, you don’t have to go through the
‘<tt>pkinfo/MANIFEST.pkgname</tt>’ and manually delete the files.
Instead, use
<code>M-x package-get-delete-package RET</code>.
</p>
@@ -1529,13 +1529,13 @@
file, ‘<tt>Local.rules.template</tt>’. Simply copy that to
‘<tt>Local.rules</tt>’ and edit it to suit your needs.
</p>
-<p>These are the variables in 'Local.rules' that you will need to
+<p>These are the variables in ’Local.rules’ that you will need to
address.
</p>
<dl compact="compact">
<dt> <var>symlink =</var> </dt>
-<dd><p>Set this to 't' if you want to do a "run in place".
-Setting this doesn't work well with 'make bindist'
+<dd><p>Set this to ’t’ if you want to do a "run in
place".
+Setting this doesn’t work well with ’make bindist’
</p>
</dd>
<dt> <var>XEMACS_PACKAGES =</var></dt>
@@ -1557,11 +1557,11 @@
</dd>
<dt> <var>BUILD_WITHOUT_MULE =</var></dt>
<dd><p>Building from CVS defaults to building the Mule
-packages. Set this to 't' if you don't want/have Mule
+packages. Set this to ’t’ if you don’t want/have Mule
</p>
</dd>
<dt> <var>MULE_PACKAGES =</var></dt>
-<dd><p>Same as for 'XEMACS_PACKAGES' except you list the Mule
+<dd><p>Same as for ’XEMACS_PACKAGES’ except you list the Mule
packages you want to install here. eg:
</p><table><tr><td> </td><td><pre class="example"> MULE_PACKAGES =
mule-packages/mule-base mule-packages/skk
</pre></td></tr></table>
@@ -1569,15 +1569,15 @@
</dd>
<dt> <var>MULE_STAGING = ${XEMACS_PACKAGES_BASE}/../Mule-Packages</var></dt>
<dd><p>Set this to where you want Mule packages installed
-to. Note: 'make bindist' does not use this variable.
+to. Note: ’make bindist’ does not use this variable.
</p>
</dd>
<dt> <var>XEMACS = xemacs</var></dt>
-<dd><p>If your XEmacs isn't in your path, change this.
+<dd><p>If your XEmacs isn’t in your path, change this.
</p>
</dd>
<dt> <var>XEMACS_NATIVE_NT =</var></dt>
-<dd><p>Set this to 't' if you are building on WinNT.
+<dd><p>Set this to ’t’ if you are building on WinNT.
</p>
</dd>
<dt> <var>INSTALL = install -c</var></dt>
@@ -1660,7 +1660,7 @@
‘<tt>Imakefile</tt>’ or an <code>automake</code> file: the
complexity is hidden in
generic rules files, in this case the ‘<tt>XEmacs.rules</tt>’
include file
in the top directory of the packages hierarchy. Although a number of
-facilities are available for complex libraries, most simple packages'
+facilities are available for complex libraries, most simple packages’
‘<tt>Makefile</tt>’s contain a copyright notice, a few variable
definitions,
an include for ‘<tt>XEmacs.rules</tt>’, and a couple of standard
targets.
</p>
@@ -1741,8 +1741,8 @@
<a name="SEC282"></a>
<h2 class="heading"> Available Packages: </h2>
<p>This section lists the Lisp packages that are currently available from
-xemacs.org and it's mirrors. If a particular package that you are
-looking for isn't here, please send a message to the
+xemacs.org and it’s mirrors. If a particular package that you are
+looking for isn’t here, please send a message to the
<a href="mailto:address@hidden";>XEmacs Beta list</a>.
</p>
<p>This data is up to date as of September 22, 2002.
@@ -1836,7 +1836,7 @@
</dd>
<dt> ‘<tt>edit-utils</tt>’</dt>
<dd><p>Single file lisp packages for various XEmacs goodies. Load this and
-weed out the junk you don't want.
+weed out the junk you don’t want.
</p>
</dd>
<dt> ‘<tt>edt</tt>’</dt>
@@ -1960,7 +1960,7 @@
</p>
</dd>
<dt> ‘<tt>mine</tt>’</dt>
-<dd><p>Elisp implementation of the game 'Minehunt'.
+<dd><p>Elisp implementation of the game ’Minehunt’.
</p>
</dd>
<dt> ‘<tt>misc-games</tt>’</dt>
@@ -2028,7 +2028,7 @@
</p>
</dd>
<dt> ‘<tt>rmail</tt>’</dt>
-<dd><p>An obsolete Emacs mailer. If you do not already use it don't start.
+<dd><p>An obsolete Emacs mailer. If you do not already use it don’t
start.
</p>
</dd>
<dt> ‘<tt>ruby-modes</tt>’</dt>
@@ -2226,7 +2226,7 @@
</p>
</dd>
<dt> ‘<tt>lookup</tt>’</dt>
-<dd><p>Dictionary support. (This isn't an English dictionary program)
+<dd><p>Dictionary support. (This isn’t an English dictionary program)
</p>
</dd>
<dt> ‘<tt>mule-base</tt>’</dt>
Index: Tests/xemacs_frame_res/xemacs_26.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/xemacs_frame_res/xemacs_26.html,v
retrieving revision 1.23
retrieving revision 1.24
diff -u -b -r1.23 -r1.24
--- Tests/xemacs_frame_res/xemacs_26.html 5 Feb 2007 15:30:27 -0000
1.23
+++ Tests/xemacs_frame_res/xemacs_26.html 3 Oct 2007 09:34:55 -0000
1.24
@@ -329,7 +329,7 @@
word at the beginning is the abbrev. The number that appears is the number
of times the abbrev has been expanded. Emacs keeps track of this to help
you see which abbrevs you actually use, in case you want to eliminate
-those that you don't use often. The string at the end of the line is the
+those that you don’t use often. The string at the end of the line is the
expansion.
</p>
<a name="IDX1078"></a>
Index: Tests/xemacs_frame_res/xemacs_28.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/xemacs_frame_res/xemacs_28.html,v
retrieving revision 1.23
retrieving revision 1.24
diff -u -b -r1.23 -r1.24
--- Tests/xemacs_frame_res/xemacs_28.html 5 Feb 2007 15:30:27 -0000
1.23
+++ Tests/xemacs_frame_res/xemacs_28.html 3 Oct 2007 09:34:55 -0000
1.24
@@ -272,10 +272,10 @@
</p>
<p>In this version of Emacs, what you see is what you get: in contrast to
some other versions, no abbreviations are expanded after you have sent the
-mail. This means you don't suffer the annoyance of having the system do
+mail. This means you don’t suffer the annoyance of having the system do
things behind your back—if the system rewrites an address you typed,
you know it immediately, instead of after the mail has been sent and
-it's too late to do anything about it. For example, you will never
+it’s too late to do anything about it. For example, you will never
again be in trouble because you forgot to delete an old alias from your
‘<tt>.mailrc</tt>’ and a new local user is given a userid which
conflicts
with one of your aliases.
Index: Tests/xemacs_frame_res/xemacs_29.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/xemacs_frame_res/xemacs_29.html,v
retrieving revision 1.26
retrieving revision 1.27
diff -u -b -r1.26 -r1.27
--- Tests/xemacs_frame_res/xemacs_29.html 5 Feb 2007 15:30:27 -0000
1.26
+++ Tests/xemacs_frame_res/xemacs_29.html 3 Oct 2007 09:34:55 -0000
1.27
@@ -119,7 +119,7 @@
<p> <kbd>Button2</kbd> in the calendar brings up a menu of operations on a
particular date; <kbd>Buttons3</kbd> brings up a menu of commonly used
calendar features that are independent of any particular date. To exit
-the calendar, type <kbd>q</kbd>. See <a
href="../lispref/Calendar.html#Calendar">Customizing the Calendar and Diary:
(lispref)Calendar</a> section `Calendar' in <cite>The XEmacs Lisp Reference
Manual</cite>, for customization
+the calendar, type <kbd>q</kbd>. See <a
href="../lispref/Calendar.html#Calendar">Customizing the Calendar and Diary:
(lispref)Calendar</a> section ‘Calendar’ in <cite>The XEmacs Lisp
Reference Manual</cite>, for customization
information about the calendar and diary.
</p>
<table class="menu" border="0" cellspacing="0">
@@ -265,7 +265,7 @@
<a name="IDX1156"></a>
<p> The commands for motion by months and years work like those for
weeks, but move a larger distance. The month commands <kbd>M-}</kbd> and
-<kbd>M-{</kbd> move forward or backward by an entire month's time. The
+<kbd>M-{</kbd> move forward or backward by an entire month’s time. The
year commands <kbd>C-x ]</kbd> and <kbd>C-x [</kbd> move forward or backward a
whole year.
</p>
@@ -383,7 +383,7 @@
<dd><p>Center calendar around specified month
(<code>calendar-other-month</code>).
</p></dd>
<dt> <kbd>.</kbd></dt>
-<dd><p>Move point to today's date (<code>calendar-goto-today</code>).
+<dd><p>Move point to today’s date (<code>calendar-goto-today</code>).
</p></dd>
</dl>
@@ -401,7 +401,7 @@
</p>
<a name="IDX1176"></a>
<a name="IDX1177"></a>
-<p> You can return to today's date with <kbd>.</kbd>
+<p> You can return to today’s date with <kbd>.</kbd>
(<code>calendar-goto-today</code>).
</p>
<hr size="6">
@@ -505,7 +505,7 @@
</p>
<dl compact="compact">
<dt> <kbd>C-SPC</kbd></dt>
-<dd><p>Set the mark to today's date (<code>calendar-set-mark</code>).
+<dd><p>Set the mark to today’s date (<code>calendar-set-mark</code>).
</p></dd>
<dt> <kbd>C-@</kbd></dt>
<dd><p>The same.
@@ -756,7 +756,7 @@
(<code>list-calendar-holidays</code>).
</p></dd>
<dt> <kbd>M-x holidays</kbd></dt>
-<dd><p>List all holidays for three months around today's date in another
+<dd><p>List all holidays for three months around today’s date in another
window.
</p></dd>
<dt> <kbd>M-x list-holidays</kbd></dt>
@@ -795,7 +795,7 @@
<a name="IDX1215"></a>
<p> The command <kbd>M-x holidays</kbd> displays the list of holidays for the
current month and the preceding and succeeding months; this works even
-if you don't have a calendar window. If you want the list of holidays
+if you don’t have a calendar window. If you want the list of holidays
centered around a different month, use <kbd>C-u M-x holidays</kbd>, which
prompts for the month and year.
</p>
@@ -807,7 +807,7 @@
<p> The command <kbd>M-x list-holidays</kbd> displays the list of holidays
for
a range of years. This function asks you for the starting and stopping
years, and allows you to choose all the holidays or one of several
-categories of holidays. You can use this command even if you don't have
+categories of holidays. You can use this command even if you don’t have
a calendar window.
</p>
<p> The dates used by Emacs for holidays are based on <em>current
@@ -851,7 +851,7 @@
<dd><p>Display times of sunrise and sunset for the date you click on.
</p></dd>
<dt> <kbd>M-x sunrise-sunset</kbd></dt>
-<dd><p>Display times of sunrise and sunset for today's date.
+<dd><p>Display times of sunrise and sunset for today’s date.
</p></dd>
<dt> <kbd>C-u M-x sunrise-sunset</kbd></dt>
<dd><p>Display times of sunrise and sunset for a specified date.
@@ -866,7 +866,7 @@
<kbd>S</kbd>. Alternatively, click <kbd>Button2</kbd> on the date, then choose
<kbd>Sunrise/Sunset</kbd> from the menu that appears. The command <kbd>M-x
sunrise-sunset</kbd> is available outside the calendar to display this
-information for today's date or a specified date. To specify a date
+information for today’s date or a specified date. To specify a date
other than today, use <kbd>C-u M-x sunrise-sunset</kbd>, which prompts for
the year, month, and day.
</p>
@@ -952,7 +952,7 @@
</p></dd>
<dt> <kbd>M-x phases-of-moon</kbd></dt>
<dd><p>Display dates and times of the quarters of the moon for three months
around
-today's date.
+today’s date.
</p></dd>
</dl>
@@ -1023,7 +1023,7 @@
<p> If you are interested in these calendars, you can convert dates one at a
time. Put point on the desired date of the Gregorian calendar and press the
appropriate keys. The <kbd>p</kbd> is a mnemonic for “print”
since Emacs
-“prints' the equivalent date in the echo area.
+“prints’ the equivalent date in the echo area.
</p><hr size="6">
<a name="Calendar-Systems"></a>
<a name="SEC314"></a>
@@ -1197,7 +1197,7 @@
calendars is to click on it with <kbd>Button2</kbd>, then choose <kbd>Other
Calendars</kbd> from the menu that appears. This displays the equivalent
forms of the date in all the calendars Emacs understands, in the form of
-a menu. (Choosing an alternative from this menu doesn't actually do
+a menu. (Choosing an alternative from this menu doesn’t actually do
anything—the menu is used only for display.)
</p>
<p> Put point on the desired date of the Gregorian calendar, then type the
@@ -1285,9 +1285,9 @@
<p> These commands ask you for a date on the other calendar, move point to
the Gregorian calendar date equivalent to that date, and display the
-other calendar's date in the echo area. Emacs uses strict completion
+other calendar’s date in the echo area. Emacs uses strict completion
(see section <a href="xemacs_9.html#SEC63">Completion</a>) whenever it asks
you to type a month name, so you
-don't have to worry about the spelling of Hebrew, Islamic, or French names.
+don’t have to worry about the spelling of Hebrew, Islamic, or French
names.
</p>
<a name="IDX1263"></a>
<a name="IDX1264"></a>
@@ -1404,7 +1404,7 @@
haab/tzolkin date combination you have typed is impossible.
</p>
<p> Emacs uses strict completion (see section <a
href="xemacs_9.html#SEC63">Completion</a>) whenever it
-asks you to type a Mayan name, so you don't have to worry about
+asks you to type a Mayan name, so you don’t have to worry about
spelling.
</p>
<hr size="6">
@@ -1495,7 +1495,7 @@
<h3 class="subsection"> 26.5.3 Commands Displaying Diary Entries </h3>
<p> Once you have created a ‘<tt>~/diary</tt>’ file, you can use
the calendar
-to view it. You can also view today's events outside of Calendar mode.
+to view it. You can also view today’s events outside of Calendar mode.
</p>
<dl compact="compact">
<dt> <kbd>d</kbd></dt>
@@ -1519,7 +1519,7 @@
<dd><p>Print hard copy of the diary display as it appears.
</p></dd>
<dt> <kbd>M-x diary</kbd></dt>
-<dd><p>Display all diary entries for today's date.
+<dd><p>Display all diary entries for today’s date.
</p></dd>
<dt> <kbd>M-x diary-mail-entries</kbd></dt>
<dd><p>Mail yourself email reminders about upcoming diary entries.
@@ -1559,7 +1559,7 @@
the <kbd>s</kbd> command.
</p>
<p> Display of selected diary entries uses the selective display feature
-to hide entries that don't apply.
+to hide entries that don’t apply.
</p>
<a name="IDX1284"></a>
<p> The diary buffer as you see it is an illusion, so simply printing the
@@ -1576,7 +1576,7 @@
how many days to include (see section <a
href="xemacs_30.html#SEC351">Customization</a>).
</p>
<p> If you put <code>(diary)</code> in your init file, this
-automatically displays a window with the day's diary entries, when you
+automatically displays a window with the day’s diary entries, when you
enter Emacs. See section <a href="xemacs_30.html#SEC377">The Init File</a>.
The mode line of the displayed window
shows the date and any holidays that fall on that date.
</p>
@@ -1634,7 +1634,7 @@
</p>
<p> If the first line of a diary entry consists only of the date or day
name with no following blanks or punctuation, then the diary window
-display doesn't include that line; only the continuation lines appear.
+display doesn’t include that line; only the continuation lines appear.
For example, this entry:
</p>
<table><tr><td> </td><td><pre class="example">02/11/1989
@@ -1647,8 +1647,8 @@
</pre></td></tr></table>
<p>appears in the diary window without the date line at the beginning.
-This style of entry looks neater when you display just a single day's
-entries, but can cause confusion if you ask for more than one day's
+This style of entry looks neater when you display just a single day’s
+entries, but can cause confusion if you ask for more than one day’s
entries.
</p>
<p> You can edit the diary entries as they appear in the window, but it is
@@ -1711,7 +1711,7 @@
is, you can use ‘<samp>11/12/1989</samp>’ or
‘<samp>11/12/89</samp>’.
</p>
<p> Dates can also have the form ‘<samp><var>monthname</var>
<var>day</var></samp>’ or
-‘<samp><var>monthname</var> <var>day</var>,
<var>year</var></samp>’, where the month's name can
+‘<samp><var>monthname</var> <var>day</var>,
<var>year</var></samp>’, where the month’s name can
be spelled in full or abbreviated to three characters (with or without a
period). Case is not significant.
</p>
@@ -1915,7 +1915,7 @@
</p>
<p> Marking sexp diary entries in the calendar is <em>extremely</em>
time-consuming, since every date visible in the calendar window must be
-individually checked. So it's a good idea to make sexp diary entries
+individually checked. So it’s a good idea to make sexp diary entries
nonmarking (with ‘<samp>&</samp>’) when possible.
</p>
<p> Another sophisticated kind of sexp entry, a <em>floating</em> diary entry,
@@ -2091,7 +2091,7 @@
<p> The variable <code>today-visible-calendar-hook</code> is a normal hook run
after the calendar buffer has been prepared with the calendar when the
current date is visible in the window. One use of this hook is to
-replace today's date with asterisks; to do that, use the hook function
+replace today’s date with asterisks; to do that, use the hook function
<code>calendar-star-date</code>.
</p>
<a name="IDX1317"></a>
@@ -2099,14 +2099,14 @@
</pre></td></tr></table>
<p>Another standard hook function marks the current date, either by
-changing its face or by adding an asterisk. Here's how to use it:
+changing its face or by adding an asterisk. Here’s how to use it:
</p>
<a name="IDX1318"></a>
<table><tr><td> </td><td><pre class="example">(add-hook
'today-visible-calendar-hook 'calendar-mark-today)
</pre></td></tr></table>
<a name="IDX1319"></a>
-<p>The variable <code>calendar-today-marker</code> specifies how to mark
today's
+<p>The variable <code>calendar-today-marker</code> specifies how to mark
today’s
date. Its value should be a character to insert next to the date or a
face name to use for displaying the date. A face named
<code>calendar-today-face</code> is provided for this purpose; that symbol is
@@ -2216,7 +2216,7 @@
<dt> <code>(holiday-sexp <var>sexp</var> <var>string</var>)</code></dt>
<dd><p>A date calculated by the Lisp expression <var>sexp</var>. The
expression
should use the variable <code>year</code> to compute and return the date of a
-holiday, or <code>nil</code> if the holiday doesn't happen this year. The
+holiday, or <code>nil</code> if the holiday doesn’t happen this year.
The
value of <var>sexp</var> must represent the date as a list of the form
<code>(<var>month</var> <var>day</var> <var>year</var>)</code>.
<var>string</var> is the name of
the holiday.
@@ -2267,12 +2267,12 @@
</pre></td></tr></table>
<p>adds the last day of Hanukkah (since the Hebrew months are numbered with
-1 starting from Nisan), the Islamic feast celebrating Mohammed's
+1 starting from Nisan), the Islamic feast celebrating Mohammed’s
birthday (since the Islamic months are numbered from 1 starting with
-Muharram), and Thomas Jefferson's birthday, which is 2 April 1743 on the
+Muharram), and Thomas Jefferson’s birthday, which is 2 April 1743 on the
Julian calendar.
</p>
-<p> To include a holiday conditionally, use either Emacs Lisp's
<code>if</code> or the
+<p> To include a holiday conditionally, use either Emacs Lisp’s
<code>if</code> or the
<code>holiday-sexp</code> form. For example, American presidential elections
occur on the first Tuesday after the first Monday in November of years
divisible by 4:
@@ -2297,7 +2297,7 @@
"US Presidential Election"))
</pre></td></tr></table>
-<p> Some holidays just don't fit into any of these forms because special
+<p> Some holidays just don’t fit into any of these forms because special
calculations are involved in their determination. In such cases you
must write a Lisp function to do the calculation. To include eclipses,
for example, add <code>(eclipses)</code> to <code>other-holidays</code>
@@ -2491,7 +2491,7 @@
<p> The two variables <code>calendar-daylight-savings-starts-time</code> and
<code>calendar-daylight-savings-ends-time</code> specify the number of minutes
after midnight local time when the transition to and from daylight
-savings time should occur. For Cambridge, Massachusetts both variables'
+savings time should occur. For Cambridge, Massachusetts both variables’
values are 120.
</p>
<hr size="6">
@@ -2518,7 +2518,7 @@
<p> Ordinarily, the mode line of the diary buffer window indicates any
holidays that fall on the date of the diary entries. The process of
checking for holidays can take several seconds, so including holiday
-information delays the display of the diary buffer noticeably. If you'd
+information delays the display of the diary buffer noticeably. If you’d
prefer to have a faster display of the diary buffer but without the
holiday information, set the variable <code>holidays-in-diary-buffer</code> to
<code>nil</code>.
@@ -2528,13 +2528,13 @@
days of diary entries to be displayed at one time. It affects the
initial display when <code>view-diary-entries-initially</code> is
<code>t</code>, as
well as the command <kbd>M-x diary</kbd>. For example, the default value is
-1, which says to display only the current day's diary entries. If the
-value is 2, both the current day's and the next day's entries are
+1, which says to display only the current day’s diary entries. If the
+value is 2, both the current day’s and the next day’s entries are
displayed. The value can also be a vector of seven elements: for
example, if the value is <code>[0 2 2 2 2 4 1]</code> then no diary entries
-appear on Sunday, the current date's and the next day's diary entries
-appear Monday through Thursday, Friday through Monday's entries appear
-on Friday, while on Saturday only that day's entries appear.
+appear on Sunday, the current date’s and the next day’s diary
entries
+appear Monday through Thursday, Friday through Monday’s entries appear
+on Friday, while on Saturday only that day’s entries appear.
</p>
<a name="IDX1333"></a>
<a name="IDX1334"></a>
@@ -2584,7 +2584,7 @@
<p>Emacs matches of the diary entries with the date forms is done with the
standard syntax table from Fundamental mode
-(see <a href="../lispref/Syntax-Tables.html#Syntax-Tables">(lispref)Syntax
Tables</a> section `Syntax Tables' in <cite>XEmacs Lisp Reference
Manual</cite>),
+(see <a href="../lispref/Syntax-Tables.html#Syntax-Tables">(lispref)Syntax
Tables</a> section ‘Syntax Tables’ in <cite>XEmacs Lisp Reference
Manual</cite>),
but with the ‘<samp>*</samp>’ changed so that it is a word
constituent.
</p>
<p> The date patterns in the list must be <em>mutually exclusive</em> and
@@ -2634,7 +2634,7 @@
<p> Your diary file can have entries based on Hebrew or Islamic dates, as
well as entries based on the world-standard Gregorian calendar.
However, because recognition of such entries is time-consuming and most
-people don't use them, you must explicitly enable their use. If you
+people don’t use them, you must explicitly enable their use. If you
want the diary to recognize Hebrew-date diary entries, for example,
you must do this:
</p>
@@ -2777,7 +2777,7 @@
</p>
<a name="IDX1351"></a>
<p> If you use the fancy diary display, you can use the normal hook
-<code>list-diary-entries-hook</code> to sort each day's diary entries by their
+<code>list-diary-entries-hook</code> to sort each day’s diary entries by
their
time of day. Add this line to your init file:
</p>
<a name="IDX1352"></a>
@@ -2938,36 +2938,36 @@
<a name="IDX1368"></a>
<dl compact="compact">
<dt> <code>%%(diary-sunrise-sunset)</code></dt>
-<dd><p>Make a diary entry for the local times of today's sunrise and sunset.
+<dd><p>Make a diary entry for the local times of today’s sunrise and
sunset.
</p></dd>
<dt> <code>%%(diary-phases-of-moon)</code></dt>
<dd><p>Make a diary entry for the phases (quarters) of the moon.
</p></dd>
<dt> <code>%%(diary-day-of-year)</code></dt>
-<dd><p>Make a diary entry with today's day number in the current year and the
number
+<dd><p>Make a diary entry with today’s day number in the current year
and the number
of days remaining in the current year.
</p></dd>
<dt> <code>%%(diary-iso-date)</code></dt>
-<dd><p>Make a diary entry with today's equivalent ISO commercial date.
+<dd><p>Make a diary entry with today’s equivalent ISO commercial date.
</p></dd>
<dt> <code>%%(diary-julian-date)</code></dt>
-<dd><p>Make a diary entry with today's equivalent date on the Julian calendar.
+<dd><p>Make a diary entry with today’s equivalent date on the Julian
calendar.
</p></dd>
<dt> <code>%%(diary-astro-day-number)</code></dt>
-<dd><p>Make a diary entry with today's equivalent astronomical (Julian) day
number.
+<dd><p>Make a diary entry with today’s equivalent astronomical (Julian)
day number.
</p></dd>
<dt> <code>%%(diary-hebrew-date)</code></dt>
-<dd><p>Make a diary entry with today's equivalent date on the Hebrew calendar.
+<dd><p>Make a diary entry with today’s equivalent date on the Hebrew
calendar.
</p></dd>
<dt> <code>%%(diary-islamic-date)</code></dt>
-<dd><p>Make a diary entry with today's equivalent date on the Islamic calendar.
+<dd><p>Make a diary entry with today’s equivalent date on the Islamic
calendar.
</p></dd>
<dt> <code>%%(diary-french-date)</code></dt>
-<dd><p>Make a diary entry with today's equivalent date on the French
Revolutionary
+<dd><p>Make a diary entry with today’s equivalent date on the French
Revolutionary
calendar.
</p></dd>
<dt> <code>%%(diary-mayan-date)</code></dt>
-<dd><p>Make a diary entry with today's equivalent date on the Mayan calendar.
+<dd><p>Make a diary entry with today’s equivalent date on the Mayan
calendar.
</p></dd>
</dl>
@@ -2976,7 +2976,7 @@
<table><tr><td> </td><td><pre
class="smallexample">&%%(diary-hebrew-date)
</pre></td></tr></table>
-<p>causes every day's diary display to contain the equivalent date on the
+<p>causes every day’s diary display to contain the equivalent date on the
Hebrew calendar, if you are using the fancy diary display. (With simple
diary display, the line ‘<samp>&%%(diary-hebrew-date)</samp>’
appears in the
diary for any date, but does nothing particularly useful.)
@@ -3103,8 +3103,8 @@
identify a <em>sort key</em> for each record, and then reorder the records
using the order determined by the sort keys. The records are ordered so
that their keys are in alphabetical order, or, for numerical sorting, in
-numerical order. In alphabetical sorting, all upper-case letters `A'
-through `Z' come before lower-case `a', in accordance with the ASCII
+numerical order. In alphabetical sorting, all upper-case letters
‘A’
+through ‘Z’ come before lower-case ‘a’, in accordance
with the ASCII
character sequence.
</p>
<p> The sort commands differ in how they divide the text into sort
@@ -3182,7 +3182,7 @@
whether the file has changed on disk since it was last visited or
</pre></td></tr></table>
-<p>where the upper case `O' comes before all lower case letters. If you apply
+<p>where the upper case ‘O’ comes before all lower case letters.
If you apply
instead <kbd>C-u 2 M-x sort-fields</kbd> you get:
</p>
<table><tr><td> </td><td><pre class="smallexample">saved. If it has, you
are asked to confirm that you want to change
@@ -3200,7 +3200,7 @@
columns by putting point at one of the columns and the mark at the other
column. Because this means you cannot put point or the mark at the
beginning of the first line to sort, this command uses an unusual
-definition of `region': all of the line point is in is considered part of
+definition of ‘region’: all of the line point is in is considered
part of
the region, and so is all of the line the mark is in.
</p>
<p> For example, to sort a table by information found in columns 10 to 15,
@@ -3385,8 +3385,8 @@
<a name="IDX1397"></a>
<a name="IDX1398"></a>
<p> <code>cd</code>, <code>pushd</code>, and <code>popd</code> commands given
to the inferior
-shell are watched by XEmacs so it can keep the
‘<samp>*shell*</samp>’ buffer's
-default directory the same as the shell's working directory. These
+shell are watched by XEmacs so it can keep the
‘<samp>*shell*</samp>’ buffer’s
+default directory the same as the shell’s working directory. These
commands are recognized syntactically by examining lines of input that are
sent. If you use aliases for these commands, you can tell XEmacs to
recognize them also. For example, if the value of the variable
@@ -3396,7 +3396,7 @@
<code>shell-cd-regexp</code> are used to recognize commands with the meaning of
‘<samp>popd</samp>’ and ‘<samp>cd</samp>’.
</p>
-<p><kbd>M-x shell-resync-dirs</kbd> queries the shell and resynchronizes
XEmacs'
+<p><kbd>M-x shell-resync-dirs</kbd> queries the shell and resynchronizes
XEmacs’
idea of what the current directory stack is. <kbd>M-x
shell-dirtrack-toggle</kbd> turns directory tracking on and off.
</p>
@@ -3476,7 +3476,7 @@
<dd><p>At end of buffer send line as input; otherwise, copy current line to
end of
buffer and send it (<code>send-shell-input</code>). When a line is copied, any
text at the beginning of the line that matches the variable
-<code>shell-prompt-pattern</code> is left out; this variable's value should be
a
+<code>shell-prompt-pattern</code> is left out; this variable’s value
should be a
regexp string that matches the prompts that you use in your subshell.
</p></dd>
<dt> <kbd>C-c C-d</kbd></dt>
@@ -3573,7 +3573,7 @@
codes needed vary from terminal to terminal, but nowadays
most terminals and terminal emulators (including xterm)
understand the so-called "ANSI escape sequences" (first
-popularized by the Digital's VT100 family of terminal).
+popularized by the Digital’s VT100 family of terminal).
The term mode also understands these escape sequences,
and for each control code does the appropriate thing
to change the buffer so that the appearance of the window
@@ -3720,7 +3720,7 @@
the rest temporarily invisible and inaccessible. Cancelling the narrowing
and making the entire buffer once again visible is called <em>widening</em>.
The amount of narrowing in effect in a buffer at any time is called the
-buffer's <em>restriction</em>.
+buffer’s <em>restriction</em>.
</p>
<dl compact="compact">
<dt> <kbd>C-x n n</kbd></dt>
@@ -3736,15 +3736,15 @@
restrict the range of operation of a replace command or repeating
keyboard macro. The word ‘<samp>Narrow</samp>’ appears in the
mode line
whenever narrowing is in effect. When you have narrowed to a part of the
-buffer, that part appears to be all there is. You can't see the rest,
-can't move into it (motion commands won't go outside the visible part),
-and can't change it in any way. However, the invisible text is not
+buffer, that part appears to be all there is. You can’t see the rest,
+can’t move into it (motion commands won’t go outside the visible
part),
+and can’t change it in any way. However, the invisible text is not
gone; if you save the file, it will be saved.
</p>
<a name="IDX1432"></a>
<a name="IDX1433"></a>
<p> The primary narrowing command is <kbd>C-x n n</kbd>
(<code>narrow-to-region</code>).
-It sets the current buffer's restrictions so that the text in the current
+It sets the current buffer’s restrictions so that the text in the current
region remains visible but all text before the region or after the region
is invisible. Point and mark do not change.
</p>
@@ -3858,7 +3858,7 @@
</p>
<p> The mode line shows you when you are in a recursive edit by displaying
square brackets around the parentheses that always surround the major
-and minor mode names. Every window's mode line shows the square
+and minor mode names. Every window’s mode line shows the square
brackets, since XEmacs as a whole, rather than any particular buffer, is
in a recursive edit.
</p>
@@ -3932,9 +3932,9 @@
buffer to another. In order to produce plausible output rather than
gibberish, it insists on a certain amount of overlap between the end of one
run of consecutive words or characters and the start of the next. That is,
-if it has just printed out `president' and then decides to jump to a
-different point in the file, it might spot the `ent' in `pentagon' and
-continue from there, producing `presidentagon'. Long sample texts produce
+if it has just printed out ‘president’ and then decides to jump to
a
+different point in the file, it might spot the ‘ent’ in
‘pentagon’ and
+continue from there, producing ‘presidentagon’. Long sample texts
produce
the best results.
</p>
<a name="IDX1448"></a>
Index: Tests/xemacs_frame_res/xemacs_3.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/xemacs_frame_res/xemacs_3.html,v
retrieving revision 1.18
retrieving revision 1.19
diff -u -b -r1.18 -r1.19
--- Tests/xemacs_frame_res/xemacs_3.html 5 Feb 2007 15:30:27 -0000
1.18
+++ Tests/xemacs_frame_res/xemacs_3.html 3 Oct 2007 09:34:55 -0000
1.19
@@ -102,7 +102,7 @@
</p>
<p> <em>Extensible</em> means you can go beyond simple customization and
write entirely new commands, programs in the Lisp language to be run by
-XEmacs's own Lisp interpreter. XEmacs is an “on-line extensible”
+XEmacs’s own Lisp interpreter. XEmacs is an “on-line
extensible”
system: it is divided into many functions that call each other. You can
redefine any function in the middle of an editing session and replace
any part of XEmacs without making a separate copy of all of XEmacs. Most
Index: Tests/xemacs_frame_res/xemacs_30.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/xemacs_frame_res/xemacs_30.html,v
retrieving revision 1.28
retrieving revision 1.29
diff -u -b -r1.28 -r1.29
--- Tests/xemacs_frame_res/xemacs_30.html 5 Feb 2007 15:30:27 -0000
1.28
+++ Tests/xemacs_frame_res/xemacs_30.html 3 Oct 2007 09:34:55 -0000
1.29
@@ -69,7 +69,7 @@
have no effect on other Emacs jobs you may run at the same time or
later. The only way an Emacs job can affect anything outside of it is
by writing a file; in particular, the only way to make a customization
-`permanent' is to put something in your init file or other appropriate
+‘permanent’ is to put something in your init file or other
appropriate
file to do the customization in each session. See section <a
href="#SEC377">The Init File</a>.
</p>
<table class="menu" border="0" cellspacing="0">
@@ -190,7 +190,7 @@
that Emacs uses require a value of a certain type. Often the value has
to be a string or a number. Sometimes we say that a certain feature is
turned on if a variable is “non-<code>nil</code>,” meaning that if
the
-variable's value is <code>nil</code>, the feature is off, but the feature is
+variable’s value is <code>nil</code>, the feature is off, but the
feature is
on for <i>any</i> other value. The conventional value to turn on the
feature—since you have to pick one particular value when you set the
variable—is <code>t</code>.
@@ -208,11 +208,11 @@
the left margin) to be used by the fill commands (see section <a
href="xemacs_23.html#SEC210">Filling Text</a>).
</p>
<table class="menu" border="0" cellspacing="0">
-<tr><td align="left" valign="top"><a href="#SEC354">27.2.1 Examining and
Setting Variables</a></td><td> </td><td align="left" valign="top">
Examining or setting one variable's value.
+<tr><td align="left" valign="top"><a href="#SEC354">27.2.1 Examining and
Setting Variables</a></td><td> </td><td align="left" valign="top">
Examining or setting one variable’s value.
</td></tr>
<tr><td align="left" valign="top"><a href="#SEC355">27.2.2 Easy Customization
Interface</a></td><td> </td><td align="left" valign="top">
Convenient and easy customization of variables.
</td></tr>
-<tr><td align="left" valign="top"><a href="#SEC360">27.2.3 Editing Variable
Values</a></td><td> </td><td align="left" valign="top">
Examining or editing list of all variables' values.
+<tr><td align="left" valign="top"><a href="#SEC360">27.2.3 Editing Variable
Values</a></td><td> </td><td align="left" valign="top">
Examining or editing list of all variables’ values.
</td></tr>
<tr><td align="left" valign="top"><a href="#SEC361">27.2.4 Local
Variables</a></td><td> </td><td align="left" valign="top">
Per-buffer values of variables.
</td></tr>
@@ -464,7 +464,7 @@
customizing the variable.
</p>
<p> The line after the ‘<samp>[State]</samp>’ line displays the
beginning of the
-option's documentation string. If there are more lines of
+option’s documentation string. If there are more lines of
documentation, this line ends with ‘<samp>[More]</samp>’; invoke
this to show
the full documentation string.
</p>
@@ -488,7 +488,7 @@
<table><tr><td> </td><td><pre class="smallexample">[State]: you have set
this option, but not saved it for future sessions.
</pre></td></tr></table>
-<p> You don't have to worry about specifying a value that is not valid;
+<p> You don’t have to worry about specifying a value that is not valid;
setting the option checks for validity and will not really install an
unacceptable value.
</p>
@@ -499,7 +499,7 @@
type <kbd>M-<TAB></kbd> (<code>widget-complete</code>) to do completion.
</p>
<p> Some options have a small fixed set of possible legitimate values.
-These options don't let you edit the value textually. Instead, an
+These options don’t let you edit the value textually. Instead, an
active field ‘<samp>[Value Menu]</samp>’ appears before the value;
invoke this
field to edit the value. For a boolean “on or off” value, the
active
field says ‘<samp>[Toggle]</samp>’, and it changes to the other
value.
@@ -723,7 +723,7 @@
<p> You can also set up the customization buffer with a specific group,
using <kbd>M-x customize-group</kbd>. The immediate contents of the chosen
group, including option variables, faces, and other groups, all appear
-as well. However, these subgroups' own contents start out hidden. You
+as well. However, these subgroups’ own contents start out hidden. You
can show their contents in the usual way, by invoking
‘<samp>[Show]</samp>’.
</p>
<a name="IDX1491"></a>
@@ -854,7 +854,7 @@
<a name="IDX1496"></a>
<p> You can make any variable <em>local</em> to a specific Emacs buffer.
-This means that the variable's value in that buffer is independent of
+This means that the variable’s value in that buffer is independent of
its value in other buffers. A few variables are always local in every
buffer. All other Emacs variables have a <em>global</em> value which is in
effect in all buffers that have not made the variable local.
@@ -913,7 +913,7 @@
that has been marked with <code>make-variable-buffer-local</code>.
</p>
<a name="IDX1502"></a>
-<p> Programs can look at a variable's default value with
<code>default-value</code>.
+<p> Programs can look at a variable’s default value with
<code>default-value</code>.
This function takes a symbol as an argument and returns its default value.
The argument is evaluated; usually you must quote it explicitly, as in
the case of:
@@ -1002,7 +1002,7 @@
a matter of personal taste, not a matter of the contents of particular
files. If you want to use Auto Fill, set up major mode hooks with your
init file to turn it on (when appropriate) for you alone
-(see section <a href="#SEC377">The Init File</a>). Don't try to use a local
variable list that would
+(see section <a href="#SEC377">The Init File</a>). Don’t try to use a
local variable list that would
impose your taste on everyone working with the file.
</p>
<p>XEmacs allows you to specify local variables in the first line
@@ -1082,7 +1082,7 @@
recently defined keyboard macro.
</p></dd>
<dt> <kbd>M-x insert-kbd-macro</kbd></dt>
-<dd><p>Insert in the buffer a keyboard macro's definition, as Lisp code.
+<dd><p>Insert in the buffer a keyboard macro’s definition, as Lisp code.
</p></dd>
</dl>
@@ -1096,7 +1096,7 @@
<p> You define a keyboard macro by executing the commands which are its
definition. Put differently, as you are defining a keyboard macro, the
definition is being executed for the first time. This way, you see
-what the effects of your commands are, and don't have to figure
+what the effects of your commands are, and don’t have to figure
them out in your head. When you are finished, the keyboard macro is
defined and also has been executed once. You can then execute the same
set of commands again by invoking the macro.
@@ -1306,9 +1306,9 @@
</p>
<table class="menu" border="0" cellspacing="0">
<tr><td align="left" valign="top"><a href="#SEC368">27.4.1
Keymaps</a></td><td> </td><td align="left" valign="top">
Definition of the keymap data structure.
- Names of Emacs's standard keymaps.
+ Names of Emacs’s standard keymaps.
</td></tr>
-<tr><td align="left" valign="top"><a href="#SEC369">27.4.2 Changing Key
Bindings</a></td><td> </td><td align="left" valign="top"> How to
redefine one key's meaning conveniently.
+<tr><td align="left" valign="top"><a href="#SEC369">27.4.2 Changing Key
Bindings</a></td><td> </td><td align="left" valign="top"> How to
redefine one key’s meaning conveniently.
</td></tr>
<tr><td align="left" valign="top"><a href="#SEC373">27.4.3 Disabling
Commands</a></td><td> </td><td align="left" valign="top"> Disabling
a command means confirmation is required
before it can be executed. This is done to protect
@@ -1349,7 +1349,7 @@
<p> Each major mode has another keymap, its <em>local keymap</em>, which
contains overriding definitions for the single-character keys that are
redefined in that mode. Each buffer records which local keymap is
-installed for it at any time, and the current buffer's local keymap is
+installed for it at any time, and the current buffer’s local keymap is
the only one that directly affects command execution. The local keymaps
for Lisp mode, C mode, and many other major modes always exist even when
not in use. They are the values of the variables <code>lisp-mode-map</code>,
@@ -1430,8 +1430,8 @@
one. When both the global and local definitions of a key are other
keymaps, the next character is looked up in both keymaps, with the local
definition overriding the global one. The character after the
-<kbd>C-x</kbd> is looked up in both the major mode's own keymap for redefined
-<kbd>C-x</kbd> commands and in <code>ctl-x-map</code>. If the major mode's
own keymap
+<kbd>C-x</kbd> is looked up in both the major mode’s own keymap for
redefined
+<kbd>C-x</kbd> commands and in <code>ctl-x-map</code>. If the major
mode’s own keymap
for <kbd>C-x</kbd> commands contains <code>nil</code>, the definition from the
global
keymap for <kbd>C-x</kbd> commands is used.
</p>
@@ -1459,7 +1459,7 @@
<p> You can redefine an Emacs key by changing its entry in a keymap.
You can change the global keymap, in which case the change is effective in
all major modes except those that have their own overriding local
-definitions for the same key. Or you can change the current buffer's
+definitions for the same key. Or you can change the current buffer’s
local map, which affects all buffers using the same major mode.
</p>
<table class="menu" border="0" cellspacing="0">
@@ -1508,7 +1508,7 @@
that you type. When called as a function, <var>key</var> is a string, a
vector of events, or a vector of key-description lists as described in
the <code>define-key</code> function description. The binding goes in
-the current buffer's local map, which is shared with other buffers in
+the current buffer’s local map, which is shared with other buffers in
the same major mode.
</p>
<p>The following example:
@@ -1585,7 +1585,7 @@
</p>
<p><var>keys</var> is the sequence of keystrokes to bind.
</p>
-<p><var>def</var> is anything that can be a key's definition:
+<p><var>def</var> is anything that can be a key’s definition:
</p>
<ul>
<li>
@@ -1748,7 +1748,7 @@
</p>
<p> The direct mechanism for disabling a command is to have a
non-<code>nil</code>
<code>disabled</code> property on the Lisp symbol for the command. These
-properties are normally set by the user's init file with
+properties are normally set by the user’s init file with
Lisp expressions such as:
</p>
<table><tr><td> </td><td><pre class="example">(put 'delete-region
'disabled t)
@@ -1770,7 +1770,7 @@
init file for you. See section <a href="#SEC377">The Init File</a>.
</p>
<p> When you attempt to invoke a disabled command interactively in Emacs,
-a window is displayed containing the command's name, its
+a window is displayed containing the command’s name, its
documentation, and some instructions on what to do next; then
Emacs asks for input saying whether to execute the command as requested,
enable it and execute, or cancel it. If you decide to enable the
@@ -1873,7 +1873,7 @@
</p>
<dl compact="compact">
<dt> ‘<samp>-</samp>’</dt>
-<dd><p>The class of whitespace characters. Please don't use the formerly
+<dd><p>The class of whitespace characters. Please don’t use the formerly
advertised , which is not supported by GNU Emacs.
</p></dd>
<dt> ‘<samp>w</samp>’</dt>
@@ -1908,7 +1908,7 @@
string.
</p></dd>
<dt> ‘<samp>$</samp>’</dt>
-<dd><p>The class of self-matching delimiters. This is intended for TeX's
+<dd><p>The class of self-matching delimiters. This is intended for TeX’s
‘<samp>$</samp>’, which is used both to enter and leave math mode.
Thus,
a pair of matching ‘<samp>$</samp>’ characters surround each piece
of math mode
TeX input. A pair of adjacent ‘<samp>$</samp>’ characters act
like a single
@@ -1972,21 +1972,21 @@
</tr></table>
<h3 class="subsection"> 27.5.2 Altering Syntax Information </h3>
-<p> It is possible to alter a character's syntax table entry by storing a new
+<p> It is possible to alter a character’s syntax table entry by storing
a new
number in the appropriate element of the syntax table, but it would be hard
to determine what number to use. Emacs therefore provides a command that
allows you to specify the syntactic properties of a character in a
convenient way.
</p>
<a name="IDX1529"></a>
-<p> <kbd>M-x modify-syntax-entry</kbd> is the command to change a character's
+<p> <kbd>M-x modify-syntax-entry</kbd> is the command to change a
character’s
syntax. It can be used interactively and is also used by major
modes to initialize their own syntax tables. Its first argument is the
character to change. The second argument is a string that specifies the
new syntax. When called from Lisp code, there is a third, optional
argument, which specifies the syntax table in which to make the change. If
not supplied, or if this command is called interactively, the third
-argument defaults to the current buffer's syntax table.
+argument defaults to the current buffer’s syntax table.
</p>
<ol>
<li>
@@ -2022,7 +2022,7 @@
<p> Use <kbd>C-h s</kbd> (<code>describe-syntax</code>) to display a
description of
the contents of the current syntax table. The description of each
character includes both the string you have to pass to
-<code>modify-syntax-entry</code> to set up that character's current syntax,
+<code>modify-syntax-entry</code> to set up that character’s current
syntax,
and some English to explain that string if necessary.
</p>
<hr size="6">
@@ -2147,15 +2147,15 @@
</p>
</dd>
<dt> True</dt>
-<dd><p><code>t</code> stands for `true'.
+<dd><p><code>t</code> stands for ‘true’.
</p>
</dd>
<dt> False</dt>
-<dd><p><code>nil</code> stands for `false'.
+<dd><p><code>nil</code> stands for ‘false’.
</p>
</dd>
<dt> Other Lisp objects</dt>
-<dd><p>Write a single-quote (') followed by the Lisp object you want.
+<dd><p>Write a single-quote (’) followed by the Lisp object you want.
</p></dd>
</dl>
@@ -2191,8 +2191,8 @@
<table><tr><td> </td><td><pre class="example">(setq c-tab-always-indent
nil)
</pre></td></tr></table>
-<p>Here we have a variable whose value is normally <code>t</code> for `true'
-and the alternative is <code>nil</code> for `false'.
+<p>Here we have a variable whose value is normally <code>t</code> for
‘true’
+and the alternative is <code>nil</code> for ‘false’.
</p>
</li><li>
Make searches case sensitive by default (in all buffers that do not
@@ -2203,7 +2203,7 @@
<p>This sets the default value, which is effective in all buffers that do
not have local values for the variable. Setting <code>case-fold-search</code>
-with <code>setq</code> affects only the current buffer's local value, which
+with <code>setq</code> affects only the current buffer’s local value,
which
is probably not what you want to do in an init file.
</p>
</li><li>
@@ -2354,7 +2354,7 @@
kept.
</p>
<p> The usual purpose of the terminal-specific library is to define the
-escape sequences used by the terminal's function keys using the library
+escape sequences used by the terminal’s function keys using the library
‘<tt>keypad.el</tt>’. See the file
‘<tt>term/vt100.el</tt>’ for an example of how this is done.
</p>
@@ -2365,7 +2365,7 @@
<code>(getenv "TERM")</code> to find the full terminal type name.
</p>
<a name="IDX1532"></a>
-<p> The library's name is constructed by concatenating the value of the
+<p> The library’s name is constructed by concatenating the value of the
variable <code>term-file-prefix</code> and the terminal type. Your init
file can prevent the loading of the terminal-specific library by setting
<code>term-file-prefix</code> to <code>nil</code>. See section <a
href="#SEC377">The Init File</a>.
@@ -2402,7 +2402,7 @@
<p>You can now change how the audible bell sounds using the variable
<code>sound-alist</code>.
</p>
-<p><code>sound-alist</code>'s value is an list associating symbols with, among
+<p><code>sound-alist</code>’s value is an list associating symbols with,
among
other things, strings of audio-data. When <code>ding</code> is called with
one of the symbols, the associated sound data is played instead of the
standard beep. This only works if you are logged in on the console of a
@@ -2435,7 +2435,7 @@
</p></dd>
</dl>
-<p>For compatibility, elements of `sound-alist' may also be of the form:
+<p>For compatibility, elements of ‘sound-alist’ may also be of the
form:
</p>
<table><tr><td> </td><td><pre class="example">( <var>sound-name</var> .
<var><sound></var> )
( <var>sound-name</var> <var><volume></var> <var><sound></var> )
@@ -2449,7 +2449,7 @@
time means a Sun SparcStation, SGI, or HP9000s700.
</p>
<p>Also note that the pitch, duration, and volume options are available
-everywhere, but most X servers ignore the `pitch' option.
+everywhere, but most X servers ignore the ‘pitch’ option.
</p>
<a name="IDX1535"></a>
<p>The variable <code>bell-volume</code> should be an integer from 0 to 100,
@@ -2982,8 +2982,8 @@
vertical scrollbars. You can also use a resource specification of the
form <code>*scrollbar.width</code>, or the usual toolkit scrollbar resources:
<code>*XmScrollBar.width</code> (Motif), <code>*XlwScrollBar.width</code>
(Lucid),
-or <code>*Scrollbar.thickness</code> (Athena). We don't recommend that you
-use the toolkit resources, though, because they're dependent on how
+or <code>*Scrollbar.thickness</code> (Athena). We don’t recommend that
you
+use the toolkit resources, though, because they’re dependent on how
exactly your particular build of XEmacs was configured.
</p>
</dd>
@@ -2992,8 +2992,8 @@
horizontal scrollbars. You can also use a resource specification of the
form <code>*scrollbar.height</code>, or the usual toolkit scrollbar resources:
<code>*XmScrollBar.height</code> (Motif), <code>*XlwScrollBar.height</code>
(Lucid),
-or <code>*Scrollbar.thickness</code> (Athena). We don't recommend that you use
-the toolkit resources, though, because they're dependent on how exactly
+or <code>*Scrollbar.thickness</code> (Athena). We don’t recommend that
you use
+the toolkit resources, though, because they’re dependent on how exactly
your particular build of XEmacs was configured.
</p>
</dd>
@@ -3210,7 +3210,7 @@
<dt> <code>info-xref</code></dt>
<dd><p>This is the face of info cross-references. If unspecified, it is copied
from <code>bold</code>. (Note that, when the mouse passes over a
-cross-reference, the cross-reference's face is determined from a
+cross-reference, the cross-reference’s face is determined from a
combination of the <code>info-xref</code> and <code>highlight</code> faces.)
</p></dd>
</dl>
@@ -3237,7 +3237,7 @@
9x13
</pre></td></tr></table>
-<p>then XEmacs won't be able to guess the names of the bold and italic
+<p>then XEmacs won’t be able to guess the names of the bold and italic
versions. All X fonts can be referred to via XLFD-style names, so you
should use those forms. See the man pages for ‘<samp>X(1)</samp>’,
‘<samp>xlsfonts(1)</samp>’, and
‘<samp>xfontsel(1)</samp>’.
@@ -3383,7 +3383,7 @@
<a name="IDX1551"></a>
<a name="IDX1552"></a>
<p> Quitting with <kbd>C-g</kbd> is used for getting rid of a partially typed
-command or a numeric argument that you don't want. It also stops a
+command or a numeric argument that you don’t want. It also stops a
running command in the middle in a relatively safe way, so you can use
it if you accidentally start executing a command that takes a long
time. In particular, it is safe to quit out of killing; either your
@@ -3453,7 +3453,7 @@
and how to recognize them and correct them.
</p>
<table class="menu" border="0" cellspacing="0">
-<tr><td align="left" valign="top"><a href="#SEC394">27.12.1 Recursive Editing
Levels</a></td><td> </td><td align="left" valign="top"> `[...]'
in mode line around the parentheses.
+<tr><td align="left" valign="top"><a href="#SEC394">27.12.1 Recursive Editing
Levels</a></td><td> </td><td align="left" valign="top">
‘[...]’ in mode line around the parentheses.
</td></tr>
<tr><td align="left" valign="top"><a href="#SEC395">27.12.2 Garbage on the
Screen</a></td><td> </td><td align="left" valign="top"> Garbage
on the screen.
</td></tr>
@@ -3464,7 +3464,7 @@
<tr><td align="left" valign="top"><a href="#SEC398">27.12.5 Emergency
Escape</a></td><td> </td><td align="left" valign="top"> Emergency
escape—
What to do if Emacs stops responding.
</td></tr>
-<tr><td align="left" valign="top"><a href="#SEC399">27.12.6 Help for Total
Frustration</a></td><td> </td><td align="left" valign="top"> When
you are at your wits' end.
+<tr><td align="left" valign="top"><a href="#SEC399">27.12.6 Help for Total
Frustration</a></td><td> </td><td align="left" valign="top"> When
you are at your wits’ end.
</td></tr>
</table>
@@ -3495,7 +3495,7 @@
<p> If the mode line has square brackets
‘<samp>[…]</samp>’ around the parentheses
that contain the names of the major and minor modes, you have entered a
recursive editing level. If you did not do this on purpose, or if you
-don't understand what that means, you should just get out of the recursive
+don’t understand what that means, you should just get out of the
recursive
editing level. To do so, type <kbd>M-x top-level</kbd>. This is called
getting
back to top level. See section <a href="xemacs_29.html#SEC346">Recursive
Editing Levels</a>.
</p>
@@ -3751,11 +3751,11 @@
case of incorrect display updating.
</p>
<p> Taking forever to complete a command can be a bug, but you must make
-certain that it was really Emacs's fault. Some commands simply take a long
+certain that it was really Emacs’s fault. Some commands simply take a
long
time. Type <kbd>C-g</kbd> and then <kbd>C-h l</kbd> to see whether the input
Emacs
received was what you intended to type; if the input was such that you
<var>know</var> it should have been processed quickly, report a bug. If you
-don't know whether the command should take a long time, find out by looking
+don’t know whether the command should take a long time, find out by
looking
in the manual or by asking for assistance.
</p>
<p> If a command you are familiar with causes an Emacs error message in a
@@ -3763,12 +3763,12 @@
bug.
</p>
<p> If a command does the wrong thing, that is a bug. But be sure you know
-for certain what it ought to have done. If you aren't familiar with the
-command, or don't know for certain how the command is supposed to work,
+for certain what it ought to have done. If you aren’t familiar with the
+command, or don’t know for certain how the command is supposed to work,
then it might actually be working right. Rather than jumping to
conclusions, show the problem to someone who knows for certain.
</p>
-<p> Finally, a command's intended definition may not be best for editing
+<p> Finally, a command’s intended definition may not be best for editing
with. This is a very important sort of problem, but it is also a matter of
judgment. Also, it is easy to come to such a conclusion out of ignorance
of some of the existing features. It is probably best not to complain
@@ -3777,7 +3777,7 @@
you want is not available. If you are not sure what the command is
supposed to do after a careful reading of the manual, check the index and
glossary for any terms that may be unclear. If you still do not
-understand, this indicates a bug in the manual. The manual's job is to
+understand, this indicates a bug in the manual. The manual’s job is to
make everything clear. It is just as important to report documentation
bugs as program bugs.
</p>
@@ -3855,10 +3855,10 @@
backtrace, you must execute the Lisp expression
<code>(setq debug-on-error t)</code> before the error happens (that is to
say, you must execute that expression and then make the bug happen). This
-causes the Lisp debugger to run (see section <a
href="xemacs_25.html#SEC259">The Emacs-Lisp Debugger</a>). The debugger's
+causes the Lisp debugger to run (see section <a
href="xemacs_25.html#SEC259">The Emacs-Lisp Debugger</a>). The debugger’s
backtrace can be copied as text into the bug report. This use of the
debugger is possible only if you know how to make the bug happen again. Do
-note the error message the first time the bug happens, so if you can't make
+note the error message the first time the bug happens, so if you can’t
make
it happen again, you can report at least that.
</p>
<p> Check whether any programs you have loaded into the Lisp world, including
@@ -3919,7 +3919,7 @@
<p>The newsgroup ‘<samp>comp.emacs.xemacs</samp>’ may be used for
bug reports,
other discussions and requests for assistance.
</p>
-<p>If you don't have access to this newgroup, you can subscribe to the
+<p>If you don’t have access to this newgroup, you can subscribe to the
mailing list version: the newsgroup is bidirectionally gatewayed into
the mailing list ‘<samp>address@hidden</samp>’.
</p>
Index: Tests/xemacs_frame_res/xemacs_31.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/xemacs_frame_res/xemacs_31.html,v
retrieving revision 1.23
retrieving revision 1.24
diff -u -b -r1.23 -r1.24
--- Tests/xemacs_frame_res/xemacs_31.html 5 Feb 2007 15:30:27 -0000
1.23
+++ Tests/xemacs_frame_res/xemacs_31.html 3 Oct 2007 09:34:55 -0000
1.24
@@ -120,7 +120,7 @@
<dt> Buffer</dt>
<dd><p>The buffer is the basic editing unit; one buffer corresponds to one
piece of text being edited. You can have several buffers, but at any
-time you are editing only one, the `selected' buffer, though several
+time you are editing only one, the ‘selected’ buffer, though
several
buffers can be visible when you are using multiple windows. See section <a
href="xemacs_18.html#SEC169">Using Multiple Buffers</a>.
</p>
</dd>
@@ -245,8 +245,8 @@
<dd><p>The cursor is the rectangle on the screen which indicates the position
called point (q.v.) at which insertion and deletion takes place.
The cursor is on or under the character that follows point. Often
-people speak of `the cursor' when, strictly speaking, they mean
-`point'. See section <a href="xemacs_7.html#SEC49">Basic Editing</a>.
+people speak of ‘the cursor’ when, strictly speaking, they mean
+‘point’. See section <a href="xemacs_7.html#SEC49">Basic
Editing</a>.
</p>
</dd>
<dt> Customization</dt>
@@ -264,7 +264,7 @@
</dd>
<dt> Default Directory</dt>
<dd><p>When you specify a file name that does not start with
‘<samp>/</samp>’ or ‘<samp>~</samp>’,
-it is interpreted relative to the current buffer's default directory.
+it is interpreted relative to the current buffer’s default directory.
See section <a href="xemacs_9.html#SEC61">Default Directory</a>.
</p>
</dd>
@@ -380,7 +380,7 @@
</p>
</dd>
<dt> Frame</dt>
-<dd><p>When running Emacs on a TTY terminal, “frame” means the
terminal's
+<dd><p>When running Emacs on a TTY terminal, “frame” means the
terminal’s
screen. When running Emacs under X, you can have multiple frames,
each corresponding to a top-level X window and each looking like
the screen on a TTY. Each frame contains one or more non-overlapping
@@ -389,9 +389,9 @@
</p>
</dd>
<dt> Global</dt>
-<dd><p>Global means `independent of the current environment; in effect
-<br>throughout Emacs'. It is the opposite of local (q.v.).
-Examples of the use of `global' appear below.
+<dd><p>Global means ‘independent of the current environment; in effect
+<br>throughout Emacs’. It is the opposite of local (q.v.).
+Examples of the use of ‘global’ appear below.
</p>
</dd>
<dt> Global Abbrev</dt>
@@ -402,7 +402,7 @@
</dd>
<dt> Global Keymap</dt>
<dd><p>The global keymap (q.v.) contains key bindings that are in effect
-unless local key bindings in a major mode's local
+unless local key bindings in a major mode’s local
keymap (q.v.) override them.See section <a
href="xemacs_30.html#SEC368">Keymaps</a>.
</p>
</dd>
@@ -516,10 +516,10 @@
</p>
</dd>
<dt> Local</dt>
-<dd><p>Local means `in effect only in a particular context'; the relevant
+<dd><p>Local means ‘in effect only in a particular context’; the
relevant
kind of context is a particular function execution, a particular
-buffer, or a particular major mode. Local is the opposite of `global'
-(q.v.). Specific uses of `local' in Emacs terminology appear below.
+buffer, or a particular major mode. Local is the opposite of
‘global’
+(q.v.). Specific uses of ‘local’ in Emacs terminology appear
below.
</p>
</dd>
<dt> Local Abbrev</dt>
@@ -561,7 +561,7 @@
</dd>
<dt> Mail</dt>
<dd><p>Mail means messages sent from one user to another through the computer
-system, to be read at the recipient's convenience. Emacs has commands for
+system, to be read at the recipient’s convenience. Emacs has commands
for
composing and sending mail, and for reading and editing the mail you have
received. See section <a href="xemacs_28.html#SEC296">Sending Mail</a>.
</p>
@@ -585,7 +585,7 @@
</p>
</dd>
<dt> Message</dt>
-<dd><p>See `mail'.
+<dd><p>See ‘mail’.
</p>
</dd>
<dt> Meta</dt>
@@ -690,7 +690,7 @@
<dt> Point</dt>
<dd><p>Point is the place in the buffer at which insertion and deletion
occur. Point is considered to be between two characters, not at one
-character. The terminal's cursor (q.v.) indicates the location of
+character. The terminal’s cursor (q.v.) indicates the location of
point. See section <a href="xemacs_7.html#SEC49">Point</a>.
</p>
</dd>
@@ -749,7 +749,7 @@
</p>
</dd>
<dt> Regexp</dt>
-<dd><p>See `regular expression'.
+<dd><p>See ‘regular expression’.
</p>
</dd>
<dt> Region</dt>
@@ -769,11 +769,11 @@
</p>
</dd>
<dt> Replacement</dt>
-<dd><p>See `global substitution'.
+<dd><p>See ‘global substitution’.
</p>
</dd>
<dt> Restriction</dt>
-<dd><p>A buffer's restriction is the amount of text, at the beginning or the
+<dd><p>A buffer’s restriction is the amount of text, at the beginning or
the
end of the buffer, that is temporarily invisible and inaccessible.
Giving a buffer a nonzero amount of restriction is called narrowing
(q.v.). See section <a href="xemacs_29.html#SEC344">Narrowing</a>.
@@ -819,10 +819,10 @@
</p>
</dd>
<dt> Sexp</dt>
-<dd><p>An sexp (short for `s-expression,' itself short for `symbolic
-expression') is the basic syntactic unit of Lisp
+<dd><p>An sexp (short for ‘s-expression,’ itself short for
‘symbolic
+expression’) is the basic syntactic unit of Lisp
in its textual form: either a list, or Lisp atom. Many Emacs commands
-operate on sexps. The term `sexp' is generalized to languages other
+operate on sexps. The term ‘sexp’ is generalized to languages
other
than Lisp to mean a syntactically recognizable expression.
See section <a href="xemacs_24.html#SEC217">Sexps</a>.
</p>
@@ -847,7 +847,7 @@
</p>
</dd>
<dt> String Substitution</dt>
-<dd><p>See `global substitution'.
+<dd><p>See ‘global substitution’.
</p>
</dd>
<dt> Syntax Table</dt>
@@ -901,7 +901,7 @@
<dt> Truncation</dt>
<dd><p>Truncating text lines in the display means leaving out any text on a
line that does not fit within the right margin of the window
-displaying it. See also `continuation line'.
+displaying it. See also ‘continuation line’.
See section <a href="xemacs_7.html#SEC49">Basic Editing</a>.
</p>
</dd>
@@ -913,7 +913,7 @@
</dd>
<dt> Variable</dt>
<dd><p>A variable is Lisp object that can store an arbitrary value. Emacs uses
-some variables for internal purposes, and has others (known as `options'
+some variables for internal purposes, and has others (known as
‘options’
(q.v.)) you can set to control the behavior of Emacs. The variables
used in Emacs that you are likely to be interested in are listed in the
Variables Index of this manual. See section <a
href="xemacs_30.html#SEC353">Variables</a>, for information on
@@ -946,7 +946,7 @@
</p>
</dd>
<dt> Word Abbrev</dt>
-<dd><p>Synonymous with `abbrev'.
+<dd><p>Synonymous with ‘abbrev’.
</p>
</dd>
<dt> Word Search</dt>
Index: Tests/xemacs_frame_res/xemacs_32.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/xemacs_frame_res/xemacs_32.html,v
retrieving revision 1.20
retrieving revision 1.21
diff -u -b -r1.20 -r1.21
--- Tests/xemacs_frame_res/xemacs_32.html 5 Feb 2007 15:30:27 -0000
1.20
+++ Tests/xemacs_frame_res/xemacs_32.html 3 Oct 2007 09:34:55 -0000
1.21
@@ -79,9 +79,9 @@
<td valign="middle" align="left">[<a href="xemacs_33.html#SEC413"
title="Index">Index</a>]</td>
<td valign="middle" align="left">[<a href="xemacs_abt.html#SEC_About"
title="About (help)"> ? </a>]</td>
</tr></table>
-<h2 class="unnumberedsec"> What's GNU? GNU's Not Unix! </h2>
+<h2 class="unnumberedsec"> What’s GNU? GNU’s Not Unix! </h2>
-<p>GNU, which stands for GNU's Not Unix, is the name for the complete
+<p>GNU, which stands for GNU’s Not Unix, is the name for the complete
Unix-compatible software system which I am writing so that I can give it
away free to everyone who can use it. Several other volunteers are helping
me. Contributions of time, money, programs, and equipment are greatly
@@ -115,7 +115,7 @@
effort to make it run on smaller machines will be left to someone who wants
to use it on them.
</p>
-<p>To avoid horrible confusion, please pronounce the `G' in the word `GNU'
+<p>To avoid horrible confusion, please pronounce the ‘G’ in the
word ‘GNU’
when it is the name of this project.
</p>
@@ -266,7 +266,7 @@
<h2 class="unnumberedsec"> How You Can Contribute </h2>
<p>I am asking computer manufacturers for donations of machines and money.
-I'm asking individuals for donations of programs and work.
+I’m asking individuals for donations of programs and work.
</p>
<p>One consequence you can expect if you donate machines is that GNU will run
on them at an early date. The machines should be complete, ready-to-use
@@ -287,7 +287,7 @@
communication and will be worked on by a small, tight group.)
</p>
<p>If I get donations of money, I may be able to hire a few people full or
-part time. The salary won't be high by programmers' standards, but I'm
+part time. The salary won’t be high by programmers’ standards,
but I’m
looking for people for whom building community spirit is as important as
making money. I view this as a way of enabling dedicated people to devote
their full energies to working on GNU by sparing them the need to make a
@@ -328,7 +328,7 @@
sources and is in sole position to make changes.
</p>
<p>Schools will be able to provide a much more educational environment by
-encouraging all students to study and improve the system code. Harvard's
+encouraging all students to study and improve the system code. Harvard’s
computer lab used to have the policy that no program could be installed on
the system if its sources were not on public display, and upheld it by
actually refusing to install certain programs. I was very much inspired by
@@ -345,7 +345,7 @@
cost: charging each breather per liter of air may be fair, but wearing the
metered gas mask all day and all night is intolerable even if everyone can
afford to pay the air bill. And the TV cameras everywhere to see if you
-ever take the mask off are outrageous. It's better to support the air
+ever take the mask off are outrageous. It’s better to support the air
plant with a head tax and chuck the masks.
</p>
<p>Copying all or parts of a program is as natural to a programmer as
@@ -369,9 +369,9 @@
<td valign="middle" align="left">[<a href="xemacs_33.html#SEC413"
title="Index">Index</a>]</td>
<td valign="middle" align="left">[<a href="xemacs_abt.html#SEC_About"
title="About (help)"> ? </a>]</td>
</tr></table>
-<h2 class="unnumberedsec"> Some Easily Rebutted Objections to GNU's Goals </h2>
+<h2 class="unnumberedsec"> Some Easily Rebutted Objections to GNU’s
Goals </h2>
-<blockquote><p>“Nobody will use it if it is free, because that means
they can't rely
+<blockquote><p>“Nobody will use it if it is free, because that means
they can’t rely
on any support.”
</p>
<p>“You have to charge for the program to pay for providing the
@@ -393,11 +393,11 @@
With Unix, the price of sources puts this out of consideration for most
businesses. With GNU this will be easy. It is still possible for there to
be no available competent person, but this problem cannot be blamed on
-distribution arrangements. GNU does not eliminate all the world's problems,
+distribution arrangements. GNU does not eliminate all the world’s
problems,
only some of them.
</p>
<p>Meanwhile, the users who know nothing about computers need handholding:
-doing things for them which they could easily do themselves but don't know
+doing things for them which they could easily do themselves but don’t
know
how.
</p>
<p>Such services could be provided by companies that sell just hand-holding
@@ -405,13 +405,13 @@
get a product with service, they will also be willing to buy the service
having got the product free. The service companies will compete in quality
and price; users will not be tied to any particular one. Meanwhile, those
-of us who don't need the service should be able to use the program without
+of us who don’t need the service should be able to use the program
without
paying for the service.
</p>
<blockquote><p>“You cannot reach many people without advertising,
and you must charge for the program to support that.”
</p>
-<p>“It's no use advertising a program people can get free.”
+<p>“It’s no use advertising a program people can get free.”
</p></blockquote>
<p>There are various forms of free or very cheap publicity that can be used to
@@ -423,8 +423,8 @@
advertising pay for it.
</p>
<p>On the other hand, if many people get GNU from their friends, and such
-companies don't succeed, this will show that advertising was not really
-necessary to spread GNU. Why is it that free market advocates don't want
+companies don’t succeed, this will show that advertising was not really
+necessary to spread GNU. Why is it that free market advocates don’t want
to let the free market decide this?
</p><blockquote><p>“My company needs a proprietary operating system
@@ -435,14 +435,14 @@
You will not be able to get an edge in this area, but neither will your
competitors be able to get an edge over you. You and they will compete in
other areas, while benefitting mutually in this one. If your business is
-selling an operating system, you will not like GNU, but that's tough on
+selling an operating system, you will not like GNU, but that’s tough on
you. If your business is something else, GNU can save you from being
pushed into the expensive business of selling operating systems.
</p>
<p>I would like to see GNU development supported by gifts from many
manufacturers and users, reducing the cost to each.
</p>
-<blockquote><p>“Don't programmers deserve a reward for their
creativity?”
+<blockquote><p>“Don’t programmers deserve a reward for their
creativity?”
</p></blockquote>
<p>If anything deserves a reward, it is social contribution. Creativity can
@@ -451,11 +451,11 @@
programs, by the same token they deserve to be punished if they restrict
the use of these programs.
</p>
-<blockquote><p>“Shouldn't a programmer be able to ask for a reward for
his creativity?”
+<blockquote><p>“Shouldn’t a programmer be able to ask for a reward
for his creativity?”
</p></blockquote>
<p>There is nothing wrong with wanting pay for work, or seeking to maximize
-one's income, as long as one does not use means that are destructive. But
+one’s income, as long as one does not use means that are destructive.
But
the means customary in the field of software today are based on
destruction.
</p>
@@ -470,10 +470,10 @@
mutual destructiveness. This is Kantian ethics; or, the Golden Rule.
Since I do not like the consequences that result if everyone hoards
information, I am required to consider it wrong for one to do so.
-Specifically, the desire to be rewarded for one's creativity does not
+Specifically, the desire to be rewarded for one’s creativity does not
justify depriving the world in general of all or part of that creativity.
</p>
-<blockquote><p>“Won't programmers starve?”
+<blockquote><p>“Won’t programmers starve?”
</p></blockquote>
<p>I could answer that nobody is forced to be a programmer. Most of us cannot
@@ -481,7 +481,7 @@
we are not, as a result, condemned to spend our lives standing on the
street making faces, and starving. We do something else.
</p>
-<p>But that is the wrong answer because it accepts the questioner's implicit
+<p>But that is the wrong answer because it accepts the questioner’s
implicit
assumption: that without ownership of software, programmers cannot possibly
be paid a cent. Supposedly it is all or nothing.
</p>
@@ -501,11 +501,11 @@
programmers made the same, that would not be an injustice either. (In
practice they would still make considerably more than that.)
</p>
-<blockquote><p>“Don't people have a right to control how their
creativity is used?”
+<blockquote><p>“Don’t people have a right to control how their
creativity is used?”
</p></blockquote>
-<p>“Control over the use of one's ideas” really constitutes
control over
-other people's lives; and it is usually used to make their lives more
+<p>“Control over the use of one’s ideas” really constitutes
control over
+other people’s lives; and it is usually used to make their lives more
difficult.
</p>
<p>People who have studied the issue of intellectual property rights carefully
@@ -525,7 +525,7 @@
</p>
<p>The idea of copyright did not exist in ancient times, when authors
frequently copied other authors at length in works of non-fiction. This
-practice was useful, and is the only way many authors' works have survived
+practice was useful, and is the only way many authors’ works have
survived
even in part. The copyright system was created expressly for the purpose
of encouraging authorship. In the domain for which it was
invented—books, which could be copied economically only on a printing
@@ -559,12 +559,12 @@
all finish late.
</p>
<p>Proprietary and secret software is the moral equivalent of runners in a
-fist fight. Sad to say, the only referee we've got does not seem to
+fist fight. Sad to say, the only referee we’ve got does not seem to
object to fights; he just regulates them (“For every ten yards you run,
you can fire one shot”). He really ought to break them up, and penalize
runners for even trying to fight.
</p>
-<blockquote><p>“Won't everyone stop programming without a monetary
incentive?”
+<blockquote><p>“Won’t everyone stop programming without a monetary
incentive?”
</p></blockquote>
<p>Actually, many people will program with absolutely no monetary incentive.
@@ -577,7 +577,7 @@
the right question is, will anyone program with a reduced monetary
incentive? My experience shows that they will.
</p>
-<p>For more than ten years, many of the world's best programmers worked at the
+<p>For more than ten years, many of the world’s best programmers worked
at the
Artificial Intelligence Lab for far less money than they could have had
anywhere else. They got many kinds of non-monetary rewards: fame and
appreciation, for example. And creativity is also fun, a reward in itself.
@@ -595,7 +595,7 @@
stop helping our neighbors, we have to obey.”
</p></blockquote>
-<p>You're never so desperate that you have to obey this sort of demand.
+<p>You’re never so desperate that you have to obey this sort of demand.
Remember: millions for defense, but not a cent for tribute!
</p>
<blockquote><p>“Programmers need to make a living somehow.”
@@ -617,9 +617,9 @@
donations from satisfied users or sell hand-holding services. I have
met people who are already working this way successfully.
</p>
-<p>Users with related needs can form users' groups and pay dues. A group
+<p>Users with related needs can form users’ groups and pay dues. A group
would contract with programming companies to write programs that the
-group's members would like to use.
+group’s members would like to use.
</p>
<p>All sorts of development can be funded with a Software Tax:
</p>
Index: Tests/xemacs_frame_res/xemacs_4.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/xemacs_frame_res/xemacs_4.html,v
retrieving revision 1.26
retrieving revision 1.27
diff -u -b -r1.26 -r1.27
--- Tests/xemacs_frame_res/xemacs_4.html 5 Feb 2007 15:30:27 -0000
1.26
+++ Tests/xemacs_frame_res/xemacs_4.html 3 Oct 2007 09:34:55 -0000
1.27
@@ -90,7 +90,7 @@
consist of one window or of two or more windows if you need to look at two
buffers a the same time.
</li><li>
-Below each text window's last line is a <em>mode line</em> (see section <a
href="#SEC10">The Mode Line</a>), which describes what is going on in that
window. The mode line
+Below each text window’s last line is a <em>mode line</em> (see section
<a href="#SEC10">The Mode Line</a>), which describes what is going on in that
window. The mode line
is in inverse video if the terminal supports that. If there are several
XEmacs windows in one frame, each window has its own mode line.
</li><li>
@@ -203,9 +203,9 @@
the same buffer appears in more than one window, point can be moved in
each window independently.
</p>
-<p> The term `point' comes from the character ‘<samp>.</samp>’,
which was the
+<p> The term ‘point’ comes from the character
‘<samp>.</samp>’, which was the
command in TECO (the language in which the original Emacs was written)
-for accessing the value now called `point'.
+for accessing the value now called ‘point’.
</p>
<hr size="6">
<a name="Echo-Area"></a>
@@ -288,7 +288,7 @@
</tr></table>
<h2 class="section"> 1.3 The Mode Line </h2>
-<p> Each text window's last line is a <em>mode line</em> which describes what
is
+<p> Each text window’s last line is a <em>mode line</em> which
describes what is
going on in that window. When there is only one text window, the mode line
appears right above the echo area. The mode line is in inverse video if
the terminal supports that, starts and ends with dashes, and contains text
@@ -305,7 +305,7 @@
</pre></td></tr></table>
<p>This gives information about the buffer being displayed in the window: the
-buffer's name, what major and minor modes are in use, whether the buffer's
+buffer’s name, what major and minor modes are in use, whether the
buffer’s
text has been changed, and how far down the buffer you are currently
looking.
</p>
@@ -314,9 +314,9 @@
buffer has not been edited. Exception: for a read-only buffer, it is
‘<samp>%%</samp>’.
</p>
-<p> <var>buf</var> is the name of the window's chosen <em>buffer</em>. The
chosen
+<p> <var>buf</var> is the name of the window’s chosen <em>buffer</em>.
The chosen
buffer in the selected window (the window that the cursor is in) is also
-XEmacs's selected buffer, the buffer in which editing takes place. When
+XEmacs’s selected buffer, the buffer in which editing takes place. When
we speak of what some command does to “the buffer”, we mean the
currently selected buffer. See section <a href="xemacs_18.html#SEC169">Using
Multiple Buffers</a>.
</p>
@@ -335,7 +335,7 @@
on how the modes differ and how you select one.
</p>
<p> <var>minor</var> is a list of some of the <em>minor modes</em> that are
turned on
-in the window's chosen buffer. For example, ‘<samp>Fill</samp>’
means that Auto
+in the window’s chosen buffer. For example,
‘<samp>Fill</samp>’ means that Auto
Fill mode is on. <code>Abbrev</code> means that Word Abbrev mode is on.
<code>Ovwrt</code> means that Overwrite mode is on. See section <a
href="xemacs_30.html#SEC352">Minor Modes</a>, for more
information. ‘<samp>Narrow</samp>’ means that the buffer being
displayed has
@@ -425,7 +425,7 @@
</td></tr>
<tr><td align="left" valign="top"><a href="#SEC16">1.9 XEmacs
Gutters</a></td><td> </td><td align="left" valign="top"> How
XEmacs uses gutters.
</td></tr>
-<tr><td align="left" valign="top"><a href="#SEC17">1.10 Inhibiting Display of
GUI Components</a></td><td> </td><td align="left" valign="top">
What if you don't like GUI?
+<tr><td align="left" valign="top"><a href="#SEC17">1.10 Inhibiting Display of
GUI Components</a></td><td> </td><td align="left" valign="top">
What if you don’t like GUI?
</td></tr>
<tr><td align="left" valign="top"><a href="#SEC18">1.11 Changing the Position,
Orientation, and Appearance of GUI Components</a></td><td> </td><td
align="left" valign="top"> Position, orientation, and appearance of GUI
objects.
</td></tr>
@@ -547,7 +547,7 @@
<p>Additionally, a modeline can be dragged horizontally, in which case it
scrolls its own text. This behavior is not enabled by default because it
could be considered as disturbing when dragging vertically. When this
-behavior is enabled, the modeline's text can be dragged either in the
+behavior is enabled, the modeline’s text can be dragged either in the
same direction as the mouse, or in the opposite sense, making the
modeline act as a scrollbar for its own text.
</p>
@@ -633,7 +633,7 @@
</p>
<p>Then "uninteresting" buffers, like internal XEmacs buffers, the
<code>*Message Log*</code> buffer, and so on are deleted from the list. Next,
-the frame's selected buffer is determined. Buffers with a different
+the frame’s selected buffer is determined. Buffers with a different
major mode from the selected buffer are removed from the list. Finally,
if the list is too long, the least recently used buffers are deleted
from the list. By default up to 6 most recently used buffers with the
@@ -683,7 +683,7 @@
<code>scrollbars-visible-p</code>, <code>toolbar-visible-p</code>, or
<code>gutter-buffers-tab-visible-p</code> respectively. (The strange form of
the last variable is due to the fact that gutters are often used to
-display transient widgets like progress gauges, which you probably don't
+display transient widgets like progress gauges, which you probably don’t
want to inhibit. It is more likely that you want to inhibit the default
display of the buffers tab widget, which is what that variable controls.
This interface is subject to change depending on developer experience
@@ -745,7 +745,7 @@
<p>XEmacs can be used with the X Window System and a window manager like
MWM or TWM. In that case, the X window manager opens, closes, and
-resizes XEmacs frames. You use the window manager's mouse gestures to
+resizes XEmacs frames. You use the window manager’s mouse gestures to
perform the operations. Consult your window manager guide or reference
manual for information on manipulating X windows.
</p>
@@ -821,7 +821,7 @@
</li><li>
There is a new frame/modeline format directive, %S, which expands to
-the name of the current frame (a frame's name is distinct from its
+the name of the current frame (a frame’s name is distinct from its
title; the name is used for resource lookup, among other things, and the
title is simply what appears above the window.)
</li></ul>
Index: Tests/xemacs_frame_res/xemacs_5.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/xemacs_frame_res/xemacs_5.html,v
retrieving revision 1.27
retrieving revision 1.28
diff -u -b -r1.27 -r1.28
--- Tests/xemacs_frame_res/xemacs_5.html 5 Feb 2007 15:30:27 -0000
1.27
+++ Tests/xemacs_frame_res/xemacs_5.html 3 Oct 2007 09:34:55 -0000
1.28
@@ -279,7 +279,7 @@
</p></dd>
<dt> <kbd>[(control c) (control 65)]</kbd></dt>
<dd><p>Typing <kbd>C-c</kbd> followed by <kbd>C-a</kbd>. (Using the ASCII code
-for the character `a')
+for the character ‘a’)
</p></dd>
<dt> <kbd>[(control c) (break)]</kbd></dt>
<dd><p>Typing <kbd>C-c</kbd> followed by the <kbd>break</kbd> character.
@@ -690,7 +690,7 @@
</p>
<a name="IDX44"></a>
<p> While we are on the subject of information for customization only,
-it's a good time to tell you about <em>variables</em>. Often the
+it’s a good time to tell you about <em>variables</em>. Often the
description of a command will say, “To change this, set the variable
<code>mumble-foo</code>.” A variable is a name used to remember a value.
Most of the variables documented in this manual exist just to facilitate
Index: Tests/xemacs_frame_res/xemacs_6.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/xemacs_frame_res/xemacs_6.html,v
retrieving revision 1.27
retrieving revision 1.28
diff -u -b -r1.27 -r1.28
--- Tests/xemacs_frame_res/xemacs_6.html 5 Feb 2007 15:30:27 -0000
1.27
+++ Tests/xemacs_frame_res/xemacs_6.html 3 Oct 2007 09:34:55 -0000
1.28
@@ -89,7 +89,7 @@
</p>
<p> It is possible to specify files to be visited, Lisp files to be
loaded, and functions to be called, by giving Emacs arguments in the
-shell command line. See section <a href="#SEC41">Command Line Switches and
Arguments</a>. But we don't recommend
+shell command line. See section <a href="#SEC41">Command Line Switches and
Arguments</a>. But we don’t recommend
doing this. The feature exists mainly for compatibility with other
editors.
</p>
@@ -101,7 +101,7 @@
</p>
<p> But starting a new Emacs each time you want to edit a different file
does not make sense. For one thing, this would be annoyingly slow. For
-another, this would fail to take advantage of Emacs's ability to visit
+another, this would fail to take advantage of Emacs’s ability to visit
more than one file in a single editing session. And it would lose the
other accumulated context, such as registers, undo history, and the mark
ring.
@@ -185,11 +185,11 @@
you use.) The only way on these systems to get back to the shell from
which Emacs was run (to log out, for example) is to kill Emacs.
</p>
-<p> Suspending also fails if you run Emacs under a shell that doesn't
+<p> Suspending also fails if you run Emacs under a shell that doesn’t
support suspending programs, even if the system itself does support it.
In such a case, you can set the variable <code>cannot-suspend</code> to a
non-<code>nil</code> value to force <kbd>C-z</kbd> to start an inferior shell.
-(One might also describe Emacs's parent shell as “inferior” for
+(One might also describe Emacs’s parent shell as “inferior”
for
failing to support job control properly, but that is a matter of taste.)
</p>
<p> When Emacs communicates directly with an X server and creates its own
@@ -396,14 +396,14 @@
<dl compact="compact">
<dt> ‘<samp>--show-dump-id</samp>’</dt>
<dt> ‘<samp>-sd</samp>’</dt>
-<dd><p>Print the ID for the new portable dumper's dump file on the terminal and
+<dd><p>Print the ID for the new portable dumper’s dump file on the
terminal and
exit. (Prints an error message and exits if XEmacs was not configured
‘<samp>--pdump</samp>’.)
</p>
</dd>
<dt> ‘<samp>--no-dump-file</samp>’</dt>
<dt> ‘<samp>-nd</samp>’</dt>
-<dd><p>Don't load the dump file. Roughly equivalent to old temacs. (Ignored
if
+<dd><p>Don’t load the dump file. Roughly equivalent to old temacs.
(Ignored if
XEmacs was not configured ‘<samp>--pdump</samp>’.)
</p>
</dd>
@@ -753,7 +753,7 @@
(you guessed it) last.
</p>
<p>By default, XEmacs expects an early package hierarchy in the
-subdirectory ‘<tt>.xemacs/xemacs-packages</tt>’ of the user's home
+subdirectory ‘<tt>.xemacs/xemacs-packages</tt>’ of the
user’s home
directory.
</p>
<p>Moreover, XEmacs expects late hierarchies in the subdirectories
@@ -888,7 +888,7 @@
<dt> <code>doc-directory</code></dt>
<dd><a name="IDX128"></a>
<p>Is the directory containing the architecture-specific
‘<tt>DOC</tt>’ file
-that contains documentation for XEmacs' commands.
+that contains documentation for XEmacs’ commands.
</p>
</dd>
<dt> <code>data-directory</code></dt>
Index: Tests/xemacs_frame_res/xemacs_7.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/xemacs_frame_res/xemacs_7.html,v
retrieving revision 1.25
retrieving revision 1.26
diff -u -b -r1.25 -r1.26
--- Tests/xemacs_frame_res/xemacs_7.html 5 Feb 2007 15:30:27 -0000
1.25
+++ Tests/xemacs_frame_res/xemacs_7.html 3 Oct 2007 09:34:55 -0000
1.26
@@ -160,7 +160,7 @@
characters act as editing commands and do not insert themselves. If you
need to insert a control character or a character whose code is above 200
octal, you must <em>quote</em> it by typing the character <kbd>Control-q</kbd>
-(<code>quoted-insert</code>) first. (This character's name is normally written
+(<code>quoted-insert</code>) first. (This character’s name is normally
written
<kbd>C-q</kbd> for short.) There are two ways to use <kbd>C-q</kbd>:
</p>
<ul>
@@ -217,9 +217,9 @@
clicking the left mouse button where you want to move to.
</p>
<p> NOTE: Many of the following commands have two versions, one that uses
-the function keys (e.g. <LEFT> or <END>) and one that doesn't.
+the function keys (e.g. <LEFT> or <END>) and one that
doesn’t.
The former versions may only be available on X terminals (i.e. not on
-TTY's), but the latter are available on all terminals.
+TTY’s), but the latter are available on all terminals.
</p>
<a name="IDX142"></a>
<a name="IDX143"></a>
@@ -605,7 +605,7 @@
</p>
<p> Sometimes it is nice to have Emacs insert newlines automatically when
a line gets too long. Continuation on the screen does not do that. Use
-Auto Fill mode (see section <a href="xemacs_23.html#SEC210">Filling Text</a>)
if that's what you want.
+Auto Fill mode (see section <a href="xemacs_23.html#SEC210">Filling Text</a>)
if that’s what you want.
</p>
<a name="IDX191"></a>
<a name="IDX192"></a>
Index: Tests/xemacs_frame_res/xemacs_8.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/xemacs_frame_res/xemacs_8.html,v
retrieving revision 1.18
retrieving revision 1.19
diff -u -b -r1.18 -r1.19
--- Tests/xemacs_frame_res/xemacs_8.html 5 Feb 2007 15:30:27 -0000
1.18
+++ Tests/xemacs_frame_res/xemacs_8.html 3 Oct 2007 09:34:55 -0000
1.19
@@ -71,7 +71,7 @@
</p>
<dl compact="compact">
<dt> <kbd>C-x u</kbd></dt>
-<dd><p>Undo one batch of changes (usually, one command's worth)
(<code>undo</code>).
+<dd><p>Undo one batch of changes (usually, one command’s worth)
(<code>undo</code>).
</p></dd>
<dt> <kbd>C-_</kbd></dt>
<dd><p>The same.
@@ -110,9 +110,9 @@
or saved.
</p>
<p> Not all buffers record undo information. Buffers whose names start with
-spaces don't; these buffers are used internally by Emacs and its extensions
-to hold text that users don't normally look at or edit. Minibuffers,
-help buffers, and documentation buffers also don't record undo information.
+spaces don’t; these buffers are used internally by Emacs and its
extensions
+to hold text that users don’t normally look at or edit. Minibuffers,
+help buffers, and documentation buffers also don’t record undo
information.
</p>
<p> Emacs can remember at most 8000 or so characters of deleted or
modified text in any one buffer for reinsertion by the undo command.
Index: Tests/xemacs_frame_res/xemacs_9.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/xemacs_frame_res/xemacs_9.html,v
retrieving revision 1.24
retrieving revision 1.25
diff -u -b -r1.24 -r1.25
--- Tests/xemacs_frame_res/xemacs_9.html 5 Feb 2007 15:30:27 -0000
1.24
+++ Tests/xemacs_frame_res/xemacs_9.html 3 Oct 2007 09:34:56 -0000
1.25
@@ -161,10 +161,10 @@
nearby directories, use <kbd>..</kbd>; thus, if you type
<kbd>../lisp/simple.el</kbd>, you will get the file named
‘<tt>/u2/emacs/lisp/simple.el</tt>’. Alternatively, you can kill
with
-<kbd>M-<DEL></kbd> the directory names you don't want (see section <a
href="xemacs_23.html#SEC206">Words</a>).
+<kbd>M-<DEL></kbd> the directory names you don’t want (see section
<a href="xemacs_23.html#SEC206">Words</a>).
</p>
-<p> If you don't want any of the default, you can kill it with <kbd>C-a
-C-k</kbd>. But you don't need to kill the default; you can simply ignore it.
+<p> If you don’t want any of the default, you can kill it with <kbd>C-a
+C-k</kbd>. But you don’t need to kill the default; you can simply
ignore it.
Insert an absolute file name, one starting with a slash or a tilde,
after the default directory. For example, to specify the file
‘<tt>/etc/termcap</tt>’, just insert that name, giving these
minibuffer
@@ -213,7 +213,7 @@
you are entering.
</p>
<p> Since <RET> in the minibuffer is defined to exit the minibuffer,
-you can't use it to insert a newline in the minibuffer. To do that,
+you can’t use it to insert a newline in the minibuffer. To do that,
type <kbd>C-o</kbd> or <kbd>C-q C-j</kbd>. (Recall that a newline is really
the
character control-J.)
</p>
@@ -310,7 +310,7 @@
in most of the names that you can complete (buffer names, file names and
command names). Thus, ‘<samp>fo</samp>’ does not complete to
‘<samp>Foo</samp>’. When
you are completing a name in which case does not matter, case may be
-ignored for completion's sake if specified by program.
+ignored for completion’s sake if specified by program.
</p>
<p>When a completion list is displayed, the completions will highlight as
you move the mouse over them. Clicking the middle mouse button on any
@@ -399,7 +399,7 @@
(<code>minibuffer-complete</code>).
</p></dd>
<dt> <kbd><SPC></kbd></dt>
-<dd><p>Complete the minibuffer text, but don't go beyond one word
+<dd><p>Complete the minibuffer text, but don’t go beyond one word
(<code>minibuffer-complete-word</code>).
</p></dd>
<dt> <kbd><RET></kbd></dt>
@@ -584,7 +584,7 @@
</p>
<a name="IDX229"></a>
<p> Icomplete mode presents a constantly-updated display that tells you
-what completions are available for the text you've entered so far. The
+what completions are available for the text you’ve entered so far. The
command to enable or disable this minor mode is <kbd>M-x
icomplete-mode</kbd>.
</p>
@@ -748,7 +748,7 @@
history unless it is identical to the most recently executed command
already there.
</p>
-<p> Even if you don't understand Lisp syntax, it will probably be obvious
+<p> Even if you don’t understand Lisp syntax, it will probably be
obvious
which command is displayed for repetition. If you do not change the text,
you can be sure the command will repeat exactly as before.
</p>
Index: Tests/xemacs_frame_res/xemacs_frame.html
===================================================================
RCS file:
/cvsroot/texi2html/texi2html/Tests/xemacs_frame_res/xemacs_frame.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- Tests/xemacs_frame_res/xemacs_frame.html 22 Apr 2003 17:56:03 -0000
1.1
+++ Tests/xemacs_frame_res/xemacs_frame.html 3 Oct 2007 09:34:56 -0000
1.2
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Frameset//EN"
"http://www.w3.org/TR/html401/frameset.dtd";>
<html>
-<head><title>XEmacs User's Manual</title></head>
+<head><title>XEmacs User’s Manual</title></head>
<frameset cols="140,*">
<frame name="toc" src="xemacs_toc_frame.html">
<frame name="main" src="xemacs.html">
Index: Tests/xemacs_frame_res/xemacs_toc.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/xemacs_frame_res/xemacs_toc.html,v
retrieving revision 1.14
retrieving revision 1.15
diff -u -b -r1.14 -r1.15
--- Tests/xemacs_frame_res/xemacs_toc.html 5 Feb 2007 15:30:27 -0000
1.14
+++ Tests/xemacs_frame_res/xemacs_toc.html 3 Oct 2007 09:34:56 -0000
1.15
@@ -596,14 +596,14 @@
<li><a name="TOC392" href="xemacs_31.html#SEC403">Glossary</a></li>
<li><a name="TOC393" href="xemacs_32.html#SEC404">The GNU Manifesto</a>
<ul class="toc">
- <li><a name="TOC394" href="xemacs_32.html#SEC405">What's GNU? GNU's Not
Unix!</a></li>
+ <li><a name="TOC394" href="xemacs_32.html#SEC405">What’s GNU?
GNU’s Not Unix!</a></li>
<li><a name="TOC395" href="xemacs_32.html#SEC406">Why I Must Write
GNU</a></li>
<li><a name="TOC396" href="xemacs_32.html#SEC407">Why GNU Will Be
Compatible With Unix</a></li>
<li><a name="TOC397" href="xemacs_32.html#SEC408">How GNU Will Be
Available</a></li>
<li><a name="TOC398" href="xemacs_32.html#SEC409">Why Many Other
Programmers Want to Help</a></li>
<li><a name="TOC399" href="xemacs_32.html#SEC410">How You Can
Contribute</a></li>
<li><a name="TOC400" href="xemacs_32.html#SEC411">Why All Computer Users
Will Benefit</a></li>
- <li><a name="TOC401" href="xemacs_32.html#SEC412">Some Easily Rebutted
Objections to GNU's Goals</a></li>
+ <li><a name="TOC401" href="xemacs_32.html#SEC412">Some Easily Rebutted
Objections to GNU’s Goals</a></li>
</ul></li>
<li><a name="TOC402" href="xemacs_33.html#SEC413">Key (Character)
Index</a></li>
<li><a name="TOC403" href="xemacs_36.html#SEC414">Command and Function
Index</a></li>
Index: Tests/xemacs_res/xemacs.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/xemacs_res/xemacs.html,v
retrieving revision 1.28
retrieving revision 1.29
diff -u -b -r1.28 -r1.29
--- Tests/xemacs_res/xemacs.html 5 Feb 2007 15:30:27 -0000 1.28
+++ Tests/xemacs_res/xemacs.html 3 Oct 2007 09:34:56 -0000 1.29
@@ -82,7 +82,7 @@
corresponds to XEmacs version 21.0.
</p>
<p>This manual is intended as a detailed reference to XEmacs. If
-you are looking for an introductory manual, see the New User's
+you are looking for an introductory manual, see the New User’s
Guide.
</p>
<table class="menu" border="0" cellspacing="0">
@@ -96,7 +96,7 @@
</td></tr>
<tr><td align="left" valign="top"><a
href="xemacs_31.html#SEC403">Glossary</a></td><td> </td><td
align="left" valign="top"> The glossary.
</td></tr>
-<tr><td align="left" valign="top"><a href="xemacs_32.html#SEC404">The GNU
Manifesto</a></td><td> </td><td align="left" valign="top"> What's
GNU? Gnu's Not Unix!
+<tr><td align="left" valign="top"><a href="xemacs_32.html#SEC404">The GNU
Manifesto</a></td><td> </td><td align="left" valign="top">
What’s GNU? Gnu’s Not Unix!
</td></tr>
<tr><th colspan="3" align="left" valign="top"><pre class="menu-comment">
Indices, nodes containing large menus
@@ -216,7 +216,7 @@
<tr><td align="left" valign="top"><a href="xemacs_29.html#SEC346">26.10
Recursive Editing Levels</a></td><td> </td><td align="left"
valign="top">
A command can allow you to do editing
"within the command". This is called a
- `recursive editing level'.
+ ‘recursive editing level’.
</td></tr>
<tr><td align="left" valign="top"><a href="xemacs_29.html#SEC347">26.11
Dissociated Press</a></td><td> </td><td align="left" valign="top">
Dissociating text for fun.
</td></tr>
@@ -808,11 +808,11 @@
<tr><th colspan="3" align="left" valign="top"><pre class="menu-comment">
Variables
-</pre></th></tr><tr><td align="left" valign="top"><a
href="xemacs_30.html#SEC354">27.2.1 Examining and Setting
Variables</a></td><td> </td><td align="left" valign="top">
Examining or setting one variable's value.
+</pre></th></tr><tr><td align="left" valign="top"><a
href="xemacs_30.html#SEC354">27.2.1 Examining and Setting
Variables</a></td><td> </td><td align="left" valign="top">
Examining or setting one variable’s value.
</td></tr>
<tr><td align="left" valign="top"><a href="xemacs_30.html#SEC355">27.2.2 Easy
Customization Interface</a></td><td> </td><td align="left"
valign="top"> Convenient and easy customization of variables.
</td></tr>
-<tr><td align="left" valign="top"><a href="xemacs_30.html#SEC360">27.2.3
Editing Variable Values</a></td><td> </td><td align="left"
valign="top"> Examining or editing list of all variables' values.
+<tr><td align="left" valign="top"><a href="xemacs_30.html#SEC360">27.2.3
Editing Variable Values</a></td><td> </td><td align="left"
valign="top"> Examining or editing list of all variables’ values.
</td></tr>
<tr><td align="left" valign="top"><a href="xemacs_30.html#SEC361">27.2.4 Local
Variables</a></td><td> </td><td align="left" valign="top">
Per-buffer values of variables.
</td></tr>
@@ -831,9 +831,9 @@
Customizing Key Bindings
</pre></th></tr><tr><td align="left" valign="top"><a
href="xemacs_30.html#SEC368">27.4.1 Keymaps</a></td><td> </td><td
align="left" valign="top"> Definition of the keymap data structure.
- Names of XEmacs's standard keymaps.
+ Names of XEmacs’s standard keymaps.
</td></tr>
-<tr><td align="left" valign="top"><a href="xemacs_30.html#SEC369">27.4.2
Changing Key Bindings</a></td><td> </td><td align="left"
valign="top"> How to redefine one key's meaning conveniently.
+<tr><td align="left" valign="top"><a href="xemacs_30.html#SEC369">27.4.2
Changing Key Bindings</a></td><td> </td><td align="left"
valign="top"> How to redefine one key’s meaning conveniently.
</td></tr>
<tr><td align="left" valign="top"><a href="xemacs_30.html#SEC373">27.4.3
Disabling Commands</a></td><td> </td><td align="left" valign="top">
Disabling a command means confirmation is required
before it can be executed. This is done to protect
@@ -858,7 +858,7 @@
<tr><th colspan="3" align="left" valign="top"><pre class="menu-comment">
Dealing with XEmacs Trouble
-</pre></th></tr><tr><td align="left" valign="top"><a
href="xemacs_30.html#SEC394">27.12.1 Recursive Editing
Levels</a></td><td> </td><td align="left" valign="top"> `[...]'
in mode line around the parentheses.
+</pre></th></tr><tr><td align="left" valign="top"><a
href="xemacs_30.html#SEC394">27.12.1 Recursive Editing
Levels</a></td><td> </td><td align="left" valign="top">
‘[...]’ in mode line around the parentheses.
</td></tr>
<tr><td align="left" valign="top"><a href="xemacs_30.html#SEC395">27.12.2
Garbage on the Screen</a></td><td> </td><td align="left"
valign="top"> Garbage on the screen.
</td></tr>
@@ -869,7 +869,7 @@
<tr><td align="left" valign="top"><a href="xemacs_30.html#SEC398">27.12.5
Emergency Escape</a></td><td> </td><td align="left" valign="top">
Emergency escape—
What to do if XEmacs stops responding.
</td></tr>
-<tr><td align="left" valign="top"><a href="xemacs_30.html#SEC399">27.12.6 Help
for Total Frustration</a></td><td> </td><td align="left"
valign="top"> When you are at your wits' end.
+<tr><td align="left" valign="top"><a href="xemacs_30.html#SEC399">27.12.6 Help
for Total Frustration</a></td><td> </td><td align="left"
valign="top"> When you are at your wits’ end.
</td></tr>
<tr><th colspan="3" align="left" valign="top"><pre class="menu-comment">
</pre></th></tr></table>
Index: Tests/xemacs_res/xemacs_1.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/xemacs_res/xemacs_1.html,v
retrieving revision 1.25
retrieving revision 1.26
diff -u -b -r1.25 -r1.26
--- Tests/xemacs_res/xemacs_1.html 5 Feb 2007 15:30:27 -0000 1.25
+++ Tests/xemacs_res/xemacs_1.html 3 Oct 2007 09:34:56 -0000 1.26
@@ -95,7 +95,7 @@
at the mercy of those companies. By contrast, our General Public
License is intended to guarantee your freedom to share and change free
software—to make sure the software is free for all its users. The
-General Public License applies to the Free Software Foundation's
+General Public License applies to the Free Software Foundation’s
software and to any other program whose authors commit to using it.
You can use it for your programs, too.
</p>
@@ -120,12 +120,12 @@
(2) offer you this license which gives you legal permission to copy,
distribute and/or modify the software.
</p>
-<p> Also, for each author's protection and ours, we want to make certain
+<p> Also, for each author’s protection and ours, we want to make certain
that everyone understands that there is no warranty for this free
software. If the software is modified by someone else and passed on, we
want its recipients to know that what they have is not the original, so
that any problems introduced by others will not reflect on the original
-authors' reputations.
+authors’ reputations.
</p>
<p> The precise terms and conditions for copying, distribution and
modification follow.
@@ -144,7 +144,7 @@
</li><li>
<a name="IDX3"></a>
-You may copy and distribute verbatim copies of the Program's source
+You may copy and distribute verbatim copies of the Program’s source
code as you receive it, in any medium, provided that you conspicuously and
appropriately publish on each copy an appropriate copyright notice and
disclaimer of warranty; keep intact all the notices that refer to this
@@ -244,7 +244,7 @@
Program), the recipient automatically receives a license from the original
licensor to copy, distribute or modify the Program subject to these
terms and conditions. You may not impose any further restrictions on the
-recipients' exercise of the rights granted herein.
+recipients’ exercise of the rights granted herein.
</li><li>
@@ -357,10 +357,10 @@
under certain conditions; type `show c' for details.
</pre></td></tr></table>
-<p>The hypothetical commands `show w' and `show c' should show the
+<p>The hypothetical commands ‘show w’ and ‘show c’
should show the
appropriate parts of the General Public License. Of course, the
-commands you use may be called something other than `show w' and `show
-c'; they could even be mouse-clicks or menu items—whatever suits your
+commands you use may be called something other than ‘show w’ and
‘show
+c’; they could even be mouse-clicks or menu items—whatever suits
your
program.
</p>
@@ -376,7 +376,7 @@
Ty Coon, President of Vice
</pre></td></tr></table>
-<p>That's all there is to it!
+<p>That’s all there is to it!
</p>
<hr size="6">
<table cellpadding="1" cellspacing="1" border="0">
Index: Tests/xemacs_res/xemacs_11.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/xemacs_res/xemacs_11.html,v
retrieving revision 1.29
retrieving revision 1.30
diff -u -b -r1.29 -r1.30
--- Tests/xemacs_res/xemacs_11.html 5 Feb 2007 15:30:27 -0000 1.29
+++ Tests/xemacs_res/xemacs_11.html 3 Oct 2007 09:34:56 -0000 1.30
@@ -141,7 +141,7 @@
</p></dd>
<dt> <kbd>C-h c <var>key</var></kbd></dt>
<dd><p>Print the name of the command that <var>key</var> runs
-(<code>describe-key-briefly</code>). Here <kbd>c</kbd> stands for
`character'. For more
+(<code>describe-key-briefly</code>). Here <kbd>c</kbd> stands for
‘character’. For more
extensive information on <var>key</var>, use <kbd>C-h k</kbd>.
</p></dd>
<dt> <kbd>C-h d <var>function</var> <RET></kbd></dt>
@@ -278,7 +278,7 @@
<h2 class="section"> 8.3 Help by Command or Variable Name </h2>
<p> <kbd>C-h f</kbd> (<code>describe-function</code>) reads the name of a Lisp
-function using the minibuffer, then displays that function's
+function using the minibuffer, then displays that function’s
documentation string in a window. Since commands are Lisp functions,
you can use the argument <var>function</var> to get the documentation of a
command that you know by name. For example,
@@ -299,7 +299,7 @@
<code>make-vector</code> properly, type <kbd>C-h f make-vector
<RET></kbd>.
Because <kbd>C-h f</kbd> allows all function names, not just command names,
you may find that some of your favorite abbreviations that work in
-<kbd>M-x</kbd> don't work in <kbd>C-h f</kbd>. An abbreviation may be unique
+<kbd>M-x</kbd> don’t work in <kbd>C-h f</kbd>. An abbreviation may be
unique
among command names, yet fail to be unique when other function names are
allowed.
</p>
@@ -373,7 +373,7 @@
so on. With each command name appears a brief description of how to use
the command, and what keys you can currently invoke it with. For
example, it would say that you can invoke <code>find-file</code> by typing
-<kbd>C-x C-f</kbd>. The <kbd>A</kbd> in <kbd>C-h A</kbd> stands for `Apropos';
+<kbd>C-x C-f</kbd>. The <kbd>A</kbd> in <kbd>C-h A</kbd> stands for
‘Apropos’;
<kbd>C-h A</kbd> runs the command <code>command-apropos</code>. This command
normally checks only commands (interactive functions); if you specify a
prefix argument, it checks noninteractive functions as well.
@@ -381,7 +381,7 @@
<p> Because <kbd>C-h A</kbd> looks only for functions whose names contain the
string you specify, you must use ingenuity in choosing the string. If
you are looking for commands for killing backwards and <kbd>C-h a
-kill-backwards <RET></kbd> doesn't reveal any, don't give up. Try just
+kill-backwards <RET></kbd> doesn’t reveal any, don’t give
up. Try just
<kbd>kill</kbd>, or just <kbd>backwards</kbd>, or just <kbd>back</kbd>. Be
persistent.
Pretend you are playing Adventure. Also note that you can use a regular
expression as the argument, for more flexibility (see section <a
href="xemacs_15.html#SEC121">Syntax of Regular Expressions</a>).
@@ -412,7 +412,7 @@
</p>
<a name="IDX260"></a>
<p> The <code>apropos-value</code> command is like <code>apropos</code>
except that it
-searches symbols' values for matches for the specified regular
+searches symbols’ values for matches for the specified regular
expression. This command does not check function definitions or
property lists by default; specify a numeric argument if you want it to
check them.
@@ -553,7 +553,7 @@
a tutorial on using Info.
</p>
<p> If you specify a numeric argument, <kbd>C-h i</kbd> prompts for the name
of
-a documentation file. This way, you can browse a file which doesn't
+a documentation file. This way, you can browse a file which doesn’t
have an entry in the top-level Info menu. It is also handy when you
need to get to the documentation quickly, and you know the exact name of
the file.
@@ -574,7 +574,7 @@
<a name="IDX267"></a>
<p> If something surprising happens, and you are not sure what commands you
typed, use <kbd>C-h l</kbd> (<code>view-lossage</code>). <kbd>C-h l</kbd>
prints the last
-100 command characters you typed in. If you see commands that you don't
+100 command characters you typed in. If you see commands that you don’t
know, you can use <kbd>C-h c</kbd> to find out what they do.
</p>
<a name="IDX268"></a>
@@ -591,7 +591,7 @@
mode that is not covered by <kbd>C-h m</kbd>. <kbd>C-h b</kbd> displays a
list of
all the key bindings currently in effect, with the local bindings of the
current major mode first, followed by the global bindings (see section <a
href="xemacs_30.html#SEC367">Customizing Key Bindings</a>). <kbd>C-h s</kbd>
displays the contents of the syntax table with
-explanations of each character's syntax (see section <a
href="xemacs_30.html#SEC374">The Syntax Table</a>).
+explanations of each character’s syntax (see section <a
href="xemacs_30.html#SEC374">The Syntax Table</a>).
</p>
<p> You can get a similar list for a particular prefix key by typing
<kbd>C-h</kbd> after the prefix key. (There are a few prefix keys for which
Index: Tests/xemacs_res/xemacs_12.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/xemacs_res/xemacs_12.html,v
retrieving revision 1.31
retrieving revision 1.32
diff -u -b -r1.31 -r1.32
--- Tests/xemacs_res/xemacs_12.html 5 Feb 2007 15:30:27 -0000 1.31
+++ Tests/xemacs_res/xemacs_12.html 3 Oct 2007 09:34:56 -0000 1.32
@@ -95,7 +95,7 @@
<p> To specify the text for a command to operate on, set <em>the
mark</em> at one end of it, and move point to the other end. The text
between point and the mark is called <em>the region</em>. You can move
-point or the mark to adjust the boundaries of the region. It doesn't
+point or the mark to adjust the boundaries of the region. It doesn’t
matter which one is set first chronologically, or which one comes
earlier in the text.
</p>
@@ -375,7 +375,7 @@
The marks you have seen go to the end of the ring, so no marks are lost.
</p>
<p> Each buffer has its own mark ring. All editing commands use the current
-buffer's mark ring. In particular, <kbd>C-u C-<SPC></kbd> always stays
in
+buffer’s mark ring. In particular, <kbd>C-u C-<SPC></kbd> always
stays in
the same buffer.
</p>
<p> Many commands that can move long distances, such as <kbd>M-<</kbd>
@@ -639,7 +639,7 @@
text but do not save it; they are known as <em>delete</em> commands. (This
distinction is made only for erasing text in the buffer.)
</p>
-<p>The commands' names and individual descriptions use the words
+<p>The commands’ names and individual descriptions use the words
‘<samp>kill</samp>’ and ‘<samp>delete</samp>’ to
indicate what they do. If you perform
a kill or delete command by mistake, use the <kbd>C-x u</kbd>
(<code>undo</code>)
command to undo it (see section <a href="xemacs_8.html#SEC59">Undoing
Changes</a>). The delete commands include <kbd>C-d</kbd>
@@ -694,10 +694,10 @@
<p> The most basic delete commands are <kbd>C-d</kbd>
(<code>delete-char</code>) and
<DEL> (<code>delete-backward-char</code>). <kbd>C-d</kbd> deletes the
character after point, the one the cursor is “on top of”. Point
-doesn't move. <DEL> deletes the character before the cursor, and
+doesn’t move. <DEL> deletes the character before the cursor, and
moves point back. You can delete newlines like any other characters in
the buffer; deleting a newline joins two lines. Actually, <kbd>C-d</kbd> and
-<DEL> aren't always delete commands; if you give them an argument,
+<DEL> aren’t always delete commands; if you give them an argument,
they kill instead, since they can erase more than one character this
way.
</p>
@@ -770,7 +770,7 @@
before point is not killed). With a negative argument, <kbd>C-k</kbd> kills
back to a number of line beginnings. An argument of -2 means
kill back to the second line beginning. If point is at the beginning of
-a line, that line beginning doesn't count, so <kbd>C-u - 2 C-k</kbd> with
+a line, that line beginning doesn’t count, so <kbd>C-u - 2 C-k</kbd> with
point at the front of a line kills the two previous lines.
</p>
<p> <kbd>C-k</kbd> with an argument of zero kills all the text before point
on the
@@ -970,7 +970,7 @@
<p> Normally, each kill command pushes a new block onto the kill ring.
However, two or more kill commands in a row combine their text into a
single entry, so that a single <kbd>C-y</kbd> yanks it all back. This means
-you don't have to kill all the text you want to yank in one command; you
+you don’t have to kill all the text you want to yank in one command; you
can kill line after line, or word after word, until you have killed what
you want, then get it all back at once using <kbd>C-y</kbd>. (Thus we join
television in leading people to kill thoughtlessly.)
@@ -1057,7 +1057,7 @@
<p> Once the text you are looking for is brought into the buffer, you can
stop doing <kbd>M-y</kbd> commands and the text will stay there. Since the
text is just a copy of the kill ring item, editing it in the buffer does
-not change what's in the ring. As long you don't kill additional text,
+not change what’s in the ring. As long you don’t kill additional
text,
the “last yank” pointer remains at the same place in the kill ring:
repeating <kbd>C-y</kbd> will yank another copy of the same old kill.
</p>
@@ -1161,7 +1161,7 @@
</p>
<p>Warning: If you use the ‘<tt>xclipboard</tt>’ application,
remember that it
maintains a list of all things that have been pasted to the clipboard (that
-is, copied with the <b>Copy</b> command). If you don't manually delete
elements
+is, copied with the <b>Copy</b> command). If you don’t manually delete
elements
from this list by clicking on the <b>Delete</b> button in the
<code>xclipboard</code>
window, the clipboard will eventually consume a lot of memory.
</p>
@@ -1281,7 +1281,7 @@
application asks the X server for the value of the selection, the X
server requests the information from the owner. When you use
selections, the selection data is not actually transferred unless
-someone wants it; the act of making a selection doesn't transfer data.
+someone wants it; the act of making a selection doesn’t transfer data.
Cut buffers are different: when you "own" a cut buffer, the data is
actually transferred to the X server immediately, and survives the
lifetime of the application.
@@ -1455,7 +1455,7 @@
<dd><p>Prepend region to contents of specified buffer.
</p></dd>
<dt> <kbd>M-x copy-to-buffer</kbd></dt>
-<dd><p>Copy region into specified buffer, deleting that buffer's old contents.
+<dd><p>Copy region into specified buffer, deleting that buffer’s old
contents.
</p></dd>
<dt> <kbd>M-x insert-buffer</kbd></dt>
<dd><p>Insert contents of specified buffer into current buffer at point.
@@ -1498,7 +1498,7 @@
end of the specified file. The file is changed immediately on disk.
This command is normally used with files that are <i>not</i> being visited
in Emacs. Using it on a file that Emacs is visiting can produce
-confusing results, because the file's text inside Emacs does not change
+confusing results, because the file’s text inside Emacs does not change
while the file itself changes.
</p>
<hr size="6">
@@ -1567,7 +1567,7 @@
the text (delete it) or save it as the “last killed” rectangle.
The
commands for these two ways are <kbd>M-x delete-rectangle</kbd> and <kbd>M-x
kill-rectangle</kbd>. In either case, the portion of each line that falls
inside
-the rectangle's boundaries is deleted, causing following text (if any) on
+the rectangle’s boundaries is deleted, causing following text (if any) on
the line to move left.
</p>
<p> Note that “killing” a rectangle is not killing in the usual
sense; the
@@ -1580,7 +1580,7 @@
</p>
<p> Inserting a rectangle is the opposite of deleting one. You specify
where to put the upper left corner by putting point there. The
-rectangle's first line is inserted at point, the rectangle's second line
+rectangle’s first line is inserted at point, the rectangle’s
second line
is inserted at a point one line vertically down, and so on. The number
of lines affected is determined by the height of the saved rectangle.
</p>
Index: Tests/xemacs_res/xemacs_13.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/xemacs_res/xemacs_13.html,v
retrieving revision 1.28
retrieving revision 1.29
diff -u -b -r1.28 -r1.29
--- Tests/xemacs_res/xemacs_13.html 5 Feb 2007 15:30:27 -0000 1.28
+++ Tests/xemacs_res/xemacs_13.html 3 Oct 2007 09:34:56 -0000 1.29
@@ -284,7 +284,7 @@
</p>
<dl compact="compact">
<dt> <kbd>C-x r w <var>r</var></kbd></dt>
-<dd><p>Save the state of the selected frame's windows in register <var>r</var>
+<dd><p>Save the state of the selected frame’s windows in register
<var>r</var>
(<code>window-configuration-to-register</code>).
</p></dd>
<dt> <kbd>M-x frame-configuration-to-register <RET>
<var>r</var></kbd></dt>
@@ -366,7 +366,7 @@
<h2 class="section"> 10.6 Keeping File Names in Registers </h2>
<p> If you visit certain file names frequently, you can visit them more
-conveniently if you put their names in registers. Here's the Lisp code
+conveniently if you put their names in registers. Here’s the Lisp code
used to put a file name in a register:
</p>
<table><tr><td> </td><td><pre class="smallexample">(set-register
?<var>r</var> '(file . <var>name</var>))
@@ -467,7 +467,7 @@
<a name="IDX376"></a>
<p> If you set the variable <code>bookmark-save-flag</code> to 1, then each
command that sets a bookmark will also save your bookmarks; this way,
-you don't lose any bookmark values even if XEmacs crashes. (The value,
+you don’t lose any bookmark values even if XEmacs crashes. (The value,
if a number, says how many bookmark modifications should go by between
saving.)
</p>
@@ -475,7 +475,7 @@
<p> Bookmark position values are saved with surrounding context, so that
<code>bookmark-jump</code> can find the proper position even if the file is
modified slightly. The variable <code>bookmark-search-size</code> says how
-many characters of context to record, on each side of the bookmark's
+many characters of context to record, on each side of the bookmark’s
position.
</p>
<p> Here are some additional commands for working with bookmarks:
Index: Tests/xemacs_res/xemacs_14.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/xemacs_res/xemacs_14.html,v
retrieving revision 1.27
retrieving revision 1.28
diff -u -b -r1.27 -r1.28
--- Tests/xemacs_res/xemacs_14.html 5 Feb 2007 15:30:27 -0000 1.27
+++ Tests/xemacs_res/xemacs_14.html 3 Oct 2007 09:34:56 -0000 1.28
@@ -285,7 +285,7 @@
less, to be precise). <kbd>C-x ></kbd> (<code>scroll-right</code>) scrolls
similarly to the right. The window cannot be scrolled any farther to
the right once it is displaying normally (with each line starting at the
-window's left margin); attempting to do so has no effect.
+window’s left margin); attempting to do so has no effect.
</p>
<hr size="6">
<a name="Selective-Display"></a>
@@ -369,7 +369,7 @@
<a name="IDX403"></a>
<p> The variable <code>echo-keystrokes</code> controls the echoing of
multi-character
keys; its value is the number of seconds of pause required to cause echoing
-to start, or zero, meaning don't echo at all. See section <a
href="xemacs_4.html#SEC9">The Echo Area</a>.
+to start, or zero, meaning don’t echo at all. See section <a
href="xemacs_4.html#SEC9">The Echo Area</a>.
</p>
<a name="IDX404"></a>
<p> If the variable <code>ctl-arrow</code> is <code>nil</code>, control
characters in the
Index: Tests/xemacs_res/xemacs_15.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/xemacs_res/xemacs_15.html,v
retrieving revision 1.33
retrieving revision 1.34
diff -u -b -r1.33 -r1.34
--- Tests/xemacs_res/xemacs_15.html 5 Feb 2007 15:30:27 -0000 1.33
+++ Tests/xemacs_res/xemacs_15.html 3 Oct 2007 09:34:56 -0000 1.34
@@ -443,7 +443,7 @@
there are multiple spaces, newlines or other punctuation between the words.
</p>
<p> Word search is useful in editing documents formatted by text formatters.
-If you edit while looking at the printed, formatted version, you can't tell
+If you edit while looking at the printed, formatted version, you can’t
tell
where the line breaks are in the source file. Word search, allows you
to search without having to know the line breaks.
</p>
@@ -500,8 +500,8 @@
</p>
<p> To gain a thorough understanding of regular expressions and how to use
them to best advantage, we recommend that you study <cite>Mastering
-Regular Expressions, by Jeffrey E.F. Friedl, O'Reilly and Associates,
-1997</cite>. (It's known as the "Hip Owls" book, because of the
picture on its
+Regular Expressions, by Jeffrey E.F. Friedl, O’Reilly and Associates,
+1997</cite>. (It’s known as the "Hip Owls" book, because of
the picture on its
cover.) You might also read the manuals to <a
href="../gawk/index.html#Top">(gawk)Top</a>,
<a href="../ed/index.html#Top">(ed)Top</a>, <cite>sed</cite>,
<cite>grep</cite>, <a href="../perl/index.html#Top">(perl)Top</a>,
<a href="../regex/index.html#Top">(regex)Top</a>, <a
href="../rx/index.html#Top">(rx)Top</a>, <cite>pcre</cite>, and <a
href="../flex/index.html#Top">(flex)Top</a>, which
@@ -509,7 +509,7 @@
</p>
<p> The XEmacs regular expression syntax most closely resembles that of
<cite>ed</cite>, or <cite>grep</cite>, the GNU versions of which all utilize
the GNU
-<cite>regex</cite> library. XEmacs' version of <cite>regex</cite> has
recently been
+<cite>regex</cite> library. XEmacs’ version of <cite>regex</cite> has
recently been
extended with some Perl–like capabilities, described in the next
section.
</p>
@@ -627,7 +627,7 @@
backtracking loops. For example, it could take hours for the regular
expression ‘<samp>\(x+y*\)*a</samp>’ to match the sequence
‘<samp>xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxz</samp>’. The slowness
is because
-Emacs must try each imaginable way of grouping the 35
‘<samp>x</samp>’'s before
+Emacs must try each imaginable way of grouping the 35
‘<samp>x</samp>’’s before
concluding that none of them can work. To make sure your regular
expressions run fast, check nested repetitions carefully.
</p>
@@ -861,7 +861,7 @@
the groupings at the end.
</p>
<p>Using ‘<samp>\(?: … \)</samp>’ rather than
‘<samp>\( … \)</samp>’ when you
-don't need the captured substrings ought to speed up your programs some,
+don’t need the captured substrings ought to speed up your programs some,
since it shortens the code path followed by the regular expression
engine, as well as the amount of memory allocation and string copying it
must do. The actual performance gain to be observed has not been
@@ -898,7 +898,7 @@
</dl>
<p> The following regular expression constructs match the empty
string—that is,
-they don't use up any characters—but whether they match depends on the
+they don’t use up any characters—but whether they match depends on
the
context.
</p>
<dl compact="compact">
@@ -1115,7 +1115,7 @@
can refer to all or part of what is matched by the <var>regexp</var>.
‘<samp>\&</samp>’
in <var>newstring</var> stands for the entire text being replaced.
‘<samp>\<var>d</var></samp>’ in <var>newstring</var>, where
<var>d</var> is a digit, stands for
-whatever matched the <var>d</var>'th parenthesized grouping in
<var>regexp</var>.
+whatever matched the <var>d</var>’th parenthesized grouping in
<var>regexp</var>.
For example,
</p>
<table><tr><td> </td><td><pre class="example">M-x replace-regexp
<RET> c[ad]+r <RET> \&-safe <RET>
Index: Tests/xemacs_res/xemacs_16.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/xemacs_res/xemacs_16.html,v
retrieving revision 1.26
retrieving revision 1.27
diff -u -b -r1.26 -r1.27
--- Tests/xemacs_res/xemacs_16.html 5 Feb 2007 15:30:27 -0000 1.26
+++ Tests/xemacs_res/xemacs_16.html 3 Oct 2007 09:34:56 -0000 1.27
@@ -129,7 +129,7 @@
<kbd>C-y</kbd> and <kbd>M-y</kbd> to retrieve. See section <a
href="xemacs_12.html#SEC91">Yanking</a>.
</p>
<p> <kbd>M-<DEL></kbd> is often useful even when you have typed only a
few
-characters wrong, if you know you are confused in your typing and aren't
+characters wrong, if you know you are confused in your typing and aren’t
sure exactly what you typed. At such a time, you cannot correct with
<DEL> except by looking at the screen to see what you did. It requires
less thought to kill the whole word and start over.
Index: Tests/xemacs_res/xemacs_17.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/xemacs_res/xemacs_17.html,v
retrieving revision 1.30
retrieving revision 1.31
diff -u -b -r1.30 -r1.31
--- Tests/xemacs_res/xemacs_17.html 5 Feb 2007 15:30:27 -0000 1.30
+++ Tests/xemacs_res/xemacs_17.html 3 Oct 2007 09:34:56 -0000 1.31
@@ -63,7 +63,7 @@
<p> The basic unit of stored data in Unix is the <em>file</em>. To edit a
file,
you must tell Emacs to examine the file and prepare a buffer containing a
-copy of the file's text. This is called <em>visiting</em> the file. Editing
+copy of the file’s text. This is called <em>visiting</em> the file.
Editing
commands apply directly to text in the buffer; that is, to the copy inside
Emacs. Your changes appear in the file itself only when you <em>save</em> the
buffer back into the file.
@@ -149,7 +149,7 @@
</p>
<p> In both cases the ‘<samp><var>user</var>@</samp>’ portion is
optional (it defaults
to your local user name). <var>path-on-remote-host</var> may use the
-‘<samp>~</samp>’ notation to indicate <var>user</var>'s home
directory on the remote
+‘<samp>~</samp>’ notation to indicate <var>user</var>’s home
directory on the remote
host. The default file name will reflect the remote host information.
</p>
<a name="IDX529"></a>
@@ -191,10 +191,10 @@
Removing a directory is similar to creating one. To remove a directory,
use <code>remove-directory</code>; it takes one argument, a file name string.
</p>
-<p> The command <kbd>M-x pwd</kbd> prints the current buffer's default
directory,
+<p> The command <kbd>M-x pwd</kbd> prints the current buffer’s default
directory,
and the command <kbd>M-x cd</kbd> sets it (to a value read using the
-minibuffer). A buffer's default directory changes only when the
<code>cd</code>
-command is used. A file-visiting buffer's default directory is initialized
+minibuffer). A buffer’s default directory changes only when the
<code>cd</code>
+command is used. A file-visiting buffer’s default directory is
initialized
to the directory of the file that is visited there. If a buffer is created
with <kbd>C-x b</kbd>, its default directory is copied from that of the
buffer that was current at the time.
@@ -258,11 +258,11 @@
(<code>find-alternate-file</code>).
</p></dd>
<dt> <kbd>C-x 4 C-f</kbd></dt>
-<dd><p>Visit a file, in another window (<code>find-file-other-window</code>).
Don't
+<dd><p>Visit a file, in another window (<code>find-file-other-window</code>).
Don’t
change this window.
</p></dd>
<dt> <kbd>C-x 5 C-f</kbd></dt>
-<dd><p>Visit a file, in another frame (<code>find-file-other-frame</code>).
Don't
+<dd><p>Visit a file, in another frame (<code>find-file-other-frame</code>).
Don’t
change this window or frame.
</p></dd>
</dl>
@@ -280,7 +280,7 @@
name is constructed by appending ‘<samp><2></samp>’,
‘<samp><3></samp>’,and so on, using
the lowest number that makes a name that is not already in use.
</p>
-<p> Each window's mode line shows the name of the buffer that is being
displayed
+<p> Each window’s mode line shows the name of the buffer that is being
displayed
in that window, so you can always tell what buffer you are editing.
</p>
<p> The changes you make with Emacs are made in the Emacs buffer. They do
@@ -331,8 +331,8 @@
</p>
<a name="IDX544"></a>
<a name="IDX545"></a>
-<p>If the variable <code>find-file-use-truenames</code>'s value is
-non-<code>nil</code>, a buffer's visited filename will always be traced back
+<p>If the variable <code>find-file-use-truenames</code>’s value is
+non-<code>nil</code>, a buffer’s visited filename will always be traced
back
to the real file. The filename will never be a symbolic link, and there
will never be a symbolic link anywhere in its directory path. In other
words, the <code>buffer-file-name</code> and <code>buffer-file-truename</code>
will
@@ -348,7 +348,7 @@
a symbolic link to a file that is already in a buffer, the existing
buffer will be found instead of a newly created one. This works if any
component of the pathname (including a non-terminal component) is a
-symbolic link as well, but doesn't work with hard links (nothing does).
+symbolic link as well, but doesn’t work with hard links (nothing does).
</p>
<a name="IDX548"></a>
<p> If you want to create a file, just visit it. Emacs prints
@@ -484,7 +484,7 @@
(<code>not-modified</code>), which removes the indication that the buffer
is modified. If you do this, none of the save commands will believe
that the buffer needs to be saved. (‘<samp>~</samp>’ is often
used as a
-mathematical symbol for `not'; thus <kbd>Meta-~</kbd> is `not', metafied.)
+mathematical symbol for ‘not’; thus <kbd>Meta-~</kbd> is
‘not’, metafied.)
You could also use <code>set-visited-file-name</code> (see below) to mark the
buffer as visiting a different file name, not in use for
anything important.
@@ -499,7 +499,7 @@
<p> <kbd>M-x set-visited-file-name</kbd> alters the name of the file that the
current buffer is visiting. It prompts you for the new file name in the
minibuffer. You can also use <code>set-visited-file-name</code> on a buffer
-that is not visiting a file. The buffer's name is changed to correspond
+that is not visiting a file. The buffer’s name is changed to correspond
to the file it is now visiting unless the new name is already used by a
different buffer; in that case, the buffer name is not changed.
<code>set-visited-file-name</code> does not save the buffer in the newly
@@ -516,7 +516,7 @@
same effect as <kbd>C-x C-w</kbd>; that is, it reads a file name, marks the
buffer as visiting that file, and saves it there. The default file name in
a buffer that is not visiting a file is made by combining the buffer name
-with the buffer's default directory.
+with the buffer’s default directory.
</p>
<p> If Emacs is about to save a file and sees that the date of the latest
version on disk does not match what Emacs last read or wrote, Emacs
@@ -526,7 +526,7 @@
</p>
<a name="IDX568"></a>
<p> If the variable <code>require-final-newline</code> is
non-<code>nil</code>, Emacs
-puts a newline at the end of any file that doesn't already end in one,
+puts a newline at the end of any file that doesn’t already end in one,
every time a file is saved or written.
</p>
<a name="IDX569"></a>
@@ -620,7 +620,7 @@
<h4 class="subsubsection"> 14.3.1.1 Single or Numbered Backups </h4>
<p> If you choose to have a single backup file (the default),
-the backup file's name is constructed by appending
‘<samp>~</samp>’ to the
+the backup file’s name is constructed by appending
‘<samp>~</samp>’ to the
file name being edited; thus, the backup file for
‘<tt>eval.c</tt>’ is
‘<tt>eval.c~</tt>’.
</p>
@@ -653,7 +653,7 @@
</dl>
<p><code>version-control</code> may be set locally in an individual buffer to
-control the making of backups for that buffer's file. For example,
+control the making of backups for that buffer’s file. For example,
Rmail mode locally sets <code>version-control</code> to <code>never</code> to
make sure
that there is only one backup for an Rmail file. See section <a
href="xemacs_30.html#SEC361">Local Variables</a>.
</p>
@@ -695,7 +695,7 @@
default, you are asked whether the excess middle versions should
really be deleted.
</p>
-<p> You can also use Dired's <kbd>.</kbd> (Period) command to delete old
versions.
+<p> You can also use Dired’s <kbd>.</kbd> (Period) command to delete
old versions.
See section <a href="#SEC163">Dired, the Directory Editor</a>.
</p>
<hr size="6">
@@ -726,9 +726,9 @@
the alternate names remain names for the file that you are editing,
and the contents accessed by those names will be the new contents.
</p>
-<p> How you make a backup file may also affect the file's owner
+<p> How you make a backup file may also affect the file’s owner
and group. If you use copying, they do not change. If renaming is used,
-you become the file's owner, and the file's group becomes the default
+you become the file’s owner, and the file’s group becomes the
default
(different operating systems have different defaults for the group).
</p>
<p> Having the owner change is usually a good idea, because then the owner
@@ -748,7 +748,7 @@
done for files that have multiple names, but renaming may still be done when
the file being edited has only one name. If the variable
<code>backup-by-copying-when-mismatch</code> is non-<code>nil</code>, copying
is
-done if renaming would cause the file's owner or group to change.
+done if renaming would cause the file’s owner or group to change.
</p>
<hr size="6">
<a name="Interlocking"></a>
@@ -779,7 +779,7 @@
warning. When this is not possible, or if the second user has started
to change the file despite the warning, Emacs checks when the file is
saved, and issues a second warning when a user is about to overwrite a
-file containing another user's changes. If you are the user editing the
+file containing another user’s changes. If you are the user editing the
file, you can take corrective action at this point and prevent actual
loss of work.
</p>
@@ -817,7 +817,7 @@
</p>
<p> Some systems are not configured to allow Emacs to make locks. On
these systems, Emacs cannot detect trouble in advance, but it can still
-detect it in time to prevent you from overwriting someone else's changes.
+detect it in time to prevent you from overwriting someone else’s changes.
</p>
<p> Every time Emacs saves a buffer, it first checks the last-modification
date of the existing file on disk to see that it has not changed since the
@@ -831,7 +831,7 @@
</p>
<p> The first thing you should do when notified that simultaneous editing
has already taken place is to list the directory with <kbd>C-u C-x C-d</kbd>
-(see section <a href="#SEC161">Directory Listing</a>). This will show the
file's current
+(see section <a href="#SEC161">Directory Listing</a>). This will show the
file’s current
author. You should attempt to contact that person and ask him not to
continue editing. Often the next step is to save the contents of your
Emacs buffer under a different name, and use <code>diff</code> to compare the
@@ -899,7 +899,7 @@
reversion.
</p>
<p>A buffer reverted from its visited file is marked “not
modified” until
-you make a change. The buffer's modes will also be recalculated, by
+you make a change. The buffer’s modes will also be recalculated, by
<code>normal-mode</code>.
</p>
<p> Some kinds of buffers whose contents reflect data bases other than files,
@@ -999,7 +999,7 @@
there is really no difference between auto-saving and explicit saving.
</p>
<a name="IDX580"></a>
-<p> Emacs deletes a buffer's auto-save file when you explicitly save the
+<p> Emacs deletes a buffer’s auto-save file when you explicitly save the
buffer. To inhibit the deletion, set the variable
<code>delete-auto-save-files</code> to <code>nil</code>. Changing the visited
file
name with <kbd>C-x C-w</kbd> or <code>set-visited-file-name</code> renames any
@@ -1026,7 +1026,7 @@
</tr></table>
<h3 class="subsection"> 14.5.2 Controlling Auto-Saving </h3>
-<p> Each time you visit a file, auto-saving is turned on for that file's
+<p> Each time you visit a file, auto-saving is turned on for that file’s
buffer if the variable <code>auto-save-default</code> is non-<code>nil</code>
(but
not in batch mode; see section <a href="xemacs_6.html#SEC39">Entering and
Exiting Emacs</a>). The default for this
variable is <code>t</code>, so Emacs auto-saves buffers that visit files by
@@ -1194,7 +1194,7 @@
<p> When a file is under version control, we also say that it is
<em>registered</em> in the version control system. Each registered file
-has a corresponding <em>master file</em> which represents the file's
+has a corresponding <em>master file</em> which represents the file’s
present state plus its change history, so that you can reconstruct from
it either the current version or any specified earlier version. Usually
the master file also records a <em>log entry</em> for each version describing
@@ -1323,10 +1323,10 @@
This cancels your last check-out, leaving the file unlocked. If you want
to make a different set of changes, you must first check the file out
again. <kbd>C-x v u</kbd> requires confirmation, unless it sees that
-you haven't made any changes since the last checked-in version.
+you haven’t made any changes since the last checked-in version.
</p>
<p> <kbd>C-x v u</kbd> is also the command to use if you lock a file and then
-don't actually change it.
+don’t actually change it.
</p>
<a name="IDX593"></a>
<a name="IDX594"></a>
@@ -1424,7 +1424,7 @@
</p>
<p> If you find that the file permissions of work files are changed
erroneously, set <code>vc-mistrust-permissions</code> to <code>t</code>. Then
VC
-always checks the master file to determine the file's status.
+always checks the master file to determine the file’s status.
</p>
<a name="IDX603"></a>
<p> You can specify additional directories to search for version control
@@ -1453,7 +1453,7 @@
</tr></table>
<h3 class="subsection"> 14.6.4 Log Entries </h3>
-<p> When you're editing an initial comment or log entry for inclusion in a
+<p> When you’re editing an initial comment or log entry for inclusion
in a
master file, finish your entry by typing <kbd>C-c C-c</kbd>.
</p>
<dl compact="compact">
@@ -1463,8 +1463,8 @@
</p></dd>
</dl>
-<p> To abort check-in, just don't type <kbd>C-c C-c</kbd> in that buffer. You
-can switch buffers and do other editing. As long as you don't try to
+<p> To abort check-in, just don’t type <kbd>C-c C-c</kbd> in that
buffer. You
+can switch buffers and do other editing. As long as you don’t try to
check in another file, the entry you were editing remains in its
buffer, and you can go back to that buffer at any time to complete the
check-in.
@@ -1510,7 +1510,7 @@
<dt> <kbd>C-x v a</kbd></dt>
<dd><a name="IDX605"></a>
<a name="IDX606"></a>
-<p>Visit the current directory's change log file and create new entries for
+<p>Visit the current directory’s change log file and create new entries
for
versions checked in since the most recent entry in the change log file
(<code>vc-update-change-log</code>).
</p>
@@ -1695,7 +1695,7 @@
</p>
<a name="IDX611"></a>
<a name="IDX612"></a>
-<p> When you are working on a large program, it's often useful to find all
+<p> When you are working on a large program, it’s often useful to find
all
the files that are currently locked, or all the files maintained in
version control at all. You can use <kbd>C-x v d</kbd>
(<code>vc-directory</code>)
to show all the locked files in or beneath the current directory. This
@@ -1860,8 +1860,8 @@
</tr></table>
<h4 class="subsubsection"> 14.6.9.2 Snapshot Caveats </h4>
-<p> VC's snapshot facilities are modeled on RCS's named-configuration
-support. They use RCS's native facilities for this, so under VC
+<p> VC’s snapshot facilities are modeled on RCS’s
named-configuration
+support. They use RCS’s native facilities for this, so under VC
snapshots made using RCS are visible even when you bypass VC.
</p>
<p> For SCCS, VC implements snapshots itself. The files it uses contain
@@ -1890,7 +1890,7 @@
least, the makefile probably mentions the file that you renamed. If you
retrieve an old snapshot, the renamed file is retrieved under its new
name, which is not the name that the makefile expects. So the program
-won't really work as retrieved.
+won’t really work as retrieved.
</p>
<hr size="6">
<a name="Version-Headers"></a>
@@ -1933,7 +1933,7 @@
<p> The default header string is ‘<samp>\$Id\$</samp>’ for RCS
and ‘<samp>\%W\%</samp>’
for SCCS. (The actual strings inserted do not have the backslashes
in them. They were placed in the Info source file so that the
-strings don't get interpreted as version-control headers when the
+strings don’t get interpreted as version-control headers when the
Info source files are maintained under version control.) You can
specify other headers to insert by setting the variable
<code>vc-header-alist</code>. Its value is a list of elements of the form
@@ -2050,7 +2050,7 @@
<code>(FROM . TO)</code>, each meaning to replace <code>FROM</code> with
<code>TO</code>
when it appears in a directory name. This replacement is done when
setting up the default directory of a newly visited file. Every
<code>FROM</code>
-string should start with `‘<samp>^</samp>’'.
+string should start with ‘‘<samp>^</samp>’’.
</p>
<p>Use this feature when you have directories which you normally refer to
via absolute symbolic links. Make <code>TO</code> the name of the link, and
@@ -2213,7 +2213,7 @@
that point is on. Some commands perform operations immediately; others
“flag” a file to be operated on later.
</p>
-<p> Most Dired commands that operate on the current line's file also treat a
+<p> Most Dired commands that operate on the current line’s file also
treat a
numeric argument as a repeat count, meaning to act on the files of the
next few lines. A negative argument means to operate on the files of the
preceding lines, and leave point on the first of those lines.
@@ -2365,7 +2365,7 @@
subdirectory. See section <a href="#SEC136">Visiting Files</a>.
</p></dd>
<dt> <kbd>o</kbd></dt>
-<dd><p>Like <kbd>f</kbd>, but uses another window to display the file's
buffer. The
+<dd><p>Like <kbd>f</kbd>, but uses another window to display the file’s
buffer. The
Dired buffer remains visible in the first window. This is like using
<kbd>C-x 4 C-f</kbd> to visit the file. See section <a
href="xemacs_19.html#SEC175">Multiple Windows</a>.
</p></dd>
Index: Tests/xemacs_res/xemacs_18.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/xemacs_res/xemacs_18.html,v
retrieving revision 1.27
retrieving revision 1.28
diff -u -b -r1.27 -r1.28
--- Tests/xemacs_res/xemacs_18.html 5 Feb 2007 15:30:27 -0000 1.27
+++ Tests/xemacs_res/xemacs_18.html 3 Oct 2007 09:34:56 -0000 1.28
@@ -63,10 +63,10 @@
<p> Text you are editing in Emacs resides in an object called a
<em>buffer</em>. Each time you visit a file, Emacs creates a buffer to
-hold the file's text. Each time you invoke Dired, Emacs creates a buffer
+hold the file’s text. Each time you invoke Dired, Emacs creates a buffer
to hold the directory listing. If you send a message with <kbd>C-x m</kbd>,
a buffer named ‘<samp>*mail*</samp>’ is used to hold the text of
the message.
-When you ask for a command's documentation, it appears in a buffer
+When you ask for a command’s documentation, it appears in a buffer
called ‘<samp>*Help*</samp>’.
</p>
<a name="IDX644"></a>
@@ -78,13 +78,13 @@
</p>
<p> When Emacs creates multiple windows, each window has a chosen buffer which
is displayed there, but at any time only one of the windows is selected and
-its chosen buffer is the selected buffer. Each window's mode line displays
+its chosen buffer is the selected buffer. Each window’s mode line
displays
the name of the buffer the window is displaying (see section <a
href="xemacs_19.html#SEC175">Multiple Windows</a>).
</p>
<p> Each buffer has a name which can be of any length but is
case-sensitive. You can select a buffer using its name. Most
buffers are created when you visit files; their names are derived from
-the files' names. You can also create an empty buffer with any name you
+the files’ names. You can also create an empty buffer with any name you
want. A newly started Emacs has a buffer named
‘<samp>*scratch*</samp>’ which
you can use for evaluating Lisp expressions in Emacs.
</p>
@@ -159,7 +159,7 @@
that display text. You can also create a buffer explicitly by typing
<kbd>C-x b <var>bufname</var> <RET></kbd>, which creates a new, empty
buffer
that is not visiting any file, and selects it for editing. The new
-buffer's major mode is determined by the value of
+buffer’s major mode is determined by the value of
<code>default-major-mode</code> (see section <a
href="xemacs_21.html#SEC190">Major Modes</a>). Buffers not visiting
files are usually used for making notes to yourself. If you try to save
one, you are asked for the file name to use.
@@ -207,7 +207,7 @@
<a name="IDX653"></a>
<a name="IDX654"></a>
<p> To print a list of all existing buffers, type <kbd>C-x C-b</kbd>. Each
-line in the list shows one buffer's name, major mode, and visited file.
+line in the list shows one buffer’s name, major mode, and visited file.
A ‘<samp>*</samp>’ at the beginning of a line indicates the buffer
has been
“modified”. If several buffers are modified, it may be time to
save
some with <kbd>C-x s</kbd> (see section <a href="xemacs_17.html#SEC137">Saving
Files</a>). A ‘<samp>%</samp>’ indicates a read-only
Index: Tests/xemacs_res/xemacs_19.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/xemacs_res/xemacs_19.html,v
retrieving revision 1.25
retrieving revision 1.26
diff -u -b -r1.25 -r1.26
--- Tests/xemacs_res/xemacs_19.html 5 Feb 2007 15:30:27 -0000 1.25
+++ Tests/xemacs_res/xemacs_19.html 3 Oct 2007 09:34:56 -0000 1.26
@@ -229,7 +229,7 @@
<dl compact="compact">
<dt> <kbd>C-x o</kbd></dt>
-<dd><p>Select another window (<code>other-window</code>). That is the letter
`o', not zero.
+<dd><p>Select another window (<code>other-window</code>). That is the letter
‘o’, not zero.
</p></dd>
<dt> <kbd>M-C-v</kbd></dt>
<dd><p>Scroll the next window (<code>scroll-other-window</code>).
@@ -246,7 +246,7 @@
<a name="IDX673"></a>
<a name="IDX674"></a>
<p> To select a different window, use <kbd>C-x o</kbd>
(<code>other-window</code>).
-That is an `o', for `other', not a zero. When there are more than
+That is an ‘o’, for ‘other’, not a zero. When there
are more than
two windows, the command moves through all the windows in a cyclic
order, generally top to bottom and left to right. From the rightmost
and bottommost window, it goes back to the one at the upper left corner.
Index: Tests/xemacs_res/xemacs_2.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/xemacs_res/xemacs_2.html,v
retrieving revision 1.20
retrieving revision 1.21
diff -u -b -r1.20 -r1.21
--- Tests/xemacs_res/xemacs_2.html 5 Feb 2007 15:30:27 -0000 1.20
+++ Tests/xemacs_res/xemacs_2.html 3 Oct 2007 09:34:56 -0000 1.21
@@ -102,7 +102,7 @@
</tr></table>
<h2 class="unnumberedsec"> Getting Other Versions of Emacs </h2>
-<p>The Free Software Foundation's version of Emacs (called <em>FSF Emacs</em>
+<p>The Free Software Foundation’s version of Emacs (called <em>FSF
Emacs</em>
in this manual and often referred to as <em>GNU Emacs</em>) is available
by anonymous FTP from ‘<tt>prep.ai.mit.edu</tt>’.
</p>
Index: Tests/xemacs_res/xemacs_20.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/xemacs_res/xemacs_20.html,v
retrieving revision 1.31
retrieving revision 1.32
diff -u -b -r1.31 -r1.32
--- Tests/xemacs_res/xemacs_20.html 5 Feb 2007 15:30:27 -0000 1.31
+++ Tests/xemacs_res/xemacs_20.html 3 Oct 2007 09:34:56 -0000 1.32
@@ -128,7 +128,7 @@
languages (French, Spanish, German) require more than 96 code positions
for accented characters. In fact, even with 8 bits to represent 96 more
character (including accented characters and symbols such as currency
-symbols), some languages' alphabets remain incomplete (Croatian,
+symbols), some languages’ alphabets remain incomplete (Croatian,
Polish). (The 64 "missing characters" are reserved for control
characters.) Furthermore, many European languages have their own
alphabets, which must conflict with the accented characters since the
@@ -141,12 +141,12 @@
character. However, many Asian languages have thousands of characters
and require two or more octets per character. For multilingual
purposes, the ISO 2022 standard establishes escape codes that allow
-switching encodings in midstream. (It's also ISO 2022 that establishes
+switching encodings in midstream. (It’s also ISO 2022 that establishes
the standard that code points 0-31 and 128-159 are control codes.)
</p>
<p>However, this is error-prone and complex for internal processing. For
this reason XEmacs uses an internal coding system which can encode all
-of the world's scripts. Unfortunately, for historical reasons, this
+of the world’s scripts. Unfortunately, for historical reasons, this
code is not Unicode, although we are moving in that direction.
</p>
<p>XEmacs translates between the internal character encoding and various
@@ -159,7 +159,7 @@
European use prior to the introduction of the Euro currency), 1-octet
ISO-8859-15 (which substitutes the Euro for the rarely used "generic
currency" symbol), 1-octet ISO-8859-5 (Cyrillic), or multioctet EUC-JP
-(Japanese). There's no way to tell without being able to read!
+(Japanese). There’s no way to tell without being able to read!
</p>
<p>A number of heuristics are incorporated in Mule for automatic
recognition, there are facilities for the user to set defaults, and
@@ -172,7 +172,7 @@
This illustrates various scripts.
</p>
<p> Keyboards, even in the countries where these character sets are used,
-generally don't have keys for all the characters in them. So XEmacs
+generally don’t have keys for all the characters in them. So XEmacs
supports various <em>input methods</em>, typically one for each script or
language, to make it convenient to type them.
</p>
@@ -313,7 +313,7 @@
<p> One way is to type the accent twice; that is a special feature for
entering the separate letter and accent. For example, <kbd>e ' '</kbd> gives
you the two characters ‘<samp>e'</samp>’. Another way is to type
another letter
-after the <kbd>e</kbd>—something that won't combine with that—and
+after the <kbd>e</kbd>—something that won’t combine with
that—and
immediately delete it. For example, you could type <kbd>e e <DEL>
'</kbd> to get separate ‘<samp>e</samp>’ and
‘<samp>'</samp>’.
</p>
@@ -480,7 +480,7 @@
text in buffer. Returning to the above example, we need to somehow tell
XEmacs that we have different encodings of fonts and text and so it
needs to convert characters between those encodings when displaying.
-That's what ‘<samp>set-charset-ccl-program</samp>’ function is
used for. There
+That’s what ‘<samp>set-charset-ccl-program</samp>’ function
is used for. There
are quite a few various CCL programs defined within XEmacs, and there is
no comprehensive list of them, so you currently have to consult sources.
</p>
@@ -582,7 +582,7 @@
</p>
<dl compact="compact">
<dt> <code>…-unix</code></dt>
-<dd><p>Don't do any end-of-line conversion; assume the file uses
+<dd><p>Don’t do any end-of-line conversion; assume the file uses
newline to separate lines. (This is the convention normally used
on Unix and GNU systems.)
</p>
Index: Tests/xemacs_res/xemacs_21.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/xemacs_res/xemacs_21.html,v
retrieving revision 1.23
retrieving revision 1.24
diff -u -b -r1.23 -r1.24
--- Tests/xemacs_res/xemacs_21.html 5 Feb 2007 15:30:27 -0000 1.23
+++ Tests/xemacs_res/xemacs_21.html 3 Oct 2007 09:34:57 -0000 1.24
@@ -85,7 +85,7 @@
several variants), C mode, and Muddle mode are for specific programming
languages. Text mode, Nroff mode, TeX mode, and Outline mode are for
editing English text. The remaining major modes are not intended for use
-on users' files; they are used in buffers created by Emacs for specific
+on users’ files; they are used in buffers created by Emacs for specific
purposes and include Dired mode for buffers made by Dired (see section <a
href="xemacs_17.html#SEC163">Dired, the Directory Editor</a>),
Mail mode for buffers made by <kbd>C-x m</kbd> (see section <a
href="xemacs_28.html#SEC296">Sending Mail</a>), and Shell
mode for buffers used for communicating with an inferior shell process
@@ -134,7 +134,7 @@
</p>
<a name="IDX736"></a>
<p> When you visit a file, Emacs usually chooses the right major mode
-based on the file's name. For example, files whose names end in
+based on the file’s name. For example, files whose names end in
<code>.c</code> are edited in C mode. The variable
<code>auto-mode-alist</code>
controls the correspondence between file names and major mode. Its value
is a list in which each element has the form:
Index: Tests/xemacs_res/xemacs_22.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/xemacs_res/xemacs_22.html,v
retrieving revision 1.27
retrieving revision 1.28
diff -u -b -r1.27 -r1.28
--- Tests/xemacs_res/xemacs_22.html 5 Feb 2007 15:30:27 -0000 1.27
+++ Tests/xemacs_res/xemacs_22.html 3 Oct 2007 09:34:57 -0000 1.28
@@ -228,7 +228,7 @@
</tr></table>
<h2 class="section"> 19.2 Tab Stops </h2>
-<p> For typing in tables, you can use Text mode's definition of <TAB>,
+<p> For typing in tables, you can use Text mode’s definition of
<TAB>,
<code>tab-to-tab-stop</code>. This command inserts indentation before point,
enough to reach the next tab stop column. Even if you are not in Text mode,
this function is associated with <kbd>M-i</kbd> anyway.
Index: Tests/xemacs_res/xemacs_23.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/xemacs_res/xemacs_23.html,v
retrieving revision 1.30
retrieving revision 1.31
diff -u -b -r1.30 -r1.31
--- Tests/xemacs_res/xemacs_23.html 5 Feb 2007 15:30:27 -0000 1.30
+++ Tests/xemacs_res/xemacs_23.html 3 Oct 2007 09:34:57 -0000 1.31
@@ -211,7 +211,7 @@
<a name="IDX767"></a>
<dl compact="compact">
<dt> <kbd>M-n</kbd></dt>
-<dd><p>Move to the beginning of the next line that isn't an nroff command
+<dd><p>Move to the beginning of the next line that isn’t an nroff command
(<code>forward-text-line</code>). An argument is a repeat count.
</p></dd>
<dt> <kbd>M-p</kbd></dt>
@@ -274,7 +274,7 @@
modes are designed for editing the two different input formats. The
command <kbd>M-x tex-mode</kbd> looks at the contents of a buffer to
determine whether it appears to be LaTeX input or not; it then
-selects the appropriate mode. If it can't tell which is right (e.g.,
+selects the appropriate mode. If it can’t tell which is right (e.g.,
the buffer is empty), the variable <code>tex-default-mode</code> controls
which mode is used.
</p>
@@ -447,7 +447,7 @@
</p>
<dl compact="compact">
<dt> <kbd>C-c C-r</kbd></dt>
-<dd><p>Invoke TeX on the current region, plus the buffer's header
+<dd><p>Invoke TeX on the current region, plus the buffer’s header
(<code>tex-region</code>).
</p></dd>
<dt> <kbd>C-c C-b</kbd></dt>
@@ -517,7 +517,7 @@
</p>
<p> In LaTeX mode, the header begins with
‘<samp>\documentstyle</samp>’ and ends
with <br>‘<samp>\begin{document}</samp>’. These are commands that
LaTeX requires
-you to use, so you don't need to do anything special to identify the
+you to use, so you don’t need to do anything special to identify the
header.
</p>
<a name="IDX794"></a>
@@ -790,10 +790,10 @@
visible (<code>show-children</code>).
</p></dd>
<dt> <kbd>M-x hide-entry</kbd></dt>
-<dd><p>Make this heading line's body invisible.
+<dd><p>Make this heading line’s body invisible.
</p></dd>
<dt> <kbd>M-x show-entry</kbd></dt>
-<dd><p>Make this heading line's body visible.
+<dd><p>Make this heading line’s body visible.
</p></dd>
</dl>
@@ -811,7 +811,7 @@
<a name="IDX815"></a>
<p> Two more powerful opposites are <kbd>C-c C-d</kbd>
(<code>hide-subtree</code>) and
<kbd>C-c C-s</kbd> (<code>show-subtree</code>). Both should be used when
point is
-on a heading line, and both apply to all the lines of that heading's
+on a heading line, and both apply to all the lines of that heading’s
<em>subtree</em>: its body, all its subheadings, both direct and indirect, and
all of their bodies. In other words, the subtree contains everything
following this heading line, up to and not including the next heading of
@@ -947,7 +947,7 @@
to. It can be given arguments just like <kbd>Meta-f</kbd>.
</p>
<a name="IDX836"></a>
-<p> The word commands' understanding of syntax is completely controlled by
+<p> The word commands’ understanding of syntax is completely controlled
by
the syntax table. For example, any character can be declared to be a word
delimiter. See section <a href="xemacs_30.html#SEC374">The Syntax Table</a>.
</p>
@@ -1000,7 +1000,7 @@
<kbd>Control-e</kbd>, which move to the beginning and end of a line. Unlike
their counterparts, <kbd>Meta-a</kbd> and <kbd>Meta-e</kbd> move over
successive
sentences if repeated or given numeric arguments. Emacs assumes
-the typist's convention is followed, and thus considers a sentence to
+the typist’s convention is followed, and thus considers a sentence to
end wherever there is a ‘<samp>.</samp>’,
‘<samp>?</samp>’, or ‘<samp>!</samp>’ followed by the
end of a line or two spaces, with any number of ‘<samp>)</samp>’,
‘<samp>]</samp>’,
‘<samp>'</samp>’, or ‘<samp>"</samp>’ characters
allowed in between. A sentence also
@@ -1081,7 +1081,7 @@
be useful even though there are no paragraphs per se.
</p>
<p> When there is a fill prefix, paragraphs are delimited by all lines
-which don't start with the fill prefix. See section <a href="#SEC210">Filling
Text</a>.
+which don’t start with the fill prefix. See section <a
href="#SEC210">Filling Text</a>.
</p>
<a name="IDX846"></a>
<a name="IDX847"></a>
@@ -1437,7 +1437,7 @@
<a name="IDX874"></a>
<p> To specify a fill prefix, move to a line that starts with the desired
prefix, put point at the end of the prefix, and give the command
-<kbd>C-x .</kbd> (<code>set-fill-prefix</code>). That's a period after the
+<kbd>C-x .</kbd> (<code>set-fill-prefix</code>). That’s a period after
the
<kbd>C-x</kbd>. To turn off the fill prefix, specify an empty prefix: type
<kbd>C-x .</kbd> with point at the beginning of a line.
</p>
Index: Tests/xemacs_res/xemacs_24.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/xemacs_res/xemacs_24.html,v
retrieving revision 1.32
retrieving revision 1.33
diff -u -b -r1.32 -r1.33
--- Tests/xemacs_res/xemacs_24.html 5 Feb 2007 15:30:27 -0000 1.32
+++ Tests/xemacs_res/xemacs_24.html 3 Oct 2007 09:34:57 -0000 1.33
@@ -159,7 +159,7 @@
</p>
<p> Each of the programming language modes defines the <TAB> key to run
an indentation function that knows the indentation conventions of that
-language and updates the current line's indentation accordingly. For
+language and updates the current line’s indentation accordingly. For
example, in C mode <TAB> is bound to <code>c-indent-line</code>.
<LFD>
is normally defined to do <RET> followed by <TAB>; thus it, too,
indents in a mode-specific fashion.
@@ -232,9 +232,9 @@
language you are working with), and escape characters that might be used
to quote those.
</p>
-<p> The other commands deal with expressions or <em>sexps</em>. The word
`sexp'
+<p> The other commands deal with expressions or <em>sexps</em>. The word
‘sexp’
is derived from <em>s-expression</em>, the term for a symbolic expression in
-Lisp. In Emacs, the notion of `sexp' is not limited to Lisp. It
+Lisp. In Emacs, the notion of ‘sexp’ is not limited to Lisp. It
refers to an expression in the language your program is written in.
Each programming language has its own major mode, which customizes the
syntax tables so that expressions in that language count as sexps.
@@ -365,7 +365,7 @@
<kbd>C-M-f</kbd>. In particular, a negative argument is useful for putting
the mark at the beginning of the previous sexp.
</p>
-<p> The list and sexp commands' understanding of syntax is completely
+<p> The list and sexp commands’ understanding of syntax is completely
controlled by the syntax table. Any character can, for example, be
declared to be an opening delimiter and act like an open parenthesis.
See section <a href="xemacs_30.html#SEC374">The Syntax Table</a>.
@@ -546,7 +546,7 @@
</p>
<p> <TAB> indents the second and following lines of the body of a
parenthetical grouping each under the preceding one; therefore, if you
-alter one line's indentation to be nonstandard, the lines below tend
+alter one line’s indentation to be nonstandard, the lines below tend
to follow it. This is the right behavior in cases where the standard
result of <TAB> does not look good.
</p>
@@ -750,7 +750,7 @@
<a name="IDX941"></a>
<p> If <code>c-tab-always-indent</code> is non-<code>nil</code>, the
<TAB> command
in C mode does indentation only if point is at the left margin or within
-the line's indentation. If there is non-whitespace to the left of point,
+the line’s indentation. If there is non-whitespace to the left of point,
<TAB> just inserts a tab character in the buffer. Normally,
this variable is <code>nil</code>, and <TAB> always reindents the
current line.
</p>
@@ -765,7 +765,7 @@
<dl compact="compact">
<dt> <code>c-indent-level</code></dt>
<dd><p>Indentation of C statements within surrounding block. The surrounding
-block's indentation is the indentation of the line on which the
+block’s indentation is the indentation of the line on which the
open-brace appears.
</p></dd>
<dt> <code>c-continued-statement-offset</code></dt>
@@ -825,7 +825,7 @@
<p> When <code>c-indent-level</code> is zero, the statements inside most
braces
line up exactly under the open brace. An exception are braces in column
-zero, like those surrounding a function's body. The statements inside
+zero, like those surrounding a function’s body. The statements inside
those braces are not placed at column zero. Instead,
<code>c-brace-offset</code> and <code>c-continued-statement-offset</code> (see
below) are added to produce a typical offset between brace levels, and
@@ -1098,7 +1098,7 @@
(<code>set-comment-column</code>) sets the comment column to the column point
is
at. <kbd>C-u C-x ;</kbd> sets the comment column to match the last comment
before point in the buffer, and then calls <kbd>Meta-;</kbd> to align the
-current line's comment under the previous one. Note that <kbd>C-u - C-x
;</kbd>
+current line’s comment under the previous one. Note that <kbd>C-u - C-x
;</kbd>
runs the function <code>kill-comment</code> as described above.
</p>
<p> <code>comment-column</code> is a per-buffer variable; altering the
variable
@@ -1311,7 +1311,7 @@
change log starts with a tab. One entry can describe several changes;
each change starts with a line starting with a tab and a star. <kbd>M-x
add-change-log-entry</kbd> visits the change log file and creates a new entry
-unless the most recent entry is for today's date and your name. In
+unless the most recent entry is for today’s date and your name. In
either case, it adds a new line to start the description of another
change just after the header line of the entry. When <kbd>M-x
add-change-log-entry</kbd> is finished, all is prepared for you to edit in
@@ -1382,7 +1382,7 @@
</p>
<p> Each entry in the tags table records the name of one tag, the name of the
file that the tag is defined in (implicitly), and the position in that file
-of the tag's definition.
+of the tag’s definition.
</p>
<p> Just what names from the described files are recorded in the tags table
depends on the programming language of the described file. They
@@ -1395,7 +1395,7 @@
<a name="IDX966"></a>
<a name="IDX967"></a>
<p>The Ebrowse is a separate facility tailored for C++, with tags and a
-class browser. See <a href="../ebrowse/index.html#Top">(ebrowse)Top</a>
section `Top' in <cite>Ebrowse User's Manual</cite>.
+class browser. See <a href="../ebrowse/index.html#Top">(ebrowse)Top</a>
section ‘Top’ in <cite>Ebrowse User’s Manual</cite>.
</p>
<table class="menu" border="0" cellspacing="0">
<tr><td align="left" valign="top"><a href="#SEC233">21.11.1 Source File Tag
Syntax</a></td><td> </td><td align="left" valign="top"> Tag
syntax for various types of code and text files.
@@ -1809,7 +1809,7 @@
</pre></td></tr></table>
<p>Note that tags are not generated for scripts so that you have to add a
-line by yourself of the form `###key <script-name>' if you want to jump
+line by yourself of the form ‘###key <script-name>’ if you
want to jump
to it.
</p>
</li><li>
@@ -1993,7 +1993,7 @@
that the specified substring appears in. To find other tags that match
the substring, give <code>find-tag</code> a numeric argument, as in <kbd>C-u
M-.</kbd>. This does not read a tag name, but continues searching the tag
-table's text for another tag containing the same substring last used.
+table’s text for another tag containing the same substring last used.
If your keyboard has a real <META> key, <kbd>M-0 M-.</kbd> is an easier
alternative to <kbd>C-u M-.</kbd>.
</p>
Index: Tests/xemacs_res/xemacs_25.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/xemacs_res/xemacs_25.html,v
retrieving revision 1.34
retrieving revision 1.35
diff -u -b -r1.34 -r1.35
--- Tests/xemacs_res/xemacs_25.html 5 Feb 2007 15:30:27 -0000 1.34
+++ Tests/xemacs_res/xemacs_25.html 3 Oct 2007 09:34:57 -0000 1.35
@@ -134,7 +134,7 @@
<p> To run <code>make</code> or another compiler, type <kbd>M-x
compile</kbd>. This
command reads a shell command line using the minibuffer, then executes
the specified command line in an inferior shell with output going to the
-buffer named ‘<samp>*compilation*</samp>’. By default, the
current buffer's
+buffer named ‘<samp>*compilation*</samp>’. By default, the
current buffer’s
default directory is used as the working directory for the execution of
the command; therefore, the makefile comes from this directory.
</p>
@@ -192,7 +192,7 @@
lines on which matches were found. To do this, type <kbd>M-x grep</kbd> with
an argument line that contains the same arguments you would give to
<code>grep</code>: a <code>grep</code>-style regexp (usually in single quotes
to
-quote the shell's special characters) followed by filenames, which may
+quote the shell’s special characters) followed by filenames, which may
use wildcard characters. The output from <code>grep</code> goes in the
‘<samp>*compilation*</samp>’ buffer. You can use <kbd>C-x `</kbd>
to find the lines that
match as if they were compilation errors.
@@ -201,10 +201,10 @@
run in interactive mode. In particular, this means that the shell starts
up with no prompt. If you find your usual shell prompt making an
unsightly appearance in the ‘<samp>*compilation*</samp>’ buffer,
it means you
-have made a mistake in your shell's initialization file
(‘<tt>.cshrc</tt>’
+have made a mistake in your shell’s initialization file
(‘<tt>.cshrc</tt>’
or ‘<tt>.shrc</tt>’ or …) by setting the prompt
unconditionally. The
shell initialization file should set the prompt only if there already is
-a prompt. Here's how to do it in <code>csh</code>:
+a prompt. Here’s how to do it in <code>csh</code>:
</p>
<table><tr><td> </td><td><pre class="example">if ($?prompt) set prompt =
...
</pre></td></tr></table>
@@ -374,7 +374,7 @@
<p>The variable is initialized by the <b>EMACSLOADPATH</b> environment
variable. If no value is specified, the variable takes the default value
specified in the file ‘<tt>paths.h</tt>’ when Emacs was built. If
a path
-isn't specified in ‘<tt>paths.h</tt>’, a default value is obtained
from the
+isn’t specified in ‘<tt>paths.h</tt>’, a default value is
obtained from the
file system, near the directory in which the Emacs executable resides.
</p>
<a name="IDX1030"></a>
@@ -536,7 +536,7 @@
</p>
<p> You cannot currently byte-compile converted Mocklisp code.
The reason is that converted Mocklisp code uses some special Lisp features
-to deal with Mocklisp's incompatible ideas of how arguments are evaluated
+to deal with Mocklisp’s incompatible ideas of how arguments are evaluated
and which values signify “true” or “false”.
</p>
<hr size="6">
@@ -696,7 +696,7 @@
you can switch buffers, visit files, and perform any other editing
operations. However, the debugger is a recursive editing level
(see section <a href="xemacs_29.html#SEC346">Recursive Editing Levels</a>); it
is a good idea to return to the backtrace
-buffer and explicitly exit the debugger when you don't want to use it any
+buffer and explicitly exit the debugger when you don’t want to use it any
more. Exiting the debugger kills the backtrace buffer.
</p>
<a name="IDX1051"></a>
@@ -733,7 +733,7 @@
that invoke the debugger on exit are flagged with stars.
</p></dd>
<dt> <kbd>u</kbd></dt>
-<dd><p>Don't enter the debugger when the current frame is exited. This
+<dd><p>Don’t enter the debugger when the current frame is exited. This
cancels a <kbd>b</kbd> command on a frame.
</p></dd>
<dt> <kbd>e</kbd></dt>
@@ -756,12 +756,12 @@
then the value specified in the <kbd>r</kbd> command is used as the value of
that frame.
</p>
-<p>The debugger's return value also matters with many errors. For example,
-<code>wrong-type-argument</code> errors will use the debugger's return value
+<p>The debugger’s return value also matters with many errors. For
example,
+<code>wrong-type-argument</code> errors will use the debugger’s return
value
instead of the invalid argument; <code>no-catch</code> errors will use the
debugger value as a throw tag instead of the tag that was not found.
If an error was signaled by calling the Lisp function <code>signal</code>,
-the debugger's return value is returned as the value of <code>signal</code>.
+the debugger’s return value is returned as the value of
<code>signal</code>.
</p></dd>
</dl>
@@ -790,7 +790,7 @@
provided for evaluating Lisp expressions interactively inside Emacs. Both
the expressions you evaluate and their output goes in the buffer.
</p>
-<p> The ‘<samp>*scratch*</samp>’ buffer's major mode is Lisp
Interaction mode, which
+<p> The ‘<samp>*scratch*</samp>’ buffer’s major mode is
Lisp Interaction mode, which
is the same as Emacs-Lisp mode except for one command, <LFD>. In
Emacs-Lisp mode, <LFD> is an indentation command. In Lisp
Interaction mode, <LFD> is bound to <code>eval-print-last-sexp</code>.
This
@@ -953,7 +953,7 @@
related but otherwise independent lisp files. These files are bundled
together for download convenience and individual files may be deleted at
will without any loss of functionality. However, we would recommend
-that you follow this rule of thumb: "When in doubt, don't delete".
+that you follow this rule of thumb: "When in doubt, don’t
delete".
</li></ul>
<hr size="6">
@@ -1022,7 +1022,7 @@
<td valign="middle" align="left">[<a href="xemacs_abt.html#SEC_About"
title="About (help)"> ? </a>]</td>
</tr></table>
<h3 class="subsection"> 22.8.4 Source Packages </h3>
-<p>Source packages contain all of the Package author's (where appropriate
+<p>Source packages contain all of the Package author’s (where appropriate
in regular packages) source code plus all of the files necessary to
build distribution tarballs (Unix Tar format files, gzipped for space
savings).
@@ -1110,7 +1110,7 @@
idea to install all packages and not interfere with the wishes of your
users.
</p>
-<p>If you can't find which package provides the feature you require, try
+<p>If you can’t find which package provides the feature you require, try
using the <code>package-get-package-provider</code> function. Eg., if you know
that you need <code>thingatpt</code>, type:
</p>
@@ -1143,7 +1143,7 @@
<p>There are three main ways to install packages:
</p>
<table class="menu" border="0" cellspacing="0">
-<tr><td align="left" valign="top"><a href="#Sumo">•
Sumo</a></td><td> </td><td align="left" valign="top">
All at once, using the 'Sumo Tarball'.
+<tr><td align="left" valign="top"><a href="#Sumo">•
Sumo</a></td><td> </td><td align="left" valign="top">
All at once, using the ’Sumo Tarball’.
</td></tr>
<tr><td align="left" valign="top"><a href="#Manually">•
Manually</a></td><td> </td><td align="left" valign="top">
Using individual package tarballs.
</td></tr>
@@ -1167,7 +1167,7 @@
</p>
<p>For an XEmacs compiled with Mule you also need:
‘<tt>xemacs-mule-sumo.tar.gz</tt>’
</p>
-<p>N.B. They are called 'Sumo Tarballs' for good reason. They are
+<p>N.B. They are called ’Sumo Tarballs’ for good reason. They are
currently about 19MB and 4.5MB (gzipped) respectively.
</p>
<p>Install them by:
@@ -1190,7 +1190,7 @@
a fresh install it is sufficient to untar the file at the top of the
package hierarchy.
</p>
-<p>Note: If you are upgrading packages already installed, it's best to
+<p>Note: If you are upgrading packages already installed, it’s best to
remove the old package first <a href="#Removing-Packages">Removing
Packages</a>.
</p>
<p>For example if we are installing the ‘<tt>xemacs-base</tt>’
@@ -1287,7 +1287,7 @@
<p>From here, you can select or unselect packages for installation using
the <RET> key, the <kbd>Mouse-2</kbd> button or selecting
"Select" from
the (Popup) Menu.
-Once you've finished selecting the packages, you can
+Once you’ve finished selecting the packages, you can
press the <kbd>x</kbd> key (or use the menu) to actually install the
packages. Note that you will have to restart XEmacs for XEmacs to
recognize any new packages.
@@ -1340,7 +1340,7 @@
those packages also.
</p>
<p>For novices and gurus alike, this step can save your bacon.
-It's easy to forget to install a critical package.
+It’s easy to forget to install a critical package.
</p>
</li><li>
Download and install the packages.
@@ -1368,7 +1368,7 @@
edit-utils, fsf-compat, mail-lib, net-utils, os-utils, prog-modes,
text-modes, time
</p>
-<p>If you are using the XEmacs package tools, don't forget to do:
+<p>If you are using the XEmacs package tools, don’t forget to do:
</p>
<p> Packages -> Add Required
</p>
@@ -1387,7 +1387,7 @@
‘<tt>pgkinfo/MANIFEST.pkgname</tt>’ file which list all the files
belonging
to the package.
</p>
-<p>No need to panic, you don't have to go through the
+<p>No need to panic, you don’t have to go through the
‘<tt>pkinfo/MANIFEST.pkgname</tt>’ and manually delete the files.
Instead, use
<code>M-x package-get-delete-package RET</code>.
</p>
@@ -1529,13 +1529,13 @@
file, ‘<tt>Local.rules.template</tt>’. Simply copy that to
‘<tt>Local.rules</tt>’ and edit it to suit your needs.
</p>
-<p>These are the variables in 'Local.rules' that you will need to
+<p>These are the variables in ’Local.rules’ that you will need to
address.
</p>
<dl compact="compact">
<dt> <var>symlink =</var> </dt>
-<dd><p>Set this to 't' if you want to do a "run in place".
-Setting this doesn't work well with 'make bindist'
+<dd><p>Set this to ’t’ if you want to do a "run in
place".
+Setting this doesn’t work well with ’make bindist’
</p>
</dd>
<dt> <var>XEMACS_PACKAGES =</var></dt>
@@ -1557,11 +1557,11 @@
</dd>
<dt> <var>BUILD_WITHOUT_MULE =</var></dt>
<dd><p>Building from CVS defaults to building the Mule
-packages. Set this to 't' if you don't want/have Mule
+packages. Set this to ’t’ if you don’t want/have Mule
</p>
</dd>
<dt> <var>MULE_PACKAGES =</var></dt>
-<dd><p>Same as for 'XEMACS_PACKAGES' except you list the Mule
+<dd><p>Same as for ’XEMACS_PACKAGES’ except you list the Mule
packages you want to install here. eg:
</p><table><tr><td> </td><td><pre class="example"> MULE_PACKAGES =
mule-packages/mule-base mule-packages/skk
</pre></td></tr></table>
@@ -1569,15 +1569,15 @@
</dd>
<dt> <var>MULE_STAGING = ${XEMACS_PACKAGES_BASE}/../Mule-Packages</var></dt>
<dd><p>Set this to where you want Mule packages installed
-to. Note: 'make bindist' does not use this variable.
+to. Note: ’make bindist’ does not use this variable.
</p>
</dd>
<dt> <var>XEMACS = xemacs</var></dt>
-<dd><p>If your XEmacs isn't in your path, change this.
+<dd><p>If your XEmacs isn’t in your path, change this.
</p>
</dd>
<dt> <var>XEMACS_NATIVE_NT =</var></dt>
-<dd><p>Set this to 't' if you are building on WinNT.
+<dd><p>Set this to ’t’ if you are building on WinNT.
</p>
</dd>
<dt> <var>INSTALL = install -c</var></dt>
@@ -1660,7 +1660,7 @@
‘<tt>Imakefile</tt>’ or an <code>automake</code> file: the
complexity is hidden in
generic rules files, in this case the ‘<tt>XEmacs.rules</tt>’
include file
in the top directory of the packages hierarchy. Although a number of
-facilities are available for complex libraries, most simple packages'
+facilities are available for complex libraries, most simple packages’
‘<tt>Makefile</tt>’s contain a copyright notice, a few variable
definitions,
an include for ‘<tt>XEmacs.rules</tt>’, and a couple of standard
targets.
</p>
@@ -1741,8 +1741,8 @@
<a name="SEC282"></a>
<h2 class="heading"> Available Packages: </h2>
<p>This section lists the Lisp packages that are currently available from
-xemacs.org and it's mirrors. If a particular package that you are
-looking for isn't here, please send a message to the
+xemacs.org and it’s mirrors. If a particular package that you are
+looking for isn’t here, please send a message to the
<a href="mailto:address@hidden";>XEmacs Beta list</a>.
</p>
<p>This data is up to date as of September 22, 2002.
@@ -1836,7 +1836,7 @@
</dd>
<dt> ‘<tt>edit-utils</tt>’</dt>
<dd><p>Single file lisp packages for various XEmacs goodies. Load this and
-weed out the junk you don't want.
+weed out the junk you don’t want.
</p>
</dd>
<dt> ‘<tt>edt</tt>’</dt>
@@ -1960,7 +1960,7 @@
</p>
</dd>
<dt> ‘<tt>mine</tt>’</dt>
-<dd><p>Elisp implementation of the game 'Minehunt'.
+<dd><p>Elisp implementation of the game ’Minehunt’.
</p>
</dd>
<dt> ‘<tt>misc-games</tt>’</dt>
@@ -2028,7 +2028,7 @@
</p>
</dd>
<dt> ‘<tt>rmail</tt>’</dt>
-<dd><p>An obsolete Emacs mailer. If you do not already use it don't start.
+<dd><p>An obsolete Emacs mailer. If you do not already use it don’t
start.
</p>
</dd>
<dt> ‘<tt>ruby-modes</tt>’</dt>
@@ -2226,7 +2226,7 @@
</p>
</dd>
<dt> ‘<tt>lookup</tt>’</dt>
-<dd><p>Dictionary support. (This isn't an English dictionary program)
+<dd><p>Dictionary support. (This isn’t an English dictionary program)
</p>
</dd>
<dt> ‘<tt>mule-base</tt>’</dt>
Index: Tests/xemacs_res/xemacs_26.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/xemacs_res/xemacs_26.html,v
retrieving revision 1.27
retrieving revision 1.28
diff -u -b -r1.27 -r1.28
--- Tests/xemacs_res/xemacs_26.html 5 Feb 2007 15:30:27 -0000 1.27
+++ Tests/xemacs_res/xemacs_26.html 3 Oct 2007 09:34:57 -0000 1.28
@@ -329,7 +329,7 @@
word at the beginning is the abbrev. The number that appears is the number
of times the abbrev has been expanded. Emacs keeps track of this to help
you see which abbrevs you actually use, in case you want to eliminate
-those that you don't use often. The string at the end of the line is the
+those that you don’t use often. The string at the end of the line is the
expansion.
</p>
<a name="IDX1078"></a>
Index: Tests/xemacs_res/xemacs_28.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/xemacs_res/xemacs_28.html,v
retrieving revision 1.27
retrieving revision 1.28
diff -u -b -r1.27 -r1.28
--- Tests/xemacs_res/xemacs_28.html 5 Feb 2007 15:30:27 -0000 1.27
+++ Tests/xemacs_res/xemacs_28.html 3 Oct 2007 09:34:57 -0000 1.28
@@ -272,10 +272,10 @@
</p>
<p>In this version of Emacs, what you see is what you get: in contrast to
some other versions, no abbreviations are expanded after you have sent the
-mail. This means you don't suffer the annoyance of having the system do
+mail. This means you don’t suffer the annoyance of having the system do
things behind your back—if the system rewrites an address you typed,
you know it immediately, instead of after the mail has been sent and
-it's too late to do anything about it. For example, you will never
+it’s too late to do anything about it. For example, you will never
again be in trouble because you forgot to delete an old alias from your
‘<tt>.mailrc</tt>’ and a new local user is given a userid which
conflicts
with one of your aliases.
Index: Tests/xemacs_res/xemacs_29.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/xemacs_res/xemacs_29.html,v
retrieving revision 1.32
retrieving revision 1.33
diff -u -b -r1.32 -r1.33
--- Tests/xemacs_res/xemacs_29.html 5 Feb 2007 15:30:27 -0000 1.32
+++ Tests/xemacs_res/xemacs_29.html 3 Oct 2007 09:34:57 -0000 1.33
@@ -119,7 +119,7 @@
<p> <kbd>Button2</kbd> in the calendar brings up a menu of operations on a
particular date; <kbd>Buttons3</kbd> brings up a menu of commonly used
calendar features that are independent of any particular date. To exit
-the calendar, type <kbd>q</kbd>. See <a
href="../lispref/Calendar.html#Calendar">Customizing the Calendar and Diary:
(lispref)Calendar</a> section `Calendar' in <cite>The XEmacs Lisp Reference
Manual</cite>, for customization
+the calendar, type <kbd>q</kbd>. See <a
href="../lispref/Calendar.html#Calendar">Customizing the Calendar and Diary:
(lispref)Calendar</a> section ‘Calendar’ in <cite>The XEmacs Lisp
Reference Manual</cite>, for customization
information about the calendar and diary.
</p>
<table class="menu" border="0" cellspacing="0">
@@ -265,7 +265,7 @@
<a name="IDX1156"></a>
<p> The commands for motion by months and years work like those for
weeks, but move a larger distance. The month commands <kbd>M-}</kbd> and
-<kbd>M-{</kbd> move forward or backward by an entire month's time. The
+<kbd>M-{</kbd> move forward or backward by an entire month’s time. The
year commands <kbd>C-x ]</kbd> and <kbd>C-x [</kbd> move forward or backward a
whole year.
</p>
@@ -383,7 +383,7 @@
<dd><p>Center calendar around specified month
(<code>calendar-other-month</code>).
</p></dd>
<dt> <kbd>.</kbd></dt>
-<dd><p>Move point to today's date (<code>calendar-goto-today</code>).
+<dd><p>Move point to today’s date (<code>calendar-goto-today</code>).
</p></dd>
</dl>
@@ -401,7 +401,7 @@
</p>
<a name="IDX1176"></a>
<a name="IDX1177"></a>
-<p> You can return to today's date with <kbd>.</kbd>
+<p> You can return to today’s date with <kbd>.</kbd>
(<code>calendar-goto-today</code>).
</p>
<hr size="6">
@@ -505,7 +505,7 @@
</p>
<dl compact="compact">
<dt> <kbd>C-SPC</kbd></dt>
-<dd><p>Set the mark to today's date (<code>calendar-set-mark</code>).
+<dd><p>Set the mark to today’s date (<code>calendar-set-mark</code>).
</p></dd>
<dt> <kbd>C-@</kbd></dt>
<dd><p>The same.
@@ -756,7 +756,7 @@
(<code>list-calendar-holidays</code>).
</p></dd>
<dt> <kbd>M-x holidays</kbd></dt>
-<dd><p>List all holidays for three months around today's date in another
+<dd><p>List all holidays for three months around today’s date in another
window.
</p></dd>
<dt> <kbd>M-x list-holidays</kbd></dt>
@@ -795,7 +795,7 @@
<a name="IDX1215"></a>
<p> The command <kbd>M-x holidays</kbd> displays the list of holidays for the
current month and the preceding and succeeding months; this works even
-if you don't have a calendar window. If you want the list of holidays
+if you don’t have a calendar window. If you want the list of holidays
centered around a different month, use <kbd>C-u M-x holidays</kbd>, which
prompts for the month and year.
</p>
@@ -807,7 +807,7 @@
<p> The command <kbd>M-x list-holidays</kbd> displays the list of holidays
for
a range of years. This function asks you for the starting and stopping
years, and allows you to choose all the holidays or one of several
-categories of holidays. You can use this command even if you don't have
+categories of holidays. You can use this command even if you don’t have
a calendar window.
</p>
<p> The dates used by Emacs for holidays are based on <em>current
@@ -851,7 +851,7 @@
<dd><p>Display times of sunrise and sunset for the date you click on.
</p></dd>
<dt> <kbd>M-x sunrise-sunset</kbd></dt>
-<dd><p>Display times of sunrise and sunset for today's date.
+<dd><p>Display times of sunrise and sunset for today’s date.
</p></dd>
<dt> <kbd>C-u M-x sunrise-sunset</kbd></dt>
<dd><p>Display times of sunrise and sunset for a specified date.
@@ -866,7 +866,7 @@
<kbd>S</kbd>. Alternatively, click <kbd>Button2</kbd> on the date, then choose
<kbd>Sunrise/Sunset</kbd> from the menu that appears. The command <kbd>M-x
sunrise-sunset</kbd> is available outside the calendar to display this
-information for today's date or a specified date. To specify a date
+information for today’s date or a specified date. To specify a date
other than today, use <kbd>C-u M-x sunrise-sunset</kbd>, which prompts for
the year, month, and day.
</p>
@@ -952,7 +952,7 @@
</p></dd>
<dt> <kbd>M-x phases-of-moon</kbd></dt>
<dd><p>Display dates and times of the quarters of the moon for three months
around
-today's date.
+today’s date.
</p></dd>
</dl>
@@ -1023,7 +1023,7 @@
<p> If you are interested in these calendars, you can convert dates one at a
time. Put point on the desired date of the Gregorian calendar and press the
appropriate keys. The <kbd>p</kbd> is a mnemonic for “print”
since Emacs
-“prints' the equivalent date in the echo area.
+“prints’ the equivalent date in the echo area.
</p><hr size="6">
<a name="Calendar-Systems"></a>
<a name="SEC314"></a>
@@ -1197,7 +1197,7 @@
calendars is to click on it with <kbd>Button2</kbd>, then choose <kbd>Other
Calendars</kbd> from the menu that appears. This displays the equivalent
forms of the date in all the calendars Emacs understands, in the form of
-a menu. (Choosing an alternative from this menu doesn't actually do
+a menu. (Choosing an alternative from this menu doesn’t actually do
anything—the menu is used only for display.)
</p>
<p> Put point on the desired date of the Gregorian calendar, then type the
@@ -1285,9 +1285,9 @@
<p> These commands ask you for a date on the other calendar, move point to
the Gregorian calendar date equivalent to that date, and display the
-other calendar's date in the echo area. Emacs uses strict completion
+other calendar’s date in the echo area. Emacs uses strict completion
(see section <a href="xemacs_9.html#SEC63">Completion</a>) whenever it asks
you to type a month name, so you
-don't have to worry about the spelling of Hebrew, Islamic, or French names.
+don’t have to worry about the spelling of Hebrew, Islamic, or French
names.
</p>
<a name="IDX1263"></a>
<a name="IDX1264"></a>
@@ -1404,7 +1404,7 @@
haab/tzolkin date combination you have typed is impossible.
</p>
<p> Emacs uses strict completion (see section <a
href="xemacs_9.html#SEC63">Completion</a>) whenever it
-asks you to type a Mayan name, so you don't have to worry about
+asks you to type a Mayan name, so you don’t have to worry about
spelling.
</p>
<hr size="6">
@@ -1495,7 +1495,7 @@
<h3 class="subsection"> 26.5.3 Commands Displaying Diary Entries </h3>
<p> Once you have created a ‘<tt>~/diary</tt>’ file, you can use
the calendar
-to view it. You can also view today's events outside of Calendar mode.
+to view it. You can also view today’s events outside of Calendar mode.
</p>
<dl compact="compact">
<dt> <kbd>d</kbd></dt>
@@ -1519,7 +1519,7 @@
<dd><p>Print hard copy of the diary display as it appears.
</p></dd>
<dt> <kbd>M-x diary</kbd></dt>
-<dd><p>Display all diary entries for today's date.
+<dd><p>Display all diary entries for today’s date.
</p></dd>
<dt> <kbd>M-x diary-mail-entries</kbd></dt>
<dd><p>Mail yourself email reminders about upcoming diary entries.
@@ -1559,7 +1559,7 @@
the <kbd>s</kbd> command.
</p>
<p> Display of selected diary entries uses the selective display feature
-to hide entries that don't apply.
+to hide entries that don’t apply.
</p>
<a name="IDX1284"></a>
<p> The diary buffer as you see it is an illusion, so simply printing the
@@ -1576,7 +1576,7 @@
how many days to include (see section <a
href="xemacs_30.html#SEC351">Customization</a>).
</p>
<p> If you put <code>(diary)</code> in your init file, this
-automatically displays a window with the day's diary entries, when you
+automatically displays a window with the day’s diary entries, when you
enter Emacs. See section <a href="xemacs_30.html#SEC377">The Init File</a>.
The mode line of the displayed window
shows the date and any holidays that fall on that date.
</p>
@@ -1634,7 +1634,7 @@
</p>
<p> If the first line of a diary entry consists only of the date or day
name with no following blanks or punctuation, then the diary window
-display doesn't include that line; only the continuation lines appear.
+display doesn’t include that line; only the continuation lines appear.
For example, this entry:
</p>
<table><tr><td> </td><td><pre class="example">02/11/1989
@@ -1647,8 +1647,8 @@
</pre></td></tr></table>
<p>appears in the diary window without the date line at the beginning.
-This style of entry looks neater when you display just a single day's
-entries, but can cause confusion if you ask for more than one day's
+This style of entry looks neater when you display just a single day’s
+entries, but can cause confusion if you ask for more than one day’s
entries.
</p>
<p> You can edit the diary entries as they appear in the window, but it is
@@ -1711,7 +1711,7 @@
is, you can use ‘<samp>11/12/1989</samp>’ or
‘<samp>11/12/89</samp>’.
</p>
<p> Dates can also have the form ‘<samp><var>monthname</var>
<var>day</var></samp>’ or
-‘<samp><var>monthname</var> <var>day</var>,
<var>year</var></samp>’, where the month's name can
+‘<samp><var>monthname</var> <var>day</var>,
<var>year</var></samp>’, where the month’s name can
be spelled in full or abbreviated to three characters (with or without a
period). Case is not significant.
</p>
@@ -1915,7 +1915,7 @@
</p>
<p> Marking sexp diary entries in the calendar is <em>extremely</em>
time-consuming, since every date visible in the calendar window must be
-individually checked. So it's a good idea to make sexp diary entries
+individually checked. So it’s a good idea to make sexp diary entries
nonmarking (with ‘<samp>&</samp>’) when possible.
</p>
<p> Another sophisticated kind of sexp entry, a <em>floating</em> diary entry,
@@ -2091,7 +2091,7 @@
<p> The variable <code>today-visible-calendar-hook</code> is a normal hook run
after the calendar buffer has been prepared with the calendar when the
current date is visible in the window. One use of this hook is to
-replace today's date with asterisks; to do that, use the hook function
+replace today’s date with asterisks; to do that, use the hook function
<code>calendar-star-date</code>.
</p>
<a name="IDX1317"></a>
@@ -2099,14 +2099,14 @@
</pre></td></tr></table>
<p>Another standard hook function marks the current date, either by
-changing its face or by adding an asterisk. Here's how to use it:
+changing its face or by adding an asterisk. Here’s how to use it:
</p>
<a name="IDX1318"></a>
<table><tr><td> </td><td><pre class="example">(add-hook
'today-visible-calendar-hook 'calendar-mark-today)
</pre></td></tr></table>
<a name="IDX1319"></a>
-<p>The variable <code>calendar-today-marker</code> specifies how to mark
today's
+<p>The variable <code>calendar-today-marker</code> specifies how to mark
today’s
date. Its value should be a character to insert next to the date or a
face name to use for displaying the date. A face named
<code>calendar-today-face</code> is provided for this purpose; that symbol is
@@ -2216,7 +2216,7 @@
<dt> <code>(holiday-sexp <var>sexp</var> <var>string</var>)</code></dt>
<dd><p>A date calculated by the Lisp expression <var>sexp</var>. The
expression
should use the variable <code>year</code> to compute and return the date of a
-holiday, or <code>nil</code> if the holiday doesn't happen this year. The
+holiday, or <code>nil</code> if the holiday doesn’t happen this year.
The
value of <var>sexp</var> must represent the date as a list of the form
<code>(<var>month</var> <var>day</var> <var>year</var>)</code>.
<var>string</var> is the name of
the holiday.
@@ -2267,12 +2267,12 @@
</pre></td></tr></table>
<p>adds the last day of Hanukkah (since the Hebrew months are numbered with
-1 starting from Nisan), the Islamic feast celebrating Mohammed's
+1 starting from Nisan), the Islamic feast celebrating Mohammed’s
birthday (since the Islamic months are numbered from 1 starting with
-Muharram), and Thomas Jefferson's birthday, which is 2 April 1743 on the
+Muharram), and Thomas Jefferson’s birthday, which is 2 April 1743 on the
Julian calendar.
</p>
-<p> To include a holiday conditionally, use either Emacs Lisp's
<code>if</code> or the
+<p> To include a holiday conditionally, use either Emacs Lisp’s
<code>if</code> or the
<code>holiday-sexp</code> form. For example, American presidential elections
occur on the first Tuesday after the first Monday in November of years
divisible by 4:
@@ -2297,7 +2297,7 @@
"US Presidential Election"))
</pre></td></tr></table>
-<p> Some holidays just don't fit into any of these forms because special
+<p> Some holidays just don’t fit into any of these forms because special
calculations are involved in their determination. In such cases you
must write a Lisp function to do the calculation. To include eclipses,
for example, add <code>(eclipses)</code> to <code>other-holidays</code>
@@ -2491,7 +2491,7 @@
<p> The two variables <code>calendar-daylight-savings-starts-time</code> and
<code>calendar-daylight-savings-ends-time</code> specify the number of minutes
after midnight local time when the transition to and from daylight
-savings time should occur. For Cambridge, Massachusetts both variables'
+savings time should occur. For Cambridge, Massachusetts both variables’
values are 120.
</p>
<hr size="6">
@@ -2518,7 +2518,7 @@
<p> Ordinarily, the mode line of the diary buffer window indicates any
holidays that fall on the date of the diary entries. The process of
checking for holidays can take several seconds, so including holiday
-information delays the display of the diary buffer noticeably. If you'd
+information delays the display of the diary buffer noticeably. If you’d
prefer to have a faster display of the diary buffer but without the
holiday information, set the variable <code>holidays-in-diary-buffer</code> to
<code>nil</code>.
@@ -2528,13 +2528,13 @@
days of diary entries to be displayed at one time. It affects the
initial display when <code>view-diary-entries-initially</code> is
<code>t</code>, as
well as the command <kbd>M-x diary</kbd>. For example, the default value is
-1, which says to display only the current day's diary entries. If the
-value is 2, both the current day's and the next day's entries are
+1, which says to display only the current day’s diary entries. If the
+value is 2, both the current day’s and the next day’s entries are
displayed. The value can also be a vector of seven elements: for
example, if the value is <code>[0 2 2 2 2 4 1]</code> then no diary entries
-appear on Sunday, the current date's and the next day's diary entries
-appear Monday through Thursday, Friday through Monday's entries appear
-on Friday, while on Saturday only that day's entries appear.
+appear on Sunday, the current date’s and the next day’s diary
entries
+appear Monday through Thursday, Friday through Monday’s entries appear
+on Friday, while on Saturday only that day’s entries appear.
</p>
<a name="IDX1333"></a>
<a name="IDX1334"></a>
@@ -2584,7 +2584,7 @@
<p>Emacs matches of the diary entries with the date forms is done with the
standard syntax table from Fundamental mode
-(see <a href="../lispref/Syntax-Tables.html#Syntax-Tables">(lispref)Syntax
Tables</a> section `Syntax Tables' in <cite>XEmacs Lisp Reference
Manual</cite>),
+(see <a href="../lispref/Syntax-Tables.html#Syntax-Tables">(lispref)Syntax
Tables</a> section ‘Syntax Tables’ in <cite>XEmacs Lisp Reference
Manual</cite>),
but with the ‘<samp>*</samp>’ changed so that it is a word
constituent.
</p>
<p> The date patterns in the list must be <em>mutually exclusive</em> and
@@ -2634,7 +2634,7 @@
<p> Your diary file can have entries based on Hebrew or Islamic dates, as
well as entries based on the world-standard Gregorian calendar.
However, because recognition of such entries is time-consuming and most
-people don't use them, you must explicitly enable their use. If you
+people don’t use them, you must explicitly enable their use. If you
want the diary to recognize Hebrew-date diary entries, for example,
you must do this:
</p>
@@ -2777,7 +2777,7 @@
</p>
<a name="IDX1351"></a>
<p> If you use the fancy diary display, you can use the normal hook
-<code>list-diary-entries-hook</code> to sort each day's diary entries by their
+<code>list-diary-entries-hook</code> to sort each day’s diary entries by
their
time of day. Add this line to your init file:
</p>
<a name="IDX1352"></a>
@@ -2938,36 +2938,36 @@
<a name="IDX1368"></a>
<dl compact="compact">
<dt> <code>%%(diary-sunrise-sunset)</code></dt>
-<dd><p>Make a diary entry for the local times of today's sunrise and sunset.
+<dd><p>Make a diary entry for the local times of today’s sunrise and
sunset.
</p></dd>
<dt> <code>%%(diary-phases-of-moon)</code></dt>
<dd><p>Make a diary entry for the phases (quarters) of the moon.
</p></dd>
<dt> <code>%%(diary-day-of-year)</code></dt>
-<dd><p>Make a diary entry with today's day number in the current year and the
number
+<dd><p>Make a diary entry with today’s day number in the current year
and the number
of days remaining in the current year.
</p></dd>
<dt> <code>%%(diary-iso-date)</code></dt>
-<dd><p>Make a diary entry with today's equivalent ISO commercial date.
+<dd><p>Make a diary entry with today’s equivalent ISO commercial date.
</p></dd>
<dt> <code>%%(diary-julian-date)</code></dt>
-<dd><p>Make a diary entry with today's equivalent date on the Julian calendar.
+<dd><p>Make a diary entry with today’s equivalent date on the Julian
calendar.
</p></dd>
<dt> <code>%%(diary-astro-day-number)</code></dt>
-<dd><p>Make a diary entry with today's equivalent astronomical (Julian) day
number.
+<dd><p>Make a diary entry with today’s equivalent astronomical (Julian)
day number.
</p></dd>
<dt> <code>%%(diary-hebrew-date)</code></dt>
-<dd><p>Make a diary entry with today's equivalent date on the Hebrew calendar.
+<dd><p>Make a diary entry with today’s equivalent date on the Hebrew
calendar.
</p></dd>
<dt> <code>%%(diary-islamic-date)</code></dt>
-<dd><p>Make a diary entry with today's equivalent date on the Islamic calendar.
+<dd><p>Make a diary entry with today’s equivalent date on the Islamic
calendar.
</p></dd>
<dt> <code>%%(diary-french-date)</code></dt>
-<dd><p>Make a diary entry with today's equivalent date on the French
Revolutionary
+<dd><p>Make a diary entry with today’s equivalent date on the French
Revolutionary
calendar.
</p></dd>
<dt> <code>%%(diary-mayan-date)</code></dt>
-<dd><p>Make a diary entry with today's equivalent date on the Mayan calendar.
+<dd><p>Make a diary entry with today’s equivalent date on the Mayan
calendar.
</p></dd>
</dl>
@@ -2976,7 +2976,7 @@
<table><tr><td> </td><td><pre
class="smallexample">&%%(diary-hebrew-date)
</pre></td></tr></table>
-<p>causes every day's diary display to contain the equivalent date on the
+<p>causes every day’s diary display to contain the equivalent date on the
Hebrew calendar, if you are using the fancy diary display. (With simple
diary display, the line ‘<samp>&%%(diary-hebrew-date)</samp>’
appears in the
diary for any date, but does nothing particularly useful.)
@@ -3103,8 +3103,8 @@
identify a <em>sort key</em> for each record, and then reorder the records
using the order determined by the sort keys. The records are ordered so
that their keys are in alphabetical order, or, for numerical sorting, in
-numerical order. In alphabetical sorting, all upper-case letters `A'
-through `Z' come before lower-case `a', in accordance with the ASCII
+numerical order. In alphabetical sorting, all upper-case letters
‘A’
+through ‘Z’ come before lower-case ‘a’, in accordance
with the ASCII
character sequence.
</p>
<p> The sort commands differ in how they divide the text into sort
@@ -3182,7 +3182,7 @@
whether the file has changed on disk since it was last visited or
</pre></td></tr></table>
-<p>where the upper case `O' comes before all lower case letters. If you apply
+<p>where the upper case ‘O’ comes before all lower case letters.
If you apply
instead <kbd>C-u 2 M-x sort-fields</kbd> you get:
</p>
<table><tr><td> </td><td><pre class="smallexample">saved. If it has, you
are asked to confirm that you want to change
@@ -3200,7 +3200,7 @@
columns by putting point at one of the columns and the mark at the other
column. Because this means you cannot put point or the mark at the
beginning of the first line to sort, this command uses an unusual
-definition of `region': all of the line point is in is considered part of
+definition of ‘region’: all of the line point is in is considered
part of
the region, and so is all of the line the mark is in.
</p>
<p> For example, to sort a table by information found in columns 10 to 15,
@@ -3385,8 +3385,8 @@
<a name="IDX1397"></a>
<a name="IDX1398"></a>
<p> <code>cd</code>, <code>pushd</code>, and <code>popd</code> commands given
to the inferior
-shell are watched by XEmacs so it can keep the
‘<samp>*shell*</samp>’ buffer's
-default directory the same as the shell's working directory. These
+shell are watched by XEmacs so it can keep the
‘<samp>*shell*</samp>’ buffer’s
+default directory the same as the shell’s working directory. These
commands are recognized syntactically by examining lines of input that are
sent. If you use aliases for these commands, you can tell XEmacs to
recognize them also. For example, if the value of the variable
@@ -3396,7 +3396,7 @@
<code>shell-cd-regexp</code> are used to recognize commands with the meaning of
‘<samp>popd</samp>’ and ‘<samp>cd</samp>’.
</p>
-<p><kbd>M-x shell-resync-dirs</kbd> queries the shell and resynchronizes
XEmacs'
+<p><kbd>M-x shell-resync-dirs</kbd> queries the shell and resynchronizes
XEmacs’
idea of what the current directory stack is. <kbd>M-x
shell-dirtrack-toggle</kbd> turns directory tracking on and off.
</p>
@@ -3476,7 +3476,7 @@
<dd><p>At end of buffer send line as input; otherwise, copy current line to
end of
buffer and send it (<code>send-shell-input</code>). When a line is copied, any
text at the beginning of the line that matches the variable
-<code>shell-prompt-pattern</code> is left out; this variable's value should be
a
+<code>shell-prompt-pattern</code> is left out; this variable’s value
should be a
regexp string that matches the prompts that you use in your subshell.
</p></dd>
<dt> <kbd>C-c C-d</kbd></dt>
@@ -3573,7 +3573,7 @@
codes needed vary from terminal to terminal, but nowadays
most terminals and terminal emulators (including xterm)
understand the so-called "ANSI escape sequences" (first
-popularized by the Digital's VT100 family of terminal).
+popularized by the Digital’s VT100 family of terminal).
The term mode also understands these escape sequences,
and for each control code does the appropriate thing
to change the buffer so that the appearance of the window
@@ -3720,7 +3720,7 @@
the rest temporarily invisible and inaccessible. Cancelling the narrowing
and making the entire buffer once again visible is called <em>widening</em>.
The amount of narrowing in effect in a buffer at any time is called the
-buffer's <em>restriction</em>.
+buffer’s <em>restriction</em>.
</p>
<dl compact="compact">
<dt> <kbd>C-x n n</kbd></dt>
@@ -3736,15 +3736,15 @@
restrict the range of operation of a replace command or repeating
keyboard macro. The word ‘<samp>Narrow</samp>’ appears in the
mode line
whenever narrowing is in effect. When you have narrowed to a part of the
-buffer, that part appears to be all there is. You can't see the rest,
-can't move into it (motion commands won't go outside the visible part),
-and can't change it in any way. However, the invisible text is not
+buffer, that part appears to be all there is. You can’t see the rest,
+can’t move into it (motion commands won’t go outside the visible
part),
+and can’t change it in any way. However, the invisible text is not
gone; if you save the file, it will be saved.
</p>
<a name="IDX1432"></a>
<a name="IDX1433"></a>
<p> The primary narrowing command is <kbd>C-x n n</kbd>
(<code>narrow-to-region</code>).
-It sets the current buffer's restrictions so that the text in the current
+It sets the current buffer’s restrictions so that the text in the current
region remains visible but all text before the region or after the region
is invisible. Point and mark do not change.
</p>
@@ -3858,7 +3858,7 @@
</p>
<p> The mode line shows you when you are in a recursive edit by displaying
square brackets around the parentheses that always surround the major
-and minor mode names. Every window's mode line shows the square
+and minor mode names. Every window’s mode line shows the square
brackets, since XEmacs as a whole, rather than any particular buffer, is
in a recursive edit.
</p>
@@ -3932,9 +3932,9 @@
buffer to another. In order to produce plausible output rather than
gibberish, it insists on a certain amount of overlap between the end of one
run of consecutive words or characters and the start of the next. That is,
-if it has just printed out `president' and then decides to jump to a
-different point in the file, it might spot the `ent' in `pentagon' and
-continue from there, producing `presidentagon'. Long sample texts produce
+if it has just printed out ‘president’ and then decides to jump to
a
+different point in the file, it might spot the ‘ent’ in
‘pentagon’ and
+continue from there, producing ‘presidentagon’. Long sample texts
produce
the best results.
</p>
<a name="IDX1448"></a>
Index: Tests/xemacs_res/xemacs_3.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/xemacs_res/xemacs_3.html,v
retrieving revision 1.22
retrieving revision 1.23
diff -u -b -r1.22 -r1.23
--- Tests/xemacs_res/xemacs_3.html 5 Feb 2007 15:30:27 -0000 1.22
+++ Tests/xemacs_res/xemacs_3.html 3 Oct 2007 09:34:57 -0000 1.23
@@ -102,7 +102,7 @@
</p>
<p> <em>Extensible</em> means you can go beyond simple customization and
write entirely new commands, programs in the Lisp language to be run by
-XEmacs's own Lisp interpreter. XEmacs is an “on-line extensible”
+XEmacs’s own Lisp interpreter. XEmacs is an “on-line
extensible”
system: it is divided into many functions that call each other. You can
redefine any function in the middle of an editing session and replace
any part of XEmacs without making a separate copy of all of XEmacs. Most
Index: Tests/xemacs_res/xemacs_30.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/xemacs_res/xemacs_30.html,v
retrieving revision 1.34
retrieving revision 1.35
diff -u -b -r1.34 -r1.35
--- Tests/xemacs_res/xemacs_30.html 5 Feb 2007 15:30:27 -0000 1.34
+++ Tests/xemacs_res/xemacs_30.html 3 Oct 2007 09:34:57 -0000 1.35
@@ -69,7 +69,7 @@
have no effect on other Emacs jobs you may run at the same time or
later. The only way an Emacs job can affect anything outside of it is
by writing a file; in particular, the only way to make a customization
-`permanent' is to put something in your init file or other appropriate
+‘permanent’ is to put something in your init file or other
appropriate
file to do the customization in each session. See section <a
href="#SEC377">The Init File</a>.
</p>
<table class="menu" border="0" cellspacing="0">
@@ -190,7 +190,7 @@
that Emacs uses require a value of a certain type. Often the value has
to be a string or a number. Sometimes we say that a certain feature is
turned on if a variable is “non-<code>nil</code>,” meaning that if
the
-variable's value is <code>nil</code>, the feature is off, but the feature is
+variable’s value is <code>nil</code>, the feature is off, but the
feature is
on for <i>any</i> other value. The conventional value to turn on the
feature—since you have to pick one particular value when you set the
variable—is <code>t</code>.
@@ -208,11 +208,11 @@
the left margin) to be used by the fill commands (see section <a
href="xemacs_23.html#SEC210">Filling Text</a>).
</p>
<table class="menu" border="0" cellspacing="0">
-<tr><td align="left" valign="top"><a href="#SEC354">27.2.1 Examining and
Setting Variables</a></td><td> </td><td align="left" valign="top">
Examining or setting one variable's value.
+<tr><td align="left" valign="top"><a href="#SEC354">27.2.1 Examining and
Setting Variables</a></td><td> </td><td align="left" valign="top">
Examining or setting one variable’s value.
</td></tr>
<tr><td align="left" valign="top"><a href="#SEC355">27.2.2 Easy Customization
Interface</a></td><td> </td><td align="left" valign="top">
Convenient and easy customization of variables.
</td></tr>
-<tr><td align="left" valign="top"><a href="#SEC360">27.2.3 Editing Variable
Values</a></td><td> </td><td align="left" valign="top">
Examining or editing list of all variables' values.
+<tr><td align="left" valign="top"><a href="#SEC360">27.2.3 Editing Variable
Values</a></td><td> </td><td align="left" valign="top">
Examining or editing list of all variables’ values.
</td></tr>
<tr><td align="left" valign="top"><a href="#SEC361">27.2.4 Local
Variables</a></td><td> </td><td align="left" valign="top">
Per-buffer values of variables.
</td></tr>
@@ -464,7 +464,7 @@
customizing the variable.
</p>
<p> The line after the ‘<samp>[State]</samp>’ line displays the
beginning of the
-option's documentation string. If there are more lines of
+option’s documentation string. If there are more lines of
documentation, this line ends with ‘<samp>[More]</samp>’; invoke
this to show
the full documentation string.
</p>
@@ -488,7 +488,7 @@
<table><tr><td> </td><td><pre class="smallexample">[State]: you have set
this option, but not saved it for future sessions.
</pre></td></tr></table>
-<p> You don't have to worry about specifying a value that is not valid;
+<p> You don’t have to worry about specifying a value that is not valid;
setting the option checks for validity and will not really install an
unacceptable value.
</p>
@@ -499,7 +499,7 @@
type <kbd>M-<TAB></kbd> (<code>widget-complete</code>) to do completion.
</p>
<p> Some options have a small fixed set of possible legitimate values.
-These options don't let you edit the value textually. Instead, an
+These options don’t let you edit the value textually. Instead, an
active field ‘<samp>[Value Menu]</samp>’ appears before the value;
invoke this
field to edit the value. For a boolean “on or off” value, the
active
field says ‘<samp>[Toggle]</samp>’, and it changes to the other
value.
@@ -723,7 +723,7 @@
<p> You can also set up the customization buffer with a specific group,
using <kbd>M-x customize-group</kbd>. The immediate contents of the chosen
group, including option variables, faces, and other groups, all appear
-as well. However, these subgroups' own contents start out hidden. You
+as well. However, these subgroups’ own contents start out hidden. You
can show their contents in the usual way, by invoking
‘<samp>[Show]</samp>’.
</p>
<a name="IDX1491"></a>
@@ -854,7 +854,7 @@
<a name="IDX1496"></a>
<p> You can make any variable <em>local</em> to a specific Emacs buffer.
-This means that the variable's value in that buffer is independent of
+This means that the variable’s value in that buffer is independent of
its value in other buffers. A few variables are always local in every
buffer. All other Emacs variables have a <em>global</em> value which is in
effect in all buffers that have not made the variable local.
@@ -913,7 +913,7 @@
that has been marked with <code>make-variable-buffer-local</code>.
</p>
<a name="IDX1502"></a>
-<p> Programs can look at a variable's default value with
<code>default-value</code>.
+<p> Programs can look at a variable’s default value with
<code>default-value</code>.
This function takes a symbol as an argument and returns its default value.
The argument is evaluated; usually you must quote it explicitly, as in
the case of:
@@ -1002,7 +1002,7 @@
a matter of personal taste, not a matter of the contents of particular
files. If you want to use Auto Fill, set up major mode hooks with your
init file to turn it on (when appropriate) for you alone
-(see section <a href="#SEC377">The Init File</a>). Don't try to use a local
variable list that would
+(see section <a href="#SEC377">The Init File</a>). Don’t try to use a
local variable list that would
impose your taste on everyone working with the file.
</p>
<p>XEmacs allows you to specify local variables in the first line
@@ -1082,7 +1082,7 @@
recently defined keyboard macro.
</p></dd>
<dt> <kbd>M-x insert-kbd-macro</kbd></dt>
-<dd><p>Insert in the buffer a keyboard macro's definition, as Lisp code.
+<dd><p>Insert in the buffer a keyboard macro’s definition, as Lisp code.
</p></dd>
</dl>
@@ -1096,7 +1096,7 @@
<p> You define a keyboard macro by executing the commands which are its
definition. Put differently, as you are defining a keyboard macro, the
definition is being executed for the first time. This way, you see
-what the effects of your commands are, and don't have to figure
+what the effects of your commands are, and don’t have to figure
them out in your head. When you are finished, the keyboard macro is
defined and also has been executed once. You can then execute the same
set of commands again by invoking the macro.
@@ -1306,9 +1306,9 @@
</p>
<table class="menu" border="0" cellspacing="0">
<tr><td align="left" valign="top"><a href="#SEC368">27.4.1
Keymaps</a></td><td> </td><td align="left" valign="top">
Definition of the keymap data structure.
- Names of Emacs's standard keymaps.
+ Names of Emacs’s standard keymaps.
</td></tr>
-<tr><td align="left" valign="top"><a href="#SEC369">27.4.2 Changing Key
Bindings</a></td><td> </td><td align="left" valign="top"> How to
redefine one key's meaning conveniently.
+<tr><td align="left" valign="top"><a href="#SEC369">27.4.2 Changing Key
Bindings</a></td><td> </td><td align="left" valign="top"> How to
redefine one key’s meaning conveniently.
</td></tr>
<tr><td align="left" valign="top"><a href="#SEC373">27.4.3 Disabling
Commands</a></td><td> </td><td align="left" valign="top"> Disabling
a command means confirmation is required
before it can be executed. This is done to protect
@@ -1349,7 +1349,7 @@
<p> Each major mode has another keymap, its <em>local keymap</em>, which
contains overriding definitions for the single-character keys that are
redefined in that mode. Each buffer records which local keymap is
-installed for it at any time, and the current buffer's local keymap is
+installed for it at any time, and the current buffer’s local keymap is
the only one that directly affects command execution. The local keymaps
for Lisp mode, C mode, and many other major modes always exist even when
not in use. They are the values of the variables <code>lisp-mode-map</code>,
@@ -1430,8 +1430,8 @@
one. When both the global and local definitions of a key are other
keymaps, the next character is looked up in both keymaps, with the local
definition overriding the global one. The character after the
-<kbd>C-x</kbd> is looked up in both the major mode's own keymap for redefined
-<kbd>C-x</kbd> commands and in <code>ctl-x-map</code>. If the major mode's
own keymap
+<kbd>C-x</kbd> is looked up in both the major mode’s own keymap for
redefined
+<kbd>C-x</kbd> commands and in <code>ctl-x-map</code>. If the major
mode’s own keymap
for <kbd>C-x</kbd> commands contains <code>nil</code>, the definition from the
global
keymap for <kbd>C-x</kbd> commands is used.
</p>
@@ -1459,7 +1459,7 @@
<p> You can redefine an Emacs key by changing its entry in a keymap.
You can change the global keymap, in which case the change is effective in
all major modes except those that have their own overriding local
-definitions for the same key. Or you can change the current buffer's
+definitions for the same key. Or you can change the current buffer’s
local map, which affects all buffers using the same major mode.
</p>
<table class="menu" border="0" cellspacing="0">
@@ -1508,7 +1508,7 @@
that you type. When called as a function, <var>key</var> is a string, a
vector of events, or a vector of key-description lists as described in
the <code>define-key</code> function description. The binding goes in
-the current buffer's local map, which is shared with other buffers in
+the current buffer’s local map, which is shared with other buffers in
the same major mode.
</p>
<p>The following example:
@@ -1585,7 +1585,7 @@
</p>
<p><var>keys</var> is the sequence of keystrokes to bind.
</p>
-<p><var>def</var> is anything that can be a key's definition:
+<p><var>def</var> is anything that can be a key’s definition:
</p>
<ul>
<li>
@@ -1748,7 +1748,7 @@
</p>
<p> The direct mechanism for disabling a command is to have a
non-<code>nil</code>
<code>disabled</code> property on the Lisp symbol for the command. These
-properties are normally set by the user's init file with
+properties are normally set by the user’s init file with
Lisp expressions such as:
</p>
<table><tr><td> </td><td><pre class="example">(put 'delete-region
'disabled t)
@@ -1770,7 +1770,7 @@
init file for you. See section <a href="#SEC377">The Init File</a>.
</p>
<p> When you attempt to invoke a disabled command interactively in Emacs,
-a window is displayed containing the command's name, its
+a window is displayed containing the command’s name, its
documentation, and some instructions on what to do next; then
Emacs asks for input saying whether to execute the command as requested,
enable it and execute, or cancel it. If you decide to enable the
@@ -1873,7 +1873,7 @@
</p>
<dl compact="compact">
<dt> ‘<samp>-</samp>’</dt>
-<dd><p>The class of whitespace characters. Please don't use the formerly
+<dd><p>The class of whitespace characters. Please don’t use the formerly
advertised , which is not supported by GNU Emacs.
</p></dd>
<dt> ‘<samp>w</samp>’</dt>
@@ -1908,7 +1908,7 @@
string.
</p></dd>
<dt> ‘<samp>$</samp>’</dt>
-<dd><p>The class of self-matching delimiters. This is intended for TeX's
+<dd><p>The class of self-matching delimiters. This is intended for TeX’s
‘<samp>$</samp>’, which is used both to enter and leave math mode.
Thus,
a pair of matching ‘<samp>$</samp>’ characters surround each piece
of math mode
TeX input. A pair of adjacent ‘<samp>$</samp>’ characters act
like a single
@@ -1972,21 +1972,21 @@
</tr></table>
<h3 class="subsection"> 27.5.2 Altering Syntax Information </h3>
-<p> It is possible to alter a character's syntax table entry by storing a new
+<p> It is possible to alter a character’s syntax table entry by storing
a new
number in the appropriate element of the syntax table, but it would be hard
to determine what number to use. Emacs therefore provides a command that
allows you to specify the syntactic properties of a character in a
convenient way.
</p>
<a name="IDX1529"></a>
-<p> <kbd>M-x modify-syntax-entry</kbd> is the command to change a character's
+<p> <kbd>M-x modify-syntax-entry</kbd> is the command to change a
character’s
syntax. It can be used interactively and is also used by major
modes to initialize their own syntax tables. Its first argument is the
character to change. The second argument is a string that specifies the
new syntax. When called from Lisp code, there is a third, optional
argument, which specifies the syntax table in which to make the change. If
not supplied, or if this command is called interactively, the third
-argument defaults to the current buffer's syntax table.
+argument defaults to the current buffer’s syntax table.
</p>
<ol>
<li>
@@ -2022,7 +2022,7 @@
<p> Use <kbd>C-h s</kbd> (<code>describe-syntax</code>) to display a
description of
the contents of the current syntax table. The description of each
character includes both the string you have to pass to
-<code>modify-syntax-entry</code> to set up that character's current syntax,
+<code>modify-syntax-entry</code> to set up that character’s current
syntax,
and some English to explain that string if necessary.
</p>
<hr size="6">
@@ -2147,15 +2147,15 @@
</p>
</dd>
<dt> True</dt>
-<dd><p><code>t</code> stands for `true'.
+<dd><p><code>t</code> stands for ‘true’.
</p>
</dd>
<dt> False</dt>
-<dd><p><code>nil</code> stands for `false'.
+<dd><p><code>nil</code> stands for ‘false’.
</p>
</dd>
<dt> Other Lisp objects</dt>
-<dd><p>Write a single-quote (') followed by the Lisp object you want.
+<dd><p>Write a single-quote (’) followed by the Lisp object you want.
</p></dd>
</dl>
@@ -2191,8 +2191,8 @@
<table><tr><td> </td><td><pre class="example">(setq c-tab-always-indent
nil)
</pre></td></tr></table>
-<p>Here we have a variable whose value is normally <code>t</code> for `true'
-and the alternative is <code>nil</code> for `false'.
+<p>Here we have a variable whose value is normally <code>t</code> for
‘true’
+and the alternative is <code>nil</code> for ‘false’.
</p>
</li><li>
Make searches case sensitive by default (in all buffers that do not
@@ -2203,7 +2203,7 @@
<p>This sets the default value, which is effective in all buffers that do
not have local values for the variable. Setting <code>case-fold-search</code>
-with <code>setq</code> affects only the current buffer's local value, which
+with <code>setq</code> affects only the current buffer’s local value,
which
is probably not what you want to do in an init file.
</p>
</li><li>
@@ -2354,7 +2354,7 @@
kept.
</p>
<p> The usual purpose of the terminal-specific library is to define the
-escape sequences used by the terminal's function keys using the library
+escape sequences used by the terminal’s function keys using the library
‘<tt>keypad.el</tt>’. See the file
‘<tt>term/vt100.el</tt>’ for an example of how this is done.
</p>
@@ -2365,7 +2365,7 @@
<code>(getenv "TERM")</code> to find the full terminal type name.
</p>
<a name="IDX1532"></a>
-<p> The library's name is constructed by concatenating the value of the
+<p> The library’s name is constructed by concatenating the value of the
variable <code>term-file-prefix</code> and the terminal type. Your init
file can prevent the loading of the terminal-specific library by setting
<code>term-file-prefix</code> to <code>nil</code>. See section <a
href="#SEC377">The Init File</a>.
@@ -2402,7 +2402,7 @@
<p>You can now change how the audible bell sounds using the variable
<code>sound-alist</code>.
</p>
-<p><code>sound-alist</code>'s value is an list associating symbols with, among
+<p><code>sound-alist</code>’s value is an list associating symbols with,
among
other things, strings of audio-data. When <code>ding</code> is called with
one of the symbols, the associated sound data is played instead of the
standard beep. This only works if you are logged in on the console of a
@@ -2435,7 +2435,7 @@
</p></dd>
</dl>
-<p>For compatibility, elements of `sound-alist' may also be of the form:
+<p>For compatibility, elements of ‘sound-alist’ may also be of the
form:
</p>
<table><tr><td> </td><td><pre class="example">( <var>sound-name</var> .
<var><sound></var> )
( <var>sound-name</var> <var><volume></var> <var><sound></var> )
@@ -2449,7 +2449,7 @@
time means a Sun SparcStation, SGI, or HP9000s700.
</p>
<p>Also note that the pitch, duration, and volume options are available
-everywhere, but most X servers ignore the `pitch' option.
+everywhere, but most X servers ignore the ‘pitch’ option.
</p>
<a name="IDX1535"></a>
<p>The variable <code>bell-volume</code> should be an integer from 0 to 100,
@@ -2982,8 +2982,8 @@
vertical scrollbars. You can also use a resource specification of the
form <code>*scrollbar.width</code>, or the usual toolkit scrollbar resources:
<code>*XmScrollBar.width</code> (Motif), <code>*XlwScrollBar.width</code>
(Lucid),
-or <code>*Scrollbar.thickness</code> (Athena). We don't recommend that you
-use the toolkit resources, though, because they're dependent on how
+or <code>*Scrollbar.thickness</code> (Athena). We don’t recommend that
you
+use the toolkit resources, though, because they’re dependent on how
exactly your particular build of XEmacs was configured.
</p>
</dd>
@@ -2992,8 +2992,8 @@
horizontal scrollbars. You can also use a resource specification of the
form <code>*scrollbar.height</code>, or the usual toolkit scrollbar resources:
<code>*XmScrollBar.height</code> (Motif), <code>*XlwScrollBar.height</code>
(Lucid),
-or <code>*Scrollbar.thickness</code> (Athena). We don't recommend that you use
-the toolkit resources, though, because they're dependent on how exactly
+or <code>*Scrollbar.thickness</code> (Athena). We don’t recommend that
you use
+the toolkit resources, though, because they’re dependent on how exactly
your particular build of XEmacs was configured.
</p>
</dd>
@@ -3210,7 +3210,7 @@
<dt> <code>info-xref</code></dt>
<dd><p>This is the face of info cross-references. If unspecified, it is copied
from <code>bold</code>. (Note that, when the mouse passes over a
-cross-reference, the cross-reference's face is determined from a
+cross-reference, the cross-reference’s face is determined from a
combination of the <code>info-xref</code> and <code>highlight</code> faces.)
</p></dd>
</dl>
@@ -3237,7 +3237,7 @@
9x13
</pre></td></tr></table>
-<p>then XEmacs won't be able to guess the names of the bold and italic
+<p>then XEmacs won’t be able to guess the names of the bold and italic
versions. All X fonts can be referred to via XLFD-style names, so you
should use those forms. See the man pages for ‘<samp>X(1)</samp>’,
‘<samp>xlsfonts(1)</samp>’, and
‘<samp>xfontsel(1)</samp>’.
@@ -3383,7 +3383,7 @@
<a name="IDX1551"></a>
<a name="IDX1552"></a>
<p> Quitting with <kbd>C-g</kbd> is used for getting rid of a partially typed
-command or a numeric argument that you don't want. It also stops a
+command or a numeric argument that you don’t want. It also stops a
running command in the middle in a relatively safe way, so you can use
it if you accidentally start executing a command that takes a long
time. In particular, it is safe to quit out of killing; either your
@@ -3453,7 +3453,7 @@
and how to recognize them and correct them.
</p>
<table class="menu" border="0" cellspacing="0">
-<tr><td align="left" valign="top"><a href="#SEC394">27.12.1 Recursive Editing
Levels</a></td><td> </td><td align="left" valign="top"> `[...]'
in mode line around the parentheses.
+<tr><td align="left" valign="top"><a href="#SEC394">27.12.1 Recursive Editing
Levels</a></td><td> </td><td align="left" valign="top">
‘[...]’ in mode line around the parentheses.
</td></tr>
<tr><td align="left" valign="top"><a href="#SEC395">27.12.2 Garbage on the
Screen</a></td><td> </td><td align="left" valign="top"> Garbage
on the screen.
</td></tr>
@@ -3464,7 +3464,7 @@
<tr><td align="left" valign="top"><a href="#SEC398">27.12.5 Emergency
Escape</a></td><td> </td><td align="left" valign="top"> Emergency
escape—
What to do if Emacs stops responding.
</td></tr>
-<tr><td align="left" valign="top"><a href="#SEC399">27.12.6 Help for Total
Frustration</a></td><td> </td><td align="left" valign="top"> When
you are at your wits' end.
+<tr><td align="left" valign="top"><a href="#SEC399">27.12.6 Help for Total
Frustration</a></td><td> </td><td align="left" valign="top"> When
you are at your wits’ end.
</td></tr>
</table>
@@ -3495,7 +3495,7 @@
<p> If the mode line has square brackets
‘<samp>[…]</samp>’ around the parentheses
that contain the names of the major and minor modes, you have entered a
recursive editing level. If you did not do this on purpose, or if you
-don't understand what that means, you should just get out of the recursive
+don’t understand what that means, you should just get out of the
recursive
editing level. To do so, type <kbd>M-x top-level</kbd>. This is called
getting
back to top level. See section <a href="xemacs_29.html#SEC346">Recursive
Editing Levels</a>.
</p>
@@ -3751,11 +3751,11 @@
case of incorrect display updating.
</p>
<p> Taking forever to complete a command can be a bug, but you must make
-certain that it was really Emacs's fault. Some commands simply take a long
+certain that it was really Emacs’s fault. Some commands simply take a
long
time. Type <kbd>C-g</kbd> and then <kbd>C-h l</kbd> to see whether the input
Emacs
received was what you intended to type; if the input was such that you
<var>know</var> it should have been processed quickly, report a bug. If you
-don't know whether the command should take a long time, find out by looking
+don’t know whether the command should take a long time, find out by
looking
in the manual or by asking for assistance.
</p>
<p> If a command you are familiar with causes an Emacs error message in a
@@ -3763,12 +3763,12 @@
bug.
</p>
<p> If a command does the wrong thing, that is a bug. But be sure you know
-for certain what it ought to have done. If you aren't familiar with the
-command, or don't know for certain how the command is supposed to work,
+for certain what it ought to have done. If you aren’t familiar with the
+command, or don’t know for certain how the command is supposed to work,
then it might actually be working right. Rather than jumping to
conclusions, show the problem to someone who knows for certain.
</p>
-<p> Finally, a command's intended definition may not be best for editing
+<p> Finally, a command’s intended definition may not be best for editing
with. This is a very important sort of problem, but it is also a matter of
judgment. Also, it is easy to come to such a conclusion out of ignorance
of some of the existing features. It is probably best not to complain
@@ -3777,7 +3777,7 @@
you want is not available. If you are not sure what the command is
supposed to do after a careful reading of the manual, check the index and
glossary for any terms that may be unclear. If you still do not
-understand, this indicates a bug in the manual. The manual's job is to
+understand, this indicates a bug in the manual. The manual’s job is to
make everything clear. It is just as important to report documentation
bugs as program bugs.
</p>
@@ -3855,10 +3855,10 @@
backtrace, you must execute the Lisp expression
<code>(setq debug-on-error t)</code> before the error happens (that is to
say, you must execute that expression and then make the bug happen). This
-causes the Lisp debugger to run (see section <a
href="xemacs_25.html#SEC259">The Emacs-Lisp Debugger</a>). The debugger's
+causes the Lisp debugger to run (see section <a
href="xemacs_25.html#SEC259">The Emacs-Lisp Debugger</a>). The debugger’s
backtrace can be copied as text into the bug report. This use of the
debugger is possible only if you know how to make the bug happen again. Do
-note the error message the first time the bug happens, so if you can't make
+note the error message the first time the bug happens, so if you can’t
make
it happen again, you can report at least that.
</p>
<p> Check whether any programs you have loaded into the Lisp world, including
@@ -3919,7 +3919,7 @@
<p>The newsgroup ‘<samp>comp.emacs.xemacs</samp>’ may be used for
bug reports,
other discussions and requests for assistance.
</p>
-<p>If you don't have access to this newgroup, you can subscribe to the
+<p>If you don’t have access to this newgroup, you can subscribe to the
mailing list version: the newsgroup is bidirectionally gatewayed into
the mailing list ‘<samp>address@hidden</samp>’.
</p>
Index: Tests/xemacs_res/xemacs_31.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/xemacs_res/xemacs_31.html,v
retrieving revision 1.27
retrieving revision 1.28
diff -u -b -r1.27 -r1.28
--- Tests/xemacs_res/xemacs_31.html 5 Feb 2007 15:30:27 -0000 1.27
+++ Tests/xemacs_res/xemacs_31.html 3 Oct 2007 09:34:57 -0000 1.28
@@ -120,7 +120,7 @@
<dt> Buffer</dt>
<dd><p>The buffer is the basic editing unit; one buffer corresponds to one
piece of text being edited. You can have several buffers, but at any
-time you are editing only one, the `selected' buffer, though several
+time you are editing only one, the ‘selected’ buffer, though
several
buffers can be visible when you are using multiple windows. See section <a
href="xemacs_18.html#SEC169">Using Multiple Buffers</a>.
</p>
</dd>
@@ -245,8 +245,8 @@
<dd><p>The cursor is the rectangle on the screen which indicates the position
called point (q.v.) at which insertion and deletion takes place.
The cursor is on or under the character that follows point. Often
-people speak of `the cursor' when, strictly speaking, they mean
-`point'. See section <a href="xemacs_7.html#SEC49">Basic Editing</a>.
+people speak of ‘the cursor’ when, strictly speaking, they mean
+‘point’. See section <a href="xemacs_7.html#SEC49">Basic
Editing</a>.
</p>
</dd>
<dt> Customization</dt>
@@ -264,7 +264,7 @@
</dd>
<dt> Default Directory</dt>
<dd><p>When you specify a file name that does not start with
‘<samp>/</samp>’ or ‘<samp>~</samp>’,
-it is interpreted relative to the current buffer's default directory.
+it is interpreted relative to the current buffer’s default directory.
See section <a href="xemacs_9.html#SEC61">Default Directory</a>.
</p>
</dd>
@@ -380,7 +380,7 @@
</p>
</dd>
<dt> Frame</dt>
-<dd><p>When running Emacs on a TTY terminal, “frame” means the
terminal's
+<dd><p>When running Emacs on a TTY terminal, “frame” means the
terminal’s
screen. When running Emacs under X, you can have multiple frames,
each corresponding to a top-level X window and each looking like
the screen on a TTY. Each frame contains one or more non-overlapping
@@ -389,9 +389,9 @@
</p>
</dd>
<dt> Global</dt>
-<dd><p>Global means `independent of the current environment; in effect
-<br>throughout Emacs'. It is the opposite of local (q.v.).
-Examples of the use of `global' appear below.
+<dd><p>Global means ‘independent of the current environment; in effect
+<br>throughout Emacs’. It is the opposite of local (q.v.).
+Examples of the use of ‘global’ appear below.
</p>
</dd>
<dt> Global Abbrev</dt>
@@ -402,7 +402,7 @@
</dd>
<dt> Global Keymap</dt>
<dd><p>The global keymap (q.v.) contains key bindings that are in effect
-unless local key bindings in a major mode's local
+unless local key bindings in a major mode’s local
keymap (q.v.) override them.See section <a
href="xemacs_30.html#SEC368">Keymaps</a>.
</p>
</dd>
@@ -516,10 +516,10 @@
</p>
</dd>
<dt> Local</dt>
-<dd><p>Local means `in effect only in a particular context'; the relevant
+<dd><p>Local means ‘in effect only in a particular context’; the
relevant
kind of context is a particular function execution, a particular
-buffer, or a particular major mode. Local is the opposite of `global'
-(q.v.). Specific uses of `local' in Emacs terminology appear below.
+buffer, or a particular major mode. Local is the opposite of
‘global’
+(q.v.). Specific uses of ‘local’ in Emacs terminology appear
below.
</p>
</dd>
<dt> Local Abbrev</dt>
@@ -561,7 +561,7 @@
</dd>
<dt> Mail</dt>
<dd><p>Mail means messages sent from one user to another through the computer
-system, to be read at the recipient's convenience. Emacs has commands for
+system, to be read at the recipient’s convenience. Emacs has commands
for
composing and sending mail, and for reading and editing the mail you have
received. See section <a href="xemacs_28.html#SEC296">Sending Mail</a>.
</p>
@@ -585,7 +585,7 @@
</p>
</dd>
<dt> Message</dt>
-<dd><p>See `mail'.
+<dd><p>See ‘mail’.
</p>
</dd>
<dt> Meta</dt>
@@ -690,7 +690,7 @@
<dt> Point</dt>
<dd><p>Point is the place in the buffer at which insertion and deletion
occur. Point is considered to be between two characters, not at one
-character. The terminal's cursor (q.v.) indicates the location of
+character. The terminal’s cursor (q.v.) indicates the location of
point. See section <a href="xemacs_7.html#SEC49">Point</a>.
</p>
</dd>
@@ -749,7 +749,7 @@
</p>
</dd>
<dt> Regexp</dt>
-<dd><p>See `regular expression'.
+<dd><p>See ‘regular expression’.
</p>
</dd>
<dt> Region</dt>
@@ -769,11 +769,11 @@
</p>
</dd>
<dt> Replacement</dt>
-<dd><p>See `global substitution'.
+<dd><p>See ‘global substitution’.
</p>
</dd>
<dt> Restriction</dt>
-<dd><p>A buffer's restriction is the amount of text, at the beginning or the
+<dd><p>A buffer’s restriction is the amount of text, at the beginning or
the
end of the buffer, that is temporarily invisible and inaccessible.
Giving a buffer a nonzero amount of restriction is called narrowing
(q.v.). See section <a href="xemacs_29.html#SEC344">Narrowing</a>.
@@ -819,10 +819,10 @@
</p>
</dd>
<dt> Sexp</dt>
-<dd><p>An sexp (short for `s-expression,' itself short for `symbolic
-expression') is the basic syntactic unit of Lisp
+<dd><p>An sexp (short for ‘s-expression,’ itself short for
‘symbolic
+expression’) is the basic syntactic unit of Lisp
in its textual form: either a list, or Lisp atom. Many Emacs commands
-operate on sexps. The term `sexp' is generalized to languages other
+operate on sexps. The term ‘sexp’ is generalized to languages
other
than Lisp to mean a syntactically recognizable expression.
See section <a href="xemacs_24.html#SEC217">Sexps</a>.
</p>
@@ -847,7 +847,7 @@
</p>
</dd>
<dt> String Substitution</dt>
-<dd><p>See `global substitution'.
+<dd><p>See ‘global substitution’.
</p>
</dd>
<dt> Syntax Table</dt>
@@ -901,7 +901,7 @@
<dt> Truncation</dt>
<dd><p>Truncating text lines in the display means leaving out any text on a
line that does not fit within the right margin of the window
-displaying it. See also `continuation line'.
+displaying it. See also ‘continuation line’.
See section <a href="xemacs_7.html#SEC49">Basic Editing</a>.
</p>
</dd>
@@ -913,7 +913,7 @@
</dd>
<dt> Variable</dt>
<dd><p>A variable is Lisp object that can store an arbitrary value. Emacs uses
-some variables for internal purposes, and has others (known as `options'
+some variables for internal purposes, and has others (known as
‘options’
(q.v.)) you can set to control the behavior of Emacs. The variables
used in Emacs that you are likely to be interested in are listed in the
Variables Index of this manual. See section <a
href="xemacs_30.html#SEC353">Variables</a>, for information on
@@ -946,7 +946,7 @@
</p>
</dd>
<dt> Word Abbrev</dt>
-<dd><p>Synonymous with `abbrev'.
+<dd><p>Synonymous with ‘abbrev’.
</p>
</dd>
<dt> Word Search</dt>
Index: Tests/xemacs_res/xemacs_32.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/xemacs_res/xemacs_32.html,v
retrieving revision 1.24
retrieving revision 1.25
diff -u -b -r1.24 -r1.25
--- Tests/xemacs_res/xemacs_32.html 5 Feb 2007 15:30:27 -0000 1.24
+++ Tests/xemacs_res/xemacs_32.html 3 Oct 2007 09:34:57 -0000 1.25
@@ -79,9 +79,9 @@
<td valign="middle" align="left">[<a href="xemacs_33.html#SEC413"
title="Index">Index</a>]</td>
<td valign="middle" align="left">[<a href="xemacs_abt.html#SEC_About"
title="About (help)"> ? </a>]</td>
</tr></table>
-<h2 class="unnumberedsec"> What's GNU? GNU's Not Unix! </h2>
+<h2 class="unnumberedsec"> What’s GNU? GNU’s Not Unix! </h2>
-<p>GNU, which stands for GNU's Not Unix, is the name for the complete
+<p>GNU, which stands for GNU’s Not Unix, is the name for the complete
Unix-compatible software system which I am writing so that I can give it
away free to everyone who can use it. Several other volunteers are helping
me. Contributions of time, money, programs, and equipment are greatly
@@ -115,7 +115,7 @@
effort to make it run on smaller machines will be left to someone who wants
to use it on them.
</p>
-<p>To avoid horrible confusion, please pronounce the `G' in the word `GNU'
+<p>To avoid horrible confusion, please pronounce the ‘G’ in the
word ‘GNU’
when it is the name of this project.
</p>
@@ -266,7 +266,7 @@
<h2 class="unnumberedsec"> How You Can Contribute </h2>
<p>I am asking computer manufacturers for donations of machines and money.
-I'm asking individuals for donations of programs and work.
+I’m asking individuals for donations of programs and work.
</p>
<p>One consequence you can expect if you donate machines is that GNU will run
on them at an early date. The machines should be complete, ready-to-use
@@ -287,7 +287,7 @@
communication and will be worked on by a small, tight group.)
</p>
<p>If I get donations of money, I may be able to hire a few people full or
-part time. The salary won't be high by programmers' standards, but I'm
+part time. The salary won’t be high by programmers’ standards,
but I’m
looking for people for whom building community spirit is as important as
making money. I view this as a way of enabling dedicated people to devote
their full energies to working on GNU by sparing them the need to make a
@@ -328,7 +328,7 @@
sources and is in sole position to make changes.
</p>
<p>Schools will be able to provide a much more educational environment by
-encouraging all students to study and improve the system code. Harvard's
+encouraging all students to study and improve the system code. Harvard’s
computer lab used to have the policy that no program could be installed on
the system if its sources were not on public display, and upheld it by
actually refusing to install certain programs. I was very much inspired by
@@ -345,7 +345,7 @@
cost: charging each breather per liter of air may be fair, but wearing the
metered gas mask all day and all night is intolerable even if everyone can
afford to pay the air bill. And the TV cameras everywhere to see if you
-ever take the mask off are outrageous. It's better to support the air
+ever take the mask off are outrageous. It’s better to support the air
plant with a head tax and chuck the masks.
</p>
<p>Copying all or parts of a program is as natural to a programmer as
@@ -369,9 +369,9 @@
<td valign="middle" align="left">[<a href="xemacs_33.html#SEC413"
title="Index">Index</a>]</td>
<td valign="middle" align="left">[<a href="xemacs_abt.html#SEC_About"
title="About (help)"> ? </a>]</td>
</tr></table>
-<h2 class="unnumberedsec"> Some Easily Rebutted Objections to GNU's Goals </h2>
+<h2 class="unnumberedsec"> Some Easily Rebutted Objections to GNU’s
Goals </h2>
-<blockquote><p>“Nobody will use it if it is free, because that means
they can't rely
+<blockquote><p>“Nobody will use it if it is free, because that means
they can’t rely
on any support.”
</p>
<p>“You have to charge for the program to pay for providing the
@@ -393,11 +393,11 @@
With Unix, the price of sources puts this out of consideration for most
businesses. With GNU this will be easy. It is still possible for there to
be no available competent person, but this problem cannot be blamed on
-distribution arrangements. GNU does not eliminate all the world's problems,
+distribution arrangements. GNU does not eliminate all the world’s
problems,
only some of them.
</p>
<p>Meanwhile, the users who know nothing about computers need handholding:
-doing things for them which they could easily do themselves but don't know
+doing things for them which they could easily do themselves but don’t
know
how.
</p>
<p>Such services could be provided by companies that sell just hand-holding
@@ -405,13 +405,13 @@
get a product with service, they will also be willing to buy the service
having got the product free. The service companies will compete in quality
and price; users will not be tied to any particular one. Meanwhile, those
-of us who don't need the service should be able to use the program without
+of us who don’t need the service should be able to use the program
without
paying for the service.
</p>
<blockquote><p>“You cannot reach many people without advertising,
and you must charge for the program to support that.”
</p>
-<p>“It's no use advertising a program people can get free.”
+<p>“It’s no use advertising a program people can get free.”
</p></blockquote>
<p>There are various forms of free or very cheap publicity that can be used to
@@ -423,8 +423,8 @@
advertising pay for it.
</p>
<p>On the other hand, if many people get GNU from their friends, and such
-companies don't succeed, this will show that advertising was not really
-necessary to spread GNU. Why is it that free market advocates don't want
+companies don’t succeed, this will show that advertising was not really
+necessary to spread GNU. Why is it that free market advocates don’t want
to let the free market decide this?
</p><blockquote><p>“My company needs a proprietary operating system
@@ -435,14 +435,14 @@
You will not be able to get an edge in this area, but neither will your
competitors be able to get an edge over you. You and they will compete in
other areas, while benefitting mutually in this one. If your business is
-selling an operating system, you will not like GNU, but that's tough on
+selling an operating system, you will not like GNU, but that’s tough on
you. If your business is something else, GNU can save you from being
pushed into the expensive business of selling operating systems.
</p>
<p>I would like to see GNU development supported by gifts from many
manufacturers and users, reducing the cost to each.
</p>
-<blockquote><p>“Don't programmers deserve a reward for their
creativity?”
+<blockquote><p>“Don’t programmers deserve a reward for their
creativity?”
</p></blockquote>
<p>If anything deserves a reward, it is social contribution. Creativity can
@@ -451,11 +451,11 @@
programs, by the same token they deserve to be punished if they restrict
the use of these programs.
</p>
-<blockquote><p>“Shouldn't a programmer be able to ask for a reward for
his creativity?”
+<blockquote><p>“Shouldn’t a programmer be able to ask for a reward
for his creativity?”
</p></blockquote>
<p>There is nothing wrong with wanting pay for work, or seeking to maximize
-one's income, as long as one does not use means that are destructive. But
+one’s income, as long as one does not use means that are destructive.
But
the means customary in the field of software today are based on
destruction.
</p>
@@ -470,10 +470,10 @@
mutual destructiveness. This is Kantian ethics; or, the Golden Rule.
Since I do not like the consequences that result if everyone hoards
information, I am required to consider it wrong for one to do so.
-Specifically, the desire to be rewarded for one's creativity does not
+Specifically, the desire to be rewarded for one’s creativity does not
justify depriving the world in general of all or part of that creativity.
</p>
-<blockquote><p>“Won't programmers starve?”
+<blockquote><p>“Won’t programmers starve?”
</p></blockquote>
<p>I could answer that nobody is forced to be a programmer. Most of us cannot
@@ -481,7 +481,7 @@
we are not, as a result, condemned to spend our lives standing on the
street making faces, and starving. We do something else.
</p>
-<p>But that is the wrong answer because it accepts the questioner's implicit
+<p>But that is the wrong answer because it accepts the questioner’s
implicit
assumption: that without ownership of software, programmers cannot possibly
be paid a cent. Supposedly it is all or nothing.
</p>
@@ -501,11 +501,11 @@
programmers made the same, that would not be an injustice either. (In
practice they would still make considerably more than that.)
</p>
-<blockquote><p>“Don't people have a right to control how their
creativity is used?”
+<blockquote><p>“Don’t people have a right to control how their
creativity is used?”
</p></blockquote>
-<p>“Control over the use of one's ideas” really constitutes
control over
-other people's lives; and it is usually used to make their lives more
+<p>“Control over the use of one’s ideas” really constitutes
control over
+other people’s lives; and it is usually used to make their lives more
difficult.
</p>
<p>People who have studied the issue of intellectual property rights carefully
@@ -525,7 +525,7 @@
</p>
<p>The idea of copyright did not exist in ancient times, when authors
frequently copied other authors at length in works of non-fiction. This
-practice was useful, and is the only way many authors' works have survived
+practice was useful, and is the only way many authors’ works have
survived
even in part. The copyright system was created expressly for the purpose
of encouraging authorship. In the domain for which it was
invented—books, which could be copied economically only on a printing
@@ -559,12 +559,12 @@
all finish late.
</p>
<p>Proprietary and secret software is the moral equivalent of runners in a
-fist fight. Sad to say, the only referee we've got does not seem to
+fist fight. Sad to say, the only referee we’ve got does not seem to
object to fights; he just regulates them (“For every ten yards you run,
you can fire one shot”). He really ought to break them up, and penalize
runners for even trying to fight.
</p>
-<blockquote><p>“Won't everyone stop programming without a monetary
incentive?”
+<blockquote><p>“Won’t everyone stop programming without a monetary
incentive?”
</p></blockquote>
<p>Actually, many people will program with absolutely no monetary incentive.
@@ -577,7 +577,7 @@
the right question is, will anyone program with a reduced monetary
incentive? My experience shows that they will.
</p>
-<p>For more than ten years, many of the world's best programmers worked at the
+<p>For more than ten years, many of the world’s best programmers worked
at the
Artificial Intelligence Lab for far less money than they could have had
anywhere else. They got many kinds of non-monetary rewards: fame and
appreciation, for example. And creativity is also fun, a reward in itself.
@@ -595,7 +595,7 @@
stop helping our neighbors, we have to obey.”
</p></blockquote>
-<p>You're never so desperate that you have to obey this sort of demand.
+<p>You’re never so desperate that you have to obey this sort of demand.
Remember: millions for defense, but not a cent for tribute!
</p>
<blockquote><p>“Programmers need to make a living somehow.”
@@ -617,9 +617,9 @@
donations from satisfied users or sell hand-holding services. I have
met people who are already working this way successfully.
</p>
-<p>Users with related needs can form users' groups and pay dues. A group
+<p>Users with related needs can form users’ groups and pay dues. A group
would contract with programming companies to write programs that the
-group's members would like to use.
+group’s members would like to use.
</p>
<p>All sorts of development can be funded with a Software Tax:
</p>
Index: Tests/xemacs_res/xemacs_4.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/xemacs_res/xemacs_4.html,v
retrieving revision 1.30
retrieving revision 1.31
diff -u -b -r1.30 -r1.31
--- Tests/xemacs_res/xemacs_4.html 5 Feb 2007 15:30:27 -0000 1.30
+++ Tests/xemacs_res/xemacs_4.html 3 Oct 2007 09:34:57 -0000 1.31
@@ -90,7 +90,7 @@
consist of one window or of two or more windows if you need to look at two
buffers a the same time.
</li><li>
-Below each text window's last line is a <em>mode line</em> (see section <a
href="#SEC10">The Mode Line</a>), which describes what is going on in that
window. The mode line
+Below each text window’s last line is a <em>mode line</em> (see section
<a href="#SEC10">The Mode Line</a>), which describes what is going on in that
window. The mode line
is in inverse video if the terminal supports that. If there are several
XEmacs windows in one frame, each window has its own mode line.
</li><li>
@@ -203,9 +203,9 @@
the same buffer appears in more than one window, point can be moved in
each window independently.
</p>
-<p> The term `point' comes from the character ‘<samp>.</samp>’,
which was the
+<p> The term ‘point’ comes from the character
‘<samp>.</samp>’, which was the
command in TECO (the language in which the original Emacs was written)
-for accessing the value now called `point'.
+for accessing the value now called ‘point’.
</p>
<hr size="6">
<a name="Echo-Area"></a>
@@ -288,7 +288,7 @@
</tr></table>
<h2 class="section"> 1.3 The Mode Line </h2>
-<p> Each text window's last line is a <em>mode line</em> which describes what
is
+<p> Each text window’s last line is a <em>mode line</em> which
describes what is
going on in that window. When there is only one text window, the mode line
appears right above the echo area. The mode line is in inverse video if
the terminal supports that, starts and ends with dashes, and contains text
@@ -305,7 +305,7 @@
</pre></td></tr></table>
<p>This gives information about the buffer being displayed in the window: the
-buffer's name, what major and minor modes are in use, whether the buffer's
+buffer’s name, what major and minor modes are in use, whether the
buffer’s
text has been changed, and how far down the buffer you are currently
looking.
</p>
@@ -314,9 +314,9 @@
buffer has not been edited. Exception: for a read-only buffer, it is
‘<samp>%%</samp>’.
</p>
-<p> <var>buf</var> is the name of the window's chosen <em>buffer</em>. The
chosen
+<p> <var>buf</var> is the name of the window’s chosen <em>buffer</em>.
The chosen
buffer in the selected window (the window that the cursor is in) is also
-XEmacs's selected buffer, the buffer in which editing takes place. When
+XEmacs’s selected buffer, the buffer in which editing takes place. When
we speak of what some command does to “the buffer”, we mean the
currently selected buffer. See section <a href="xemacs_18.html#SEC169">Using
Multiple Buffers</a>.
</p>
@@ -335,7 +335,7 @@
on how the modes differ and how you select one.
</p>
<p> <var>minor</var> is a list of some of the <em>minor modes</em> that are
turned on
-in the window's chosen buffer. For example, ‘<samp>Fill</samp>’
means that Auto
+in the window’s chosen buffer. For example,
‘<samp>Fill</samp>’ means that Auto
Fill mode is on. <code>Abbrev</code> means that Word Abbrev mode is on.
<code>Ovwrt</code> means that Overwrite mode is on. See section <a
href="xemacs_30.html#SEC352">Minor Modes</a>, for more
information. ‘<samp>Narrow</samp>’ means that the buffer being
displayed has
@@ -425,7 +425,7 @@
</td></tr>
<tr><td align="left" valign="top"><a href="#SEC16">1.9 XEmacs
Gutters</a></td><td> </td><td align="left" valign="top"> How
XEmacs uses gutters.
</td></tr>
-<tr><td align="left" valign="top"><a href="#SEC17">1.10 Inhibiting Display of
GUI Components</a></td><td> </td><td align="left" valign="top">
What if you don't like GUI?
+<tr><td align="left" valign="top"><a href="#SEC17">1.10 Inhibiting Display of
GUI Components</a></td><td> </td><td align="left" valign="top">
What if you don’t like GUI?
</td></tr>
<tr><td align="left" valign="top"><a href="#SEC18">1.11 Changing the Position,
Orientation, and Appearance of GUI Components</a></td><td> </td><td
align="left" valign="top"> Position, orientation, and appearance of GUI
objects.
</td></tr>
@@ -547,7 +547,7 @@
<p>Additionally, a modeline can be dragged horizontally, in which case it
scrolls its own text. This behavior is not enabled by default because it
could be considered as disturbing when dragging vertically. When this
-behavior is enabled, the modeline's text can be dragged either in the
+behavior is enabled, the modeline’s text can be dragged either in the
same direction as the mouse, or in the opposite sense, making the
modeline act as a scrollbar for its own text.
</p>
@@ -633,7 +633,7 @@
</p>
<p>Then "uninteresting" buffers, like internal XEmacs buffers, the
<code>*Message Log*</code> buffer, and so on are deleted from the list. Next,
-the frame's selected buffer is determined. Buffers with a different
+the frame’s selected buffer is determined. Buffers with a different
major mode from the selected buffer are removed from the list. Finally,
if the list is too long, the least recently used buffers are deleted
from the list. By default up to 6 most recently used buffers with the
@@ -683,7 +683,7 @@
<code>scrollbars-visible-p</code>, <code>toolbar-visible-p</code>, or
<code>gutter-buffers-tab-visible-p</code> respectively. (The strange form of
the last variable is due to the fact that gutters are often used to
-display transient widgets like progress gauges, which you probably don't
+display transient widgets like progress gauges, which you probably don’t
want to inhibit. It is more likely that you want to inhibit the default
display of the buffers tab widget, which is what that variable controls.
This interface is subject to change depending on developer experience
@@ -745,7 +745,7 @@
<p>XEmacs can be used with the X Window System and a window manager like
MWM or TWM. In that case, the X window manager opens, closes, and
-resizes XEmacs frames. You use the window manager's mouse gestures to
+resizes XEmacs frames. You use the window manager’s mouse gestures to
perform the operations. Consult your window manager guide or reference
manual for information on manipulating X windows.
</p>
@@ -821,7 +821,7 @@
</li><li>
There is a new frame/modeline format directive, %S, which expands to
-the name of the current frame (a frame's name is distinct from its
+the name of the current frame (a frame’s name is distinct from its
title; the name is used for resource lookup, among other things, and the
title is simply what appears above the window.)
</li></ul>
Index: Tests/xemacs_res/xemacs_5.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/xemacs_res/xemacs_5.html,v
retrieving revision 1.32
retrieving revision 1.33
diff -u -b -r1.32 -r1.33
--- Tests/xemacs_res/xemacs_5.html 5 Feb 2007 15:30:27 -0000 1.32
+++ Tests/xemacs_res/xemacs_5.html 3 Oct 2007 09:34:57 -0000 1.33
@@ -279,7 +279,7 @@
</p></dd>
<dt> <kbd>[(control c) (control 65)]</kbd></dt>
<dd><p>Typing <kbd>C-c</kbd> followed by <kbd>C-a</kbd>. (Using the ASCII code
-for the character `a')
+for the character ‘a’)
</p></dd>
<dt> <kbd>[(control c) (break)]</kbd></dt>
<dd><p>Typing <kbd>C-c</kbd> followed by the <kbd>break</kbd> character.
@@ -690,7 +690,7 @@
</p>
<a name="IDX44"></a>
<p> While we are on the subject of information for customization only,
-it's a good time to tell you about <em>variables</em>. Often the
+it’s a good time to tell you about <em>variables</em>. Often the
description of a command will say, “To change this, set the variable
<code>mumble-foo</code>.” A variable is a name used to remember a value.
Most of the variables documented in this manual exist just to facilitate
Index: Tests/xemacs_res/xemacs_6.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/xemacs_res/xemacs_6.html,v
retrieving revision 1.32
retrieving revision 1.33
diff -u -b -r1.32 -r1.33
--- Tests/xemacs_res/xemacs_6.html 5 Feb 2007 15:30:27 -0000 1.32
+++ Tests/xemacs_res/xemacs_6.html 3 Oct 2007 09:34:57 -0000 1.33
@@ -89,7 +89,7 @@
</p>
<p> It is possible to specify files to be visited, Lisp files to be
loaded, and functions to be called, by giving Emacs arguments in the
-shell command line. See section <a href="#SEC41">Command Line Switches and
Arguments</a>. But we don't recommend
+shell command line. See section <a href="#SEC41">Command Line Switches and
Arguments</a>. But we don’t recommend
doing this. The feature exists mainly for compatibility with other
editors.
</p>
@@ -101,7 +101,7 @@
</p>
<p> But starting a new Emacs each time you want to edit a different file
does not make sense. For one thing, this would be annoyingly slow. For
-another, this would fail to take advantage of Emacs's ability to visit
+another, this would fail to take advantage of Emacs’s ability to visit
more than one file in a single editing session. And it would lose the
other accumulated context, such as registers, undo history, and the mark
ring.
@@ -185,11 +185,11 @@
you use.) The only way on these systems to get back to the shell from
which Emacs was run (to log out, for example) is to kill Emacs.
</p>
-<p> Suspending also fails if you run Emacs under a shell that doesn't
+<p> Suspending also fails if you run Emacs under a shell that doesn’t
support suspending programs, even if the system itself does support it.
In such a case, you can set the variable <code>cannot-suspend</code> to a
non-<code>nil</code> value to force <kbd>C-z</kbd> to start an inferior shell.
-(One might also describe Emacs's parent shell as “inferior” for
+(One might also describe Emacs’s parent shell as “inferior”
for
failing to support job control properly, but that is a matter of taste.)
</p>
<p> When Emacs communicates directly with an X server and creates its own
@@ -396,14 +396,14 @@
<dl compact="compact">
<dt> ‘<samp>--show-dump-id</samp>’</dt>
<dt> ‘<samp>-sd</samp>’</dt>
-<dd><p>Print the ID for the new portable dumper's dump file on the terminal and
+<dd><p>Print the ID for the new portable dumper’s dump file on the
terminal and
exit. (Prints an error message and exits if XEmacs was not configured
‘<samp>--pdump</samp>’.)
</p>
</dd>
<dt> ‘<samp>--no-dump-file</samp>’</dt>
<dt> ‘<samp>-nd</samp>’</dt>
-<dd><p>Don't load the dump file. Roughly equivalent to old temacs. (Ignored
if
+<dd><p>Don’t load the dump file. Roughly equivalent to old temacs.
(Ignored if
XEmacs was not configured ‘<samp>--pdump</samp>’.)
</p>
</dd>
@@ -753,7 +753,7 @@
(you guessed it) last.
</p>
<p>By default, XEmacs expects an early package hierarchy in the
-subdirectory ‘<tt>.xemacs/xemacs-packages</tt>’ of the user's home
+subdirectory ‘<tt>.xemacs/xemacs-packages</tt>’ of the
user’s home
directory.
</p>
<p>Moreover, XEmacs expects late hierarchies in the subdirectories
@@ -888,7 +888,7 @@
<dt> <code>doc-directory</code></dt>
<dd><a name="IDX128"></a>
<p>Is the directory containing the architecture-specific
‘<tt>DOC</tt>’ file
-that contains documentation for XEmacs' commands.
+that contains documentation for XEmacs’ commands.
</p>
</dd>
<dt> <code>data-directory</code></dt>
Index: Tests/xemacs_res/xemacs_7.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/xemacs_res/xemacs_7.html,v
retrieving revision 1.30
retrieving revision 1.31
diff -u -b -r1.30 -r1.31
--- Tests/xemacs_res/xemacs_7.html 5 Feb 2007 15:30:27 -0000 1.30
+++ Tests/xemacs_res/xemacs_7.html 3 Oct 2007 09:34:57 -0000 1.31
@@ -160,7 +160,7 @@
characters act as editing commands and do not insert themselves. If you
need to insert a control character or a character whose code is above 200
octal, you must <em>quote</em> it by typing the character <kbd>Control-q</kbd>
-(<code>quoted-insert</code>) first. (This character's name is normally written
+(<code>quoted-insert</code>) first. (This character’s name is normally
written
<kbd>C-q</kbd> for short.) There are two ways to use <kbd>C-q</kbd>:
</p>
<ul>
@@ -217,9 +217,9 @@
clicking the left mouse button where you want to move to.
</p>
<p> NOTE: Many of the following commands have two versions, one that uses
-the function keys (e.g. <LEFT> or <END>) and one that doesn't.
+the function keys (e.g. <LEFT> or <END>) and one that
doesn’t.
The former versions may only be available on X terminals (i.e. not on
-TTY's), but the latter are available on all terminals.
+TTY’s), but the latter are available on all terminals.
</p>
<a name="IDX142"></a>
<a name="IDX143"></a>
@@ -605,7 +605,7 @@
</p>
<p> Sometimes it is nice to have Emacs insert newlines automatically when
a line gets too long. Continuation on the screen does not do that. Use
-Auto Fill mode (see section <a href="xemacs_23.html#SEC210">Filling Text</a>)
if that's what you want.
+Auto Fill mode (see section <a href="xemacs_23.html#SEC210">Filling Text</a>)
if that’s what you want.
</p>
<a name="IDX191"></a>
<a name="IDX192"></a>
Index: Tests/xemacs_res/xemacs_8.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/xemacs_res/xemacs_8.html,v
retrieving revision 1.22
retrieving revision 1.23
diff -u -b -r1.22 -r1.23
--- Tests/xemacs_res/xemacs_8.html 5 Feb 2007 15:30:27 -0000 1.22
+++ Tests/xemacs_res/xemacs_8.html 3 Oct 2007 09:34:58 -0000 1.23
@@ -71,7 +71,7 @@
</p>
<dl compact="compact">
<dt> <kbd>C-x u</kbd></dt>
-<dd><p>Undo one batch of changes (usually, one command's worth)
(<code>undo</code>).
+<dd><p>Undo one batch of changes (usually, one command’s worth)
(<code>undo</code>).
</p></dd>
<dt> <kbd>C-_</kbd></dt>
<dd><p>The same.
@@ -110,9 +110,9 @@
or saved.
</p>
<p> Not all buffers record undo information. Buffers whose names start with
-spaces don't; these buffers are used internally by Emacs and its extensions
-to hold text that users don't normally look at or edit. Minibuffers,
-help buffers, and documentation buffers also don't record undo information.
+spaces don’t; these buffers are used internally by Emacs and its
extensions
+to hold text that users don’t normally look at or edit. Minibuffers,
+help buffers, and documentation buffers also don’t record undo
information.
</p>
<p> Emacs can remember at most 8000 or so characters of deleted or
modified text in any one buffer for reinsertion by the undo command.
Index: Tests/xemacs_res/xemacs_9.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/xemacs_res/xemacs_9.html,v
retrieving revision 1.29
retrieving revision 1.30
diff -u -b -r1.29 -r1.30
--- Tests/xemacs_res/xemacs_9.html 5 Feb 2007 15:30:27 -0000 1.29
+++ Tests/xemacs_res/xemacs_9.html 3 Oct 2007 09:34:58 -0000 1.30
@@ -161,10 +161,10 @@
nearby directories, use <kbd>..</kbd>; thus, if you type
<kbd>../lisp/simple.el</kbd>, you will get the file named
‘<tt>/u2/emacs/lisp/simple.el</tt>’. Alternatively, you can kill
with
-<kbd>M-<DEL></kbd> the directory names you don't want (see section <a
href="xemacs_23.html#SEC206">Words</a>).
+<kbd>M-<DEL></kbd> the directory names you don’t want (see section
<a href="xemacs_23.html#SEC206">Words</a>).
</p>
-<p> If you don't want any of the default, you can kill it with <kbd>C-a
-C-k</kbd>. But you don't need to kill the default; you can simply ignore it.
+<p> If you don’t want any of the default, you can kill it with <kbd>C-a
+C-k</kbd>. But you don’t need to kill the default; you can simply
ignore it.
Insert an absolute file name, one starting with a slash or a tilde,
after the default directory. For example, to specify the file
‘<tt>/etc/termcap</tt>’, just insert that name, giving these
minibuffer
@@ -213,7 +213,7 @@
you are entering.
</p>
<p> Since <RET> in the minibuffer is defined to exit the minibuffer,
-you can't use it to insert a newline in the minibuffer. To do that,
+you can’t use it to insert a newline in the minibuffer. To do that,
type <kbd>C-o</kbd> or <kbd>C-q C-j</kbd>. (Recall that a newline is really
the
character control-J.)
</p>
@@ -310,7 +310,7 @@
in most of the names that you can complete (buffer names, file names and
command names). Thus, ‘<samp>fo</samp>’ does not complete to
‘<samp>Foo</samp>’. When
you are completing a name in which case does not matter, case may be
-ignored for completion's sake if specified by program.
+ignored for completion’s sake if specified by program.
</p>
<p>When a completion list is displayed, the completions will highlight as
you move the mouse over them. Clicking the middle mouse button on any
@@ -399,7 +399,7 @@
(<code>minibuffer-complete</code>).
</p></dd>
<dt> <kbd><SPC></kbd></dt>
-<dd><p>Complete the minibuffer text, but don't go beyond one word
+<dd><p>Complete the minibuffer text, but don’t go beyond one word
(<code>minibuffer-complete-word</code>).
</p></dd>
<dt> <kbd><RET></kbd></dt>
@@ -584,7 +584,7 @@
</p>
<a name="IDX229"></a>
<p> Icomplete mode presents a constantly-updated display that tells you
-what completions are available for the text you've entered so far. The
+what completions are available for the text you’ve entered so far. The
command to enable or disable this minor mode is <kbd>M-x
icomplete-mode</kbd>.
</p>
@@ -748,7 +748,7 @@
history unless it is identical to the most recently executed command
already there.
</p>
-<p> Even if you don't understand Lisp syntax, it will probably be obvious
+<p> Even if you don’t understand Lisp syntax, it will probably be
obvious
which command is displayed for repetition. If you do not change the text,
you can be sure the command will repeat exactly as before.
</p>
Index: Tests/xemacs_res/xemacs_toc.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/Tests/xemacs_res/xemacs_toc.html,v
retrieving revision 1.18
retrieving revision 1.19
diff -u -b -r1.18 -r1.19
--- Tests/xemacs_res/xemacs_toc.html 5 Feb 2007 15:30:27 -0000 1.18
+++ Tests/xemacs_res/xemacs_toc.html 3 Oct 2007 09:34:58 -0000 1.19
@@ -596,14 +596,14 @@
<li><a name="TOC392" href="xemacs_31.html#SEC403">Glossary</a></li>
<li><a name="TOC393" href="xemacs_32.html#SEC404">The GNU Manifesto</a>
<ul class="toc">
- <li><a name="TOC394" href="xemacs_32.html#SEC405">What's GNU? GNU's Not
Unix!</a></li>
+ <li><a name="TOC394" href="xemacs_32.html#SEC405">What’s GNU?
GNU’s Not Unix!</a></li>
<li><a name="TOC395" href="xemacs_32.html#SEC406">Why I Must Write
GNU</a></li>
<li><a name="TOC396" href="xemacs_32.html#SEC407">Why GNU Will Be
Compatible With Unix</a></li>
<li><a name="TOC397" href="xemacs_32.html#SEC408">How GNU Will Be
Available</a></li>
<li><a name="TOC398" href="xemacs_32.html#SEC409">Why Many Other
Programmers Want to Help</a></li>
<li><a name="TOC399" href="xemacs_32.html#SEC410">How You Can
Contribute</a></li>
<li><a name="TOC400" href="xemacs_32.html#SEC411">Why All Computer Users
Will Benefit</a></li>
- <li><a name="TOC401" href="xemacs_32.html#SEC412">Some Easily Rebutted
Objections to GNU's Goals</a></li>
+ <li><a name="TOC401" href="xemacs_32.html#SEC412">Some Easily Rebutted
Objections to GNU’s Goals</a></li>
</ul></li>
<li><a name="TOC402" href="xemacs_33.html#SEC413">Key (Character)
Index</a></li>
<li><a name="TOC403" href="xemacs_36.html#SEC414">Command and Function
Index</a></li>
Index: doc/texi2html.html
===================================================================
RCS file: /cvsroot/texi2html/texi2html/doc/texi2html.html,v
retrieving revision 1.56
retrieving revision 1.57
diff -u -b -r1.56 -r1.57
--- doc/texi2html.html 3 Oct 2007 07:39:33 -0000 1.56
+++ doc/texi2html.html 3 Oct 2007 09:34:58 -0000 1.57
@@ -205,7 +205,7 @@
considering that there is so much Texinfo documentation in
the world.
</p>
-<p>Some time ago <code>makeinfo</code> wasn't able to produce
+<p>Some time ago <code>makeinfo</code> wasn’t able to produce
<acronym>HTML</acronym> output format, but people still wanted documentation in
<acronym>HTML</acronym>. This was the birthing hour for
<code>texi2html</code>. The basic purpose of <code>texi2html</code>
@@ -255,19 +255,19 @@
<p>You would like to produce <acronym>HTML</acronym> files from your existing
Texinfo
files? There are two programs you can use to do this. The first is
-<code>makeinfo</code> (see <a
href="texinfo.html#Generating-HTML">(texinfo)Generating HTML</a> section
`Generating HTML' in <cite>GNU Texinfo</cite>).
+<code>makeinfo</code> (see <a
href="texinfo.html#Generating-HTML">(texinfo)Generating HTML</a> section
‘Generating HTML’ in <cite>GNU Texinfo</cite>).
The second is <code>texi2html</code>.
</p>
-<p>The design goal of <code>makeinfo</code>'s <acronym>HTML</acronym> output
was to produce
+<p>The design goal of <code>makeinfo</code>’s <acronym>HTML</acronym>
output was to produce
readable <acronym>HTML</acronym> output. It is now possible to use
<acronym>CSS</acronym>
for <acronym>HTML</acronym> customization. Another possibility is to use
intermediate
formats, like docbook or <code>makeinfo</code> <acronym>XML</acronym>
and <acronym>XSL</acronym> stylesheets to customize the resulting document.
Still the
-output produced by <code>makeinfo</code> isn't customizable.
+output produced by <code>makeinfo</code> isn’t customizable.
</p>
<p>The current development of <code>texi2html</code> tries to
provide for producing the more interesting and sophisticated
<acronym>HTML</acronym>
-pages that today's Internet users have come to expect.
+pages that today’s Internet users have come to expect.
The goal behind <code>texi2html</code> is to generate attractive
<acronym>HTML</acronym> by
default but also to allow users considerable freedom to affect the final
style and design of the output <acronym>HTML</acronym> pages. This is
achieved via
@@ -385,7 +385,7 @@
To play nice with encodings you
also need the <code>Encode</code> and <code>Unicode::Normalize</code> modules.
</p>
-<p>To rebuild the script perl isn't required in most cases. For more
+<p>To rebuild the script perl isn’t required in most cases. For more
information about advanced build features, see <a href="#SEC8">Advanced build
features</a>.
</p>
<hr size="6">
@@ -508,7 +508,7 @@
<code>Text::Unidecode</code> should be used or not. The default is to detect
it
with a test. This code requires the <code>Text::Unidecode</code> module.
</p>
-<p><code>perl</code> isn't
+<p><code>perl</code> isn’t
needed to build the script. the script is build by
‘<tt>./configure</tt>’
and a shell script launched by <code>make</code> which is a simple
wrapper around a <code>sed</code> one-liner. The <code>perl</code> command
@@ -519,8 +519,8 @@
</p>
<p>The translations are managed by a script <code>manage_i18n.pl</code>,
created
by <code>./configure</code>. <code>manage_i18n.pl</code> requires
-<code>Data::Dumper</code> to function normally. If this module isn't there
-<code>./configure</code> detects it and <code>manage_i18n.pl</code> doesn't
+<code>Data::Dumper</code> to function normally. If this module isn’t
there
+<code>./configure</code> detects it and <code>manage_i18n.pl</code>
doesn’t
really rebuild the translations, but only copy files. It is possible
to use the <code>./configure</code> switch <a name="IDX4"></a>
‘<samp>--enable-translations</samp>’
@@ -637,11 +637,11 @@
</p></dd>
<dt> ‘<samp>node</samp>’</dt>
<dd><p>The document is split at every sectioning command. It is not
necessarily
-split at each node, if the <code>@node</code> structure doesn't correspond with
+split at each node, if the <code>@node</code> structure doesn’t
correspond with
the sectioning command structure (see below).
</p></dd>
<dt> ‘<samp>none</samp>’</dt>
-<dd><p>The document isn't split. This is the default.
+<dd><p>The document isn’t split. This is the default.
</p></dd>
</dl>
@@ -649,10 +649,10 @@
elements in Texinfo: <code>@node</code> and the structuring commands
(<code>@top</code>,
<code>@section</code>, <code>@appendixsubsec</code>, and so on). A node just
preceding
a structuring command is considered to be part of the same sectioning element
-as that command. If the <code>@node Top</code> isn't associated with a
structuring
+as that command. If the <code>@node Top</code> isn’t associated with a
structuring
command it also defines a sectioning element.
</p>
-<p>By default, nodes which aren't associated with a structuring command are not
+<p>By default, nodes which aren’t associated with a structuring command
are not
considered to be sectioning commands. They are always considered to be part
of a sectioning element defined by a structuring command. It is possible to
change this behaviour via the <a name="IDX9"></a>
@@ -664,7 +664,7 @@
</p>
<p>This default behaviour mimics <code>texi2dvi</code> behaviour, which
ignores
<code>@node</code> commands for the purprose of sectioning, while the second
-looks like <code>makeinfo</code> behaviour (see <a
href="texinfo.html#Two-Paths">(texinfo)Two Paths</a> section `Two Paths' in
<cite>GNU Texinfo</cite>).
+looks like <code>makeinfo</code> behaviour (see <a
href="texinfo.html#Two-Paths">(texinfo)Two Paths</a> section ‘Two
Paths’ in <cite>GNU Texinfo</cite>).
</p>
<p>As an illustration, the following table shows how a sample Texinfo document
is
divided into sectioning elements when <a name="IDX11"></a>
@@ -767,7 +767,7 @@
name.
</p>
<p>By default, <code>texi2html</code> generates the manual file in the current
-directory if the manual isn't split. A ‘<samp>.html</samp>’ file
extension is appended
+directory if the manual isn’t split. A ‘<samp>.html</samp>’
file extension is appended
to the manual name.
</p>
<p>If the manual is split the files are put in a directory named after the
@@ -792,7 +792,7 @@
</pre></td></tr></table>
<p>This default behavior may be modified by several command line options. If
the
-output isn't split, the prefix file name may be overrided by the
+output isn’t split, the prefix file name may be overrided by the
<a name="IDX13"></a>
‘<samp>--output</samp>’ command line option (variable <a
name="IDX14"></a>
<code>$OUT</code>). If the output
@@ -842,7 +842,7 @@
<code>$NODE_FILES</code>).
The default is false for this option.
If the output
-isn't split at nodes, <code>texi2html</code> will still output files named
after
+isn’t split at nodes, <code>texi2html</code> will still output files
named after
the nodes, without real content but redirecting to the right file.
This trick enables the generated <acronym>HTML</acronym> manual to be a
target for the cross-references of other manuals generated by
@@ -1068,7 +1068,7 @@
<code>@CSS_FILES</code>).
</p>
<p>The option use is the same than for <code>makeinfo</code> and is described
-extensively in <a href="texinfo.html#HTML-CSS">(texinfo)HTML CSS</a> section
`HTML CSS' in <cite>GNU Texinfo</cite>.
+extensively in <a href="texinfo.html#HTML-CSS">(texinfo)HTML CSS</a> section
‘HTML CSS’ in <cite>GNU Texinfo</cite>.
Briefly, the <acronym>CSS</acronym> <code>@import</code> lines from the
external file
<acronym>CSS</acronym> file are pasted before the
<code>texi2html</code> <acronym>CSS</acronym> rules, and the external file
<acronym>CSS</acronym>
@@ -1164,7 +1164,7 @@
</p>
<a name="IDX71"></a>
<p>‘<samp>--l2h-tmp</samp>’ sets the directory used for temporary
-files, this name shouldn't contain a dot ‘<samp>.</samp>’
+files, this name shouldn’t contain a dot ‘<samp>.</samp>’
(variable is <a name="IDX72"></a>
<code>$L2H_TMP</code>). Defaults to the current dir.
</p>
@@ -1265,7 +1265,7 @@
<h1 class="chapter"> 5. Overview of initialization files content and loading
</h1>
<p>The initialization files are <code>perl</code> files, read as explained
-in <a href="#SEC17">Use initialization files for fine tuning</a>. You don't
need to know much of <code>perl</code>
+in <a href="#SEC17">Use initialization files for fine tuning</a>. You
don’t need to know much of <code>perl</code>
to do some simple changes in variable values, however, to be able to
really take advantage of all the features of the initialization file,
a good knowledge of <code>perl</code> is required.
@@ -1547,7 +1547,7 @@
top element.
</p>
<p>The top element is formatted differently than a normal element if there
-is a <code>@top</code> section or the <code>@node Top</code> isn't associated
+is a <code>@top</code> section or the <code>@node Top</code> isn’t
associated
with a sectioning command.
</p></dd>
<dt> <em>Misc elements</em></dt>
@@ -1560,12 +1560,12 @@
</li><li> About page
</li></ol>
-<p>The <em>About page</em> shouldn't be present for documents consisting
+<p>The <em>About page</em> shouldn’t be present for documents consisting
in only one sectioning element, or for documents unsplit and without
navigation information. The <em>Footnote page</em> should only
be present if the footnotes appear on a separated page
(see section <a href="#SEC14">Page layout related command line options</a>),
however a footnote element is present if
-the document isn't split. The <em>Table of contents</em> should only
+the document isn’t split. The <em>Table of contents</em> should only
be formatted if <code>@contents</code> is present in the document.
Similarly the <em>Overview</em> should only appear if
<code>@shortcontents</code>
or <code>@summarycontents</code> is present. The Table of contents and
@@ -1617,7 +1617,7 @@
<p>In the header some important meta data may be defined, like the
title or style information, and textual informations may be present
-in comments. All this doesn't appear directly in the displayed
+in comments. All this doesn’t appear directly in the displayed
<acronym>HTML</acronym>, though.
</p>
<p>The page layout is mainly controlled by functions, the precise functions
@@ -1733,7 +1733,7 @@
<p>A lot of customization of the navigation panel may be achieved without
redefining functions, with variables redefinition.
-In case it isn't enough, it is also possible to redefine the function
+In case it isn’t enough, it is also possible to redefine the function
doing the navigation panel formatting.
</p>
<table class="menu" border="0" cellspacing="0">
@@ -2174,7 +2174,7 @@
exampleindent, firstparagraphindent, everyheading, everyfooting,
evenheading, evenfooting, oddheading, oddfooting, setcontentsaftertitlepage,
setshortcontentsaftertitlepage, frenchspacing.
-If the command doesn't have any arg, it will be true is it was set.
+If the command doesn’t have any arg, it will be true is it was set.
</p>
<a name="SEC34"></a>
@@ -2392,7 +2392,7 @@
<code>$CSS_LINES</code>. If this
variable is defined the variable value is used instead of being
constructed using the <a name="IDX132"></a>
-<code>%css_map</code> entries. For example if you don't
+<code>%css_map</code> entries. For example if you don’t
want any css entries, set
</p>
<table><tr><td> </td><td><pre class="example">$CSS_LINES = '';
@@ -2404,7 +2404,7 @@
to modify the array corresponding with the array
reference <code>$Texi2HTML::THISDOC{'css_lines'}</code> that contains
the normal <acronym>CSS</acronym> files lines (for details on what corresponds
with
-those different lines, see <a href="texinfo.html#HTML-CSS">(texinfo)HTML
CSS</a> section `HTML CSS' in <cite>GNU Texinfo</cite>).
+those different lines, see <a href="texinfo.html#HTML-CSS">(texinfo)HTML
CSS</a> section ‘HTML CSS’ in <cite>GNU Texinfo</cite>).
The right place to modify these arrays is in a function appearing in
the <code>@command_handler_process</code> array
(see section <a href="#SEC91">Bypassing normal formatting</a>). Later, the
<acronym>CSS</acronym> lines
@@ -2460,7 +2460,7 @@
</p>
<p>The HTML encoding of the resulting document is defined by
<a name="IDX139"></a>
-<code>$ENCODING_NAME</code>. If the variable isn't defined,
+<code>$ENCODING_NAME</code>. If the variable isn’t defined,
the <code>@documentencoding</code> value is used, or the
<a name="IDX140"></a>
<code>$OUT_ENCODING</code> value, if set. <code>$ENCODING_NAME</code> may
@@ -2471,7 +2471,7 @@
<p>The description of the document may be specified in
<a name="IDX141"></a>
<code>$DOCUMENT_DESCRIPTION</code>. If this variable is undef, the text
-associated with <code>@documentdescription</code> is used, and if there isn't
+associated with <code>@documentdescription</code> is used, and if there
isn’t
such test a default description is constructed using the document title and
the name of the first section of the file.
</p>
@@ -2771,7 +2771,7 @@
<dd><p><var>$filehandle</var> is the opened filehandle the function should
write to.
<var>$begin_page</var> is true if the element is the first in a page.
This function should begin the Top element. At the time this function is called
-the top element text hasn't been parsed.
+the top element text hasn’t been parsed.
</p></dd></dl>
<dl>
@@ -2828,7 +2828,7 @@
is set. This behaviour is more consistent with <code>texi2dvi</code>.
If <code>@setcontentsaftertitlepage</code> appears in the document,
and even if <code>$INLINE_CONTENTS</code> is set, the table of contents are
-merged in the title (which isn't output in the default case, see
+merged in the title (which isn’t output in the default case, see
<a href="#SEC49">Formatting of title page</a>).
</p>
<p>Several variables may be used to control the formatting of table of
contents
@@ -2922,7 +2922,7 @@
</p></dd>
</dl>
-<p>This function doesn't return anything but should fill the array
corresponding
+<p>This function doesn’t return anything but should fill the array
corresponding
with the
<a name="IDX178"></a>
<code>$Texi2HTML::TOC_LINES</code> and
@@ -3151,7 +3151,7 @@
<a name="IDX190"></a>
</dt>
<dd><p>Formatting of footnotes section or page in case footnotes are on a
-separated page or the document isn't split.
+separated page or the document isn’t split.
</p></dd>
</dl>
@@ -3530,7 +3530,7 @@
the values corresponding with two interfaces. The values may be strings or
hash references, and you can chose the interface depending on the one you
prefer. The interface with hash reference is a bit more flexible but might also
-be regarded as more complex. If you don't like either of these interfaces you
+be regarded as more complex. If you don’t like either of these
interfaces you
can define your own.
</p>
<p>Some remarks are in order:
@@ -3784,7 +3784,7 @@
</tr></table>
<h3 class="subsection"> 7.3.3 Defining the style and indicatric commands
interface </h3>
-<p>If you don't like this scheme, it is possible to change how those commands
+<p>If you don’t like this scheme, it is possible to change how those
commands
are processed by redefining the following function reference:
</p>
<dl>
@@ -3979,7 +3979,7 @@
<p>Some characters are special, for example we have
‘<samp>&</samp>’, ‘<samp>"</samp>’,
‘<samp><</samp>’ and ‘<samp>></samp>’ in
<acronym>HTML</acronym>. In some cases some
-pieces of text don't go through the above function, but still
+pieces of text don’t go through the above function, but still
needs to be protected to appear in text.
This is done by the function associated with the function reference
</p>
@@ -4067,7 +4067,7 @@
as ‘<samp>%</samp>’.
</p>
<p>When a <code>@documentlanguage</code> appears in the document and the
language
-wasn't set on the command line, it may be convenient for the user to
+wasn’t set on the command line, it may be convenient for the user to
redefine some variables based on the new language. There is a function
reference that may be used for that, it is called each time a
<code>@documentlanguage</code> is encountered:
@@ -4077,7 +4077,7 @@
<a name="IDX233"></a>
</dt>
<dd><p>This function is called each time <code>@documentlanguage</code> is
encountered
-and the language wasn't seet on the command line. It should be used
+and the language wasn’t seet on the command line. It should be used
to retranslate some strings based on the new language.
</p></dd></dl>
@@ -4145,13 +4145,13 @@
node name mapped to an identifier acceptable as a file name.
<var>$xml_node_identifier</var> is the
node name mapped to an identifier acceptable as an <acronym>XML</acronym>
identifier.
-Those identifiers are built as explained in <a
href="texinfo.html#HTML-Xref">(texinfo)HTML Xref</a> section `HTML Xref' in
<cite>GNU Texinfo</cite>,
+Those identifiers are built as explained in <a
href="texinfo.html#HTML-Xref">(texinfo)HTML Xref</a> section ‘HTML
Xref’ in <cite>GNU Texinfo</cite>,
thus allowing for cross references to external manuals. <var>$file</var> is the
manual or file name of the external reference. This function should return an
href leading to the external manual.
</p>
<p>The default for this function is to make a reference compatible with
-<code>makeinfo</code> (see <a href="texinfo.html#HTML-Xref">(texinfo)HTML
Xref</a> section `HTML Xref' in <cite>GNU Texinfo</cite>).
+<code>makeinfo</code> (see <a href="texinfo.html#HTML-Xref">(texinfo)HTML
Xref</a> section ‘HTML Xref’ in <cite>GNU Texinfo</cite>).
</p></dd></dl>
<dl>
@@ -4468,7 +4468,7 @@
<a href="#SEC67">Formatting (or not) a paragraph and a preformatted
region</a>, and the name of the complex
format will be available to the function formatting the text.
</p>
-<p>If you aren't satisfied with this scheme, you can redefine the following
+<p>If you aren’t satisfied with this scheme, you can redefine the
following
function reference for a better control over the complex format formatting:
</p>
<dl>
@@ -4682,10 +4682,10 @@
If the text is empty nothing is added to the text.
</li></ul>
-<p>In case the <code>%format_map</code> isn't used, a function reference called
+<p>In case the <code>%format_map</code> isn’t used, a function reference
called
<code>$table_list</code>
should be redefined, the associated function will be called each time
-a command isn't found in <code>%format_map</code>.
+a command isn’t found in <code>%format_map</code>.
</p>
<dl>
<dt><u>Function Reference:</u> $whole_table_list <b>table_list</b><i> $command
$text</i>
@@ -4783,7 +4783,7 @@
</pre></td></tr></table>
</li><li>
-If the command isn't a shortcut, it is associated with an array
+If the command isn’t a shortcut, it is associated with an array
reference. The first element is ‘<samp>f</samp>’,
‘<samp>v</samp>’ or ‘<samp>t</samp>’ corresponding
with the index type (‘<samp>f</samp>’ for function,
‘<samp>v</samp>’ for variable,
‘<samp>t</samp>’ for type).
@@ -5206,7 +5206,7 @@
<p>If the menu is to be formatted in a single preformatted environment,
an entry for ‘<samp>menu</samp>’ should be added to the
<code>$complex_format_map</code>
hash reference (see section <a href="#SEC70">Formatting of complex formats
(<code>@example</code>, <code>@display</code>…)</a>).
-In the default case, if the user didn't add an entry himself, a very simple
+In the default case, if the user didn’t add an entry himself, a very
simple
entry is used, with:
</p>
<table><tr><td> </td><td><pre
class="example">$complex_format_map->{'menu'} = { 'begin' => q{''} ,
'end' => q{''},
@@ -5239,7 +5239,7 @@
<code>$NODE_NAME_IN_MENU</code> is
true, however, node names are used. If <a name="IDX273"></a>
<code>$AVOID_MENU_REDUNDANCY</code>
-is true and menu entry equal menu description the description isn't printed.
+is true and menu entry equal menu description the description isn’t
printed.
This is the default. Likewise, if node or section name equal entry name,
do not print entry name.
</p>
@@ -5777,7 +5777,7 @@
<p>The function references are called like:
</p>
<dl>
-<dt><u>Function Reference:</u> $status
<b>$command_handler{'$command'}</b><i>->{'init'} $command $text $count</i>
+<dt><u>Function Reference:</u> $status
<b>$command_handler{’$command’}</b><i>->{’init’}
$command $text $count</i>
<a name="IDX295"></a>
</dt>
<dd><p><var>$command</var> is the @-command name, <var>$text</var> is the text
appearing
@@ -5788,7 +5788,7 @@
</p></dd></dl>
<dl>
-<dt><u>Function Reference:</u> $result
<b>$command_handler{'$command'}</b><i>->{'expand'} $command $count $state
$text</i>
+<dt><u>Function Reference:</u> $result
<b>$command_handler{’$command’}</b><i>->{’expand’}
$command $count $state $text</i>
<a name="IDX296"></a>
</dt>
<dd><p><var>$command</var> is the @-command name, <var>$count</var> is a
counter counting
@@ -5917,12 +5917,12 @@
<dd><p>If true the args and the macro are kept, otherwise they are discarded.
The defaut is to have <code>keep</code> undef for all the commands.
If <code>keep</code> is true for <code>@verbatiminclude</code> the default
-action for this macro isn't done.
+action for this macro isn’t done.
</p></dd>
</dl>
-<p>Commands which don't appear in the hashes
+<p>Commands which don’t appear in the hashes
<a name="IDX301"></a>
<code>%simple_map</code>, <a name="IDX302"></a>
<code>%simple_map_pre</code>,
@@ -6088,7 +6088,7 @@
</tr></table>
<h3 class="appendixsubsec"> A.1.2 Contributing translations to another
language </h3>
-<p>If the language isn't currently supported, copy the
‘<tt>en</tt>’ file in
+<p>If the language isn’t currently supported, copy the
‘<tt>en</tt>’ file in
‘<tt>i18n</tt>’ to a file with name the two-letter ISO-639
language code of your language
and then add your translations to the strings. You could also add your
@@ -6155,7 +6155,7 @@
./manage_i18n.pl update
</pre></td></tr></table>
-<p>These two commands won't work if you don't have the
+<p>These two commands won’t work if you don’t have the
<code>Data::Dumper</code> module installed.
And to merge the new translation files in
‘<tt>translations.pl</tt>’, do
</p>
@@ -6218,7 +6218,7 @@
</li><li> End of line removal is done in formatting function of definition line
formatting.
</li><li> node_file_name now should only returns the node file, since the
-redirection file isn't used anymore. element_file_name only is used for
+redirection file isn’t used anymore. element_file_name only is used for
file names, whatever NODES_FILES is.
</li></ul>
</li><li> changes between 1.66 and 1.68:
@@ -6243,16 +6243,16 @@
</p>
<p>If you want a backward compatibility you can use
‘<samp>-subdir</samp>’
for the output directory if the document is split, and
‘<samp>-out-file</samp>’
-if the document isn't split. This hasn't been tested extensively though.
+if the document isn’t split. This hasn’t been tested extensively
though.
</p></li><li> Many options has been obsoleted but they are retained for
backward compatibility.
</li><li> The init files are searched in new directories, however they
are still searched for in the old directories for backward
compatibility.
-</li><li> the option ‘<samp>--glossary</samp>’ doesn't do
anything. Likely
+</li><li> the option ‘<samp>--glossary</samp>’ doesn’t do
anything. Likely
nothing specific is done regarding bibliographies. This has been
decided because this added some semantics to the texinfo formatting
-language that weren't part of texinfo.
+language that weren’t part of texinfo.
<p>It should be possible to do
something similar with macros. See for example
‘<tt>glossary.texi</tt>’
@@ -6260,11 +6260,11 @@
in the directory ‘<tt>examples</tt>’. In the web2c package there is
an example of use of BibTeX, see <a
href="http://tug.org/texlive/devsrc/Build/source/TeX/texk/web2c/doc/";>http://tug.org/texlive/devsrc/Build/source/TeX/texk/web2c/doc/</a>
(the examples for bibliography are taken from the
texinfo home page <a
href="http://www.gnu.org/software/texinfo/texinfo.html";>http://www.gnu.org/software/texinfo/texinfo.html</a>).
-</p></li><li> don't use <code>T2H_CENTER_IMAGE</code>. <code>@center</code>
should be used
+</p></li><li> don’t use <code>T2H_CENTER_IMAGE</code>.
<code>@center</code> should be used
insead, it will give the right output for all the formats.
</li><li> If a directory creation fails the program aborts. This is much safer.
</li><li> The interface for internationalisation changed, although
-the previous wasn't documented a lot.
+the previous wasn’t documented a lot.
</li><li> the API described in this manual changed a lot. A important
change was to use the <code>Texi2HTML::Config</code> names space instead of
variables prefixed with ‘<samp>T2H_</samp>’ or
‘<samp>t2h_</samp>’. To cope with
@@ -6272,7 +6272,7 @@
Some variables are now in <code>%Texi2HTML::THISDOC</code>.
</li><li> <code>@ifinfo</code> regions are not expanded by default. This may
lead
to warnings or errors especially if the Top node is enclosed in
-<code>@ifinfo</code>, as some node won't appear in menus. The quick fix
+<code>@ifinfo</code>, as some node won’t appear in menus. The quick fix
is to call <code>texi2html</code> with the option
‘<samp>--ifinfo</samp>’ and
the right way should be to make more use of <code>@ifnottex</code>.
</li><li> The code appearing before the first node is now outputted, it was
@@ -6304,9 +6304,9 @@
<h1 class="chapter"> C. How little texi2html texinfo differs from GNU texinfo
</h1>
<p>For features documented in the texinfo manual, the texinfo interpretation
-by <code>texi2html</code> shouldn't differ from the interpretation of
+by <code>texi2html</code> shouldn’t differ from the interpretation of
<code>makeinfo</code> or <code>texi2dvi</code>. However for constructs with
-unspecified behaviour <code>texi2html</code> often doesn't lead to the
+unspecified behaviour <code>texi2html</code> often doesn’t lead to the
same result than <code>makeinfo</code> or <code>texi2dvi</code>.
<code>makeinfo</code>
and <code>texi2dvi</code> are also inconsistent in most of these cases (or
broken). You are urged not to use these features unless absolutely necessary.
@@ -6336,7 +6336,7 @@
<dd><p>The special @-commands are commands like <code>@pagesizes</code>,
<code>@sp</code>,
<code>@evenheading</code>, <code>@raisesections</code>, <code>@defindex</code>
and a lot
more. In many cases <code>makeinfo</code> and <code>texi2dvi</code>
-don't parse those commands the same way too. <code>texi2html</code> may also
+don’t parse those commands the same way too. <code>texi2html</code> may
also
show some differences in parsing of the arguments of these commands,
in case there are wrong arguments, and also ignore differently things
following those commands. How user defined macros, set and values
@@ -6361,7 +6361,7 @@
</p>
<ul>
<li> <code>@rmacro</code> and <code>@macro</code> behave exactly the same. In
fact
-this goes against a documented behaviour, however if a user don't
+this goes against a documented behaviour, however if a user don’t
want a recursive macro he can simply avoid reusing the macro in the
definition. If somebody report that the feature is usefull we could try
to implement it.
@@ -6371,14 +6371,14 @@
<p>with the ‘<samp>\</samp>’ being removed after the first
expansion. Otherwise
it is not possible to produce a <code>address@hidden macro</code> in a macro.
</p></li><li> <code>@unmacro</code> is interpreted during the macro argument
expansion.
-Don't know what <code>makeinfo</code> exactly do.
+Don’t know what <code>makeinfo</code> exactly do.
</li><li> Some <code>@value</code> may be expanded later than the others, those
that are in special commands, like <code>@node</code>.
</li></ul>
</dd>
<dt> <code>@,</code> in <code>@node</code></dt>
-<dd><p>Like <code>texi2dvi</code> but unlike <code>makeinfo</code>
<code>@,</code> don't
+<dd><p>Like <code>texi2dvi</code> but unlike <code>makeinfo</code>
<code>@,</code> don’t
break <code>@node</code> arguments like a regular ‘<samp>,</samp>’.
</p></dd>
<dt> Things before first node or preamble</dt>
@@ -6390,7 +6390,7 @@
knows about.
</p></dd>
<dt> commands in <code>@ifset</code> and <code>@ifclear</code></dt>
-<dd><p><code>texi2html</code> doesn't need a proper nesting of internal
<code>@ifset</code>
+<dd><p><code>texi2html</code> doesn’t need a proper nesting of internal
<code>@ifset</code>
or <code>@ifclear</code> if they are in ignored or raw regions (like
<code>@html</code>
or <code>@verbatim</code>). For example the following is accepted by
<code>texi2html</code> and not by <code>makeinfo</code>:
| [Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Texi2html-cvs] texi2html ChangeLog texi2html.init Tests/German...,
Patrice Dumas <=