Re: Inconsistency in writing apostrophe in info and html output with version 7.0.3

[Raymond Toy]

On 6/5/23 10:50, Gavin Smith wrote:


On Mon, Jun 05, 2023 at 07:18:00AM -0700, Raymond Toy wrote:

Maxima grovels over the html file to find appropriate links to use for the
html version of the manual. This was working fine with 6.8 and earlier
because I found appropriate regexps to find the links.

This stopped working in 7.0.3 (and maybe earlier?). The regexps no longer
work. This is fine; there was no promise that the format of html links would
be consistent.

The problem I’m seeing is that in the texi source, we have:

|@vrindex Euler's number |

That apostrophe is really an apostrophe character, unicode U+27.

However, in the generated info file, the index has:

|* Euler’s number: Functions and Variables for Constants. |


We'd already addressed this problem for Info output:

https://lists.gnu.org/archive/html/bug-texinfo/2023-02/msg00048.html


The summary is that words with apostrophes, like "don't", should be
output in Info with an ASCII apostrophe so it is easy to search for these
words.

The end result of this was that we made the output for ' and `
in Texinfo, as well as hyphen characters, use ASCII characters
by default, with a new customiation variable to control this
(ASCII_DASHES_AND_QUOTES).  This will be included in the next Texinfo
release.

Are you easily able to check this with the current Texinfo development
sources?

If you use Texinfo 7.0.3 then you could try setting OPEN_QUOTE_SYMBOL
or CLOSE_QUOTE_SYMBOL to ' (ASCII apostrophe) to turn this off.


I added |--set-customization-variable OPEN_QUOTE_SYMBOL=' 
--set-customization-variable CLOSE_QUOTE_SYMBOL='| to the invocation of 
makeinfo. This seemed to work. Kind of. We have:


|11 Maxima’s Database  * Menu: * Introduction to 
Maxima's Database:: |


That’s an actual apostrophe. However, I think maxima parses the info 
file using the section title:


|11.1 Introduction to Maxima’s Database |

and that’s U+2019, not an apostrophe (U+27).

This isn’t catastrophic. There appear to be only two places where this 
happens so I can just make a special case for them.


.

​

[PROPOSED] * doc/texinfo.tex: spelling fixes

[Paul Eggert]

* doc/texinfo.tex: Fix two misspellings in comments.
Originally reported by Josh Soref  in:
https://lists.gnu.org/r/bug-gnulib/2023-06/msg00057.html
---
 doc/texinfo.tex | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/doc/texinfo.tex b/doc/texinfo.tex
index 9e66eeb720..8885f1827c 100644
--- a/doc/texinfo.tex
+++ b/doc/texinfo.tex
@@ -3,7 +3,7 @@
 % Load plain if necessary, i.e., if running under initex.
 \expandafter\ifx\csname fmtname\endcsname\relax\input plain\fi
 %
-\def\texinfoversion{2023-04-06.21}
+\def\texinfoversion{2023-06-08.14}
 %
 % Copyright 1985, 1986, 1988, 1990-2023 Free Software Foundation, Inc.
 %
@@ -5783,7 +5783,7 @@ might help (with 'rm \jobname.?? \jobname.??s')%
   % below is chosen so that the gutter has the same value (well, +-<1pt)
   % as it did when we hard-coded it.
   %
-  % We put the result in a separate register, \doublecolumhsize, so we
+  % We put the result in a separate register, \doublecolumnhsize, so we
   % can restore it in \pagesofar, after \hsize itself has (potentially)
   % been clobbered.
   %
@@ -8180,7 +8180,7 @@ might help (with 'rm \jobname.?? \jobname.??s')%
 % Read recursive and nonrecursive macro bodies. (They're different since
 % rec and nonrec macros end differently.)
 % 
-% We are in \macrobodyctxt, and the \xdef causes backslashshes in the macro 
+% We are in \macrobodyctxt, and the \xdef causes backslashes in the macro 
 % body to be transformed.
 % Set \macrobody to the body of the macro, and call \macrodef.
 %
-- 
2.40.1