[dmurphy]

Maybe in the near future. Thanks for the reply, Addam.

Reply

[dmurphy]

Hi Derek,

It doesn't seem to matter from where I copy it. I've copied it from NotePad++, from Slack, and even from this forum. I am pasting it into a reference-type DITA topic (although it doesn't matter the topic type). I had only tried it in tags on view. I just tried it in plain text view. XMetaL does not crash when I paste it in plain text view, but when I try to switch back to tags on view, it says “Unknown tag name. The tag name “PrincipalType:name” is not defined.”  It does not switch back to tags on view unless I remove the string. So evidently, even if it's pasted into a codeblock, it interprets it as a tag.

Several people in our organization have tried this. They all reported that XMetaL crashed as soon as they paste the string. Is there some way to enclose that type of content so it is not interpreted as XML tags?

Thanks,
Dana

Reply

[dmurphy]

Hi Derek – Sorry, I should have mentioned that in the beginning. We are using an SDL CMS. We use SuiteHelp 4 output type, which does not support DITA 1.3. I guess SuiteHelp 5 does support it.

Reply

[dmurphy]

Derek – I have a solution for this. We cannot use DITA 1.3 yet because the custom output we use does not support DITA 1.3. I didn't know about the default setting for DITA version in XMetaL. After switching from DITA 1.3 to 1.2 in Tools > DITA Options, no more errors about rowheaders in tables!

Thanks.

Reply

[dmurphy]

Thanks for the reply, Derek. If I double-the error while in Plain Text view, it takes me to the colspec element. If I insert rowheader=”norowheader” into each of the colspec elements, I do not get the errors anymore. But when I try to save or check it in, it throws an “invalid against DTD error.”

We do not use a specialized DTD. However, I noticed that in the topic that has the errors, the DOCTYPE line is this:

But in a newly created topic, it is this:

If I create a new topic, copy all content from the topic that has the errors, and paste it into the new topic, it does not report the “rowheader” errors. But if I change the DTD reference in the topic with the errors, to the one from the new topic, it still has the errors.

So I believe you're right, it's a DTD issue, but I just can't figure out how to resolve it. I don't want to just create topics and copy all content into those because we would lose all of the versioning info for the topics (we use a CMS).

Reply

[dmurphy]

By the way, it is XMetal 6.

Reply

[dmurphy]

No, we do not use specializations.

Reply

[Author]

Posts