Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Marth64 <marth64@proxyid.net>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] doc/faq: replace non-breaking spaces (0xA0) with normal space
Date: Wed, 3 Jan 2024 16:21:18 -0600
Message-ID: <CA+28BfAr4yB-FOxJHmmaUMJBZBUYxLatAoUnvLmvm7sn3WwW_w@mail.gmail.com> (raw)
In-Reply-To: <87fe17f9-6bed-4986-ab03-fdb1c34cab55@betaapp.fastmail.com>

Hi,
I felt that it was strange in all of documentation, this is the only
scenario where 0xA0 is used for a space character instead of the ordinary
space 0x20. It is invisible when viewing in email or many IDE but in my
editor I was able to see the exact hex character was not a ordinary space
character.

The string currently is actually as follows under a hex lens:
(default ~5<0xA0>Mo) and @code{analyzeduration} (default 5,000,000<0xA0>µs
= 5<0xA0>s). For

So I wanted to make it consistent, and not have weird space characters when
not necessary

On Wed, Jan 3, 2024 at 4:12 PM Jean-Baptiste Kempf <jb@videolan.org> wrote:

> Why this change?
>
> On Wed, 3 Jan 2024, at 19:47, Marth64 wrote:
> > Signed-off-by: Marth64 <marth64@proxyid.net>
> > ---
> >  doc/faq.texi | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/doc/faq.texi b/doc/faq.texi
> > index 39f28eef08..5998e0d000 100644
> > --- a/doc/faq.texi
> > +++ b/doc/faq.texi
> > @@ -450,7 +450,7 @@ work with streams that were detected during the
> > initial scan; streams that
> >  are detected later are ignored.
> >
> >  The size of the initial scan is controlled by two options:
> @code{probesize}
> > -(default ~5 Mo) and @code{analyzeduration} (default 5,000,000 µs =
> 5 s). For
> > +(default ~5 Mo) and @code{analyzeduration} (default 5,000,000 µs = 5
> s). For
> >  the subtitle stream to be detected, both values must be large enough.
> >
> >  @section Why was the @command{ffmpeg} @option{-sameq} option removed?
> > What to use instead?
> > --
> > 2.34.1
> >
> > _______________________________________________
> > 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".
>
> --
> Jean-Baptiste Kempf -  President
> +33 672 704 734
> _______________________________________________
> 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".
>
_______________________________________________
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".

  reply	other threads:[~2024-01-03 22:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-03 18:47 Marth64
2024-01-03 22:11 ` Jean-Baptiste Kempf
2024-01-03 22:21   ` Marth64 [this message]
2024-01-04  7:45     ` Jean-Baptiste Kempf
2024-01-04 21:30       ` Marth64

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=CA+28BfAr4yB-FOxJHmmaUMJBZBUYxLatAoUnvLmvm7sn3WwW_w@mail.gmail.com \
    --to=marth64@proxyid.net \
    --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