Vertical Spacing less than @sp 1

2020-10-24 Thread Christopher Dimech


Is it possible to introduce a spacing between two lines of text
to be less than '@sp 1' or '@*', perhaps by half.

When I am writing a list or enumeration using @* look
as too much of a vertical space.

@enumerate
---@item
-Line Text 1
-@item
-Line Text 2 @sp 0.5
---@item
-Line Text 3
@end enumerate



Re: @smallverbatim

2020-10-24 Thread Christopher Dimech
You are correct, it works.  Missed the \setnormaldispenv
in \envdef\verbatim.


> Sent: Saturday, October 24, 2020 at 3:31 PM
> From: "Gavin Smith" 
> To: "Christopher Dimech" 
> Cc: "help-texinfo gnu" 
> Subject: Re: @smallverbatim
>
> On Sat, Oct 24, 2020 at 03:16:44PM +0200, Christopher Dimech wrote:
> > Have tried '@set dispenvsize small' for @quotation, @example, @display, 
> > @format.
> >
> > However, @verbatim is still using a large font.
> >
>
> Did you update to the most recent texinfo.tex?  Looks ok to me.
>
> \input texinfo
>
> normal
> @set dispenvsize small
>
> @verbatim
> a a
> bb d
>  f ff
> llm dsalk alke
> @end verbatim
>
> normal
>
> @example
> a a
> bb d
>  f ff
> llm dsalk alke
> @end example
>
> @bye
>
>



Re: @smallverbatim

2020-10-24 Thread Gavin Smith
On Sat, Oct 24, 2020 at 03:16:44PM +0200, Christopher Dimech wrote:
> Have tried '@set dispenvsize small' for @quotation, @example, @display, 
> @format.
> 
> However, @verbatim is still using a large font.
> 

Did you update to the most recent texinfo.tex?  Looks ok to me.

\input texinfo

normal
@set dispenvsize small

@verbatim
a a
bb d
 f ff
llm dsalk alke
@end verbatim

normal

@example
a a
bb d
 f ff
llm dsalk alke
@end example

@bye



Re: @smallverbatim

2020-10-24 Thread Christopher Dimech
> This would be a good idea if not for the fact that there
> are already documents using @smallbook and they may use
> an inconsistent mix of @smallexample and @example etc.

One solution could be to have @smallbook set @example, etc.
with a small size anyway.  A warning can be added in the
texinfo for people to remove calls to the @small versions
and eventually remove their use after a year or so.

I tend to find Warnings useful as I can go change my commands
at the time I am modifying the files and running the texinfo
programs.

c*


> Sent: Saturday, October 24, 2020 at 2:58 PM
> From: "Gavin Smith" 
> To: "Christopher Dimech" 
> Cc: "help-texinfo gnu" 
> Subject: Re: @smallverbatim
>
> On Sat, Oct 24, 2020 at 02:30:33PM +0200, Christopher Dimech wrote:
> > Yes, I confirm they are good and approve them being set
> > by dafault.  Do you mean I simply call @quotation
> > rather than @smallquotation.  It certainly makes things
> > easier.  Almost always I use @smallbook, and even for
> > @smallbook, the small versions are also better.  Can
> > you see if they can be used by default as well for
> > @smallbook.
>
> This would be a good idea if not for the fact that there
> are already documents using @smallbook and they may use
> an inconsistent mix of @smallexample and @example etc.
> One thing you could do is add an extra line to your source
> file, like:
>
> @smallbook
> @set dispenvsize small
>
> Then you would not have to bother with writing @smallexample, etc.
>
>
>
>
>



Re: @smallverbatim

2020-10-24 Thread Christopher Dimech
Have tried '@set dispenvsize small' for @quotation, @example, @display, @format.

However, @verbatim is still using a large font.




> Sent: Saturday, October 24, 2020 at 2:58 PM
> From: "Gavin Smith" 
> To: "Christopher Dimech" 
> Cc: "help-texinfo gnu" 
> Subject: Re: @smallverbatim
>
> On Sat, Oct 24, 2020 at 02:30:33PM +0200, Christopher Dimech wrote:
> > Yes, I confirm they are good and approve them being set
> > by dafault.  Do you mean I simply call @quotation
> > rather than @smallquotation.  It certainly makes things
> > easier.  Almost always I use @smallbook, and even for
> > @smallbook, the small versions are also better.  Can
> > you see if they can be used by default as well for
> > @smallbook.
>
> This would be a good idea if not for the fact that there
> are already documents using @smallbook and they may use
> an inconsistent mix of @smallexample and @example etc.
> One thing you could do is add an extra line to your source
> file, like:
>
> @smallbook
> @set dispenvsize small
>
> Then you would not have to bother with writing @smallexample, etc.
>
>
>
>
>



Re: @smallverbatim

2020-10-24 Thread Gavin Smith
On Sat, Oct 24, 2020 at 02:45:38PM +0200, Christopher Dimech wrote:
> Gavin, so what's left is to have @verbatim accept \smallword?

No, you just use @verbatim and it will use a smaller font by default.



Re: @smallverbatim

2020-10-24 Thread Christopher Dimech
Gavin, so what's left is to have @verbatim accept \smallword?


> Sent: Saturday, October 24, 2020 at 2:17 PM
> From: "Gavin Smith" 
> To: "Christopher Dimech" 
> Cc: "help-texinfo gnu" 
> Subject: Re: @smallverbatim
>
> On Sat, Oct 24, 2020 at 01:33:36PM +0200, Christopher Dimech wrote:
> > Was not a request for consistency. I find the @small versions more useful
> > because the customary one makes the text too big.  For instance, a quotation
> > is much better when using @smallquotation.
> >
> > I needed to use verbatim as it does not expand commands, but needed the
> > small version.
>
> The latest version works quite well with @bsixpaper, IMHO, because
> small fonts are on by default for @verbatim, @example, etc. and
> the margin is reduced, so most existing uses of it are OK without
> overlong lines.
>
> https://ftp.gnu.org/gnu/texinfo/texinfo.tex
>



Re: @smallverbatim

2020-10-24 Thread Christopher Dimech
Yes, I confirm they are good and approve them being set
by dafault.  Do you mean I simply call @quotation
rather than @smallquotation.  It certainly makes things
easier.  Almost always I use @smallbook, and even for
@smallbook, the small versions are also better.  Can
you see if they can be used by default as well for
@smallbook.


> Sent: Saturday, October 24, 2020 at 2:17 PM
> From: "Gavin Smith" 
> To: "Christopher Dimech" 
> Cc: "help-texinfo gnu" 
> Subject: Re: @smallverbatim
>
> On Sat, Oct 24, 2020 at 01:33:36PM +0200, Christopher Dimech wrote:
> > Was not a request for consistency. I find the @small versions more useful
> > because the customary one makes the text too big.  For instance, a quotation
> > is much better when using @smallquotation.
> >
> > I needed to use verbatim as it does not expand commands, but needed the
> > small version.
>
> The latest version works quite well with @bsixpaper, IMHO, because
> small fonts are on by default for @verbatim, @example, etc. and
> the margin is reduced, so most existing uses of it are OK without
> overlong lines.
>
> https://ftp.gnu.org/gnu/texinfo/texinfo.tex
>



Re: @smallverbatim

2020-10-24 Thread Gavin Smith
On Sat, Oct 24, 2020 at 01:33:36PM +0200, Christopher Dimech wrote:
> Was not a request for consistency. I find the @small versions more useful
> because the customary one makes the text too big.  For instance, a quotation
> is much better when using @smallquotation.
> 
> I needed to use verbatim as it does not expand commands, but needed the
> small version.

The latest version works quite well with @bsixpaper, IMHO, because
small fonts are on by default for @verbatim, @example, etc. and
the margin is reduced, so most existing uses of it are OK without
overlong lines.

https://ftp.gnu.org/gnu/texinfo/texinfo.tex



Re: @smallverbatim

2020-10-24 Thread Christopher Dimech
Was not a request for consistency. I find the @small versions more useful
because the customary one makes the text too big.  For instance, a quotation
is much better when using @smallquotation.

I needed to use verbatim as it does not expand commands, but needed the
small version.


> Sent: Saturday, October 24, 2020 at 12:41 PM
> From: "Gavin Smith" 
> To: "Christopher Dimech" 
> Cc: "help-texinfo gnu" 
> Subject: Re: @smallverbatim
>
> On Fri, Oct 23, 2020 at 02:37:01PM +0200, Christopher Dimech wrote:
> > Have been playing with @quotation, @example, @display, @format, @verbatim
> > and their small versions and found them all useful, particularly the small
> > versions.
> >
> > However, a small version of @verbatim is not present.  It would help to also
> > have @smallverbatim.
>
> It could be done (although somebody would have to do the work for it).  In
> my opinion, however, the @small... variants should never have been invented,
> and consistency is not a great argument for adding more commands.
>
> My preferred solution would be to use @small... variants unconditionally
> for certain page sizes.
>
> I know it is not very flexible, but texinfo.tex has never been very
> flexible.
>
> For example, for B6:
>
> diff --git a/doc/texinfo.tex b/doc/texinfo.tex
> index 6c5754f3d..fb9b69d58 100644
> --- a/doc/texinfo.tex
> +++ b/doc/texinfo.tex
> @@ -7663,13 +7663,13 @@ might help (with 'rm \jobname.?? \jobname.??s')%
>% without the active space; thus we have to use \xdef and \gobble.
>% The \egroup ends the \verbbox started at the end of the last line in
>% the block.
>  \endgroup
>  %
>  \envdef\verbatim{%
> -\setupverbatim\doverbatim
> +\setnormaldispenv\setupverbatim\doverbatim
>  }
>  \let\Everbatim = \afterenvbreak
>
>
>  % @verbatiminclude FILE - insert text of file in verbatim environment.
>  %
> @@ -11489,12 +11489,13 @@ directory should work if nowhere else does.}
>  \def\bsixpaper{{\globaldefs = 1
>\afourpaper
>\internalpagesizes{140mm}{100mm}%
>  {-6.35mm}{-12.7mm}%
>  {\bindingoffset}{14pt}%
>  {176mm}{125mm}%
> +  \let\SETdispenvsize=\smallword
>\globaldefs = 0
>  }}
>
>
>  % @pagesizes TEXTHEIGHT[,TEXTWIDTH]
>
>



Re: @smallverbatim

2020-10-24 Thread Gavin Smith
On Fri, Oct 23, 2020 at 02:37:01PM +0200, Christopher Dimech wrote:
> Have been playing with @quotation, @example, @display, @format, @verbatim
> and their small versions and found them all useful, particularly the small
> versions.
> 
> However, a small version of @verbatim is not present.  It would help to also
> have @smallverbatim.

It could be done (although somebody would have to do the work for it).  In
my opinion, however, the @small... variants should never have been invented,
and consistency is not a great argument for adding more commands.

My preferred solution would be to use @small... variants unconditionally
for certain page sizes.

I know it is not very flexible, but texinfo.tex has never been very
flexible.

For example, for B6:

diff --git a/doc/texinfo.tex b/doc/texinfo.tex
index 6c5754f3d..fb9b69d58 100644
--- a/doc/texinfo.tex
+++ b/doc/texinfo.tex
@@ -7663,13 +7663,13 @@ might help (with 'rm \jobname.?? \jobname.??s')%
   % without the active space; thus we have to use \xdef and \gobble.
   % The \egroup ends the \verbbox started at the end of the last line in
   % the block.
 \endgroup
 %
 \envdef\verbatim{%
-\setupverbatim\doverbatim
+\setnormaldispenv\setupverbatim\doverbatim
 }
 \let\Everbatim = \afterenvbreak
 
 
 % @verbatiminclude FILE - insert text of file in verbatim environment.
 %
@@ -11489,12 +11489,13 @@ directory should work if nowhere else does.}
 \def\bsixpaper{{\globaldefs = 1
   \afourpaper
   \internalpagesizes{140mm}{100mm}%
 {-6.35mm}{-12.7mm}%
 {\bindingoffset}{14pt}%
 {176mm}{125mm}%
+  \let\SETdispenvsize=\smallword
   \globaldefs = 0
 }}
 
 
 % @pagesizes TEXTHEIGHT[,TEXTWIDTH]




Re: @ref without page numbers

2020-10-24 Thread Christopher Dimech
Dear Gavin,

Have now tested your modification of texinfo.tex to remove the page
number and if works.

I also put the page number as a superscript.  It is easy to do, and
independently of whether customary or not, it does solve particular
problems if you could be so kind to put the options to do them.

With the appended 'p', it should not conflict with footnotes.
Furthermore as seen in the subscript commands 1. and 2., because the
page number it after close right bracket ']' and before the comma ','
of the reference, people would not confuse it with a footnote.  Appending
the letter 'p' could act as abbreviation if people think it is really
necessary.

1. Like this

\turnoffactive \sup{\refx{#1-pg}{}}%

2. and like this

\turnoffactive \sup{p\refx{#1-pg}{}}%


  %\ifoutputpagenumberinxref
% But we always want a comma and a space:
%,\space
%
% output the `page 3'.
%\turnoffactive \putwordpage\tie\sup\refx{#1-pg}{}%
\turnoffactive \sup{p\refx{#1-pg}{}}%
% Add a , if xref followed by a space
\if\space\noexpand\tokenafterxref ,%
\else\ifx\  \tokenafterxref ,% @TAB
\else\ifx\*\tokenafterxref ,%   @*
\else\ifx\  \tokenafterxref ,%   @SPACE
\else\ifx\  \tokenafterxref ,%@NL
\else\ifx\tie\tokenafterxref ,% @tie
\fi\fi\fi\fi\fi\fi
  %\fi




-
Christopher Dimech
Chief Administrator - Naiad Informatics - GNU Project (Geocomputation)
- Geophysical Simulation
- Geological Subsurface Mapping
- Disaster Preparedness and Mitigation
- Natural Resource Exploration and Production
- Free Software Advocacy


> Sent: Friday, October 23, 2020 at 11:44 PM
> From: "Gavin Smith" 
> To: "Christopher Dimech" 
> Cc: "help-texinfo gnu" 
> Subject: Re: @ref without page numbers
>
> On Fri, Oct 23, 2020 at 10:40:52PM +0200, Christopher Dimech wrote:
> > Dear Gavin,
> >
> > You are quite right, if the manual is printed, one needs the page numbers.
> >
> > I would be satisfied with an option in which the page number is printed
> > as a superscript @sup{page-no} (similar to footnote numbers) next to the
> > closing square bracket.
> >
> > That is, from this
> >
> > Section 1.13 [Intactv-Function], page 11,
> >
> > to this
> >
> > Section 1.13 [Intactv-Function]@sup{11},
> >
> > The would solve the problem, yet keep requirements intact.
> >
> > Regards
> > Christopher
>
> There's no precedent for this - this looks like a footnote reference.
> Would it not be simpler to miss out the page number, as in my patch
> here?
>
> https://lists.gnu.org/archive/html/bug-texinfo/2016-11/msg00048.html
>



Re: @ref without page numbers

2020-10-24 Thread Eli Zaretskii
> From: Christopher Dimech 
> Date: Fri, 23 Oct 2020 23:00:40 +0200
> Cc: help-texinfo gnu 
> 
> Pdf are very important in business settings, and because Texinfo allows
> inclusion of mathematical expression (through @math, @tex), the pdf output
> is very useful.

Texinfo doesn't have a separate PDF output format.  It just
piggy-backs the printed-document format for that, so it gets
everything that the printed-document format is supposed to produce.

If we want PDF output that has its own rules, we must develop an
independent PDF back-end.  I'm sure patches to that effect will be
welcome.  Until that is done, the printed format is what we have, and
need to live with.  IMO, at least.