[Rest2web-develop] Question about 'build' in restindex
Brought to you by:
mjfoord
|
From: Eur I. C. G. <cl...@is...> - 2007-03-23 10:17:31
|
I need some clarification of what 'build:' in the restindex does.
I can understand that when it's set to 'yes' then the file in which
the 'build: yes' is will be processed (using docutils) to create an
HTML version. By default, thus, a file abcd.txt will be processed to
create a file abcd.html.
However I'm not clear what happens with 'build: no'. If the file
abcd.txt has a restindex with 'build: no' does anything happen at all?
In the documentation it says "allows you to specify that a file is not
to be built, but should be included in the index." So, this
apparently means that the index for the directory where the file
abcd.txt is will have a reference to 'abcd', but we haven't built
abcd. Is this just so that if I want to include a pre-existing
abcd.html file I can create a corresponding abcd.txt with 'build: no'?
Going on from this I'm trying to understand what restindex.txt does
for me. I can see that it would be useful to combine (say) the
abcd.txt, defg.txt and hijk.txt files that I would otherwise need to
create to add pre-existing abcd.html, defg.html and hijk.html files to
a rest2web index, is this what restindex.txt is for? If so how can it
refer to multiple targets? Does one do it as follows:-
restindex
target: abcd.html
/restindex
restindex
target: defg.html
/restindex
restindex
target: hijk.html
/restindex
--
Chris Green
|