[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: Re: DOCBOOK-APPS: clarify profiling logic
ed nixon wrote: > I assumed that simply naming the attribute with > <xsl:param name="profile.attribute">audiencelevel</xsl:param> and then > initializing it with > <xsl:param name="profile.value">manager</xsl:param> would do the trick. Yes. But this way, you can use just one custom attribute. > However, how the value got associatedwith the attribute under this > scenario seems a little magical, now that I think about it. No magic there. Using say profile.userlevel=foo is equivalent to profile.attribute=userlevel and profile.value=foo > Although > things seemed to work fine until I started to use combinations. How > multiple value attributes came together would be even bigger magic, I guess. Multiple values in an attribute aren't problem. You must just separate them with ; (more precisely with profile.separator) > I'll try this with different, non-custom attributes and see where I end up. If you really think that you need more then one custom profiling attribute, then submit RFE. It would be easy to add parameters like profile.attribute1 and profile.value1. Jirka -- ----------------------------------------------------------------- Jirka Kosek e-mail: jirka@kosek.cz http://www.kosek.cz
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC