public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/27832]  New: texi2pod issues
Date: Wed, 31 May 2006 09:33:00 -0000	[thread overview]
Message-ID: <bug-27832-87@http.gcc.gnu.org/bugzilla/> (raw)

The generated gcc.1 man page contais a couple of weird texinfo artefacts,
I suppose the problem is in texi2pod.pl in most cases, but am not 100% sure.
1) @anchor{something} doesn't seem to be handled and makes it all the way
   through into the man page (should it be just nuked for the man page?)
   E.g. in:
       -Wtrigraphs
           @anchor{Wtrigraphs} Most trigraphs in comments cannot affect the
meaning of the program.  However, a
2) @pxref{something} makes it all the way through into the man page too
   E.g. in:
       -Wno-deprecated-declarations
           Do not warn about uses of functions, variables, and types marked as
deprecated by using the "deprecated"
           attribute.  (@pxref{Function Attributes}, @pxref{Variable
Attributes}, @pxref{Type Attributes}.)
3) @item is only handled at the beginning of line, so we have
            @item max-inline-insns-single
             is set to I<n>/2.
            @item max-inline-insns-auto
             is set to I<n>/2.
            @item min-inline-insns
             is set to 130 or I<n>/4, whichever is smaller.
            @item max-inline-insns-rtl
             is set to I<n>.
   Perhaps this should be solved by removing the spaces in invoke.texi.
4) @samp{@@} in the texi source is transformed weirdly:
@samp{;}, and each switch starts with an @samp{@@} instead of the
@samp{-}, without spaces between multiple switches.  This is supposed to
ease shell-processing.
becomes in gcc.pod:
B<;>, and each switch starts with an B<@} instead of the
@samp{->, without spaces between multiple switches.  This is supposed to
ease shell-processing.


-- 
           Summary: texi2pod issues
           Product: gcc
           Version: 4.1.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: other
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: jakub at gcc dot gnu dot org


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27832


             reply	other threads:[~2006-05-31  9:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-31  9:33 jakub at gcc dot gnu dot org [this message]
2006-08-25  4:53 ` [Bug other/27832] " pinskia at gcc dot gnu dot org
2006-09-03  5:34 ` pinskia at gcc dot gnu dot org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-27832-87@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).