From: Gyan Doshi <ffmpeg@gyani.pro>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [FFmpeg-cvslog] avfilter/vf_subtitles: add wrap_unicode option
Date: Thu, 25 May 2023 12:44:13 +0530
Message-ID: <25a9483e-91ed-4465-842a-ecb7e7e0eab3@gyani.pro> (raw)
In-Reply-To: <20230525033525.DE1754102A6@natalya.videolan.org>
On 2023-05-25 09:05 am, Zhao Zhili wrote:
> ffmpeg | branch: master | Zhao Zhili <zhilizhao@tencent.com> | Tue May 23 13:22:25 2023 +0800| [43ace8f2bc29faf335e31b9893e6b8928ba3f541] | committer: Zhao Zhili
>
> avfilter/vf_subtitles: add wrap_unicode option
>
> So CJK can be wrapped automatically.
>
> Signed-off-by: Zhao Zhili <zhilizhao@tencent.com>
>
>> http://git.videolan.org/gitweb.cgi/ffmpeg.git/?a=commit;h=43ace8f2bc29faf335e31b9893e6b8928ba3f541
> ---
>
> doc/filters.texi | 7 +++++++
> libavfilter/version.h | 2 +-
> libavfilter/vf_subtitles.c | 18 ++++++++++++++++++
> 3 files changed, 26 insertions(+), 1 deletion(-)
>
> diff --git a/doc/filters.texi b/doc/filters.texi
> index 76d9f11edc..6c5b61d763 100644
> --- a/doc/filters.texi
> +++ b/doc/filters.texi
> @@ -22440,6 +22440,13 @@ Set subtitles stream index. @code{subtitles} filter only.
> @item force_style
> Override default style or script info parameters of the subtitles. It accepts a
> string containing ASS style format @code{KEY=VALUE} couples separated by ",".
> +
> +@item wrap_unicode
> +Break lines according to the Unicode Line Breaking Algorithm. Only available
> +since libass version 0x01600010, and whether it's usable depends on the built
> +of libass.
Added details about version requirements in 944243477b
Regards,
Gyan
_______________________________________________
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:[~2023-05-25 7:14 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20230525033525.DE1754102A6@natalya.videolan.org>]
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=25a9483e-91ed-4465-842a-ecb7e7e0eab3@gyani.pro \
--to=ffmpeg@gyani.pro \
--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