Mailing-List: contact dev-help@forrest.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@forrest.apache.org
Received-SPF: neutral (asf.osuosl.org: local policy)
Message-ID: <43765DAC.7060109@apache.org>
Date: Sat, 12 Nov 2005 21:25:00 +0000
From: Ross Gardler <rgardler@apache.org>
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
MIME-Version: 1.0
To: dev@forrest.apache.org
Subject: Re: docbook documentation splittet in several chunk
References: <87vez1i7ej.fsf@open-tk.de>
 <1131617640.8582.1.camel@localhost>	<87hdakiwjo.fsf@localhost.localdomain>
 <4373C4D8.7010902@apache.org>	<1131662665.4063.26.camel@k2.flat5>
 <87slu4ou0i.fsf@open-tk.de>	<437470BD.8050107@apache.org>
 <87hdajp65z.fsf@open-tk.de>	<1131723191.8276.13.camel@localhost>
 <4374C3FC.2000805@apache.org>	<87d5l7otiv.fsf@open-tk.de>
 <437504A2.2030904@apache.org>	<878xvupuz7.fsf@open-tk.de>
 <4375CDEC.2000104@apache.org> <871x1lpyg2.fsf@open-tk.de>
In-Reply-To: <871x1lpyg2.fsf@open-tk.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable

Fabian M=FCller wrote:
> Ross Gardler <rgardler@apache.org> writes:
>=20
>=20
>>>>But what is the *source* returned. This is only what your browser
>>>>tries to o when rendering.
>>>
>>>The source contains one line:
>>><?xml version=3D"1.0" encoding=3D"ISO-8859-1"?>
>>>There is nothing more.
>>
>>No wonder it doesn't work then. You need a stylesheet that actually
>>outputs something for Forrest to work with. As Kevin pointed out this
>>stylesheet creates multiple files, they are, most likely written to
>>disk.

=2E..

> But would it help, if the stylesheet would not write files to the disk
> but outputs the data for further processing by Forrest?

Yes, because then Forrest has something to process.

> Then it would be Forrest's task to save the several files and I guess
> that it would be Forrest's task to choose a name for each of the files
> as well.

No. It would not save the files. It generates them on demand.=20
(internally there is a cache which does get written to disk but that is=20
not a premanent store).

> As I wrote my initial post I thought that there must be a simple
> solution for this question like "write this and this and it works"
> because I thought that it is a frequently used and requested
> feature. But know I guess that my assumption was wrong. What do you
> think? Isn't that what I want to do a quite basic wish for a lot of
> users?

No it is not a common use case, but you are right in that I am sure=20
there are other users with this same need.

Chunking has been used before within Forrest. For example, see my old=20
lecture slides (this was done with Forrest 0.5 many years ago):

Single page:

http://www.gardler.org/teaching/courses/databaseSystems/xml/databases.htm=
l

Slides (i.e. chunked, note the next button in the top left):

http://www.gardler.org/teaching/courses/databaseSystems/xml/slide/number1=
/databases.html

Another example of chunking can be seen in the photo gallery plugin.

If you are willing to work at it we could advise on how to get a=20
chunking plugin together. The biggest hurdle is deciding how to chunk=20
the documents, i.e. at what point they should be split. However, this=20
would have to be done with our internal XDoc format otherwise it will be =

of no use to other Forrest users. So our first problem is getting your=20
Docbook source into XDoc.

Have you tride using the simplified-docbook plugin for it?

Ross