|
From: | Raymond Toy |
Subject: | Inconsistency in writing apostrophe in info and html output with version 7.0.3 |
Date: | Mon, 5 Jun 2023 07:18:00 -0700 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.9.1 |
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.
In emacs , the
apostrophe shows up as \342\200\231
,
which is Right_Single_Quotation_Mark, unicode U+2019.
This is a problem because we use the info file as the source of truth, but the HTML file only uses an apostrophe, so we end up with an entry that we can find in the info file but not in the html file. This did not happen in texinfo 6.8.
Was this intentional? If so, are all apostrophes (U+27) converted to right_single_quotation_mark (U+2019) in the info file? That’s something I can deal with since it’s consistent.
[Prev in Thread] | Current Thread | [Next in Thread] |