Date: Sun, 20 Feb 2000 23:50:02 -0800 (PST) From: Will Andrews <andrews@technologist.com> To: freebsd-doc@freebsd.org Subject: Re: docs/16854: Typos from Chapter 4 of FreeBSD Handbook Message-ID: <200002210750.XAA92147@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR docs/16854; it has been noted by GNATS. From: Will Andrews <andrews@technologist.com> To: bobj@atlantic.net Cc: freebsd-gnats-submit@FreeBSD.ORG Subject: Re: docs/16854: Typos from Chapter 4 of FreeBSD Handbook Date: Mon, 21 Feb 2000 02:40:27 -0500 On Sun, Feb 20, 2000 at 09:14:36PM -0800, bobj@atlantic.net wrote: > Same URL > Section 4.4.6. ELF support > > "...we wish to unofficially support the 2.2 as long as > possible." > > The 2.2 what? The 2.2 ports? The 2.2 binaries? I think > a word is missing here. I think they meant "[...] 2.2 a.out binary format". > Same URL > Section 4.4.16. Do's and Dont's > > "Here is a list of common do's and dont's that you encounter > during the porting process." As mentioned in a previous > typos submission, "Do's and Dont's" is not spelled correctly. > It should be "Dos and Don'ts", but you have to play games > with fonts for it to make sense. I think it depends on your point of view. Personally I prefer "Do's and Don'ts".. > Same URL > Section 4.4.16.5. Differentiating operating systems and OS versions > > 3.3-RELEASE > 3.3-STABLE > 3.3-STABLE after adding mkstemps() to libc > ??--> > 4.0-CURRENT after 3/4 branch > 4.0-CURRENT after change in dynamic linker handling > 4.0-CURRENT after C++ constructor/destructor order change > > The list of values for __FreeBSD_version does not include > entries for 3.4-RELEASE or 3.4-STABLE. Hmm.. I could swear I saw that list somewhere else that had 3.4-R and 3.4-S in there. Maybe the web's version is outdated. > Same URL > Section 4.4.16.22. If you are stuck... > > "Do look at existing examples and the bsd.port.mk file before > asking us questions! ;) " > > Although it looks fine in plain text, this emoticon does not > look right when rendered in italics on my browser. > It needs a nose. In other places it is rendered as ;-) Cosmetic bug. :-) > Same URL > Section 4.4.18. Automated package list creation > > "If your port honours PREFIX (which it should) you can then > install the port and create the package list. " > > This uses the British spelling "honours". I haven't noticed > British usage in earlier sections, although perhaps I > wasn't looking. If consistency is considered important, > someone should decide whether British or American spellings > will be used, or perhaps create SGML tags that allow alternate > spellings to be specified so that regional editions of the > Handbook can be easily rendered. Creating a tool to automate > the search for words so affected would then also be handy. I don't think it matters which way it goes, but I suppose your suggestion could be taken by the doc team. There's other words like "colour", too, that would be affected. > Same URL > Section 4.4.20.1. Current list of categories > > "afterstep* Ports to support AfterStep window manager " > > Reads better as "Ports to support the Afterstep...". Add > the word "the". Also, there should be a period at the end > to be consistent with other entries in the list. How about "Ports that support the AfterStep window manager" ? > Same URL > Same Section > > "irc Internet Chat Relay utilities. " > > Should say "Internet Relay Chat", at least in my dialect. Oops! *attempts to find somebody to blame for this* :-) > Same URL > Section 4.4.20.2. Choosing the right category > > "Also, you do not need to list net when the port belongs > to either of irc, mail, mbone, news, security, or www. " > > To me, "either" implies a choice between two options; > either a or b. I would change "either" to "any". I'm > not sure how the rest of the world feels about this. I agree with your opinion. > Same URL > Same Section, 4.4.20.2. Choosing the right category > > "If you are not sure about the category, please put a > comment to that effect in your send-pr submission so > we can discuss it before import it." > > There should be a word between "before" and "import". > Probably "we". Also, the parentheses around the Agreed. > next sentence should be removed (a sentence that > consists of nothing but a parenthetical phrase doesn't > seem quite right). You mean like your last sentence there? :-) -- Will Andrews <andrews@technologist.com> GCS/E/S @d- s+:+>+:- a--->+++ C++ UB++++ P+ L- E--- W+++ !N !o ?K w--- ?O M+ V-- PS+ PE++ Y+ PGP+>+++ t++ 5 X++ R+ tv+ b++>++++ DI+++ D+ G++>+++ e->++++ h! r-->+++ y? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200002210750.XAA92147>