public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug other/11146] Bad characters can happen in cpp.1, gcc.1 man pages
[not found] <bug-11146-4@http.gcc.gnu.org/bugzilla/>
@ 2022-01-07 7:35 ` pinskia at gcc dot gnu.org
2022-01-07 7:52 ` pinskia at gcc dot gnu.org
1 sibling, 0 replies; 5+ messages in thread
From: pinskia at gcc dot gnu.org @ 2022-01-07 7:35 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=11146
--- Comment #8 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
So we were doing:
Define the macros @sc{__gnuc__}, @sc{__gnuc_minor__}
Where texi2pod.pl does:
s/\@sc\{([^\}]*)\}/\U$1/g;
Which should be fine. It should have replaced @sc{__gnuc__} with __GNUC__.
We do now:
cpp.texi:defines @code{__GNUC__} to @var{x}, @code{__GNUC_MINOR__} to @var{y},
texi2pod.pl does this for @code:
s/\@(?:code|kbd)\{([^\}]*)\}/C<$1>/g;
Note @sc is defined at:
https://www.gnu.org/software/texinfo/manual/texinfo/html_node/Smallcaps.html
I suspect this was a pod2man bug, looking into the perl source base to find
when the fix was included. There was some __ replacement rules in pod2man in
the recent versions of perl.
^ permalink raw reply [flat|nested] 5+ messages in thread* [Bug other/11146] Bad characters can happen in cpp.1, gcc.1 man pages
[not found] <bug-11146-4@http.gcc.gnu.org/bugzilla/>
2022-01-07 7:35 ` [Bug other/11146] Bad characters can happen in cpp.1, gcc.1 man pages pinskia at gcc dot gnu.org
@ 2022-01-07 7:52 ` pinskia at gcc dot gnu.org
1 sibling, 0 replies; 5+ messages in thread
From: pinskia at gcc dot gnu.org @ 2022-01-07 7:52 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=11146
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |MOVED
--- Comment #9 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
podlators 2.1.0 (2008-06-01)
Add a new utf8 option to Pod::Man. If set, do not convert non-ASCII
characters to *roff escapes or X, and instead output literal UTF-8
characters. Add a new --utf8 option to pod2man.
[Pod::Man] Match text between \f(CW and \fP or \fR in headings
non-greedily to get the fonts right with multiple C<> formatting
codes.
[Pod::Man] Protect .Sh text against leading *roff control characters
since some *roff implementations apparently "look through" font
escapes at the beginning of lines.
[Pod::Man] Escape backslashes separately from processing non-ASCII
characters and do that, dash escaping, and underscore adjustment
before processing non-ASCII characters. Otherwise, we escape the
hyphen in eth characters.
This was a bug in pod2man which was fixed in 2008 I think. Anyways I can't
reproduce the original bug with the even the original .texi code back in which
is why I am suspecting it was a pod2man issue.
^ permalink raw reply [flat|nested] 5+ messages in thread
[parent not found: <bug-11146-2447@http.gcc.gnu.org/bugzilla/>]
* [Bug other/11146] New: Bad characters in cpp.1, gcc.1 man pages
@ 2003-06-11 3:10 drk@sgi.com
2003-10-26 22:00 ` [Bug other/11146] Bad characters can happen " pinskia at gcc dot gnu dot org
0 siblings, 1 reply; 5+ messages in thread
From: drk@sgi.com @ 2003-06-11 3:10 UTC (permalink / raw)
To: gcc-bugs
PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11146
Summary: Bad characters in cpp.1, gcc.1 man pages
Product: gcc
Version: 3.3
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: other
AssignedTo: unassigned@gcc.gnu.org
ReportedBy: drk@sgi.com
CC: gcc-bugs@gcc.gnu.org
The gcc/3.3 tarball has corrupted cpp.1 and gcc.1 man
pages. If you check, there are a couple NULL characters
(and some other garbage) where the __GNUC_MINOR__ macro
should be.
^ permalink raw reply [flat|nested] 5+ messages in thread* [Bug other/11146] Bad characters can happen in cpp.1, gcc.1 man pages
2003-06-11 3:10 [Bug other/11146] New: Bad characters " drk@sgi.com
@ 2003-10-26 22:00 ` pinskia at gcc dot gnu dot org
0 siblings, 0 replies; 5+ messages in thread
From: pinskia at gcc dot gnu dot org @ 2003-10-26 22:00 UTC (permalink / raw)
To: gcc-bugs
PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11146
pinskia at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|[3.3 regression] Bad |Bad characters can happen in
|characters in cpp.1, gcc.1 |cpp.1, gcc.1 man pages
|man pages |
Target Milestone|3.3.3 |---
------- Additional Comments From pinskia at gcc dot gnu dot org 2003-10-26 21:48 -------
Since this is no longer a regression moving changing the target milestone.
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2022-01-07 7:52 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <bug-11146-4@http.gcc.gnu.org/bugzilla/>
2022-01-07 7:35 ` [Bug other/11146] Bad characters can happen in cpp.1, gcc.1 man pages pinskia at gcc dot gnu.org
2022-01-07 7:52 ` pinskia at gcc dot gnu.org
[not found] <bug-11146-2447@http.gcc.gnu.org/bugzilla/>
2008-02-01 3:50 ` bje at gcc dot gnu dot org
2008-02-01 4:12 ` bje at gcc dot gnu dot org
2003-06-11 3:10 [Bug other/11146] New: Bad characters " drk@sgi.com
2003-10-26 22:00 ` [Bug other/11146] Bad characters can happen " pinskia at gcc dot gnu dot org
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).