"Invisible" text in FM, but appears in RH

[adrianaharper]

Hi all, using TCS2 on Windows 7 64 bit.

I am linking an FM book by reference into RH. In my RH book (mostly directly below anchored frame screen shots) I seem to have some periods, bullet points, etc. (in random spots - not consistently). In FM - I can't see them to delete them. To edit in RH makes no sense since everytime I update in RH it just overrides the manual delete (reading my FM files).

Does anyone know how to get these 'hidden' pieces of formatting to show themselves in my FM books so I can take care of them at the source?

TIA,

Adriana

[Matt-Tech Comm Tools]

1-Have you looked for hidden conditional text in and around your markers?

2-Have you saved as MIF & opened in a text editor to look for clues?

-Matt

---

Matt Sullivan
director of training
roundpeg, inc.

http://blogs.roundpeg.com
http://twitter.com/mattrsullivan

[adrianaharper]

Hi Matt,

Thanks. I looked at the MIF in notepad and for conditional text references and gathered the following...

-in some cases, it seems like the image in the anchored frame seems to think it is the same paragraph tag as the text it came after. So if the image is anchored at the end of the last line of a bulleted list, it has a bullet below it. I can fix this by adding a line of body paragraph text between the image and the text above... this is not idea as it generates extra spacing but better than a random bullet point i guess!

-in some cases, it seems if i make the image conditional (insert image by reference in anchored frame, mark as conditional) it won't stay put. Other times, conditionally marked images seem to stay where they are inserted. not sure what i'm doing differently...

I'm not sure of the why behind these cases?

[Matt-Tech Comm Tools]

Yep, that's a bit unfortunate with the extra space...but part of designing for both print and

online simultaneously.

There's likely a CSS fix for the extra space, but I don't know the CSS to fix that one off the top of my head.

Regarding the conditional text, I just wanted to make sure the extra characters weren't hidden condit text in your FM doc. It sounds like that's not the case, so you can ignore that part...

-Matt

---

Matt Sullivan
director of training
roundpeg, inc.

http://blogs.roundpeg.com
http://twitter.com/mattrsullivan

[Arnis Gubins]

Adriana,

From a FM point of view, you'd be better off creating a specific paratag for just holding the anchored graphics only. This way, you should be able to avoid the spurious bullets and when you apply a condition to it, you're applying that condition to a complete paragraph (entity).

[adrianaharper]

Hi Arnis,

Thanks- an interesting idea. I'm not sure I understand (pardon me sounding ignorant; not intended!) Why would I need a paragraph tag for anchored frames? I thought the point of the anchored frames was to keep the images where they are put into the text, etc.

In other words- I would create a paratag for images (for example), then insert an image by reference in an anchored frame, and then code the anchored frame with the images paratag?

If you have a spare moment for additional info/guidance on this idea, I would be grateful!

Thanks,

Adriana

[Burtin]

Hi.

I reported this feature as a bug quite a while ago. The only work-around I have found that is consistent is what Arnis has already suggested.

Hope this helps.

[adrianaharper]

Hi, Thanks.  I'm not 100% sure I understand how to do what Arnis is suggesting...

[Burtin]

I have a para style, "spacer,"set to all minimal dimensions, and I use it following problematic paras, like bullets, etc. I have mapped it into RH as well, so it changes the style immediately after the problematic style. It's a kludge, I know, but it will work until Adobe fixes the issue with bullets, etc.

Hope this helps...

[Arnis Gubins · Accepted solution]

Hi Adriana,

What I'm suggesting is to create FM paratags that will be used to hold anchored frames and tables only, i.e. special purpose "containers". If you ever need to apply conditions, then select the paratag that contains only the anchor. This approach provides easier maintenance scenarios, gives you more control at the tops of pages (e.g. use negative spaces in the paratag space below and the table space above to move the table to the top of the text frame on new pages), provides alternate find/change/list of strategies, controlled RH mappings, etc.