Hi John,<br><br><div class="gmail_quote">On Sun, Nov 7, 2010 at 2:37 PM, John Coppens <span dir="ltr"><<a href="mailto:john@jcoppens.com">john@jcoppens.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
On Sun, 7 Nov 2010 21:06:33 +0100<br>
Mike Massonnet <<a href="mailto:mmassonnet@gmail.com">mmassonnet@gmail.com</a>> wrote:<br>
<br>
> Hi John,<br>
<div class="im">><br>
><br>
> gnome-doc-tool html -c index.css index.page<br>
><br>
> This will use the external CSS file index.css. In order to create an<br>
> initial CSS file run the command<br>
><br>
> gnome-doc-tool css<br>
><br>
> However if you don't wish to use an external CSS, you can drop the "-c<br>
> css" parameter and CSS will be included inside the HTML file.<br>
<br>
</div>Thanks Mike!<br>
<br>
I haven't seen this info on the mallard pages!<br>
<br>
I tried this, and found that it generates an index.html file, and cache<br>
file. Could you indicate what the intended 'workflow' would be?<br>
<br>
- have the .page files local, and upload only the html files to the site<br>
or<br>
- have the .page uploaded, and some mechanism to run gnome-doc-tool<br>
there every time some html is requested or when new .page files are<br>
uploaded (not very nice...)<br>
<br>
Thanks,<br>
<font color="#888888">John<br>
</font><div><div></div><div class="h5"><br><br></div></div></blockquote><div><br>You'd probably want to just upload the html files to the site. <br><br>Of course, each time you update your .page files, you would want to push up new static versions of the HTML.<br>
<br>Mike has provided a very good overview of how to build the html files, though.<br><br>Jim<br></div></div>