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

[Stefano Sabatini]

On date Saturday 2024-01-06 15:49:56 -0600, Marth64 wrote:
> This reverts commit 6442d1ddd62160e96c686c30648b6111e3e0c264.
> 
> A valid point was made, that the non-breaking space will cause this text
> to render better by ensuring the unit never seperates from the number.

I'm not convinced the non-breaking space was a good idea in the first
place, the fact that there is a single instance in the whole
documentation confirms this.

In fact even if the unit and value are not on the same line we don't
miss much in terms of readability.

On the other hand it is very hard to edit such non-printable
characters, and you can bet what as much as you can that most
contributors will not get it right or consistent.

> Signed-off-by: Marth64 <marth64 at proxyid.net>
> ---
>  doc/faq.texi | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/doc/faq.texi b/doc/faq.texi
> index 5998e0d000..39f28eef08 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 at ffmpeg.org
> https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
> 
> To unsubscribe, visit link above, or email
> ffmpeg-devel-request at ffmpeg.org with subject "unsubscribe".