My apologies. My previous answer to your support request was completely
wrong. Our implementation indeed filters reltables. Moreover it seems to
do so quite correctly.
We didn't manage to reproduce the problem you have reported using ditac
2.2.0[*] using either stock conditional processing attributes (e.g.
"audience") or attributes specialized from props (e.g. your "customer"
attribute).
Please find attached to my next --private-- email the test case we have
used to attempt to reproduce the problem you have described. Please feel
free to modify this test case in order to reproduce the problem.
---
[*] You have reported the problem for ditac 2.1.0_01. However we don't
see any changes between ditac 2.2 and 2.1.0_01 which could have fixed a
bug related to conditional processing.
On 03/14/2012 03:33 PM, ditac-support wrote:
> In fact, in our implementation, we have completely *forgotten* the fact that
> a user could want to filter reltable, relrow, relcell, etc, elements.
> Everything else in a map, topicrefs of all kinds but also the map title and
> topicmeta elements, should be correctly processed.
On 03/14/2012 02:25 PM, Darren Carlton wrote:
> Problem:
> filtering on relrow with specialized attributes appears to be broken
>
> Details:
> I have a ditamap that contains the following entries:
> <topicref customer="AA" href=foo.dita"/>
> ...
> <reltable linking="normal">
> <relheader>
> <relcolspec type="task"/>
> <relcolspec type="task"/>
> <relcolspec type="reference"/>
> <relcolspec type="concept"/>
> <relcolspec type="concept"/>
> </relheader>
> <relrow customer="AA">
> <relcell type="task">
> <topicref href="foo.dita"/>
> </relcell>
> <relcell type="task">
> <topicref href="bar.dita/>
> </relcell>
> <relcell type="reference"/>
> <relcell type="concept"/>
> <relcell type="concept"/>
> </relrow>
>
> My ditaval file contains this entry:
> <prop att="customer" val="AA" action="exclude"></prop>
>
>
> The "customer" attribute is a specialization of props as follows:
> 1. An entities file defines this:
> <!ENTITY % customer-d-attribute
> "customer CDATA #IMPLIED"
> >
> <!ENTITY customer-d-att
> "a(props customer)"
> >
>
> 2. The map DTD declares the attributes by declaring the entities file
> and then specifying this:
> <!ENTITY % props-attribute-extensions "%customer-d-attribute;" >
>
>
>
> When I build, I get this message:
> ditac: WARNING: ::: "file:/foo.dita#foo", href points outside processed
> topics
>
> If I move the "customer" attribute from the relrow to the topicref in
> the relationship table, everything works OK.
>
> So I think the issue is with relrow recognizing specialized filtering
> attributes.
>
>
> Ditac Version:
> ditac: INFO: ditac version is 2.1.0_01
>
> OS used to run ditac:
> Ubuntu 10.10
>
> Java runtime version:
> java version "1.6.0_24"
>
> ditac command-line (launched through ant)
>
> <target name="ditac2javahelp">
> <java classname="com.xmlmind.ditac.convert.Converter"
> fork="true"
> failonerror="true"
> classpathref="maven.dependency.classpath"
> maxmemory="2248m">
> <arg line="-format xhtml"/>
> <arg line="-xslt2 xhtml ${ditac.dir}/ita/xsl/javahelp/ita-javahelp.xsl"/>
> <arg line="-filter ${dita.input.valfile}"/>
> <!-- Ditac stylesheet parameters -->
> <arg line="-p helpset-basename ${application}_helpset.hs -p map-basename
> ${application}_map.jhm"/>
> <arg line="-p toc-basename ${application}.js -p index-basename
> ${application}_index.xml"/>
> <arg line="-p xsl-resources-directory branding -p css-name
> ${application}.css"/>
> <!-- Output File -->
> <arg line="${output.dir}/_.html"/>
> <!-- Input File -->
> <arg line="${args.input}"/>
> <jvmarg
> value="-Djava.util.logging.config.file=${basedir}/tools/fop/logging.properties"/>
> <jvmarg
> value="-Dxml.catalog.files=${ditac.dir}/schema/catalog.xml;${basedir}/tools/${ita.dita.dir}/catalog-dita.xml"/>
> </java>
> </target>
--
XMLmind DITA Converter Support List
[email protected]
http://www.xmlmind.com/mailman/listinfo/ditac-support
