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.

Similar Messages

Ability to globally delete all text/topics that have a certain conditional tag?

When deleting a conditional tag in FrameMaker, there is an option to either delete all tagged text, or make the text unconditional. But in Robohelp, it seems the only option is to make the text unconditional. Is there any way to delete all the text with a specific conditional tag, other than deleting it manually? I am using Robo 7. Is there an option to do this in the newer versions? Thanks!

If you are bringing in content from FrameMaker and want to delete (not bring) certain content having a conditional text applied in the FM source, then while conversion there is a simple way to achieve it, apply "FrameMaker condition text build Expression" during Import/Link FM source.
If you use this option while you import or Link any FM source with conditions, then all the text/content having condition set as hidden in FrameMaker will get remove from the topics generated
but inside RoboHelp you dont have this option to directly remove content from topic, but while generating any output you have the option to exclude any content with a condition applied over it!
Hope this will help
Ashish

How can I update the path of text insets?

We are starting to include an amount of text insets for FM files.
In this starting period there are changings that happen.
If the name or the path of a text insets change, you have to repeat the
import procedure for every single text inset.
For changes of referenced graphics (path or name) FM has a fine working procedure:
When loading a FM file a message comes up with the uncorrect graphic file. You have
to change the reference and the correction is done.
If you changed the name of the graphic directory you have to change the new name for the
first graphic file and all references will change afterwards automatically.
Both procedures does not work for text insets. My questions:
I'm working with FM 10: Does anybody knows if there is a work-around for me?
Does anybody knows if there are features for processing text insets in FM 12?
Thanks in advance

This is exactly the kind of thing that ExtendScript is made for. I'd say that ES is by far the easiest way, if you know how to use it. This example is but one of many case studies for why scripting knowledge is a big advantage to an FM user.
The following script will go through a whole document and do a search/replace within text inset paths, according the the search and replace strings specified. It is a short, simple script with around 20 lines, and took a short time to write. Compare that with manually changing each inset. It is a perfect example of how a little bit of knowledge can have a huge benefit, both for you the user and the longevity of the FM platform. I encourage anyone to learn more. But before I get out of control, let me just leave it at that and hope that this might be helpful.
Russ
updateTextInsetPaths();
function updateTextInsetPaths()
    var searchString = "some\\path\\string\\to\\change";
    var replaceString = "the\\new\\path\\string";
    var doc = app.ActiveDoc;
    if(!doc.ObjectValid())
        alert("No active document. Cannot continue");
        return;
    var pathsUpdated = 0;
    var inset = doc.FirstTiInDoc;
    while(inset.ObjectValid())
        var path = inset.TiFile;
        path = path.replace(searchString, replaceString);
        inset.TiFile = path;
        pathsUpdated++;
        inset = inset.NextTiInDoc;
    alert("Operation complete. " + pathsUpdated + "path(s) updated.");

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.

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

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

How to retrieve all external refereces in a frame maker file without conditional text of hidden

How to retrieve all external refereces in a frame maker file without conditional text of hidden

Hi, Finally I found the solution of the above problem. Use following interface-function combination. ///////////code start UIDList lst = Utils<IInCopyWorkFlowUtils>()->GetInCopyStories(doc); for(int32 index = 0;index < lst.Length();index++) { UIDRef incopyStory = Utils<IInCopyWorkFlowUtils>()->GetContainingInCopyStory(lst.GetRef(index)); if(incopyStory == UIDRef::gNull) { break; } IDataLink * dLink = Utils<IInCopyBridgeUtils>()->QueryDataLink(incopyStory); if(dLink == nil) { break; } } //////code end

JSP 2.0 tag file with conditional body?

Is it possible to write a tag file that conditionally outputs its body?
For example:
<my:conditionalTag booleanAttr="false">
Since booleanAttr is false, you will never see this output.
</my:conditionalTag>
Thanks,
B

I apologize for the typo..
You can use the Java Standard Tag Library (JSTL), which has a <c:choose> tag with <c:when> or <c:if>. So as you can see with the example above, you are to use the <c:when> tag inside <c:choose> . Here is an example of using <c:if>(notice that you don't need the <c:choose> tag this time):
<c:if test="${true}">
do something
</c:if>
[/code

Batch export text from multiple Indesign files, applying em and strong tags

Hi there,
I am struggling for a while now with the following workflow:
batch exporting all text (text only) as plain text, from multiple Indesign files, applying and for all the bold and italics (for instance: Molluptas verion nossum idist doluptatet maiorerum quiaspienit, cum erferiosapis eos expe nonsequas verumquae dolor sim eos doluptatiur autet lab idicili beatum deliquat).
Properly tagging the styles, will be too time consuming, as these documents are as old as 1998, have inconsistent untagged styles; it will mean to manually open up each file, assign tags for all styles (not to mention that might be some local overwrites).
This task is necessary to have all the archive, available on wordpress website.
Any feedback would be much appreciated it.
Thanks.

There may well be a script or you may have pay someone to write it. All I can tell you is that any text not mapped to a style will be a mess in the HTML code.
Can’t comment on Quark files. I have no clue what they’re capable of.
Bob

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.

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

Text disappearing in pdf when re-ordering tags

I have a pdf (Acrobat 8 Pro), and I have created it as a tagged pdf in InDesign CS3. However, when I convert it to the pdf, the order of the tags changes, so that I need to use the Touchup Reading Order tool. When I do this, however, text disappears. The text in the ID file is in an opaque text box, and what is actually happening when I re-order in Acrobat is that the text is moved behind the opaque box so that it is no longer visible, but it still appears in the Order dialogue box.
However, in ID, they are one object - it is a text box containing text, not a separate opaque box behind the text. Otherwise I might try tagging the box as an artifact and see if that works. Theoretically, I could select it in Acrobat to tag it as an artifact, but the selection tool only allows me to select rectangular areas, and so it selects both the opaque box and the text behind it.
Any suggestions?
Win XP

I have run into this problem myself. I have been able to use the object selection tool (In Acrobat 8 Pro) to select the box in front of the text and delete it without also deleting the text.

How load text into dynamic text boxes from external file?

hi all,
my animation is very simple - a background image and 2 text boxes. one of the textboxes shows a large word, which crossfades to another word, with a total of about 12 words (showing one at a time in different text boxes fading in & out in the same spot).
i need a way to have the text be imported dynamically via xml or json (xml preferred). this article is a good start, but i noticed he's putting all of the text into one box - i need separate strings put into separate boxes from the xml.
Chris Gannon - Loading XML via AJAX into Adobe Edge
he uses
var outputField = $(this.lookupSelector(“xmlOutput”));
for his text box. what would be the best way to revise this code to include all my individual strings to be loaded into my individual text boxes? thinking an array might work, but my js skills are limited.
any other suggestions or tutorials you could point me to would be appreciated.
thanks!!

thanks joel_pau !
this is helpful in seeing how the array is created, but after giving it a go I became a little confused.
i wound up trying it again based on the example i linked out to previously, but it's not adding the text from my xml file when previewing.
here's the code i'm using in edge animate on my stage. something must be wrong somewhere. let me know if you have any suggestions on this.
// insert code to be run when the composition is fully loaded here
// here i'm assigning a variable to each one of my textboxes at they're named in my edge animate comp
var outputField1 = $(this.lookupSelector("helps2"));
var outputField2 = $(this.lookupSelector("communicate"));
var outputField3 = $(this.lookupSelector("experience"));
var outputField4 = $(this.lookupSelector("interact"));
var outputField5 = $(this.lookupSelector("understand"));
var outputField6 = $(this.lookupSelector("overcome"));
var outputField7 = $(this.lookupSelector("flourish"));
var outputField8 = $(this.lookupSelector("collab"));
var outputField9 = $(this.lookupSelector("trust"));
var outputField10 = $(this.lookupSelector("grow"));
var outputField11 = $(this.lookupSelector("engage"));
var outputField12 = $(this.lookupSelector("survive"));
var outputField13 = $(this.lookupSelector("thrive"));
var outputField14 = $(this.lookupSelector("evolve"));
var outputField15 = $(this.lookupSelector("connect"));
var outputField16 = $(this.lookupSelector("achieve"));
$.ajax({
    type: "GET",
    url: "myxmlfile.xml",
    dataType: "xml",
    success: function(xml) {
//here i'm trying to load the the text in my xml file into my textboxes in edge animate. 'txt1, txt2, txt3' are the tags in my xml file
        outputField1 = $(xml).find('txt1').text();
        outputField2 = $(xml).find('txt2').text();
        outputField3 = $(xml).find('txt3').text();
        outputField4 = $(xml).find('txt4').text();
        outputField5 = $(xml).find('txt5').text();
        outputField6 = $(xml).find('txt6').text();
        outputField7 = $(xml).find('txt7').text();
        outputField8 = $(xml).find('txt8').text();
        outputField9 = $(xml).find('txt9').text();
        outputField10 = $(xml).find('txt10').text();
        outputField11 = $(xml).find('txt11').text();
        outputField12 = $(xml).find('txt12').text();
        outputField13 = $(xml).find('txt13').text();
        outputField14 = $(xml).find('txt14').text();
        outputField15 = $(xml).find('txt15').text();
        outputField16 = $(xml).find('txt16').text();
but nothing happens on preview. my textboxes still contain the original text that lives in my comp.

Searching for content in text insets

In a FrameMaker book, is there a way to search all the text insets in a book without opening each individual inset?
I'm working on a project that has more than 30 text insets. I'd like to search for certain terms without having to open each inset. I'm using FrameMaker 11.

Not really, as FM won't search the inset content directly. You could try creating an auxiliary book that contains just the inset files and use the Find function on that book. You can also add this book to your main book and mark it with Exclude so it doesn't get output, but still provides access to everything from the main book file.

FM 9: Cannot apply conditional tags

I've been able to create conditional text tags, apply them, and see the conditional indicators fine in several documents using FM 9. Recently, in a new book, I'm unable to apply conditional tags. I believe I've figured out the new UI, since conditional tagging has worked before. I can create tags and configure them fine, but when I apply them to text, a table, graphic, etc. nothing happens; the text remains unconditional.

What specific version of FM, as shown in Help > About? What O/S and service pack level?
Does FM's built-in Comment condition work for you?
As a test, I'd suggest creating a small test file, create a new condition and apply it to some easily searchable text, e.g. "zzxy" or something, and also apply FM's built-in "Comment" condition to another piece of text, then saving the file as MIF. Then look at the MIF with a text editor, or the excellent freebie MIFBrowser,
http://www.wideman-one.com/gw/tech/framemaker/mifbrowse.htm
and search for the text. You should be able to see whether the condition(s) have been applied to the text correctly (or not), and also see how the conditions themselves are defined in the Condition Catalog entries.
Sheila

Text Inset in Container File Loses Conditional Tag

Similar Messages

Maybe you are looking for