Juan Jose Pablos wrote:
On Tue, 2005-05-17 at 12:06 +0200, Ferdinand Soethe wrote:
Looking at the details, I keep wondering if it wouldn't save us much
work to get rid of x-docs and fix FOR-470 in one step.
In order to get rid of x-docs, we need to create the stylesheet for
xdocs --> xhtml so, I
I've started looking into FOR-470.
Looking at the details, I keep wondering if it wouldn't save us much
work to get rid of x-docs and fix FOR-470 in one step.
If we don't I'd change all the wording for raw-files to 'xdocs' now just to
change all of them to 'content' for the next release.
So if
> On Tue, 2005-05-17 at 12:06 +0200, Ferdinand Soethe wrote:
>Looking at the details, I keep wondering if it wouldn't save us much
>work to get rid of x-docs and fix FOR-470 in one step.
In order to get rid of x-docs, we need to create the stylesheet for
xdocs --> xhtml so, I recond that this nee
I just realized that this will also involve changing the documentation
and plugin sites and that is more than I'm able to do properly before
the .7-release. So I'll withdraw my proposal and just fix FOR-470.
Ferdinand
On Tue, 2005-05-17 at 12:06 +0200, Ferdinand Soethe wrote:
> I've started looking into FOR-470.
>
> Looking at the details, I keep wondering if it wouldn't save us much
> work to get rid of x-docs and fix FOR-470 in one step.
>
> If we don't I'd change all the wording for raw-files to 'xdocs' now
