Re: Inconsistency in writing apostrophe in info and html output with version 7.0.3
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 Oops. Sorry. I'm on the mailing list, but I don't recall seeing this. My memory is not so good anymore. :-( 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'll look into this soon; thanks for the tip. It's a bit of a problem though because people use all different versions of texinfo to build maxima docs. I've pretty much stayed with 6.8, but some want to use the ancient 5.1, and some are building with 7.0.3. I can check with the current dev version. But it will take a while since I'm in the middle of getting this to work with 7.0.3.
Re: Inconsistency in writing apostrophe in info and html output with version 7.0.3
On 6/5/23 08:32, Eli Zaretskii wrote:
Date: Mon, 5 Jun 2023 08:11:00 -0700
From: Raymond Toy
It appears not to be consistent. We have this in the texinfo source:
@fnindex N'th previous output
with a real apostrohpe. The info file has
* N'th previous output: Functions and Variables for Command
Line.
and that’s also a real apostrophe. Don’t know what’s different between the two
cases.
I'm guessing that @fnindex is the index of function names, in which
case it generates a "code" typeface, where ASCII characters are not
converted to their Unicode typographical equivalents.
So this is consistent, jut not the kind of consistency you expected.
Ah, that makes sense. Except that it’s not really a function. For
context, we do:
|@anchor{%th} @deffn {Function} %th (@var{i}) @fnindex N'th previous output |
Not sure what else we should do here. I’ll have to play around with the
customization variables to see what I can do.
Thanks for you help.
Re: Inconsistency in writing apostrophe in info and html output with version 7.0.3
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. > 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. We should check the output in HTML for these constructs to check they are what they should be. Consistency with Info output sounds like a good idea. I hope to look into this issue soon. > 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. I think so but it will change in future Texinfo releases.
Re: Inconsistency in writing apostrophe in info and html output with version 7.0.3
> Date: Mon, 5 Jun 2023 08:11:00 -0700 > From: Raymond Toy > > It appears not to be consistent. We have this in the texinfo source: > > > @fnindex N'th previous output > > with a real apostrohpe. The info file has > > > * N'th previous output: Functions and Variables for Command > Line. > > and that’s also a real apostrophe. Don’t know what’s different between the > two cases. I'm guessing that @fnindex is the index of function names, in which case it generates a "code" typeface, where ASCII characters are not converted to their Unicode typographical equivalents. So this is consistent, jut not the kind of consistency you expected.
Re: Inconsistency in writing apostrophe in info and html output with version 7.0.3
> Date: Mon, 5 Jun 2023 07:18:00 -0700 > From: Raymond Toy > > 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 the default, but it is customizable, see the node "Other Customization Variables" in the Texinfo manual.
Re: Inconsistency in writing apostrophe in info and html output with version 7.0.3
On 6/5/23 07:18, Raymond Toy wrote: 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. It appears not to be consistent. We have this in the texinfo source: |@fnindex N'th previous output | with a real apostrohpe. The info file has |* N'th previous output: Functions and Variables for Command Line. | and that’s also a real apostrophe. Don’t know what’s different between the two cases.
Inconsistency in writing apostrophe in info and html output with version 7.0.3
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.
