From owner-freebsd-doc@freebsd.org Sat Apr 30 15:02:44 2016 Return-Path: Delivered-To: freebsd-doc@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C4E58B22E94 for ; Sat, 30 Apr 2016 15:02:44 +0000 (UTC) (envelope-from jhs@berklix.com) Received: from slim.berklix.org (slim.berklix.org [94.185.90.68]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 5D020121D for ; Sat, 30 Apr 2016 15:02:43 +0000 (UTC) (envelope-from jhs@berklix.com) Received: from mart.js.berklix.net (p5083CD2E.dip0.t-ipconnect.de [80.131.205.46]) (authenticated bits=128) by slim.berklix.org (8.14.5/8.14.5) with ESMTP id u3UF1D6a014860 for ; Sat, 30 Apr 2016 17:01:13 +0200 (CEST) (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (fire.js.berklix.net [192.168.91.41]) by mart.js.berklix.net (8.14.3/8.14.3) with ESMTP id u3UF2d2r011657 for ; Sat, 30 Apr 2016 17:02:39 +0200 (CEST) (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (localhost [127.0.0.1]) by fire.js.berklix.net (8.14.7/8.14.7) with ESMTP id u3UF2Sow058936 for ; Sat, 30 Apr 2016 17:02:40 +0200 (CEST) (envelope-from jhs@berklix.com) Message-Id: <201604301502.u3UF2Sow058936@fire.js.berklix.net> To: FreeBSD-doc@freebsd.org Subject: Re: Where did we lurn to spel? From: "Julian H. Stacey" Organization: http://berklix.eu BSD Unix Linux Consultants, Munich Germany User-agent: EXMH on FreeBSD http://berklix.eu/free/ X-URL: http://www.berklix.eu In-reply-to: Your message "Thu, 28 Apr 2016 16:38:00 -0600." Date: Sat, 30 Apr 2016 17:02:28 +0200 X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 30 Apr 2016 15:02:44 -0000 Warren Block wrote: > > accept in comments. How about dont vs don't ? > > The old "be generous in what you accept and strict in what you produce" > saying can apply. The code is what we produce, and comments should be > as good as we can make them. "Thru" is difficult to justify. "Dont" > and "cant" could be from trying to avoid an apostrophe. Just spelling > out the words instead of using the contraction solves the problem. Single apostrophes are best avoided, noisey when hunting unmatched brackets or quotes with eg my http://www.berklix.com/~jhs/src/bsd/jhs/bin/public/brackets/ Cheers, Julian -- Julian Stacey, BSD Linux Unix Sys Eng Consultant Munich http://berklix.eu/jhs/ Mail plain text, No quoted-printable, HTML, base64, MS.doc. Prefix old lines '> ' Reply below old, like play script. Break lines by 80. Let Brits in EU vote on Brexit https://petition.parliament.uk/petitions/112142 Lie to companies extorting personal data: Prevent abuse, loss & ID theft.