Gay Alson wrote: > 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?
No, that won't work. Each text inset that you import must be a complete flow. If all your text inset source files are concatenated into one flow, when you import into the destination file, you'll get the entire shebang. The only way to combine multiple text insets into one file is to put each in its own flow. Then when you import, FM prompts you to choose which flow you want. I believe the limit on text flows per file is more than 256, but can't locate any hard number (there may not be one). Personally, I'd never put hundreds of text insets in a single file just because it's not a user-friendly way to organize things. I'd instead create a text insets book. Within that, I'd put the text insets into several files based on some logical organizing principle -- subject matter, purpose, etc. -- so that it's easy to find things, work with related topics, etc. > 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. You can't insert a text frame directly into another text frame. I'm guessing that you just placed it on top of the Flow A text frame (try moving/resizing that, and you'll probably find that the Metadata frame isn't affected). You can put a text frame inside another text frame _indirectly_ by creating an anchored frame and then creating a text frame inside that. If you have a bunch of short (less than a page) text insets, this would be an easy way to organize them. Put the metadata into the main flow, with a nearly page-filling anchored frame below each set of metadata. In each anchored frame, create a text frame, give it a unique flow name, and insert the text inset text. I don't think this approach is workable for longer text insets because I don't believe you can connect text frames that are in different anchored frames. Maybe you could connect the text frame inside the anchored frame to a text frame on a disconnected page -- I don't know. If your text insets are longer than a page, a better approach would be to use separate text frames for the metadata flow and the text insets. It will get somewhat fussy to set up and maintain, though (especially if there were a lot of churn in the content and length of the text insets). I'd keep the number per file fairly low (and use a book of text insets, as I mentioned before). HTH! Richard G. Combs Senior Technical Writer Polycom, Inc. richardDOTcombs AT polycomDOTcom 303-223-5111 ------ rgcombs AT gmailDOTcom 303-903-6372 ------
