Andreas Gaumann wrote:
>
> there is a variable in .latex2html-init called $NAV_BORDER. But it takes
> no effect. I try to set it to 0 but there are still borders.
It has to be set as: $NAV_BORDER = '0';
to get the character digit '0' rather than the number 0.
But in your case even that is not enough,
for you are not using the standard icons.
Look inside latex2html.config .
The Navigation panel uses the subroutine &img_tag
which has a pattern to match the standard names, using $alt .
Further down in sub img_tag , the icon's name is tested for a match
with $alt . If it matches, $NAV_BORDER is used, otherwise
the border attribute is set to be BORDER="1" .
The code for &img_tag is not very sophisticated, and doesn't include
lots of different tests that could be applicable to formatting the
placement of the icons in the navigation panel.
This is for a very good reason:
it is meant to be totally clear as to what it does, so that it is easy
to change when you don't like the standard nav-panel.
However the more complicated you want the changes to be,
the more you need to know about Perl to get it right.
Furthermore, this code is in latex2html.config (rather than in the
main latex2html script) so that it is easy to find, for use as
a model to be customised.
Go for it! ;-)
> Another problem are two dots in the table of contents. On the one hand
> it seems that the title page is handled as two extra levels and the
> whole document (and it�s structure) is a sub part of these two levels
> (of the titlepage). But on the other hand theres no descriptional text
> on the right side of the dots. Is this a bug?
Yes, and No.
Strict LaTeX style is that you should not use \subsubsection
except within a \subsection, within a \section.
Similarly \paragraph ought to be inside a \subsubsection; etc.
If you violate this style, and ask for numbering to be shown,
you get things like:
0.0.1
2.0.0.1 etc.
In LaTeX2HTML, there is an analogous effect for the
formatting of the nested lists within a mini-toc.
Each of those extra levels ( the *two dots*, aas you called them)
corresponds to a preceding '0', where a sectioning-level has been skipped.
Previous versions of LaTeX2HTML did not show those levels;
but the HTML code was not correct --- tags were not properly nested.
Now the code is 100% valid, but you get the extra dots.
It is highly non-trivial to generate code that gives what you
want to see, and is 100% valid in all cases.
Think about how you want the mini-TOCs to look in following 2 cases:
\section{....}
\paragraph ...
\paragraph ...
\paragraph ...
% end of section
and
\section{...}
\paragraph ...
\subsection{...}
\subsubsection{...}
\paragraph ...
\paragraph ...
\subsubsection{...}
\paragraph ...
\paragraph ...
% end of section
> You can see this effect on my homepage,
> http://www.unix-ag.uni-siegen.de/~gaumann/node1.html
> and in the documents linked on
> http://www.unix-ag.uni-siegen.de/~gaumann/node8.html
I saw the problem on node1.html but not on node8.html .
Another consideration for the formatting of mini-TOCs
is the effect of the document-class.
E.g. {article} expects to find \section commands,
whereas {report} and {book} expect \chapter commands.
Since I cannot access your main.tex source file, I cannot see
what document-class you are using, to give better advice on
how to tackle the problem from this angle.
> And my third problem is that Latex2HTML hangs when I compile a document
> that includes the natbib package. I use the \citep, the \citet and the
> changed \bibitem command of this package. When translating the document,
> the pages are passed, the images are created and then Latex2HTML hangs
> while "doing section links". (Doing nothing, but load is still up.)
> $VERBOSITY = 4; says "*** replace markers ***" several times with a lot
> of numbers between. (In that document are no formulas, some image.)
>
> I�ve pressed Ctrl+C and get an segmentation fault. The output of this
> available at
> http://www.unix-ag.uni-siegen.de/~gaumann/neugier/neugier.html
> (The first pages are relativly ok, but then (on node8.html and
> node9.html) it gets completely broken. If you watch this, perhaps take a
> look at node10.html and node12.html). The TeX source of the text is at
> http://www.unix-ag.uni-siegen.de/~gaumann/neugier/tex/neugier.tex
OK, thanks for making it available.
I'll have a look, to see if I can track down what is causing the problem.
> Any suggestions to these problems?
> --
> Andreas Gaumann <[EMAIL PROTECTED]>
>
> http://www.unix-ag.uni-siegen.de/~gaumann/
> student at the University of Siegen
>
Hope this helps,
Ross Moore
