From: Gyan Doshi <ffmpeg@gyani.pro> To: ffmpeg-devel@ffmpeg.org Subject: Re: [FFmpeg-devel] [PATCH v2] lavc/libaribcaption: Fix mistake in document decoders.texi Date: Thu, 2 Nov 2023 01:21:09 +0530 Message-ID: <93eafd32-5cc6-49bc-9092-479b32d3066a@gyani.pro> (raw) In-Reply-To: <20231101152421.70296-1-xqq@xqq.im> On 2023-11-01 08:54 pm, zheng qian wrote: > Fix the mistake in the description of `-caption_encoding encoding_scheme` option. Will fix commit message and push. Thanks, Gyan > > Signed-off-by: zheng qian <xqq@xqq.im> > --- > doc/decoders.texi | 5 +---- > 1 file changed, 1 insertion(+), 4 deletions(-) > > diff --git a/doc/decoders.texi b/doc/decoders.texi > index eb00e2a9e9..f75364166e 100644 > --- a/doc/decoders.texi > +++ b/doc/decoders.texi > @@ -391,7 +391,7 @@ Specifies the encoding scheme of input subtitle text. > > @table @samp > @item auto > -Automatically detect text encoding. > +Automatically detect text encoding (default). > @item jis > 8bit-char JIS encoding defined in ARIB STD B24. > This encoding used in Japan for ISDB captions. > @@ -403,9 +403,6 @@ Latin character encoding defined in ABNT NBR 15606-1. > This encoding is used in South America for SBTVD / ISDB-Tb captions. > @end table > > -The default is @dfn{ass} as same as @dfn{libaribb24} decoder. > -Some present players (e.g., @dfn{mpv}) expect ASS format for ARIB caption. > - > @item -font @var{font_name[,font_name2,...]} > Specify comma-separated list of font family names to be used for @dfn{bitmap} > or @dfn{ass} type subtitle rendering. _______________________________________________ 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:[~2023-11-01 19:51 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-11-01 15:03 [FFmpeg-devel] [PATCH 0/1] Fix document mistake for lavc/libaribcaption zheng qian 2023-11-01 15:03 ` [FFmpeg-devel] [PATCH 1/1] lavc/libaribcaption: Fix mistake in document decoders.texi zheng qian 2023-11-01 15:13 ` Gyan Doshi 2023-11-01 15:24 ` [FFmpeg-devel] [PATCH v2] " zheng qian 2023-11-01 19:51 ` Gyan Doshi [this message] 2023-11-02 8:40 ` Gyan Doshi 2023-11-02 9:01 ` zheng qian
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=93eafd32-5cc6-49bc-9092-479b32d3066a@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