The problem with too narrow Italic was not caused by an old version of the bitmaps, which would be fixed by loading the ones on squeaksource. It was caused by "isSynthetic" being used for two purposes: 1) Deciding which fonts were safe to delete when cleaning cache 2) Deriving a custom baseKern for italic fonts calculated from a non-italic font. The two clash however, when you strikethrough/bold/underline an already custom italic font, since it would be both synthetic and have the italic property... My suggested hotfix was to remove the setting of fonts as synthetic when derived from custom italic fonts, although this will cause them to not be deleted when cleaning cache, it will make them render correctly. A better alternative, I think, is to introduce another synthetic setting (inst var type of StrikeFont, only 0 and 3 is currently used), indicating the font is synthetic in the sense it can be deleted from caches, but derived from an italic base font so no kern adjustment should be used. The issue that the paint rule for making derived bold/italic versions do not respect alpha values if they exist in the base font still remains unsolved by this. Cheers, Henry On 08.01.2010 21:05, Stéphane Ducasse wrote:
are you suggesting that we load your DejaVu package in pharodev?
On Jan 8, 2010, at 6:02 PM, Alain Plantec wrote:
Mariano Martinez Peck a écrit :
Thanks Henrik. However, I tried what you told me and still is ugly :(
maybe you could try with the dejavu from www.squeaksource.com/DejaVu Alain
Any idea?
Thanks
Mariano
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project