On Wed, Jul 09, 2025 at 06:18:15AM +, Werner LEMBERG wrote:
>
> Hello Patrice and Gavin,
>
>
> thanks for your answers.
>
> >> Why ``? I consider this surprising since the item description
> >> of a menu entry (i.e., the third part of an entry) is not output
> >> with ``.
> >
> > The idea
On Wed, Jul 09, 2025 at 06:36:08AM +, Werner LEMBERG wrote:
> Maybe you can provide a list of the most important CSS changes, or
> maybe add a section that describes how to do the transition to Texinfo
> 7.0 and newer?
Here is what is in tta/TODO (which is more notes than TODO). We have
not f
On Mon, Jun 30, 2025 at 04:51:24PM +0100, Gavin Smith wrote:
> I am not a fan of the idea of adding a Local Variable for
> this. Space is limited in that section. From Info.pm:
>
> # Note: Info readers expect the Local Variables section to be
> # under 1000 bytes in length so not many va
On Mon, Jun 30, 2025 at 02:47:01PM +0300, Eli Zaretskii wrote:
> > Date: Sun, 29 Jun 2025 18:59:22 +0200
> > From: pertu...@free.fr
> >
> > What about adding a 'Local Variables' with the name of the first node
> > with indices with makeinfo and using that instead of "Index" in nodes
> > names to d
On Sat, Jun 28, 2025 at 08:53:21PM +0100, Gavin Smith wrote:
> On Sat, Jun 28, 2025 at 10:23:59PM +0300, Eli Zaretskii wrote:
> > > From: Gavin Smith
> > > Date: Sat, 28 Jun 2025 19:54:36 +0100
> > >
> > > I also don't think it is a huge restriction to have "Index" in the
> > > node name. Non-En
On Sat, Jun 28, 2025 at 09:45:03PM +0100, Gavin Smith wrote:
> And now I have warnings with this manual (patch at the end of this mail):
>
> $ TEXINFO_XS_STRUCTURE=0 ../tta/perl/texi2any.pl info.texi
> info.texi:461: warning: unexpected node `Help-]' in menu
> info.texi:462: warning: unexpected no
On Wed, Mar 12, 2025 at 12:40:54AM +0100, pertu...@free.fr wrote:
> On Tue, Mar 11, 2025 at 09:22:55PM +, Gavin Smith wrote:
> > On Tue, Mar 11, 2025 at 10:02:25AM +0100, pertu...@free.fr wrote:
> > > On Mon, Mar 10, 2025 at 07:28:54PM +, Gavin Smith wrote:
> > > > Isn't that changing the p
On Tue, Mar 11, 2025 at 09:22:55PM +, Gavin Smith wrote:
> On Tue, Mar 11, 2025 at 10:02:25AM +0100, pertu...@free.fr wrote:
> > On Mon, Mar 10, 2025 at 07:28:54PM +, Gavin Smith wrote:
> > > Isn't that changing the purpose of --transliterate-file-names?
> > >
> > > Before: "texi2any --tra
On Sun, Mar 02, 2025 at 09:48:26AM +, Gavin Smith wrote:
> as if the following were done instead:
>
> @node Chapter
> @chapter Chapter
>
> @subsubheading Topic
>
> @node Section
> @section Section
>
> Here, the @subsubheading is just producing output (just like regular
> parag
On Sun, Mar 09, 2025 at 12:33:40PM +, Gavin Smith wrote:
> >
> > What I plan to do is:
> > * name for links to external nodes is the default one independently of
> > customization variables. If users ask for it, we can add to htmlxref
> > hello type translit
> > * name for redirecti
On Mon, Mar 10, 2025 at 07:28:54PM +, Gavin Smith wrote:
> On Mon, Mar 10, 2025 at 02:33:40PM +0100, pertu...@free.fr wrote:
> > On Sun, Mar 09, 2025 at 12:33:40PM +, Gavin Smith wrote:
> > > >
> > > > What I plan to do is:
> > > > * name for links to external nodes is the default one inde
On Sun, Mar 02, 2025 at 09:48:26AM +, Gavin Smith wrote:
> On Sat, Feb 15, 2025 at 01:17:43PM +, Werner LEMBERG wrote:
> >
> > > I propose that, if USE_NEXT_HEADING_FOR_LONE_NODE is set, the
> > > @*heading appearing after a @node be treated as much as possible
> > > like a sectioning comm
On Mon, Mar 03, 2025 at 06:09:31PM +, Gavin Smith wrote:
> On Sun, Mar 02, 2025 at 10:27:39PM +0100, pertu...@free.fr wrote:
> > We should have a way to change the format if needed. We cannot have the
> > same format forever if it is not adequate.
>
> The htmlxref.cnf format is good enough fo
On Mon, Mar 03, 2025 at 08:11:29PM +, Gavin Smith wrote:
> > I don't reproduce that, I think that the issue is probably that a file
> > is read twice, rather than warnings being emitted twice per file.
> > Where/how/what do you call to get that result, and where are the
> > htmlxref.d directori
On Sun, Mar 02, 2025 at 07:33:45PM +, Gavin Smith wrote:
> On Sun, Mar 02, 2025 at 04:58:09PM +0100, pertu...@free.fr wrote:
>
> > > (However, I'm not certain that .translit etc. suffixes would be the
> > > end of augmenting the htmlxref.cnf format, so we should think if there
> > > are any ot
On Sun, Mar 02, 2025 at 02:19:26PM +, Gavin Smith wrote:
> On Sun, Mar 02, 2025 at 12:59:27PM +0100, pertu...@free.fr wrote:
> > On Sun, Mar 02, 2025 at 11:43:37AM +, Gavin Smith wrote:
> > > On Sun, Mar 02, 2025 at 12:27:49PM +0100, pertu...@free.fr wrote:
> > > Could we look at extending
On Sun, Mar 02, 2025 at 02:19:26PM +, Gavin Smith wrote:
> hello typetranslit
> hello mono${GS}/hello/manual/hello.html
> hello node${GS}/hello/manual/html_node_node/
> hello node.translit ${GS}/hello/manual/html_node_translit/
>
> then I g
On Sun, Mar 02, 2025 at 11:43:37AM +, Gavin Smith wrote:
> On Sun, Mar 02, 2025 at 12:27:49PM +0100, pertu...@free.fr wrote:
> Could we look at extending the htmlxref.cnf format?
>
> As well as mono/chapter/section/node, like:
>
> GS = ${G}/software
> hello mono${GS}/hello/manua
On Sun, Mar 02, 2025 at 12:02:25PM +0100, pertu...@free.fr wrote:
> On Sun, Mar 02, 2025 at 09:48:26AM +, Gavin Smith wrote:
> > On Sat, Feb 15, 2025 at 01:17:43PM +, Werner LEMBERG wrote:
> > >
> > > > I propose that, if USE_NEXT_HEADING_FOR_LONE_NODE is set, the
> > > > @*heading appeari
On Sun, Mar 02, 2025 at 09:06:27AM +, Gavin Smith wrote:
> On Sun, Mar 02, 2025 at 12:57:40AM +0100, pertu...@free.fr wrote:
> > On Sat, Mar 01, 2025 at 08:09:57PM +, Gavin Smith wrote:
> > > ADD_TRANSLITERATED_REDIRECTION_FILES would be fine. I guess it could be
> > > taken to imply that
On Sun, Mar 02, 2025 at 09:48:26AM +, Gavin Smith wrote:
> On Sat, Feb 15, 2025 at 01:17:43PM +, Werner LEMBERG wrote:
> >
> > > I propose that, if USE_NEXT_HEADING_FOR_LONE_NODE is set, the
> > > @*heading appearing after a @node be treated as much as possible
> > > like a sectioning comm
On Sat, Mar 01, 2025 at 08:09:57PM +, Gavin Smith wrote:
> ADD_TRANSLITERATED_REDIRECTION_FILES would be fine. I guess it could be
> taken to imply that these are additional files that are being added.
This is implemented. I think that we could keep this customization
option for some years,
On Sat, Mar 01, 2025 at 06:56:28PM +, Gavin Smith wrote:
> > We need another variable, and we should document that it is transitory
> > and that we will remove it someday, while TRANSLITERATE_FILE_NAMES
> > should remain.
> >
> > What about ADD_NODES_REDIRECTIONS_TRANSLITERATED?
>
> That name
On Sat, Mar 01, 2025 at 05:24:29PM +, Gavin Smith wrote:
> On Wed, Feb 12, 2025 at 01:45:37AM +0100, pertu...@free.fr wrote:
> > On Tue, Feb 11, 2025 at 10:06:54PM +, Gavin Smith wrote:
> > > So it seems to me that this transliteration produces bad results in many
> > > cases and should be
On Mon, Feb 24, 2025 at 10:05:23PM +0100, pertu...@free.fr wrote:
> I will implement then. It will apply to Info output too.
Actually, it won't as for now in Plaintext/Info output code, FORMAT_MENU
is not checked when adding an automatically generated menu. That could
be changed, but not for the
On Mon, Feb 24, 2025 at 08:52:15PM +, Gavin Smith wrote:
> On Mon, Feb 24, 2025 at 05:28:19PM +, Werner LEMBERG wrote:
> > Given that a detailmenu in Info style looks very un-HTML-ish I think
> > it would be best if `texi2any` didn't generate a detailmenu for HTML
> > output by default if `
On Tue, Feb 18, 2025 at 07:36:54PM +, Gavin Smith wrote:
> > I think that it is too much special casing that would lead to unexpected
> > results and too much code to handle, since we could have instead a
> > simpler alternative, with a command like
> > @anchornamed{Software Copying Permissions
On Tue, Feb 18, 2025 at 04:04:45PM +, Gavin Smith wrote:
> On Tue, Feb 18, 2025 at 04:04:53PM +0100, pertu...@free.fr wrote:
> > On Mon, Feb 17, 2025 at 07:13:43PM +, Gavin Smith wrote:
> > > On Mon, Feb 17, 2025 at 07:37:23PM +0100, pertu...@free.fr wrote:
> > > The user could also specify
On Mon, Feb 17, 2025 at 07:13:43PM +, Gavin Smith wrote:
> On Mon, Feb 17, 2025 at 07:37:23PM +0100, pertu...@free.fr wrote:
> > One possibility, which is not very acceptable either would be to allow
> > an empty @anchorname to remove the link between a @node and @heading,
> > for example
> >
On Sun, Feb 16, 2025 at 04:52:16PM +, Gavin Smith wrote:
> On Sun, Feb 16, 2025 at 04:56:37PM +0100, pertu...@free.fr wrote:
> > What should we do for @*heading not at the top level, like
> >
> > @node node
> >
> > @quotation
> > @heading in quitation
> > Quote
> > @end quotation
> >
> > @he
On Sun, Feb 16, 2025 at 03:36:07PM +, Gavin Smith wrote:
> > Actually, I was proposing the opposite, so I was probably unclear.
> >
> > For @node, the association is with the next sectioning command, even if
> > there are @*heading commands in-between. This is also quite
> > theoretical, as t
On Sun, Feb 16, 2025 at 12:24:23PM +, Gavin Smith wrote:
> On Sun, Feb 16, 2025 at 12:57:21PM +0100, pertu...@free.fr wrote:
> > This is only true if USE_NODES=1. For HTML, if USE_NODES=0, the
> > sectioning commands define units of output and @node are only
> > used ase targets of cross-refe
On Sun, Feb 16, 2025 at 12:35:11PM +, Gavin Smith wrote:
> On Sun, Feb 16, 2025 at 01:00:24PM +0100, pertu...@free.fr wrote:
> > On Sat, Feb 15, 2025 at 02:26:11PM +, Gavin Smith wrote:
> > > @label could be ok for the command, but it could be confusing as there
> >
> > Even without a conf
On Sat, Feb 15, 2025 at 02:26:11PM +, Gavin Smith wrote:
> @label could be ok for the command, but it could be confusing as there
Even without a confusion with LaTeX command, @label is confusing to be
used as a target to cross references, because it is exactly the opposite
of what seems to me
On Sat, Feb 15, 2025 at 04:38:34PM +, Gavin Smith wrote:
> On Sat, Feb 15, 2025 at 01:16:13PM +, Werner LEMBERG wrote:
> >
> > [folding answers to two e-mails into one]
> >
> > >> Because in Info a `@node` always needs a `@menu` entry, AFAIK,
> > >> which is inconsistent with the `@XXXhea
On Sat, Feb 15, 2025 at 01:16:13PM +, Werner LEMBERG wrote:
>
> > So, this is not different if a @node is before an @XXXheading, it
> > may appear in an explicit node direction and in another @node menu.
>
> Well, the behaviour of `@node` in a split HTML document is to start a
> new file. Ho
On Fri, Feb 14, 2025 at 02:05:23PM +, Werner LEMBERG wrote:
> Well, I think that your `@anchorlabel` suggestion is the way to go.
> Actually, I would prefer a shorter name, say, `@label`. Then you can
> demote
>
> ```
> @node Foo
> @subsection Foo doodle doo
> ```
>
> to
>
> ```
> @label Fo
On Fri, Feb 14, 2025 at 02:59:45PM +, Werner LEMBERG wrote:
> >> Well, I think that your `@anchorlabel` suggestion is the way to go.
> >> Actually, I would prefer a shorter name, say, `@label`. Then you
> >> can demote
> >>
> >> ```
> >> @node Foo
> >> @subsection Foo doodle doo
> >> ```
> >>
On Fri, Feb 14, 2025 at 02:05:23PM +, Werner LEMBERG wrote:
> >> > But do you really want to get the old sectioning name back for
> >> > printed output?
> >>
> >> Yes, because using `@anchor` would be the result of demoting, say,
> >> `@subsection` to `@subsubheading`.
> >
> > It seems to me
On Thu, Feb 13, 2025 at 12:53:44PM +, Werner LEMBERG wrote:
>
> >> * For translators, having the same anchor name as in the original
> >> document helps a lot in translation. And vice versa, it helps
> >> maintainers who don't speak the particular language to still do
> >> various maint
On Wed, Feb 12, 2025 at 10:12:15PM +0100, pertu...@free.fr wrote:
> I do not like the automatic association of an inline command like
> @anchor, that may happen anywhere, to another command. I think that it
> would be cleaner to have an @-command with two arguments, instead, like
>
> @anchorlabel
On Wed, Feb 12, 2025 at 04:56:26PM +, Gavin Smith wrote:
> Having removed @anchor from the scope of "@xrefautomaticsectiontitle",
> there is now a reason to add a new command that affects @anchor only.
>
> Your proposal from a few days ago of using a @*heading command appears
> relevant. We c
On Wed, Feb 12, 2025 at 10:52:35AM +, Werner LEMBERG wrote:
> > I get the reasoning, but it is not clear to me why one would want to
> > use something else than the @anchor argument for a link. There
> > aren't much constraints on anchor content, except that it should be
> > unique. I do not
On Tue, Feb 11, 2025 at 10:06:54PM +, Gavin Smith wrote:
> So it seems to me that this transliteration produces bad results in many
> cases and should be turned off by default.
Ok. Should I add some backward compatibility redirection files or not?
> Users could at least understand
> why sequ
On Thu, Feb 06, 2025 at 11:51:10PM +0100, pertu...@free.fr wrote:
> I think that we should avoid
> changing too often as the HTML cross manual links will be broken before
> all the manuals have been rebuilt.
It could be possible to generate redirection files with the previous
default for one relea
On Mon, Feb 10, 2025 at 04:54:24PM +, Gavin Smith wrote:
> On Mon, Feb 10, 2025 at 03:46:27PM +, Werner LEMBERG wrote:
> >
> > >> And Japanese people are probably even offended because, as it
> > >> currently happens, almost all Japanese characters are represented
> > >> with Chinese sylla
On Mon, Feb 10, 2025 at 03:46:27PM +, Werner LEMBERG wrote:
>
> >> And Japanese people are probably even offended because, as it
> >> currently happens, almost all Japanese characters are represented
> >> with Chinese syllables...
> >
> > In addition to --no-transliterate-file-names, it is al
On Mon, Feb 10, 2025 at 05:25:19PM +, Gavin Smith wrote:
> Users could do transliteration of node names in the Texinfo source
> if they wanted. Instead of writing
>
> @node garçonnière
>
> they could write
>
> @node garconniere
>
> (I searched Google for a French word with accents in it.)
On Mon, Feb 10, 2025 at 07:22:45PM +, Gavin Smith wrote:
> While playing with this I found a bug. Line numbers in htmlxref.cnf may
> not be correctly reported.
>
> I note that the edition of htmlxref.cnf I am using has exactly 801 lines
> so it is as if the line counter for htmlxref.cnf is no
On Fri, Feb 07, 2025 at 02:10:57PM +, Werner LEMBERG wrote:
> > Likewise, Finnish speakers strongly protest if "ä" is rendered as
> > "ae".
>
> And Japanese people are probably even offended because, as it
> currently happens, almost all Japanese characters are represented with
> Chinese sylla
On Thu, Feb 06, 2025 at 08:42:38PM +, Gavin Smith wrote:
> Well, I checked the sources of Texinfo 4.13 and transliterate_file_names
> appears to be off by default:
>
> I checked Texinfo 5.2 (September 2013) and it was on by default for that
> release, with 'TRANSLITERATE_FILE_NAMES' => 1 in %d
On Thu, Feb 06, 2025 at 07:53:06PM +, Werner LEMBERG wrote:
>
> > To handle such cases, texi2any offers the
> > --transliterate-file-names command line option. [...]
> >
> > This is the default.
>
> Well, it is customary to always show the opposite option of the
> default in the `-
On Thu, Feb 06, 2025 at 05:19:17PM +, Gavin Smith wrote:
> >
> > To handle such cases, texi2any offers the
> > --transliterate-file-names command line option. This option enables
> > transliteration of node names into ASCII characters for the purposes of
> > file name creation and
On Thu, Feb 06, 2025 at 05:02:30PM +, Werner LEMBERG wrote:
>
> I don't understand. How gets 'ö' mapped to 'o'? It is not NFC, but
> it can't be transliteration either, can it? I thought that the idea
> of transliteration is to map non-ASCII characters to ASCII strings
> unambiguously,
No,
On Thu, Feb 06, 2025 at 04:05:36PM +, Werner LEMBERG wrote:
>
> > https://www.gnu.org/software/texinfo/manual/texinfo/html_node/HTML-Xref-8_002dbit-Character-Expansion.html
>
> Thanks, but I don't think this is a valid explanation. 'o' is
> definitely *not* the NFC of 'ö'! AFAICS, the above
On Thu, Feb 06, 2025 at 03:46:41PM +, Werner LEMBERG wrote:
> > I would be quite surprised that this worked with texi2any since the
> > 5.0 release of GNU Texinfo. Maybe there was no error message, but
> > the result was probably unexpected. It could have worked with
> > makeinfo in C pre 5.0
On Sat, Feb 01, 2025 at 09:08:09AM +, Werner LEMBERG wrote:
>
> > Looks like a bug to me. I think that the nodes/anchor/float targets
> > should be there. (Also probably the @*heading command targets, the
> > footnotes, but it is less important).
Added in
https://git.savannah.gnu.org/cgit/t
On Fri, Jan 31, 2025 at 10:07:20PM +, Werner LEMBERG wrote:
>
> >> I'm searching a way to make `texi2any` dump all cross-reference
> >> targets (i.e., the arguments of `@node` and `@anchor`) to a file
> >> for a given document, for example, by adding some code to a file
> >> loaded via `--init
On Thu, Jan 09, 2025 at 07:58:02AM +0200, Eli Zaretskii wrote:
> > Date: Wed, 8 Jan 2025 20:46:59 +0100
> > From: pertu...@free.fr
> >
> > What to do next? Add information on DPI/font size/DPL to the image in
> > Info, contact Emacs persons who could discuss the issue/do the change?
> > (Through
On Fri, Jan 10, 2025 at 09:53:03PM +, Werner LEMBERG wrote:
>
> >> Could we change the referent index to the last one, rather than the
> >> first, as Werner mentioned it may often be more appropriate:
> >>
> >> Assuming that a large document has multiple indices, the most
> >> general ind
On Fri, Jan 10, 2025 at 09:23:20PM +, Gavin Smith wrote:
> Could we change the referent index to the last one, rather than the
> first, as Werner mentioned it may often be more appropriate:
>
> Assuming that a large document has multiple indices, the most general
> index is normally the la
On Thu, Jan 09, 2025 at 05:57:00AM +, Werner LEMBERG wrote:
> Meanwhile I believe it would be fully sufficient for most users to add
> a Texinfo command that specifies a node name for a section that
> contains the index (or indices), and which is then used accordingly in
> the navigation bar, f
On Thu, Jan 02, 2025 at 12:57:43AM +, Gavin Smith wrote:
> If texi2any generates the images with a given DPI (dots per inch) setting
> to dvips (-d argument) (say 200), then it seems that all Emacs would need
> is a variable to specify the DPI of the Info images. The image size
> would then be
On Thu, Jan 02, 2025 at 12:57:43AM +, Gavin Smith wrote:
> If texi2any generates the images with a given DPI (dots per inch) setting
> to dvips (-d argument) (say 200), then it seems that all Emacs would need
> is a variable to specify the DPI of the Info images. The image size
> would then be
On Tue, Dec 24, 2024 at 06:38:19PM +, Gavin Smith wrote:
> On Tue, Dec 24, 2024 at 07:45:02PM +0200, Eli Zaretskii wrote:
> > > From: Gavin Smith
> > > Date: Tue, 24 Dec 2024 17:21:36 +
> > >
> > > We could ask Emacs users or developers if there is a way to make
> > > the images be displa
On Wed, Nov 27, 2024 at 05:29:02PM +0200, Eli Zaretskii wrote:
> > and getting the result from the return of the Perl function:
> > result_sv = POPs;
> > result_ret = SvPVutf8 (result_sv, len);
>
> OK, thanks. This should work, if we avoid the cases where the caller
> allocates memory that Pe
On Wed, Nov 27, 2024 at 04:29:43PM +0200, Eli Zaretskii wrote:
> > From: Gavin Smith
> > Date: Tue, 26 Nov 2024 18:33:31 +
> >
> > On the two systems you mention (Cygwin64 and Macos-13), in spite of
> > Perl appearing to be new enough, calling gettext does not work. It
> > is presumed that c
On Sun, Nov 24, 2024 at 01:05:56PM +, Gavin Smith wrote:
> Thanks. I imagine that if the user's document had the same language
> in different examples (e.g. TeX), but that it had to be highlighted
> differently for the same language in different examples (e.g. TeX
> with different catcodes, e.
On Tue, Oct 29, 2024 at 04:19:23PM +, Werner LEMBERG wrote:
> This is with a self-compiled version 7.1. For some auto-generated
> documentation I tried stuff like this:
>
> ```
> @table @asis
> @item @anchor{foo}@code{foo} ...
> @item @anchor{bar}@code{bar} ...
> ...
> @end table
> ```
> BTW,
On Sat, Oct 26, 2024 at 10:43:54AM +0100, Gavin Smith wrote:
> Thanks, this makes sense to me. As far as I understand, this "mingw" is
> not a valid architecture worth supporting. It is said to be mingw but
> some cygwin programs are in use:
Indeed, it is not mingw built on mingw, it is mingw bu
On Thu, Aug 29, 2024 at 07:43:00AM +0300, Eli Zaretskii wrote:
> > From: Gavin Smith
> > Date: Wed, 28 Aug 2024 21:26:55 +0100
> >
> > I'm a bit confused as I thought it was configuration files which we
> > were discussing, which would be XDG_CONFIG_DIRS, not XDG_DATA_DIRS.
> >
> > I see that ht
On Thu, Apr 11, 2024 at 09:06:05AM +0300, Eli Zaretskii wrote:
> > From: Gavin Smith
> > Date: Wed, 10 Apr 2024 23:53:31 +0100
> >
> > I agree that the warning is not really necessary. I don't mind
> > either way. It's up to you if you want to try to remove the warning.
> > It's questionable w
On Wed, Mar 06, 2024 at 07:28:52PM +, Gavin Smith wrote:
> It could just be the same error message as when used outwith @itemize:
>
> @asis foo
>
> - which gives an error message like:
>
> test.texi:11: @asis expected braces
I also think that it is the best.
> Although it is very u
On Wed, Mar 06, 2024 at 01:32:16PM +, Werner LEMBERG wrote:
>
> > Here is another proposal, which seems much clearer to me, but is
> > probably too long:
>
> > @itemize command argument with omitted braces should not require an
> > argument, but @asis does. Use braces for @asis
>
> I sugge
On Sun, Feb 04, 2024 at 12:07:17PM +0100, Andreas Schwab wrote:
> On Feb 04 2024, Eli Zaretskii wrote:
>
> > If we want collation which uses only codepoints, disregarding any
> > collation weights defined by the Unicode TR10, we could use
> > en_US.utf-8, but then, as Gavin says, using glibc colla
On Sun, Feb 04, 2024 at 12:55:36PM +0200, Eli Zaretskii wrote:
> > Date: Sun, 4 Feb 2024 11:42:52 +0100
> > From: pertu...@free.fr
> > Cc: Gavin Smith , bug-texinfo@gnu.org
> >
> > On Fri, Feb 02, 2024 at 08:57:01AM +0200, Eli Zaretskii wrote:
> > > I think en_US.utf-8 is (or at least can be by de
On Fri, Feb 02, 2024 at 08:57:01AM +0200, Eli Zaretskii wrote:
> > From: Gavin Smith
> > Date: Thu, 1 Feb 2024 22:16:07 +
> > Cc: Patrice Dumas , bug-texinfo@gnu.org
> >
> > On Thu, Feb 01, 2024 at 09:01:42AM +0200, Eli Zaretskii wrote:
> > > > Date: Wed, 31 Jan 2024 23:11:02 +0100
> > > > Fr
On Sun, Jan 21, 2024 at 03:13:25PM -0700, Karl Berry wrote:
> Hi Patrice,
>
> I understand the principle, but for me the lossage in practice is even
> more unfortunate (by far). It sure seems to me that the "rare" case
> should be the one to have to make the config file setting. Indeed, the
> very
On Mon, Nov 06, 2023 at 02:37:57PM +0200, Eli Zaretskii wrote:
> > Date: Mon, 6 Nov 2023 09:20:37 +0100
> > From: pertu...@free.fr
> > Cc: Gavin Smith , bug-texinfo@gnu.org
> >
> > libtexinfo corresponds to the 'pure' C common code that performs the
> > computations needed for texi2any, working on
On Sun, Nov 05, 2023 at 09:59:44PM +0200, Eli Zaretskii wrote:
>
> I don't have any libtexinfo shared library here, and I don't see one
> being built, let alone installed, as part of Texinfo. is this
> something new in the development sources? If so, what code is linked
> into libtexinfo?
Yes,
On Thu, Oct 12, 2023 at 06:00:44PM +0100, Gavin Smith wrote:
> On Thu, Oct 12, 2023 at 09:21:45AM +0300, Eli Zaretskii wrote:
> > > From: Gavin Smith
> > > Date: Wed, 11 Oct 2023 18:15:04 +0100
> > > Cc: Patrice Dumas
> > >
> > > On Wed, Oct 11, 2023 at 06:12:51PM +0100, Gavin Smith wrote:
> > >
On Wed, Sep 06, 2023 at 02:53:35PM +0300, Eli Zaretskii wrote:
> > From: Gavin Smith
> > Date: Wed, 6 Sep 2023 02:51:47 +0100
> >
> > On Tue, Sep 05, 2023 at 09:16:47PM +0200, Patrice Dumas wrote:
> > > I think I understand what you don't understand, actually this is not
> > > about displaying th
On Fri, Mar 10, 2023 at 09:42:19AM +0200, Eli Zaretskii wrote:
> > From: Gavin Smith
> > Date: Fri, 10 Mar 2023 07:19:15 +
> > Cc: pertu...@free.fr, bug-texinfo@gnu.org
> >
> > On Fri, Mar 10, 2023 at 09:05:58AM +0200, Eli Zaretskii wrote:
> > > I'm not saying that texi2any doesn't play by th
On Thu, Mar 09, 2023 at 09:01:08AM +0200, Eli Zaretskii wrote:
> > There may be some need to modify texi2any more generally (for
> > example for upper casing, for locale dependent index keys sorting,
> > maybe for line breaking in Info output). There may be some trouble
> > with presentation of in
On Thu, Mar 09, 2023 at 09:10:13AM +0200, Eli Zaretskii wrote:
> > Indeed, following this change, the following two nodes will clash while
> > they did not before
> >
> > @node my node
> >
> > @node my @sc{node}
> >
> > However, I consider it better if the two nodes clash.
>
> Do we have a good
On Thu, Mar 09, 2023 at 09:10:13AM +0200, Eli Zaretskii wrote:
> > From: pertu...@free.fr
> > Indeed, following this change, the following two nodes will clash while
> > they did not before
> >
> > @node my node
> >
> > @node my @sc{node}
> >
> > However, I consider it better if the two nodes cl
On Wed, Mar 08, 2023 at 10:16:02PM +0200, Eli Zaretskii wrote:
> > From: Gavin Smith
> > Date: Wed, 8 Mar 2023 20:11:02 +
> > Cc: Patrice Dumas , bug-texinfo@gnu.org
> >
> > It is to affect URLs, not for the main text of the document that the user
> > would read.
>
> If it's _only_ for URLs,
On Wed, Mar 08, 2023 at 10:17:42PM +0200, Eli Zaretskii wrote:
> > From: Gavin Smith
> > Date: Wed, 8 Mar 2023 20:06:19 +
> > Cc: Patrice Dumas , bug-texinfo@gnu.org
> >
> > > > * what capitalization means could differ for locales
> > >
> > > Not for ASCII characters, right?
> >
> > A class
On Sun, Feb 12, 2023 at 12:04:38PM +, Gavin Smith wrote:
> On Sun, Feb 12, 2023 at 11:38:43AM +, Gavin Smith wrote:
> > I'll try to look at this commit more to see if I can find anything else.
>
> It's good news: we can keep the uninlined function. The slowdown almost
> goes away complete
On Sun, Feb 12, 2023 at 11:38:42AM +, Gavin Smith wrote:
> Indeed, the difference was at the first place I checked: on
> 2022-09-10, commit 46bfa18bb0, where the time came out as 43.9 sec.
>
> 2022-09-10 Patrice Dumas
>
>* tp/Texinfo/ParserNonXS.pm (_parse_texi, _process_remaining_
On Sun, Feb 12, 2023 at 09:47:10AM +, Gavin Smith wrote:
>
> With TEXINFO_XS=omit, it now takes 52 seconds. I tested Texinfo
> 7.0.2 and it only took 42 seconds.
>
> (I thought this was still longer than I remembered, so tested
> with Texinfo 6.8, where it came out 23 seconds without XS modu
On Sat, Feb 11, 2023 at 08:30:07PM +, Gavin Smith wrote:
> >
> > How many manuals set documentlanguage? With the proliferation of
> > documentencoding set to UTF-8, I think disabling the collation for
> > "en" will be next to futile.
>
> If I understand correctly, until recently more standar
On Sat, Jan 07, 2023 at 05:10:39PM +0200, Eli Zaretskii wrote:
>
> How do you see that there's "a file with the two nodes concatenated".
> What I see is index.html and Node1.html. The contents of the latter
> is this:
Well, the first Node1.html that was generated had both nodes
concatenated, but
On Sat, Jan 07, 2023 at 03:37:21PM +0200, Eli Zaretskii wrote:
> > From: Gavin Smith
> > Date: Sat, 7 Jan 2023 12:29:33 +
> > Cc: pertu...@free.fr, torbjorn.svens...@foss.st.com, bug-texinfo@gnu.org
> >
> > On Sat, Jan 07, 2023 at 01:06:41PM +0200, Eli Zaretskii wrote:
> > > How do you "set"
On Sat, Jan 07, 2023 at 11:54:03AM +0200, Eli Zaretskii wrote:
> > Date: Sat, 7 Jan 2023 10:38:57 +0100
> > From: pertu...@free.fr
> > Cc: Gavin Smith , torbjorn.svens...@foss.st.com,
> > bug-texinfo@gnu.org
> >
> > No, what I would like to know is whether nodes are concatenated when
> > split
On Sat, Jan 07, 2023 at 09:08:56AM +0200, Eli Zaretskii wrote:
> > From: Gavin Smith
> > Date: Sat, 7 Jan 2023 00:35:25 +
> >
> > > Does anybody knows if nodes are correctly concatenated with case
> > > insensitive filesystems if CASE_INSENSITIVE_FILENAMES is not set?
> >
> > It would be goo
On Thu, Dec 22, 2022 at 11:22:40AM +0100, pertu...@free.fr wrote:
> On Wed, Dec 21, 2022 at 09:13:08PM -0700, arn...@skeeve.com wrote:
> > Hi.
> >
> > Thanks for figuring this out. The problem is that in this case
> > there is no way to directly give the table a title and anchor for cross
> > ref
On Wed, Dec 21, 2022 at 09:13:08PM -0700, arn...@skeeve.com wrote:
> Hi.
>
> Thanks for figuring this out. The problem is that in this case
> there is no way to directly give the table a title and anchor for cross
> referencing from the main text except by wrapping it in @float.
>
> I suppose tha
Hello,
The error actually comes from a construct like
@cartouche
@float Table,label
@caption{Return}
@end float
@end cartouche
My feeling is that @float should only be valid at top-level, not in a
block command, such as @cartouche, if in a block, the float cannot
float.
I would propose to ha
On Wed, Dec 21, 2022 at 01:41:59AM -0700, arn...@skeeve.com wrote:
>
> I've never used latex. I assume the sequence is something like
>
> makeinfo --latex gawk.texi # should have no errors / warnings
> latex gawk.tex
> latex gawk.tex # second time for xrefs and indexing
>
1 - 100 of 187 matches
Mail list logo
