> Date: Sun, 06 Nov 2022 16:09:59 + (UTC)
> Cc: arn...@skeeve.com, bug-texinfo@gnu.org
> From: Werner LEMBERG
>
> * I think it would be OK if the documentation says that i18n support
> for sorting only works with awk programs that understand `LANG`.
Gawk understands and uses any LC_* and L
> Date: Sun, 06 Nov 2022 17:19:23 + (UTC)
> Cc: arn...@skeeve.com, bug-texinfo@gnu.org
> From: Werner LEMBERG
>
> Again, I think it's OK if i18n support only works with glibc
It is?
> and similarly capable C libraries
Are there such libraries in existence, when locale data is considered?
W
> From: arn...@skeeve.com
> Date: Sun, 06 Nov 2022 11:25:27 -0700
> Cc: bug-texinfo@gnu.org, arn...@skeeve.com
>
> Eli Zaretskii wrote:
>
> > > and similarly capable C libraries
> >
> > Are there such libraries in existence, when locale data is cons
> From: Gavin Smith
> Date: Tue, 8 Nov 2022 16:34:03 +
>
> We have always developed Texinfo in a linear fashion (in git and before
> that SVN). However, the development repository is not necessarily always
> in a fit state to be released with new work being done. So one question
> I have is
> From: Gavin Smith
> Date: Tue, 8 Nov 2022 19:34:51 +
> Cc: bug-texinfo@gnu.org
>
> When we did a new major release, would we merge "master" into "release"?
No, you just cut a new release branch. The release branch is only for
a certain release or a series of releases, depending on the
dev
Hi,
Texinfo 7.0 added support for producing the manual in the EPUB format,
but there's no standard directory to install that in GNU Coding
Standards. Would you please recommend where to install that, and
suggest a patch for the GCS document to reflect that? The first
question about that "from th
> From: Gavin Smith
> Date: Wed, 9 Nov 2022 19:20:53 +
> Cc: bug-texinfo@gnu.org
>
> It's not clear that there should be a dedicated directory for installed
> EPUB files, or that people would install lots of these. I'm not too
> clear on how people would use the EPUB output.
>
> The 'docdir
> From: Gavin Smith
> Date: Wed, 9 Nov 2022 19:58:19 +
> Cc: bug-texinfo@gnu.org
>
> On Wed, Nov 09, 2022 at 09:36:44PM +0200, Eli Zaretskii wrote:
> > > htmldir, dvidir etc. all default to ${docdir} by default (with
> > > autoconf/automake). The
> Date: Sat, 12 Nov 2022 00:17:34 +0100
> From: Vincent Lefevre
> Cc: 989...@bugs.debian.org
>
> [Cc to the Debian bug 989029, which I reported last year:
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989029
>
> I'm now reporting it upstream since it still occurs with "info"
> from Te
> Date: Sat, 12 Nov 2022 10:26:39 +0100
> From: Patrice Dumas
> Cc: Vincent Lefevre , bug-texinfo@gnu.org,
> 989...@bugs.debian.org
>
> On Sat, Nov 12, 2022 at 09:27:34AM +0200, Eli Zaretskii wrote:
> > See that "Bugs" at the end? This is the problem: si
> Date: Sat, 12 Nov 2022 11:39:41 +0100
> From: Vincent Lefevre
> Cc: bug-texinfo@gnu.org, 989...@bugs.debian.org
>
> > * Menu:
> >
> > * Bugs::
> >
> > See that "Bugs" at the end? This is the problem: since "Bugs" is a
> > top-level node, its presence in a level-1 node's menu makes the no
> Date: Sat, 12 Nov 2022 11:56:47 +0100
> From: Vincent Lefevre
>
> Oops, I misread the file. I actually think that it is correct.
> IMHO, to get the tree structure, you should not follow the menu,
> but only the "File:" lines.
You can't: SPC and DEL are supposed to traverse the tree, not just t
> Date: Sat, 12 Nov 2022 12:40:11 +0100
> From: Vincent Lefevre
>
> > > Oops, I misread the file. I actually think that it is correct.
> > > IMHO, to get the tree structure, you should not follow the menu,
> > > but only the "File:" lines.
> >
> > You can't: SPC and DEL are supposed to traverse
> Date: Sat, 12 Nov 2022 13:28:17 +0100
> From: Vincent Lefevre
> Cc: gavinsmith0...@gmail.com, bug-texinfo@gnu.org, 989...@bugs.debian.org
>
> > > But "down" is the reverse of "up".
> >
> > No, it isn't. It is only the reverse of "up" if the node structure is
> > a perfect tree.
>
> But if th
> Date: Mon, 14 Nov 2022 17:27:20 +0100
> From: Hilmar Preuße
>
> This seems to hang forever:
>
>$ LC_ALL=C info python3.10 -n 'Other Language Changes<3>'
Where can one find this python3.10 Info manual?
> From: Gavin Smith
> Date: Wed, 16 Nov 2022 23:05:59 +
> Cc: Sam James , bug-texinfo@gnu.org
>
> Can you please email me the python3.10.info file off-list so I can
> fix it.
File sent off-list.
> From: Gavin Smith
> Date: Fri, 2 Dec 2022 22:46:43 +
> Cc: "bug-texinfo@gnu.org"
>
> On Fri, Dec 02, 2022 at 09:02:04PM +, LaPolla, Justin Anthony wrote:
> > I found a bug in the stand-alone Info reader. To reproduce:
> >
> > Open any file in info. For example, 'info gcc'.
> >
>
> From: Gavin Smith
> Date: Sat, 3 Dec 2022 15:25:20 +
> Cc: Texinfo
>
> The report was dir file corruption if install-info was interrupted.
>
> I've attempted to fix this issue by creating a temporary file with
> mkstemp, and then renaming it. I've added the Gnulib module for mkstemp
> as
> From: Gavin Smith
> Date: Sat, 3 Dec 2022 18:26:26 +
> Cc: ped...@gmail.com, bug-texinfo@gnu.org
>
> > Moreover, the MS runtime implements 'rename' in a way that fails if the
> > destination exists. So you will need the Gnulib replacement for it.
>
> That is quite a big difference.
>
> I
> From: Gavin Smith
> Date: Sat, 3 Dec 2022 19:19:50 +
> Cc: ped...@gmail.com, bug-texinfo@gnu.org
>
> On Sat, Dec 03, 2022 at 08:54:42PM +0200, Eli Zaretskii wrote:
> > I suggest the other way around: try renaming, and if it fails, remove and
> > retry renaming.
> From: Bruno Haible
> Date: Thu, 08 Dec 2022 01:21:51 +0100
>
> Gavin Smith wrote:
> > I expect it is not a gnulib problem. install-info/install-info.c declares
> > a function called "error" which appears to clash with a function from glibc.
> > ... The "error" module is brought in by "xalloc"
> From: Arsen Arsenović
> Cc: Bruno Haible , gavinsmith0...@gmail.com,
> s...@gentoo.org, bug-texinfo@gnu.org, bug-gnu...@gnu.org
> Date: Thu, 08 Dec 2022 09:25:01 +0100
>
> > Shouldn't we report this to the GCC folks? It could be a bug in lto,
> > no? I mean, 'error' is not a symbol that appl
> From: Bruno Haible
> Cc: gavinsmith0...@gmail.com, s...@gentoo.org, bug-texinfo@gnu.org,
> bug-gnu...@gnu.org
> Date: Thu, 08 Dec 2022 20:00:31 +0100
>
> Eli Zaretskii wrote:
> > > Attempting to --whole-archive link on that platform grants us:
> > >
>
> From: Gavin Smith
> Date: Sat, 10 Dec 2022 00:22:37 +
> Cc: bug-texinfo@gnu.org
>
> The script was under contrib/fix-info-dir. The whole contrib/ directory
> was excluded from the tar ball.
>
> Which distributions use the script and when/how is it run?
>
> The script appears to have hard
> From: Gavin Smith
> Date: Sat, 10 Dec 2022 00:35:19 +
>
> > d.texi:2: bad @table argument
>
> would be sufficient. It could be difficult to explain the usage
> of @table in an short error message.
>
> Perhaps if there is no argument at all it could be
>
> > d.texi:2: @table requires an
> From: Tomasz Kłoczko
> Date: Sat, 10 Dec 2022 00:37:40 +
>
> Fedora is using it
> https://src.fedoraproject.org/rpms/texinfo/tree/rawhide
> https://src.fedoraproject.org/rpms/texinfo/blob/rawhide/f/texinfo.spec#_107
> It is very useful on regenerate dir file after any changes on add/remove
[Please use Reply All to keep the other people and the list on the CC.]
> From: Tomasz Kłoczko
> Date: Sat, 10 Dec 2022 09:04:05 +
>
> On Sat, 10 Dec 2022 at 07:43, Eli Zaretskii wrote:
> [..]
>
> Why not use install-info for that? It can do these tasks, AFAICT.
> From: Gavin Smith
> Date: Sat, 10 Dec 2022 10:01:09 +
> Cc: kloczko.tom...@gmail.com, bug-texinfo@gnu.org
>
> On Sat, Dec 10, 2022 at 09:38:17AM +0200, Eli Zaretskii wrote:
> > > From: Gavin Smith
> > > Date: Sat, 10 Dec 2022 00:22:37 +
> > >
[Once again, please use Reply All to reply.]
> From: Tomasz Kłoczko
> Date: Sat, 10 Dec 2022 11:06:29 +
>
> On Sat, 10 Dec 2022 at 11:02, Eli Zaretskii wrote:
>
> > install-info (de)register single file.
> > It is completely different tool.
>
> It is n
> From: Gavin Smith
> Date: Wed, 14 Dec 2022 08:13:55 +
> Cc: 59...@debbugs.gnu.org, bug-texinfo@gnu.org
>
> I think using curly quotes by default was a mistake in the first place
> for UTF-8 input; however, any changes to the defaults should be discussed
> on bug-texinfo@gnu.org. The main i
> From: "Kuberry, Paul Allen"
> Date: Wed, 14 Dec 2022 18:27:04 +
>
> Between Texinfo 6.7 and 6.8, a change took place where CPPFLAGS is no longer
> populated in the file tp/Texinfo/XS/Makefile (created from
> tp/Texinfo/XS/Makefile.in). However, it is populated a few folders up in
> tp/Ma
> From: Arsen Arsenović
> Date: Fri, 06 Jan 2023 19:37:17 +0100
>
> The info program goes onto the next page when reaching the end of a
> buffer, where the info-mode on GNU Emacs 30.0.50 (build 1,
> x86_64-pc-linux-gnu, GTK+ Version 3.24.35, cairo version 1.17.6) of
> 2022-12-26 stops at the end
> From: Arsen Arsenović
> Cc: bug-texinfo@gnu.org
> Date: Fri, 06 Jan 2023 21:43:06 +0100
>
> > The (info)Top node on my system has a next node ("(info)Getting
> > Started"), which pure ``n'' and (Info-next) take me to, but none of the
> > in-buffer navigation commands (including /) do.
>
> Aha!
> From: Gavin Smith
> Date: Fri, 6 Jan 2023 22:02:54 +
> Cc: Eli Zaretskii , bug-texinfo@gnu.org
>
> On Fri, Jan 06, 2023 at 09:23:17PM +0100, Arsen Arsenović wrote:
> > Evening Eli,
> >
> > Eli Zaretskii writes:
> >
> > > That's not
> 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 good to know the answer to this.
I've built the GDB HTML docs on MS-Windows wit
> 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, or there is only one node in the output.
Only one node is in the output,
> Date: Sat, 7 Jan 2023 11:21:29 +0100
> From: pertu...@free.fr
> Cc: gavinsmith0...@gmail.com, torbjorn.svens...@foss.st.com,
> bug-texinfo@gnu.org
>
> On Sat, Jan 07, 2023 at 11:54:03AM +0200, Eli Zaretskii wrote:
> > > Date: Sat, 7 Jan 2023 10:38:57 +0100
&
> 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" the CASE_INSENSITIVE_FILENAMES from the
> Date: Sat, 7 Jan 2023 15:41:36 +0100
> From: pertu...@free.fr
> Cc: Gavin Smith , torbjorn.svens...@foss.st.com,
> bug-texinfo@gnu.org
>
> On Sat, Jan 07, 2023 at 03:37:21PM +0200, Eli Zaretskii wrote:
> > > From: Gavin Smith
> > > Date: Sat, 7 Jan
> From: Gavin Smith
> Date: Sat, 11 Feb 2023 19:46:12 +
>
> On Sat, Feb 11, 2023 at 08:04:15PM +0100, Patrice Dumas wrote:
> > Other than that I do not have much other idea than disabling it, for
> > instance if documentlanguage is en. The result with Unicode::Collate is
> > better for accen
> Date: Sat, 11 Feb 2023 21:40:58 +0100
> From: pertu...@free.fr
>
> For french, and I belive all the languages with accented letters that
> should sort next to the non accented letter, for instance e and é, the
> sort is much better with Unicode::Collate.
But if the index entries actually don't
> From: Gavin Smith
> Date: Sun, 12 Feb 2023 09:47:10 +
> Cc: pertu...@free.fr, bug-texinfo@gnu.org
>
> > On my system, which is a
> > 12-year old Windows XP, producing the Emacs Lisp Reference manual for
> > Emacs 27.2 takes just 18.1 sec of CPU time, so how come Gavin reports
> > such huge
> Date: Wed, 8 Mar 2023 16:40:26 +0100
> From: Patrice Dumas
>
> Hello,
>
> Right now, as seen in "HTML Cross-reference Command Expansion"
>
> For @sc, any letters are capitalized.
>
> I'd like to change that for 3 reasons
> * what capitalization means could differ for locales
Not for ASCII
> Date: Wed, 8 Mar 2023 20:36:49 +0100
> From: Patrice Dumas
> Cc: bug-texinfo@gnu.org
>
> > > For @sc, any letters are capitalized.
> > >
> > > I'd like to change that for 3 reasons
> > > * what capitalization means could differ for locales
> >
> > Not for ASCII characters, right?
>
> Probab
> 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, then it could be OK. But beware of clashing
due to case differences that will
> 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 classic example is that the upper case of i may be İ in Turkish although
Does texi2an
> Date: Wed, 8 Mar 2023 22:27:49 +0100
> From: pertu...@free.fr
> Cc: Gavin Smith , bug-texinfo@gnu.org
>
> On Wed, Mar 08, 2023 at 10:17:42PM +0200, Eli Zaretskii wrote:
> > Does texi2any at all work in the Turkish locale?
>
> I can't see why not.
I suggest
> Date: Wed, 8 Mar 2023 23:31:55 +0100
> From: pertu...@free.fr
> Cc: Gavin Smith , bug-texinfo@gnu.org
>
> On Wed, Mar 08, 2023 at 10:16:02PM +0200, Eli Zaretskii wrote:
> > > From: Gavin Smith
> > > Date: Wed, 8 Mar 2023 20:11:02 +
> > &g
> Date: Thu, 9 Mar 2023 21:14:52 +0100
> From: pertu...@free.fr
> Cc: gavinsmith0...@gmail.com, bug-texinfo@gnu.org
>
> > > I do not think that it matters in texi2any (and for perl character
> > > strings more generally).
> >
> > It could matter if texi2any up-cases some text that includes 'i',
>
> 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 the locale's rules.
> > Quite the
> From: Gavin Smith
> Date: Sat, 11 Mar 2023 22:04:55 +
> Cc: Patrice Dumas , bug-texinfo@gnu.org
>
> It is pretty common to use @sc with a lower case argument where the
> argument is intended to be in upper case.
The Texinfo manual says:
TeX typesets any uppercase letters between the
> Date: Mon, 20 Mar 2023 18:27:00 + (UTC)
> Cc: bug-texinfo@gnu.org
> From: Werner LEMBERG
>
> @subheading Predefined commands
>
> @raggedright
> @findex \virgula
> @code{\virgula},
> @findex \caesura
> @code{\caesura},
> @findex \divisioMinima
> @code{\divisioMinima},
> @findex \divisioMaio
> From: Arash Esbati
> Cc: bug-texinfo@gnu.org
> Date: Sun, 02 Apr 2023 18:58:52 +0200
>
> In file included from MiscXS.xs:8:
> C:/pathto/msys64/mingw64/lib/perl5/core_perl/CORE/XSUB.h:618: warning: "free"
> redefined
> 618 | #define freePerlMem_free
> |
> In file inc
> From: Arash Esbati
> Cc: Eli Zaretskii , bug-texinfo@gnu.org
> Date: Mon, 03 Apr 2023 17:07:02 +0200
>
> 1. When I do 'info dir' with my build, I see:
>
>Next: vdir invocation, Prev: ls invocation, Up: Directory listing
>
>10.2 `
> From: Arash Esbati
> Cc: gavinsmith0...@gmail.com, bug-texinfo@gnu.org
> Date: Mon, 03 Apr 2023 18:11:13 +0200
>
> Eli Zaretskii writes:
>
> > Which console is this? Is this a Command Prompt window, or some kind
> > of MSYS2 terminal emulator (mintty)?
>
> From: Arash Esbati
> Cc: gavinsmith0...@gmail.com, bug-texinfo@gnu.org
> Date: Mon, 03 Apr 2023 18:32:13 +0200
>
> > What happens if you invoke 'info' from the default Windows Command
> > Prompt window? does the problem persist?
>
> My build looks like this in cmd.exe:
??? What is your conso
> Date: Mon, 03 Apr 2023 19:43:54 +0300
> From: Eli Zaretskii
> Cc: gavinsmith0...@gmail.com, bug-texinfo@gnu.org
>
> > and Msys2 info looks like this:
>
> Your MSYS2 Info was built without libiconv, right?
Actually, that's not it: MSYS2 build is not a MinGW build
> From: Arash Esbati
> Cc: gavinsmith0...@gmail.com, bug-texinfo@gnu.org
> Date: Tue, 04 Apr 2023 09:35:07 +0200
>
> > ??? What is your console output codepage set to?
>
> C:\>chcp
> Aktive Codepage: 850.
That's likely the problem: this codepage doesn't support Unicode
quotes. What remain
> From: Gavin Smith
> Date: Tue, 4 Apr 2023 10:34:23 +0100
> Cc: Eli Zaretskii , bug-texinfo@gnu.org
>
> On Tue, Apr 04, 2023 at 09:35:07AM +0200, Arash Esbati wrote:
> > Eli Zaretskii writes:
> >
> > > What do you get from rpl_nl_langin
> From: Gavin Smith
> Date: Tue, 4 Apr 2023 10:56:28 +0100
> Cc: Eli Zaretskii , bug-texinfo@gnu.org
>
> The other thing that I am confused about is that you said you were
> building on "Win10, Msys2/MinGW64". Would Msys2 and MinGW64 not
> be two differen
> From: Gavin Smith
> Date: Tue, 4 Apr 2023 10:59:53 +0100
> Cc: Eli Zaretskii , bug-texinfo@gnu.org
>
> On Tue, Apr 04, 2023 at 09:35:07AM +0200, Arash Esbati wrote:
> > Eli Zaretskii writes:
> >
> > > ??? What is your console output codepage set to?
>
> Date: Tue, 4 Apr 2023 12:48:14 +0200
> From: Patrice Dumas
>
> On Tue, Apr 04, 2023 at 10:59:53AM +0100, Gavin Smith wrote:
> > On Tue, Apr 04, 2023 at 09:35:07AM +0200, Arash Esbati wrote:
> > > Eli Zaretskii writes:
> > >
> > > >
> Date: Tue, 04 Apr 2023 15:11:01 +0300
> From: Eli Zaretskii
> Cc: ar...@gnu.org, bug-texinfo@gnu.org
>
> There's an easier way:
>
> (gdb) ./ginfo.exe
Sorry, this was supposed to be
$ gdb ./ginfo.exe
> From: Gavin Smith
> Date: Tue, 4 Apr 2023 13:56:23 +0100
> Cc: ar...@gnu.org, bug-texinfo@gnu.org
>
> Ok, so assuming that this is all correct, we know that it is possible
> to build Texinfo for MSYS2 because it was done officially, and Arash
> had the official MSYS2 info program installed.
>
> From: Arash Esbati
> Cc: gavinsmith0...@gmail.com, bug-texinfo@gnu.org
> Date: Tue, 04 Apr 2023 15:05:01 +0200
>
> >> C:\>chcp
> >> Aktive Codepage: 850.
> >
> > That's likely the problem: this codepage doesn't support Unicode
> > quotes. What remains to be understood is why doesn't info.
> From: Arash Esbati
> Cc: gavinsmith0...@gmail.com, bug-texinfo@gnu.org
> Date: Tue, 04 Apr 2023 15:32:47 +0200
>
> Sure. And just to confirm: I opened a cmd.exe, adjusted %path% so I
> have the mingw64 directories for its .dll's included, adjusted
> %infopath% and did
>
> c:\path\to\my\nat
> From: Arash Esbati
> Date: Wed, 05 Apr 2023 09:46:28 +0200
>
> The only other warnings I get are (linebreaks added manually):
>
> --8<---cut here---start->8---
> parsetexi/handle_commands.c: In function 'handle_other_command':
> parsetexi/handle_commands.c:3
> Date: Wed, 5 Apr 2023 11:31:12 +0200
> From: Patrice Dumas
> Cc: Arash Esbati , bug-texinfo@gnu.org
>
> On Wed, Apr 05, 2023 at 11:47:08AM +0300, Eli Zaretskii wrote:
> > Those are real bugs: we should cast to inptr_t instead of long.
>
> We already do that in s
> From: Gavin Smith
> Date: Wed, 5 Apr 2023 12:24:58 +0100
> Cc: Patrice Dumas , ar...@gnu.org, bug-texinfo@gnu.org
>
> GNU coding standards (Info node (standards)CPU Portability):
>
> You need not cater to the possibility that 'long' will be smaller
> than pointers and 'size_t'. We know
> From: Gavin Smith
> Date: Wed, 5 Apr 2023 14:59:23 +0100
> Cc: pertu...@free.fr, ar...@gnu.org, bug-texinfo@gnu.org
>
> Might it be better to round-trip through intptr_t rather than through
> a pointer type?
Yes, I think this will be better. Cleaner, too.
> > I think you are forgetting the e
> From: Arash Esbati
> Cc: bug-texinfo@gnu.org
> Date: Thu, 06 Apr 2023 08:55:22 +0200
>
> I see that Texinfo doesn't have any instructions how to build and install
> Texinfo with MinGW64. Should I make a proposal?
It depends on what MinGW64-specific nits you think should be there.
The only Wi
> From: Arash Esbati
> Cc: gavinsmith0...@gmail.com, bug-texinfo@gnu.org
> Date: Thu, 06 Apr 2023 13:22:46 +0200
>
> Eli Zaretskii writes:
>
> > The only Windows-specific issue I'm aware of is that the 'configure'
> > command should point to t
> From: Arash Esbati
> Cc: gavinsmith0...@gmail.com, bug-texinfo@gnu.org
> Date: Thu, 06 Apr 2023 14:18:50 +0200
>
> Eli Zaretskii writes:
>
> > Why on Earth is a system header included only in msys2-runtime-devel?
> >
> > Also, is msys2-runtime-devel ab
> From: Arash Esbati
> Cc: gavinsmith0...@gmail.com, bug-texinfo@gnu.org
> Date: Thu, 06 Apr 2023 20:13:32 +0200
>
> Eli Zaretskii writes:
>
> > Btw, I just built Texinfo 7.0.3, and info.exe still displays Unicode
> > quotes as I expect: transliterated t
> From: Sebastian Carlos
> Date: Fri, 21 Apr 2023 16:51:30 +0200
>
> I noticed that GNU Info does render man pages, but there's no mention of this
> feature on the GNU Info
> manual. And it's not entirely clear if there's a way to explicitly read man
> pages with GNU Info, or if it's
> just a f
[Please keep the list address on the CC.]
> From: Sebastian Carlos
> Date: Fri, 21 Apr 2023 17:30:20 +0200
>
> Stand-alone GNU Info for version 7.0.3, where I only found two mentions:
>
> > --all, -a
> > Find all files matching manual. Three usage patterns are supported, as
> > follows.
> > Fi
> Date: Mon, 5 Jun 2023 07:18:00 -0700
> From: Raymond Toy
>
> Maxima grovels over the html file to find appropriate links to use for the
> html version of the manual.
> This was working fine with 6.8 and earlier because I found appropriate
> regexps to find the links.
>
> This stopped working
> Date: Mon, 5 Jun 2023 08:11:00 -0700
> From: Raymond Toy
>
> It appears not to be consistent. We have this in the texinfo source:
>
>
> @fnindex N'th previous output
>
> with a real apostrohpe. The info file has
>
>
> * N'th previous output: Functions and Variables for Com
> From: Bruno Haible
> Date: Fri, 18 Aug 2023 01:00:01 +0200
>
> On mingw 5.0.3, I see 56 test failures:
>
> FAIL: ii-0001-test
> FAIL: ii-0002-test
Isn't this a problem with different EOL conventions in the expected
results and in what install-info compiled for Windows produces? If
so, you ne
> From: Gavin Smith
> Date: Fri, 18 Aug 2023 14:47:48 +0100
> Cc: bug-texinfo@gnu.org
>
> As the log file shows, the Unicode::Collate module is not found. I don't
> know what the solution to this is.
>
> It is meant to be included (in the "perl core") with perl 5.26.3 (the perl
> version report
> Date: Tue, 5 Sep 2023 20:01:53 +0200
> From: Patrice Dumas
>
> Currently, when counting the width of a line of character, we count
> control characters that are also spaces as having a width of 1. I think
> that it is not good, as control characters either should not have a
> width, for end of
> Date: Tue, 5 Sep 2023 20:19:40 +0200
> From: Patrice Dumas
> Cc: bug-texinfo@gnu.org
>
> On Tue, Sep 05, 2023 at 09:09:18PM +0300, Eli Zaretskii wrote:
> > > Date: Tue, 5 Sep 2023 20:01:53 +0200
> > > From: Patrice Dumas
> > >
> > > Curren
> Date: Tue, 5 Sep 2023 21:16:47 +0200
> From: Patrice Dumas
> Cc: bug-texinfo@gnu.org
>
> I think I understand what you don't understand, actually this is not
> about displaying the characters, which is not really done by texi2any,
> it is about situations where we need to count the width of cha
> 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 the characters, which is not really done by texi2any,
> > it is about situati
> From: Gavin Smith
> Date: Sat, 30 Sep 2023 17:16:57 +0100
> Cc: platform-test...@gnu.org
>
> A pretest distribution for the next Texinfo release (7.1) has been
> uploaded to
>
> https://alpha.gnu.org/gnu/texinfo/texinfo-7.0.93.tar.xz
This fails to build on MS-Windows with mingw.org's MinGW.
> From: Gavin Smith
> Date: Sat, 7 Oct 2023 17:26:51 +0100
> Cc: bug-texinfo@gnu.org
>
> I've changed xspara__print_escaped_spaces not to use malloc and free,
> although adding dTHX should be harmless.
Yes, I've seen that. Applying that change doesn't prevent the
crashes.
> Try going into the
> From: Gavin Smith
> Date: Sun, 8 Oct 2023 08:50:51 +0100
> Cc: bug-texinfo@gnu.org
>
> The program appears to crash after the "@include version-stnd.texi" line
> which read a new input file. This suggests that the problem may be to
> do with reading input, somewhere in 'next_text' in input.c.
> Date: Sun, 08 Oct 2023 12:41:19 +0300
> From: Eli Zaretskii
> Cc: bug-texinfo@gnu.org
>
> Starting program: d:\usr\Perl\bin\perl.exe ../tp/texi2any.pl info-stnd.texi
>
> Program received signal SIGSEGV, Segmentation fault.
> 0x692a6fc6 in getdelim ()
> fr
> From: Gavin Smith
> Date: Sun, 8 Oct 2023 12:50:51 +0100
> Cc: bug-texinfo@gnu.org
>
> On Sun, Oct 08, 2023 at 02:39:36PM +0300, Eli Zaretskii wrote:
> > Sorry, I was mistaken: the Gnulib getdelim is not used here. Instead,
> > this build uses the MinGW implement
> Date: Sun, 08 Oct 2023 14:39:36 +0300
> From: Eli Zaretskii
> CC: bug-texinfo@gnu.org
>
> Sorry, I was mistaken: the Gnulib getdelim is not used here. Instead,
> this build uses the MinGW implementation of getdelim, and that one has
> a subtle bug, which rears its ugly he
> Date: Sun, 08 Oct 2023 16:42:05 +0300
> From: Eli Zaretskii
> CC: bug-texinfo@gnu.org
>
> The next set of problems is in install-info: the new code in this
> version fails to close files, and then Windows doesn't let us
> remove/rename them. The result is that a
> From: Gavin Smith
> Date: Sun, 8 Oct 2023 16:33:22 +0100
> Cc: bug-texinfo@gnu.org
>
> > > Hence, I propose to initialise n to 0, rather than 120 as in the patch
> > > below.
> >
> > No, the value must be positive, otherwise it still crashes. It's a
> > bug in MinGW implementation.
>
> Can y
> From: Gavin Smith
> Date: Sun, 8 Oct 2023 17:04:36 +0100
> Cc: bug-texinfo@gnu.org
>
> On Sun, Oct 08, 2023 at 04:55:24PM +0300, Eli Zaretskii wrote:
> > > Date: Sun, 08 Oct 2023 16:42:05 +0300
> > > From: Eli Zaretskii
> > > CC: bug-texinfo@gnu.org
&
> Date: Sun, 08 Oct 2023 19:31:12 +0300
> From: Eli Zaretskii
> Cc: bug-texinfo@gnu.org
>
> I see a very large diff, full of non-ASCII characters. A typical hunk
> is below:
>
> -(ì) @'{e} é (é) @'{@dotless{i}} í (í) @dotless{i} ı (ı) @dotless{j} ȷ
>
> From: Gavin Smith
> Date: Sun, 8 Oct 2023 18:29:23 +0100
> Cc: bug-texinfo@gnu.org
>
> On Sun, Oct 08, 2023 at 07:31:12PM +0300, Eli Zaretskii wrote:
> > I see a very large diff, full of non-ASCII characters. A typical hunk
> > is below:
> >
> >
> From: Gavin Smith
> Date: Sun, 8 Oct 2023 20:21:44 +0100
> Cc: bug-texinfo@gnu.org
>
> Just comparing the first line in the hunk:
>
> -(ì) @'{e} é (é) @'{@dotless{i}} í (í) @dotless{i} ı (ı) @dotless{j} ȷ
> +(ì) @'{e} é (é) @'{@dotless{i}} í (í) @dotless{i} ı (ı) @dotless{j} ȷ (ȷ)
>
> the lin
> From: Bruno Haible
> Cc: bug-texinfo@gnu.org
> Date: Mon, 09 Oct 2023 18:15:05 +0200
>
> Eli Zaretskii wrote:
> > unless the locale's codeset is UTF-8, any character that is not
> > printable _in_the_current_locale_ will return -1 from wcwidth. I'm
>
> From: Bruno Haible
> Cc: gavinsmith0...@gmail.com, bug-texinfo@gnu.org
> Date: Mon, 09 Oct 2023 19:18:25 +0200
>
> Eli Zaretskii wrote:
> > > I just tried it now: On Linux (Ubuntu 22.04), in a de_DE.UTF-8 locale,
>
> Oops, typo: What I tested was the de_DE.ISO-88
> Date: Mon, 9 Oct 2023 21:17:28 +0200
> From: Patrice Dumas
>
> On Sun, Oct 08, 2023 at 06:29:23PM +0100, Gavin Smith wrote:
> >
> > I remember that in the past, I broke up some of these lines to avoid
> > test failures on some platform that had different wcwidth results for
> > some characters
> From: Gavin Smith
> Date: Mon, 9 Oct 2023 20:39:59 +0100
> Cc: Bruno Haible , bug-texinfo@gnu.org
>
> > IOW, unless the locale's codeset is UTF-8, any character that is not
> > printable _in_the_current_locale_ will return -1 from wcwidth. I'm
> > guessing that no one has ever tried to run the
1 - 100 of 1476 matches
Mail list logo
