Unwanted paragraph tag after text inset

9.0p255 on XP ... Just searched the forum for a reminder, as it's not every day I need to work with insets. A couple of posts towards the top of a long thread gave the tip of leaving a special space between the anchor for the inset and the end-of-paragraph marker; "ah, that sounds familiar!" I thought, and tried it. Well, it may sound familiar ... but it doesn't work. Yes, I've already tried a special paragraph style with space above and below set to -2; no luck there either. All the more annoying since I'm fairly sure I did manage to do it in another file-set/on another PC last year. Thanks in advance for any tips!

Niels -
I am stuck in Frame 7.0p577 on Mac (having not yet invested in emulators etc.), so what I say here may not apply to Frame 9 on Windows – but it probably does. I am very familiar with the iceberg of an issue whose tip you have encountered. As I see it, here's what's up:
When Frame imports a text inset, it takes the end-of-flow and turns it into an end-of-paragraph (displayed with ¶ at its end, assuming you have Display Text Symbols turned on in View Options). Provided that the inset is followed by another paragraph, then all is well. However, the creation of this extra paragraph is insidious in cases where the inset lies at the end of a flow.
First, if the inset ends a document, an extra line results; that extra line is troublesome if it pushes over a page boundary. The workaround is to increase the height of the page frame, to make room for the line without spilling onto a new page, but that's messy because the manual height adjustment needs to be adjusted again if subsequent editing changes the placement of the extra line.
Second, it seems that the extra paragraph takes the paragraph tag – and therefore, the paragraph formatting – of the FIRST paragraph in the inset. If the first paragraph of the inset's source flow has an autonumber, then the stray paragraph after the inset will appear with ANOTHER autonumber of that style.
Third, if an inset is placed in a table cell, the extra line causes the height of that cell to increase. In the common case that the cell then exceeds the height of other cells in the row, the height of the entire row will increase, leaving undesired space. Workarounds such as manually limiting row height are a pain.
Fourth, if the inset is placed in a footnote, the extra line causes the footnote height of that cell to increase, leaving unwanted space between footnotes of at the bottom of the page.
Over the years I have adopted the following technique: At the front of flows liable to be used as inset sources, I have an empty paragraph tagged BOF. I set the BOF format in both the source document and the host document to Run-In. Any autonumbering in the first functional paragraph of the source will then be prevented from being carried into the referring document. You might think that a comparable paragraph at the end of the inset source – EOF, maybe – would defeat the insidious behaviour that I describe, but too much of this and things start to fail.
I have one or two additional ideas in case anyone who made it this far wishes to contact me directly. In fact I'd be delighted for anyone who understands any of the above to contact me!
I would be delighted if someone at Adobe would follow-up on this, but honestly don’t expect too much.
- Charles,
www dot Poynton dot com

Similar Messages

Extra and unwanted paragraph tag after text inset

Using Framemaker 7.2 -- we maintain a number of manuals which reference a group of common sections, each of which is a separate .fm file.
The ratio is one-to-many: for example, there is an .fm file called "Bob" which contains information common to multiple manuals. The contents of "Bob" is then imported by reference into other .fm files which reside with the rest of each manual.
By way of description, the entirety of the in the target document is selected when clicked anywhere; double-clicking causes the Text Inset Properties dialog to appear. "Updating of Imported Flow" is set to Automatic.
The problem is that each time "Bob" is updated and the changes are populated out to the dependent sections of the manuals, an empty paragraph is inserted at the end of the imported text. By default, this empty paragraph receives a tag which causes it to show up in the TOC of the manual in question.
This behaviour is annoying until the erroneous TOC sneaks through the editing process -- my fault! -- at which point it becomes embarrassing. Is there a way to prevent this behaviour from happening in the first place?

> We would like to insert the text inset between two topic titles.
> When we do this, an empty paragraph tag appears under the text inset.
Well, not really. A text inset has to be anchored to a paragraph.
This is the paragraph in which the cursor is placed when you
import the inset. If you anchor it to an empty paragraph, then
that paragraph will still be there, empty except for the inset anchor.
(There is no "anchor" symbol associated with an inset)
> When we delete the paragraph tag, it seems that the last topic
> title becomes a part of the text inset.
No, it doesn't. The topic title is placed in the same paragraph as
the inset anchor, that's all.
> When you update the FM book, go to the TOC and click on the link
> of this last topic title, the whole title and text inset is selected,
> not only the title as it used to be.
And why is this a concern? The inset should work as expected.
The reason is that if you follow a TOC link, the whole paragraph
becomes selected, including the inset anchor and the inset.
If this bothers you for some reason, you need to anchor the inset
in a VERY small paragraph between the two topic titles, say 2-pt
font size with zero space above/below.
/Thomas Michanek

PgfLocked Yes after text inset

I'm spinning off versions of some manuals for another division (same product, different paint), and decided that rather than entirely clone parallel FM files, I'd try having the main Flow A be a text inset from the defining instance of the product manual, with division-specific content controlled by Condition Codes. Grave warnings on this forum to the contrary notwithstanding, it works perfectly . But I did run into an oddity while testing.
The clone manual started as a whole-flow paste of the defining content. When I began to test doing it as an inset, I deleted the clone Flow A, which had a Heading1 as the first Paragraph Format. This left an empty Heading1, into which the defining flow was imported, as:
<*> Body Page Flow [ A (Main Flow) ]
<*> Retain Source's Formatting
<*> Automatic
Alas, there were two extra empty pages at the end, due to the Heading1 having Top of Page elected, and due to Make Page Count Even on save.
So I deleted the inset and tried to change the Heading1 to Body.
No go.
I could insert or delete text in that Heading1 (so it wasn't set to read-only), but nothing would change the Paragraph Format.
So I saved it as a MIF. I found these tags:
<Para
<Unique 5547797>
<PgfTag `Heading1'>
<Pgf
 <PgfLocked Yes>
> # end of Pgf
<ParaLine
 <TextRectID 80>
 <String `'>
> # end of ParaLine
> # end of Para
> # end of TextFlow
# End of MIFFile
I've never noticed tag PgfLocked before.
And if you import the inset with
<*> Reformat Using Current Document's Formats
tag PgfLocked is not there.
Changing "Yes" to "No" (MIF hacking) fixed the problem.
Is there a Frame menu item for this? (this is 7.1/Unix)
I'm guessing that specifying:
<*> Retain Source's Formatting
is what's causing the lock.

... I don't believe it's documented in the FM9 MIF reference guide
It's certainly not in Help. And it's had no mention here (at least based on a quick googling).
I probably never noticed it before because it's probably never been in any MIF I hacked.
Meanwhile, back at the culprit:
<*> Retain Source's Formatting
I found two more reasons to avoid this option on text insets:
Text defined by Variables in the inset lose their Character Formats (and it might be my imagination, but the loss appears to occur during printing - the ChFmt is visible during edit)
If the text inset contains a text inset (yes, that actually works), text defined by Variables in the subordinate inset don't make it into the top document at all.
And this is the case when when all of the documents involved share the same pfg/ch formats and variable defs.
<*> Reformat Using Current Document's Formats
fixes both of these problems, plus the <PgfLocked Yes> issue.

Feature request: Heading Tags and Paragraph Tags for Text element

Sugestion: Would like to see Reflow be able to format text element with heading tags like <h1> and paragraph tag .

Thanks! Style management and reusable styles are a HUGE feature set coming to Reflow...won't be there immediately but very soon. Thanks for the input.

Add paragraph tags after each period

Hi!
I'm into a hidious task to add paragraph
markers after each period (.) in a long set of text. Is there any
way to automate this work?

Andy Bay wrote:
> I'm into a hidious task to add 
paragraph markers after each period (.) in a long set of text. Is
there any way to automate this work?
Start by making a backup, then use Find and Replace.
Set the Search to Source Code. Search for ". " (without the
quotes).
Replace with "." (again, without the
quotes). Click Replace All.
You can finally tidy it up with Commands > Apply Source
Formatting.
David Powers, Adobe Community Expert
Author, "The Essential Guide to Dreamweaver CS3" (friends of
ED)
Author, "PHP Solutions" (friends of ED)
http://foundationphp.com/

Unknown space after text inset

As seen in the picture below (also added link for larger picture, will be available 24 h ExtraZoom High Definition image #32005. Zoom in or zoom out high resolution photo.),
there is a huge space between the inset (table broken across 2 pages) and the following paragraph.
All insets are written in the same way, but only this one happens to look so weird. I've checked the inset and there is no huge space at the end of it.
As you can see in the picture below, the end of the page is right at the end of the table's anchor (text cursor can be seen)
Any ideas as to what I could possibly do to resolve this?
Thank you!

Hello!
In regards to your response, I've uploaded the fm files (main file + insets) and scrubbed the confidential information out of them. The issue is still reproducible, as seen in the Data.fm document.
Thank you for replying on such short notice!
Dropbox - fm files.zip

Some conditional text in text inset showing when text inset is set to condition and hidden

I'm using Frame 8 on XP Pro SP3.
I have some text insets that I want to mark to appear or disappear depending on whether the document needs them or not. One is "domestic" and the other is "row".
My problem is that within the text inset is a condition (G2) that also appears in the document that I want to show in the document whether or not the text inset shows.
So what's happening is:
1 - Click on the text inset.
2 - Set it to "domestic".
3 - Set my target file to show "row" along with "G2".
4 - The text inset disappears except the "G2" tagged text from the inset still shows.
I end up with a heading on the following paragraph that has the paragraph number followed by however many instances of text tagged "G2" in the text inset or insets followed by the actual text of the heading.
I seem to remember that previously if you tagged a text inset with a condition and then turned off the condition, the text inset (all of it) did not show. So it appears that Frame 8 now will hide the text inset except for any text tagged with a condition that is used and set to show in the target file.
I'm haven't played with the expressions much, but I'm not sure there's a way to tell it to use the "G2" condition in the file, but ignore it if it's in a text inset that isn't to be shown.
Thanks,
Mike

Mike, please specify the exact version of FM you're using, from Help > About, the "pxxx" numbers.

Text Inset in Container File Loses Conditional Tag

Hi,
(Framemaker 8.0p277,unstructured)
I have a number of books that make use of text inset and conditional text. Some text insets contain conditional text in their source. Then, after the inset is put into the container file, the inset may be further conditionalized. This illustrates the situation:
--- Text Inset ---
This inset was created for end users.
When using function X, blah blah blah
-----End Inset----
The red text indicates an InternalDocComment condition. This inset is then placed into the container file where it has another condition applied, PrintOnly for example. PrintOnly is in blue.
The writer is able to set all this up fine. After placing the inset into the container, she selects the inset and applies PrintOnly. The text inset appears in blue and the InternalDocComment as visible shows the maroon of two mixed colors. The writer saves the file, continues working on the files, then later in the week, the writer opens the container file. The blue color indicator is gone from the inset. When the writer selects the inset and chooses Apply Conditional Text, the Conditional Text dialog shows the current selection is Conditional (radio button) but no tags appear in the In portion of the dialog.
I've tried using spacer paragraphs in and around the text inset to see if we can get the conditional tag to "stick" but nothing is working.
Has anyone run into this before?
TIA,
Mary

I use a lot of conditional text and insets but within a structured document. I have noticed that FrameMaker does not always do what one thinks it does. For example, copy a piece of unconditional text and paste it in the middle of conditional text and the pasted text remains unconditional. Each time you open the document, FrameMaker updates the text insets. In your case, it is updating a text inset that is on the whole unconditional. So, my guess is that it bringing it in as unconditional, much like the copy and paste example above. You might test this by creating a small document with the inset and over conditioning, saving it in the mif format, opening the mif file, and looking at how the conditioning is applied. Then save the Frame file, open it, save as mif, and repeat the above. If the containing file conditions DO hold up, then try removing the conditioning within the containing file and reapplying it; this may help to clear out some bad conditioning.
I vaguely recall trying to conditionalize a text inset within the containing document and had problems. I cannot remember what exactly the problems were. My solution was to do the conditioning within the inset file itself. So, if the text inset is always to be conditionalized in the containing document, then do the conditioning within the document itself.

Why does my paragraph tag for images get repositioned AFTER the image?

I have TCS2 and link my FM docs to RH.
I use a paragraph tag in FM called "figure" for my imported images. I noticed there is too much space after the images in RH and discovered the "figure" tag is BELOW the images. So even if I map the tag to a RH style, it won't do any good. Any suggestions?

This might fix your problem. Look at how your anchored frame appears in the FrameMaker document. It's probably like this:
┴ ¶
Which is simply the anchored frame marker followed by the paragraph marker.
Now try this. Before the anchored frame marker, add a forced space (CTRL-Space).
|_| ┴ ¶
When RoboHelp interprets this, it appears to place the paragraph before the anchored frame, not after it.
This is assuming you've got the anchoring position set to"Below Current Line," as suggested earlier.
Hope this helps!
Jason

TCS4: Hyperlinks in RH10 are broken after an FM text inset. Why?

Hyperlinks from another FM document of the same FM Book does not work in RoboHelp after an FM inset. But hyperlinks from the same FM document works in Robohelp after an FM inset.
All the hyperlinks work in PDF.
Note: The hyperlinks are not within the text inset but outside the text inset. As long as it is after the text inset, from that point onward, the links will not work (if they point to another FM doc).
eg:
text inset
content
hyperlink broken (from another FM doc of same FM book)
Please help. It would be a pain if this does not work at all.
Kai

I would set up a simple set of files to test this with TCS5 (download a trial on a machine that doesn’t have any TCS products on it) and if you can reproduce the behaviour, report it as a bug and send the files to the TCS Support group. They’re not going to be patching TCS4 now that 5 is out.

Cross reference markers are deleted for content in text insets

Cross reference markers are deleted for content text insets. I currently have a chapter that is built from several Import by Reference files. I added an introductory paragraph with cross reference links to heading 2 titles in these text insets. Everything works and saves normally, although the cross reference markers disappear from the chapter when files are checked out a few days later. An extra Heading 2 is also added to the end of the document.
Steps to reproduce:
1. Create a chapter composed of several text insets.
2. Create a list of cross references to headings in these text insets at the beginning of the chapter.
3. Check in/check out the files from a source control product.
What went wrong?:
The cross reference markers are gone, resulting in broken cross references. An empty Heading 2 is also added to the end of the document following the final text inset
What should have happened?:
The markers should remain and the heading 2 tag should not be applied to the document.
Product version:
Product: FrameMaker
Version: 7.2
Platform information:Windows XP
Hardware: Dell Latitude D620
OS Version: Windows XP Professional Version 2002, Service Pack 3.
RAM: 1GB

Thanks for the information, Van. We did try several techniques including adding the insertion point immediately after the text inset before the normal paragraph tag, but none seemed to consistently work. I will investigate this scenario futher, though, in light of your comments.
We have managed to determine a workaround for this issue by avoiding a string of text insets. For some reason, using multiple text insets without separating them with normal text causes most of the problems after we add the files to our source control system. The situaton is not ideal, but it does work for the time being anyway.
Steve

Missing closing paragraph tags

Well this is a conundrum. The closing paragraph tag (i.e.
) which is considered optional and which Dreamweaver does
not automatically insert at the end of a paragraph makes a
difference to Internet Explorer (at least version 7.0 which I
previewed the page in). Without the closing tag, IE does not add
space btw paragraphs. I created many web pages recently and
previewed everything in Firefox. I wasn't sure what the client was
talking about when they complained that I was removing spaces btw
paragraphs. I had to go back by hand and insert the missing tags.
Has anyone else run into this problem? Why would a tag that
is so essential be considered optional? Any way just make sure that
you close your paragraphs!
Tom

> Here is the doctype code from one of the problem
documents
> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01
Transitional//EN"
> "
http://www.w3.org/TR/html4/loose.dtd">
>
> (Is there a recommendation for which doctype to use?)
You should choose a doctype that's consistent with your
coding ability.
This one is fine unless you are an advanced coder.
> This seems like a loophole that Dreamweaver should try
to fix. I only say
> this
> after having spent several hours having to fix this.
Normally it wouldn't
> bother me.
I have confirmed your finding. I'll submit it. Wouldn't hurt
if you did
too!
http://www.adobe.com/cfusion/mmform/index.cfm?name=wishform
Murray --- ICQ 71997575
Adobe Community Expert
(If you *MUST* email me, don't LAUGH when you do so!)
==================
http://www.projectseven.com/go
- DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs,
Tutorials & Resources
==================
"TSemmes" <[email protected]> wrote in
message
news:gqr5lv$5s6$[email protected]..
> Here is the doctype code from one of the problem
documents
> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01
Transitional//EN"
> "
http://www.w3.org/TR/html4/loose.dtd">
>
> (Is there a recommendation for which doctype to use?)
>
> Actually I did a test with Dreamweaver to see if it
would automatically
> add
> the closing tag.
> This is what I found.
> If the text that is being editing does not have a
paragraph closing tag,
> when
> that text is broken into paragraphs, each paragraph does
not have a
> closing
> tag. It seems that Dreamweaver picks up its decision to
include a closing
> tag
> or not, by the paragraph that is already there.
>
> This seems like a loophole that Dreamweaver should try
to fix. I only say
> this
> after having spent several hours having to fix this.
Normally it wouldn't
> bother me.
>
> Tom
>

Importing a XML file in my INDD template. I get lots of unwanted paragraph breaks

Hi,
I am importing a XML file in my INDD template. I get lots of unwanted paragraph breaks where the closing xml tags for elements appear.
Can someone guide me please to rectify the problem?
Regards,
~shibu

Here is the screen shot from INDD: Though I manage to get rid 0f them when i close up the XML tag manually, I want a sure-shot solution. Thanks for helping me out.
and here is the screen shot of the XML coding:
<para aid:pstyle="4 body text">Another common alkali is potassium hydroxide, KOH.</para>
<equation><mathphrase>KOH(aq) → K<superscript>+</superscript>(aq) + OH<superscript>–</superscript>(aq)</mathphrase></equation>
<qandaset>
<title aid:pstyle="7 Questions heading"><emphasis role="underline">Questions A</emphasis></title><qandadiv><qandaentry><question><orderedlist numeration="arabic" startingnumber="1">
<listitem><para aid:pstyle="7 Question text">Two solutions are tested with universal indicator paper. Solution A has a pH of 8 and solution B has a pH of 14. What does this tell you about the two solutions?</para></listitem>
<listitem><para aid:pstyle="7 Question text">Methyl orange is added to a solution and the solution turns pink. What does this tell you about the solution?</para></listitem><listitem><para aid:pstyle="7 Question text">What does the ‘basicity’ of an acid refer to?</para></listitem>
<listitem><para aid:pstyle="7 Question text">Calcium oxide is an example of a base. How do you know this?</para></listitem>
</orderedlist>
</question>
</qandaentry>
</qandadiv>
</qandaset>
</sect1>
<sect1>
<title aid:pstyle="3 Heading">What are salts?</title>
<para aid:pstyle="4 body text">Previously, it was explained that acids contain <emphasis role="bold" aid:cstyle="4 body bold">replaceable hydrogen atoms</emphasis>, and that when <emphasis role="bold" aid:cstyle="4 body bold">metal atoms</emphasis> take their place, a compound called a salt is formed. The names of salts have two parts, as shown:</para>

<para aid:pstyle="4 body text">The table shows the four most common acids and their salt names.</para>

How to customize the content set in text as part of tag cq:text property="text"/

We use the tag <cq:text property="text"/> to get the content, which is set in the jcr property "text". Text was set in Richtext component and it has hyper link.
Now, we have to customize the text.
Example:-
Actual Text in 'text' property:-
Click <a data-action="Hyperlink" data-upc-tooltip-type="none" href="/content/www-abc-healthcare-ch/en/offer.html">here</a> for the link 
After customization in 'text' property:-
Click <a data-action="Hyperlink" data-upc-tooltip-type="none" href="/content/www-abc-healthcare-ch/en/offer">here</a> for the link 
i.e .html has been removed.
I tried customizing and set back to text attribute using <c:set var="text" value="<CustomizedText>" /> but even after that tag <cq:text property="text"/> retrieves the old content i.e with .html
Please suggest how to override text content, so that the tag <cq:text property="text"/> will print customized text.

Which version of cq? Is Strict Extension Check enabled at http://<host>:<port>/system/console/configMgr/com.day.cq.rewriter.linkchecker.impl.LinkCheckerTra nsformerFactory
Thanks,
Sham

Make new paragraph tag available in all documents in a book

I'm very new to FM10, so please excuse my ignorance.
All I want to do is make a custom paragraph available in all the chapters
of my book. I created a variation of Heading2 (and gave it the paragraph tag
of H2), in one chapter and use it extensively there.
I checked the "add to catalog" box when I created it, but when I'm working on
the other documents (chapters) in the book, H2 doesn't show up in the
paragraph catalog .
After failing to make "import format" work, I even tried to re-create the same H2
paragraph from scratch in one of the the other chapters.
But to add insult to injury, after typing in all the custom H2 characteristics in that
other chapter, and attempting to put in the catalog (which was not showing
an H2 in that chapter), FM told me that it couldn't do it because there was already
a paragraph tag of that name in the catalog.
At that point I decided to throw myself on the mercy of the forum.
Cheers,
JP

JP,
Open the file in which you created the H2 tag. In the book file, select all. Then with the book file selected, select File > Import > Formats. In the dialog, deselect all and then select paragraph formats. From the dropdown at the top, select the open file. Click OK, or whatever. This copies all the paragraph formats from the open file into all the selected files of the book. IF an H2 tag already exists in any of the files in the book, it is overwritten. No tags NOT in the open file are deleted.
After failing to make "import format" work, I even tried to re-create the same H2
paragraph from scratch in one of the the other chapters.
But to add insult to injury, after typing in all the custom H2 characteristics in that
other chapter, and attempting to put in the catalog (which was not showing
an H2 in that chapter), FM told me that it couldn't do it because there was already
a paragraph tag of that name in the catalog.
The second paragraph implies that the import format DID work. What do you mean by failing to make import format work?
Van

Unwanted paragraph tag after text inset

Similar Messages

Maybe you are looking for