On Wed, Sep 25, 2019 at 3:03 PM Vincent Lefevre <[email protected]> wrote: > This fixes some cases, but not others. I've attached a url-break.texi > file with 4 cases. And I've tested 4 different texinfo.tex solutions > (the old one, the new one, the new one with this patch, and another > one with just a \allowbreak). As a summary:
Thanks for preparing the different cases. I've committed a change that stops the ragged-right output in the cases you sent but keeps it in others.
\input texinfo @c -*-texinfo-*-
@iftex
@afourpaper
@end iftex
Initial text to test the justification of the line containing the
first part of the URL: blah blah blah blah blah blah blah blah.
@url{https://www.1234567890123456789012345678901234567890123.invalid}.
Text to test the justification of the line containing the last part
of the URL: blah blah blah blah blah blah blah blah.
Initial text to test the justification of the line containing the
first part of the URL: blah blah blah blah blah blah blah blah.
@url{https://www.1234567890123456789012345678901234567890.invalid}.
Text to test the justification of the line containing the last part
of the URL: blah blah blah blah blah blah blah blah.
Initial text to test the justification of the line containing the
first part of the URL: blah blah blah blah blah blah blah blah.
@url{https://www.1234567890123456789012345678901234567.invalid}.
Text to test the justification of the line containing the last part
of the URL: blah blah blah blah blah blah blah blah.
Initial text to test the justification of the line containing the
first part of the URL: blah blah blah blah blah blah blah blah.
@url{https://www.1234567890123456789012345678901234.invalid}.
Text to test the justification of the line containing the last part
of the URL: blah blah blah blah blah blah blah blah.
see the
@url{https://www.gnu.org/software/libc/manual/html_node/Message-catalogs-with-gettext.html}
foo foo foo foo foo foo foof see the @url{https://www.gnu.org/software/libc/manual/html_node/}
In case of problem, please read the @file{INSTALL} file carefully
before reporting a bug, in particular section ``In case of problem''.
Some problems are due to bad configuration on the user side (not
specific to MPFR)@. Problems are also mentioned in the FAQ
@url{https://www.mpfr.org/faq.html}.
@bye
url-break.pdf
Description: Adobe PDF document
