From owner-cvs-all Wed Oct 21 14:51:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA16809 for cvs-all-outgoing; Wed, 21 Oct 1998 14:51:18 -0700 (PDT) (envelope-from owner-cvs-all@FreeBSD.ORG) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA16800; Wed, 21 Oct 1998 14:51:16 -0700 (PDT) (envelope-from nik@FreeBSD.org) From: Nik Clayton Received: (from nik@localhost) by freefall.freebsd.org (8.8.8/8.8.5) id OAA06823; Wed, 21 Oct 1998 14:51:13 -0700 (PDT) Date: Wed, 21 Oct 1998 14:51:13 -0700 (PDT) Message-Id: <199810212151.OAA06823@freefall.freebsd.org> To: cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG Subject: cvs commit: doc/en/handbook README handbook.sgml Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk nik 1998/10/21 14:51:13 PDT Modified files: en/handbook README handbook.sgml Log: Removed double whitespace from the end of stops -- . , ! ? : ; Some parts of the handbook had single spaces after stops, some had double or triple. While the typographical convention for monospaced fonts may be to use double spaces after them, that doesn't apply here. TeX will ignore them, as will HTML. If we need them for a plain text version of the Handbook then the stylesheet / conversion mechanism can insert them as necessary. Searching for _\([;:!\.\?,]\) +_ in Emacs and replacing with _\1 _ (ignore the '_', they're just to delineate the regexps) does the job quite nicely. However, you can't do this everywhere, since some of the double spaces might be in program listings or other literal sections (e.g., the BSD Copyright), so you need to sit and bounce on the 'y' or 'n' key as appropriate for each occurance of a stop. Revision Changes Path 1.35 +24 -0 doc/en/handbook/README 1.34 +2292 -2292doc/en/handbook/handbook.sgml To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message