Issues with fm-indexterm

[MargoToth]

Hi all,

I am working with Framemake11 and DITA 1.2. Fm-indexterm is defined the commonElements.eddmod.fm.  I added  fm-indexterm to the general rule list for all the elements I would use it in,  such as the following:

(<TEXT> | ph | codeph | filepath | msgph | userinput | systemoutput | b | u | i | sup | sub | uicontrol | xref | fm-xref | cmdname | msgnum | varname | tm | note | dl | ul | ol | sl | codeblock | msgblock | fig | image | table | fn | menucascade | draft-comment | keyword | term | indexterm | fm-indexterm)*

I can insert an fm- indexterm without error, but when I save, I consistently get the following xml error:

Error at file C:\Untitled2.dita.058, line 38, char 47, Message: Unknown element 'fm-indexterm'

This is happening in tasks, concepts, and references.

Any ideas on what I need to do to fix this?

Thanks in advance. This list is a life (and time) saver.

Margo

[ScottPrentice]

Hi Margo...

Have you created your own structure application or are you using one of the default apps? If you're using the default apps, you should be able to use fm-indexterm already in all those places. Can you explain more about what you're doing?

It sounds like what's happening is that fm-indexterm is getting written out to the DITA file .. and this is not a valid DITA element. The default import/export client that ships with Frame performs some magic on the fm-indexterm element on save (and file open) to translate between the DITA indexterm element and syntax, and the fm-indexterm element. The fm-indexterm element is a marker and should only exist while you've got the file open in FM .. when you save, it gets converted into an indexterm element.

...scott

[MargoToth]

Hi Scott,

Thanks for the quick reply.

Yes, we are using the default apps.  We haven't messed with them at all. We have heavily modified the EDDs for the task, concept, and reference.

Here's  the full message error message:

XML Parser Messages (Document Instance)

Error at file C:\Untitled2.dita.419, line 36, char 47, Message: Unknown element 'fm-indexterm'

Error at line 36, char 73, Message: Element 'fm-indexterm' is not valid for content model '(#PCDATA|dl|parml|fig|syntaxdiagram|imagemap|image|lines|lq|note|hazardstatement|object|ol|pre|codeblock|msgblock|screen|simpletable|sl|table|ul|boolean|cite|keyword|apiname|option|parmname|cmdname|msgnum|varname|wintitle|ph|b|i|sup|sub|tt|u|codeph|synph|filepath|msgph|systemoutput|userinput|menucascade|uicontrol|q|term|abbreviated-form|tm|xref|state|data|data-about|foreign|unknown|draft-comment|fn|indextermref|indexterm|required-cleanup)*'

And here is what is in the read/write ruls for commonElements.rulesmod.txt:

/* Index terms */

element "indexterm" {

  is fm marker element;

  marker text is content;

  }

Do you think I may have a corrupt file?

[ScottPrentice]

Hmm .. well saying you haven't messed with them at all, but saying you've heavily modified the EDDs is a bit contradictory .. you *have* messed with them. 

It's hard to say what's wrong, but for some reason the fm-indexterm element is being written to the XML file, and it shouldn't be. The api client should be converting it into an indexterm on save. If you're using the default apps, then you shouldn't need to add fm-indexterm to the general rule .. it should be there already.

What you need to do it to roll back to the actual original default (unmodified) apps and confirm that you can use the fm-indexterm element there, then start customizing as needed. Have you created a clone of the default apps to a new name or are you using the original names? It's really best to leave the default apps alone (completely unmodified) and create your own apps from those with new names. That way you can always roll back to the default apps for testing and comparison.

Cheers! (?)

...scott