bug-texinfo
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: wrong-type-argument


From: Bruce Korb
Subject: Re: wrong-type-argument
Date: Mon, 01 Oct 2001 02:56:06 -0700

Eli Zaretskii wrote:
> 
> If I misunderstand the problem, please post a short Texinfo fragment
> and the output generated by makeinfo from that fragment, and point out
> which parts you think are generated incorrectly.

It is probably my misunderstanding that is causing a misexplanation
of the problem, but I am certain that there are some problems.
You can see a rendering of an earlier, but similar, output here:

  http://AutoGen.sourceforge.net/doc/autogen_7.html#SEC165

= = = = = = =  SOURCE FRAGMENT  = = = = = = =
@ifhtml
<TABLE>
....
</TABLE>

[1] See the lengthy list of features @xref{Features}.


[2] There is a user-visible dependency iff the developer does a
dynamic link to the libopts.so library.  Developers are free
to either link statically or ship libopts.so with their product.
A Debian package would need only a dependency on the package
supplying libopts (libopts9, at present).

The Guile library is now generally pre-installed on all
GNU/Linux systems.


  -- James R. Van Zandt
@end ifhtml
= = = = = = =  RESULT FRAGMENT  = = = = = = =
<TABLE>
....
</TABLE>

[1] See the lengthy list of features @xref{Features}.


[2] There is a user-visible dependency iff the developer does a
dynamic link to the libopts.so library.  Developers are free
to either link statically or ship libopts.so with their product.
A Debian package would need only a dependency on the package
supplying libopts (libopts9, at present).

The Guile library is now generally pre-installed on all
GNU/Linux systems.


  -- James R. Van Zandt
= = = = = = =  ANALYSIS  = = = = = = =
1.  "@xref{Features}" was not expanded
2.  <P>...</P> were not inserted
= = = = = = =  CONCLUSION  = = = = = = =
@ifhtml/@end ifhtml behaves exactly as you described
@html/@end html, i.e., there is no texinfo macro processing.


= = = = = = =  SOURCE FRAGMENT  = = = = = = =
  -- James R. Van Zandt
@iftex
@ifhtml

<P>The following gibberish is for TeX processing <STRONG>ONLY</STRONG>.
Unfortunately, there is a bug in the texinfo pre-processor
and it seems to be emitting this stuff for HTML, too.  This
is wrong, but I cannot fix it.  Sorry.

<P><FONT SIZE=-6><!-- make it unreadable -->
@end ifhtml
@end iftex
@ifnothtml
@center Comparative Analysis Table
@multitable @columnfractions .26 .11 .11 .11 .11 .11 .11
@item Feature \ Package #
@tab 1
@tab 2
@tab 3
@tab 4
@tab 5
@tab 6
= = = = = = =  RESULT FRAGMENT  = = = = = = =
  -- James R. Van Zandt

<P>The following gibberish is for TeX processing <STRONG>ONLY</STRONG>.
Unfortunately, there is a bug in the texinfo pre-processor
and it seems to be emitting this stuff for HTML, too.  This
is wrong, but I cannot fix it.  Sorry.

<P><FONT SIZE=-6><!-- make it unreadable -->
<P>
@ifnothtml
Comparative Analysis Table
@multitable @columnfractions .26 .11 .11 .11 .11 .11 .11
<LI>Feature \ Package #

@tab 1
@tab 2
@tab 3
@tab 4
@tab 5
@tab 6
= = = = = = =  ANALYSIS  = = = = = = =
1.  Despite the fact I am producing HTML output, the text between
    @iftex and @end iftex _was_ processed.  This is completely 
    contrary to the documentation and intuitive behavior.
2.  The "@ifnothtml" macro is passed through to the output HTML.
3.  The HTML produced for "@multitable" is bogus and should generate
    a warning until it can be fixed.  Perhaps suppress the HTML
    output, too.  What is produced is worthless.
= = = = = = =  CONCLUSION  = = = = = = =
1.  The @ifxxx stuff needs work for HTML
2.  @multitable needs work for HTML



reply via email to

[Prev in Thread] Current Thread [Next in Thread]