problems with the default font
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."
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 <tudor@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."
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 <estebanlm@gmail.com> 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 <tudor@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 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."
On 12 Mar 2016, at 21:22, Tudor Girba <tudor@tudorgirba.com> 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 <estebanlm@gmail.com> 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 <tudor@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 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."
Yes, thatâs right.
On 12 Mar 2016, at 14:19, Tudor Girba <tudor@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."
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 <maxleske@gmail.com> wrote:
Yes, thatâs right.
On 12 Mar 2016, at 14:19, Tudor Girba <tudor@tudorgirba.com <mailto:tudor@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 <http://www.feenk.com/>
"From an abstract enough point of view, any two things are similar."
bah⦠âfix itâ in the sense that correct fonts will be restored :)
On 12 Mar 2016, at 14:19, Tudor Girba <tudor@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."
participants (3)
-
Esteban Lorenzano -
Max Leske -
Tudor Girba