From: TADANO Tokumei <aimingoff@pc.nifty.jp>
To: ffmpeg-devel@ffmpeg.org
Cc: TADANO Tokumei <aimingoff@pc.nifty.jp>
Subject: [FFmpeg-devel] [PATCH v4 0/3] lavc/libaribcaption.c: add MSZ characters related options
Date: Tue, 17 Oct 2023 22:13:32 +0900
Message-ID: <20231017131335.201277-1-aimingoff@pc.nifty.jp> (raw)
Re-send the patchset.
The patches are same as v3, but its thread were corrupted.
-----
This patch add MSZ (Middle Size; half width) characters related
options and some fixes.
As Jan suggested to PATCH v2, I split it into 3 patches, drop `#if`s, and
bump required libaribcaption version to 1.1.1 (author preferred version).
TADANO Tokumei (3):
lavc/libaribcaption.c: FIX: change all `boot` option var to `int`
lavc/libaribcaption.c: add MSZ characters related options
lavc/libaribcaption.c: rename `-replace_fullwidth_ascii` option
configure | 2 +-
doc/decoders.texi | 28 ++++++++++++++++++++++------
libavcodec/libaribcaption.c | 28 +++++++++++++++++++---------
3 files changed, 42 insertions(+), 16 deletions(-)
--
2.39.2
_______________________________________________
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".
next reply other threads:[~2023-10-17 13:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-17 13:13 TADANO Tokumei [this message]
2023-10-17 13:13 ` [FFmpeg-devel] [PATCH v4 1/3] lavc/libaribcaption.c: FIX: change all `boot` option var to `int` TADANO Tokumei
2023-10-29 8:46 ` Jan Ekström
2023-10-17 13:13 ` [FFmpeg-devel] [PATCH v4 2/3] lavc/libaribcaption.c: add MSZ characters related options TADANO Tokumei
2023-10-29 8:51 ` Jan Ekström
2023-10-29 16:23 ` Jan Ekström
2023-10-17 13:13 ` [FFmpeg-devel] [PATCH v4 3/3] lavc/libaribcaption.c: rename `-replace_fullwidth_ascii` option TADANO Tokumei
2023-10-29 8:53 ` Jan Ekström
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=20231017131335.201277-1-aimingoff@pc.nifty.jp \
--to=aimingoff@pc.nifty.jp \
--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