Eric Larkin wrote: > > Thank you for the prompt response, and my apologies for a false alarm. > > After further investigation, I determined the problem was due to a CVS > configuration error - it was marking the jar files as text, and consequently > corrupting them when they were published to the webserver. We have the > default configuration loading from the webserver now...the next step is to > start playing with customization. > > In case you are wondering, I am working with Rick Lansky (who has sent you a > separate question about an enhancement to the stylesheet processing > functions). His question relates to a desire we have to enforce certain > document integrity rules for our docbook-based technical documentation (for > example, that each entity has a globally unique value within our entire > document set, not just a unique value within the xml file itself). While > this is possible with your Java API (as evidenced by the documentHook > XMLMind already uses to "fix the cols attribute of tgroup and entrytbl" in > docbook documents), it is much more elegant for us if this is done with > stylesheets, as we are then able to use the *same* stylesheets for > processing & verifying the documents outside of XMLMind. > > We have purchased one copy of the Professional Edition for testing and > development, and I am hoping to purchase several more if we can get the > customizations to work well enough.
You said the magic words :-)
