The name attribute on extension-point element is a human readable name for the extension point. J

I have no more problems. 0.9.19RC10 works good with OT 1..7.4. Thanks. Ben

Hi Toshihiko, The other option you could have used, which is a little bit of a cheat is to use the element which does support @href in the .

Hi, Joe. The DITA TC is aware of this discrepancy. I cannot remember whether we decided to modify the DTDs or the spec language to resolve this inconsistency;

Hi Eliot and Kris and other on the DITA spec committee: In the dita spec for the element, it says: "Note: Beginning with DITA 1.2, the general task

Virginia, can I ask what you are trying to accomplish? I'll probably be able to give a better answer if I understand what you want to do. Best, Kris Kristen

... The @search attribute itself is yes or no, and just indicates whether the element and its children should be included in search results. For example, we

I'm not sure if the @search attribute does much. Supposedly, it is intended to indicate whether the target of a element "is available for

I have put 0.9.19RC10 up on the DITA for Publishers Files area (https://sourceforge.net/projects/dita4publishers/files/release-candidate/?) This should resolve

Due to an upgrade of the SourceForge project hosting for DITA for Publishers, the source repository has moved to a new location. If you have checked out the

If I want to use the @search capability for metadata...after compilation, where do I see the results? Does someone have an example of the @search and an

Dear Mr. Kimber, Thank you for your suggestion. Unfortunately my client does not want to apply specialization to their DTDs. So I still want to implement this

Data elements by default are not rendered. So you would need to implement custom processing to use those data elements to generate some output, including

Hi All, I'm developing a styleheet for DITA to PDF. Currently my client asked to me to make a cover page of PDF with their company logo image and product

OK, I have resolved the problem locally. The fix is to add elements to the plugin descriptors for the plugins that provide the extensions, e.g.:

I'm looking at these issues now. Note that I have clearly been leaning on the default lax processing prior to 1.7. Cheers, E. ... -- Eliot Kimber Senior

Hi all, I renamed plugin.xml to plugin_off.xml. However integration still reports another error. D:\DITA-OT1.7.3>ant -f integrator.xml Unable to locate

I had not, but you pointed me in the right direction. Reading the documentation for that feature got me looking into what DTD oXygen is using to validate my

In this case the integrator complains that the "xsl.transtype-html2" extension point hasn't been declared in the plugin.xml even if the implementation is

Did you run integrator?