On Mon, Jun 18, 2001 at 02:49:53PM +0100, Andy Wardley wrote:
> On Mon, Jun 18, 2001 at 08:46:49AM -0400, Richard Chen wrote:
> > The html version of the installed manual page such as
> > http://localhost/tt2/docs/Manual/Intro.html
> > do not preserve literal [% ... %] constructs.
> > For example, instead of the correct illustration line like
> >
> > Dear [% tt_start_tag %] name [% tt_end_tag %],
> >
> > it shows the line
> > Dear name,
>
> I'm confused. I've checked the docs in the latest version (2.03)
> and they do seem to generate the correct code.
>
> For example:
>
> http://www.tt2.org/docs/default/Manual/Intro.html
>
> where the output is correctly generated as:
>
> <pre>Dear <b>[% name %]</b>,</pre>
>
> from the template (in my case) /usr/local/tt2/docs/src/Manual/Intro.html
>
> <pre>Dear [% tt_start_tag %] name [% tt_end_tag %],</pre>
>
> > This makes these web version of the manual pages very confusing.
>
> Are you sure you're reading the generated output and not the source?
> Or do you have the generated HTML output overwriting the source templates?
>
I found the problem. The make install completed with error messages like
Include Path: [ /home/richard/tpc4/examples/lib, /usr/local/tt2/examples/lib,
/usr/local/tt2/templates ]
Ignore: [ \b(CVS|RCS)\b ]
Copy: [ \.gif$ ]
Accept: [ * ]
+ splash/menu.html
! examples error - library is not defined
+ splash/panel.html
which I have ignored. It is the inclusion of the sample directory
/home/richard/tpc4/examples/lib which caused the problems. Once
this directory is removed, the install finished without problems
and the documentation looks great.
The reason I did not pay attention to the install error messages
was that I had also seen error messages coming from t/dbi.t tests
against an oracle database. But I knew those errors are harmless because
they are due to
1. usage of char(nnn) instead of varchar(nnn)
(this leads to mismatch due the padding of blanks)
2. use lowercase field names when only uppercase names are returned
I am not that familiar with tt2 yet to offer sound suggestions
for fixing the tests failures because they must be portable across
different databases. But definitely the current dbi.t tests
will not work well for oracle database.
Thanks for your help Andy.
Richard
