• State Verified Answer
  • Replies 2 replies
  • Subscribers 138 subscribers
  • Views 2040 views
  • Users 0 members are here
Options
Related

ish* attributes are killing my 2.5.4 DITA OT builds. How do I handle them?

Simon Bate

My DITA OT publishing events are failing because the files extracted from the content store contain ish* attributes, such as "ishlabelxpath".

I suspect there's an action in publishing that I'm missing in the publishing chain.

My client's KnowledgeCenter (hasn't been upgraded to Tridion) has been producing output using several different 1.x OTs with many different plugins.

One wrinkle is that we're adding a 2.5.4 OT to the Publishing Service.

Everything works great, right up to when the OT starts. The OT's genlist pipeline fails with a parsing error when it encounters the ishlablexpath attribute.

Where are these attributes normally handled in the Pubishing Service? Is there a step I'm missing that adds the attribute to the DTD?
Rate translation
×
Suggest better translation
×
Parents
  • +1

    Dear Simon,

    This issue seems to me to be related to the fact that you haven't re-routed the catalog of the DITA-OT 2.5.4 towards the SDL Knowledge Center DTD's.
    Could you please change the file 'catalog-dita_template.xml' so that it is complaint with the catalog-dita_template.xml files used by the working DITA-OT 1.x instances.
    In short it comes down to replacing the available information of the file by the following statement pointing to the correct file location for your installation.


    <nextCatalog catalog="../../../../WebAuthor/ASP/DocTypes/catalog.xml" />

    I hope this helps.

    Kind Regards,

    Raf
Reply
  • +1

    Dear Simon,

    This issue seems to me to be related to the fact that you haven't re-routed the catalog of the DITA-OT 2.5.4 towards the SDL Knowledge Center DTD's.
    Could you please change the file 'catalog-dita_template.xml' so that it is complaint with the catalog-dita_template.xml files used by the working DITA-OT 1.x instances.
    In short it comes down to replacing the available information of the file by the following statement pointing to the correct file location for your installation.


    <nextCatalog catalog="../../../../WebAuthor/ASP/DocTypes/catalog.xml" />

    I hope this helps.

    Kind Regards,

    Raf
Children