Hi Markus,
Have a look at StrikeFont>>writeAsStrike2named: and #readFromStrike2:.
I assume with these methods you can write out the existing strike
fonts and read them in again. I would not care about the existing TT
fonts as they are in low quality (i.e., blurry, probably because of
missing sub-pixel AA).
I think that, at least for now, we should leave the two strike fonts I
propose in the system and not remove the whole font implementation to
not depend on the platform specific free type font implementation.
This also leaves the possibility to remove the free type functionality
for server images to reduce the memory footprint.
Adrian
On Oct 17, 2008, at 20:59 , Markus Fritsche wrote:
Stéphane Ducasse schrieb:
So basically, I'd like to vote for "remove and make loadable steph
by
steph"
step by step because steph is too buzy :)
Markus we hear well your wishes now the best way to make it real
is to send us some code :)
Just fair. I'll see what I can up with to load fonts by request with
the
tools supplied within a vanilla pharo image and a given URL (don't
nail
me on that, I'm known not to keep promises).
I guess if I will contribute code I will have to give a signature and
mail it, right!?
_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
