public inbox for cygwin-cvs@sourceware.org help / color / mirror / Atom feed
From: Michael Frysinger <vapier@sourceware.org> To: cygwin-cvs@sourceware.org, newlib-cvs@sourceware.org Subject: [newlib-cygwin] texi2pod.pl: import support for @t{...} from gcc Date: Thu, 11 Nov 2021 01:16:10 +0000 (GMT) [thread overview] Message-ID: <20211111011610.35EC73858435@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=newlib-cygwin.git;h=957f0a864a624a98d3fa220ffb4b7030cd261505 commit 957f0a864a624a98d3fa220ffb4b7030cd261505 Author: Simon Marchi <simon.marchi@polymtl.ca> Date: Wed Jan 15 12:58:08 2020 -0500 texi2pod.pl: import support for @t{...} from gcc GDB's man page source (in gdb.texinfo) contains: @t{++} The @t{...} part is supposed to display the wrapped text with a fixed-width font. The texi2pod.pl script currently doesn't handle @t{...}, so it appears as-is in the man page: You can use GDB to debug programs written in C, C@t{++}, Fortran and Modula-2. gcc's version of texi2pod.pl (at contrib/texi2pod.pl in gcc's repo) replaces @t{...} with the wrapped text as-is, which I think is an acceptable behavior. The fixed-width font distinction is not really important for a man page, where the text will be displayed with whatever font the user is using. Import the line that does that from gcc's version. I have verified that there is no other, unwanted change in man pages generated in binutils' and GDB's doc, with this patch applied. etc/ChangeLog: * texi2pod.pl: Handle @t{...} tags. Diff: --- etc/ChangeLog | 4 ++++ etc/texi2pod.pl | 1 + 2 files changed, 5 insertions(+) diff --git a/etc/ChangeLog b/etc/ChangeLog index 78e9366e3..8742e2afc 100644 --- a/etc/ChangeLog +++ b/etc/ChangeLog @@ -1,3 +1,7 @@ +2020-01-15 Simon Marchi <simon.marchi@polymtl.ca> + + * texi2pod.pl: Handle @t{...} tags. + 2018-06-19 Simon Marchi <simon.marchi@ericsson.com> * configure.in: Remove AC_PREREQ. diff --git a/etc/texi2pod.pl b/etc/texi2pod.pl index b0540338c..8d92bcf60 100644 --- a/etc/texi2pod.pl +++ b/etc/texi2pod.pl @@ -381,6 +381,7 @@ sub postprocess s/\@file\{([^\}]*)\}/F<$1>/g; s/\@w\{([^\}]*)\}/S<$1>/g; s/\@(?:dmn|math)\{([^\}]*)\}/$1/g; + s/\@t\{([^\}]*)\}/$1/g; # keep references of the form @ref{...}, print them bold s/\@(?:ref)\{([^\}]*)\}/B<$1>/g;
reply other threads:[~2021-11-11 1:16 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20211111011610.35EC73858435@sourceware.org \ --to=vapier@sourceware.org \ --cc=cygwin-cvs@sourceware.org \ --cc=newlib-cvs@sourceware.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: linkBe 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).