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, Tudor Girba <tu...@tudorgirba.com> 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 fonts in the top > part): > <Screen Shot 2016-03-12 at 1.58.46 PM.png> > When I look in Settings, it says that it uses Source Sans Pro. > > However, if I reload the fonts and set it again to Source Sans Pro, I get > this picture with the correct rendering (look at the category name > “announcing"): > > <Screen Shot 2016-03-12 at 2.18.09 PM.png> > > Interestingly, the code font looks the same in both situations. Can you > confirm this effect? > > Cheers, > Doru > > > > -- > www.tudorgirba.com <http://www.tudorgirba.com/> > www.feenk.com > > "From an abstract enough point of view, any two things are similar." > > > >
