From owner-svn-ports-all@FreeBSD.ORG Sat Jun 21 21:13:50 2014 Return-Path: Delivered-To: svn-ports-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B2F74D29; Sat, 21 Jun 2014 21:13:50 +0000 (UTC) Received: from apnoea.adamw.org (apnoea.adamw.org [204.109.59.150]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 416422591; Sat, 21 Jun 2014 21:13:50 +0000 (UTC) Received: from [192.168.192.25] (dhcp-108-170-169-12.cable.user.start.ca [108.170.169.12]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by apnoea.adamw.org (Postfix) with ESMTPSA id 79683120B5F; Sat, 21 Jun 2014 17:13:47 -0400 (EDT) Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\)) Subject: Re: svn commit: r358704 - head/Mk From: Adam Weinberger In-Reply-To: <53A5EF35.3020702@sasktel.net> Date: Sat, 21 Jun 2014 17:13:45 -0400 Content-Transfer-Encoding: quoted-printable Message-Id: References: <201406211423.s5LENFt4010937@svn.freebsd.org> <3AC42E34-C633-4797-9539-D57676A19E62@adamw.org> <53A5EF35.3020702@sasktel.net> To: Stephen Hurd X-Mailer: Apple Mail (2.1878.2) Cc: svn-ports-head@freebsd.org, Adam Weinberger , svn-ports-all@freebsd.org, Eitan Adler , ports-committers@freebsd.org X-BeenThere: svn-ports-all@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: SVN commit messages for the ports tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 21 Jun 2014 21:13:50 -0000 On 21 Jun, 2014, at 16:46, Stephen Hurd wrote: > While it supports a great deal of output formats, it supports a very > small number of input formats. Of course, "PS" isn't universally > understood anymore, some maybe "PostScript and PDF handing via > Ghostscript" would be better... or "Use Ghostscript for PDF and = Postscript=94. I really like =93PostScript and PDF handling via Ghostscript.=94 It=92s = clear, clean, and more-or-less accurate... I wouldn=92t suspect there = are too many ports that rely on GS for its bitmap rasterization. = (Right?) > I'm not even sure that Ghostscript needs to be repeated in the > description since the option name is shown. Possibly even "for > PostScript and PDF rasterization" would be best. >=20 > Quite often the word following the option name on the line is the = option > name with different casing. I agree with everything you just said, except I think that consistency = is vitally important for clarity so GHOSTSCRIPT should match the way = other descriptions are formatted. Ideally though, descriptions should say what the OPTION will accomplish, = as you and Eitan have pointed out. =93PS and PDF rasterization=94 tells = me what enabling it will accomplish, and I can be confident that I can = deselect it if I don=92t want PS and PDF rasterization support. And = while we=92re at it, there should be a pop-up box that tells me which = dependencies will be added by selecting this OPTION. # Adam --=20 Adam Weinberger adamw@adamw.org http://www.adamw.org