Samah,
I'm afraid I'm down to grasping at straws, now, as I haven't done a
whole lot with this feature and can't see any obvious problem with
what you've done, though the needing to include the namespace prefix
inside the "element" attribute does make me think something isn't
quite right, as this doesn't follow the pattern of the examples in the
distributed doctypes.
For reference, what version of Arbortext Editor are you using? Can
you provide the full DTD and DCF you're working with (privately to me,
if you aren't comfortable with making it available on the list)?
One other thing I'd suggest is only putting the non-required elements
into the InsertAutoWithin, leaving Editor to supply the required ones
as it normally does. Your last example appeared to follow that, but
perhaps a little more experimentation with different combinations
might shed some new light on the issue.
-Brandon 🙂
On Wed, Aug 12, 2009 at 10:56 AM, Samah
Abu-Mahmeed<sabu-mahmeed@jonesmcclure.com> wrote:
> Hi Brandon,
>
> No, the DTD does not incorporate a namespace. I just used it in the
> markup.
>
> When it allows me to insert the indexterm, AT inserts the required field
> (as in specified in the DTD) and does not insert the additional elements
> I added in the dcf. I don't something else happening.
>
> <contexttransformations>
> <insertautowithin element="evidbook:indexterm"<br"/>> xmlns:evidbook="evidbook.dtd">
> <evidbook:secondary></evidbook:secondary>
> <evidbook:tertiary></evidbook:tertiary>
> </insertautowithin>
> </contexttransformations>
>
>
> Thanks,
>
> Samah
>
