[Date Prev][Date Next] [Thread Prev][Thread Next]
[Date Index] [Thread Index] [New search]

Re: Keeping font overrides in crossreferece <$paratext>

Thomas, Peter,

Both suggestions are ones that certainly expand my current
knowledge and practice in using FM.  I'll take it offline and
carve out a niche of time to experiment with it.

For completeness of the thread, the problem summary is that I
wanted a cross-reference to a paragraph that duplicates the
paragraph text using <$paratext>, but I want all font overrides
in the source paragraph to be preserved in the cross-reference.
Normally, certain character format parameters are preserved if
they were applied in the source paragraph as character format
tags.  However, some are not (most notably italics).
Furthermore, each character that has been subjected to multiple
character format tags is only associated with one tag; the
cumulative effect of multiple format tags is realized through
overrides to the one tag.  The end result is that not all of the
character formatting is duplicated in the cross-reference.

The following suggestions are alternative approaches to preserve
complex character formatting completely in cross-referencing.

Thanks, all.  I'll follow up when I've had a chance to try them.


P.S. Posted to
Fred Ma
Dept. of Electronics, Carleton University
1125 Colonel By Drive, Ottawa, Ontario
Canada, K1S 5B6

Thomas M. wrote:
> If I understand you correctly, you should be able to achieve
> this by using a generated List of Paragraphs. If you're using a
> book file for this document, you simply add the LOP file at the
> appropriate place in the book. If this is a single document
> file, you can still generate a LOP file and include it by
> reference at the appropriate place.  It's an extra step to set
> up and format the LOP file, and an extra step to generate it
> for a single document, but it may very well be worth it.
> Generated files do preserve *all* character formatting made
> with character tags. Again, formatting with overrides,
> including applying multiple tags, are not preserved.  If you
> don't feel like creating "combination tags", you could perhaps
> apply the missing formatting manually in the generated LOP
> file. Such manual formatting is of course deleted if you
> regenerate the LOP file, so it needs to be done at the final
> stage.
> This won't be a "prefect" solution either, but perhaps a bit
> better than having the figure captions only in the list of
> captions file. Unless you really have very complex and numerous
> "multi-tag" formatting, I would consider creating "combination
> tags", even if they clutter the character catalog somewhat.
> Only you see it, right? :-)

Peter G. wrote:
> * Create a new file to contain the captions. Define a custom
> master page with no template text frame - the one usually named
> flow A. Draw text frames on this page, one per caption; name
> the text flow for each frame to indicate its caption, such as
> "Flow: Caption of phenomenon 1." Format as required.
> * In the source document, where you need the caption, import
> the text inset, just as you would insert a cross-reference.
> * In the location where you need the one-page list of captions,
> import the text insets. If you need thumbnails of the images on
> this page, create a two-column table; import the graphics and
> size appropriately, for column 1, and import the insets for
> column 2.
> If you need to revise the information or the graphics, you'd
> revise it in the source of the inset, or the source of the
> graphic, then update the book.

** To unsubscribe, send a message to majordomo@omsys.com **
** with "unsubscribe framers" (no quotes) in the body.   **