Re: crop marks?

Hi. Gavin Smith wrote: > However, they probably aren't in the right place. I don't really > understand what the cropmarks are for in the first place. Doesn't it > depend on what areas of a page a printer is capable of printing on, > which depends on the printer? When printing an @smallbook book

Re: crop marks?

Commenting out one line in texinfo.tex makes the bottom cropmarks visible: Index: texinfo.tex === --- texinfo.tex (revision 8191) +++ texinfo.tex (working copy) @@ -418,7 +418,7 @@ \ifcropmarks \egroup % end of \vbox

Re: please migrate to git

> There is "svn blame" which you can use to see when each line in a > file was changed. Indeed, but useless for me, since it only shows me existing code while I'm wanting the opposite :-) I could have done manual bisecting, this is, checking revision by revision until I find the change. > I'm h

Re: crop marks?

Gavin Smith wrote: > On Tue, Nov 13, 2018 at 07:56:39AM -0700, arn...@skeeve.com wrote: > > Once upon a time there was an @cropmarks command in texinfo.tex that > > put cropmarks in the corners of the page. This was particularly helpful > > for working with @smallbook in order to visualize what

Re: crop marks?

On Tue, Nov 13, 2018 at 07:56:39AM -0700, arn...@skeeve.com wrote: > Once upon a time there was an @cropmarks command in texinfo.tex that > put cropmarks in the corners of the page. This was particularly helpful > for working with @smallbook in order to visualize what would actually > come back if

Re: my-bib-macros.texi

On Wed, Oct 17, 2018 at 10:19:25AM -0700, wlharv...@mac.com wrote: > The utility file my-bib-macros.texi, referenced on the > Texinfo - The GNU Documentation System https://www.gnu.org/software/texinfo/ > > has a bug in line 210: > > (See item [\ref\] in @

Re: please migrate to git

On Mon, Nov 19, 2018 at 11:27:04AM +0100, Werner LEMBERG wrote: > while trying to update lilypond's init script from texi2html version > 1.82 to 5.0 ??? this is what distributions provide today ??? I wanted to > find out where function `get_index' was changed. To get all changes > in the now obsol

Re: please migrate to git

On Mon, 19 Nov 2018, Masamichi Hosoda wrote: > No, I update it manually. I am doing this via cron scripts and Github deploy ssh keys which allows me to ignore it completely ;-) Also, it helps with CI testing via Travis-CI. Norbert -- PREINING Norbert http://www.prei

Re: please migrate to git

>> Here is a git mirror I've converted. >> https://github.com/trueroad/texinfo > > Ahh, great. Is that automatically/regularly updated? No, I update it manually.

Re: please migrate to git

On Mon, 19 Nov 2018, Masamichi Hosoda wrote: > Here is a git mirror I've converted. > https://github.com/trueroad/texinfo Ahh, great. Is that automatically/regularly updated? Thanks a lot Norbert -- PREINING Norbert http://www.preining.info Accelia Inc. +JA

Re: please migrate to git

Hi Werner, Norbert, all >> Given that Savannah provides git support and that it is rather easy to >> import an SVN repository to git (using `git svn ...') I strongly >> suggest to migrate to git. > > If there is interest, I can set up a git svn mirror as I have done for > luatex, texlive, texlive

Re: please migrate to git

Hi Werner, all > svn log --diff -r "{2009-01-01}:{2018-11-19}" > ~/texi2html.changes Umpf, not good. Much faster to do a git svn checkout and then use git. > Given that Savannah provides git support and that it is rather easy to > import an SVN repository to git (using `git svn ...') I strongl

please migrate to git

Folks, while trying to update lilypond's init script from texi2html version 1.82 to 5.0 – this is what distributions provide today – I wanted to find out where function `get_index' was changed. To get all changes in the now obsolete texi2html directory I issued the following command (I wasn't s