Re: not all doc "clean-ups" are good

[Trevor Daniels]

Werner LEMBERG wrote Sunday, August 21, 2011 6:13 AM

> Well, it helps in situations like this
>
>     This is a  paragraph with  some text to
>     demonstrate  that  a  path  name   like
>     /usr/local/share/lilypond/foo.bar
>     should be split after backslashes.
>
> which looks better with a break after the backslash:

This is sensible, and I agree replacing 
/ with /@/ here is good.  But changing
"and/or" to "and/@/or" is bad (one you
changed recently.)  Splitting such short 
strings will make little difference to the
layout, and I would argue that placing
the "/or" at the start of a new line renders
the text less readable, not more.

So a / in any string less than, say, 12 characters
should be left alone.

Trevor
 


-----
No virus found in this message.
Checked by AVG - www.avg.com
Version: 10.0.1392 / Virus Database: 1520/3846 - Release Date: 08/20/11