On Sun, 7 Jan 2024, Stefano Sabatini wrote:
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.
Hard to edit how? It is not like we are in the 80s using ASCII charset and
editors with 80x25 text console to edit the files...
The whole topic is kind of bikesheddy, so I don't really mind either way,
I just don't see the benefit of using @tie{} or whatever instead of proper
utf8 chars any half decent editor would support.
Regards,
Marton
_______________________________________________
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".
