Chris Despopoulos wrote:
> If you apply bold to a char range that includes the last char in a
pgf,
> then Maker will assume the whole pgf should be bolded. Using the
Default
> Font setting in the fmt catalog won't change it back to its default
> properties. I've found that you should always have
Chris Despopoulos wrote:
> If you apply bold to a char range that includes the last char in a
pgf,
> then Maker will assume the whole pgf should be bolded. Using the
Default
> Font setting in the fmt catalog won't change it back to its default
> properties. I've found that you should always hav
This looks like part of a bigger problem with character ranges. It's
understandable that you would get this behavior where arrowing from one
direction makes the transition point show one property, and from the other
direction the transition point shows another. The fact that the Enter key (new
This looks like part of a bigger problem with character ranges. It's
understandable that you would get this behavior where arrowing from one
direction makes the transition point show one property, and from the other
direction the transition point shows another. The fact that the Enter key (new
At 02:30 PM 6/25/2009, Fred Ridder wrote:
>Am I correct that FrameMaker's behavior when you type an Enter in
>conditionalized text changed before version 8.0? The behavior I'm seeing
>in FM8.0 seems flat-out wrong to me, and is driving me crazy.
Fred,
You are correct and I agree that the beha
At 02:30 PM 6/25/2009, Fred Ridder wrote:
>Am I correct that FrameMaker's behavior when you type an Enter in
>conditionalized text changed before version 8.0? The behavior I'm seeing
>in FM8.0 seems flat-out wrong to me, and is driving me crazy.
Fred,
You are correct and I agree that the beha
FrameMaker 8.0p277, Windows XP SP3.
Am I correct that FrameMaker's behavior when you type an Enter in
conditionalized text changed before version 8.0? The behavior I'm seeing in
FM8.0 seems flat-out wrong to me, and is driving me crazy.
I older versions of FrameMaker (at least through 7.0,
FrameMaker 8.0p277, Windows XP SP3.
Am I correct that FrameMaker's behavior when you type an Enter in
conditionalized text changed before version 8.0? The behavior I'm seeing in
FM8.0 seems flat-out wrong to me, and is driving me crazy.
I older versions of FrameMaker (at least through 7.0
