From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:37340) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eXwJy-0001es-3b for guix-patches@gnu.org; Sat, 06 Jan 2018 16:48:07 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eXwJu-0002MZ-3d for guix-patches@gnu.org; Sat, 06 Jan 2018 16:48:06 -0500 Received: from debbugs.gnu.org ([208.118.235.43]:58068) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1eXwJu-0002MU-06 for guix-patches@gnu.org; Sat, 06 Jan 2018 16:48:02 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1eXwJt-000852-N5 for guix-patches@gnu.org; Sat, 06 Jan 2018 16:48:01 -0500 Subject: [bug#29943] [PATCH] doc: Describe Wayland status. Resent-Message-ID: From: ludo@gnu.org (Ludovic =?UTF-8?Q?Court=C3=A8s?=) References: <20180102131851.6dde5704@mykolab.com> <87608ft6lt.fsf@gnu.org> <20180106144308.bvkqqsp6vhj3d377@abyayala> <87h8rysouh.fsf@gnu.org> <87r2r2ekib.fsf@gmail.com> Date: Sat, 06 Jan 2018 22:47:42 +0100 In-Reply-To: <87r2r2ekib.fsf@gmail.com> (Maxim Cournoyer's message of "Sat, 06 Jan 2018 16:37:48 -0500") Message-ID: <87608eslq9.fsf@gnu.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-patches-bounces+kyle=kyleam.com@gnu.org Sender: "Guix-patches" To: Maxim Cournoyer Cc: 29943@debbugs.gnu.org, Rutger Helling Hi Maxim, Maxim Cournoyer skribis: > ludo@gnu.org (Ludovic Court=C3=A8s) writes: [...] >>> Under which conditions does this result in non-proper rendering? >>> It's certainly not a Tex issue from what I can tell. So far I assumed i= t's just a convention >>> because in some countries this is the default and in some not. >>> I think we have a very short explanation in the Manual, but this never = really >>> explained why or what could go wrong. Maybe we could extend that. >> >> It=E2=80=99s a convention notably followed by Emacs=E2=80=99s =E2=80=98f= orward-sentence=E2=80=99 >> function, and also a Texinfo thing (info "(texinfo) Not Ending a >> Sentence"). >> >> Hmm actually the Texinfo manual now suggests the opposite (i.e., that it >> needs help only for non-end-of-sentence spacing), but I wonder if it=E2= =80=99s >> accurate. >> >> Ludo=E2=80=99. > > The old texinfo section that touched that subject was the "Multiple > Spaces" node[0]: > > Ordinarily, TeX collapses multiple whitespace characters (space, > tab, and newline) into a single space. (Info output, on the other > hand, preserves whitespace as you type it, except for changing a > newline into a space; this is why it is important to put two > spaces at the end of sentences in Texinfo documents.) > > The current version of the Texinfo manual indeed drops this advice and > includes a new section "12.3.4 '@frenchspacing' VAL: Control Sentence > Spacing" where we can learn about a setting that controls the appearance = of > the end of sentence spacing in the *output* of Info. > > It seems that at this point the only reason to keep this convention is > to accommodate Emacs, where the variable `sentence-end-double-space' is > true by default and means that[1]: > > [...] a period followed by just one space does not count as the end o= f a > sentence, and the filling functions avoid breaking the line at such > a place. > > A justification for this is written in the Emacs manual[2]: > > If you want to use just one space between sentences, you can set the > variable =E2=80=98sentence-end-double-space=E2=80=99 to =E2=80=98nil= =E2=80=99 to make the sentence > commands stop for single spaces. However, this has a drawback: > there is no way to distinguish between periods that end sentences > and those that indicate abbreviations. For convenient and reliable > editing, we therefore recommend you follow the two-space convention. > The variable =E2=80=98sentence-end-double-space=E2=80=99 also affects= filling (*note > Fill Commands::). > > [0] https://docs.freebsd.org/info/texinfo/texinfo.info.Multiple_Spaces.h= tml > [1] (elisp)Standard Regexps > [2] (emacs)Sentences Excellent, thanks for explaining! I pretty much agree with the Emacs explanation for that convention, but I admit this is often surprising to newcomers. Ludo=E2=80=99.