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