From: Stefano Sabatini <stefasab@gmail.com>
To: FFmpeg development discussions and patches
<ffmpeg-devel@ffmpeg.org>, Frank Plowman <post@frankplowman.com>
Subject: Re: [FFmpeg-devel] [PATCH] doc/t2h: Support texinfo 7.0
Date: Tue, 7 Nov 2023 00:38:10 +0100
Message-ID: <ZUl44r+GpFuL20t+@mariano> (raw)
In-Reply-To: <ZUl4blLofYbivXi8@mariano>
On date Tuesday 2023-11-07 00:36:14 +0100, Stefano Sabatini wrote:
> On date Sunday 2023-11-05 13:53:38 +0000, post@frankplowman.com wrote:
> > From: Frank Plowman <post@frankplowman.com>
> >
> > Texinfo 7.0, released in November 2022, changed the names of various
> > functions. Compiling docs with Texinfo 7.0 results in warnings and
> > improperly formatted documentation. More old names appear to have
> > been removed in Texinfo 7.1, released October 2023, which causes docs
> > compilation to fail.
> >
> > This PR addresses the issue by adding logic to switch between the old
> > and new function names depending on the Texinfo version.
> >
> > CC
> > https://www.mail-archive.com/debian-bugs-dist@lists.debian.org/msg1938238.html
> > https://bugs.gentoo.org/916104
> >
> > Signed-off-by: Frank Plowman <post@frankplowman.com>
> > ---
> > doc/t2h.pm | 97 +++++++++++++++++++++++++++++++++++++++++++-----------
> > 1 file changed, 78 insertions(+), 19 deletions(-)
> >
> > diff --git a/doc/t2h.pm b/doc/t2h.pm
> > index d07d974286..1f23083703 100644
> > --- a/doc/t2h.pm
> > +++ b/doc/t2h.pm
> [...]
> > @@ -112,8 +145,8 @@ sub ffmpeg_heading_command($$$$$)
> > $cmdname
> > = $Texinfo::Common::level_to_structuring_command{$cmdname}->[$heading_level];
> > }
>
> > - $result .= &{$self->{'format_heading_text'}}(
> > - $self, $cmdname, $heading,
> > + $result .= &{get_formatting_function($self,'format_heading_text')}(
>
> > + $self, $cmdname, [$heading],
>
> Are the added [] intended? This is causing rendering of titles as
> ARRAYXNNNNN (as Perl is trying to render a dictionary with its address
Here I meant array in place of dictionary.
> in place of a string element). Dropping the [] fixes the issue.
I tested with makeinfo 6.8.
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
prev parent reply other threads:[~2023-11-06 23:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-05 13:53 post
2023-11-05 21:01 ` Stefano Sabatini
2023-11-06 17:31 ` Frank Plowman
2023-11-06 18:18 ` Gyan Doshi
2023-11-06 23:36 ` Stefano Sabatini
2023-11-06 23:38 ` Stefano Sabatini [this message]
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=ZUl44r+GpFuL20t+@mariano \
--to=stefasab@gmail.com \
--cc=ffmpeg-devel@ffmpeg.org \
--cc=post@frankplowman.com \
/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
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
This inbox may be cloned and mirrored by anyone:
git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
ffmpegdev@gitmailbox.com
public-inbox-index ffmpegdev
Example config snippet for mirrors.
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git