Yes. We even printed the manual in question this way last year.

The workaround seems to be to add the font family name to the
character format, which is OK in this instance, but would be odd if
using with a different font family. Then I would have to make a
different character format tag for that or all other font families.

This used to be OK before SP2. I wonder whether SP2 manages fonts
somewhat differently.

Thanks for the input.

Bodvar

On 8/8/06, Peter Gold <khpeter at earthlink.net> wrote:
> Hi, B?dvar:
>
> Have you verified that bold isn't being applied by selecting the text
> and examining it with the character designer, or printing to PDF or
> paper, or by increasing the zoom percentage? Some fonts at some
> magnifications don't always display bold properties on screen in FM.
>
> HTH
>
> Peter Gold
> KnowHow ProServices
>
> Bodvar Bjorgvinsson wrote:
> > Hi all.
> >
> > I have earlier complained about problems with Character tags where
> > bold becomes bolded or bold does not work at all, so therefore I have
> > as much as possible tried  in structured FM to use Characther change
> > format elements. However, these elements can not be used on
> > autonumbering, so there I am stuck with the dreaded Character format
> > tags.
> >
> > I have this problem now, that we are using numbered notes, which are
> > set to Angle=Oblique (Helvetica being the default font). The character
> > format tag, called Note changes the following: Weight=Bold, and
> > Color=Note.
> > Out of this the only change I get is the color. The weight is still
> > regular althoug the Character Format Tag distinctly says bold.
>
>

Reply via email to