Document validates but NoName is generated when opening

[shoose]

Hi all,

We have an xDocbook structured app based on Frame 11 and Docbook 4.2.   It has been stable until the last week or so.  Here are the changes we made to the structured app recently:

1. Added some functionality to the EDD including some Format Change Lists and attribute values, but nothing that seems major. The EDD validates and does not produce errors when its element definitions are imported into a document.

2. Added support to the DTD for an equation element to be allowed inside a line element

3. No edits to the rules.

4. In structapps.fm, we turned off "Try Alternative Extensions"

5. In the template, we added or tweaked some styles.

We retain our documents in XML and open them in Frame only to edit them.

However, each time we open any document in Frame now, a NoName element wraps whatever the top-level valid element is, whether a <chapter> or <appendix>. I can unwrap it and the document validates using the Element | Validate feature.  I save and close the document.  If I open the XML in a text editor, its top level element is <chapter>.  There is no <NoName.>  But if I open it again in FrameMaker, NoName is generated again at the top of the hierarchy. This is true even for documents that we have not edited or touched in months, so it cannot be the content itself; it must be something with the structured app.

To test, I have reverted the EDD back to a timeframe when it was known to have worked properly, and imported it into the template, then reopened the documents.  This is problematic of course because the documents currently contain attribute values that were not supported earlier, so Frame complains about these when I validate.  But the NoName element is always created no matter how far back I go with the EDD.

Finally -- and particularly strange -- is that I revert the EDD to an earlier, known stable version, import it into the template, and open some documents that we have not edited in months -- thus, recreating an environment that worked before.  Still, NoName is generated. I have not yet reverted the changes to structapps or the DTD and will try that next -- but I don't see how those could be the issue.

So the questions are:

1. What would make Frame generate a NoName element for a document that has valid structure?

2. What can trigger the generation of a NoName element?

Thanks for any help!

Shelley

Shelley Hoose

Sr Doc Developer

Rogue Wave Software

[shoose]

Hi all,

I have to apologize about this -- so sorry for those who were scratching their heads.  Apparently I introduced a NoName element into the content of the template.  I did not even know this was possible, and not sure how I could have done it.

So everything is ok now.

Thanks and again, sorry for the waste of anyone's time who read and puzzled over this.  😞

- Shelley

[Lynne A. Price]

Shelley,

   If the main flow in your template has content when you open an XML document, FM places the content of the XML document after the existing content. It then creates a NoName element to hold these two content segments. It's fairly easy to insert something like a space by accident into a template--something that's there but not visible. If you then open an XML document with <chapter> as the document element, the result will be a space followed by the chapter. Since the structured flow must have a root element, FM creates a NoName element.

   This doesn't seem to be quite your situation, since in the case I just described, you won't be able to unwrap the NoName. Your case, though, may have been some variation of such a situation. By the way, if your template contains a paragraph break (caused by unintentially pressing Return), FM does not create a NoName. With this variation, NoName is not needed since FM discards end-of-paragraph characters at element boundaries when it is manipulating elements.

        --Lynne

[shoose]

Lynne -- Thanks for the clarification on behavior when the template has content.  I still don't understand how a NoName element could have been introduced into the template itself in the first place.  But at least now I know it can happen so should not be stumped by this issue again.

- Shelley