"Trevor Daniels" <[email protected]> writes: > 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.
Uh what? This places "and/" at the end of the line, and "or" at the beginning of the next line. And that is not really a significant impediment to reading. -- David Kastrup _______________________________________________ lilypond-devel mailing list [email protected] https://lists.gnu.org/mailman/listinfo/lilypond-devel
