lilypond-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Texinfo - manual line breaks in URLs?


From: Michael Käppler
Subject: Re: Texinfo - manual line breaks in URLs?
Date: Mon, 22 Jun 2020 17:59:58 +0200
User-agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.9.0

Am 19.06.2020 um 09:51 schrieb Werner LEMBERG:

[snip]
Since my distro is not that old, I do not think it would be a good
idea to require a newer texinfo version, so I would suggest that we
stick with texinfo.tex from
http://git.savannah.gnu.org/cgit/texinfo.git/commit/util/texi2dvi?id=77390b679e5f4833661fda9f34fd7da119bb942e
I disagree.  While this is the right way for the next development
version, in the long run the new indexing code has advantages.  For
example, right now we have index entries like
Ok, I just feared that there might be other incompatibilities if
the texinfo.tex version and the texi2dvi version diverge too much.
I do not fully understand what you mean by
"this is the right way for the next development
version", however - if you think it is feasible to upgrade
to the most recent texinfo.tex version, with the
seealso->moreref changes and possibly further adjustments,
why not update now?
Do you suggest to do in it two steps insteads?


   tablature .............................  23
   tablature, and beams ..................  14
   tablature, and harmonic indications ... 234
   tablature, and harmonics .............. 345
   tablature, and polyphony .............. 100
   tablature, and slides .................  48
   ...

With the new code it will be possible to have this condensed to

   tablature .............................  23
     and beams ...........................  14
     and harmonic indications ............ 234
     and harmonics ....................... 345
     and polyphony ....................... 100
     and slides ..........................  48
   ...

which enormously increases the legibility IMHO.

It seems that the required change in `texi2dvi` is a one-liner.  We
could test that and apply the patch by ourselves if necessary.
Seems pretty hacky to me to patch a present version of 'texi2dvi' for
using it. Maybe we can ship the whole 'texi2dvi' script, as we do it for
texinfo.tex? That way we could ensure that texinfo.tex and texi2dvi are
always compatible.
AFAICT (please correct me, if I make wrong assumptions here)
the script does not have other special dependencies, it only runs the
programs that
are given with TEX, PDFTEX, PDFLATEX etc.

To evaluate the first step of switching to texinfo.tex from
http://git.savannah.gnu.org/cgit/texinfo.git/commit/?id=77390b679e5f4833661fda9f34fd7da119bb942e
(The last version working without patched texi2dvi, at least for me),
I compared the PDFs generated with this version with reference PDFs,
compiled
against the currently bundled texinfo.tex.

See the results here:
https://drive.google.com/drive/folders/1czVl2glLVoQiUOLu1mvnWh9hozivaPuC?usp=sharing

Green color = reference version with texinfo.tex from out repo
Red color = version with texinfo.tex from aforementioned commit

It seems the differences are mainly in URL breaking and formatting, and
index formatting.
What do you think?
As a next step, now that David's MR is in, I would try to update to
current texinfo.tex
and compare the output again.
Then I could try to remove the @/ occurrences and as a last step
set @urefbreakstyle before.

Cheers,
Michael






reply via email to

[Prev in Thread] Current Thread [Next in Thread]