From: James Almer <jamrial@gmail.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH] doc/t2h: Support texinfo 7.1 and 7.2 pretest
Date: Tue, 21 Jan 2025 00:20:20 -0300
Message-ID: <7ff87601-fae6-41d2-859d-30212b89d1a9@gmail.com> (raw)
In-Reply-To: <ZyTsQ9ZtCcARGh14@free.fr>
[-- Attachment #1.1.1: Type: text/plain, Size: 1303 bytes --]
On 11/1/2024 11:57 AM, Patrice Dumas wrote:
>
> Here is a proposed patch for portability of doc/t2h.pm for GNU Texinfo
> 7.1 and 7.1.90 (7.2 pretest). I tested against 7.1 and 7.1.90 (7.2
> pretest). There is a difference in the headings compared to the website
> version, maybe related to FA_ICONS not being set the same, but the
> result seems correct.
>
> I also renamed $element to $output_unit in ffmpeg_heading_command as in
> new equivalent makeinfo/texi2any code the $element variable is the
> $command variable in ffmpeg_heading_command, which is very confusing. I
> left as is the $command variable to have a patch easier to read, but it
> could make sense to rename $command as $element later on.
>
> The patch could also have effects with Texinfo 7.0, since some of the
> changes are for that version, but that probably never show up because it
> is for situations that may not exist in ffmpeg manuals (for example
> @node without sectioning command), or because the code is robust to some
> missing information (case of $heading_level in ffmpeg_heading_command
> that was not set, as far as I can tell).
>
> ---
> doc/t2h.pm | 169 ++++++++++++++++++++++++++++++++++++++++-------------
> 1 file changed, 129 insertions(+), 40 deletions(-)
Will apply.
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]
[-- Attachment #2: Type: text/plain, Size: 251 bytes --]
_______________________________________________
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".
parent reply other threads:[~2025-01-21 3:20 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <ZyTsQ9ZtCcARGh14@free.fr>]
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=7ff87601-fae6-41d2-859d-30212b89d1a9@gmail.com \
--to=jamrial@gmail.com \
--cc=ffmpeg-devel@ffmpeg.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
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