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 <j...@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-requ...@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-requ...@ffmpeg.org with subject "unsubscribe".
