Inspiring

Question

Condition settings must not change between <XRef> and <XRefEnd>

Forum|Forum|11 years ago
January 13, 2015
1 reply
351 views

(FM12 on Win7)

For files that I upgraded from FM11, I now see messages in the FM console that I did not notice from FM11:

"MIF: "<file path> [#####]: Condition settings must not change between <XRef> and <XRefEnd>.

Apparently FM12 reports an anomaly that FM11 did not.

What is the importance or significance of these reports?

Best regards,

This topic has been closed for replies.

Bob_Niland

Community Expert

re: "MIF: "<file path> ...

Are you opening a MIF or doing a MIF wash when this happens?

Just taking a quick look, it's not clear to me how one could even get a condition applied within an <XRef>...<XRefEnd> range.

If the source text being xref'd is CC'd, that CC itself does not appear in at the Xref. The source text is either there or not, depending on the current Show/Hide status of the CC, but CC markers don't appear in the data structure at the Xref.

One can apply a CC to an Xref, but in that case the CC markers are outside the Xref markers. You can't even select less than the whole Xref's string to apply a CC to ...

... in FM7 anyway.

M

max_drawdownAuthor

Inspiring

@error7103,

Thanks.

Context: RoboHelp 11 was updating the presence of linked FM files. While that update operation was underway, the FM console reported those messages.

I happen to agree re: applying a condition on part of an xref. Seems bizarre.

Uh, CC = ?

Best regards,

M

max_drawdownAuthor

Inspiring

Here's a sample of a MIF that is reported the console messages.

   <XRef

    <XRefName `Figure+Num[]'>

    <XRefSrcText `75642: fgc-FigCaption: Figure\x11 2.1.\x14 product interface'>

    <XRefSrcIsElem No>

    <XRefSrcFile `'>

    <XRefLastUpdate 1414596356 119000>

    <XRefSrcElemNonUniqueId `'>

    <XRefAltText `'>

    <XRefApiClient

     <XRefClientName `'>

     <XRefClientType `'>

    > # end of XRefApiClient

    <Unique 1291320>

   > # end of XRef

   <String `['>

   <Font

    <FTag `l-Link'>

    <FLocked No>

   > # end of Font

   <String `Figure'>

   <Char HardSpace>

   <String `2.1'>

   <Font

    <FTag `'>

    <FLocked No>

   > # end of Font

   <Unconditional >                    # THE ERROR MESSAGE IDENTIFIES THIS LINE

   <String `]'>

   <Font

    <FTag `'>

    <FLocked No>

   > # end of Font

   <Conditional

    <InCondition `Print'>

   > # end of Conditional           # ANOTHER ERROR MESSAGE IDENTIFIES THIS LINE

   <XRefEnd >                         # AND HERE IS THE END OF THE XREF

So from the looks of the MIF, condition controls really appear within the xref as the error message indicates.

How they got there I have no idea.

Again, I had not noticed this behavior in FM11.

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded