On Fri, Oct 21, 2022 at 03:18:06PM +0200, Patrice Dumas wrote:
> > It would seem like a simple change to treat @w the same as @shortcaption
> > and @math here.
>
> It is probably the converse that would be best, that is add
> contain_simple_text to shortcaption and math... Actually,
> it would
On Thu, Oct 20, 2022 at 04:42:45PM +0200, Patrice Dumas wrote:
> It could also be possible to accept more commands in @w without giving a
> warning.
Given that @footnote and @verb don't work properly inside @w and the
using @pxref inside @w isn't something that document authors particularly
want
On Thu, Oct 20, 2022 at 10:44:09PM +0200, Patrice Dumas wrote:
> On Thu, Oct 20, 2022 at 05:34:06PM +0100, Gavin Smith wrote:
> >
> > I don't see any reason why @w shouldn't contain anything that
> > can be output inside a paragraph, except maybe for @footnote.
>
>
It came up by accident in the other discussion that the treatment
of multiple spaces inside @w is inconsistent between texinfo.tex and
texi2any.
@w has a very simple implementation in texinfo.tex - it
puts the contents into an \hbox, which stops line break.
In texi2any, as well as stopping line
On Thu, Oct 20, 2022 at 05:34:07PM +0100, Gavin Smith wrote:
> In theory there is a potential problem with a @footnote inside @w.
> texi2any.pl appears to do the right thing here. However,
> texinfo.tex does not - the footnote disappears completely!
I found the following in &quo
On Thu, Oct 20, 2022 at 01:20:19PM +0200, Robert Pluim wrote:
> platforms, Emacs can yank these objects with the @code{yank-media}
> command---but only in modes that have support for it (@w{@pxref{Yanking
> Media,,, elisp, The Emacs Lisp Reference Manual}}).
>
> Is there a reason for
The first pretest for the Texinfo 7.0 release has been uploaded to
https://alpha.gnu.org/gnu/texinfo/texinfo-6.8.90.tar.xz
There have been many changes since the previous release (see below),
but among the most notable are the addition of LaTeX and EPUB 3 as
texi2any output formats.
It's also
On Wed, Oct 19, 2022 at 08:43:21AM +0800, Wu XiangCheng wrote:
> I have tested them and almost OK. Yet two small things could be fixed.
Thanks, committed.
On Tue, Oct 18, 2022 at 09:55:45PM +0200, Hilmar Preuße wrote:
> Am 17.10.2022 um 22:45 teilte Gavin Smith mit:
>
> Hi Gavin,
>
> > An improvement would be to check the exit status of "man -a" and if
> > not found, to fall back to loading the man page as usual.
On Tue, Oct 18, 2022 at 06:11:12PM +0100, Gavin Smith wrote:
> On Fri, Oct 07, 2022 at 07:19:57AM +0100, Gavin Smith wrote:
> > > Using \txizhpackage label to determine whether to change the
> > > behavior.Would you like to put such hooks in main file? Or may
>
On Fri, Oct 07, 2022 at 07:19:57AM +0100, Gavin Smith wrote:
> > Using \txizhpackage label to determine whether to change the
> > behavior.Would you like to put such hooks in main file? Or may
> > another elegant way?
>
> Yes I will try to add hooks like this for these
On Mon, Oct 17, 2022 at 10:20:03PM +0200, Hilmar Preuße wrote:
> Dear maintainers,
>
> info runs out of memory when trying to dump python3.10 docs on stdout:
>
>$ dpkg-query -W python3.10-doc
>python3.10-doc3.10.7-2
>
>$ info python3.10 > /dev/null
>info: memory exhausted
>
On Sun, Oct 16, 2022 at 03:26:45PM +0100, Gavin Smith wrote:
> On Sun, Oct 16, 2022 at 04:58:59PM +0300, Eli Zaretskii wrote:
> > > From: Gavin Smith
> > > Date: Sun, 16 Oct 2022 14:23:27 +0100
> > > Cc: bug-texinfo@gnu.org
> > >
> > > I've co
On Sun, Oct 16, 2022 at 10:08:17PM -0700, Raymond Toy wrote:
> Hmm, my default browser is Firefox. The output looks right, but I didn't
> check to see how it was actually rendered. I think texinfo 6.8 mathjax
> uses the SVG output instead of CHTML. Not sure why that is and if it
> really
On Sun, Oct 16, 2022 at 04:58:59PM +0300, Eli Zaretskii wrote:
> > From: Gavin Smith
> > Date: Sun, 16 Oct 2022 14:23:27 +0100
> > Cc: bug-texinfo@gnu.org
> >
> > I've committed more code to use "man -w" first to check if the man page
> >
On Sat, Oct 15, 2022 at 11:58:53PM +0200, Hilmar Preusse wrote:
> Dear developers,
>
> I noticed that "info -w" is puzzlingly slow when the argument is a man page:
>
> $ time -p info -w ffmpeg-all
> *manpages*
> real 1.06
> user 1.47
> sys 0.16
>
> In contrast, "man -w" is
On Sat, Oct 15, 2022 at 11:52:19PM +0200, Hilmar Preusse wrote:
> Dear developers,
>
> "info -o" exits with status 0 when it can't find the node:
>
> $ info -o /dev/null lolcow
> info: No menu item 'lolcow' in node '(dir)Top'
>
> $ echo $?
> 0
>
Thank you for the report. I
On Sat, Oct 15, 2022 at 07:14:04PM -0500, Jacob Bachmeyer wrote:
> Since @math is defined to use TeX syntax in its argument, would it be better
> to extend the other Texinfo processors to recognize \var inside @math and do
> whatever is needed to make it act as @var in that case?
@var already
On Sat, Oct 15, 2022 at 12:40:32PM +0200, Vincent Lefevre wrote:
> The spaces in math mode can normally stretch and shrink (not in
> the same way as outside of math mode, though). But there are some
> TeX commands that changes spaces to fixed spaces in math mode.
> I just wanted to be sure that @w
On Sat, Oct 15, 2022 at 05:36:36PM +0200, Jakub Wilk wrote:
> ---
> doc/texinfo.texi | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/doc/texinfo.texi b/doc/texinfo.texi
> index 2f31fce9e4..6f2e0cc161 100644
> --- a/doc/texinfo.texi
> +++ b/doc/texinfo.texi
> @@ -24091,7
On Mon, Sep 05, 2022 at 09:16:30PM +0100, Gavin Smith wrote:
> On Sat, Sep 03, 2022 at 01:49:40PM +, Werner LEMBERG wrote:
> > For consistency I think it would be better if `@cartouche` obeyed the
> I tried working on the right margin of the cartouche but I didn't
> figure it
On Sat, Oct 15, 2022 at 03:20:22PM +0200, Patrice Dumas wrote:
> Should be done for latex2html too. I still haven't finished handling
> @latex blocks correctly, but should be done soon.
I doubt it is correct to convert the contents of @latex and @tex
blocks when outputting HTML unless --iflatex
On Sat, Oct 15, 2022 at 02:28:54PM +0200, Patrice Dumas wrote:
> On Sat, Oct 15, 2022 at 12:32:00PM +0100, Gavin Smith wrote:
> >
> > l2h and t4h settings still output "@var" literally even with
> > '-c CONVERT_TO_LATEX_IN_MATH=1'. I'm going to spend some time
On Fri, Oct 14, 2022 at 09:27:22PM -0500, Jacob Bachmeyer wrote:
> TeX has an \ifmmode conditional that is true in math mode; @var/\var and
> other marking macros could be adjusted to mark their arguments appropriately
> when invoked in math mode. Are there other macros that would be appropriate
On Fri, Oct 14, 2022 at 09:27:22PM -0500, Jacob Bachmeyer wrote:
> Vincent Lefevre wrote:
> > On 2022-10-14 11:30:33 +0200, Patrice Dumas wrote:
> > > On Fri, Oct 14, 2022 at 12:40:08AM +0200, Vincent Lefevre wrote:
> > > > On 2022-10-13 21:15:57 +0200, Patrice Dumas wrote:
> > > > All of them are
On Sat, Oct 15, 2022 at 12:40:04AM +0200, Vincent Lefevre wrote:
> > In your use case, you can avoid line breaks using the @w command:
> >
> > @deftypefun int f4 ()
> > @w{@math{@var{n} = -2}}.
> > @end deftypefun
>
> If the @w ignored in math mode?
No, the contents of @w are not split across
On Fri, Oct 14, 2022 at 01:15:03PM +0200, Vincent Lefevre wrote:
>
> \input texinfo@c -*-texinfo-*-
>
> @macro ttie {}
> @end macro
>
> @deftypefun int f1 ()
> @math{@var{n}=-2}.
> @end deftypefun
>
> @deftypefun int f2 ()
>
On Fri, Oct 14, 2022 at 07:06:04AM +0100, Gavin Smith wrote:
> On Fri, Oct 14, 2022 at 12:40:08AM +0200, Vincent Lefevre wrote:
> > On 2022-10-13 21:15:57 +0200, Patrice Dumas wrote:
> > > I agree with Gavin, you should not use @math if you want normal text,
> > > but g
On Fri, Oct 14, 2022 at 08:40:58AM -0700, Raymond Toy wrote:
> > I tested the page
> > https://mathjax.github.io/MathJax-demos-web/tex-chtml.html
> > with lynx (there are no Texinfo manuals with mathjax enabled I know of,
> > if anybody knows about one, please tell me), and the result seems good
On Fri, Oct 14, 2022 at 12:40:08AM +0200, Vincent Lefevre wrote:
> On 2022-10-13 21:15:57 +0200, Patrice Dumas wrote:
> > I agree with Gavin, you should not use @math if you want normal text,
> > but given that there is now good support of TeX math in texi2any for
> > HTML with any of the 3
On Thu, Oct 13, 2022 at 11:20:24PM +0200, Vincent Lefevre wrote:
> is not true. More precisely, I would expect
>
> @macro ttie
> @end macro
>
> to generate nothing, but inserting @ttie{} in a TeX expression
> modifies the spacing in the generated PDF.
Please provide a minimal example showing
On Thu, Oct 13, 2022 at 10:28:26PM +0200, Patrice Dumas wrote:
> Hello,
>
> With TeX, the following leads to \times being output as text and not as a
> symbol:
>
> @inlinefmtifelse{info, something, @math{a \times 2}}.
>
> I attach a file that can be used to check the result in that case and
>
On Wed, Oct 12, 2022 at 11:11:53AM +0200, Patrice Dumas wrote:
> On Wed, Oct 12, 2022 at 01:13:07AM +0200, Vincent Lefevre wrote:
> > With Texinfo 6.8 and HTML output, @minus{} is converted to a hyphen
> > instead of a real minus character (U+2212 MINUS SIGN).
>
> It is actually not clear to me
On Wed, Oct 12, 2022 at 09:26:43PM +0200, Patrice Dumas wrote:
> On Wed, Oct 12, 2022 at 01:46:28PM +0200, Vincent Lefevre wrote:
> > BTW, I thought that --enable-encoding was the default. But after,
> > testing, it isn't. The makeinfo(1) man page should be clarified.
> > Instead of
> >
> >
On Thu, Oct 13, 2022 at 11:57:26AM +0200, Vincent Lefevre wrote:
> On 2022-10-13 06:48:49 +0100, Gavin Smith wrote:
> > This is the default if MathJax is not turned on or tex4ht or latex2html
> > are not used. The tag marks the text as separate. There is not
> > much mo
On Wed, Oct 12, 2022 at 12:40:12AM +0200, Vincent Lefevre wrote:
> The Texinfo manual says
>
>The '@math' command has no special effect on the Info output or (by
> default) the HTML output, merely outputting the contents verbatim.
>
> However, as said later, the contents are emphasized (with
On Fri, Oct 07, 2022 at 10:11:39AM +0800, Wu XiangCheng wrote:
> 在 2022/10/7 04:15, Gavin Smith 写道:
> > On Fri, Oct 07, 2022 at 01:07:13AM +0800, Wu XiangCheng wrote:
> > > ---
> > > ChangeLog | 5 +
> > > doc/txi-zh.tex | 478 +++
On Fri, Oct 07, 2022 at 01:07:13AM +0800, Wu XiangCheng wrote:
> ---
> ChangeLog | 5 +
> doc/txi-zh.tex | 478 +
> 2 files changed, 483 insertions(+)
>
> diff --git a/ChangeLog b/ChangeLog
> index 0052938a44..f166ed85a3 100644
> ---
On Fri, Oct 07, 2022 at 01:07:11AM +0800, Wu XiangCheng wrote:
> ---
> ChangeLog | 5 +
> doc/texinfo-zh.tex | 53 ++
> 2 files changed, 58 insertions(+)
> create mode 100644 doc/texinfo-zh.tex
This appears to be a trivial modification
On Tue, Oct 04, 2022 at 08:38:47PM +, Werner LEMBERG wrote:
> > I know very little about LuaTeX so don't know how to generate a
> > luatex-plain format the way you state, so I have difficulty
> > replicating this problem.
>
> Assuming you have a complete TeXLive installation, you really have
On Tue, Oct 04, 2022 at 01:39:04PM -0400, Richard Stallman wrote:
> [[[ To any NSA and FBI agents reading my email: please consider]]]
> [[[ whether defending the US Constitution against all enemies, ]]]
> [[[ foreign or domestic, requires you to follow Snowden's example. ]]]
>
> >
On Tue, Oct 04, 2022 at 04:25:37PM +0100, Gavin Smith wrote:
> > However, using it as
> >
> > ```
> > PDFTEX="luatex --fmt=luatex-plain" texi2pdf foo.texi
> > ```
> >
> > fails with
> >
> > ```
> > texi2dvi: TeX neit
On Tue, Oct 04, 2022 at 06:12:15AM +, Werner LEMBERG wrote:
>
>
> For testing purposes I generated a 'luatex-plain' format with
>
> ```
> mtxrun --generate
> mtxrun --script plain --make
> ```
>
> However, using it as
>
> ```
> PDFTEX="luatex --fmt=luatex-plain" texi2pdf foo.texi
> ```
>
On Mon, Oct 03, 2022 at 08:31:06AM +0100, Jonathan Wakely wrote:
> On Mon, 3 Oct 2022 at 07:01, Gavin Smith via Gcc wrote:
> >
> > On Sun, Oct 02, 2022 at 09:06:06PM -0400, Richard Stallman wrote:
> > > generates the following output:
> > >
> > >
On Sun, Oct 02, 2022 at 09:06:06PM -0400, Richard Stallman wrote:
> generates the following output:
>
> Some macros are predefined on each kind of machine
> (see
On Sun, Oct 02, 2022 at 12:52:05PM +0100, Gavin Smith wrote:
> The only thing I could find is this page from 2014:
>
> https://tex.stackexchange.com/questions/176931/how-to-escape-character-in-index
>
> but this only treats | in the math context. A commenter there says it
>
The groff manual indexes "\|" which is output in the LaTeX output as
\index[es]{\textbackslash{}"|@\texttt{\textbackslash{}"|}}%
However this leads to an error:
! Extra }, or forgotten \endgroup.
}
l.72 \item \texttt{\textbackslash{}|}}
On Sat, Oct 01, 2022 at 04:06:18PM +, Werner LEMBERG wrote:
>
> > I added some extra space in commit 2d1867cd03. It's probably not
> > perfect either but hopefully it will be good enough.
>
> Thanks, but it seems that you haven't called 'git push'...
My apologies, git push failed because
On Sat, Oct 01, 2022 at 03:02:25PM +, Werner LEMBERG wrote:
>
> > I have committed the fix similar to the following, although I expect
> > it is not perfect: [...]
>
> Thanks.
>
> > You may notice that @center @image is still slightly closer than
> > @image after this change, but it looks
On Tue, Sep 20, 2022 at 09:54:09AM +, Werner LEMBERG wrote:
> Much better, thanks. However, if `@raggedright` is involved, there
> are still cases where the space after 'Chapter X:' is wider than
> usual. Attached is an example.
>
>
> Werner
I confirmed this, although it seems barely
On Fri, Sep 30, 2022 at 02:41:42PM +, Werner LEMBERG wrote:
> As can be seen, the `@center` macro swallows the vertical space before
> the image, which is a bug, I guess.
I have committed the fix similar to the following, although I expect it
is not perfect:
diff --git a/doc/texinfo.tex
On Fri, Sep 30, 2022 at 03:34:08PM -0600, Karl Berry wrote:
> Norbert suggested that they could make cm-super (or lmodern) a depends
> or recommends on texinfo, if you wish. Please advise :).
I hope it was clear from my other mail that I don't think this is a good
idea.
> This could be done
On Thu, Sep 29, 2022 at 04:43:04PM -0600, Karl Berry wrote:
> Patrice, Gavin - I've been talking with my friend Norbert Preining, who
> used to be the Debian maintainer of the texlive packages. (He's also one
> of the principal maintainers, with me and a couple others, of upstream
> TeX Live.)
>
On Fri, Sep 30, 2022 at 08:23:11AM +0900, Norbert Preining wrote:
> > He's willing in principle to suggest that cm-super[-minimal] become part
> > of the recommended TeX packages, but I'm not sure that is warranted.
>
> I just suggested two possible options, both I don't mind:
> - make cm-super
On Wed, Sep 28, 2022 at 01:24:00PM -0700, Raymond Toy wrote:
> The manual says:
>
> For TeX, this command causes a file txi-locale.tex to be read (if it
> exists).
>
> But when I run texi2pdf maxima.texi, I get
>
> ./maxima.texi:4: Cannot read language file txi-ru.tex.
>
> Which is true, but I
On Wed, Sep 28, 2022 at 08:21:45PM +0100, Charles Reilly wrote:
> A fix is attached.
Thanks, committed in 79c29a9b2e0.
On Tue, Sep 27, 2022 at 06:41:44PM -0600, Karl Berry wrote:
> kb> Regarding typewriter: I reiterate the need to turn it off for display
> kb> environments.
>
> On second thought, for the LaTeX backend, I can see how it would be
> better to simply take the default, that is,
On Tue, Sep 27, 2022 at 09:38:30AM +0200, pertu...@free.fr wrote:
> ... but my feeling is
> that this is the symptom of something wrong being done with fonts
> selection in the LaTeX output, not an issue with microtype as such.
It is just a consequence of using T1 encoded fonts, which aren't used
On Tue, Sep 27, 2022 at 09:26:15AM +0200, Patrice Dumas wrote:
> > I'm not sure if it would be correct to ignore spaces for other commands:
> > @math, @value, @verb... Almost every command could be different. It
> > seems quite simple to say that these spaces are ignored for BRACE_arguments
> >
On Tue, Sep 27, 2022 at 06:07:08PM +0100, Charles Reilly wrote:
> Hi,
>
> Using info I have had some issues with finding the first entry in the index.
> For example, try running "info gzip". The first entry in the concept index
> for gzip is "bugs". Some example searches:
>
> ibugs -
On Tue, Sep 27, 2022 at 01:32:36AM +0200, pertu...@free.fr wrote:
> So, my question is how does Texinfo TeX select scalable fonts for the
> letters that exists in cm fonts, while LaTeX does not? Is there a way
> to have LaTeX select the same scalable fonts as TeX (even when cm-super
> is not
On Sun, Sep 25, 2022 at 04:11:13PM +0200, Patrice Dumas wrote:
> I suggest, for texi2any
> * not to ignore spaces for indicating brace @-commands and @w (nothing
> changes for those commands) and also for the following list of @-commands
> that are somewhat similar to indicating @-commands:
>
On Mon, Sep 26, 2022 at 12:09:21PM +0200, Patrice Dumas wrote:
> I implemented in LaTeX output too. There was an error without the
> cm-super font. I am a bit surprised that microtyping works out of the
> box in TeX, but not with LaTeX...
>
> I documented that cm-super is needed in the
On Sun, Sep 25, 2022 at 11:36:02AM +0100, Gavin Smith wrote:
> Still to do:
> * Documentation
> * Stub implementation in texi2any (doesn't need to do anything for
> any other output format).
Patrice has taken care of texi2any and I've added some documentation,
so all that is left
On Sat, Sep 24, 2022 at 03:18:07PM -0600, Karl Berry wrote:
> I am mainly unsure about if/how this should be turned on in Texinfo
> files.
>
> Just make it an option, say, @microtype on|off. Off by default. (And
> forced to "off" when output is dvi.) That way it doesn't disturb
>
> --- a/ChangeLog
> +++ b/ChangeLog
> @@ -1,3 +1,10 @@
> +2022-09-07 Sam James
> +
> + * install-info/install-info.c: Recognize .zst file
> + extension from the zstd compression tool.
> +
> + * info/filesys.c: Ditto.
> +
> 2022-09-05 Gavin Smith
On Sat, Sep 17, 2022 at 02:28:08PM -0600, Karl Berry wrote:
> Hi Gavin. I've found that the microtype package for LaTeX
> (https://ctan.org/pkg/microtype) helps significantly in eliminating
> overfull lines without the need for rewriting text. (It also improves
> the esthetic appearance of the
On Sat, Sep 24, 2022 at 01:39:47AM +, Tommy Nguyen wrote:
> I am using texinfo-6.8-4.fc37.
>
> Hardened malloc[1] is a security focused malloc implementation.
> According to them, crashes are usually bugs in the application because
> they are more strict than the glibc malloc. When running
On Tue, Sep 20, 2022 at 05:13:00AM +, Werner LEMBERG wrote:
>
> Right now, at the top of a page, the height of an `@image` box is
> aligned with the base line of the top line. I ask to shift the image
> box up so that it aligns with the top of the top (default text) line,
> since the current
On Sat, Sep 17, 2022 at 02:28:07PM -0600, Karl Berry wrote:
> Hi Gavin - the new (since August) setting of \lastlinefit in texinfo.tex
> can cause numerous new underfull hboxes in existing documents.
> Essentially every last line of a paragraph now becomes a candidate for
> being underfull, while
On Fri, Sep 16, 2022 at 06:18:09AM +, Werner LEMBERG wrote:
>
> [texinfo.tex version 2022-09-15.17]
>
>
> I noticed that for unknown reasons the space width between
> 'Chapter X:' and the following text in the header line varies; see
> attached images. Unfortunately, I can't see any logic
On Thu, Sep 15, 2022 at 04:13:49PM +, Werner LEMBERG wrote:
>
> >> As far as I can see, the last thing not obeying the 'text block' is
> >> the table of contents. I can't see any reason why this is so –
> >> actually, the page number is uncomfortably near to the top line of
> >> the TOC, as
On Thu, Sep 08, 2022 at 05:27:20AM +, Werner LEMBERG wrote:
> As far as I can see, the last thing not obeying the 'text block' is
> the table of contents. I can't see any reason why this is so –
> actually, the page number is uncomfortably near to the top line of the
> TOC, as can be seen on
On Mon, Sep 12, 2022 at 03:43:48AM +0200, Vincent Lefevre wrote:
> The spacing is due to \smartitaliccorrection in the \var definition.
> I suppose that if useful for slanted, it should be disabled for
> slanted typewriter.
Please try the latest commit.
On Sat, Sep 03, 2022 at 01:49:40PM +, Werner LEMBERG wrote:
>
> [texinfo version 2022-09-03.12]
>
>
> Consider the attached example file `cartouche.tex` and the
> corresponding PDF file. As can be seen, the `@cartouche` environment
> sticks out a lot at the top of the page.
>
> For
On Sat, Sep 03, 2022 at 09:53:33PM +0100, Gavin Smith wrote:
> > OK, I thought that @var was always using a slanted typewriter font.
> > But then, this yields another inconsistency!
>
> This is not the case. In fact, @var has always used a slanted non-typewriter
> font whe
On Sat, Sep 03, 2022 at 08:25:17PM +0200, Vincent Lefevre wrote:
> On 2022-09-02 17:42:33 +0100, Gavin Smith wrote:
> > On Fri, Sep 02, 2022 at 05:49:26PM +0200, Vincent Lefevre wrote:
> > > With texinfo.tex 2022-09-01.06, consider
> > >
> > > @deffn Comma
I found bad vertical spacing with the @heading-like commands in the
LaTeX output. It can be seen in the Tips appendix in texinfo.texi, or
here is a minimal example:
\input texinfo
@chapter One
@noindent test test test test test
@example
a
b
c
@end example
@heading Heading
@noindent
On Sat, Sep 03, 2022 at 11:51:32AM +, Werner LEMBERG wrote:
>
> [texinfo version 2022-09-01.06]
>
>
> Consider the following example.
>
> ```
> \input texinfo.tex
>
> foo
>
> @multitable {blubb} {bla}
> @item blubb @tab bla
> @item blubb @tab bla
> @end multitable
>
> bar
>
>
In the LaTeX output we override the plain page style:
% plain page style for part and chapter, which call \thispagestyle{plain}
\renewpagestyle{plain}{\sethead[\thepage{}][][]
{}{}{\thepage{}}}
- so that we have page numbers on chapter pages.
I feel that
On Fri, Sep 02, 2022 at 05:49:26PM +0200, Vincent Lefevre wrote:
> With texinfo.tex 2022-09-01.06, consider
>
> @deffn Command name-min arg-min
> @end deffn
>
> @deffn Command name-min @var{arg-min}
> @end deffn
>
> In printed output (PDF), name-min is printed in typewriter font
> as expected,
On Thu, Sep 01, 2022 at 03:04:53AM +0200, Vincent Lefevre wrote:
> On 2022-08-31 17:46:53 +0100, Gavin Smith wrote:
> > It's all chapter pages that don't have anything in the heading. This
> > was deliberate.
>
> Well, there's the page number in the heading.
>
> With
On Tue, Aug 30, 2022 at 06:27:27PM +0200, Vincent Lefevre wrote:
> With texinfo.tex 2021-04-25.21 (current version in Debian/unstable)
> and 2022-07-27.14 (latest version), even-numbered chapter pages
> no longer have a title in the heading. The manual doesn't seem to
> document such an exception,
On Mon, Aug 29, 2022 at 01:46:06PM +, Werner LEMBERG wrote:
>
> Since `texinfo.tex` doesn't support cropmarks any more, I suggest to
> remove `\outerhsize`, `\outervsize`, and `\topandbottommargin`
> altogether.
>
>
> Werner
>
OK done.
On Fri, Aug 26, 2022 at 10:20:08PM +0200, pertu...@free.fr wrote:
> On Fri, Aug 26, 2022 at 06:37:08PM +0100, Gavin Smith wrote:
> >
> > The LaTeX output will still use variable-width for @var unconditionally and
> > not subject to configuration. Hence there will be an
In the manual there are sections like
@table @code
@item --enable-encoding
@itemx --disable-encoding
@vindex IX--ONE
@vindex IX--TWO
@end table
(IX--ONE was originally --enable-encoding and IX--TWO was --disable-encoding,
but I found it easier to read the dumps for this
On Fri, Aug 26, 2022 at 02:14:27PM +, Werner LEMBERG wrote:
>
> > I've added this as '@set txicodevaristt'. I've tested it with
> > texi2pdf -t '@set txicodevaristt'.
>
> Thanks, this works. Please document it in `texinfo.texi` :-)
>
>
> Werner
>
>
> PS: I still vote for making
On Wed, Aug 24, 2022 at 05:38:08PM +0200, Patrice Dumas wrote:
> Hello,
>
> The sed use in texi2dvi, with comment_iftex could be replaced
> by a direct use of makeinfo, starting with 5.0, released in 16 February
> 2013 (as stated in the comment).
>
> The following call would be the best, to
On Sun, Aug 21, 2022 at 07:59:17PM +, Werner LEMBERG wrote:
>
> > It would be easy to add a switch to texinfo.tex that would switch
> > on/off the old behaviour. It would be used like "@set
> > txicodevarttsl" (probably with a better name).
>
> OK.
I've added this as '@set txicodevaristt'.
On Mon, Aug 22, 2022 at 12:35:44AM +0200, Patrice Dumas wrote:
> Hello,
>
> In all the formats output by texi2any, except in LaTeX which is
> more consistent with TeX, @r, @i, @b, @sansserif and @slanted switch
> back to normal context if in code/monospace context. This is not
> the case in
On Sun, Aug 21, 2022 at 11:14:16PM +0200, pertu...@free.fr wrote:
> On Sun, Aug 21, 2022 at 06:28:11PM +0100, Gavin Smith wrote:
> >
> > It wouldn't do anything for any other output formats, so there shouldn't
> > need to be any changes to texi2any, or any new comm
On Sun, Aug 21, 2022 at 04:54:36PM +, Werner LEMBERG wrote:
>
> >> However, using a Texinfo configuration as suggested in another
> >> e-mail would be a much friendlier solution for than that, which
> >> could even be issued using `texi2pdf`'s `--command` option or using
> >> a `texinfo.cnf`
On Sun, Aug 21, 2022 at 11:24:56AM +, Werner LEMBERG wrote:
>
> [CCing `bug-texinfo` – this was lost by accident, right?]
Yes.
> Two meta-ness levels meet in things like
>
> ```
> Add command line option @code{--jobs @var{n}}, where @var{n} ...
> ```
Here @var{n} outputs in two different
- Forwarded message from Gavin Smith -
Date: Sun, 21 Aug 2022 10:18:39 +0100
From: Gavin Smith
To: Werner LEMBERG
Subject: Re: wrong font shape for `@var` in `@example`
On Sun, Aug 21, 2022 at 05:16:17AM +, Werner LEMBERG wrote:
>
> [texinfo.tex 2022-08-20.19]
>
&g
On Sun, Aug 21, 2022 at 11:59:54AM +0200, pertu...@free.fr wrote:
> This is not directly related to the changes I proposed for @def*
> commands lines. Having @var always be roman with ligatures is Gavin
> decision, although I don't disagree with that decision. This is
> somewhat related to the
On Sat, Aug 20, 2022 at 07:26:37PM +, Werner LEMBERG wrote:
>
> [texinfo version 2022-08-20.18]
>
>
> >> I've had another look at and I've fixed it, so @U can be used for
> >> ASCII characters once again.
> >
> > Thanks for the quick fix.
>
> I said this too early :-)
>
>
> This code
>
On Sat, Aug 20, 2022 at 05:02:44PM +, Werner LEMBERG wrote:
>
> [texinfo.tex version 2022-08-20.16]
>
> > It wasn't as simple as that but I've made the change to use vertical
> > glue and penalties only (following LaTeX 'needspace'). I've
> > committed it and will upload shortly.
>
> Alas,
On Sat, Aug 20, 2022 at 02:23:39PM +0100, Gavin Smith wrote:
> While it's consistent to allow @U to be used for ASCII characters,
> it doesn't appear to offer any benefit. If the code is re-enabled
> the second point here would still need to be fixed.
I've had another look at and I
On Sat, Aug 20, 2022 at 07:17:32AM +, Werner LEMBERG wrote:
>
> [texinfo.tex 2022-08-21.14]
>
> Processing
>
> ```
> \input texinfo
>
> @documentencoding UTF-8
>
> @include ae/lily-651af4bb.texidoc
>
> @bye
> ```
>
> (it's not necessary to actually have an include file) with
>
> ```
>
On Sat, Aug 20, 2022 at 02:24:29PM +0200, Patrice Dumas wrote:
> Hello,
>
> Cross reference with non ascii character fails when the other manual is
> not in the same encoding. I attach an example with an ISO-8859-1 manual
> and an UTF-8 manual, both have the node
> @node chap Cross-ref thé
>
601 - 700 of 2304 matches
Mail list logo
