Probably you know all this but just in case.
Arbortext profiling expects multiple values to be separated by semicolons so
it "should" be:
And, of course, Arbortext expects the attribute to be defined in the DTD in
the element's ATTLIST:
product CDATA #IMPLIED
Can you change one element's definition in the DTD and one element
instance's profiling to match Arbortext's expectations and see what happens?
On Tue, Jul 14, 2009 at 2:59 PM, Margaret Devere <
> Hi folks --
> Something very problematic has just happened to my entire file set (only
> about 50 files affected, but still ....)
> We have a specialization that allows us to apply profiling across 9
> dimensions. For certain dimensions, we apply more than one value (e.g.,
> product="ProductA ProductB"). AE shows this in red strikeout, but v5.3
> always went ahead and rendered it, and I had everything set up and
> I upgraded to v5.4 and got that working. Copied the custom folder over,
> etc. etc.
> Now, I'm able to apply profiles just the way I always was, but when I
> render, all of the elements that had this "multiple" profile value get
> their profile attribute stripped. I check the content before I render,
> and all the values are there. I check after I render, and the profiles
> are gone.
> So I ran the Validate DITA Specialization utility and got 36 errors, all
> along the lines of "architecture is an improper additional attribute"
> ("architecture" is one of our custom dimensions).
> I read the install.pdf for v5.4 and it says "... thoroughly test the
> functionality. This is especially important in the areas of ...
> profiling, ...." And that's all they say.
> I don't think I can use profile groups -- they would not be mutually
> exclusive within a doc.
> It looks to me as if we need to update our specialization. We had this
> done for us so I don't know much about it but I can plunge in if need
> Any ideas from any angle? Something I can turn off in the rendering
> process to avoid updating the specialization? I can always publish from
> v5.3 but that won't work in the long run -- I'm dying to use v5.4
> Margaret Devere
> P.S. Hello to all the folks I met at PTCUser, and thanks for the many