At 14:08 -0600 4/2/14, Craig Ede wrote: >The essence of the workaround that was described is based on the fact that >font family changes are respected in xrefs (try formatting part of a line with >WingDings, for instance). Thus the kludge that allows you to define a family >that incorporates formatting like bold, or italics, or blue, or whatever by >simply making it look like a different font family. (Disclaimer: I have never >done this.)
Ah... clever. >There are good arguments (as the one you make) for ignoring such formatting as >bold, ital and the like in an xref, but ignoring a ZapfDingbat or symbol font >char format could be disastrous. Imagine a mu becoming an "m" within an xref. >So FrameMaker is designed not to ignore that. The wonderful thing is that you >can use that "feature" to accomplish (albeit with a bit of work) what is >desired by the original poster. Never a day goes past without my learning something new about FrameMaker, even after more than 20 years of using it. Makes life interesting, I guess ;-) -- Steve _______________________________________________ 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.
