Graham Percival <gra...@percival-music.ca> writes: > On Wed, Jul 11, 2012 at 03:50:21PM +0200, David Kastrup wrote: >> Janek Warchoł <janek.lilyp...@gmail.com> writes: >> >> > On Wed, Jul 11, 2012 at 1:56 PM, David Kastrup <d...@gnu.org> wrote: >> >> >> >> "Phil Holmes" <m...@philholmes.net> writes: >> >> > It should wrap between the words "the file" and the filename. > > +1 > >> > It would probably be less ugly that an overstretched line. As for >> > "rephrasing" strategy, i find it not suited to our needs. It's good >> > for publishers, whose job is to take care of such details when they >> > have an almost-ready-to-publish material. We are not a publishing >> > house: we don't want to fiddle with typography in our manuals. Also, >> > the manuals change, and the "rephrasing" solution is not flexible >> > enough. > > +1 > >> Typography is not magic. It has to obey the laws of physics. > > ... > > The "law" that I want TeX to do is this: > - if a word would be printed in the right-hand margin, insert a > line-break before that word. > > That's it.
No, that isn't it. What is supposed to happen to the line(s) before the break? If there is no answer meeting the configured constraints to that question, TeX does not break. > Sure. So we're asking if TeX can be tweaked to consider > additional solutions. (namely, "always add a line-break before > anything with an overfull hbox, regardless of what that makes the > rest of that paragraph look lik") Sure, that is what the emergencystretch stuff (and the @finalout command explained in the Texinfo chapter I cited) are all about. You can tell TeX to go ahead and choose ugly rather than flag the problematic paragraphs parts. > The answer could be "no, TeX is not flexible enough to do that". Fair > enough; we're accustomed to living within the limitations of our > tools. But this isn't an "impossible" or "magical" request. Phil already explained that he did not want to revert to the documented solutions TeX considers too ugly for consideration without explicit prodding. -- David Kastrup _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
