Exactly. This is why he pointed out that he got this error in a fresh Pharo 3.0 image :). In a Moose image, free type fonts are installed properly, hence we do not get the error. We only get the wrong rendering. Doru On Fri, Mar 28, 2014 at 3:00 PM, Igor Stasenko <siguctua@gmail.com> wrote:
This error message usually happens because it cannot find the freetype font for given font name, and substitutes it with system-default bitmap font, which are *not* supported by Athens.
(LogicalFont familyName: 'crazy non existing font name' pointSize:10) realFont => a StrikeFont(Bitmap DejaVu Sans 9 14)
so, please check your font(s) setup and fonts you using.
On 28 March 2014 14:50, Blondeau Vincent <vincent.blondeau@worldline.com>wrote:
No, I did not change the Free type in the pharo settings.
But if I do it under Moose, I got :
*De :* moose-dev-bounces@iam.unibe.ch [mailto: moose-dev-bounces@iam.unibe.ch] *De la part de* Stéphane Ducasse *Envoyé :* vendredi 28 mars 2014 14:44 *à :* Pharo Development List *Cc :* Moose-related development *Objet :* [Moose-dev] Re: [Pharo-dev] Re: Fwd: Font problem is still there
vincent
Did you changed the freetype settings?
Setf
On 28 Mar 2014, at 14:36, Blondeau Vincent < vincent.blondeau@worldline.com> wrote:
+1.
So, I did on a fresh Moose 5.0 Image under W7:
Gofer new
smalltalkhubUser: 'Pharo' project: 'Athens';
configuration;
loadDevelopment.
And :
AthensSceneView new scene: [ :canvas | |s|
canvas setFont: (LogicalFont familyName: 'FreeSans' pointSize: 20).
s:= String newFrom: ($A to: $Z),($a to: $z), ($0 to: $9).
canvas pathTransform restoreAfter: [
canvas pathTransform translateX: 0 Y: 50.
canvas setPaint: Color black.
canvas drawString:s ]
];openInWindow
And I got :
<image001.png>
<image002.png>
And under a fresh Pharo 3.0 :
<image003.png>
Vincent
*De :* moose-dev-bounces@iam.unibe.ch [ mailto:moose-dev-bounces@iam.unibe.ch <moose-dev-bounces@iam.unibe.ch>] *De la part de* Tudor Girba *Envoyé :* vendredi 28 mars 2014 14:28 *à :* Moose-related development *Objet :* [Moose-dev] Re: Fwd: [Pharo-dev] Font problem is still there
Hi,
This was discussed before both on the Moose and on the Pharo mailing list. We are loading explicitly an older version of Athens because we could not work at all with the one that came from Pharo, and nobody reacted at the time to the font issue:
GTImageSetupCommandLineHandler>>loadOlderAthensPackagesToCorrectTheFontCachingProblem
"
This is a workaround fir the bug described here:
https://pharo.fogbugz.com/f/cases/12777/Athens-font-cacheing-bug
"
Gofer new
smalltalkhubUser: 'Pharo' project: 'Pharo30';
package: 'Athens-Cairo' constraint: [ :version |
version author = 'MarcusDenker' and: [ version versionNumber = 51 ] ];
package: 'Athens-Core' constraint: [ :version |
version author = 'MarcusDenker' and: [ version versionNumber = 34 ] ];
load
Now it's great that you are looking at it. So, I now removed it from the setup and the image is now relying on the latest Pharo 3.0. The build is running now:
https://ci.inria.fr/moose/job/moose-5.0/1008/
Cheers,
Doru
On Fri, Mar 28, 2014 at 2:18 PM, Stéphane Ducasse < stephane.ducasse@inria.fr> wrote:
Hi guys.
This is strange that moose is using a so old version of Athens.
Stef
Begin forwarded message:
*From: *Igor Stasenko <siguctua@gmail.com>
*Subject: Re: [Pharo-dev] Font problem is still there*
*Date: *28 Mar 2014 14:03:17 GMT+1
*To: *Pharo Development List <pharo-dev@lists.pharo.org>
*Reply-To: *Pharo Development List <pharo-dev@lists.pharo.org>
so, i checked both in 4.9 and 5.0 Moose images on linux...
got weird results and sometimes crashes.
in 5.0 image the version is: Athens-Cairo-MarcusDenker.51
- this one uses pretty old code, which renders text using 'toy' cairo api for text rendering.
in my working image, where i work every day it is:
Athens-Cairo-SvenVanCaekenberghe.64
and there's also couple important fixes since .51 as well as different font rendering code which no longer using toy api..
so, guys, if you want me to continue, please try using latest versions and report problems about it,
because it makes no sense to find a fix in something which outdated and thrown away many months ago.
Load the latest dev version of Athens from smalltalkhub (it is version 2.5)
ConfigurationOfAthens loadDevelopment.
try it out.
Here's what i got on latest fresh vanilla out of the box Pharo 3.0 image on linux system:
<image004.jpg>
P.S. i am not saying that it is *impossible* that there is problems in new version, just asking you to report problems with that version,
not one which year(s) old.
-- Best regards, Igor Stasenko.
_______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
--
www.tudorgirba.com
"Every thing has its own flow"
------------------------------
Ce message et les pièces jointes sont confidentiels et réservés à l'usage exclusif de ses destinataires. Il peut également être protégé par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant être assurée sur Internet, la responsabilité de Worldline ne pourra être recherchée quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne saurait être recherchée pour tout dommage résultant d'un virus transmis.
This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Worldline liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.
------------------------------
Ce message et les pièces jointes sont confidentiels et réservés à l'usage exclusif de ses destinataires. Il peut également être protégé par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant être assurée sur Internet, la responsabilité de Worldline ne pourra être recherchée quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne saurait être recherchée pour tout dommage résultant d'un virus transmis.
This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Worldline liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.
-- Best regards, Igor Stasenko.
-- www.tudorgirba.com "Every thing has its own flow"
