From: Mike Frysinger <vapier@gentoo.org>
To: newlib@sourceware.org
Subject: [PATCH 07/12] texi2pod.pl: import support for @t{...} from gcc
Date: Tue, 9 Nov 2021 19:14:26 -0500 [thread overview]
Message-ID: <20211110001431.2212-8-vapier@gentoo.org> (raw)
In-Reply-To: <20211110001431.2212-1-vapier@gentoo.org>
From: Simon Marchi <simon.marchi@polymtl.ca>
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.
---
etc/ChangeLog | 4 ++++
etc/texi2pod.pl | 1 +
2 files changed, 5 insertions(+)
diff --git a/etc/ChangeLog b/etc/ChangeLog
index 78e9366e349a..8742e2afc15d 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 b0540338c8ec..8d92bcf6023b 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;
--
2.33.0
next prev parent reply other threads:[~2021-11-10 0:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-10 0:14 [PATCH 00/12] sync etc/ to bfd/gdb tree Mike Frysinger
2021-11-10 0:14 ` [PATCH 01/12] Fix compile time warning messages building with gcc v6.1.1 Mike Frysinger
2021-11-10 0:14 ` [PATCH 02/12] update-copyright.py for binutils Mike Frysinger
2021-11-10 0:14 ` [PATCH 03/12] Update the address of the FSF in the copyright notice of files which were using the old address Mike Frysinger
2021-11-10 0:14 ` [PATCH 04/12] Update year range in copyright notice of binutils files Mike Frysinger
2021-11-10 0:14 ` [PATCH 05/12] Bump to autoconf 2.69 and automake 1.15.1 Mike Frysinger
2021-11-10 0:14 ` [PATCH 06/12] Update year range in copyright notice of binutils files Mike Frysinger
2021-11-10 0:14 ` Mike Frysinger [this message]
2021-11-10 0:14 ` [PATCH 08/12] Add libctf to update-copyright.py Mike Frysinger
2021-11-10 0:14 ` [PATCH 09/12] Update year range in copyright notice of binutils files Mike Frysinger
2021-11-10 0:14 ` [PATCH 10/12] texi2pod.pl: add no-op --no-split option support [PR28144] Mike Frysinger
2021-11-10 0:14 ` [PATCH 11/12] etc: rename configure.in to configure.ac Mike Frysinger
2021-11-10 0:14 ` [PATCH 12/12] etc: switch to automake Mike Frysinger
2021-11-10 10:54 ` [PATCH 00/12] sync etc/ to bfd/gdb tree Corinna Vinschen
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=20211110001431.2212-8-vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=newlib@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: 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).