() k...@freefriends.org (Karl Berry)
() Wed, 12 Sep 2012 22:01:34 GMT
Breaking @cartouche over pages is TeXnically possible. So is
supporting background colors for @example / @verbatim. It's just
that I personally am never going to work on either one -- way too
much effort for way
On Thu, Sep 13, 2012 at 10:40:31AM +0200, Thien-Thi Nguyen wrote:
() k...@freefriends.org (Karl Berry)
() Wed, 12 Sep 2012 22:01:34 GMT
Another approach is to define a syntax to associate key/value pairs w/
any particular environment. This could map to ‘class’ attributes for
HTML output,
With respect, Masters:
I would like to comment on Mr. Nguyen's remarks. (Bear with me a moment.)
I have produced a handful of in-depth manuals at my job (I'm an Oracle/UNIX
administrator for a large hospital network) -- a few using Texinfo, a few
with DocBook. Over the past 12-18 months I have
() Jason Massey janixs...@gmail.com
() Thu, 13 Sep 2012 09:48:58 -0400
[the horror the horror]
Yeah, XML is suboptimal. SXML is slightly better, but still rotten.
*So, I guess what I am saying is that I hope that Texinfo does not
meander into XML-verbosity.* Actually, I'm begging that
On Thu, Sep 13, 2012 at 08:07:47PM +0200, Thien-Thi Nguyen wrote:
The sooner makeinfo supports uniform pass-through specification, the
sooner it can remove itself from the style-wishlist treadmill.
Aren't the @inlineraw, and @html... commands enough to pass-through
whatever you want?
--
Pat
The sooner makeinfo supports uniform pass-through specification, the
sooner it can remove itself from the style-wishlist treadmill.
Texinfo has never been on that treadmill and never will be, because it
is not and never will be a goal to support output in any conceivable
