From: Oneric <oneric@oneric.de>
To: ffmpeg-devel@ffmpeg.org
Subject: [FFmpeg-devel] [PATCH v3 0/4] Fix some active sequences in subtitles
Date: Mon, 12 Feb 2024 03:01:55 +0100
Message-ID: <20240212020159.6806-1-oneric@oneric.de> (raw)
Changes from v2:
- rebased ontop of the recently pushed eol normalisation.
As a result no more CRLFs in here and Patchwork should be happy
- added a fourth cosmetic commit adjusting
explicit linebreaks to the new normalisation
Changes from v1:
- ff_ass_bprint_text_event now only inserts a word-joiner
if there isn’t already one anyway
- added a third commit improving the handling of
curly brackets for standard ASS renderers
Oneric (4):
avcodec/webvttdec: honour bidi marks
avcodec/{ass,webvttdec}: fix handling of backslashes
avcodec/{ass,webvttdec}: more portable curly brace escapes
avocdec/ass: simplify linebreaks
libavcodec/ass.c | 47 +++++++++++++++++++++++---------------
libavcodec/webvttdec.c | 4 ++--
tests/ref/fate/sub-webvtt | 2 +-
tests/ref/fate/sub-webvtt2 | 2 +-
4 files changed, 33 insertions(+), 22 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:[~2024-02-12 2:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-12 2:01 Oneric [this message]
2024-02-12 2:01 ` [FFmpeg-devel] [PATCH v3 1/4] avcodec/webvttdec: honour bidi marks Oneric
2024-02-12 2:01 ` [FFmpeg-devel] [PATCH v3 2/4] avcodec/{ass, webvttdec}: fix handling of backslashes Oneric
2024-02-12 2:01 ` [FFmpeg-devel] [PATCH v3 3/4] avcodec/{ass, webvttdec}: more portable curly brace escapes Oneric
2024-02-12 2:01 ` [FFmpeg-devel] [PATCH v3 4/4] avocdec/ass: simplify linebreaks Oneric
2024-03-11 16:41 ` Marth64
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=20240212020159.6806-1-oneric@oneric.de \
--to=oneric@oneric.de \
--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