- 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 Top". I'm not
sure what more you want it to do -- isn't that error message clear that
the dir file could not be parsed? I can't imagine any rational way to
detect "corruption" per se. If you compile a corrupted C source file,
the compiler is going to give a parse error, not say "file
corrupted".(*)
- install-info was called on a corrupted file, but succeeded[2].
I am guessing this is relevant to the Debian install-info, not the
Texinfo install-info. If it is really the Texinfo install-info, then I
again need the dir file, plus the install-info invocation, plus
(perhaps) the info files involved.
Thanks,
k
(*) Actually, gcc gives a warning that null character(s) were ignored.
C doesn't allow nulls. But I can't arbitrarily ignore null characters
in Info, they're actually used as a marker. Putting in a special case
to look for a bunch of nulls in a row could be done, but it seems
somehow wrong. Given that there's already an error message being
reported, it's not clear to me that it's worth it.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
