On Mon, Nov 16, 2020 at 06:58:13PM +, Gavin Smith wrote:
>
> I've attempted to mirror what you've done in the XS code, and updated the
> tests. I still haven't gotten around to working out how to run the tex4ht
> and latex2html tests, so could you regenerate those and check the changes
>
On Wed, Nov 18, 2020 at 09:47:09PM +, Gavin Smith wrote:
>
> I doubt that relative names beginning "../" were much considered
> when @image was implemented (or even file names with directory parts
> at all).
>
> I haven't thought of a clear answer for this issue yet. I think that
> for
On Tue, Nov 17, 2020 at 01:47:41PM +0100, Christopher Dimech wrote:
> > > @image{../../Ideogr/Ch03b--Chmed/igc03--01--Sicl--CircAmRg,8cm,8cm,AltText,png}
> > >
> > > Furthermore, you cannot put ".png" as the fifth argument because for html
> > > that will
> > > fail. You have to put "png",
On Sun, Nov 22, 2020 at 09:02:17AM +, Gavin Smith wrote:
> On Sun, Nov 22, 2020 at 12:46:35AM +0100, Patrice Dumas wrote:
> > I think that
> > the point is to copy the image file from where it is found to the
> > destination directory.
>
> Could this break the bu
;
>
>
>
> > Sent: Thursday, November 12, 2020 at 1:35 PM
> > From: "Christopher Dimech"
> > To: "Patrice Dumas"
> > Cc: "help-texinfo gnu"
> > Subject: Re: MathJax problem with \gdef
> >
> > > Sent: Thursday, No
On Thu, Nov 12, 2020 at 11:57:47AM +0100, Christopher Dimech wrote:
> Have done more tests with @tex, @math, and @displaymath.
>
> \gdef is working for pdf output but not with MathJax.
I am not an expert in MathJax, but I think that MathJax only interpret
the LaTeX/TeX locally, so cannot know
On Thu, Nov 12, 2020 at 04:16:31PM +0100, Christopher Dimech wrote:
> How about
>
>
> @tex
> $$ {d \over dt} u(t) = v(t) $$
> $$ \int {d \over dt}\, u(t)\, dt = \int v(t)\, dt + C $$
> $$ u(t) = \int v(t)\, dt + C $$
> @end tex
>
> I find no way except to split it up using three
On Sat, Nov 14, 2020 at 06:26:07PM +0100, Christopher Dimech wrote:
> Still for productivity's sake, output is better than no output.
> This is especially important for large works, where the author
> does not want complete failure because of some inconsistency.
It really depends. In particular
On Sun, Nov 15, 2020 at 12:40:05AM +0100, Christopher Dimech wrote:
> What is the command for displaying images for html output. When I use
> @image, the image is only being displayed when using texi2pdf.
It is @image. It is documented here
On Sun, Nov 15, 2020 at 05:12:13PM +0100, Christopher Dimech wrote:
>
> But now I have understood the problem,
>
> Although the file exists at
> ../Ideogr/Ch03b--Chmed/igc03--01--Sicl--CircAmRg.png
> because the html index file resides in a subdirectory generated by texi2any,
> the
> code got
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
On Tue, Oct 20, 2020 at 04:53:11PM +0100, Gavin Smith wrote:
>
> Possibly, @novalidate was supposed to do this, as well as checking
> cross-references:
>
> https://www.gnu.org/software/texinfo/manual/texinfo/html_node/Pointer-Validation.html
>
> > Instead, makeinfo checks that the tree
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
On Tue, Oct 20, 2020 at 03:02:58PM +0200, Christopher Dimech wrote:
> I have sent you a small test, it is not with anchors with with simple nodes
> and
> sections:
>
> I am getting the following output from makeinfo
>
For some reason now the 'unreferenced node' messages have disappeared,
but
On Tue, Oct 20, 2020 at 05:30:15PM +0200, Christopher Dimech wrote:
> Understood. Had thought it exists but not documented, but reading your
> comment again, you are correct. Would one be able to call it inside the
> source code?
Currently customization variables can only be set on the command
Hello,
It is not enough to set ICONS, you also need to specify which image to
use for which button. An example is in the source tree, in
tp/t/init/icons.init:
https://git.savannah.gnu.org/cgit/texinfo.git/tree/tp/t/init/icons.init
The images used in the example come from texi2html, but we did
On Thu, Jan 07, 2021 at 12:39:16PM +, Gavin Smith wrote:
> On Wed, Jan 06, 2021 at 05:09:24PM +0100, michael-franz...@gmx.com wrote:
> > I would like to use Roman Numerals (i, ii, iii, iv) for @enumerate. The
> > manual does
> > describe this possibility.
>
> Somebody would have to
On Tue, Jun 22, 2021 at 07:21:33PM +0200, Christopher Dimech wrote:
> Am running a macro that continues on the next line, but pdfetex quits and
> exits
> with bad status. Should this problem not have been fixed before?
It probably depends on the macro and what it expands to. You would need
to
On Wed, Jun 23, 2021 at 04:12:24PM +0200, Christopher Dimech wrote:
>
> (./txiversion.tex
> ! I can't find file `texinfo.tex'.
> l.1 \input texinfo.tex
Could it be because you didn't install it? Instruction are in INSTALL.
--
Pat
On Wed, Jun 23, 2021 at 08:52:44PM +0200, Christopher Dimech wrote:
>
> Quite likely. I compare it with how I customarily install other
> development versions in Gnu for testing. There seem to be many
> considerations when installing texinfo.
I think everybody agrees that having to install
Hello,
On Mon, Jun 21, 2021 at 08:37:48PM +0200, henri-bi...@francemel.fr wrote:
>
> I went through the manual but have not found any information about how to
> output
>
> mathematical expressions for html output.
It should be in the next release, which is due soon, with the
customization
On Tue, Jun 22, 2021 at 12:19:01AM +0200, Patrice Dumas wrote:
>
> If you have an example, I could test with the development version.
There is actually already a text with \gdef. It actually works with
latex2html and partially with tex4ht, and it doesn't work with MathJax.
--
Pat
On Tue, Jun 22, 2021 at 12:59:43AM +0200, henri-bi...@francemel.fr wrote:
> It is important for that to work also with MathJax, because I had been using
>
> \def for global definition of mathematical structures that @tex could
> understand.
>
>
>
> The advantage of MathJax is the ability to
On Thu, Jun 24, 2021 at 03:12:30PM +0200, Christopher Dimech wrote:
>
> Have been running the development version of texi2pdf with the following
> command.
>
> /home/hagbard/Admir/bin/texinfo/bin/texi2pdf 06a-amcoh.texi
>
> bin/tex/texinfo has been created and includes tekinfo.text as expected
On Fri, Jun 25, 2021 at 06:59:38AM +0100, Gavin Smith wrote:
> Apart from creating an ls-R file I am not sure what is wrong. Did
> texinfo.tex actually get installed under /usr/local/share/texmf/tex/texinfo?
I also do not understand what's going on, as the kpathsea path looks
good, and there is
On Thu, Jun 24, 2021 at 11:53:36PM +0200, Christopher Dimech wrote:
>
> > export TEXINPUTS=/usr/local/share/texmf:$TEXINPUTS
> Error Occurs
>
> hagbard@fuckup:
> + ~/01cuneus/tdr/06ch
> pdfetex 06a-amcoh.texi
> This is pdfTeX, Version 3.14159265-2.6-1.40.18 (TeX Live 2017/Debian)
> (preloaded
> Sent: Thursday, May 13, 2021 at 12:47 AM
> > From: "Patrice Dumas"
> > To: pie...@caramail.com
> > Cc: "help-texinfo gnu"
> > Subject: Re: @chapter starting at specified number
> >
> > Hello,
> >
> > Not sure that it corresponds
Hello,
Not sure that it corresponds to your use, but @raisesections and @lowersections
could be of use:
https://www.gnu.org/software/texinfo/manual/texinfo/html_node/Raise_002flower-sections.html
On Wed, May 12, 2021 at 04:05:17AM +0200, pie...@caramail.com wrote:
> Currently, using @chapter
On Sat, Sep 11, 2021 at 11:20:00PM -0400, Mike Frysinger wrote:
> i couldn't easily find an answer in the archives or manual, so feel free to
> point me to docs or discussions that i missed. surely this can't be a new
> idea that i managed to come up with myself. or there's a good reason that
>
On Sun, Sep 12, 2021 at 03:09:30PM -0400, Mike Frysinger wrote:
>
> based on the manual description, it sounds like the tree structure is
> accessible already since that's how the @contents are generated, and
> it's able to output that just fine. so i (naively) assume that adding
> an automatic
Resending, as for some reason Mike may not be in the recipients...
On Sun, Sep 12, 2021 at 03:09:30PM -0400, Mike Frysinger wrote:
>
> based on the manual description, it sounds like the tree structure is
> accessible already since that's how the @contents are generated, and
> it's able to
On Sat, Sep 18, 2021 at 08:44:19PM -0700, Sarah Morgensen wrote:
> Hello,
>
> Is there a way to avoid a non-functional link in the HTML output when
> there is no htmlxref.cnf entry for an xref?
The idea behind the specification of the HTML cross references file
destinations, when there is no
On Sun, Oct 10, 2021 at 10:18:39AM +, Alan Mackenzie wrote:
> Hello, Jacob.
>
> I have not yet figured out how to add a new command line option. I
> envisage the new option being called --enable-utf8-punctuation, with a
> default value of ON.
>
> So, my question. Are the maintainers of
On Mon, Oct 11, 2021 at 11:35:06AM +, Alan Mackenzie wrote:
> Hello, Gavin.
>
>
> Apologies for not being all that clear in my initial post. I hope I've
> now made it clear what I'm asking for - as an option, of course.
> --disable-encoding does not do what I want - it squeezes _all_
>
On Sat, Dec 18, 2021 at 06:05:53PM -0800, Robert Dodier wrote:
> Hi Pat, you mentioned it's not clear what I'm trying to do.
>
> The Texinfo for such items looks like
>
> @deffn foo (x, y, z)
>
> Yadda yadda yadda, foo bar baz quux mumble blurf.
>
> @opencatbox
> @category{Foobar}
>
On Fri, Dec 17, 2021 at 08:37:11PM -0800, Robert Dodier wrote:
> Hi Pat, thanks for your message.
>
> It doesn't look like the --ifsomething / --no-ifsomething options will
> help. Essentially the problem is that the @ commands which are going
> to end up as HTML need to be kept, without actually
On Tue, Dec 21, 2021 at 03:05:18PM -0500, Alfred M. Szmidt wrote:
>However, please consider whether it would be better to set this option on
>the command line rather than inside the Texinfo file itself as it may not
>be the best place for controlling details of the output.
>
> An idea
On Mon, Oct 11, 2021 at 08:47:40PM +, Alan Mackenzie wrote:
>
> I think it is also undocumented that texi2any puts Unicode punctuation
> characters around things like @code{foo}. It sometimes uses ASCII
> punctuation characters instead. Which it uses and when, I think is also
>
On Mon, Oct 11, 2021 at 02:22:57PM +, Alan Mackenzie wrote:
>
> Again, I am asking for an option which would give a clean, clear way not
> to output Unicode >0x7f for the Texinfo formatting characters, whilst
> not affecting any of the other facilities for manipulating non-ASCII
> characters.
On Tue, Oct 26, 2021 at 11:21:39AM -0500, Eric Blake wrote:
> On Tue, Oct 26, 2021 at 02:30:26AM +0200, 4dr14n31t0r Th3 G4m3r wrote:
> > The output documented is not what you get from executing the m4 commands as
> > documented. See https://www.gnu.org/software/m4/manual/m4.html#Dumpdef
>
>
On Sun, Dec 12, 2021 at 11:00:12PM -0800, Robert Dodier wrote:
> Hi, I hope all is well with you-all.
>
> First of all, am I reinventing a wheel here? Is there already an
> implementation of a category system for Texinfo? There wasn't when I
> got started but that was a long time (more than 10
On Wed, Dec 15, 2021 at 09:20:32PM -0800, Robert Dodier wrote:
> Hi Patrice, thanks a lot for your message.
>
> I looked into the possibility of a Texinfo --> Texinfo XML -->
> mogrifications --> Texinfo pipeline, but it looks like it's not going
> to work. The translation from Texinfo to XML is
On Tue, Jul 13, 2021 at 05:22:38AM +0200, lisa-as...@perso.be wrote:
>
> Is it correct to say that when using `@ref ` there are only two possibilities.
>
>
>
> (1) reference to a node
>
> (2) reference to an anchor.
There are also references to @float (label is flot second argument).
--
On Mon, Mar 14, 2022 at 12:55:59PM +0100, H. Fernandes wrote:
> Hi,
>
> Should not the option be to the other way to preserve the default behavior.
The new behaviour is considered to better for two reasons, one is that
the mini-tocs are considered to have a better usability than menus, menus
On Wed, Aug 30, 2023 at 06:54:45AM +, Oleander wrote:
> As far as I know latex3 does not support exporting to html, epub,
> ascii and I need those formats. I should have explained it better but
> I don't need all the formatting options latex offers since I mostly
> write prose with some
On Mon, Nov 06, 2023 at 07:29:50PM +, Gavin Smith wrote:
> On Sun, Nov 05, 2023 at 11:30:42AM +, Ihor Radchenko wrote:
> > May someone please explain the correct usage of @anchor in the above
> > example and why the warning is being thrown?
>
> I don't think there's really much wrong with
Follow-up Comment #6, bug #64752 (project octave):
It is possible, there is a direction that corresponds to next in reading
order, called 'Forward' (and there is one for previous in reading order, which
is called 'Back'). Now, the difficulty is how to add it to the header buttons.
I attach an
On Thu, Apr 21, 2022 at 10:48:50AM +0200, Yannick Sirjean wrote:
> Hi everyone,
> I'm newbie in texinfo system.
> I don't know where to find the warnings and errors list (and the
> description) for the makeinfo program. It's better to know them to
> understand "errors" in the "code".
There is no
On Thu, Jun 09, 2022 at 10:20:57AM -0500, Perry Smith wrote:
> Hi,
>
> I found this thread in the bug-texinfo mailing list[1]. I’m wanting to
> format the org-mode info file into ePub. Indeed, I’d like to reformat many
> of the info files into ePub assuming that I can find a tool chain that
Hello,
A new version, no functional change, but code could be more clear
like that.
On Mon, Oct 10, 2022 at 09:40:34AM +0200, Patrice Dumas wrote:
> Hello,
>
> The API changed again, for the new API, the attached init file should be
> ok.
>
> --
> Pat
> # Make the o
On Sat, Oct 22, 2022 at 06:23:43PM +0200, Jean Abou Samra wrote:
> Hi,
>
> \command
>
> Note: command
>
> Note the missing backslash after "Note:".
>
> Unfortunately, LilyPond is still using texi2html, and it is
> difficult for us to switch to makeinfo --html aka. texi2any.
We are preparing
On Tue, Sep 13, 2022 at 08:14:48PM -0400, Stefan Monnier wrote:
>
> There's something I don't understand about @include:
>
> Say, I have:
>
> doc/foo.texi
> doc/gpl.texi
> bar.texi
>
> if my `foo.texi` has
>
> @include gpl.texi
> @include ../bar.texi
>
> I will be able to
On Wed, Sep 14, 2022 at 10:16:16AM -0400, Stefan Monnier wrote:
> > Right now, I can't think of a way to make this happen. The only
> > thing I can think of would be to change the code to consider that
> > only paths with leading . are considered differently.
>
> Actually, from where I stand,
On Thu, Sep 15, 2022 at 03:35:26PM -0400, Stefan Monnier wrote:
> > Have you tried the -I option?
>
> I had not, but I just tried and that doesn't help: apparently when
> the file starts with "." it's not searched along the list of include
> directories but only relative to pwd (whereas I'd need
On Sun, Sep 25, 2022 at 10:18:31PM -0700, Robert Dodier wrote:
> On Sat, Sep 24, 2022 at 2:07 AM Patrice Dumas wrote:
>
> > On Tue, Sep 20, 2022 at 04:31:08PM -0700, Raymond Toy wrote:
> > > Is it possible to customize what @var does (for info files) without
> > >
On Tue, Sep 20, 2022 at 04:31:08PM -0700, Raymond Toy wrote:
> Is it possible to customize what @var does (for info files) without
> redefining @var?
> Maxima redefines @var to
>
> @macro var {expr}
> <\expr\>
> @end macro
>
> This breaks things like
>
> @table @var
One possibility could be to
On Tue, Sep 20, 2022 at 04:31:08PM -0700, Raymond Toy wrote:
> Is it possible to customize what @var does (for info files) without
> redefining @var?
> Maxima redefines @var to
>
> @macro var {expr}
> <\expr\>
> @end macro
This is not recommended, and could even be forbidden, in my opinion, to
On Mon, Oct 10, 2022 at 09:12:40AM -0700, Raymond Toy wrote:
> Thanks for the new version. I assume this will probably be the API for the
> next texinfo release?
Yes. I do not think that the API will change again, I think that the
new release is for sometime soon.
> (I tried to require at
Hello,
The API changed again, for the new API, the attached init file should be
ok.
--
Pat
# Make the output file names consist of the base name followed by a number.
use strict;
# REMARK: if more than one manual is processed, $file_nr, %reference_file_name_file_nr
# and
On Sun, Aug 14, 2022 at 07:18:45AM -0700, Raymond Toy wrote:
> For a while maxima has been customizing the html file names that makeinfo
> uses. Basically, the file names are of the form maxima_nnn.html or
> maxima_toc.html for the table of contents.
>
> I would like to be able to change this so
On Sun, Aug 14, 2022 at 07:18:45AM -0700, Raymond Toy wrote:
> For a while maxima has been customizing the html file names that makeinfo
> uses. Basically, the file names are of the form maxima_nnn.html or
> maxima_toc.html for the table of contents.
>
> I would like to be able to change this so
On Sun, Aug 14, 2022 at 11:50:12AM -0700, Raymond Toy wrote:
> On Sun, Aug 14, 2022 at 9:46 AM Patrice Dumas wrote:
>
> > On Sun, Aug 14, 2022 at 07:18:45AM -0700, Raymond Toy wrote:
> > > For a while maxima has been customizing the html file names that makeinfo
> > &
On Sun, Aug 14, 2022 at 07:18:45AM -0700, Raymond Toy wrote:
> For a while maxima has been customizing the html file names that makeinfo
> uses. Basically, the file names are of the form maxima_nnn.html or
> maxima_toc.html for the table of contents.
>
> I would like to be able to change this so
On Wed, Jan 04, 2023 at 05:08:09PM +0700, Nutchanon Wetchasit wrote:
> Hello,
>
> So what I would like to know is: what is the last version of GNU Texinfo
> that its `makeinfo` or `texi2html` utility produces SGML-style HTML output
> which DOES NOT make _any_ use of HTML construct introduced
On Tue, Jan 10, 2023 at 05:57:29PM +0100, Arsen Arsenović wrote:
> Hi Eli,
>
> Eli Zaretskii writes:
>
> > I'd expect downstream distros to do that already. If they don't,
> > maybe Texinfo should (although I'm not sure how to arrange for that in
> > a way that won't make the job of Texinfo
On Wed, Nov 23, 2022 at 09:31:07PM +, Gavin Smith wrote:
>
> I've been working on this, and with my current code I have, with the
> following input:
>
> @table @asis
> @item AAA
> @itemx BBB
> @vindex index1
> @vindex index2
> @vindex index3
> Hello
>
>
On Wed, Nov 23, 2022 at 09:31:07PM +, Gavin Smith wrote:
> I made this change by adding a new conversion for the 'table_term' type
> in HTML.pm, which outputs the , so that everything inside the
> 'table_term' (@item, @itemx and @?index) is output inside the .
>
> This might be the wrong way
On Mon, Nov 21, 2022 at 08:35:01PM -0600, Jacob Bachmeyer wrote:
> Patrice Dumas wrote:
> > Currently yes. But indeed, it would be natural in that case to follow
> > @deffn by @defvarx. I think that it would not be hard to implement that
> > in texi2any, but I am not sure
On Thu, Nov 24, 2022 at 12:07:47AM +0100, Patrice Dumas wrote:
> of the elements, but for a tree that is given. The TREE_TRANSFORMATIONS
> are much better suited for changing the tree.
As a side note the relate_index_entries_to_table_entries_in_tree
transformation replace index entris in
On Tue, Nov 22, 2022 at 07:21:05AM -0800, Raymond Toy wrote:
> On Tue, Nov 22, 2022 at 12:59 AM Patrice Dumas wrote:
>
> I personally find it kind of weird to mix deffn and defvrx in the same
> block. If I were writing this from scratch, I would have separated them.
> But this
On Fri, Nov 25, 2022 at 10:12:21PM +, Gavin Smith wrote:
> There may be a related issue with associating index entries with other
> constructs. For example, a paragraph:
>
> @cindex paragraph 1
> This is a paragraph.
>
> outputing in HTML as
>
>
> This is a paragraph.
>
On Fri, Nov 25, 2022 at 10:12:21PM +, Gavin Smith wrote:
> On Tue, Nov 22, 2022 at 09:49:33PM +, Gavin Smith wrote:
> > On Tue, Nov 22, 2022 at 10:23:24PM +0100, Patrice Dumas wrote:
> > > Maybe not important if there are other changes afterwards, but with the
>
On Fri, Nov 25, 2022 at 10:12:21PM +, Gavin Smith wrote:
> On Tue, Nov 22, 2022 at 09:49:33PM +, Gavin Smith wrote:
> > On Tue, Nov 22, 2022 at 10:23:24PM +0100, Patrice Dumas wrote:
> > > Maybe not important if there are other changes afterwards, but with the
>
On Sat, Nov 26, 2022 at 03:58:59PM +, Gavin Smith wrote:
> On Thu, Nov 24, 2022 at 12:07:47AM +0100, Patrice Dumas wrote:
> > It is also possible to do something when the element is first
> > encountered, with $default_types_open{'table_term'} =
> > \&_open_table_t
On Sat, Nov 26, 2022 at 03:58:59PM +, Gavin Smith wrote:
> On Thu, Nov 24, 2022 at 12:07:47AM +0100, Patrice Dumas wrote:
> > It is also possible to do something when the element is first
> > encountered, with $default_types_open{'table_term'} =
> > \&_open_table_t
On Sat, Nov 26, 2022 at 04:45:24PM +, Gavin Smith wrote:
> On Wed, Nov 23, 2022 at 11:56:30PM +0100, Patrice Dumas wrote:
> > As I said before I do not think that it is right to merge the first
> > index entry with the @item, but that's a separate issue.
&g
On Sat, Nov 26, 2022 at 08:18:43PM +, Gavin Smith wrote:
> On Sat, Nov 26, 2022 at 03:59:00PM +, Gavin Smith wrote:
> > I still haven't put index entries before the very first
> > @item in a @table inside the - I need to do something with the
> > 'before_item' element.
>
> It should be
On Sat, Nov 26, 2022 at 05:49:54PM +0100, Arsen Arsenović wrote:
>
> Gavin Smith writes:
>
> > I have nuked the relate_index_entries_to_table_entries transformation
> > which made this association. According to the changelog, I introduced
> > this code in November 2020. This may remove some
On Sat, Nov 26, 2022 at 05:49:54PM +0100, Arsen Arsenović wrote:
>
> I wanted to give implementing that an attempt, but while trying to
> configure and build the texinfo trunk, I get:
This should be fixed by
On Sat, Nov 26, 2022 at 11:11:52PM +0100, Patrice Dumas wrote:
> It is a help for formats that have restrictions on what can be in
> tables. Maybe would be a good think to check that the DocBook is also
> valid.
Seems like that it is better as index entries are better in in
Do
On Tue, Nov 22, 2022 at 09:49:31PM +, Gavin Smith wrote:
> > > I think deciding on the right output for the existing usage and
> > > implementing such is more important than devising and implementing
> > > new language constructs.
> >
> > Sure, except that for that case, I do not think that
On Tue, Nov 22, 2022 at 09:49:31PM +, Gavin Smith wrote:
> On Tue, Nov 22, 2022 at 10:23:24PM +0100, Patrice Dumas wrote:
> > Maybe not important if there are other changes afterwards, but with the
> > change, in HTML, the result is now invalid, as the index entries end up
>
On Tue, Nov 22, 2022 at 09:11:58PM +, Gavin Smith wrote:
>
> I've committed a change to move the index entries to the 'table_term'
> element, and updated the code in the 'relate_index_entry_to_table_entry'
> tree transformation to look for an index entry in the new place. My
> intention is
On Mon, Nov 21, 2022 at 03:29:29PM +0100, Arsen Arsenović wrote:
>
> The solution of using an indexing table command (like @vtable) seems to
> be the better one generally, though.
It does not solve the case of wanting more than one index entry per
table item.
> I see now that the generic case
On Mon, Nov 21, 2022 at 11:37:10AM -0800, Raymond Toy wrote:
> However, I've run into a small issue. The original Scribe did things like:
>
> @defun[fun {check-region-query-size}, args {@i[region]}]
> @defhvar1[var {Region Query Size}, val {30}]
> @enddefun
>
> This basically looks like as if
On Mon, Nov 21, 2022 at 08:49:34PM +, Gavin Smith wrote:
> My current work is at the bottom of the email. This will need more testing
> and also implementing in the XS parser, so it will take me at least few days
> to
> finish.
It could also be a tree transformation that is applied after
On Mon, Nov 21, 2022 at 10:04:16PM +0100, Patrice Dumas wrote:
> To have the 'pedantic' variable index entry associated with the
> '-pedantic' table term label. Instead of @item, it could be another
> command, like @itemindex, so something like
>
> @itable @code
> @ite
On Sun, Nov 27, 2022 at 10:34:15AM +, Gavin Smith wrote:
> On Sat, Nov 26, 2022 at 11:11:52PM +0100, Patrice Dumas wrote:
> > I spotted two cases for which the index entry could also be with the
> > table term (in xtables inter_item_commands_in_table test), with a
> >
On Wed, Apr 05, 2023 at 11:03:36AM +0200, to...@tuxteam.de wrote:
>
> I was dreaming of a world where both doc systems converge
> in a way their respective users don't notice, and we end
> up with a Grand Unified Documentation (GUD) for all things
> free.
Because of the differences in design, as
On Sat, Feb 11, 2023 at 11:59:07AM +, Gavin Smith wrote:
>
> I've commited changes to texinfo.tex to introduce @defblock, @deflinex
> and @deftypelinex. @deflinex is like @deffnx and @deftypelinex is like
> @deftypefnx. The names of these could change, for example to remove the 'x'
> at the
On Fri, Feb 10, 2023 at 01:35:15PM +, Gavin Smith wrote:
> On Thu, Feb 02, 2023 at 07:14:53PM +, Gavin Smith wrote:
> > I imagine that there would be another type of block
> > like @defblock ... @end defblock which could contain the @def lines,
> > which would allow the same formatting
On Sun, Jul 16, 2023 at 02:46:10PM -0600, Karl Berry wrote:
> I seem to recall that in the past there was a warning when a
> normally-structured manual had a missing menu entry? That doesn't seem
> to happen now, and I failed to find anything in the manual. Am I just
> going crazy :)?
A warning
On Tue, May 23, 2023 at 09:58:47AM +0100, Joao Dinis wrote:
> Hi,
>
> I'm a newbie on texinfo, using to write an users manual.
> In that process I found the need to detail a configuration file by showing a
> few lines of it, followed by a description of what those lines mean, then
> showing a few
On Mon, Jan 22, 2024 at 08:48:03AM +, Jean-Christophe Helary wrote:
> > It's questionable whether this would be a correct use of
> > and or not. The online DocBook documentation says,
> >
> > "The AuthorGroup element is a wrapper around multiple authors or other
> > collaborators."
> >
>
On Sat, Jan 20, 2024 at 06:08:07PM +, Jean-Christophe Helary wrote:
> > On Jan 21, 2024, at 3:01, Patrice Dumas wrote:
> >
> > Not necessarily very important, but UTF-8 is the default input encoding
> > since Texinfo 6.7 (23 September 2019), depending on the Texinfo
On Sat, Dec 30, 2023 at 04:28:02PM +0100, Hilaire Fernandes wrote:
> Hi folks,
>
> I just upgraded some documentation to 7.x.
>
> How can I avoid the mini-toc in the middle of the html document. See in the
> examples below. The first example is really confusing.
How the 'menus' are formatted
On Sat, Dec 30, 2023 at 04:50:12PM +0100, Hilaire Fernandes wrote:
> Hi,
>
> Since upgrading to texinfo 7.0.3, when rendering html, the table of contents
> always appears after the copying, even if instructed differently.
Indeed, the default for CONTENTS_OUTPUT_LOCATION is now 'after_top' in the
On Sat, Jan 06, 2024 at 09:37:03AM +, Jean-Christophe Helary wrote:
>
> > But, for such links to work, we
> > need a facility to tell the Info reader that when a link goes to a
> > manual named FOO.info, it should visit FOO-LANG.info instead. Again,
> > something that involves a change in
On Thu, Jan 11, 2024 at 08:09:28AM +0200, Eli Zaretskii wrote:
> > Date: Wed, 10 Jan 2024 21:52:23 +0100
> > From: Patrice Dumas
> > Cc: Eli Zaretskii , Stefan Kangas ,
> > Vincent Belaïche ,
> > emacs-de...@gnu.org, r...@gnu.org, help-texinfo@gnu.org
>
On Thu, Jan 11, 2024 at 05:08:28PM +0200, Eli Zaretskii wrote:
> This is a much more complex solution, and it has some problematic
> aspects: it requires a network connection and some users consideer
> such features an annoyance.
Of course, and not only that, it also requires a way to know which
101 - 200 of 213 matches
Mail list logo
