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: Thu, 4 Jan 2024 15:30:42 -0600
Message-ID: <CA+28BfCEm2j0Y3TW2d4ARXLraLA=9rp22Qjz6q4Rk5N3qsdNcA@mail.gmail.com> (raw)
In-Reply-To: <a4861578-7df2-4fe2-98b8-c401d4a98e01@betaapp.fastmail.com>

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

      reply	other threads:[~2024-01-04 21:31 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
2024-01-04  7:45     ` Jean-Baptiste Kempf
2024-01-04 21:30       ` Marth64 [this message]

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+28BfCEm2j0Y3TW2d4ARXLraLA=9rp22Qjz6q4Rk5N3qsdNcA@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