On Sat, Jun 06, 2026 at 02:33:53PM -0600, Karl Berry wrote:
> Hi Gavin, Patrice, all - I happened to notice occasional use of
> "lower-case" and "upper-case". These words are not hyphenated in most of
> the manual. While I was there, I ran a simple spelling check and
> doubled-word check.

Thanks, applied in full.


> One change I did not make, since it's in the code: "COPIABLE" is
> normally spelled "COPYABLE", for "COPIABLE_LINKS". If you change the
> parameter name, I suggest "COPYABLE_LINK_TARGETS" or "COPYABLE_ANCHORS",
> since links themselves are normally copyable. At least I think that's
> what it does? I'm not entirely sure from the description. --best, karl.

As far as I could tell, both spellings have been considered correct.

The variable was in fact originally called "COPIABLE_ANCHORS".  It was
renamed to "COPIABLE_LINKS" in Texinfo 7.0.

We could change it to COPYABLE if we were going to change it anyway but
there does not seem much point to me.  It's possible (as with many of the
texi2any customization variables) that it is not much used, and in that
case it would not inconvenience users much if we changed the spelling.

The purpose of this variable can be seen on a page like the following:

https://gcc.gnu.org/onlinedocs/gcc-16.1.0/gcc/Floating-Point-Format-Builtins.html

If you view this in a web browser and put your mouse pointer over
any of the lines showing function signatures, you can see a ΒΆ symbol
appear. In many web browsers, you can then do something like right click
and click on "Copy link address" in the menu that appears.  This enables
you to save a link to a particular part of a page, like:

https://gcc.gnu.org/onlinedocs/gcc-16.1.0/gcc/Floating-Point-Format-Builtins.html#index-_005f_005fbuiltin_005finf

Using "texi2any -c COPIABLE_LINKS=0" would omit these links from appearing
in the output.

Reply via email to