FM changes conditional tags on imported files

[Peter32610444u0rc]

FM changes the conditional tags on imported files the next time I open the target file after import. The result is a conditional filter that lets conditional text slip through to the generated PDF, though it shouldn't have been there. I can change the setting back, but FM refuses to keep it.

Keep this please      I don't want to see this

[Jeff_Coatsworth]

What version of FM are you using and what are you importing from? Are these Text Insets that are being created?

[Peter32610444u0rc]

The version is 17.0.3.

I import files created with the same version as the target files.

[Jeff_Coatsworth]

Ok, and was this working before and now it doesn't or was it never working?
How is the content ending up inside FM - as a new document in a book or as a Text Inset within an existing doc?

[Peter32610444u0rc]

I think it has been doing this since I started creating documentation in FM about six months ago.

These are .fm-files imported into other .fm-files like this:

[Winfried Reng]

Hi Peter,

Does the source file already have the correct Show/Hide settings?

Do you select in the target document only the text inset to check the Show/Hide settings? Not also additional characters before/after the text inset?

Best regards, Winfried

[Jeff_Coatsworth]

Ah yes - that state in the "I don't want this" image usually means you've selected a mixed bit of conditioned content and some with none or a different type of condition applied.

[Peter32610444u0rc]

Yes, but I haven't. I select the whole text insert and then apply the conditional setting. To make it even more mysterious, FM does not always change it.

I select the text inserts with the mouse. As the picture shows, the numbers of the next (unconditional) heading are also selected. That does not, however, apply any conditions to the heading (and it shouldn't).

[Jeff_Coatsworth]

So the whole of 13.9 in this image is the text inset (the heading, anchored frame, image, caption, and 2-row table)?

[Peter32610444u0rc]

Yes, that is right.

[Jeff_Coatsworth]

So what's selecting part of the next 13.10 heading and xref tag? Have you tried teasing that apart to see if there's some other element in there (maybe super tiny)?

[Peter32610444u0rc]

I cannot tell.

      

[Winfried Reng]

A FrameMaker file always ends with the end of flow character.

If you insert a file into another file as a text inset, this end of flow character is turned into a paragraph mark at the end of the text inset. When the text inset is inserted at the beginning of a paragraph, you see this paragraph mark at the end of the text inset. In this example here the text inset continues to the beginning of the next paragraph (heading 13.10 or in the next screenshot empty paragraph).

[Peter32610444u0rc]

Hi Winfried,

The problematic inserts are typically used without conditional tags.

I select only the text inserts as described in my reply to Jeff Coatsworth.

Best regards, Peter

[Winfried Reng]

Ah, so the condition is not in the source document, but you apply it to the text inset?

Yes. Then your issue could happen.

I will check, if I find more info.