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
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 -
@@
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
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
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,
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 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
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?
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]
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
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
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.
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
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
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,
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
201 - 224 of 224 matches
Mail list logo
