Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Thilo Borgmann via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: ffmpeg-devel@ffmpeg.org
Cc: Thilo Borgmann <thilo.borgmann@mail.de>
Subject: Re: [FFmpeg-devel] [PATCH] Revert "doc/faq: replace non-breaking spaces (0xA0) with normal space"
Date: Sun, 7 Jan 2024 14:16:23 +0100
Message-ID: <72671e16-424f-416c-83ab-39d8c25ad230@mail.de> (raw)
In-Reply-To: <ZZqVQ+mxfTtqLIYe@mariano>

Am 07.01.24 um 13:12 schrieb 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.

I think we could use @tie{} instead of an invisible 0xA0 wherever we want non-breaking spaces.
Even if we seem not to care much about these in the docs.

-Thilo
_______________________________________________
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-07 13:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-06 21:49 Marth64
2024-01-07 12:12 ` Stefano Sabatini
2024-01-07 13:16   ` Thilo Borgmann via ffmpeg-devel [this message]
2024-01-07 14:36     ` Stefano Sabatini
2024-01-07 15:29     ` [FFmpeg-devel] [PATCH v2] doc/faq: Use texi's @tie instead of 0xA0 for non-breaking space Marth64
2024-01-08 19:46       ` Stefano Sabatini
2024-01-10 19:01         ` Stefano Sabatini
2024-01-07 18:46   ` [FFmpeg-devel] [PATCH] Revert "doc/faq: replace non-breaking spaces (0xA0) with normal space" Marton Balint
2024-01-07 18:51     ` James Almer

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=72671e16-424f-416c-83ab-39d8c25ad230@mail.de \
    --to=ffmpeg-devel@ffmpeg.org \
    --cc=thilo.borgmann@mail.de \
    /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