Re: Locale-independent paragraph formatting

(Reply accidentally not sent to the list.) - Forwarded message from Gavin Smith - Date: Thu, 9 Nov 2023 21:25:28 + From: Gavin Smith To: Bruno Haible Subject: Re: Locale-independent paragraph formatting [was Re: Texinfo 7.0.93 pretest available] On Thu, Nov 09, 2023 at 08

Locale-independent paragraph formatting [was Re: Texinfo 7.0.93 pretest available]

(Reply accidentally not sent to list.) - Forwarded message from Gavin Smith - Date: Thu, 9 Nov 2023 20:11:59 + From: Gavin Smith To: Bruno Haible Subject: Locale-independent paragraph formatting [was Re: Texinfo 7.0.93 pretest available] On Tue, Oct 10, 2023 at 07:29:15PM

Re: Task-completion reporting does not reflect -o argument

On Wed, Nov 08, 2023 at 03:07:04PM -0500, Jonathan Dushoff wrote: > When I specify an alternative pdf target on the command line, the > argument is respected, but the console reports that it is not. See > below. This can cause serious confusion in complicated work flows, and > is presumably easy

Re: Code from installed libtexinfo.so.0 run for non-installed texi2any

On Mon, Nov 06, 2023 at 06:46:02PM +0100, Andreas Schwab wrote: > On Nov 06 2023, pertu...@free.fr wrote: > > > It is pkglibdir. Would be easy to change Makefile.am to put them there, > > but are we sure that the linker will find them when the dlopened *XS > > files are loaded by perl? > >

Re: Code from installed libtexinfo.so.0 run for non-installed texi2any

On Mon, Nov 06, 2023 at 02:25:20PM +0100, pertu...@free.fr wrote: > It is pkglibdir. Would be easy to change Makefile.am to put them there, > but are we sure that the linker will find them when the dlopened *XS > files are loaded by perl? The straightforward way of doing this seems to me to be

Re: ffmpeg documentation no longer builds after Texinfo 7.1 (due to --init-file=)

On Mon, Nov 06, 2023 at 12:21:40PM +0100, Arsen Arsenović wrote: > Thanks for the review, I've fixed those up. I'll see about sending it > upstream in when I have enough time to thoroughly test. > > Have a lovely day! Thanks for working on this. It seems to me that a customization API could

Re: Code from installed libtexinfo.so.0 run for non-installed texi2any

On Sun, Nov 05, 2023 at 09:59:44PM +0200, Eli Zaretskii wrote: > The XS modules are installed in a directory which is usually not > looked into by the dynamic linker. Is that what you are talking > about? If so, we have been using "non-public libraries" since long > ago, no? Or what am I

Re: Code from installed libtexinfo.so.0 run for non-installed texi2any

On Sun, Nov 05, 2023 at 07:52:53PM +0100, Andreas Schwab wrote: > On Nov 05 2023, Gavin Smith wrote: > > > The dynamically loaded libraries used by texi2any (XS modules) are > > completely different. Technically, they are loaded in the same way, > > by the

Re: Code from installed libtexinfo.so.0 run for non-installed texi2any

On Sun, Nov 05, 2023 at 07:38:27PM +0200, Eli Zaretskii wrote: > > From: Gavin Smith > > Date: Sun, 5 Nov 2023 17:04:47 + > > > > > Maybe one day libtexinfo could be a public library, but not for now > > > and libtexinfoxs should probably never ever b

Re: Code from installed libtexinfo.so.0 run for non-installed texi2any

On Sun, Nov 05, 2023 at 05:16:44PM +0100, Patrice Dumas wrote: > On Sat, Nov 04, 2023 at 10:58:35PM +0000, Gavin Smith wrote: > > > > Bingo. /usr/local/lib/libtexinfo.so.0 is being run. It shouldn't even > > be installed directly in /usr/local/lib. > > I c

Re: Post release texi2any performance regression

On Sun, Nov 05, 2023 at 11:59:11AM +0100, Patrice Dumas wrote: > On Sat, Nov 04, 2023 at 04:06:05PM +0000, Gavin Smith wrote: > > > At that point, using a new env variable to use perl for > > > structuring/transformations would be very easy based on your patch. > > >

Re: Post release texi2any performance regression

On Sun, Nov 05, 2023 at 01:01:21PM +0100, Patrice Dumas wrote: > > Indeed, commenting out those lines of code (although it makes the output > > incorrect) appeared to restore the run time to that of 7.1. > > > > This may have been due to a fairly recent change, but the lack of a > > stable,

Re: Post release texi2any performance regression

On Sat, Nov 04, 2023 at 04:06:06PM +, Gavin Smith wrote: > > > Applying this patch slows the program down by about 3% now. However, > > > it could still be useful for investigating why development texi2any is > > > still significantly slower (about 5%) t

Code from installed libtexinfo.so.0 run for non-installed texi2any

I have just had a frustrating time trying to work out why none of the changes I was making to the parsetexi module were taking effect. For example, the same debugging messages were still being printed even though I had effaced all instances of them from the source code. I suspected that installed

Re: Post release texi2any performance regression

On Sat, Nov 04, 2023 at 04:06:06PM +, Gavin Smith wrote: > > To me the most likely reason would be that simple_parser has been > > removed, such that calls of gdt/pgdt from perl are slower. > > Thanks, I'll try to investigate this. This is very significant for TEXINFO

Re: set_labels_identifiers_target -fsanitize=undefined error

On Sat, Nov 04, 2023 at 01:10:47PM +, Sam James wrote: > > John Paul Adrian Glaubitz writes: > > > Hi Gavin! > > > > On Sat, 2023-11-04 at 11:00 +, Gavin Smith wrote: > >> The line in question is: > >> > >> memcpy

Re: Post release texi2any performance regression

On Sat, Nov 04, 2023 at 02:50:36PM +0100, Patrice Dumas wrote: > On Sat, Nov 04, 2023 at 01:18:58PM +0000, Gavin Smith wrote: > > On Sat, Oct 28, 2023 at 05:42:51PM +0100, Gavin Smith wrote: > > > I managed to disable a lot of the new XS code and get the test suite > > &g

Re: Post release texi2any performance regression

On Sat, Oct 28, 2023 at 05:42:51PM +0100, Gavin Smith wrote: > I managed to disable a lot of the new XS code and get the test suite > to pass. I had to leave the XS translation module active due to the > coupling that now exists between it and the XS parser. This patch wasn't working an

set_labels_identifiers_target -fsanitize=undefined error

On Wed, Nov 01, 2023 at 03:44:01PM +, Sam James wrote: > > John Paul Adrian Glaubitz writes: > > > Hello! > > > > Starting with texinfo 7.1, there is a regression that results in texi2any > > crashing with a Bus Error on SPARC running on Linux [1]: > > > > /bin/bash: line 16: 753042 Bus

Re: [7.1] texi2any crashes with Bus Error on SPARC

f --git a/ChangeLog b/ChangeLog index 34596b8f70..1987470ed5 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,10 @@ +2023-11-04 Gavin Smith + + * info/scan.c (write_tag_contents): Check if added text is of + zero length in order to avoid subsequently calling memcpy with + a null

Re: texi2any not translating @copying contents without @documentlanguage

On Thu, Nov 02, 2023 at 10:52:56AM +0100, Patrice Dumas wrote: > On Thu, Nov 02, 2023 at 07:02:03AM +0000, Gavin Smith wrote: > > On Wed, Nov 01, 2023 at 11:10:04PM +0100, Patrice Dumas wrote: > > > > However, removing the first "@documentlanguage fr" line p

Re: texi2any not translating @copying contents without @documentlanguage

On Wed, Nov 01, 2023 at 11:10:04PM +0100, Patrice Dumas wrote: > > However, removing the first "@documentlanguage fr" line prevents the > > translation: > > That's because an element is onlt marked as 'untranslated' if there is a > @documentlanguage set at the time of parsing. It is possible to

texi2any not translating @copying contents without @documentlanguage

While testing other translation problems with texi2any, I stumbled across another problem. The following input outputs as expected: \input texinfo @c -*-texinfo-*- @documentlanguage fr @copying @defivar copying a b @error{} @end defivar @end copying @node Top @top top @node chap @chapter

Re: t/languages.t documentlanguage test failure (more failures)

On Tue, Oct 31, 2023 at 08:39:55PM +, Gavin Smith wrote: > It is something to be aware of when removing translations, that the > directories under LocaleData (not tracked in git) should be deleted > as well. This appears to have exposed a further problem where multiple translation fi

Re: t/languages.t documentlanguage test failure (fixed)

On Mon, Oct 30, 2023 at 07:25:40PM +, Gavin Smith wrote: > The test "perl -w t/languages.t documentlanguage" started failing > recently for me. This test refers to the input file > tp/tests/formatting/documentlanguage.texi which specifies > "@documentlanguage pt&quo

Re: Post release texi2any performance regression

On Sun, Oct 29, 2023 at 03:18:14PM +0100, Patrice Dumas wrote: > In commit > https://git.savannah.gnu.org/cgit/texinfo.git/commit/?id=7f1b750038f13a58bbd513a6f2f07dda5e87ad3f > I have modified the code such that with XS the first document built > out of the parser is a minimal document, without

t/languages.t documentlanguage test failure

The test "perl -w t/languages.t documentlanguage" started failing recently for me. This test refers to the input file tp/tests/formatting/documentlanguage.texi which specifies "@documentlanguage pt". The results for this test were updated recently (commit 6c70eec56d90, Patrice Dumas

Re: Norwegian translation for texinfo_document

On Sun, Oct 29, 2023 at 11:15:30AM +0100, Karl Ove Hufthammer wrote: > I can confirm that the language code for Norwegian translations should > *never* be ‘no’; it should be either ‘nb’ (for Norwegian Bokmål) or ‘nn’ > (for Norwegian Nynorsk). This has been the case since at least 2002. There >

Re: XDG directory compliance?

On Wed, Oct 25, 2023 at 07:46:01PM +0100, Gavin Smith wrote: > One thing I've been thinking of doing for a while is to make Texinfo > programs meet the XDG standard: > > https://specifications.freedesktop.org/basedir-spec/basedir-spec-latest.html > > The only file I'm aw

Re: Encoding-named locale files in po_document

On Sat, Oct 28, 2023 at 09:04:45AM -0300, Rafael Fontenelle wrote: > Hello, > > Browsing the source code repository, I noticed that the po_document > directory [1] has a few locale files named with their encoding, like > 'pt_BR.us-ascii.po' and 'pl.iso-8859-2.po'. Most of these have a more >

Re: Post release texi2any performance regression

On Sat, Oct 28, 2023 at 11:15:36AM +0200, Patrice Dumas wrote: > > At the moment, performance improvements from the new code seem > > hypothetical. > > Actually, my guess was that there would also be a performance > improvement with the XS overrides of parser >

Re: Disabling XS translation functions - please help

On Fri, Oct 27, 2023 at 01:56:21PM +0100, Gavin Smith wrote: > I consider texi2any to be in a semi-broken state at the moment, with > the new code entangled with the program in a way that I am finding > difficult to remove. I may not have much more time to work on this in > the com

Disabling XS translation functions - please help

I was attempting to disable the XS translation functions in the XS parser, as I said in another email. This would be necessary for the XS parser to function correctly, and should allow for isolating and disabling the other new texi2any code that is causing a slowdown. However, I found even this

Re: Post release texi2any performance regression

On Fri, Oct 27, 2023 at 01:22:01AM +0200, Patrice Dumas wrote: > On Thu, Oct 26, 2023 at 06:45:10PM +0100, Gavin Smith wrote: > > > > > For timing optimization, it seems to me that we should have only one > > > target, the combination were everything is done in XS.

Re: Post release texi2any performance regression

On Thu, Oct 26, 2023 at 12:13:10AM +0200, Patrice Dumas wrote: > > Can I please propose that it is made easy to disable all new XS code > > in texi2any, as I have done here, so we can avoid losing the performance > > of texi2any 7.1. I don't really care how it's done, as long as TEXINFO_XS > >

Re: Texinfo 7.1 released

On Wed, Oct 25, 2023 at 07:41:09PM +0300, Eli Zaretskii wrote: > The warning is real: wchar_t is a 16-bit data type on MS-Windows, > whereas the code assumes it's of the same width as wint_t. > > I changed the offending code to say this instead: > > if (!strchr

Re: Post release texi2any performance regression

On Tue, Oct 24, 2023 at 06:15:06PM +0200, Patrice Dumas wrote: > Maybe it is because of the C code that is run in parallel with perl code? > That would be my first guess. Hopefully, the default will be not to run > C and perl in parallel for the release. Maybe you could compare with > a run with

t/test_tree_copy.t error

t/test_tree_copy.t, which is run as part of the test suite, prints an error: $ perl -w t/test_tree_copy.t 1..7 ok 1 - modules loading ERROR: copy_tree: no tree_document_descriptor ok 2 # skip test perl not XS ok 3 - tree to texi and original match ok 4 - tree and copy to texi match ok 5 - tree

XDG directory compliance?

One thing I've been thinking of doing for a while is to make Texinfo programs meet the XDG standard: https://specifications.freedesktop.org/basedir-spec/basedir-spec-latest.html The only file I'm aware of is .infokey for the info program, but there may be others. This would mean that the file

Re: Texinfo 7.1 released

@@ +2023-10-23 Gavin Smith + + * tp/Texinfo/XS/xspara.c (get_utf8_codepoint): + Wrapper for mbrtowc/btowc. + [_WIN32]: Do not call btowc, as it was tested to be very slow + on MinGW. Report from Eli Zaretskii. + 2023-10-18 Gavin Smith Texinfo 7.1 diff

Re: Texinfo 7.1 released

On Sun, Oct 22, 2023 at 10:05:16PM +0300, Eli Zaretskii wrote: > > This patch, applied to 7.1, removes the recently added dTHX calls, > > but also removes the fprintf calls that were preventing compilation > > without it: > > It doesn't help: 1:20.7 instead of 1:21.2. I'm running out of ideas.

Re: Texinfo 7.1 released

On Sun, Oct 22, 2023 at 09:06:39PM +0300, Eli Zaretskii wrote: > Thanks. Looks like the slowdown is in XSParagraph: without it, I get > 21.8 sec, only slightly slower than Texinfo 7.0.3. Disabling MiscXS > as well yields almost the same time (0.05 sec longer) as with MiscXS, > and disabling

Re: Texinfo 7.1 released

On Sun, Oct 22, 2023 at 09:06:39PM +0300, Eli Zaretskii wrote: > > You could then disable modules with e.g. > > > > mv ../tp/../tp/Texinfo/XS/XSParagraph.la{,.disable} > > > > or > > > > mv ../tp/../tp/Texinfo/XS/MiscXS.la{,.disable} > > Thanks. Looks like the slowdown is in XSParagraph:

Re: Texinfo 7.1 released

On Sun, Oct 22, 2023 at 06:37:39PM +0300, Eli Zaretskii wrote: > > Date: Sun, 22 Oct 2023 17:30:15 +0300 > > From: Eli Zaretskii > > Cc: bug-texinfo@gnu.org > > > > > From: Gavin Smith > > > Date: Sun, 22 Oct 2023 14:23:53 +0100 > > > Cc

Re: Texinfo 7.1 released

On Sun, Oct 22, 2023 at 03:58:42PM +0300, Eli Zaretskii wrote: > > From: Gavin Smith > > Date: Sun, 22 Oct 2023 13:35:19 +0100 > > Cc: bug-texinfo@gnu.org > > > > On Sun, Oct 22, 2023 at 12:06:21PM +0300, Eli Zaretskii wrote: > > > . makeinfo is painfully

Re: Texinfo 7.1 released

On Sun, Oct 22, 2023 at 12:06:21PM +0300, Eli Zaretskii wrote: > . makeinfo is painfully slow. For example, building the ELisp > manual that is part of Emacs takes a whopping 82.3 sec. By > contrast, Texinfo-7.0.3 takes just 20.7 sec. And this is with > Perl extensions being used!

Post release texi2any performance regression

Typical texi2any run times are somewhat longer now, compared with the last released version ("time" output below) - roughly 5% longer. Any idea what's responsible for the longer run times? At what point with the new code did the performance get worse? I've run texi2any with NYTProf both for 7.1

Re: po_document/pl.iso-8859-2.po file is misplaced

On Thu, Oct 19, 2023 at 04:59:13PM +0200, Patrice Dumas wrote: > I think that it tests a case that is relative to the next change in > Changelog: > 2023-08-06 Patrice Dumas > > * tp/Texinfo/Translations.pm (gdt): have the gettext framework convert > translated strings to UTF-8, and

Re: branch master updated: * info/info.c (get_initial_file), * info/infodoc.c (info_get_info_help_node), * info/nodes.c (info_get_node_with_defaults): Use strcmp or strcasecmp instead of mbscasecmp in

On Thu, Oct 19, 2023 at 05:07:23PM +0300, Eli Zaretskii wrote: > On MS-DOS and MS-Windows, argv[0] is usually NOT what the user types > on the command line, it's what the OS fills in, and it usually puts > there the full absolute file name of the executable. Not in the context of this code where

Re: branch master updated: * info/info.c (get_initial_file), * info/infodoc.c (info_get_info_help_node), * info/nodes.c (info_get_node_with_defaults): Use strcmp or strcasecmp instead of mbscasecmp in

On Thu, Oct 19, 2023 at 03:26:51PM +0300, Eli Zaretskii wrote: > > diff --git a/info/info.c b/info/info.c > > index 8ca4a17e58..d7a6afaa2c 100644 > > --- a/info/info.c > > +++ b/info/info.c > > @@ -250,7 +250,7 @@ get_initial_file (int *argc, char ***argv, char **error) > > { > >/* If

po_document/pl.iso-8859-2.po file is misplaced

I am not happy with the presence of the po_document/pl.iso-8859-2.po file in the Texinfo sources. This was added in commit fe9bd340 (2023-08-06). The reason is that it is unlike all the other translation files in that directory, in that the file has not been provided by translators. It has only

Texinfo 7.1 released

We have released version 7.1 of Texinfo, the GNU documentation format. This package contains tools to produce documentation in various formats, including HTML and PDF, from source files in the Texinfo format. Texinfo is a text-based format with commands for marking text, document structuring,

Re: dropping completely frames in HTML output

On Tue, Oct 17, 2023 at 05:08:44PM +0200, Patrice Dumas wrote: > Hello, > > I suggest dropping completely HTML frames output code from texi2any. > frames are deprecated, this code is not well maintained, and, most > likely, not used at all. (Not for the upcoming release but afterwards). > >

Re: Document translations broken in Texinfo 7.0.90?

On Tue, Oct 17, 2023 at 01:59:20PM +0100, Gavin Smith wrote: > I've made a commit to adjust the translations. See commit 8144698cc8b6e. I forgot to include the new file in the commit; added in e3be1a6426.

Re: Document translations broken in Texinfo 7.0.90?

On Tue, Sep 26, 2023 at 08:34:52PM +0100, Gavin Smith wrote: > On Wed, Aug 30, 2023 at 06:19:53PM +0200, Patrice Dumas wrote: > > > I wonder if there is anything that can be done with the gettext API to > > > try for a translation both with and without a context. Wh

Re: implementation language [was: library for unicode collation in C for texi2any?]

On Sun, Oct 15, 2023 at 12:00:51PM -0700, Per Bothner wrote: > I'm far from a C++ expert these days, but some ideas: > > * First of course you can define some helper methods: > > class TargetElement { > Extra *extra; > Command *unit_command() { return extra ? extra->init_command() : nullptr;

Re: Texinfo 7.0.94 pretest available

On Sun, Oct 15, 2023 at 03:17:17PM +0300, Eli Zaretskii wrote: > > From: Gavin Smith > > Date: Sun, 15 Oct 2023 12:57:46 +0100 > > Cc: bug-texinfo@gnu.org > > > > On Sun, Oct 15, 2023 at 12:00:47PM +0300, Eli Zaretskii wrote: > > > Thanks. > > >

Re: implementation language [was: library for unicode collation in C for texi2any?]

On Sat, Oct 14, 2023 at 01:49:26PM -0700, Per Bothner wrote: > On 10/14/23 09:12, Patrice Dumas wrote: > > On Thu, Oct 12, 2023 at 10:25:23AM -0700, Per Bothner wrote: > > > C++ has a more extensive and useful standard library than C. > > > > I guess there is an hash map, but I am not sure that

MinGW "info" program broken?

On Sun, Oct 15, 2023 at 01:24:32PM +0200, Bruno Haible wrote: > - The behaviour of the 'ginfo' program on MSVC is the same as on mingw, > albeit not really useful currently: './info -f texinfo.info' spits out > the entire manual to stdout at once. It looks like the device gets set >

Re: Texinfo 7.0.94 on native Windows

On Sun, Oct 15, 2023 at 01:24:32PM +0200, Bruno Haible wrote: > On mingw 5.0.3, there are no test failures any more. > A big improvement, compared to 7.0.90 (see my earlier report at > ). This is likely to the fix that Eli sent

Re: Texinfo 7.0.94 pretest available

On Sun, Oct 15, 2023 at 12:00:47PM +0300, Eli Zaretskii wrote: > After fixing the above, most of the tests pass, but 3 texi2any tests > fail: > > FAIL: test_scripts/layout_formatting_info_ascii_punctuation.sh > FAIL: test_scripts/layout_formatting_info_disable_encoding.sh > FAIL:

Re: Texinfo 7.0.94 pretest available

On Sun, Oct 15, 2023 at 12:00:47PM +0300, Eli Zaretskii wrote: > Thanks. > > This doesn't compile with MinGW, because some of the dTHX additions I > needed for the previous pretest were not installed(?), and are still > missing. The patch I needed is below. I hadn't installed those changes

Re: library for unicode collation in C for texi2any?

On Thu, Oct 12, 2023 at 11:39:14AM +0200, Patrice Dumas wrote: > Hello, > > There is a translation to C of texi2any code going on, for the future, > after the next release, mainly for the conversion to HTML in a first > step. > > One thing I could not find easily in C is something to replace the

Texinfo 7.0.94 pretest available

A pretest distribution for the next Texinfo release (7.1) has been uploaded to https://alpha.gnu.org/gnu/texinfo/texinfo-7.0.94.tar.xz There have not been many changes since the previous pretest. We are making this pretest mainly to test build fixes for the MinGW platform. We hope to release

Re: implementation language [was: library for unicode collation in C for texi2any?]

On Thu, Oct 12, 2023 at 01:24:07PM -0700, Per Bothner wrote: > On 10/12/23 11:35, Gavin Smith wrote: > > Calling [using Perl] a "mistake" is a very strong statement! Why do you > > say that? > > Surely texi2any 7.0.3 (2023) is more func

Re: library for unicode collation in C for texi2any?

On Fri, Oct 13, 2023 at 07:31:29AM +, Werner LEMBERG wrote: > > >> OK, no tailoring. I wasn't aware of those differences, thanks for > >> pointing me to it. > >> > >> Hopefully, we agree that `@documentlanguage` should set a > >> language-specific collation for the index. > > > > Without

Re: Texinfo 7.0.93 pretest available

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: > > > I will send you a diff

Re: Translation of some document strings with contexts does not work at all

On Thu, Oct 12, 2023 at 11:25:13PM +0200, pertu...@free.fr wrote: > I wouldn't say that, this untranslated stuff arise only in specific > cases. That being said, your analysis looks solid and the code buggy. > > The issue should be fixed in master, thanks for the report. That looks great, thank

Re: implementation language [was: library for unicode collation in C for texi2any?]

On Thu, Oct 12, 2023 at 10:25:23AM -0700, Per Bothner wrote: > On 10/12/23 02:39, Patrice Dumas wrote: > > There is a translation to C of texi2any code going on, for the future, > > after the next release, mainly for the conversion to HTML in a first step. > > I've always thought that C++ is the

Translation of some document strings with contexts does not work at all

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: > > > I will send you a diff

Re: Texinfo 7.0.93 pretest available

On Wed, Oct 11, 2023 at 02:59:06PM +0300, Eli Zaretskii wrote: > > From: Gavin Smith > > Date: Tue, 10 Oct 2023 20:24:47 +0100 > > Cc: br...@clisp.org, bug-texinfo@gnu.org > > > > On Tue, Oct 10, 2023 at 02:55:09PM +0300, Eli Zaretskii wrote: > > &

Re: Texinfo 7.0.93 pretest available

On Tue, Oct 10, 2023 at 10:03:46PM +0300, Eli Zaretskii wrote: > > From: Gavin Smith > > Date: Tue, 10 Oct 2023 18:09:15 +0100 > > Cc: Eli Zaretskii , bug-texinfo@gnu.org > > > > On Mon, Oct 09, 2023 at 11:32:49PM +0200, Bruno Haible wrote: > > > Ga

Re: Texinfo 7.0.93 pretest available

On Tue, Oct 10, 2023 at 02:55:09PM +0300, Eli Zaretskii wrote: > > If this simple stub is preferable to the Gnulib implementation for > > MS-Windows, (e.g. it makes the tests pass) we could re-add it again. > > We can do that, but I think we should first explore a better > alternative: use UTF-8

Re: Texinfo 7.0.93 pretest available

On Mon, Oct 09, 2023 at 11:32:49PM +0200, Bruno Haible wrote: > Gavin Smith wrote: > > It is supposed to attempt to force the locale to a UTF-8 locale. You > > can see the code in xspara_init that attempts to change the locale. There > > is also a comment b

Re: Texinfo 7.0.93 pretest available

On Mon, Oct 09, 2023 at 05:06:39PM +0300, Eli Zaretskii wrote: > > I wonder if for some of the non-ASCII characters wcwidth is returning 0 or > > -1 leading the line to be longer. > > Yes, quite a few characters return -1 from wcwidth, in particular the > ȷ character above (which explains the

Re: Texinfo 7.0.93 pretest available

On Sun, Oct 08, 2023 at 08:45:11PM +0300, Eli Zaretskii wrote: > > 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, f

Re: Texinfo 7.0.93 pretest available

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: > > -(ì) @'{e} é (é) @'{@dotless{i}} í (í) @dotless{i} ı (ı) @dotless{j} ȷ > -(ȷ) ‘@H{a}’ a̋ ‘@dotaccent{a}’ ȧ (ȧ) ‘@ringaccent{a}’ å (å) >

Re: Texinfo 7.0.93 pretest available

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 > > > > 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

Re: Texinfo 7.0.93 pretest available

On Sun, Oct 08, 2023 at 04:42:05PM +0300, Eli Zaretskii wrote: > 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 almost all the install-info > tests fail with Permission

Re: Texinfo 7.0.93 pretest available

On Sun, Oct 08, 2023 at 04:38:46PM +0300, Eli Zaretskii wrote: > > According to the documentation for getline, > > > > If you set ‘*LINEPTR’ to a null pointer, and ‘*N’ to zero, before > > the call, then ‘getline’ allocates the initial buffer for you by > > calling ‘malloc’. This

Re: Texinfo 7.0.93 pretest available

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 implementation of getdelim, and that one has > a subtle bug, which rears its ugly head because the second argument to > getline, here:

Re: Texinfo 7.0.93 pretest available

> > or for a smaller file, > > > > /d/usr/Perl/bin/perl ../tp/texi2any.pl info-stnd.texi -c DEBUG=1 > > > > to get an idea of where the crash is occurring. > The output of the last command is: GET_A_NEW_LINE > > and then it crashes. > > Does this help? The program appears to crash after

Re: Texinfo 7.0.93 pretest available

On Sat, Oct 07, 2023 at 04:00:17PM +0300, Eli Zaretskii wrote: > > 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 > &

Re: question about node printing in t/Infokey-config

On Sat, Sep 30, 2023 at 10:21:13PM -0700, Mike Fulton wrote: > Hi, > > I am trying to understand why testcase ./t/c-u-m-x-scroll-forward.sh fails > for me on z/OS. > From the trace, I see that it is reading the characters from the > pseudotty in and correctly > processing them, until it gets to

Texinfo 7.0.93 pretest available

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 There are not many changes since the previous pretest distribution: * Make a minor change to a couple of strings to allow them to be translated * Fix

Re: Is @emph{See} translatable?

On Tue, Sep 26, 2023 at 09:53:38PM +0100, Gavin Smith wrote: > On Tue, Sep 26, 2023 at 09:12:23PM +0200, Petr Pisar wrote: > > # FIXME: "See" should be translatable, but gettext insists that it's an > > identifier. > > #. TRANSLATORS: redirect to another in

Re: Is @emph{See} translatable?

On Tue, Sep 26, 2023 at 09:12:23PM +0200, Petr Pisar wrote: > # FIXME: "See" should be translatable, but gettext insists that it's an > identifier. > #. TRANSLATORS: redirect to another index entry > #: tp/Texinfo/Convert/HTML.pm:5675 > #, perl-brace-format > msgid

Re: Document translations broken in Texinfo 7.0.90?

On Wed, Aug 30, 2023 at 06:19:53PM +0200, Patrice Dumas wrote: > > I wonder if there is anything that can be done with the gettext API to > > try for a translation both with and without a context. What occurs to > > me is testing the return value of pgettext, seeing if it is equal to the > >

Re: Texinfo 7.0.92 pretest on NetBSD 9.0

On Thu, Sep 21, 2023 at 06:24:01PM +0200, Patrice Dumas wrote: > Hello, > > On Wed, Sep 20, 2023 at 08:44:34PM +0100, Gavin Smith wrote: > > Perhaps we should keep on resetting CFLAGS and LDFLAGS (in line with > > the autoconf manual), but leave CPPFLAGS alone due to gnu

Re: overfull box in printed toc with @/

On Wed, Sep 20, 2023 at 03:22:58PM -0600, Karl Berry wrote: > Please push it out to ftp.gnu.org? --best, karl. Done.

Re: Texinfo 7.0.92 pretest on NetBSD 9.0

Patrice wrote: > I think that the first one is not such an issue, as it is set quite > early, the libunistring module is called afterwards. I agree with this. Bruno wrote: > I first did it like this with libintl, ca. 25 years ago, and this approach > to modify CPPFLAGS works fine, except there

Re: overfull box in printed toc with @/

On Tue, Sep 19, 2023 at 10:51:26AM -0600, Karl Berry wrote: > Hi Gavin - with this input file: > > \input texinfo > @contents > @chapter Test > @section Sec > @subsection > foofoo@code{\DeclareRobustCommand@{@var{cmd}@}[@var{num}][@var{default}]@/@{@var{definition}@} > } > @bye > > I get an

Re: Texinfo 7.0.92 pretest on NetBSD 9.0

On Tue, Sep 19, 2023 at 07:43:26PM +0200, Patrice Dumas wrote: > Hello, > > Thanks for the analysis! > > On Tue, Sep 19, 2023 at 04:22:42PM +0200, Bruno Haible wrote: > > * But you can see from the log above that no -I option is in use that > > allows the compiler to find the *installed* . > >

Re: Texinfo 7.0.92 pretest on CentOS Stream 9

On Tue, Sep 19, 2023 at 06:02:09PM +0200, Patrice Dumas wrote: > Hello Bruno, > > The issue seems to be Unicode::Normalize missing. This is not > surprising if Centos is aiming for a minimalist default perl > interpreter. > > A simple fix would be to require it in the > [Perl version and

Re: Texinfo 7.0.92 pretest on AIX 7.3.1

On Tue, Sep 19, 2023 at 03:29:57PM +0200, Bruno Haible wrote: > This is already fixed by gnulib commit > https://git.savannah.gnu.org/gitweb/?p=gnulib.git;a=commitdiff;h=17c85713388407841f5c9978ecb3ccaf34ef76f1 > Interestingly, texinfo/tp/Texinfo/XS/gnulib/lib/stddef.in.h has the fix > but

Re: "error: too deeply nested expressions" for large Perl input file

On Mon, Sep 18, 2023 at 09:05:45PM +0200, Bruno Haible wrote: > Gavin Smith wrote: > > In gettext 0.22, there is an error running xgettext with a large input > > file: > > > > $ /usr/local/bin/xgettextHTML.pm > > HTML.pm:8052: error: too deeply neste

Re: Document translations broken in Texinfo 7.0.90?

On Mon, Sep 04, 2023 at 07:22:49PM +0200, Jean-Charles Malahieude wrote: > Le 04/09/2023 à 18:31, Gavin Smith a écrit : > > > > I'm sorry, I don't know what you mean by "the FTP". > > > > Sorry, I used to call it "Free Translation > Project"

Re: install-info truncates all files at 8192 bytes

On Wed, Sep 13, 2023 at 12:44:23PM +0200, Andreas Schwab wrote: > Commit 25584009e7 broke reading files bigger than 8192 because it tries > to read zero byte after the first 8192 bytes are read. This was introduced on 2023-08-18 by my change - I hope this has not affected anybody too badly. I've

Texinfo 7.0.92 pretest available

A pretest distribution for the next Texinfo release (7.1) has been uploaded to https://alpha.gnu.org/gnu/texinfo/texinfo-7.0.92.tar.xz Changes from 7.0.91 to 7.0.92: * A bad bug in install-info has been fixed where the dir file would be truncated at 8192 bytes (bug introduced 2023-08-18).

Re: catcode problems with `@include`

On Tue, Sep 12, 2023 at 08:32:10AM +, Werner LEMBERG wrote: > > [texinfo.tex version 2023-08-13.14] > > > Please consider the attached files. If I say > > ``` > luatex foo.texinfo > ``` > > the `@tex` environment within this file works just fine, and file > `foo.lua` is correctly loaded.

<    1   2   3   4   5   6   7   8   9   10   >