Date: Tue, 9 Jul 2013 15:42:49 -0600 (MDT) From: Warren Block <wblock@wonkity.com> To: Gabor Kovesdan <gabor@FreeBSD.org> Cc: svn-doc-head@freebsd.org, svn-doc-all@freebsd.org, doc-committers@freebsd.org, Warren Block <wblock@freebsd.org> Subject: Re: svn commit: r42201 - head/en_US.ISO8859-1/books/fdp-primer/docbook-markup Message-ID: <alpine.BSF.2.00.1307091541060.46436@wonkity.com> In-Reply-To: <51DC7984.4080106@FreeBSD.org> References: <201307090627.r696RuOg076372@svn.freebsd.org> <alpine.GSO.1.10.1307091512330.26275@multics.mit.edu> <51DC7984.4080106@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 9 Jul 2013, Gabor Kovesdan wrote: > Em 09-07-2013 21:13, Benjamin Kaduk escreveu: >>> Remove a confusing paragraph whose net contribution is negative. Remove >>> some from "Ports Collection", it's unnecessary. Make one example >> >> Was this discussed anywhere? I am seeing a pretty long precedent for the >> non-breaking space. > Indeed it wasn't discussed but I think that these non-breaking spaces should > be reconsidered. I had added the to the Ports Collection in the word list very recently, then saw that it really made no sense to force those two words to be on the same line. > Typography rules and conventions are language-dependent. For example, in > Hungarian it is not nice to end a line with a sentence-starting single-letter > article. Afaik, English does not have such rules, except widows and orphans, > which are more concerned with aesthetics. It is reasonable to avoid a line > break between FreeBSD and 9.X or similar cases but probably not for such long > terms as Ports Collection. Actually, it may just hit back because it may make > justified paragraphs very ugly in our print formats. Exactly.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.1307091541060.46436>