Agreed, draft mode should be an option you request, not the default. Set
draft.mode parameter to 'no' by default and then if the user decides he
wants draft mode, he will ask for it and the draft page masters will be
loaded.
I wonder how many people actually use draft mode.
On 9/20/10 3:44
In my customization layer I set the draft mode to yes by default and only
when a final build is run do I turn draft off.
On Mon, Sep 20, 2010 at 7:18 AM, Ron Catterall r...@catterall.net wrote:
Agreed, draft mode should be an option you request, not the default. Set
draft.mode parameter to
I didn't yet made the webhelp docbkx plugin but the plugin will mimic what
your are doing in your ant file.
I am not sure it is a long task, I think about 3 steps:
- you guess you just need to split your ant file in 2 by extracting the
compilation part into a top directory (like
I also agree that draft mode as currently implemented should have a default of
no.
The problem I have with the current, image-based draft watermark mechanism is
that if the image is dark enough to appear when printed (on all
printers...different printers yield different results), then it's so
Hello,
I am happy to announce that a new version of oXygen XML Editor is
available from our website
http://www.oxygenxml.com
One of the new features in version 12 is support for DocBook conditional
text processing. This allows to easily set profiling attribute values,
organize sets of
I believe it was set to maybe so that the status attribute on things like
chapters and sections can be used to indicate that part of a document is draft
(in documents that may take months to complete, being able to indicate that
part of a document is draft is important, since significant
All,
I understand Larry's concern. However, this scenario provides for a broken
FOP system right out of the box, which is a concern of mine. Yes, we can
provide a customization that shuts this off, but if we are eventually going to
set it to no why not just have the default no and set the
Hi,
There have been a number of issues raised against 1.76.0, but 1.76.1
should be released soon. When should we plan on having the critical
bugs closed so we can send out a release candidate for testing
(assuming snapshots are still broken)?
Thanks,
Keith
I have a customisation of the DocBook stylesheets which sets
xsl:param name=xref.with.number.and.title0/xsl:param
This was working with version 1.75.2 of the stylesheets. However, on
upgrading to 1.76.0 this no longer works. The numbers and the titles
are both output for references to tables,
