<HTML >
<HEAD>
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></HEAD><BODY lang=EN-US link=blue vlink=purple><DIV><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>I don’t know if I badly explained my own thinking or if I misunderstood the suggested procedure. <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>When I mentioned a “master” document, I originally envisioned it as one big doc into which would be imported all text inset files. However, they would NOT be imported to other files FROM this file – this is just a master dump file for the purpose of holding metadata that could be searched when writers want TI files to use.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>After reading the idea of text flows, I put the four lines of metadata into a separate text frame at the start of the TI template file (from which each TI file will be made) and I named that flow tag “Metadata”. Then I imported each TI file, one at a time, into the “master” file and when prompted which text flow tag to import, I selected “Metadata”. The result was just what I wanted: a .fm file containing ONLY the metadata.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>I was afraid having the small Metadata text flow frame in the corner of my main Flow Tag A would cause problems and some of your comments seem to bear this out, so I’m experimenting with putting that little text frame in a margin, outside Flow Tag A. So far, it doesn’t seem to pose a problem.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>I still feel that Flow Tag A should be left alone as the container for the main TI file – it’s connected so pages continue as they should. Then the few lines of metadata are in a separate area that can be imported into the “master” (dump) file. It’s the only time this text flow will ever be used, and since the text in this small frame has a condition tag applied that is routinely hidden, the “real” TI file can be edited, imported where needed, etc., with no real change to existing TI functionality.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>At least, that’s my theory!<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Many thanks – as always – to you folks who so willingly give of your time and ideas. This list is a fantastic resource.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>~~Gay<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Fred Ridder [mailto:docudoc@hotmail.com] <br><b>Sent:</b> Thursday, August 04, 2011 11:50 AM<br><b>To:</b> Gay Alson; rshuttleworth@avbasesystems.com<br><b>Cc:</b> framers@lists.frameusers.com<br><b>Subject:</b> RE: Any way to hide unconditional text?<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>Gay Alson wrote:<br> <o:p></o:p></span></p><div><div><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>You mentioned putting each text inset file in a different flow, up to 256. But as we may end up with several hundred text inset files over time, it occurred to me to try it the other way ‘round: That is, to see if the main contents of each text inset file could remain in Flow Tag A, with only the four-line metadata in a separate flow. (Which means dealing only with two text flows instead of many.) That’s what I tried and it does work, at least in my first experiments. Can you think of any reason NOT to continue with that? I also wasn’t sure about where to place the new text frame containing the Metadata Flow Tag, so I inserted it in the upper left of my regular Flow A. I had my doubts whether FM would permit a text flow within the frame of the larger Flow A but it seems to be okay.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>No, this will *not* work for your purposes. When you reference a text inset file from a "container" file, you specify which flow to import from. If all the content chunks are in Flow A, then all you will ever be able to do is include *all* the content chunks each time you do an insert from that TI file. The whole point of putting the content chunks in separate, named flows is to be able to reference them as separate content objects. It doesn't matter if all your meta-data text is in the same flow, because you will never need to insert those chunks individually into another document.</span><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>-Fred Ridder</span><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'><o:p></o:p></span></p></div></div></div></div><p class=MsoNormal style='margin-bottom:12.0pt'><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";background:white'><o:p> </o:p></span></p><p class=MsoNormal align=center style='text-align:center'><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";background:white'>Click <a href="https://www.mailcontrol.com/sr/wQw0zmjPoHdJTZGyOCrrhg==">here</a> to report this email as spam.<o:p></o:p></span></p></div></DIV>
<DIV>
<HR>
</DIV>
<DIV STYLE="FONT-SIZE: 7pt; COLOR: gray; FONT-FAMILY: verdana">
<DIV STYLE="FONT-SIZE: 9pt; FONT-FAMILY: Courier New">
<FONT FACE="Verdana" COLOR="gray" SIZE="1">This e-mail is for the use of the intended recipient(s) only. If you have received this e-mail in error, please notify the sender immediately and then delete it. If you are not the intended recipient, you must not use, disclose or distribute this e-mail without the author's prior permission. We have taken precautions to minimize the risk of transmitting software viruses, but we advise you to carry out your own virus checks on any attachment to this message. We cannot accept liability for any loss or damage caused by software viruses.</FONT>
</DIV>
<DIV STYLE="FONT-SIZE: 9pt; FONT-FAMILY: Courier New"> </DIV>
<DIV STYLE="FONT-SIZE: 9pt; FONT-FAMILY: Courier New">
<FONT FACE="Verdana" COLOR="gray" SIZE="1">Le présent courriel est envoyé à l’intention exclusive de son ou de ses destinataires. Si vous avez reçu ce courriel par erreur, veuillez en aviser immédiatement l’expéditeur et supprimer ce message. Si vous n’êtes pas le destinataire visé, nous vous informons que toute utilisation, divulgation ou distribution de cette communication est strictement interdite sans la permission préalable de l’auteur. Des précautions ont été prises afin de réduire au maximum le risque de transmission de virus informatique, mais nous tenons à vous conseiller de procéder à vos propres vérifications antivirus de toute pièce jointe à ce message. Aucune responsabilité ne sera assumée à la suite de toute perte ou de tout dommage causés par des virus.</FONT>
</DIV>
</DIV><br><br>
<P align=center><FONT style="BACKGROUND-COLOR: #ffffff">This message has been scanned for malware by Websense. </FONT><A href="http://www.websense.com/"><FONT style="BACKGROUND-COLOR: #ffffff" color=#000000>www.websense.com</FONT></A></P>
</body></HTML>