From: AnandajithS via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: ffmpeg-devel@ffmpeg.org
Cc: AnandajithS <code@ffmpeg.org>
Subject: [FFmpeg-devel] [PR] avfilter/vf_drawtext: fix newline being shown as glyph (PR #21776)
Date: Tue, 17 Feb 2026 20:05:14 -0000
Message-ID: <177135871478.25.6926878858532365435@29965ddac10e> (raw)
PR #21776 opened by AnandajithS
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/21776
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/21776.patch
During processing, the newline character is included in the range
passed to shape_text_hb because the pointer representing the current
character is moved forward by GET_UTF8 macro before newline check,
which causes it to create a notdef glyph
This PR fixes the issue by adding a check condition in shape_text_hb
to exclude the newline character
Fixes #21565
Signed-off-by: AnandajithS <anandajiths2006@gmail.com>
>From 675631f6cde9447c8e206a3a4367fab636370329 Mon Sep 17 00:00:00 2001
From: AnandajithS <anandajiths2006@gmail.com>
Date: Wed, 18 Feb 2026 00:54:20 +0530
Subject: [PATCH] avfilter/vf_drawtext: fix newline being shown as glyph
During processing, the newline character is included in the range
passed to shape_text_hb because the pointer representing the current
character is moved forward by GET_UTF8 macro before newline check,
which causes it to create a notdef glyph
This PR fixes the issue by adding a check condition in shape_text_hb
to exclude the newline character
Signed-off-by: AnandajithS <anandajiths2006@gmail.com>
---
libavfilter/vf_drawtext.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/libavfilter/vf_drawtext.c b/libavfilter/vf_drawtext.c
index 2812de37f5..de6c61aea3 100644
--- a/libavfilter/vf_drawtext.c
+++ b/libavfilter/vf_drawtext.c
@@ -1458,7 +1458,7 @@ continue_on_failed2:
TextLine *cur_line = &s->lines[line_count];
HarfbuzzData *hb = &cur_line->hb_data;
cur_line->cluster_offset = line_offset;
- ret = shape_text_hb(s, hb, start, p - start);
+ ret = shape_text_hb(s, hb, start, p - start - (code?1:0));
if (ret != 0) {
goto done;
}
--
2.52.0
_______________________________________________
ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
To unsubscribe send an email to ffmpeg-devel-leave@ffmpeg.org
reply other threads:[~2026-02-17 20:05 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=177135871478.25.6926878858532365435@29965ddac10e \
--to=ffmpeg-devel@ffmpeg.org \
--cc=code@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