Re: [Pharo-dev] problems with the default font

2016-03-12 Thread Esteban Lorenzano
> On 12 Mar 2016, at 21:22, Tudor Girba wrote: > > Hi, > > I meant to ask if you confirm that the rendering looks like the DejaVu font > :). I know it was not intentional. > > Indeed, I confirm that just saving fixed the problem. > > I checked the issue tracker and I

Re: [Pharo-dev] problems with the default font

2016-03-12 Thread Tudor Girba
Hi, I meant to ask if you confirm that the rendering looks like the DejaVu font :). I know it was not intentional. Indeed, I confirm that just saving fixed the problem. I checked the issue tracker and I did not find a bug. Is there such a report or should I create one? Cheers, Doru > On

Re: [Pharo-dev] problems with the default font

2016-03-12 Thread Esteban Lorenzano
bah… “fix it” in the sense that correct fonts will be restored :) > On 12 Mar 2016, at 14:19, Tudor Girba wrote: > > Hi, > > It looks to me as if in the latest Pharo, the default font is rendered with > the DejaVu bitmap font instead of Source Sans Pro. > > Here is

Re: [Pharo-dev] problems with the default font

2016-03-12 Thread Max Leske
Yes, that’s right. > On 12 Mar 2016, at 14:19, Tudor Girba wrote: > > Hi, > > It looks to me as if in the latest Pharo, the default font is rendered with > the DejaVu bitmap font instead of Source Sans Pro. > > Here is how the font looks like in Nautilus (look at the

Re: [Pharo-dev] problems with the default font

2016-03-12 Thread Esteban Lorenzano
no, I do not confirm (that the defaults are DejaVu): it is a bug. what actually happens is an effect of the infamous “font bug” that is around. in fact, if you have that effect with a latest image you should not need to reload fonts, just saving image will fix it. > On 12 Mar 2016, at 14:19,