Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Nicolas George <george@nsup.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] proposal for a minor change in the behavior of the drawtext filter
Date: Sun, 24 Apr 2022 12:07:09 +0200
Message-ID: <YmUhTUSJlofacoSv@phare.normalesup.org> (raw)
In-Reply-To: <291427c1-9428-3895-da3e-0de5ca2fba0f@tiscali.it>


[-- Attachment #1.1: Type: text/plain, Size: 2332 bytes --]

Francesco Carusi (12022-04-22):
> I'm working on an enhanced version of the drawtext filter and would like to
> discuss with you about a minor change in its behavior related to line
> spacing management.
> In the current implementation the space between two lines of text is set
> equal to the height of the highest glyph found in the text plus the optional
> user defined "line_spacing" parameter (which defaults to 0):
> 
> line_height = max_glyph_h + line_spacing
> 
> This has some drawbacks:
> 1) the line height depends on the text
>     See image "line_height-old.png" (the blue lines where added by me)
>     The filter is applied three times with tree slightly different texts:
> the line_spacing parameter was not specified,
>     but the actual line height changes due to the different heights of the
> glyphs
> 2) the line height is not consistent between the same text being rendered by
> the filter and by external tools
> 
> The proposed change is:
> 1) the default line height is set to the font-defined line height
> 2) the line_spacing parameter, if specified, sets the actual line height
> (line_height = line_spacing)
> 3) the default value of line_spacing is set to -1 (which means: use the
> default line height)
> 
> The image "line_height-new.png" shows the effect of the new behavior.
> 
> Which is the impact of the change?
> A) users using the line_spacing parameter would see less space between lines
> B) users not using the line_spacing parameter would see (in most cases) more
> space between lines
> 
> Can the impact be mitigated?
> Well, yes, we may add a new parameter named 'line_height' and deprecate
> 'line_spacing', in this way anyone using line_spacing explicitly would not
> see any change in the filter behavior. I don't like this solution but it may
> help reducing the impact of the change.

Hi. While your proposal shows merit in itself, it also feels like the
first towards re-inventing a layout engine. The problem with line
spacing is the tiniest of drawtext problems: look for right-to-left,
ligatures and so much more.

If you want to enhance the output of drawtext, I think it would be more
efficient to choose a good layout engine library, Libre and portable,
and to make it use it optionally.

Regards,

-- 
  Nicolas George

[-- 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".

  parent reply	other threads:[~2022-04-24 10:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-22 10:01 Francesco Carusi
2022-04-22 10:30 ` Michael Niedermayer
2022-04-22 12:48   ` Francesco Carusi
2022-04-22 13:22     ` Michael Koch
2022-04-22 15:07       ` Francesco Carusi
2022-04-22 15:57         ` Michael Koch
2022-04-24 10:07 ` Nicolas George [this message]
2022-04-26 10:15   ` Francesco Carusi

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=YmUhTUSJlofacoSv@phare.normalesup.org \
    --to=george@nsup.org \
    --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