From: Oneric <oneric@oneric.de>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH v4 2/4] avcodec/{ass, webvttdec}: fix handling of backslashes
Date: Thu, 4 Apr 2024 20:36:50 +0200
Message-ID: <Zg7zQhLokd0CDDev@oneric.de> (raw)
In-Reply-To: <CA+28BfCyxL7UVLQD36miPGfVaCsHuzxCuYFJDHjKAHhsVZ9+yA@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 741 bytes --]
On Thu, Apr 04, 2024 at 13:26:55 -0500, Marth64 wrote:
> > Is \N a special sequence in ASS-speak
> \N is the special line break sequence in ASS
>
> I’m not sure of other special sequences following the \ character, I yield
> to Oneric on this question.
Standard ASS(2) and SSAv4 have
\N (forced linebreak)
\n (linebreak hint)
\h (nonbreaking space)
libass further has \{ and \} dealt with by the following commit.
Afaik no ASS renderer ever supported \\.
The added escaping happens for non-ASS format (in which those sequences
are just normal text) which get encoded into ASS by ffmpeg. If it weren’t
escaped we’d get sudden linebreaks, spaces etc and missing text.
It doesn’t affect ASS->ASS remuxing.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 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".
next prev parent reply other threads:[~2024-04-04 18:37 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-19 21:42 [FFmpeg-devel] [PATCH v4 0/4] Fix some active sequences in subtitles Oneric
2024-02-19 21:42 ` [FFmpeg-devel] [PATCH v4 1/4] avcodec/webvttdec: honour bidi marks Oneric
2024-04-04 16:59 ` Stefano Sabatini
2024-02-19 21:42 ` [FFmpeg-devel] [PATCH v4 2/4] avcodec/{ass, webvttdec}: fix handling of backslashes Oneric
2024-04-04 17:44 ` Stefano Sabatini
2024-04-04 17:56 ` Marth64
2024-04-04 18:02 ` Stefano Sabatini
2024-04-04 18:26 ` Marth64
2024-04-04 18:36 ` Oneric [this message]
2024-04-04 21:53 ` Stefano Sabatini
2024-02-19 21:42 ` [FFmpeg-devel] [PATCH v4 3/4] avcodec/{ass, webvttdec}: more portable curly brace escapes Oneric
2024-04-04 17:48 ` Stefano Sabatini
2024-02-19 21:42 ` [FFmpeg-devel] [PATCH v4 4/4] avocdec/ass: simplify linebreaks Oneric
2024-04-04 17:50 ` Stefano Sabatini
2024-02-26 22:26 ` [FFmpeg-devel] [PATCH v4 0/4] Fix some active sequences in subtitles Oneric
2024-03-19 20:59 ` Marth64
2024-03-26 16:01 ` Marth64
2024-04-03 19:50 ` Oneric
2024-04-06 7:27 ` Stefano Sabatini
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=Zg7zQhLokd0CDDev@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