After testing the toolkit, I see that you're correct. I've asked the
Yahoo dita-users group about this, as it makes no sense to me, but
thanks for the explanation!  

On a related topic, it looks like conrefs to map elements should not be
scoped. We had an earlier discussion about this regarding a topicgroup,
but I think it applies to all map elements. If my topicref @conref looks
like this: 

bar.ditamap#x/y

the toolkit gives this error: 

[xslt] [DOTX010E][ERROR]: Unable to find target for
conref="bar.ditamap#x/y". Check the target element is available, and
that it is a 'xxxx' element. Check to make sure the target of conref is
correct.

If I change my @conref to:

bar.ditamap#y

the process runs without a problem. However, XXE complains that it can't
transclude the @conref in this form. 




-----Original Message-----
From: Hussein Shafie [mailto:[email protected]] 
Sent: Wednesday, August 09, 2006 1:52 AM
To: Mark Fletcher
Cc: xmleditor-support at xmlmind.com
Subject: Re: [XXE] dita_map.css shows @href of source topicref even when
a @conref is specified

Mark Fletcher wrote:
> If an @href is to be shown, I would think it should be the @href of 
> the target element. Can this be fixed?

This is already the case, unless the source of the conref has its own
href attribute. Example:

[1] Source topicref is
<topicref href="foo.dita"/>

[2] Set its conref attribute to "bar.ditamap#x/y", where
"bar.ditamap#x/y" is <topicref id="y" href="gee.dita"/>

[3] XXE transcludes <topicref href="foo.dita"/> but you'll still see in
XXE  href="foo.dita" as CSS generated content.

This is the correct behavior[*]: a topicref which is the source of the
conref must not have an href attribute because this href attribute would
``have priority'' over the href attribute of the conref target.




> Which leads to a question. I've tried overriding the selector that 
> provides this content (topicref:before) with this one:
>  
> topicref[conref]:before {
>     content: "";
> }
>  
> but it's never used. Is there something peculiar about how the @conref

> attribute is handled by CSS?
> 

A topicref having a conref attribute is immediately transcluded (i.e. at
document load time). The transcluded topicref no longer has a conref
attribute and therefore the above CSS rule cannot be applied. Once
again, this is the correct behavior[*].



---
[*] Ask the DITA gurus! we've just ``reverse-engineered'' the DITA OT
1.2.2 XSLT style sheets which handle transclusion.




Reply via email to