>>>>> "RM" == Ross Moore <[EMAIL PROTECTED]> writes:

RM> It is up to the browser to choose how to render:
RM>
RM> <TABLE> <CAPTION><STRONG>Table:</STRONG> A long caption that is
RM> much wider than the table.</CAPTION> <TR>...
RM>
RM> For a {tabular} environment, it make no sense to use other than
RM> this straight-forward markup.

I see.

RM> With a {minipage} the game changes, for the {minipage} itself
RM> generates a <TABLE> tag, while the {tabular} inside it uses its
RM> own separate <TABLE> tag.  In your example the caption is
RM> associated to the {minipage} rather than to the {tabular}.
RM>
RM> Now (in LaTeX) you can pass width information for the {minipage}.
RM>
RM> In current versions of LaTeX2HTML the width is ignored, but I've
RM> just now implemented it so that the width is read and expanded by
RM> the $MATH_SCALE_FACTOR (since this corresponds to the desired
RM> font-scaling between on-paper and on-screen).
RM>
RM> However one can also request different widths as follows:
RM>
RM> \begin{htmlonly}
RM>  \begin{minipage}{3in}
RM> \end{htmlonly}
RM> %\begin{latexonly}
     ^
    omit this

RM>  \begin{minipage}{1.75in}
RM> %end{minipage}

That doesn't seem to change anything, at least with Netscape 4.05.

RM> Certainly it's possible.  The problem is to deduce sensible widths
RM> to use with the <TABLE> tags, given that you cannot know what size
RM> fonts the reader will be using.

Understood.

RM> Setting a value for WIDTH=...  is a dubious strategy from this
RM> point of view. But *not* setting a value causes the caption to be
RM> wrapped with the width of the contents --- this may not be wide
RM> enough.

Right.

RM> This is one that has been at the back of my mind for awhile.  It
RM> had not been clear (and still isn't 100% obvious) what is the best
RM> way to use the length information of a {minipage}.
RM>
RM> So when v98.1p6 comes out (real soon), you'll be able to test
RM> whether or not you like how I've now implemented this situation.

OK, I look forward to trying it out.

>> 1. Create a file called CvsC++.tex containing, e.g.:
>> ....  Doing section links ...../^CvsC++\./: nested *?+ in regexp at
>> /users/turner/Tools/latex2html/latex2html line 935.
RM>
RM> Fixing this is a 1-liner:
RM>
RM>     $STYLESHEET = '' if ($STYLESHEET =~ /\Q^$FILE/);
RM>                                          ^^______insert this

Great.  Thanks...

-John

Reply via email to