From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ffbox0-bg.mplayerhq.hu (ffbox0-bg.ffmpeg.org [79.124.17.100]) by master.gitmailbox.com (Postfix) with ESMTP id B821F47FFF for ; Sun, 7 Jan 2024 18:46:20 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id E638568CD11; Sun, 7 Jan 2024 20:46:17 +0200 (EET) Received: from iq.passwd.hu (iq.passwd.hu [217.27.212.140]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id E5E7968CBD2 for ; Sun, 7 Jan 2024 20:46:10 +0200 (EET) Received: from localhost (localhost [127.0.0.1]) by iq.passwd.hu (Postfix) with ESMTP id 6B177E8CAE for ; Sun, 7 Jan 2024 19:46:10 +0100 (CET) X-Virus-Scanned: amavisd-new at passwd.hu Received: from iq.passwd.hu ([127.0.0.1]) by localhost (iq.passwd.hu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rFdtgnXwVjL4 for ; Sun, 7 Jan 2024 19:46:05 +0100 (CET) Received: from iq (iq [217.27.212.140]) by iq.passwd.hu (Postfix) with ESMTPS id 224ABE89F2 for ; Sun, 7 Jan 2024 19:46:05 +0100 (CET) Date: Sun, 7 Jan 2024 19:46:05 +0100 (CET) From: Marton Balint To: FFmpeg development discussions and patches In-Reply-To: Message-ID: References: <20240106214955.1558448-1-marth64@proxyid.net> MIME-Version: 1.0 Subject: Re: [FFmpeg-devel] [PATCH] Revert "doc/faq: replace non-breaking spaces (0xA0) with normal space" X-BeenThere: ffmpeg-devel@ffmpeg.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: FFmpeg development discussions and patches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: FFmpeg development discussions and patches Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Errors-To: ffmpeg-devel-bounces@ffmpeg.org Sender: "ffmpeg-devel" Archived-At: List-Archive: List-Post: 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-request@ffmpeg.org with subject "unsubscribe".