> 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 did not find a bug. Is t
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 Mar
Hm. Actually, I clicked “force all” so that the font size was set to 10. Now
that I’ve looked at it again I can’t reproduce what you say.
I know what you mean though, I’ve had situations where the font was suddenly
different but I never investigated. Are you sure it’s not just the font size?
>
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 how the font looks like i
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 fonts in the top
> part
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, T
