Hi Norbert,
I hope life after release of TL2005 has settled down a bit
Well, just redirected into other areas :(.
Interstingly, the files state something a bit different:
A license statement clearly taken from tex.web, so I'm glad it is not
considered nonfree :).
we (actually
Dear Dr. Shinsaku,
I'm one of the people developing the TeX Live software distribution for
the TeX user groups. The Debian project recently asked me about XyMTeX,
which we do currently include in TeX Live, based on your license
statement being analogous to that of Knuth's for TeX itself.
But
Regretfully, Dr. Shinsaku unambiguously replied to me that he wishes to
restrict XyMTeX distribution. So I'll be taking it out of TeX Live for
next year.
Date: Thu, 01 Dec 2005 09:16:29 +0900
From: Fujita Shinsaku [EMAIL PROTECTED]
To: [EMAIL PROTECTED] (Karl Berry)
Subject: Re: XyMTeX licensing
Hi Loic,
+ * Fix segfault when resizing the terminal rapidly by checking more
carefully
+whether the display line is set prior to refering to it.
+[info/display.c:display_update_one_window]
Thanks for sending in this change (and thanks, Norbert, for passing it
on, since
Here is another bug report, this time about segfaults. It contains
extensive backtraces and a small patch.
Thanks. I haven't heard about this one before. If you can't reproduce
it, I doubt I can either, but the patch sounds fine in any case, even if
it doesn't 100% solve it.
Anyway,
0600? 0666 might lead to an information leak.
Thanks, changed.
This comment is outdated after the patch.
Right. I fixed that comment and a couple other minor things when I applied.
Thanks,
Karl
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble?
Hi Norbert,
Maybe this email got lost somewhere, so
Sorry, I've been away.
Since the file COPYING is not shipped by Debian, I could not check
there.
Of course the COPYING file in Texinfo is just the GPL, as it is in
virtually every (original) GNU distribution. Changing every
That sound fine for me. But also if you issue:
info --version
Oh. My mistake. help2man just includes the output of --version, I
forgot that.
Also here the version 2 or (at your option) any later version is
missing. Thats what caused me to open this bug: both the man page
Hi Helge,
Then this topic should be discussed in an appropriate form at some
I know of no appropriate forum, but I'll ask rms at some point about
changing and standardizing the wording of --version output for GNU
packages.
Best,
karl
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a
since there is never the guarantee
Guarantees aren't necessary, in my mind. With context, there is
probably no way to guarantee that anyone can ever get exactly the same
result as you unless they come over to your office and duplicate your
disks :). (Probably not even that would be
IMHO this is not enough for removal neither from TeX Live upsream nor
Debian.
I don't plan to remove the wsuipa fonts without some actual confirmation
that they are nonfree. Until then, I assume it is carelessness, as in
so many other cases.
I guess I'll write Pierre MacKay (UW
Do you have a good suggestion how to fix that?
Just have to forcibly remove leading whitespace from `line', I guess.
I'll look into it.
At least Debian i-i which will still be around
for some time, but we are working hard on it!)
I hope you are aware that Ben Asselstine has
On CTAN, there's the dtx and ins file and a pbox.pdf, which seems to
I updated pbox in TL; now pbox.pdf is included.
Thanks,
karl
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
How should we proceed now? Move ucs from texlive-latex-recommended to
texlive-latex-extra to narrow the user base of that package?
I think that would be a good idea, but it should first be done in the
upstream collections. What do others think?
I moved ucs from
INFO-DIR-SECTION GNU Gettext Utilities
START-INFO-DIR-ENTRY
This is gettext.info, produced by makeinfo version 4.11 from gettext.texi.
It's a (quite unfortunate) bug, and I think I've fixed it for the next
Texinfo release.
karl
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
patgen can only read files containing ONLY \patterns{...}
I updated the man page to try to describe this better (among other
things). See attached.
Thanks,
k
patgen.man
Description: Binary data
should we start NOW a repackaging effort as Frank pointed out
some time ago,
I don't have the energy, myself. The whole infrastructure
reimplementation seems like more than enough to tackle for one year ...
karl
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a
tmmath, hvmath? Should we do the same there?
Indeed. I've removed tmmath and hvmath from TL. Thanks.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
With 4.11 PLUS your patch from the above it is still happening,
Ah, the case before had a @dircategory. I didn't try without.
(I surmise that's the difference, anyway.)
- insert_string (START-INFO-DIR-ENTRY\n);
+ add_word (START-INFO-DIR-ENTRY\n);
I installed it. Thanks
@direntry
* ZSH: (zsh). The Z Shell Manual.
@end direntry
I made the change below to work around this buggy input. Hope it
doesn't cause undue distress. Meanwhile, how about patching the zsh
manual, or at least reporting the problem to them, if zsh is still
Maybe the better fix would be renaming all the nodes in coreutils.texi to
comply with this convention?
I think the node names should stay as they are. The convention is
either Invoking xxx or xxx invocation.
http://www.gnu.org/prep/standards/html_node/Manual-Structure-Details.html
I
jimm info simply displays the first node it finds with a name matching
jimm pr. In my case, it is currently the PreScript node of a2ps.info.
What? That makes no sense to me at all. Info doesn't look inside every
info file randomly looking for nodes to match. It has to be in a dir
mstone The debian install-info routine (IIRC) predates the
gnu install-info,
That wasn't my understanding, but I never actually researched it. I was
not aware of any Debian ii at the time that rms wrote GNU ii (I was
maintaining Texinfo by then -- 1996), but then, I probably wouldn't
patgen can only read files containing ONLY \patterns{...}
As opposed to what? I wouldn't expect patgen to parse .tex files.
As far as I can tell from a quick glance at patgen.web, it reads a
hyph-en-ated word list and (optionally) existing patterns (and an
auxiliary translate file), and
I have to change the file to:
I agree the documentation should be improved. I don't think it's worth
hacking the program to try to somehow parse out the patterns.
karl
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
The version of latexmp included with texlive-metapost, version 1.1.0,
I updated latexmp in the source repo. I also wrote the author about
releasing the source to the doc.
Thanks,
k
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL
Thank you very much - his address is still the one above?
That is where I wrote, yes. No answer yet.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
/usr/share/doc/texlive-fonts-extra/latex/cmastro/cmastro10.300pk
They are gone.
$ mktexpk cmastro10.300pk
mktexpk: don't know how to create bitmap font for cmastro10.300pk.
mktexpk isn't that smart. You have to say
mktexpk cmastro10
and ask for the resolution with cmdline
it is not clear where they get their advice from.
Sebastian decided as best he could, many years ago. Very little has
changed in the set of recommended TL packages for a long time now.
Anyway, the main point here is not the classification of ucs, but rather
the possible bug in it. I see
Wouldn't it be the case for having the support files for non-free fonts
As far as I know, the Lucida metrics are not included in TeX Live 2007.
Frank or anyone, if there's an issue for TL here, please explain.
Karl
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of
documentation is there, in collection-fontsrecommended (as part of
psnfssx).
Oh yeah. The place to fix this is psnfssx; I'd prefer to have the
Lucida styles/docs removed too, but it doesn't make sense for TL to do
something different than CTAN here. I haven't yet written the
maintainers
TEXEDIT = ${EDITOR:-vi} +%d %s
work and respect the EDITOR environment variable?
Well, texmfmp.c ends up calling system(3) on the string, so it would
seem so, but when I actually tried it, it didn't seem to work. I dunno.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of
Regarding filenames containing spaces and the TEXEDIT et al. values:
1) is there any reason not to change the compile-time default in
web2c/c-auto.in? If you want to add the definitions in the Debian
texmf.cnf, that's fine, of course, but I don't see why the default
shouldn't change
Unless the OS ending with `$' - err, `s' likes better, I prefer ''.
I committed the change using '%s'.
Akira, please let me know if that causes problems for you and %s would
be better.
Thanks,
karl
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble?
+#ifdef WIN32
+#define EDITOR emacs +%d \%s\
+#else
#define EDITOR vi +%d '%s'
+#endif
Thanks, I installed that change.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Regarding the license README etc. for fpl, I've updated the fpl package
in TeX Live from what is on CTAN now. Let me know if you spot any
problems.
Utopia is another matter, I'll write about that separately (later).
Thanks,
Karl
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of
Regarding the license info for utopia, I added the {README,LICENSE}*.txt
files to TL, in texmf-dist/doc/fonts/utopia.
One thing I'm wondering about is where the tfm/vf's on CTAN came from.
Does anyone know if there are fontinst sources floating around
somewhere? Or something? When I created the
CTAN:/fonts/psfonts/psnfss-source/utopia/
Thanks.
How is that solved for other map files in psnfss (chrter.map,
fpls.map, pazo.map)?
All of those map files are in psnfss too.
Oh well, I'm not going to pursue it. Life is too short.
Best,
Karl
--
To UNSUBSCRIBE, email to [EMAIL
Yes - this should probably be fixed by including
CTAN://fonts/psfonts/bh/lucida/doc/fonts/lucida/readme.lucida:
I fixed it by removing all of the Lucida support files from TL instead.
Unlike some of the others, they are separate on CTAN and part of psnfssx
rather than psnfss, so it was
Do you have any idea how this could be fixed?
When I run the current texi2dvi in a directory named `x~', I do not get
an error in the default (local) --build mode, as Christian (hi
Christian) is apparently invoking it. So maybe try the current source
from CVS, to see if that works now?
It
Could you or anyone else please take a look at this, give your comments
(please leave the Cc on list, especially the Debian bug report).
Well, it is certainly a good thing to avoid the fixed-length buffer.
I applied the patch, modulo error message wording.
Thanks!
Karl
--
To
TEXMFSYSVAR is not in SYSTEXMF. Does anybody know why this is so?
I don't recall an explicit decision being made.
Is there any reason not to include TEXMFSYSVAR in the future?
Doing this makes sense to me, but I'd like to get Thomas E's opinion.
Thomas?
Thanks,
k
--
To UNSUBSCRIBE,
but collection-humanities does not require collection-latexextra. (In
fact, it does not require any collection, not even latexbase, but that
might be because some are generic macros.)
It would be ok for collection-humanities to require latexbase (I
assume that is collection-latex in
Where is bigfoot now?
collection-humanities
None of that is specific to humanities at all.
Happy to hear this. I moved it to collection-latexextra.
Thanks,
k
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
But please test the following change (I don't know whether it
is related to the problem).
I installed this change in TL, since it's obviously desirable,
independent of the present bug. (I gather it didn't help.)
More later, I hope.
Thanks,
k
--
To UNSUBSCRIBE, email to [EMAIL
Doesn't look straightforward to fix - any ideas?
We will probably reinstate the Catalogue in TL, and when we do, I guess
we should not just copy the files, but set up some kind of conversion
process. Ugh.
Does MiKTeX contain the Catalogue? If so, are the links properly
transformed? If so,
Foo. Bar.
Foo.
Bar.
I can agree it's a bug, but makeinfo has always simply copied
intraline spaces (Foo. Bar.) as-is, and I, at least, am not likely
to implement anything different in the foreseeable future, if ever.
makeinfo has no real understanding of text at all. I
since it is a one-time exercise,
I don't understand. Any massaging process will be rerun a zillion
times, since of course the Catalogue is being updated constantly. (Not
that I have any objection to Elisp myself.)
karl
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of
texlive location='footmisc'/
...
/entry
[the id is the name of the xml file (and hence the name of the converted
html file); the texlive location is the name of the tpm file.]
given that info, one could in principle match things up, presumably?
Yes, thanks. That
-dDEVICEWIDTHPOINTS=50 -dDEVICEHEIGHTPOINTS=50
Akira, does this sound like a good solution to you?
(It seems ok to me.)
I'm not sure whether we need even more 0s,
If I'm doing my arithmetic right, 500,000 points is more than 150
yards/meters. I find it hard to picture
So there are probably false positives, but what about abstract,
accents, acronym, aeguill?
I do not know of any attempt to ever sync texdoctk.dat between TL and
teTeX, so it is not surprising there are differences in every direction.
If you or anyone would like to maintain that file,
don't think it makes much sense to change it [in c-auto.in]
Why not?
Better include it in texmf.cnf, making it more visible.
Including every possible variable in texmf.cnf just for visibility
doesn't exactly seem desirable to me. Although I suppose it's pretty
close to that now!
Best,
This has been assigned CAN-2005-3011, please mention this number in
the changelog when you fix this to allow easy tracking.
Someone, please send me the actual bug report, and (hopefully) a fix.
Thanks,
karl
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe.
It increased its revision control version number from 1.3 to 1.11,
but there are no changes - have they all been reverted?
There were no changes to texindex.c. The $Id$ change isn't meaningful
-- it happened because of temporarily moving Texinfo to berlios (because
savannah was dead for
I've adapted the OpenBSD stuff and created a patch. Maybe
you want to look at it if this works.
Thanks for doing this.
In general, the OpenBSD code seems to be a couple versions back, as it
has KR function definitions and omits a couple other changes I made
(quite) a while ago.
I wonder
In fact the patch seems to be against texinfo-4.8, the last released
version of texinfo.
Well, the patch applies, but that's not what I was saying.
One question: For the upcoming texinfo-4.8 package in Debian, can I use
the patch of Henry, Karl?
It's up to you, but I don't
Can you please comment on my first try on this, attached.
That looks just fine. I'll apply it later today or tomorrow. Thanks
Norbert!
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Hi Hilmar,
% The default settings are not secure when you process LaTeX files of
% possibly doubtful origin. In this case, set openin_any = p.
I'm not too excited about putting such a vague and alarmist message into
texmf.cnf. I have no objection to putting in something more specific,
Well, the submitter spoke about some mal code sent to somebody, who
calls it and the LaTeX file does something really bad.
As far as I know, foreign files can't do anything *really* bad.
As distributed, TeX will only write files (via \openout) under
TEXMFOUTPUT (if set) or the current
are there any plans to enable dvips to include TrueType fonts in a
Postscript file, by wrapping them up as Type42 fonts?
I am not aware of anything along these lines. Tom?
If there is some TrueType+TeX volunteer interested in working on it,
patches would be welcome, I'm sure. I also
Please consider to drop dvipdfm in favor of dvipdfmx!
Funny thing. I asked the fmx maintainers the same thing, about
completely dropping fm in favor of fmx in TL, and they advised me not
to do so. fm had additional programs (ebb and something else), and
different behavior in some cases.
Hi Frank and all,
So can hbf2gf stay as a top directory?
Seems fine to me, FWIW. Did someone suggest otherwise?
Probably this is just a missing
feature of the TDS. What do others think?
Obviously the TDS cannot explicitly mention every program in the world,
that being an
The attached file gives an error
Stijn, I'm not sure if you ever found the resolution.
Using \loggingall on your source quickly shows there is, as Taco et
al. surmised, an infinite loop. The log file ends with this:
...
[EMAIL PROTECTED] ...nd \z@ [EMAIL PROTECTED]@@p \boldmath {{b^c}}
-l, --language=LANGspecify the LANG of FILE (LaTeX or Texinfo)
I changed it to use latex and texinfo.
there was no change in 4.12.
I never saw the bug report before. I'm sure there are many bugs (and
fixes) in all the distro tracking systems, but unfortunately I have
never
I intend to reintroduce crypt++el into Debian because I think we still
I haven't tracked it down yet, but on the face of it, crypt++ doesn't
work with Emacs 22. When I visit a .tar.gz file, it doesn't get
uncompressed. jka-compr.el warns that users have to take out all the
compression
+ VCSDIRS='\(\.svn\|\.git\|\.bzr\|\.hg\|_darcs\)'
(cd $TEXMFLS_R \ls -LRa 2/dev/null) \
- | sed -e '/^$/{n;s%^\./%%;s%^%./%;}; /^\.$/d; /^\.\.$/d; /^\.svn$/d;'
\
+ | sed -e '/^$/{n;s%^\./%%;s%^%./%;}; /^\.$/d; /^\.\.$/d;
/^'$VCSDIRS'$/d;' \
-e
So my patch additionally includes a replacement of those two
statements with ${var##pattern} and ${var%pattern} expansions. These
expansions are POSIX and should thus be reasonably portable.
Sorry, POSIX introduced many incompatible shell constructs (and command
line options,
Thanks for the report, but ...
However I also noticed use of echo+sed dirname replacement (with comment
can't rely on dirname -- basename was relied on on the next line
though),
Well, that's because basename can be relied on :).
which would have problems with spaces at the end
Hi Stefan,
So maybe we can just remove it from the binary distribution, but
keep the sources in the CVS so that people who use the script
can still download it?
Sounds good to me. So can you apply the patch below (or similar) to
your source for your next release? I checked it in to
kpsewhere acts very strangely here. It looks as if the whole concept of
kpsewhere flawed, maybe only in newer web2c/libkpathsea versions?
I've never understood/maintained/looked at kpsewhere.
This is what I get in native TL (development):
$ kpsewhere texmf.cnf
FIrst: What do you get when you make
man Top
No manual entry for Top.
And I assume that this returns the manpage for Top, which is here on my
system the same as man top.
Sounds right to me.
I'm just guessing, since I still can't reproduce this bug any more, but
how
Can somebody explain to me the reason for [KPSE_DOT]
I've forgotten, if I ever knew. Thomas?
I have a few observations, not especially related to the original report.
1) kpathsea/expand.c says (and implements):
/* If $KPSE_DOT is defined in the environment, prepend it to any relative
I think that the correct solution is to replace the final default else
with the conditional test:
} else if (elt[0] != 0) {
/* empty components can appear in TEXMFCNF; we skip over these */
Sounds reasonable to me. Thomas, Olaf?
Thanks Julian (and all).
karl
--
Someone did not like this /. and has removed it. Karl? Olaf? :-)
I don't remember doing so, although I may have in a fit of madness.
I can put it back.
I guess TETEXDIR is always specified as an absolute path? Or am I
missing something else?
Thanks,
Karl
--
To UNSUBSCRIBE, email to
Hi Norbert,
Subsubsection without subsection within a section are on the wrong level
Sorry, I can't get excited about this one. It seems a lot to ask for
the bookmarks to be correct when the document structuring is
incorrect. No doubt it could be fixed with enough time effort, and if
Hi Norbert,
In the testfile we have the following bookmarks:
appendix A: first appendix
A.1 first section of appendix
A.1.1 subsection
A.2 second section of appendix
A.3 third section of appendix.
Unfortunately the jumping of bookmarks is simple, but
WIth HTML 4.01 Transitional for texinfo.html I get only 4 errors.
Just out of curiousity, what are those four errors?
Thanks,
k
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
$ info/ginfo ./notexistingfile
and I landed at the manpage of top
What is wrong here???
Sorry, I can't explain it. I do get the No menu item error, with
precisely your invocation. Comes from line 2551 in session.c, I guess
Maybe it's related to the dir file contents somehow
http://www.gnu.org/software/texinfo/dtd/4.8/texinfo.dtd:2: parser error :
Comment not terminated
!-- $Id: texinfo.dtd,v 1.2 2006/01/31 00:45:48 karl E
Document Type Definition for Texinfo XML output (--xml).
Wow, XML does not allow comments including the string --? Pardon me
for
- a part of the file only is corrupted, but neither did info mention it
was corrupted, nor could it use the non-corrupted part, so I believe
there is an abort strategy in place[1], but it doesn't expose
failures,
You said that it reported the error, Could not find node
Line 6780 column 91: document type does not allow element SMALL here.
...ls(1)/a program small class=dots.../small
Line 8421 column 25: document type does not allow element PRE here;
Line 8424 column 24: document type does not allow element P here;
Line 9322 column 24:
Does your info also go to make_manpage_node and returns a if (node)
true?
It returns NULL -- because man top fails for me! (Long story.)
Ok, I will have to see if we can get the good error even when man pages
are properly installed :).
Thanks much for pushing this.
k
--
To
Does your info also go to make_manpage_node and returns a if (node)
true?
I take it back. I fixed my man setup but make_manpage_node still
returns zero. Not surprising, because it's being called with
pagename=./asdkiafdasdf, rather than top. So why is yours
asking for top's man page?
Did you compare the DIR files you have on your machines? Perhaps some
entry there references top, with the intent to get to the Top node...
There is no top in my dir file. I've never seen a top entry in a dir
file, actually.
But sure, it still could be that, or something else, about
Attached dir.gz
Was missing
I still get the error message instead of the top man page. Using
INFOPATH=~/tmp ./ginfo ./foobar
However, messing around with gdb, I surmise that the man page was being
generated by this code at the end of info_get_node:
/* If the node not found was Top,
+Be careful, as the paper size will stick to a predefined size if there
+is one close enough. To disable this behavior, use @samp{-tunknown}.
Thanks Vincent. I'll make that change in the doc (or some equivalent).
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of
- the current LPPL allows to change the internal identification as an
alternative to renaming the file, and
Indeed, this is the main difference between the Knuth license and the
current LPPL, as I know you know.
- it does not permit to distribute changed versions, even when
fmtutil sets and exports TEXINPUTS=$tmpdir:$TEXINPUTS, but that is not
sufficient. One has to set TEXFORMATS, too. I therefore suggest the
following patch, based on teTeX-3.0's version:
I don't see why not. Thomas?
Thanks,
k
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a
but what I did is the following:
Wow, thanks!!
I tested the attached patch against texinfo/makeinfo 4.8 and it worked,
Please say exactly how you tested it, ie, which environment variables
you set to what, what the makeinfo invocation was, what the input file
was. I have had a great
Maybe make info used a unpatched makeinfo?
Info output must not and does not translate Next: and so on, because
they are effectively keywords -- Info readers would stop working if they
were translated. Norbert's patch changed the HTML output, which is
fine.
--
To UNSUBSCRIBE, email to
Will this patch also be applied upstream?
Some variation thereof.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Hi Norbert,
Back on this from November ...
146133 and 151850 Matching vs. Searching
--
If you take a info file which is split into different files, and there
is a node containing a `.', jumping to this node does not work.
I
It seems that the generation of the info files, especially with the
jump indications at the end of the first file, are improperly
created. WOuldn't this explain the problem?
Yes, it might explain it, except that those jump indications are
correct, as far as I can tell.
That's why
Can you tell me in which function the scanning is performed, I can take
a look into the code.
Ugh, when I've looked at this stuff before, it seems to be spread all
over. Most of the relevant code is in nodes.c, I think, e.g.,
info_get_node.
(And maybe once I learn how to debug an
GNU. Free.Document.License
and boing, I cannot go the the node.
Ah!
Is it documented somewhere that node names *SHOULD NOT* contain .?
Yes, in the Texinfo manual.
If yes, we can also forget about this and close this bug, because info
is not used according to the
276000 Wrong page number in table of contents
I have just checked in this changed to texinfo.tex which I hope fixes
this one. (texinfo.tex is a lot easier to hack than info :)
Thanks,
Karl
--- texinfo.tex 8 Jan 2006 22:14:37 - 1.206
+++ texinfo.tex 27 Jan 2006 22:46:07 -
@@
What was the reason that node names cannot contain the sequence
. or .\t etc
??
The only thing I can think of is that it is somehow related to the dir
file, which contains entries like this, with a period followed by
whitespace:
* Bash: (bash). The GNU
Ok, it didn't apply to texinfo from 4.8, but:
Hardly surprising. You should distribute the latest released
texinfo.tex, available from ftp://tug.org/tex/texinfo.tex (or linked
from http://www.gnu.org/software/texinfo). Lots of fixes. texinfo.tex
is the one thing that I can update
So it is okay to include always the latest texinfo.tex together with
info and makeinfo etc from 4.8?
Yes.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Mp... brings you *ALSO*! to the top of the appendix page,
although it is actually on the next page
(this could be related to the error 276000 see below???)
Happily, it seems your surmise was correct: this bug is not happening
for me now, so I suppose that it was
1 - 100 of 220 matches
Mail list logo
