style following inset
Thanks to all for sharing your solutions. The general consensus is that containing the spacing in the inset not only works but is expedient. I will implement and include with new user training. Again, thanks for all you kind responses. Mollye Mollye Barrett, ClearPath, LLC content management solutions 414-331-1378 (cell)
RE: style following inset
Thanks to all for sharing your solutions. The general consensus is that containing the spacing in the inset not only works but is expedient. I will implement and include with new user training. Again, thanks for all you kind responses. Mollye Mollye Barrett, ClearPath, LLC content management solutions 414-331-1378 (cell) ___ You are currently subscribed to Framers as [EMAIL PROTECTED] Send list messages to [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] or visit http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com Send administrative questions to [EMAIL PROTECTED] Visit http://www.frameusers.com/ for more resources and info.
style following inset
Hi Mollye, Just catching up on my digest version, so pardon the late response. The solution outlined by Richard Combs is an effective one, and there is also one more alternative: Create a new paragraph tag from your standard body paragraph tag and name it, for example, "TI.Start." Configure it so that it has a 2 pt. font size, and Above Pgf, Below Pgf, and Line Spacing are all set to 0 points. Ensure that every text inset begins with a TI.Start paragraph (with no content, obviously). This does not remove the "empty paragraph" but sets it to an empty, 2 pt paragraph with zero spacing, effectively removing it from view. This has the advantage of keeping the solution in the text inset itself, and removes the need to remember to insert content after the text inset - more of a "set and forget" solution. Of course, you have to remember to keep it in the text inset, but if you create a text inset template, you can set it up so it appears as the first line in the flow, followed by a standard body paragraph tag. You only need to create the new TI.Start tag in the text inset template - it does not have to become part of your standard template. When you import the text inset, it will show up in the style list as "*TI.Start." Regards, Keith Arnett Lead Technical Writer Software AG USA, Inc. \ Fairfax VA -Original Message- Date: Thu, 21 Feb 2008 09:30:28 -0700 From: "Combs, Richard" Subject: RE: style following inset To: , Mollye Barrett wrote: >> I'm working with an unstructured document set that uses text >> insets. When insets are imported into the target document, >> the empty paragraph tag following the inset automatically >> becomes a repeat of the first style in the previous inset. >> So, if the inset starts with a numbered list, the next empty >> paragraph tag in the document becomes a number list too. > That "empty" pgf isn't really empty. It's the _container_ pgf into which > you imported the text inset. If you click the inset to select it, you'll > see from the highlighting that it sits in that pgf. There's an _extra_ > pgf break because the text inset itself ends with a paragraph break. > > Enough context. The fix is simple: Put something -- anything -- between > the text inset and the end of its container pgf. > > For existing text insets, position the cursor between the the text inset > and the pilcrow (end-of-pgf symbol) of the container pgf and type > something. I use a non-breaking space (Ctrl-Space) so that there's a > little symbol there (I always work with View > Symbols on), and it's > less likely to be accidentally deleted. Change the pgf format to > whatever you want (I have a special format I use as a text inset > container) and update the text inset. The container pgf remains > unchanged. > > For a new text inset, if the text cursor is in an empty pgf when you > import the inset, the inset will "sit" up against the pilcrow and cause > your problem. Type the Ctrl-Space first, then move the cursor to the > left of it before importing the inset. Or consider importing the inset > with the cursor at the beginning of a non-empty pgf (i.e., to the left > of some text). > > HTH! > Richard
RE: style following inset
Hi Mollye, Just catching up on my digest version, so pardon the late response. The solution outlined by Richard Combs is an effective one, and there is also one more alternative: Create a new paragraph tag from your standard body paragraph tag and name it, for example, "TI.Start." Configure it so that it has a 2 pt. font size, and Above Pgf, Below Pgf, and Line Spacing are all set to 0 points. Ensure that every text inset begins with a TI.Start paragraph (with no content, obviously). This does not remove the "empty paragraph" but sets it to an empty, 2 pt paragraph with zero spacing, effectively removing it from view. This has the advantage of keeping the solution in the text inset itself, and removes the need to remember to insert content after the text inset - more of a "set and forget" solution. Of course, you have to remember to keep it in the text inset, but if you create a text inset template, you can set it up so it appears as the first line in the flow, followed by a standard body paragraph tag. You only need to create the new TI.Start tag in the text inset template - it does not have to become part of your standard template. When you import the text inset, it will show up in the style list as "*TI.Start." Regards, Keith Arnett Lead Technical Writer Software AG USA, Inc. \ Fairfax VA -Original Message- Date: Thu, 21 Feb 2008 09:30:28 -0700 From: "Combs, Richard" <[EMAIL PROTECTED]> Subject: RE: style following inset To: <[EMAIL PROTECTED]>, Mollye Barrett wrote: >> I'm working with an unstructured document set that uses text >> insets. When insets are imported into the target document, >> the empty paragraph tag following the inset automatically >> becomes a repeat of the first style in the previous inset. >> So, if the inset starts with a numbered list, the next empty >> paragraph tag in the document becomes a number list too. > That "empty" pgf isn't really empty. It's the _container_ pgf into which > you imported the text inset. If you click the inset to select it, you'll > see from the highlighting that it sits in that pgf. There's an _extra_ > pgf break because the text inset itself ends with a paragraph break. > > Enough context. The fix is simple: Put something -- anything -- between > the text inset and the end of its container pgf. > > For existing text insets, position the cursor between the the text inset > and the pilcrow (end-of-pgf symbol) of the container pgf and type > something. I use a non-breaking space (Ctrl-Space) so that there's a > little symbol there (I always work with View > Symbols on), and it's > less likely to be accidentally deleted. Change the pgf format to > whatever you want (I have a special format I use as a text inset > container) and update the text inset. The container pgf remains > unchanged. > > For a new text inset, if the text cursor is in an empty pgf when you > import the inset, the inset will "sit" up against the pilcrow and cause > your problem. Type the Ctrl-Space first, then move the cursor to the > left of it before importing the inset. Or consider importing the inset > with the cursor at the beginning of a non-empty pgf (i.e., to the left > of some text). > > HTH! > Richard ___ You are currently subscribed to Framers as [EMAIL PROTECTED] Send list messages to [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] or visit http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com Send administrative questions to [EMAIL PROTECTED] Visit http://www.frameusers.com/ for more resources and info.
RE: style following inset
Mollye, Try the following: In the text inset, insert empty paragraph above the text. Create the paragraph tag with a small font size (2pt), 0 spacing above and below, and import tag into the book files. Insert the text inset into the book file at an empty paragraph below the previous paragraph. The empty paragraph takes on the format of that first empty paragraph in the text inset. Regards, Joe -Original Message- Date: Thu, 21 Feb 2008 10:03:32 -0600 (CST) From: "Mollye Barrett" <[EMAIL PROTECTED]> Subject: style following inset To: framers@lists.frameusers.com Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain;charset=iso-8859-1 I'm working with an unstructured document set that uses text insets. When insets are imported into the target document, the empty paragraph tag following the inset automatically becomes a repeat of the first style in the previous inset. So, if the inset starts with a numbered list, the next empty paragraph tag in the document becomes a number list too. I know this will go away when and if the documents are structured but that is not an option right now. Can anyone recommend best practices for handling unstructured insets and/or specifically how to resolve this unwelcome problem. I seem to recall a fix but I haven't been faced with this problem for a long time. Any help is truly appreciated! Mollye Barrett ClearPath, LLC 414-331-1378 -- Message: 10 Date: Thu, 21 Feb 2008 09:07:34 -0700 From: "Grant Hogarth" <[EMAIL PROTECTED]> Subject: RE: SYSTEC Toolbox & Deleting unused conditions throughout a book To: "Linda G. Gallagher" <[EMAIL PROTECTED]>, Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset="us-ascii" My apologies --- it would appear that you are correct, and that I misrepresented the product. *sigh* It works so well for all the other entities, I did not think to confirm that it handled conditions. It appears that the version for FM8 *does* handle conditions, but I can't swear to it. "My bad" as the expression goes. Grant -Original Message- From: Linda G. Gallagher [mailto:[EMAIL PROTECTED] Sent: Thursday, February 21, 2008 8:56 AM To: Grant Hogarth; framers@lists.frameusers.com Subject: RE: Deleting unused conditions throughout a book Hmm. It doesn't say that it handles conditions on the sit, and a copy I have for FM 7.0 does not. I did try to order it. I keep going around in circles, though, in the ordering process and just sent an email to their customer support. Does it really handle conditions? ~ Linda G. Gallagher TechCom Plus, LLC lindag at techcomplus dot com www.techcomplus.com 303-450-9076 or 800-500-3144 User guides, online help, FrameMaker and WebWorks ePublisher templates -Original Message- From: Grant Hogarth [mailto:[EMAIL PROTECTED] Sent: Thursday, February 21, 2008 8:22 AM To: Linda G. Gallagher; framers@lists.frameusers.com Subject: RE: Deleting unused conditions throughout a book Toolbox from SYSTEC SystemHaus will do that --- and much more. (I've no association with them other than as a very satisfied customer) www.systec-gmbh.com/toolbox Grant --- Grant Hogarth Senior Technical Writer Equis International - A Reuters Company +1 801 270 3180 (t) | +1 801 815 8353 (m) | +1 801 265 3999 (f) Email: [EMAIL PROTECTED] URL: www.equis.com TZ: Mountain (GMT +7) Reuters news and information reaches one billion people every day. Get the latest news at Reuters.com -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Linda G. Gallagher Sent: Thursday, February 21, 2008 7:20 AM To: framers@lists.frameusers.com Subject: Deleting unused conditions throughout a book Framers, I'm just full of questions this week. I found Pgf Whopper, which lets me find and delete unused conditions on a file basis, but I'd like to know if there's a way to find and delete them throughout an entire book. My client has about 20 books and tons of conditions, many seemingly unused. The system I'm working on doesn't have FrameScript, so it's not an option right now, but might be in the future. Thanks again! ~ Linda G. Gallagher TechCom Plus, LLC lindag at techcomplus dot com www.techcomplus.com 303-450-9076 or 800-500-3144 User guides, online help, FrameMaker and WebWorks ePublisher templates ___ You are currently subscribed to Framers as [EMAIL PROTECTED] Send list messages to [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] or visit http://lists.frameusers.com/mailman/options/framers/gr
RE: style following inset
Put a tiny empty paragraph at the very beginning of the file/document that you are 'insetting' Regards, Micheal O'Laoghaire CBS Documentation Comverse Inc. Cambridge, MA. Tel: (617) 273-5414 -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mollye Barrett Sent: Thursday, February 21, 2008 11:04 AM To: framers@lists.frameusers.com Subject: style following inset I'm working with an unstructured document set that uses text insets. When insets are imported into the target document, the empty paragraph tag following the inset automatically becomes a repeat of the first style in the previous inset. So, if the inset starts with a numbered list, the next empty paragraph tag in the document becomes a number list too. I know this will go away when and if the documents are structured but that is not an option right now. Can anyone recommend best practices for handling unstructured insets and/or specifically how to resolve this unwelcome problem. I seem to recall a fix but I haven't been faced with this problem for a long time. Any help is truly appreciated! Mollye Barrett ClearPath, LLC 414-331-1378 ___ You are currently subscribed to Framers as [EMAIL PROTECTED] Send list messages to [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] or visit http://lists.frameusers.com/mailman/options/framers/micheal.olaoghaire%4 0comverse.com Send administrative questions to [EMAIL PROTECTED] Visit http://www.frameusers.com/ for more resources and info. ___ You are currently subscribed to Framers as [EMAIL PROTECTED] Send list messages to [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] or visit http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com Send administrative questions to [EMAIL PROTECTED] Visit http://www.frameusers.com/ for more resources and info.
style following inset
Mollye, Try the following: In the text inset, insert empty paragraph above the text. Create the paragraph tag with a small font size (2pt), 0 spacing above and below, and import tag into the book files. Insert the text inset into the book file at an empty paragraph below the previous paragraph. The empty paragraph takes on the format of that first empty paragraph in the text inset. Regards, Joe -Original Message- Date: Thu, 21 Feb 2008 10:03:32 -0600 (CST) From: "Mollye Barrett" Subject: style following inset To: framers at lists.frameusers.com Message-ID: <36631.67.52.221.170.1203609812.squirrel at www.itobin.com> Content-Type: text/plain;charset=iso-8859-1 I'm working with an unstructured document set that uses text insets. When insets are imported into the target document, the empty paragraph tag following the inset automatically becomes a repeat of the first style in the previous inset. So, if the inset starts with a numbered list, the next empty paragraph tag in the document becomes a number list too. I know this will go away when and if the documents are structured but that is not an option right now. Can anyone recommend best practices for handling unstructured insets and/or specifically how to resolve this unwelcome problem. I seem to recall a fix but I haven't been faced with this problem for a long time. Any help is truly appreciated! Mollye Barrett ClearPath, LLC 414-331-1378 -- Message: 10 Date: Thu, 21 Feb 2008 09:07:34 -0700 From: "Grant Hogarth" Subject: RE: SYSTEC Toolbox & Deleting unused conditions throughout a book To: "Linda G. Gallagher" , Message-ID: Content-Type: text/plain; charset="us-ascii" My apologies --- it would appear that you are correct, and that I misrepresented the product. *sigh* It works so well for all the other entities, I did not think to confirm that it handled conditions. It appears that the version for FM8 *does* handle conditions, but I can't swear to it. "My bad" as the expression goes. Grant -Original Message- From: Linda G. Gallagher [mailto:lin...@techcomplus.com] Sent: Thursday, February 21, 2008 8:56 AM To: Grant Hogarth; framers at lists.frameusers.com Subject: RE: Deleting unused conditions throughout a book Hmm. It doesn't say that it handles conditions on the sit, and a copy I have for FM 7.0 does not. I did try to order it. I keep going around in circles, though, in the ordering process and just sent an email to their customer support. Does it really handle conditions? ~ Linda G. Gallagher TechCom Plus, LLC lindag at techcomplus dot com www.techcomplus.com 303-450-9076 or 800-500-3144 User guides, online help, FrameMaker and WebWorks ePublisher templates -Original Message- From: Grant Hogarth [mailto:grant.hoga...@reuters.com] Sent: Thursday, February 21, 2008 8:22 AM To: Linda G. Gallagher; framers at lists.frameusers.com Subject: RE: Deleting unused conditions throughout a book Toolbox from SYSTEC SystemHaus will do that --- and much more. (I've no association with them other than as a very satisfied customer) www.systec-gmbh.com/toolbox Grant --- Grant Hogarth Senior Technical Writer Equis International - A Reuters Company +1 801 270 3180 (t) | +1 801 815 8353 (m) | +1 801 265 3999 (f) Email: grant.hogarth at reuters.com URL: www.equis.com TZ: Mountain (GMT +7) Reuters news and information reaches one billion people every day. Get the latest news at Reuters.com -Original Message- From: framers-boun...@lists.frameusers.com [mailto:framers-bounces at lists.frameusers.com] On Behalf Of Linda G. Gallagher Sent: Thursday, February 21, 2008 7:20 AM To: framers at lists.frameusers.com Subject: Deleting unused conditions throughout a book Framers, I'm just full of questions this week. I found Pgf Whopper, which lets me find and delete unused conditions on a file basis, but I'd like to know if there's a way to find and delete them throughout an entire book. My client has about 20 books and tons of conditions, many seemingly unused. The system I'm working on doesn't have FrameScript, so it's not an option right now, but might be in the future. Thanks again! ~ Linda G. Gallagher TechCom Plus, LLC lindag at techcomplus dot com www.techcomplus.com 303-450-9076 or 800-500-3144 User guides, online help, FrameMaker and WebWorks ePublisher templates ___ You are currently subscribed to Framers as Grant.Hogarth at reuters.com. Send list messages to framers at lists.frameusers.com. To unsubscribe send a blank email to framers-unsubscribe at lists.frameusers.com or visit http://lists
style following inset
In response to Rene Stephenson, Richard Combs wrote (in part):> A flow always contains one or more pgfs. So a one-sentence flow is also > a one-pgf flow; you can't avoid the pgf end. But you should be able to > (I haven't tried it) define the source pgf as a Run-In Head so that > there's no break after it. > > Here's another idea: Save your sentence as a text file and import that > by reference. In the Import Text File by Reference dialog, select Merge > Lines into Paragraphs. FM inserts the entire sentence at the cursor > location, and it assumes the formatting of the container pgf. It's actually much easier (and better) than that! What you need to do is select the "Reformat as Plain Text" option in the Import Text Flow by Reference dialog. As long as the source flow contains only an end-of- flow mark (i.e. does not contain a paragraph mark), the text will be imported into your target document as a plain text string, without any end-of-flow mark. This means you can put sub-paragraph insets *anywhere*, even multiple ones in the same paragraph. The only shortcoming of this approach is that you can't bring along any ormatting; the inset only contains plain text, but you *can* format the whole inset in the container doc. At my last employer, I implemented this kind of system for the titles of all the books in our System Release Bookshelf (about 50 titles), and all writers were supposed to use text insets rather typing the titles so that everybody's references would stay in sync when any of the titles changed. We just had to apply the "TitleRef" character tag to italicize the titles after performing the insert. Another point to note if you are dealing with short insets is that they do not always have to be in separate files. My system used a multi-flow source document that had all 50 book titles in separately defined, named text flows. Just remember to keep the flow names short unless you feel like using Resource Editor to make the list box wider in the Import Flow dialog. -Fred Ridder _ Helping your favorite cause is as easy as instant messaging.?You IM, we give. http://im.live.com/Messenger/IM/Home/?source=text_hotmail_join
style following inset
Hi Mollye, Just make sure that the paragraph which follows the text inset is not empty (if possible). If this option is not possible, for example, if the text inset is at the end of your text flow, you can do this: 1. Put a new paragraph after the text inset. 2. In this paragraph, type a single character, for example a full stop. 3. Create a dedicated paratag, for example "eoti", meaning "end of text inset" with the Color set to White in the Para Designer. 4. Apply this paratag to the paragraph with the single character. 5. Update the text inset to test it. If you also generate WebHelp or HTMLHelp output of this FM file, make sure that you set this paratag (eoti) to No Output. Good luck. Yves Barbion Documentation Architect Adobe-Certified FrameMaker Instructor Scripto Belgium Mollye Barrett wrote: > I'm working with an unstructured document set that uses text insets. When > insets are imported into the target document, the empty paragraph tag > following the inset automatically becomes a repeat of the first style in > the previous inset. So, if the inset starts with a numbered list, the next > empty paragraph tag in the document becomes a number list too. > > I know this will go away when and if the documents are structured but that > is not an option right now. Can anyone recommend best practices for > handling unstructured insets and/or specifically how to resolve this > unwelcome problem. I seem to recall a fix but I haven't been faced with > this problem for a long time. > > Any help is truly appreciated! > > > Mollye Barrett > ClearPath, LLC > 414-331-1378 > ___ > > > You are currently subscribed to Framers as yves.barbion at gmail.com. > > Send list messages to framers at lists.frameusers.com. > > To unsubscribe send a blank email to > framers-unsubscribe at lists.frameusers.com > or visit > http://lists.frameusers.com/mailman/options/framers/yves.barbion%40gmail.com > > Send administrative questions to listadmin at frameusers.com. Visit > http://www.frameusers.com/ for more resources and info. > >
style following inset
Rene Stephenson wrote: > OK, bear with me - What about the situation where you have a > text inset that's just a sentence, and there's no trailing > paragraph break in the inset, and you want to use the > sentence mid-paragraph elsewhere? I can't seem to get the > inset sentence to flow to the next sentence without a > paragraph break showing up in the container doc that's not in > the inset. It's like the file end character (that doubled-S > squiggle thing) makes FM put a paragraph break there > regardless of what I put after the inset marker. Is that just > functioning as designed, and I'm not supposed to be able to > use an inset that way? (...in which case, maybe a user > variable is a better answer if it's just a sentence we need > to reuse mid-paragraph...?) The squiggle thing is an end-of-flow symbol. A text inset is never just a sentence, it's always an entire flow (of course, there may have only one sentence -- or word -- in the flow). When the source is an FM file, this is explicit in the dialog box, Import Text Flow by Reference, where you can select which flow in the source doc to import. A flow always contains one or more pgfs. So a one-sentence flow is also a one-pgf flow; you can't avoid the pgf end. But you should be able to (I haven't tried it) define the source pgf as a Run-In Head so that there's no break after it. Here's another idea: Save your sentence as a text file and import that by reference. In the Import Text File by Reference dialog, select Merge Lines into Paragraphs. FM inserts the entire sentence at the cursor location, and it assumes the formatting of the container pgf. > How about when you have the inset preceding a paragraph of > body text, and the last paragraph of the inset is supposed to > be a numbered list, but the numbering won't hold if you > follow the text inset with anything other than a numbered list? Now, that one I've never seen. Sorry, I don't have a clue; that shouldn't happen. :-( Richard -- Richard G. Combs Senior Technical Writer Polycom, Inc. richardDOTcombs AT polycomDOTcom 303-223-5111 -- rgcombs AT gmailDOTcom 303-777-0436 --
RE: style following inset
In response to Rene Stephenson, Richard Combs wrote (in part):> A flow always contains one or more pgfs. So a one-sentence flow is also > a one-pgf flow; you can't avoid the pgf end. But you should be able to > (I haven't tried it) define the source pgf as a Run-In Head so that > there's no break after it. > > Here's another idea: Save your sentence as a text file and import that > by reference. In the Import Text File by Reference dialog, select Merge > Lines into Paragraphs. FM inserts the entire sentence at the cursor > location, and it assumes the formatting of the container pgf. It's actually much easier (and better) than that! What you need to do is select the "Reformat as Plain Text" option in the Import Text Flow by Reference dialog. As long as the source flow contains only an end-of- flow mark (i.e. does not contain a paragraph mark), the text will be imported into your target document as a plain text string, without any end-of-flow mark. This means you can put sub-paragraph insets *anywhere*, even multiple ones in the same paragraph. The only shortcoming of this approach is that you can't bring along any ormatting; the inset only contains plain text, but you *can* format the whole inset in the container doc. At my last employer, I implemented this kind of system for the titles of all the books in our System Release Bookshelf (about 50 titles), and all writers were supposed to use text insets rather typing the titles so that everybody's references would stay in sync when any of the titles changed. We just had to apply the "TitleRef" character tag to italicize the titles after performing the insert. Another point to note if you are dealing with short insets is that they do not always have to be in separate files. My system used a multi-flow source document that had all 50 book titles in separately defined, named text flows. Just remember to keep the flow names short unless you feel like using Resource Editor to make the list box wider in the Import Flow dialog. -Fred Ridder _ Helping your favorite cause is as easy as instant messaging. You IM, we give. http://im.live.com/Messenger/IM/Home/?source=text_hotmail_join ___ You are currently subscribed to Framers as [EMAIL PROTECTED] Send list messages to [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] or visit http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com Send administrative questions to [EMAIL PROTECTED] Visit http://www.frameusers.com/ for more resources and info.
RE: style following inset
Rene Stephenson wrote: > OK, bear with me - What about the situation where you have a > text inset that's just a sentence, and there's no trailing > paragraph break in the inset, and you want to use the > sentence mid-paragraph elsewhere? I can't seem to get the > inset sentence to flow to the next sentence without a > paragraph break showing up in the container doc that's not in > the inset. It's like the file end character (that doubled-S > squiggle thing) makes FM put a paragraph break there > regardless of what I put after the inset marker. Is that just > functioning as designed, and I'm not supposed to be able to > use an inset that way? (...in which case, maybe a user > variable is a better answer if it's just a sentence we need > to reuse mid-paragraph...?) The squiggle thing is an end-of-flow symbol. A text inset is never just a sentence, it's always an entire flow (of course, there may have only one sentence -- or word -- in the flow). When the source is an FM file, this is explicit in the dialog box, Import Text Flow by Reference, where you can select which flow in the source doc to import. A flow always contains one or more pgfs. So a one-sentence flow is also a one-pgf flow; you can't avoid the pgf end. But you should be able to (I haven't tried it) define the source pgf as a Run-In Head so that there's no break after it. Here's another idea: Save your sentence as a text file and import that by reference. In the Import Text File by Reference dialog, select Merge Lines into Paragraphs. FM inserts the entire sentence at the cursor location, and it assumes the formatting of the container pgf. > How about when you have the inset preceding a paragraph of > body text, and the last paragraph of the inset is supposed to > be a numbered list, but the numbering won't hold if you > follow the text inset with anything other than a numbered list? Now, that one I've never seen. Sorry, I don't have a clue; that shouldn't happen. :-( Richard -- Richard G. Combs Senior Technical Writer Polycom, Inc. richardDOTcombs AT polycomDOTcom 303-223-5111 -- rgcombs AT gmailDOTcom 303-777-0436 -- ___ You are currently subscribed to Framers as [EMAIL PROTECTED] Send list messages to [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] or visit http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com Send administrative questions to [EMAIL PROTECTED] Visit http://www.frameusers.com/ for more resources and info.
Re: style following inset
OK, bear with me - What about the situation where you have a text inset that's just a sentence, and there's no trailing paragraph break in the inset, and you want to use the sentence mid-paragraph elsewhere? I can't seem to get the inset sentence to flow to the next sentence without a paragraph break showing up in the container doc that's not in the inset. It's like the file end character (that doubled-S squiggle thing) makes FM put a paragraph break there regardless of what I put after the inset marker. Is that just functioning as designed, and I'm not supposed to be able to use an inset that way? (...in which case, maybe a user variable is a better answer if it's just a sentence we need to reuse mid-paragraph...?) How about when you have the inset preceding a paragraph of body text, and the last paragraph of the inset is supposed to be a numbered list, but the numbering won't hold if you follow the text inset with anything other than a numbered list? Rene L. Stephenson - Original Message From: "Combs, Richard" <[EMAIL PROTECTED]> To: Rene Stephenson <[EMAIL PROTECTED]>; [EMAIL PROTECTED]; framers@lists.frameusers.com Sent: Thursday, February 21, 2008 1:22:54 PM Subject: RE: style following inset Rene Stephenson > We have the same problem and have heard it's just a bug w/ FM > 7.2 unstructured insets. Our solution is to use Silicon > Prairie's Paragraph Tools to Remove Paragraph Overrides > immediately before generating the book for our output formats. It's not a bug specific to 7.2, this behavior has existed forever. I suspect it's related to the bug that produces a pgf override when a char format abuts up against the pilcrow (end-of-pgf marker). There's no need for tools or repeated fixes. See my earlier post about separating the text inset from the pilcrow with a space (or something). That will eliminate the problem once and for all. Richard -- Richard G. Combs Senior Technical Writer Polycom, Inc. richardDOTcombs AT polycomDOTcom 303-223-5111 -- rgcombs AT gmailDOTcom 303-777-0436 -- ___ You are currently subscribed to Framers as [EMAIL PROTECTED] Send list messages to [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] or visit http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com Send administrative questions to [EMAIL PROTECTED] Visit http://www.frameusers.com/ for more resources and info.
style following inset
OK, bear with me - What about the situation where you have a text inset that's just a sentence, and there's no trailing paragraph break in the inset, and you want to use the sentence mid-paragraph elsewhere? I can't seem to get the inset sentence to flow to the next sentence without a paragraph break showing up in the container doc that's not in the inset. It's like the file end character (that doubled-S squiggle thing) makes FM put a paragraph break there regardless of what I put after the inset marker. Is that just functioning as designed, and I'm not supposed to be able to use an inset that way? (...in which case, maybe a user variable is a better answer if it's just a sentence we need to reuse mid-paragraph...?) How about when you have the inset preceding a paragraph of body text, and the last paragraph of the inset is supposed to be a numbered list, but the numbering won't hold if you follow the text inset with anything other than a numbered list? Rene L. Stephenson - Original Message From: "Combs, Richard" To: Rene Stephenson ; mollye at clearpath.cc; framers at lists.frameusers.com Sent: Thursday, February 21, 2008 1:22:54 PM Subject: RE: style following inset Rene Stephenson > We have the same problem and have heard it's just a bug w/ FM > 7.2 unstructured insets. Our solution is to use Silicon > Prairie's Paragraph Tools to Remove Paragraph Overrides > immediately before generating the book for our output formats. It's not a bug specific to 7.2, this behavior has existed forever. I suspect it's related to the bug that produces a pgf override when a char format abuts up against the pilcrow (end-of-pgf marker). There's no need for tools or repeated fixes. See my earlier post about separating the text inset from the pilcrow with a space (or something). That will eliminate the problem once and for all. Richard -- Richard G. Combs Senior Technical Writer Polycom, Inc. richardDOTcombs AT polycomDOTcom 303-223-5111 -- rgcombs AT gmailDOTcom 303-777-0436 --
style following inset
I'm using FM 8. I'll try the override tool and see what happens. Thanks, Mollye > We have the same problem and have heard it's just a bug w/ FM 7.2 > unstructured insets. Our solution is to use Silicon Prairie's Paragraph > Tools to Remove Paragraph Overrides immediately before generating the book > for our output formats. > > Rene L. Stephenson > > > > > > > - Original Message > From: Mollye Barrett > To: framers at lists.frameusers.com > Sent: Thursday, February 21, 2008 11:03:32 AM > Subject: style following inset > > I'm working with an unstructured document set that uses text insets. When > insets are imported into the target document, the empty paragraph tag > following the inset automatically becomes a repeat of the first style in > the previous inset. So, if the inset starts with a numbered list, the next > empty paragraph tag in the document becomes a number list too. > > I know this will go away when and if the documents are structured but that > is not an option right now. Can anyone recommend best practices for > handling unstructured insets and/or specifically how to resolve this > unwelcome problem. I seem to recall a fix but I haven't been faced with > this problem for a long time. > > Any help is truly appreciated! > > > Mollye Barrett > ClearPath, LLC > 414-331-1378 > ___ > > > You are currently subscribed to Framers as rinnie1 at yahoo.com. > > Send list messages to framers at lists.frameusers.com. > > To unsubscribe send a blank email to > framers-unsubscribe at lists.frameusers.com > or visit > http://lists.frameusers.com/mailman/options/framers/rinnie1%40yahoo.com > > Send administrative questions to listadmin at frameusers.com. Visit > http://www.frameusers.com/ for more resources and info. > > > > Mollye Barrett ClearPath, LLC 414-331-1378
style following inset
Rene Stephenson > We have the same problem and have heard it's just a bug w/ FM > 7.2 unstructured insets. Our solution is to use Silicon > Prairie's Paragraph Tools to Remove Paragraph Overrides > immediately before generating the book for our output formats. It's not a bug specific to 7.2, this behavior has existed forever. I suspect it's related to the bug that produces a pgf override when a char format abuts up against the pilcrow (end-of-pgf marker). There's no need for tools or repeated fixes. See my earlier post about separating the text inset from the pilcrow with a space (or something). That will eliminate the problem once and for all. Richard -- Richard G. Combs Senior Technical Writer Polycom, Inc. richardDOTcombs AT polycomDOTcom 303-223-5111 -- rgcombs AT gmailDOTcom 303-777-0436 --
style following inset
Hi Mollye We have used unstructured insets and came across the same problem. As far as I am aware, the only way to handle this problem is to avoid consecutive insets. In our case, we ensure that insets represent an entire section, and are always enclosed by heading tags. For example Heading 1 Heading 2 Heading 3 Heading 3 Heading 3 Heading 2 ...etc... The obvious drawback to this is the heading text cannot be contained in the inset. I don't think there is any other way around the problem that doesn't incur formatting issues (such as those you mentioned) or using superfluous empty paragraphs to separate consecutive insets. Steven Teasdale GE Multilin -Original Message- From: framers-boun...@lists.frameusers.com [mailto:framers-bounces at lists.frameusers.com] On Behalf Of Mollye Barrett Sent: Thursday, February 21, 2008 11:04 AM To: framers at lists.frameusers.com Subject: style following inset I'm working with an unstructured document set that uses text insets. When insets are imported into the target document, the empty paragraph tag following the inset automatically becomes a repeat of the first style in the previous inset. So, if the inset starts with a numbered list, the next empty paragraph tag in the document becomes a number list too. I know this will go away when and if the documents are structured but that is not an option right now. Can anyone recommend best practices for handling unstructured insets and/or specifically how to resolve this unwelcome problem. I seem to recall a fix but I haven't been faced with this problem for a long time. Any help is truly appreciated! Mollye Barrett ClearPath, LLC 414-331-1378 ___ You are currently subscribed to Framers as steven.teasdale at ge.com. Send list messages to framers at lists.frameusers.com. To unsubscribe send a blank email to framers-unsubscribe at lists.frameusers.com or visit http://lists.frameusers.com/mailman/options/framers/steven.teasdale%40ge .com Send administrative questions to listadmin at frameusers.com. Visit http://www.frameusers.com/ for more resources and info.
style following inset
Put a tiny empty paragraph at the very beginning of the file/document that you are 'insetting' Regards, Micheal O'Laoghaire CBS Documentation Comverse Inc. Cambridge, MA. Tel: (617) 273-5414 -Original Message- From: framers-boun...@lists.frameusers.com [mailto:framers-bounces at lists.frameusers.com] On Behalf Of Mollye Barrett Sent: Thursday, February 21, 2008 11:04 AM To: framers at lists.frameusers.com Subject: style following inset I'm working with an unstructured document set that uses text insets. When insets are imported into the target document, the empty paragraph tag following the inset automatically becomes a repeat of the first style in the previous inset. So, if the inset starts with a numbered list, the next empty paragraph tag in the document becomes a number list too. I know this will go away when and if the documents are structured but that is not an option right now. Can anyone recommend best practices for handling unstructured insets and/or specifically how to resolve this unwelcome problem. I seem to recall a fix but I haven't been faced with this problem for a long time. Any help is truly appreciated! Mollye Barrett ClearPath, LLC 414-331-1378 ___ You are currently subscribed to Framers as Micheal.OLaoghaire at comverse.com. Send list messages to framers at lists.frameusers.com. To unsubscribe send a blank email to framers-unsubscribe at lists.frameusers.com or visit http://lists.frameusers.com/mailman/options/framers/micheal.olaoghaire%4 0comverse.com Send administrative questions to listadmin at frameusers.com. Visit http://www.frameusers.com/ for more resources and info.
style following inset
Thanks all. You've jogged my memory with details and I'll give the fixes a try on this doc set. Mollye Barrett ClearPath, LLC 414-331-1378
Re: style following inset
Glad to learn that. (Had to dig the reply out of my spam folder where it had gotten misrouted by my spam filter.) Rene L. Stephenson - Original Message From: "Combs, Richard" <[EMAIL PROTECTED]> To: Rene Stephenson <[EMAIL PROTECTED]>; [EMAIL PROTECTED]; framers@lists.frameusers.com Sent: Thursday, February 21, 2008 1:22:54 PM Subject: RE: style following inset Rene Stephenson > We have the same problem and have heard it's just a bug w/ FM > 7.2 unstructured insets. Our solution is to use Silicon > Prairie's Paragraph Tools to Remove Paragraph Overrides > immediately before generating the book for our output formats. It's not a bug specific to 7.2, this behavior has existed forever. I suspect it's related to the bug that produces a pgf override when a char format abuts up against the pilcrow (end-of-pgf marker). There's no need for tools or repeated fixes. See my earlier post about separating the text inset from the pilcrow with a space (or something). That will eliminate the problem once and for all. Richard -- Richard G. Combs Senior Technical Writer Polycom, Inc. richardDOTcombs AT polycomDOTcom 303-223-5111 -- rgcombs AT gmailDOTcom 303-777-0436 -- ___ You are currently subscribed to Framers as [EMAIL PROTECTED] Send list messages to [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] or visit http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com Send administrative questions to [EMAIL PROTECTED] Visit http://www.frameusers.com/ for more resources and info.
style following inset
Glad to learn that. (Had to dig the reply out of my spam folder where it had gotten misrouted by my spam filter.) Rene L. Stephenson - Original Message From: "Combs, Richard" To: Rene Stephenson ; mollye at clearpath.cc; framers at lists.frameusers.com Sent: Thursday, February 21, 2008 1:22:54 PM Subject: RE: style following inset Rene Stephenson > We have the same problem and have heard it's just a bug w/ FM > 7.2 unstructured insets. Our solution is to use Silicon > Prairie's Paragraph Tools to Remove Paragraph Overrides > immediately before generating the book for our output formats. It's not a bug specific to 7.2, this behavior has existed forever. I suspect it's related to the bug that produces a pgf override when a char format abuts up against the pilcrow (end-of-pgf marker). There's no need for tools or repeated fixes. See my earlier post about separating the text inset from the pilcrow with a space (or something). That will eliminate the problem once and for all. Richard -- Richard G. Combs Senior Technical Writer Polycom, Inc. richardDOTcombs AT polycomDOTcom 303-223-5111 -- rgcombs AT gmailDOTcom 303-777-0436 --
RE: style following inset
Rene Stephenson > We have the same problem and have heard it's just a bug w/ FM > 7.2 unstructured insets. Our solution is to use Silicon > Prairie's Paragraph Tools to Remove Paragraph Overrides > immediately before generating the book for our output formats. It's not a bug specific to 7.2, this behavior has existed forever. I suspect it's related to the bug that produces a pgf override when a char format abuts up against the pilcrow (end-of-pgf marker). There's no need for tools or repeated fixes. See my earlier post about separating the text inset from the pilcrow with a space (or something). That will eliminate the problem once and for all. Richard -- Richard G. Combs Senior Technical Writer Polycom, Inc. richardDOTcombs AT polycomDOTcom 303-223-5111 -- rgcombs AT gmailDOTcom 303-777-0436 -- ___ You are currently subscribed to Framers as [EMAIL PROTECTED] Send list messages to [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] or visit http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com Send administrative questions to [EMAIL PROTECTED] Visit http://www.frameusers.com/ for more resources and info.
style following inset
I'm working with an unstructured document set that uses text insets. When insets are imported into the target document, the empty paragraph tag following the inset automatically becomes a repeat of the first style in the previous inset. So, if the inset starts with a numbered list, the next empty paragraph tag in the document becomes a number list too. I know this will go away when and if the documents are structured but that is not an option right now. Can anyone recommend best practices for handling unstructured insets and/or specifically how to resolve this unwelcome problem. I seem to recall a fix but I haven't been faced with this problem for a long time. Any help is truly appreciated! Mollye Barrett ClearPath, LLC 414-331-1378
Re: style following inset
I'm using FM 8. I'll try the override tool and see what happens. Thanks, Mollye > We have the same problem and have heard it's just a bug w/ FM 7.2 > unstructured insets. Our solution is to use Silicon Prairie's Paragraph > Tools to Remove Paragraph Overrides immediately before generating the book > for our output formats. > > Rene L. Stephenson > > > > > > > - Original Message > From: Mollye Barrett <[EMAIL PROTECTED]> > To: framers@lists.frameusers.com > Sent: Thursday, February 21, 2008 11:03:32 AM > Subject: style following inset > > I'm working with an unstructured document set that uses text insets. When > insets are imported into the target document, the empty paragraph tag > following the inset automatically becomes a repeat of the first style in > the previous inset. So, if the inset starts with a numbered list, the next > empty paragraph tag in the document becomes a number list too. > > I know this will go away when and if the documents are structured but that > is not an option right now. Can anyone recommend best practices for > handling unstructured insets and/or specifically how to resolve this > unwelcome problem. I seem to recall a fix but I haven't been faced with > this problem for a long time. > > Any help is truly appreciated! > > > Mollye Barrett > ClearPath, LLC > 414-331-1378 > ___ > > > You are currently subscribed to Framers as [EMAIL PROTECTED] > > Send list messages to [EMAIL PROTECTED] > > To unsubscribe send a blank email to > [EMAIL PROTECTED] > or visit > http://lists.frameusers.com/mailman/options/framers/rinnie1%40yahoo.com > > Send administrative questions to [EMAIL PROTECTED] Visit > http://www.frameusers.com/ for more resources and info. > > > > Mollye Barrett ClearPath, LLC 414-331-1378 ___ You are currently subscribed to Framers as [EMAIL PROTECTED] Send list messages to [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] or visit http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com Send administrative questions to [EMAIL PROTECTED] Visit http://www.frameusers.com/ for more resources and info.
Re: style following inset
We have the same problem and have heard it's just a bug w/ FM 7.2 unstructured insets. Our solution is to use Silicon Prairie's Paragraph Tools to Remove Paragraph Overrides immediately before generating the book for our output formats. Rene L. Stephenson - Original Message From: Mollye Barrett <[EMAIL PROTECTED]> To: framers@lists.frameusers.com Sent: Thursday, February 21, 2008 11:03:32 AM Subject: style following inset I'm working with an unstructured document set that uses text insets. When insets are imported into the target document, the empty paragraph tag following the inset automatically becomes a repeat of the first style in the previous inset. So, if the inset starts with a numbered list, the next empty paragraph tag in the document becomes a number list too. I know this will go away when and if the documents are structured but that is not an option right now. Can anyone recommend best practices for handling unstructured insets and/or specifically how to resolve this unwelcome problem. I seem to recall a fix but I haven't been faced with this problem for a long time. Any help is truly appreciated! Mollye Barrett ClearPath, LLC 414-331-1378 ___ You are currently subscribed to Framers as [EMAIL PROTECTED] Send list messages to [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] or visit http://lists.frameusers.com/mailman/options/framers/rinnie1%40yahoo.com Send administrative questions to [EMAIL PROTECTED] Visit http://www.frameusers.com/ for more resources and info. ___ You are currently subscribed to Framers as [EMAIL PROTECTED] Send list messages to [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] or visit http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com Send administrative questions to [EMAIL PROTECTED] Visit http://www.frameusers.com/ for more resources and info.
style following inset
We have the same problem and have heard it's just a bug w/ FM 7.2 unstructured insets. Our solution is to use Silicon Prairie's Paragraph Tools to Remove Paragraph Overrides immediately before generating the book for our output formats. Rene L. Stephenson - Original Message From: Mollye Barrett To: framers at lists.frameusers.com Sent: Thursday, February 21, 2008 11:03:32 AM Subject: style following inset I'm working with an unstructured document set that uses text insets. When insets are imported into the target document, the empty paragraph tag following the inset automatically becomes a repeat of the first style in the previous inset. So, if the inset starts with a numbered list, the next empty paragraph tag in the document becomes a number list too. I know this will go away when and if the documents are structured but that is not an option right now. Can anyone recommend best practices for handling unstructured insets and/or specifically how to resolve this unwelcome problem. I seem to recall a fix but I haven't been faced with this problem for a long time. Any help is truly appreciated! Mollye Barrett ClearPath, LLC 414-331-1378 ___ You are currently subscribed to Framers as rinnie1 at yahoo.com. Send list messages to framers at lists.frameusers.com. To unsubscribe send a blank email to framers-unsubscribe at lists.frameusers.com or visit http://lists.frameusers.com/mailman/options/framers/rinnie1%40yahoo.com Send administrative questions to listadmin at frameusers.com. Visit http://www.frameusers.com/ for more resources and info.
style following inset
Mollye Barrett wrote: > I'm working with an unstructured document set that uses text > insets. When insets are imported into the target document, > the empty paragraph tag following the inset automatically > becomes a repeat of the first style in the previous inset. > So, if the inset starts with a numbered list, the next empty > paragraph tag in the document becomes a number list too. That "empty" pgf isn't really empty. It's the _container_ pgf into which you imported the text inset. If you click the inset to select it, you'll see from the highlighting that it sits in that pgf. There's an _extra_ pgf break because the text inset itself ends with a paragraph break. Enough context. The fix is simple: Put something -- anything -- between the text inset and the end of its container pgf. For existing text insets, position the cursor between the the text inset and the pilcrow (end-of-pgf symbol) of the container pgf and type something. I use a non-breaking space (Ctrl-Space) so that there's a little symbol there (I always work with View > Symbols on), and it's less likely to be accidentally deleted. Change the pgf format to whatever you want (I have a special format I use as a text inset container) and update the text inset. The container pgf remains unchanged. For a new text inset, if the text cursor is in an empty pgf when you import the inset, the inset will "sit" up against the pilcrow and cause your problem. Type the Ctrl-Space first, then move the cursor to the left of it before importing the inset. Or consider importing the inset with the cursor at the beginning of a non-empty pgf (i.e., to the left of some text). HTH! Richard -- Richard G. Combs Senior Technical Writer Polycom, Inc. richardDOTcombs AT polycomDOTcom 303-223-5111 -- rgcombs AT gmailDOTcom 303-777-0436 --
RE: style following inset
Thanks all. You've jogged my memory with details and I'll give the fixes a try on this doc set. Mollye Barrett ClearPath, LLC 414-331-1378 ___ You are currently subscribed to Framers as [EMAIL PROTECTED] Send list messages to [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] or visit http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com Send administrative questions to [EMAIL PROTECTED] Visit http://www.frameusers.com/ for more resources and info.
RE: style following inset
Mollye Barrett wrote: > I'm working with an unstructured document set that uses text > insets. When insets are imported into the target document, > the empty paragraph tag following the inset automatically > becomes a repeat of the first style in the previous inset. > So, if the inset starts with a numbered list, the next empty > paragraph tag in the document becomes a number list too. That "empty" pgf isn't really empty. It's the _container_ pgf into which you imported the text inset. If you click the inset to select it, you'll see from the highlighting that it sits in that pgf. There's an _extra_ pgf break because the text inset itself ends with a paragraph break. Enough context. The fix is simple: Put something -- anything -- between the text inset and the end of its container pgf. For existing text insets, position the cursor between the the text inset and the pilcrow (end-of-pgf symbol) of the container pgf and type something. I use a non-breaking space (Ctrl-Space) so that there's a little symbol there (I always work with View > Symbols on), and it's less likely to be accidentally deleted. Change the pgf format to whatever you want (I have a special format I use as a text inset container) and update the text inset. The container pgf remains unchanged. For a new text inset, if the text cursor is in an empty pgf when you import the inset, the inset will "sit" up against the pilcrow and cause your problem. Type the Ctrl-Space first, then move the cursor to the left of it before importing the inset. Or consider importing the inset with the cursor at the beginning of a non-empty pgf (i.e., to the left of some text). HTH! Richard -- Richard G. Combs Senior Technical Writer Polycom, Inc. richardDOTcombs AT polycomDOTcom 303-223-5111 -- rgcombs AT gmailDOTcom 303-777-0436 -- ___ You are currently subscribed to Framers as [EMAIL PROTECTED] Send list messages to [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] or visit http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com Send administrative questions to [EMAIL PROTECTED] Visit http://www.frameusers.com/ for more resources and info.
Re: style following inset
Hi Mollye, Just make sure that the paragraph which follows the text inset is not empty (if possible). If this option is not possible, for example, if the text inset is at the end of your text flow, you can do this: 1. Put a new paragraph after the text inset. 2. In this paragraph, type a single character, for example a full stop. 3. Create a dedicated paratag, for example "eoti", meaning "end of text inset" with the Color set to White in the Para Designer. 4. Apply this paratag to the paragraph with the single character. 5. Update the text inset to test it. If you also generate WebHelp or HTMLHelp output of this FM file, make sure that you set this paratag (eoti) to No Output. Good luck. Yves Barbion Documentation Architect Adobe-Certified FrameMaker Instructor Scripto Belgium Mollye Barrett wrote: > I'm working with an unstructured document set that uses text insets. When > insets are imported into the target document, the empty paragraph tag > following the inset automatically becomes a repeat of the first style in > the previous inset. So, if the inset starts with a numbered list, the next > empty paragraph tag in the document becomes a number list too. > > I know this will go away when and if the documents are structured but that > is not an option right now. Can anyone recommend best practices for > handling unstructured insets and/or specifically how to resolve this > unwelcome problem. I seem to recall a fix but I haven't been faced with > this problem for a long time. > > Any help is truly appreciated! > > > Mollye Barrett > ClearPath, LLC > 414-331-1378 > ___ > > > You are currently subscribed to Framers as [EMAIL PROTECTED] > > Send list messages to [EMAIL PROTECTED] > > To unsubscribe send a blank email to > [EMAIL PROTECTED] > or visit > http://lists.frameusers.com/mailman/options/framers/yves.barbion%40gmail.com > > Send administrative questions to [EMAIL PROTECTED] Visit > http://www.frameusers.com/ for more resources and info. > > ___ You are currently subscribed to Framers as [EMAIL PROTECTED] Send list messages to [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] or visit http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com Send administrative questions to [EMAIL PROTECTED] Visit http://www.frameusers.com/ for more resources and info.
RE: style following inset
Hi Mollye We have used unstructured insets and came across the same problem. As far as I am aware, the only way to handle this problem is to avoid consecutive insets. In our case, we ensure that insets represent an entire section, and are always enclosed by heading tags. For example Heading 1 Heading 2 Heading 3 Heading 3 Heading 3 Heading 2 ...etc... The obvious drawback to this is the heading text cannot be contained in the inset. I don't think there is any other way around the problem that doesn't incur formatting issues (such as those you mentioned) or using superfluous empty paragraphs to separate consecutive insets. Steven Teasdale GE Multilin -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mollye Barrett Sent: Thursday, February 21, 2008 11:04 AM To: framers@lists.frameusers.com Subject: style following inset I'm working with an unstructured document set that uses text insets. When insets are imported into the target document, the empty paragraph tag following the inset automatically becomes a repeat of the first style in the previous inset. So, if the inset starts with a numbered list, the next empty paragraph tag in the document becomes a number list too. I know this will go away when and if the documents are structured but that is not an option right now. Can anyone recommend best practices for handling unstructured insets and/or specifically how to resolve this unwelcome problem. I seem to recall a fix but I haven't been faced with this problem for a long time. Any help is truly appreciated! Mollye Barrett ClearPath, LLC 414-331-1378 ___ You are currently subscribed to Framers as [EMAIL PROTECTED] Send list messages to [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] or visit http://lists.frameusers.com/mailman/options/framers/steven.teasdale%40ge .com Send administrative questions to [EMAIL PROTECTED] Visit http://www.frameusers.com/ for more resources and info. ___ You are currently subscribed to Framers as [EMAIL PROTECTED] Send list messages to [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] or visit http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com Send administrative questions to [EMAIL PROTECTED] Visit http://www.frameusers.com/ for more resources and info.
style following inset
I'm working with an unstructured document set that uses text insets. When insets are imported into the target document, the empty paragraph tag following the inset automatically becomes a repeat of the first style in the previous inset. So, if the inset starts with a numbered list, the next empty paragraph tag in the document becomes a number list too. I know this will go away when and if the documents are structured but that is not an option right now. Can anyone recommend best practices for handling unstructured insets and/or specifically how to resolve this unwelcome problem. I seem to recall a fix but I haven't been faced with this problem for a long time. Any help is truly appreciated! Mollye Barrett ClearPath, LLC 414-331-1378 ___ You are currently subscribed to Framers as [EMAIL PROTECTED] Send list messages to [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] or visit http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com Send administrative questions to [EMAIL PROTECTED] Visit http://www.frameusers.com/ for more resources and info.
