Hi Herbert,

>Other than that problem I'd suggest to reintroduce the unique system id for
>fonts. Only with this approach we can work with all the fonts that OS/2
>never heard of, like the many mentioned in OOo's (in-)famous VCL.xcu
>configuration file.

ah ok, I'll do it.


>Please see vcl/source/gdi/pdfwriter_impl.cxx for details on when the
>emulated boldness is triggered:
>    (maFontSelData.mpFontData->GetWeight() <= WEIGHT_MEDIUM)
> && (maFontSelData.GetWeight() > WEIGHT_MEDIUM)
>This means that if the requested font is bold and the selected device font
>has medium weight then the exported text gets emulated boldness.

so my first idea was correct.

I did some more debugging, but the problem seems to be at higher level:
when an 'Arial Bold' text is drawn to the display, OOo calls
SalGraphics::SetFont exactly with this font, and screen is ok.
But when it comes to pdf export, in the new presentation space,
SalGraphics::SetFont is called to select the 'Arial' font. The pointers
are different, so OOo is effectively using two different fonts.

Could you explain this? meanwhile I'll debug the code slightly more,
maybe I can see why this happens.

TIA,


Bye,

        Yuri Dario

/*
 * member of TeamOS/2 - Italy
 * http://www.os2power.com/yuri
 * http://www.teamos2.it
 */

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to