At 01:47 AM 1/11/2008, Steve Rickaby wrote:
>Xrefs are picking up font and/or color information from the xref target -
>or somewhere - rather than from the underlying text. If I manually zap
>them with 'default para font', all is well until the document is opened
>again, the xrefs are updated, a
At 01:47 AM 1/11/2008, Steve Rickaby wrote:
>Xrefs are picking up font and/or color information from the xref target -
>or somewhere - rather than from the underlying text. If I manually zap
>them with 'default para font', all is well until the document is opened
>again, the xrefs are updated, a
At 01:47 AM 1/11/2008, Steve Rickaby wrote:
> Xrefs are picking up font and/or color information from the xref target
> - or somewhere - rather than from the underlying text. If I manually zap
> them with 'default para font', all is well until the document is opened
> again, the xrefs are updat
At 01:47 AM 1/11/2008, Steve Rickaby wrote:
> Xrefs are picking up font and/or color information from the xref target
> - or somewhere - rather than from the underlying text. If I manually zap
> them with 'default para font', all is well until the document is opened
> again, the xrefs are updat
FrameMaker 7.0, structured, Mac OS X 10.4.11
I am seeing a strange problem that I cannot recall having encountered before.
Xrefs are picking up font and/or color information from the xref target - or
somewhere - rather than from the underlying text. If I manually zap them with
'default para fon
FrameMaker 7.0, structured, Mac OS X 10.4.11
I am seeing a strange problem that I cannot recall having encountered before.
Xrefs are picking up font and/or color information from the xref target - or
somewhere - rather than from the underlying text. If I manually zap them with
'default para fon
