Texinfo Image Re-Scaling for Papersize

2020-10-31 Thread Christopher Dimech
Recently small page sizes (e.g. @bsixpaper) was added. I have some documents with images of a certain size for B5 Paper, which get too large and some parts get of the image gets cut off. Could Texinfo be made to adjust the image size accordingly as is done with text to fit smaller pages. How

Re: Development Tree lacking @bsixpaper

2020-10-31 Thread Gavin Smith
On Fri, Oct 30, 2020 at 10:33:16PM +0100, Christopher Dimech wrote: > Am trying the Development Tree and I thought the version would now have > @bsixpaper, > @bsixpaper, ... > > Regards > C* > It does.

Re: Development Tree lacking @bsixpaper

2020-10-31 Thread Christopher Dimech
I did the following command and installed. git clone https://git.savannah.gnu.org/git/texinfo.git I did the following and seeme good. Did I get the wrong one? texi2pdf -v texi2dvi (GNU Texinfo 6.7dev) Copyright (C) 2019 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later

Re: Texinfo Image Re-Scaling for Papersize

2020-10-31 Thread Gavin Smith
On Sat, Oct 31, 2020 at 10:37:33AM +0100, Christopher Dimech wrote: > > Recently small page sizes (e.g. @bsixpaper) was added. I have some documents > with images of a certain size for B5 Paper, which get too large and some parts > get of the image gets cut off. > > Could Texinfo be made to adj

Re: Development Tree lacking @bsixpaper

2020-10-31 Thread Gavin Smith
On Sat, Oct 31, 2020 at 12:04:28PM +0100, Christopher Dimech wrote: > @bsixpaper works if I put texinfo.texi in the local directory. > > When using @smallbook, I get smallbook, but when I remove > @smallbook and call @bsixpaper, I am getting @afourpaper > > > @ifclear InclFl--Chmed > \input texi

Re: Development Tree lacking @bsixpaper

2020-10-31 Thread Christopher Dimech
> Sent: Saturday, October 31, 2020 at 12:25 PM > From: "Gavin Smith" > To: "Christopher Dimech" > Cc: help-texinfo@gnu.org > Subject: Re: Development Tree lacking @bsixpaper > > On Sat, Oct 31, 2020 at 12:04:28PM +0100, Christopher Dimech wrote: > > @bsixpaper works if I put texinfo.texi in t

Re: Texinfo Image Re-Scaling for Papersize

2020-10-31 Thread Christopher Dimech
I can see your point. > Sent: Saturday, October 31, 2020 at 12:01 PM > From: "Gavin Smith" > To: "Christopher Dimech" > Cc: "help-texinfo gnu" > Subject: Re: Texinfo Image Re-Scaling for Papersize > > On Sat, Oct 31, 2020 at 10:37:33AM +0100, Christopher Dimech wrote: > > > > Recently small pa

Re: Development Tree lacking @bsixpaper

2020-10-31 Thread Gavin Smith
On Sat, Oct 31, 2020 at 12:35:42PM +0100, Christopher Dimech wrote: > > > > Sent: Saturday, October 31, 2020 at 12:25 PM > > From: "Gavin Smith" > > To: "Christopher Dimech" > > Cc: help-texinfo@gnu.org > > Subject: Re: Development Tree lacking @bsixpaper > > > > On Sat, Oct 31, 2020 at 12:04:

Re: Development Tree lacking @bsixpaper

2020-10-31 Thread Patrice Dumas
On Sat, Oct 31, 2020 at 12:35:42PM +0100, Christopher Dimech wrote: > > C* But when there is an official release, one would not need to > store locally. Am I right? I never used to put the file in local > directory for official releases before. I am not sure how you got the new releases before,

Re: Development Tree lacking @bsixpaper

2020-10-31 Thread Christopher Dimech
I usually want to use the most recent source code when preparing for my releases. That helps make improvements at a much earlier time, and thusly be able to release a better product that works better as users start updating the associated packages later on. - Christopher Dimec

Re: @menu puts too many restrictions to produce the .info file

2020-10-31 Thread Gavin Smith
On Tue, Oct 20, 2020 at 05:59:56PM +0100, Gavin Smith wrote: > On Tue, Oct 20, 2020 at 04:53:11PM +0100, Gavin Smith wrote: > > If an author wants to have irregular menu or node structures for some > > reason (I haven't made sense exactly of what Christopher is doing > > with his documents) then th

Re: @menu puts too many restrictions to produce the .info file

2020-10-31 Thread Christopher Dimech
Good evening Gavin. I have actually. My original plan was to have multiple menus for different types of users, so they may traverse it according to the job they want to do. Many, including myself end up having to go though a lot of menu paths to get what I need. So it is customary for me to simpl