Bug 19737 - Doc page “20.5.2 Infinity and NaN” has incorrect HTML character entities for infinity & pi
Summary: Doc page “20.5.2 Infinity and NaN” has incorrect HTML character entities for ...
Status: RESOLVED FIXED
Alias: None
Product: glibc
Classification: Unclassified
Component: admin (show other bugs)
Version: unspecified
: P2 normal
Target Milestone: 2.32
Assignee: Florian Weimer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-02-26 23:15 UTC by Slipp Douglas Thompson
Modified: 2020-07-16 08:18 UTC (History)
4 users (show)

See Also:
Host:
Target:
Build:
Last reconfirmed:
fweimer: security-


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Slipp Douglas Thompson 2016-02-26 23:15:25 UTC
The HTML documentation page “20.5.2 Infinity and NaN” (http://www.gnu.org/software/libc/manual/html_node/Infinity-and-NaN.html) has incorrectly double-escaped HTML character entities for infinity & pi symbols.

The infinity entity code being used is “∞” when it should be just “∞”, and the pi entity code being used is “@amp;pi;” when it should be just “π”.  The result is that currently the rendered HTML shows “@infin;” and “π” instead of “∞” and “π”.
Comment 1 Jonathan Wakely 2020-07-14 11:48:04 UTC
The https://www.gnu.org/software/libc/manual/html_node/Parsing-of-Floats.html page also has the ∞ entity in the description of strtod.
Comment 3 Florian Weimer 2020-07-15 06:42:39 UTC
Looks like a Texinfo regression/behavioral change. I'll see if I can fix this on the glibc side.
Comment 4 Florian Weimer 2020-07-15 07:06:51 UTC
Patch posted: https://sourceware.org/pipermail/libc-alpha/2020-July/116357.html
Comment 5 Florian Weimer 2020-07-16 08:18:31 UTC
Fixed in glibc 2.32:

commit da7d62b50396c8b6d67c1ba800a196e83e2ec469
Author: Florian Weimer <fweimer@redhat.com>
Date:   Thu Jul 16 10:17:31 2020 +0200

    manual: Use Unicode instead HTML entities for characters (bug 19737)
    
    Texinfo no longer treats arguments to @set in @ifhtml blocks as
    literal HTML, so the & in the entity references was encoded as
    @amp; in HTML.  Using the equivalent Unicode characters avoids
    this issue.
    
    Reviewed-by: Carlos O'Donell <carlos@redhat.com>
    Tested-by: Carlos O'Donell <carlos@redhat.com>