Pratyush Yadav <me@xxxxxxxxxxxxxxxxx> writes: > Maybe we should just have a consistent convention throughout the > documentation on whether to use one space after a full-stop or two. > Right now in some places we use one space, in some others we use two, > even in the same file. This is slightly distracting when reading. As somebody who almost always goes to the source on a fixed width font terminal and not to formatted output, I personally find it distracting not to have the extra space at the end of a sentence. > And FWIW, our man pages are always > rendered with one space, even if the source file has two. Or three, for that matter ;-) It is one of the reasons why we didn't really care and have not gone churning the source. > Having a convention would at least result in uniformity, even if > it won't end the debate on which is better. Yup. If I were to dictate a convention, I'd say we should have one extra space after a full-stop or similar that ends a sentence. As you pointed out, the choice of the convention does not make any difference to the end product for end users, and only affect those who work on the source with mark-ups, that is a fairly easy thing to declare, without letting anybody argue for or against---it is not better or worse than the other choice, but choosing one and sticking to it is probably much better than not having a uniform convention. Having said that, let's not go berserk and start reformatting, especially areas that are actively touched for non-stylistic reasons. Those other changes are much much more important. Thanks.
