As quoted from Cameron Shorter <[EMAIL PROTECTED]>:
> +1 retrospectively.
>
> However, I don't think we need docbook at all now.
> Docbook was used to build our design documentation during the build
> process. (Old design documentation is stored in mapbuilder/design).
That could be right; the o
+1 retrospectively.
However, I don't think we need docbook at all now.
Docbook was used to build our design documentation during the build
process. (Old design documentation is stored in mapbuilder/design).
However I think all our design notes have been migrated to
http://communitymapbuilder.or
As quoted from Linda Derezinski <[EMAIL PROTECTED]>:
> +1
All votes in favour! ;-)
It has been done.
Kind regards,
--
-- Gertjan van Oosten, [EMAIL PROTECTED], West Consulting B.V., +31 15 2191 600
-
This SF.net email is sp
+1
On 6/8/07 4:44 AM, "Gertjan van Oosten" <[EMAIL PROTECTED]> wrote:
> Hi MapBuilders,
>
> Any objections if I upgrade bin/docbook-xsl in the ol-integration
> sandbox to a more recent release (1.72.0)? It is about half the size of
> the version we use now:
>
> 35M bin/docbook-xsl
> 17M
Hi MapBuilders,
Any objections if I upgrade bin/docbook-xsl in the ol-integration
sandbox to a more recent release (1.72.0)? It is about half the size of
the version we use now:
35M bin/docbook-xsl
17M bin/docbook-xsl-1.72.0
and has the same functionality: generating the docs with the n
