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.
This commit is contained in:
parent
ce7ee35d24
commit
2d91cbead9
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=3646
4 changed files with 6900 additions and 6876 deletions
|
|
@ -362,3 +362,27 @@ for example,
|
|||
33. Finished sweep. If it's white space sensitive (examples, program
|
||||
listings, PGP signatures...) the white space is now correct. I may
|
||||
have missed one or two on the way, I'll catch them later.
|
||||
|
||||
34. Removed repeated spaces 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 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 occurence of a stop.
|
||||
|
||||
|
|
|
|||
File diff suppressed because it is too large
Load diff
Loading…
Add table
Add a link
Reference in a new issue