[FFmpeg-devel] [PATCH] doc/faq: replace non-breaking spaces (0xA0) with normal space

[FFmpeg-devel] [PATCH] doc/faq: replace non-breaking spaces (0xA0) with normal space

[Marth64]

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

Re: [FFmpeg-devel] [PATCH] doc/faq: replace non-breaking spaces (0xA0) with normal space

[Jean-Baptiste Kempf]

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

Re: [FFmpeg-devel] [PATCH] doc/faq: replace non-breaking spaces (0xA0) with normal space

[Marth64]

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

Re: [FFmpeg-devel] [PATCH] doc/faq: replace non-breaking spaces (0xA0) with normal space

[Jean-Baptiste Kempf]

On Wed, 3 Jan 2024, at 23:21, Marth64 wrote:
> 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). 

IMHO, this was correct and should be used everywhere to avoid splitting a number from its unit in various part of the documentation.

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

Re: [FFmpeg-devel] [PATCH] doc/faq: replace non-breaking spaces (0xA0) with normal space

[Marth64]

I understand now and that makes sense. If no objections, I am happy to make
a patch to revert!


On Thu, Jan 4, 2024 at 1:46 AM Jean-Baptiste Kempf <jb@videolan.org> wrote:

>
>
> On Wed, 3 Jan 2024, at 23:21, Marth64 wrote:
> > 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).
>
> IMHO, this was correct and should be used everywhere to avoid splitting a
> number from its unit in various part of the documentation.
>
> —
> 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".