problems with the default font

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|

problems with the default font

Tudor Girba-2
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):
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"):


Interestingly, the code font looks the same in both situations. Can you confirm this effect?

Cheers,
Doru



--
www.tudorgirba.com
www.feenk.com

"From an abstract enough point of view, any two things are similar."




Reply | Threaded
Open this post in threaded view
|

Re: problems with the default font

EstebanLM
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 <[hidden email]> 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
www.feenk.com

"From an abstract enough point of view, any two things are similar."





Reply | Threaded
Open this post in threaded view
|

Re: problems with the default font

Max Leske
In reply to this post by Tudor Girba-2
Yes, that’s right.

On 12 Mar 2016, at 14:19, Tudor Girba <[hidden email]> 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
www.feenk.com

"From an abstract enough point of view, any two things are similar."





Reply | Threaded
Open this post in threaded view
|

Re: problems with the default font

EstebanLM
In reply to this post by Tudor Girba-2
bah… “fix it” in the sense that correct fonts will be restored :) 

On 12 Mar 2016, at 14:19, Tudor Girba <[hidden email]> 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
www.feenk.com

"From an abstract enough point of view, any two things are similar."





Reply | Threaded
Open this post in threaded view
|

Re: problems with the default font

Max Leske
In reply to this post by Max Leske
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?


On 12 Mar 2016, at 15:00, Max Leske <[hidden email]> wrote:

Yes, that’s right.

On 12 Mar 2016, at 14:19, Tudor Girba <[hidden email]> 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
www.feenk.com

"From an abstract enough point of view, any two things are similar."






Reply | Threaded
Open this post in threaded view
|

Re: problems with the default font

Tudor Girba-2
In reply to this post by EstebanLM
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 12, 2016, at 2:59 PM, Esteban Lorenzano <[hidden email]> wrote:
>
> 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 <[hidden email]> 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
>> www.feenk.com
>>
>> "From an abstract enough point of view, any two things are similar."
>>
>>
>>
>>
>

--
www.tudorgirba.com
www.feenk.com

"Next time you see your life passing by, say 'hi' and get to know her."





Reply | Threaded
Open this post in threaded view
|

Re: problems with the default font

EstebanLM

> On 12 Mar 2016, at 21:22, Tudor Girba <[hidden email]> 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 there such a report or should I create one?

well… I closed last one (I submitted a fix), but I think I need to open a new one :)

Esteban

>
> Cheers,
> Doru
>
>
>> On Mar 12, 2016, at 2:59 PM, Esteban Lorenzano <[hidden email]> wrote:
>>
>> 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 <[hidden email]> 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
>>> www.feenk.com
>>>
>>> "From an abstract enough point of view, any two things are similar."
>>>
>>>
>>>
>>>
>>
>
> --
> www.tudorgirba.com
> www.feenk.com
>
> "Next time you see your life passing by, say 'hi' and get to know her."
>
>
>
>
>