Hi Team,

I installed the new doc build system in the 2.1 cvs.
Unfortunately, there are more problems to solve than
bearable for integrating it into 2.0 right now, I
think.

Most problems arise with the use of Batik to generate
the images:
- Sometimes the build process just hangs
- Sometimes out of memory exceptions occur
Next problem is that batik resolves resources
relative to the current directory. For building
the docs using ant this is no problem as we
can set the current directory when cocoon is started.
But when cocoon is running, you don't know the
current directory and therefore the images
for the navigation are not rendered correctly.

We could solve all this problems if we remove
the dependence to batik, and use text instead of
images for the navigation. In fact, this should
everything make working fine - and much faster.

The printer-docs currently use the same stylesheets
than the normal docs use. If anyone volunteers
for changing them, I would be very happy!

I don't want to integrate the doc system into 2.0
before these problems are solved.

Carsten

> -----Ursprüngliche Nachricht-----
> Von: Carsten Ziegeler [mailto:[EMAIL PROTECTED]]
> Gesendet: Donnerstag, 4. Oktober 2001 10:20
> An: Cocoon-Dev@Xml. Apache. Org
> Betreff: New doc build system
>
>
> Hi Team,
>
> I think we have a first workable version of the new
> documentation build system with - of course - Cocoon
> as the engine.
>
> Currently this is checked-in as an addition to the
> 2.1 cvs.
>
> If noone objects I want to replace the old system
> in both cvs tomorrow. This step would include
> removing the then obsolete xdocs directory, add
> the documentation directory and fix all build
> targets.
>
> Carsten
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, email: [EMAIL PROTECTED]
>


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

Reply via email to