From owner-freebsd-doc Sat Apr 6 10: 1:52 2002 Delivered-To: freebsd-doc@freebsd.org Received: from mailsrv.otenet.gr (mailsrv.otenet.gr [195.170.0.5]) by hub.freebsd.org (Postfix) with ESMTP id 32AE937B419 for ; Sat, 6 Apr 2002 10:01:47 -0800 (PST) Received: from hades.hell.gr (patr530-b228.otenet.gr [212.205.244.236]) by mailsrv.otenet.gr (8.12.2/8.12.2) with ESMTP id g36I1a2a004133; Sat, 6 Apr 2002 21:01:38 +0300 (EEST) Received: from hades.hell.gr (hades [127.0.0.1]) by hades.hell.gr (8.12.2/8.12.2) with ESMTP id g36I1PpY013052; Sat, 6 Apr 2002 21:01:25 +0300 (EEST) (envelope-from keramida@ceid.upatras.gr) Received: (from charon@localhost) by hades.hell.gr (8.12.2/8.12.2/Submit) id g36I1O5m013047; Sat, 6 Apr 2002 21:01:24 +0300 (EEST) (envelope-from keramida@ceid.upatras.gr) Date: Sat, 6 Apr 2002 21:01:22 +0300 From: Giorgos Keramidas To: Ceri , freebsd-doc@FreeBSD.org Subject: Re: RFC: Removing "try and " from the docs Message-ID: <20020406180122.GB8722@hades.hell.gr> References: <20020404133226.GA8872@hades.hell.gr> <20020404143819.GB8766@submonkey.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020404143819.GB8766@submonkey.net> User-Agent: Mutt/1.3.28i Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On 2002-04-04 15:38, Ceri wrote: > > RCS file: /home/ncvs/doc/en_US.ISO8859-1/articles/filtering-bridges/article.sgml,v > > > > - If there are any problems, you should try and sort them out now > > + If there are any problems, you should try to sort them out now > > before proceeding. > > s/try to// perhaps ? Done :) > > RCS file: /home/ncvs/doc/en_US.ISO8859-1/books/developers-handbook/tools/chapter.sgml,v > > > > Although Emacs does have menus, it is well worth learning > > the key bindings, as it is much quicker when you are editing > > - something to press a couple of keys than to try and find the > > - mouse and then click on the right place. And, when you are > > + something to press a couple of keys than finding the > > + mouse and then clicking on the right place. And, when you are > > ...as pressing a couple of keys when you are editing is much > quicker than finding the mouse and then clicking in the right > place. This one looks better. Yes, I see your point. Either all verbs should use "to " or a gerund. > I'd like to drop the word "online" from "online on their monitor". > I do know what you mean, and it makes sense, but it looks bizarre and > could be confusing. Aye. Les confusion is good. We don't want to confuse readers. > Also, I'm not convinced that the handbook is "beautiful" :) That was meant to mean "aesthetically pleasing" so I might change it to that, if it looks better that way. > > --- en_US.ISO8859-1/books/fdp-primer/structure/chapter.sgml 26 Mar 2002 22:31:55 -0000 1.10 > > +++ en_US.ISO8859-1/books/fdp-primer/structure/chapter.sgml 3 Apr 2002 22:22:35 -0000 > Same problem here that I have with the emacs one above. Well, I'll leave this one out. This paragraph needs a rewrite to make it appear like something meaningful. Merely substituting "try and -> try to " won't solve any problems here. > > Index: en_US.ISO8859-1/books/handbook/basics/chapter.sgml > > =================================================================== > > RCS file: /home/ncvs/doc/en_US.ISO8859-1/books/handbook/basics/chapter.sgml,v > > retrieving revision 1.59 > > diff -u -r1.59 chapter.sgml > > --- en_US.ISO8859-1/books/handbook/basics/chapter.sgml 26 Mar 2002 23:37:38 -0000 1.59 > > +++ en_US.ISO8859-1/books/handbook/basics/chapter.sgml 3 Apr 2002 22:23:39 -0000 > > @@ -890,7 +890,7 @@ > > send—some of them have a specific meaning, others are interpreted > > by the application, and the application's documentation will tell you > > how that application interprets signals. You can only send a signal to > > - a process that you own. If you try and send a signal to someone else's > > + a process that you own. If you send a signal to someone else's > > process it will be ignored. The exception to this is the > > Slightly bigger problem here. > If you try to send a signal to someone else's process your attempt will fail > with EPERM, as opposed to being ignored. > This is the only one that I'd definitely want to see fixed, the others are > just MHO. I was thinking of that too. Referring to errors like EPERM in the "basics" chapter somehow seems like an overkill though. But I guess it's ok, since kill(1) or kill(2) will fail with EPERM. So we might just refer to these two here with something like: If you send a signal to someone else's process with &man.kill.1; or &man.kill.2; it will fail with EPERM, since you are not permitted to signal processes of other users. The exception to this is the ... Thanks Ceri, a very useful review. Giorgos Keramidas FreeBSD Documentation Project keramida@{freebsd.org,ceid.upatras.gr} http://www.FreeBSD.org/docproj/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message