Date: Mon, 10 Jul 2000 09:34:06 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Richard Dawe <rich AT phekda DOT freeserve DOT co DOT uk>
cc: DJGPP workers <djgpp-workers AT delorie DOT com>
Subject: Re: mkdoc patch, take 2
In-Reply-To: <396792CB.85E1BCDE@phekda.freeserve.co.uk>
Message-ID: <Pine.SUN.3.91.1000710093330.5255B-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Sat, 8 Jul 2000, Richard Dawe wrote:

> 1. When producing @multitable in texinfo, is there an easy way to make a
> column consume the rest of the table? The problem here is that we have a
> 2-column table. The left-hand column's width can be calculated easily, but
> the right column should use the remaining space. I have a hack based on an
> assumption of 80-columns width.

I guess I don't understand what does ``the rest of the table'' mean in
the first sentence above.

Is the problem that you don't know the actual line length produced by
`makeinfo'?  If so, then that can be controlled by the --fill-column
option to `makeinfo'; the default is 72.  TeX and HTML output is
another matter, however.

> 2. With the default qualifiers for the ansi target, C89 compatibility is
> set to yes, but C99 is set to unknown. Should the unknown part be
> displayed in the portability?

Why should C99 default to unknown?  Why not to yes?

In any case, I agree that displaying ``unknown'' is not a good idea.

> 2. Make @port-note be a multi-line @ command

Yes, please.

> @port-note ansi
> This
> uses
> four
> lines.
> @end port-note
> 
> or:
> 
> @port-note ansi {This uses one line.}

The first possibility is IMHO better: it doesn't violate Texinfo's
rule that lone unescaped braces are not allowed.