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.)

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.


> Date: Tue, 4 Feb 2014 19:54:44 +0000
> To:;;
> From:
> Subject: RE: FM12 has char format in xref been fixed?
> How you got about it all depends on the context. I would guess from your 
> original post that you want to use <$paratext> and get the text *and* any 
> character formatting applied to it. But FrameMaker doesn't work like that: 
> you can't 'recover' character formatting from an xref source's text.
> I don't know about maker.ini fixes, as FrameMaker 7 for Mac doesn't use 
> maker.ini.
> If all the above is nonsense, or completely off-base, I apologize: I'm trying 
> to think in the midst of a gale that's trying to take the roof off.
> -- 
> Steve [Trim e-mails: use less disk, use less power, use less planet]
> _______________________________________________

You are currently subscribed to framers as

Send list messages to

To unsubscribe send a blank email to
or visit

Send administrative questions to Visit for more resources and info.

Reply via email to