From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id C6E37138010 for ; Sat, 20 Oct 2012 14:33:22 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 4276921C054; Sat, 20 Oct 2012 14:33:14 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by pigeon.gentoo.org (Postfix) with ESMTP id 3535A21C046 for ; Sat, 20 Oct 2012 14:32:43 +0000 (UTC) Received: from [192.168.1.33] (230.Red-2-137-43.dynamicIP.rima-tde.net [2.137.43.230]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: pacho) by smtp.gentoo.org (Postfix) with ESMTPSA id A572633D78E for ; Sat, 20 Oct 2012 14:32:40 +0000 (UTC) Subject: Re: [gentoo-dev] About DESCRIPTION in ebuilds needing to end with a dot "." From: Pacho Ramos To: gentoo-dev@lists.gentoo.org In-Reply-To: <20121020142705.15162.qmail@stuge.se> References: <1350673317.12879.30.camel@belkin4> <20121019223736.33f2ee38@pomiocik.lan> <1350713353.12879.57.camel@belkin4> <20121020142705.15162.qmail@stuge.se> Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-Mc4rofKMqh9S9v3QLlg9" Date: Sat, 20 Oct 2012 16:32:36 +0200 Message-ID: <1350743556.12879.71.camel@belkin4> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org Mime-Version: 1.0 X-Mailer: Evolution 2.32.3 X-Archives-Salt: 320c8b08-da8b-4700-a0de-a03ce13c09ad X-Archives-Hash: 6205ab239cee405486329dcfebdaf626 --=-Mc4rofKMqh9S9v3QLlg9 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable El s=C3=A1b, 20-10-2012 a las 16:27 +0200, Peter Stuge escribi=C3=B3: > Pacho Ramos wrote: > > > So, rephrasing the example Alexandre pasted, consider: > > >=20 > > > x11-libs/qt-core - The Qt toolkit is a comprehensive C++ application > > > development framework. > > >=20 > > > vs. > > >=20 > > > x11-libs/qt-core - A comprehensive C++ application development framew= ork > > >=20 > > > Which one is better, in your opinion? > >=20 > > Well, I my case I would prefer second >=20 > I agree, I also like the second example. >=20 >=20 > > sentence... >=20 > http://en.wikipedia.org/wiki/Sentence_(linguistics)#Major_and_minor_sente= nces >=20 > Suggests that even a phrase such as the second example above can be > called a (minor) sentence. >=20 >=20 > > but it would still end with a dot. >=20 > I think that looks ugly and is redundant. >=20 > Especially if we were to require that all DESCRIPTION phrases must > always be presented with a full stop, I think it is a very bad idea > to enforce that they are written into the ebuilds. Especially if > there is a rule that they will always be terminated by a full stop > then that should and must be added by tools using the ebuild. >=20 > It makes absolutely no sense to have so frequent redundant data in > ebuilds, and it seems like full stop or no full stop is a matter of > presentation policy and should thus happen during presentation. >=20 >=20 > > But if it sounds rare for you, no problem. >=20 > ebuilds are markup and not formatting IMO, and the two shouldn't be > confused. If you want to work on presentation (which is important > too!) then go for it, but in any case I don't think a full stop at > end of descriptions is really worth the cost. All user interfaces are > shitty enough already, and users are unable to deal with information > already, so please don't add redundancy like full stops would be to > the problem. >=20 >=20 > //Peter Well, no problem in either way we finally choose (either "." or not), was simply trying to know what is preferred and try to unify the handling. --=-Mc4rofKMqh9S9v3QLlg9 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iEYEABECAAYFAlCCtgQACgkQCaWpQKGI+9Q7gwCeJqoQuYYTKK0UNNPk0zx3k/oS aZAAnjuwA0y2Y3114sglgGZPE7fxCdjv =+jC2 -----END PGP SIGNATURE----- --=-Mc4rofKMqh9S9v3QLlg9--