Re: Take account of splitting option in gendocs.sh

+ gendocs: support chapter- and section-level split Seems sensible to me. Basically making the html-by-node part of the template conditional along with the other split options? (Overall, it seems to me that several of these variants are pretty pointless nowadays, but never mind.) FWIW, in

toc multiline section titles misaligned in TeX

In the toc, if a chapter/section/whatever titles breaks across lines, the second line is not aligned with the first. The output in the main text is ok. Example doc follows. I'll attach the output I get with texinfo.tex [version 2023-07-02.10]. --thanks, karl. \input texinfo @contents @node chap

Re: toc multiline section titles misaligned in TeX

I have done some work on this and it should be aligned in the latest version (2023-07-17.15, git commit 64c51c055836b9980). Thanks Gavin. It looks fine now. I appreciate your doing this. I couldn't remember if it ever aligned either :). Another (separate but sort of related) problem that

Re: toc multiline section titles misaligned in TeX

It's possible to do this by reading the toc file another time for the sole purpose of getting the widths of the section numbers in each chapter. Yeah. Why I never did it. Thanks for tackling it. I think the output does not necessarily look ideal. Not ideal, but a vast improveme

Re: toc multiline section titles misaligned in TeX

Subject: Re: toc multiline section titles misaligned in TeX Thank you for doing all that, Gavin. It looks good to me. Can the new version be pushed out to ftp.gnu.org? --thanks, karl.

overfull box in printed toc with @/

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 overfull box in the toc (texinfo.tex version 2023-09-12.17): Overfull \hbox (65.62492p

Re: overfull box in printed toc with @/

So I've commited the change ... Please let us know if the change works ok with your manual and if there are any regressions. Indeed, current texinfo.tex in git fixes the overfull hbox bug in the toc, and I haven't noticed any regressions or other problems. Thanks! Please push it ou

Re: Texinfo.tex, problem with too-long table inside @float

I think I'd suggest omitting the \vtop if LOC is set to some new value, like "longfloat". If table material was ever actually floated, including "here", it would need to be in a vbox since it should not be split across pages, as Gavin already pointed out. Actually doing something sensible with a m

Re: makeinfo 7.1 misses menu errors

I believe this is an intentional feature in recent Texinfo versions. To get the warnings back, you need to run makeinfo with the command-line option "-c CHECK_NORMAL_MENU_STRUCTURE=1". Thanks for the hint. I reported a similar thing in July 2023, https://lists.gnu.org/archive/html/help

Re: makeinfo 7.1 misses menu errors

Hi Gavin, The problem as I remember it was that the error messages are awful: No argument, but having any message at all is infinitely better than silence. I urge you to restore them by default, suboptimal as they are. It's true that those msgs as such have never made a great deal of sense t

Re: makeinfo 7.1 misses menu errors

This goes against the practice of the vast majority of existing Texinfo manuals, so this existing practice should be well supported. Indeed. That is the crucial point. Those warnings are needed in well over 99% of existing manuals, as far as I've seen :). I think that it could be poss

Re: makeinfo 7.1 misses menu errors

Hi Patrice, then they can set CHECK_NORMAL_MENU_STRUCTURE on explicitely. It's easy to say that, but it creates an incompatibility for the 99.99% case. I can't set it for makeinfo 7.x without giving people using 6.x (which is most everyone, downstream) a useless warning. Nor can I omit i

Re: makeinfo 7.1 misses menu errors

Patrice: sure, I understand. Gavin: let me add one more point: if the warning is not reenabled by default, you are essentially forcing every maintainer of every manual to add a new flag to their makeinfo invocation, conditional on the makeinfo version. This seems ... bad. --thanks, karl.

Re: texinfo-4.13.93 pretest available

Hi Norbert, because help2man is missing, and it tries to re-generated texi2dvi.1 Is there a reason for that? Sure, of course there's a reason :). The dependency on the source file is the only way man page regeneration can work (reliably) :). we patch texi2dvi in a trivial way. Is y

Re: [PATCH] install-info: fix memory leak

if (!f) { + free (*opened_filename); *opened_filename = concat (filename, ".xz", ""); f = fopen (*opened_filename, FOPEN_RBIN); } Thanks. I installed it. I couldn't see any reason why it was lacking in the .gz case (just above this), so I a

Re: texinfo-4.13.93 pretest available

Hi, Please incorporate this update in po_document/ Thanks for the effort, but changes to translations must go through the Translation Project, http://translationproject.org. Please contact the French team for Texinfo about this. Best, Karl

Re: texinfo-4.13.93 pretest available

Not sure if you want ;-) - trap "cleanup" 0 1 2 15 + trap "cleanup" 0 HUP INT TERM When I grep for trap in my directory of GNU binaries, all I see is numbers, not names, so I think I'll decline to install that. Don't especially want to fix something that isn't broken. besides t

[bug #28316] partial verbatim inclusion

Update of bug #28316 (project texinfo): Assigned to: olegkat => None ___ Reply to this item at: ___ Mes

Re: Unstable sorting of index items

Hi Ben, --- a/makeinfo/index.c +++ b/makeinfo/index.c Thanks for the fix, but the makeinfo implementation in C is no longer maintained. I'm guessing the replacement in Perl (in the tp/ directory of the sources) also does a stable sort of index entries. Patrice, can you confirm? k

Re: [NITPICK] build: AC_PREREQ minor issues

so that the explicit AC_PREREQ by Texinfo is redundant. Thanks, I removed it.

Re: info equivalent of "man -wa"?

i'm mostly interested emulating man(1)'s -wa behavior As far as I know, info doesn't have anything like -a. I doubt it would be hard to add, though. Sergey, any chance of looking into that? In the case of info, -a would only make sense with things other than normal "bring up an info page",

texinfo-4.13.94 pretest available

I've put up the next Texinfo pretest: http://alpha.gnu.org/gnu/texinfo/texinfo-4.13.94.tar.xz ftp://alpha.gnu.org/gnu/texinfo/texinfo-4.13.94.tar.xz No new features (since the last pretest) to speak of. Full NEWS: http://cvs.savannah.gnu.org/viewvc/texinfo/texinfo/NEWS?view=markup As before,

Re: info equivalent of "man -wa"?

i'll note that man(1) does support -a in its normal "view the manpage" Yep, I use it all the time :). i don't know how hard that would be to emulate in info(1), It makes no sense to do so. man is fundamentally a non-interactive program that outputs to stdout. As I said before, info i

[bug #38168] support --all

URL: Summary: support --all Project: texinfo - GNU documentation system Submitted by: karl Submitted on: Fri 25 Jan 2013 09:05:22 AM PST Category: info Release:

texinfo-4.13.95 pretest available

I've put up the next Texinfo pretest: http://alpha.gnu.org/gnu/texinfo/texinfo-4.13.95.tar.xz ftp://alpha.gnu.org/gnu/texinfo/texinfo-4.13.95.tar.xz For translators, there is a new texinfo_document domain in the Translation Project (http://translationproject.org/domain/texinfo_document.html).

Re: some more itching msgids

What you write is why I suggested what I did: tex4ht.pm failed to open %s: %s Or perhaps: makeinfo:tex4ht.pm failed to open %s: %s since tex4ht.pm isn't what the user invoked. k

texinfo-4.13.96 pretest available

I've put up the next Texinfo pretest: http://alpha.gnu.org/gnu/texinfo/texinfo-4.13.96.tar.xz ftp://alpha.gnu.org/gnu/texinfo/texinfo-4.13.96.tar.xz The main change is for translators: we changed many messages for consistent capitalization. Sorry about that, but it needed to be done. Also, t

Re: texinfo-4.13.96 pretest available

Changelog says two times 4.13.95 Yes, thanks, fixed. k

Re: texinfo-4.13.96 pretest available

Would you mind feeding the FTP? Sorry, I don't understand. Both http://alpha.gnu.org/gnu/texinfo/texinfo-4.13.96.tar.xz ftp://alpha.gnu.org/gnu/texinfo/texinfo-4.13.96.tar.xz work as far as I can tell. If you mean the files at the Translation Project, that's up to the coordinators the

Re: Local Preferences in Texinfo files

So maybe it would be a good idea to put a sentance or two to that effect into the Texinfo manual - perhaps it is already there The possibility of having a texinfo.cnf has been mentioned in the manual for umpteen years, since I first implemented it. Another idea to consider: If such lo

[bug #38168] support --all

Follow-up Comment #2, bug #38168 (project texinfo): It shouldn't be too bad if limited to --where, at least for starters? Anyway, please hold off on committing anything (just in case), since I think we're about to make the release. ___ Re

texinfo-4.13.97 pretest available

Well, since we made some changes to the test setup and a few other things, it seems prudent to have one more pretest: http://alpha.gnu.org/gnu/texinfo/texinfo-4.13.97.tar.xz ftp://alpha.gnu.org/gnu/texinfo/texinfo-4.13.97.tar.xz Full NEWS: http://cvs.savannah.gnu.org/viewvc/texinfo/texinfo/NEW

Re: Bug#700354: info: segfault on tab completion on large terminals

> $ echo $LINES $COLUMNS > 64 208 > > Start info with the make info file from make-doc 3.81-5.1: > $ info make > > Enter these keystrokes: > i p TAB TAB > > Result: segfault. I can reproduce this, even without all the special compiler flags (-g on

Re: [bug-recutils] Recutils manual does not build.

Funny enough the pre-release 4.13.94 of makeinfo does not complain about the missing nodes... Please send the Texinfo file that is problematic. k

Re: texi2pdf (Texinfo 4.13.97) problem: missing footer

please find bug.texi and bug.pdf (among other files), the latter missing the right-side footer on page 3. I'll look at it later, though I'm not sure it will be fixable. I thought there was a warning in the manual about @thissection not being reliable, but I don't see it now :(. Anyway, t

texinfo-5.0 available

We have released version 5.0 of Texinfo, the GNU documentation format. It's available via a mirror (xz is much smaller than gz, but gz is available too just in case): http://ftpmirror.gnu.org/texinfo/texinfo-5.0.tar.xz http://ftpmirror.gnu.org/texinfo/texinfo-5.0.tar.gz Or if automatic redire

Re: broken link

http://www.gnu.org/software/texinfo/manual/texinfo/html_node/Texinfo-Document-Structure.html [is broken] Indeed. Thanks for the report. It seems not all of the new files I checked in actually made it to the live www.gnu.org web server. I have to ask the FSF sysadmins to fix it, so it w

Re: texinfo-5.0 available

So will the change below to install-info/Makefile.am do the trick? Looks like it. Please send the manifest file. Also, will 'transform' rename the file to install-info.exe.manifest at "make install" time? I believe so. I guess we'll find out. k

Re: HP-UX 11 build issues with texinfo 5.0

Hi Richard, * gnulib/lib/xalloc.h: Forwarded to gnulib, as you saw. at line 28 of info/info-utils.c: #ifdef __hpux #define va_copy(ap1,ap2) memcpy((&ap1),(&ap2),sizeof(va_list)) #endif Ok, installed. export PATH=/usr/contrib/bin:$PATH It seems like this is better to

Re: makeinfo 5.0 is 34x slower when building Emacs info

but 224 seconds with texinfo 5.0 Paul - of course we were greatly concerned about the slowdown. That's why I specifically mentioned it in the announcement and NEWS file and documentation. The short answer is no, nothing can be done. If/Since you edit Texinfo files often enough that it's so

texinfo sources now in svn

For the sake of those few people who might be interested: we are now developing texinfo in subversion rather than cvs. https://savannah.gnu.org/svn/?group=texinfo Unfortunately this means the cvs-specific urls into the sources in various places are invalidated. We'll have to fix them as we find t

Re: TRAMP User Manual problems with Texinfo 5.0

Hi Patrice, > > @set x@c > > I am not sure how this should be interpreted? Same as @set x The @c and everything following should be ignored. (The newline is already not included in an @set value, of course.) I think @set x@c and @set x @c are equivalent, because we already ignore s

Re: makeinfo 5.0 is 34x slower when building Emacs info

Well, I am not much of a fan of C++, but I recognize your arguments, and anyway, all that doesn't matter one way or another. What matters is what someone is willing to actually write and maintain. Patrice was willing to put in the (enormous amount of) work necessary to create a new implementation

Re: makeinfo 5.0 is 34x slower when building Emacs info

Hi Joel, Is there a free Perl compiler? I mentioned Perl compilers in my first message :). In short, they offer no substantive help. There's the usable compiler that you found which precompiles to byte code, but the Perl-source parse phase is not the time consumer here. So it would help a

Re: texinfo-5.0 available

+static void pc_initialize_terminal (char *); static void w32_info_init (void) { - static void pc_initialize_terminal (char *); Applied, thanks.

Re: texinfo-5.0 available

I submit a correct one below, and it includes the manifest file (which must have DOS CR-LF EOL Done, I hope.

Re: [PATCH] Please, add lzip support to info and install-info

The attached patch adds support for lzip-compressed files (.lz) to info and install-info. Thanks, installed.

[bug #38380] texinfo 5.0 has case-sensitve filesystem test

Follow-up Comment #3, bug #38380 (project texinfo): To skip the test: how about creating a file foo.html, and then seeing if FOO.HTML exists? The problematic files: t/results/converters_tests/sample_utf8/res_html/index.html and Index.html. Maybe the test itself (if it isn't skipped) has to creat

Re: TRAMP User Manual problems with Texinfo 5.0

it was consistent with some changes in the GNU coding standards. The coding standards themselves don't require a particular style of quoting, but almost all GNU packages are using '...' now and a number of people asked for this, as I recall. Failing to include the change in NEWS was a mistake

Re: texinfo-5.0 in-place upgrade doesn't symlink makeinfo

ln: failed to create symbolic link â€˜/usr/bin/makeinfoâ€™: File exists Oops. Thanks for the report, fixed for next time. Thanks, Karl

Re: ouch, a hundred and fifty untranslated strings

What went wrong? I bcc'd coordinator on all pretest and official release announcements. Maybe the bcc made the messages not be seen? But I'm pretty sure I've done that in the past. And I know other maintainers do. shouldn't the absence of incoming updated translations have triggered

Re: inter-@deftypefun spacing discrepancy

Perhaps it could be added to NEWS as a "deliberate discrepancy"? Yes, I will. I imagine there are many generated documents I doubt it is all that "many", since the manual always more or less implicitly recommended putting in blank lines in the source document where you wanted them, a

texinfo-5.0.90 pretest available

Here's the first pretest for the next release: ftp://alpha.gnu.org/gnu/texinfo/texinfo-5.0.90.tar.xz http://alpha.gnu.org/gnu/texinfo/texinfo-5.0.90.tar.xz The NEWS below. As you might expect, this was about fixing bugs and reducing incompatibilities found in 5.0. Keep those reports coming :

Re: texinfo-5.0.90 pretest available

There's only one previous *implementation* in the usual meaning of the word, but sure, I'll explicitly mention pre-5.0. Thanks, k

[bug #38470] Missing check for termcap library -ltinfo (part of ncurses bundle)

Update of bug #38470 (project texinfo): Open/Closed:Open => Closed Status:None => Fixed ___ Follow-up Comment #1: thanks for the repo

Re: one sentence split over two msgids

one sentence, and should be offered as such for translation. Right, thanks. To match similar messages, maybe the string should drop the second colon? "tex4ht.pm: could not open %s" I was under the impression that we usually did end with the colon. I remember writing messages lik

texinfo-5.0.91 pretest available

Here's the next (and hopefully last) pretest for the next release: ftp://alpha.gnu.org/gnu/texinfo/texinfo-5.0.91.tar.xz http://alpha.gnu.org/gnu/texinfo/texinfo-5.0.91.tar.xz Just a couple of changes for translators, etc. I plan to release 5.1 by Monday at the latest, barring disaster. Than

texinfo-5.1 available

We've released version 5.1 of Texinfo, the GNU documentation format. It's available via a mirror (xz is much smaller than gz, but gz is available too just in case): http://ftpmirror.gnu.org/texinfo/texinfo-5.1.tar.xz http://ftpmirror.gnu.org/texinfo/texinfo-5.1.tar.gz Or if automatic redirect

Re: info.info conflict between emacs and texinfo

Both emacs and texinfo install the info.info info file. This needs to be resolved. Fine, I'll remove it from Texinfo, since in practice info.texi has been maintained in Emacs for many years. (I've been copying it from the latest Emacs distribution before making a Texinfo release.) k

Re: info.info conflict between emacs and texinfo

But isn't that strange ... I mean texinfo ships the info reader, Emacs ships an Info reader too -- the original one, and one far more commonly used than standalone Info, I suspect. And most all changes to info.texi in the last X years have been about info.el and Emacs things. shouldn't i

Re: info.info conflict between emacs and texinfo

Sorry, yes, of course, info-stnd is the doc of the info program. Mixed it with the documentation of info format. Uffa. Actually, info.texi is mostly a tutorial on using Info readers -- applicable to both readers. It's not at all about documenting Info format (Patrice and I wrote that for

Re: Fix a crash in stand-alone Info due to bad indexing of a string

which caused us to write outside of a string's bounds when we up-case or down-case a partial match found by index-search. The result was that the following call to 'free' crashed. Thanks for the report. 1) My first attempts did not reproduce it, though of course I don't doubt there i

Re: MinGW build issues in Texinfo 5.1

The patches to fix that are below. Ok, installed. (Btw, does the fact that I can check out the repository using svn+ssh and my savannah user name mean that I can commit changes myself?) Yes. (You've been a member of the texinfo project on savannah for a very long time. Maybe origin

Re: Bad use of EXEEXT in man/Makefile.am

I guess a fix would be to change man_rule_0 so that it won't use EXEEXT with makeinfo. I guess. If this doesn't work, or if there's a simpler way, let me know. k --- Makefile.am (revision 5242) +++ Makefile.am (working copy) @@ -42,13 +42,15 @@ MAKEINFO = $(PERL) -I "$(tpdir)" "$(tpdir

Re: makeinfo swallows page breaks

Guileœôòùs Texinfo parser Argh. The idea of a full second Texinfo parser in GNU is fundamentally wrong. If you want to call it a "Guile docstring parser, whose language happens to bear some resemblance to a subset of Texinfo", fine. Anyway, your change to use more Guile in the Guile build p

Re: Fix a crash in stand-alone Info due to bad indexing of a string

Try 'info' from Texinfo 4.13, and you will see the same case changes. I see. I never ran into that. I was just comparing against 5.1 info. The bug in 5.0 inadvertently removed this feature. It's not a feature, it's a bug. The program should report the text of the actual index entry th

Re: Fix a crash in stand-alone Info due to bad indexing of a string

The capitalization is intended to highlight the part of string that is matched. Oh. Never would have guessed that. By all means, then, let it stand/be restored. Especially if/since Emacs is going to do it too. Thanks, karl

Re: Output looks different in PDF / HTML

Hi Petra, @itemize takes an argument specifying the item marker to use. That always defaults to a bullet in TeX, Info, etc., regardless of nesting. In the nested list, you need to explicitly say @itemize @minus (or whatever marker you want). Here is the section in the manual that talks about it:

Re: makeinfo swallows page breaks

In contrast with Karl, I am not that afraid of other parsers, as long as they check their results In theory, that would be fine. In practice, everyone else who has ever attempted to write a parser fails to maintain it over time --- let alone do anything as rigorous as the checking you are

Re: "special" spaces in Texinfo parsing and output

also lines consisting only of spaces are emptied in @example and the like Removing trailing whitespace in the Info output seems like the one thing that is ok to me, though it would also be ok to preserve it. I see that leading and internal whitespace is already preserved inside @example.

Re: "special" spaces in Texinfo parsing and output

It seems that that the makeinfo in C considered explicitly spaces to be something along [\r\n\t ]. Yes. something sensible and consistent with TeX/LaTeX, having something sensible coming first. Agreed, but fortunately, there's no conflict. (La)TeX does something sensible, namely

Re: texinfo-5.0+ incompatible with GDB's gdbint.info image

infobug.tar.gz = https://bugzilla.redhat.com/attachment.cgi?id=717865 Sigh, I thought that had been fixed. Thanks for the report, Sergey or I will look at it asap. k

Re: bug#13965: info.info conflict between emacs and texinfo

Hi Glenn, Why does it matter? It is the same file, just provided by two packages. I know. I keep them synced. It's Andreas's request, not mine. The current situation is totally not a problem in my own life, but I can imagine it creating a discrepancy when there is version skew and a new ve

Re: bug#13965: info.info conflict between emacs and texinfo

No, you don't. Evidently I messed up for texinfo 5.1. Sorry. Shoot me. +@include doclicense.texi How about naming the file fdl.texi, like virtually every other package does? k

Re: bug#13965: info.info conflict between emacs and texinfo

If it really helps you, we could rename it. Well, obviously it is not a stopper. I can edit the file when I import it and ignore that difference. We'll have to change 58 files, several of which also live in other repositories. The point is that nearly every other package in GNU use

Re: @option should maybe use @w

Hi. I just noticed a case, using texinfo.tex 2012-11-08.11, where @option{--posix} got line broken between the second hyphen and the `posix'; That's awful. Thanks for the report. Can you send me the paragraph in question, please? perhaps @option should use @w around it's argum

Re: docbook generation problem with @image

Separate from what you're actually reporting ... @c FIXME: One day, it should not be necessary to have two cases, @c but rather just the one without the "txt" final argument. I remember talking about this with you before, but not what the conclusion was (as usual). If you

Re: [bug #38795] texi2any makes CR in output when input is mixed CR-LF and LF files

[Eliminating bbdb-info] FWIW, my views are: - that stuff in the doc about "only recognizes newline" is left over from many, many years ago (the original Elisp texinfo-format-buffer, looks like to me). I'll remove or change it. - I think both C and Perl makeinfo have always preserved the CRLF's

[bug #38795] texi2any makes CR in output when input is mixed CR-LF and LF files

Update of bug #38795 (project texinfo): Open/Closed:Open => Closed ___ Follow-up Comment #1: Discussion on list ... ___ Reply to th

[bug #38168] support --all

Update of bug #38168 (project texinfo): Open/Closed:Open => Closed Status: Ready For Test => Fixed ___ Follow-up Comment #4: all sounds good. cl

Re: minor typ-o in the manual

The last quoted sentence should probably read either Indeed. Will fix. Thanks Alex!

Re: install-info failure under LANG=it_IT.UTF-8

Subject: install-info failure under LANG=it_IT.UTF-8 Thanks for the report, will investigate as soon as I have a chance.

[bug #38997] "@itemx must follow @item" is now an error

Update of bug #38997 (project texinfo): Open/Closed:Open => Closed ___ Follow-up Comment #1: Hi Hilmar - thanks for the suggestion. yeah, if we had to do it over, a warning would probably h

Re: Bug#710171: Allow math rendering in HTML

> texi2html, which texinfo superseeds, allowed the rendering of @math > environments to images in HTML output. Please add similar functionality > to texinfo. Is this planned Well, Patrice and I haven't talked about that specifically. Patrice? (We have had other discussions about

Re: compilation error with SVN rev5259

Hi Werner, Not enough arguments for Texinfo::Structuring::merge_indices at ../tp/Texinfo/Convert/IXIN.pm line 625, near "$index_names)" Well, since the problem isn't apparent, here are some random speculations: 1) I wonder if something went wrong with the svn checkout and the sourc

Re: Searching info files using info browser

Hi Gavin, * Edit previous searches made with "s" or "/". If I press the up key, I get a message "[`ESC O a' is invalid]". Pressing Alt-P gives the message "[`ESC p' is invalid]". Oops, bad. I get those same errors. Not bound in that keymap, I surmise. * Skip the current screen

Re: facing pages in PDF browsers

- \pdfcatalog{/PageMode /UseOutlines} + \pdfcatalog{/PageMode /UseOutlines /PageLayout /TwoPageRight} Sounds good, will install shortly, thanks Reinhard. karl

Re: facing pages in PDF browsers

texinfo.cnf (Node "Preparing for TeX" in the manual, which I see is missing a few words, including "configuration". Fixing ...) k

Re: facing pages in PDF browsers

Reinhard, Finally getting back to your proposed texinfo.tex change. this change some browsers display two pages by default though they didn't in the past, I rather suspect people will be very unhappy about that. I know I would be, if my PDF reader happened to care about it. the pa

Re: HTML output buglets

Hi Tom, From http://www.w3.org/TR/html401/types.html#h-6.12: Prev Refers to the previous document in an ordered series of documents. Some user agents also support the synonym "Previous". I think this means that "prev" is the preferred form. I agree. Patrice?

Re: facing pages in PDF browsers

from what you say I deduce that you don't use Adobe Reader, That is true. Not in many years. Nevertheless, I'm afraid your logic escapes me. As far as I can see, your description is that AR currently starts in one-page mode on Texinfo documents, and with the change it will start in two-pag

Re: Please type a command or say `\end'

This error message doesn't say enough. It's hardwired in the binary. There's no (realistic) way to change it. What's the problem? It got to the end of the input and did not see an \end (plain TeX) command. That's @bye in the Texinfo world ... k

Re: @enumerate does not support start numbers ≥ 10

- if (!defined($arg->{'text'}) or $arg->{'text'} !~ /^[[:alnum:]]$/) { + if (!defined($arg->{'text'}) or ($arg->{'text'} !~ /^[[:alnum:]]$/ and + $arg->{'text'} !~ /^[0-9]+$/)) { Thanks, but it appears to be insufficient. For me, running the patched ma

Re: texinfo-4.13a 53 of 53 tests failed

Hi Dennis, looks like the testsuite has a strange dependency on Linux coreutils 1) For the record, it's GNU coreutils, there is no "Linux" coreutils. because the syntax to a simple "cp" is wrong. 2) The syntax is wrong because (it seems) mktemp is missing on your system, hence there i

Re: texinfo-4.13a 53 of 53 tests failed

Well, I guess I am at a loss what to do here. Simplest: since the test failures are completely spurious, just ignore them and install the software. Another possibility: Install Texinfo 5.1 instead of 4.13a. The most time-consuming: if you insist on making the tests work in 4.13a, create a tr

[bug #39547] "info gcc" shows gccgo manual

Update of bug #39547 (project texinfo): Open/Closed:Open => Closed Status:None => Invalid ___ Reply to this item at:

Re: rule for period and sentence ending

The current rule for sentence ending is: Sure, it's arguable, but I don't want to change it, partly because I think Knuth made the right decision, partly because there's no way to do things at the "word" level in TeX, and partly because it would introduce a significant incompatibility in Texin

Re: rule for period and sentence ending

However @. is a bit buggy for PDF output: it seems that kerning is lost. For instance, compare the space between the P and the period with: @emph{OP}. Bar @emph{OP}@. Bar Thanks for the report. I'll see if I can fix it. Best, Karl

Re: rule for period and sentence ending

@emph{OP}. Bar @emph{OP}@. Bar I updated texinfo.tex on ftp.gnu.org with this fix. Thanks. (Oops, the % after \comma isn't needed. Later.) k --- texinfo.tex (revision 5274) +++ texinfo.tex (working copy) @@ -3,7 +3,7 @@ % Load plain if necessary, i.e., if running under initex. \ex

Re: Warn about invalid node names

Hi Glenn, Surely these people can live with the warnings, or use --no-warn? No, people absolutely hate warnings, and absolutely hate using --no-warn. I don't think users would be at all happy if their documents that have always run through perfectly well started spewing zillions of (in their

  1   2   3   4   5   6   7   8   9   10   >