Hi, We changed the default fonts in Pharo for the ones that are used normally in Moose. They are: Source Sans Pro and Source Code Pro. We needed to do it for several reasons: 1) TxText (the new text model) is cairo based, and cairo just can work with real fonts, so we need them as default (now we will be able to integrate TxText and start the replace of old editors) 2) Current fonts takes too much space and do not scales fine (at least that Iâve been told) So, well, that⦠you will see âsomething differentâ when you download latest image version :) cheers, Esteban
Cool
On 02 Dec 2014, at 09:48, Esteban Lorenzano <estebanlm@gmail.com> wrote:
Hi,
We changed the default fonts in Pharo for the ones that are used normally in Moose. They are: Source Sans Pro and Source Code Pro. We needed to do it for several reasons:
1) TxText (the new text model) is cairo based, and cairo just can work with real fonts, so we need them as default (now we will be able to integrate TxText and start the replace of old editors) 2) Current fonts takes too much space and do not scales fine (at least that Iâve been told)
So, well, that⦠you will see âsomething differentâ when you download latest image version :)
cheers, Esteban
Great!! I am sooo happy, we are moving forward! 2014-12-02 10:41 GMT+01:00 Yuriy Tymchuk <yuriy.tymchuk@me.com>:
Cool
On 02 Dec 2014, at 09:48, Esteban Lorenzano <estebanlm@gmail.com> wrote:
Hi,
We changed the default fonts in Pharo for the ones that are used normally in Moose. They are: Source Sans Pro and Source Code Pro. We needed to do it for several reasons:
1) TxText (the new text model) is cairo based, and cairo just can work with real fonts, so we need them as default (now we will be able to integrate TxText and start the replace of old editors) 2) Current fonts takes too much space and do not scales fine (at least that Iâve been told)
So, well, that⦠you will see âsomething differentâ when you download latest image version :)
cheers, Esteban
Great! Doru p.s. Finally :) On Tue, Dec 2, 2014 at 9:48 AM, Esteban Lorenzano <estebanlm@gmail.com> wrote:
Hi,
We changed the default fonts in Pharo for the ones that are used normally in Moose. They are: Source Sans Pro and Source Code Pro. We needed to do it for several reasons:
1) TxText (the new text model) is cairo based, and cairo just can work with real fonts, so we need them as default (now we will be able to integrate TxText and start the replace of old editors) 2) Current fonts takes too much space and do not scales fine (at least that Iâve been told)
So, well, that⦠you will see âsomething differentâ when you download latest image version :)
cheers, Esteban
-- www.tudorgirba.com "Every thing has its own flow"
What is the difference between 'Open Sans' and 'Source Code Sans' ? I am using the former in my 3.0 image, and I like it a bit more, it seems a bit wider.
On 02 Dec 2014, at 11:27, Tudor Girba <tudor@tudorgirba.com> wrote:
Great!
Doru
p.s. Finally :)
On Tue, Dec 2, 2014 at 9:48 AM, Esteban Lorenzano <estebanlm@gmail.com> wrote: Hi,
We changed the default fonts in Pharo for the ones that are used normally in Moose. They are: Source Sans Pro and Source Code Pro. We needed to do it for several reasons:
1) TxText (the new text model) is cairo based, and cairo just can work with real fonts, so we need them as default (now we will be able to integrate TxText and start the replace of old editors) 2) Current fonts takes too much space and do not scales fine (at least that Iâve been told)
So, well, that⦠you will see âsomething differentâ when you download latest image version :)
cheers, Esteban
-- www.tudorgirba.com
"Every thing has its own flow"
There is no Source Code Sans :). There is only "Source Sans Pro" or "Source Code Pro". Doru On Tue, Dec 2, 2014 at 11:35 AM, Sven Van Caekenberghe <sven@stfx.eu> wrote:
What is the difference between 'Open Sans' and 'Source Code Sans' ?
I am using the former in my 3.0 image, and I like it a bit more, it seems a bit wider.
On 02 Dec 2014, at 11:27, Tudor Girba <tudor@tudorgirba.com> wrote:
Great!
Doru
p.s. Finally :)
On Tue, Dec 2, 2014 at 9:48 AM, Esteban Lorenzano <estebanlm@gmail.com> wrote: Hi,
We changed the default fonts in Pharo for the ones that are used normally in Moose. They are: Source Sans Pro and Source Code Pro. We needed to do it for several reasons:
1) TxText (the new text model) is cairo based, and cairo just can work with real fonts, so we need them as default (now we will be able to integrate TxText and start the replace of old editors) 2) Current fonts takes too much space and do not scales fine (at least that Iâve been told)
So, well, that⦠you will see âsomething differentâ when you download latest image version :)
cheers, Esteban
-- www.tudorgirba.com
"Every thing has its own flow"
-- www.tudorgirba.com "Every thing has its own flow"
On 02 Dec 2014, at 11:46, Tudor Girba <tudor@tudorgirba.com> wrote:
There is no Source Code Sans :). There is only "Source Sans Pro" or "Source Code Pro".
Yes, right now in the latest 4.0. But there used to be a different one, that is the one I am using, see screenshot (http://www.google.com/fonts/specimen/Open+Sans). I don't remember where I got it from (Igor is the author), but I have been using it for months. My question was, why choose one above the other ?
Doru
On Tue, Dec 2, 2014 at 11:35 AM, Sven Van Caekenberghe <sven@stfx.eu> wrote: What is the difference between 'Open Sans' and 'Source Code Sans' ?
I am using the former in my 3.0 image, and I like it a bit more, it seems a bit wider.
On 02 Dec 2014, at 11:27, Tudor Girba <tudor@tudorgirba.com> wrote:
Great!
Doru
p.s. Finally :)
On Tue, Dec 2, 2014 at 9:48 AM, Esteban Lorenzano <estebanlm@gmail.com> wrote: Hi,
We changed the default fonts in Pharo for the ones that are used normally in Moose. They are: Source Sans Pro and Source Code Pro. We needed to do it for several reasons:
1) TxText (the new text model) is cairo based, and cairo just can work with real fonts, so we need them as default (now we will be able to integrate TxText and start the replace of old editors) 2) Current fonts takes too much space and do not scales fine (at least that Iâve been told)
So, well, that⦠you will see âsomething differentâ when you download latest image version :)
cheers, Esteban
-- www.tudorgirba.com
"Every thing has its own flow"
-- www.tudorgirba.com
"Every thing has its own flow"
On 02 Dec 2014, at 12:02, Sven Van Caekenberghe <sven@stfx.eu> wrote:
On 02 Dec 2014, at 11:46, Tudor Girba <tudor@tudorgirba.com <mailto:tudor@tudorgirba.com>> wrote:
There is no Source Code Sans :). There is only "Source Sans Pro" or "Source Code Pro".
Yes, right now in the latest 4.0.
But there used to be a different one, that is the one I am using, see screenshot (http://www.google.com/fonts/specimen/Open+Sans <http://www.google.com/fonts/specimen/Open+Sans>). I don't remember where I got it from (Igor is the author), but I have been using it for months.
no, it was me the author⦠and it was a mistake I made first time thatâs why I removed it (but I can package it and put it somewhere anyway⦠I was even thinking on create a âFont Repositoryâ where put different fonts, until I found this: http://smalltalkhub.com/#!/~girba/FreeFonts <http://smalltalkhub.com/#!/~girba/FreeFonts> which is a cool repo, but does not works completely along our version⦠we will need to merge :P)
My question was, why choose one above the other ?
I replaced it with the Source Sans Pro because same family fonts works better together (Source * Pro) cheers, Esteban
<Screen Shot 2014-12-02 at 11.57.13.png>
Doru
On Tue, Dec 2, 2014 at 11:35 AM, Sven Van Caekenberghe <sven@stfx.eu <mailto:sven@stfx.eu>> wrote: What is the difference between 'Open Sans' and 'Source Code Sans' ?
I am using the former in my 3.0 image, and I like it a bit more, it seems a bit wider.
On 02 Dec 2014, at 11:27, Tudor Girba <tudor@tudorgirba.com> wrote:
Great!
Doru
p.s. Finally :)
On Tue, Dec 2, 2014 at 9:48 AM, Esteban Lorenzano <estebanlm@gmail.com> wrote: Hi,
We changed the default fonts in Pharo for the ones that are used normally in Moose. They are: Source Sans Pro and Source Code Pro. We needed to do it for several reasons:
1) TxText (the new text model) is cairo based, and cairo just can work with real fonts, so we need them as default (now we will be able to integrate TxText and start the replace of old editors) 2) Current fonts takes too much space and do not scales fine (at least that Iâve been told)
So, well, that⦠you will see âsomething differentâ when you download latest image version :)
cheers, Esteban
-- www.tudorgirba.com
"Every thing has its own flow"
-- www.tudorgirba.com
"Every thing has its own flow"
On 02 Dec 2014, at 12:12, Esteban Lorenzano <estebanlm@gmail.com> wrote:
On 02 Dec 2014, at 12:02, Sven Van Caekenberghe <sven@stfx.eu> wrote:
On 02 Dec 2014, at 11:46, Tudor Girba <tudor@tudorgirba.com> wrote:
There is no Source Code Sans :). There is only "Source Sans Pro" or "Source Code Pro".
Yes, right now in the latest 4.0.
But there used to be a different one, that is the one I am using, see screenshot (http://www.google.com/fonts/specimen/Open+Sans). I don't remember where I got it from (Igor is the author), but I have been using it for months.
no, it was me the author⦠and it was a mistake I made first time thatâs why I removed it (but I can package it and put it somewhere anyway⦠I was even thinking on create a âFont Repositoryâ where put different fonts, until I found this: http://smalltalkhub.com/#!/~girba/FreeFonts which is a cool repo, but does not works completely along our version⦠we will need to merge :P)
Maybe it would be even better if there was code in the image to make these embedded fonts yourself (or a comment).
My question was, why choose one above the other ?
I replaced it with the Source Sans Pro because same family fonts works better together (Source * Pro)
OK. It seems to have a smaller width, we'll see.
cheers, Esteban
<Screen Shot 2014-12-02 at 11.57.13.png>
Doru
On Tue, Dec 2, 2014 at 11:35 AM, Sven Van Caekenberghe <sven@stfx.eu> wrote: What is the difference between 'Open Sans' and 'Source Code Sans' ?
I am using the former in my 3.0 image, and I like it a bit more, it seems a bit wider.
On 02 Dec 2014, at 11:27, Tudor Girba <tudor@tudorgirba.com> wrote:
Great!
Doru
p.s. Finally :)
On Tue, Dec 2, 2014 at 9:48 AM, Esteban Lorenzano <estebanlm@gmail.com> wrote: Hi,
We changed the default fonts in Pharo for the ones that are used normally in Moose. They are: Source Sans Pro and Source Code Pro. We needed to do it for several reasons:
1) TxText (the new text model) is cairo based, and cairo just can work with real fonts, so we need them as default (now we will be able to integrate TxText and start the replace of old editors) 2) Current fonts takes too much space and do not scales fine (at least that Iâve been told)
So, well, that⦠you will see âsomething differentâ when you download latest image version :)
cheers, Esteban
-- www.tudorgirba.com
"Every thing has its own flow"
-- www.tudorgirba.com
"Every thing has its own flow"
⦠and I lost fonts again :( I made an integration and fonts got lost⦠Iâm reviving issue, and working on it :( Esteban
On 02 Dec 2014, at 12:47, Sven Van Caekenberghe <sven@stfx.eu> wrote:
On 02 Dec 2014, at 12:12, Esteban Lorenzano <estebanlm@gmail.com> wrote:
On 02 Dec 2014, at 12:02, Sven Van Caekenberghe <sven@stfx.eu> wrote:
On 02 Dec 2014, at 11:46, Tudor Girba <tudor@tudorgirba.com> wrote:
There is no Source Code Sans :). There is only "Source Sans Pro" or "Source Code Pro".
Yes, right now in the latest 4.0.
But there used to be a different one, that is the one I am using, see screenshot (http://www.google.com/fonts/specimen/Open+Sans). I don't remember where I got it from (Igor is the author), but I have been using it for months.
no, it was me the author⦠and it was a mistake I made first time thatâs why I removed it (but I can package it and put it somewhere anyway⦠I was even thinking on create a âFont Repositoryâ where put different fonts, until I found this: http://smalltalkhub.com/#!/~girba/FreeFonts which is a cool repo, but does not works completely along our version⦠we will need to merge :P)
Maybe it would be even better if there was code in the image to make these embedded fonts yourself (or a comment).
My question was, why choose one above the other ?
I replaced it with the Source Sans Pro because same family fonts works better together (Source * Pro)
OK. It seems to have a smaller width, we'll see.
cheers, Esteban
<Screen Shot 2014-12-02 at 11.57.13.png>
Doru
On Tue, Dec 2, 2014 at 11:35 AM, Sven Van Caekenberghe <sven@stfx.eu> wrote: What is the difference between 'Open Sans' and 'Source Code Sans' ?
I am using the former in my 3.0 image, and I like it a bit more, it seems a bit wider.
On 02 Dec 2014, at 11:27, Tudor Girba <tudor@tudorgirba.com> wrote:
Great!
Doru
p.s. Finally :)
On Tue, Dec 2, 2014 at 9:48 AM, Esteban Lorenzano <estebanlm@gmail.com> wrote: Hi,
We changed the default fonts in Pharo for the ones that are used normally in Moose. They are: Source Sans Pro and Source Code Pro. We needed to do it for several reasons:
1) TxText (the new text model) is cairo based, and cairo just can work with real fonts, so we need them as default (now we will be able to integrate TxText and start the replace of old editors) 2) Current fonts takes too much space and do not scales fine (at least that Iâve been told)
So, well, that⦠you will see âsomething differentâ when you download latest image version :)
cheers, Esteban
-- www.tudorgirba.com
"Every thing has its own flow"
-- www.tudorgirba.com
"Every thing has its own flow"
Thanks, Esteban. This kind of work is too under appreciated. Cheers, Doru On Tue, Dec 2, 2014 at 1:10 PM, Esteban Lorenzano <estebanlm@gmail.com> wrote:
⦠and I lost fonts again :( I made an integration and fonts got lost⦠Iâm reviving issue, and working on it :(
Esteban
On 02 Dec 2014, at 12:47, Sven Van Caekenberghe <sven@stfx.eu> wrote:
On 02 Dec 2014, at 12:12, Esteban Lorenzano <estebanlm@gmail.com> wrote:
On 02 Dec 2014, at 12:02, Sven Van Caekenberghe <sven@stfx.eu> wrote:
On 02 Dec 2014, at 11:46, Tudor Girba <tudor@tudorgirba.com> wrote:
There is no Source Code Sans :). There is only "Source Sans Pro" or "Source Code Pro".
Yes, right now in the latest 4.0.
But there used to be a different one, that is the one I am using, see screenshot (http://www.google.com/fonts/specimen/Open+Sans). I don't remember where I got it from (Igor is the author), but I have been using it for months.
no, it was me the author⦠and it was a mistake I made first time thatâs why I removed it (but I can package it and put it somewhere anyway⦠I was even thinking on create a âFont Repositoryâ where put different fonts, until I found this: http://smalltalkhub.com/#!/~girba/FreeFonts which is a cool repo, but does not works completely along our version⦠we will need to merge :P)
Maybe it would be even better if there was code in the image to make these embedded fonts yourself (or a comment).
My question was, why choose one above the other ?
I replaced it with the Source Sans Pro because same family fonts works better together (Source * Pro)
OK. It seems to have a smaller width, we'll see.
cheers, Esteban
<Screen Shot 2014-12-02 at 11.57.13.png>
Doru
On Tue, Dec 2, 2014 at 11:35 AM, Sven Van Caekenberghe <sven@stfx.eu> wrote: What is the difference between 'Open Sans' and 'Source Code Sans' ?
I am using the former in my 3.0 image, and I like it a bit more, it seems a bit wider.
On 02 Dec 2014, at 11:27, Tudor Girba <tudor@tudorgirba.com> wrote:
Great!
Doru
p.s. Finally :)
On Tue, Dec 2, 2014 at 9:48 AM, Esteban Lorenzano <estebanlm@gmail.com> wrote: Hi,
We changed the default fonts in Pharo for the ones that are used normally in Moose. They are: Source Sans Pro and Source Code Pro. We needed to do it for several reasons:
1) TxText (the new text model) is cairo based, and cairo just can work with real fonts, so we need them as default (now we will be able to integrate TxText and start the replace of old editors) 2) Current fonts takes too much space and do not scales fine (at least that Iâve been told)
So, well, that⦠you will see âsomething differentâ when you download latest image version :)
cheers, Esteban
-- www.tudorgirba.com
"Every thing has its own flow"
-- www.tudorgirba.com
"Every thing has its own flow"
-- www.tudorgirba.com "Every thing has its own flow"
:) looks like I fixed it⦠weâll see in next integrations. Esteban
On 02 Dec 2014, at 13:31, Tudor Girba <tudor@tudorgirba.com> wrote:
Thanks, Esteban. This kind of work is too under appreciated.
Cheers, Doru
On Tue, Dec 2, 2014 at 1:10 PM, Esteban Lorenzano <estebanlm@gmail.com <mailto:estebanlm@gmail.com>> wrote: ⦠and I lost fonts again :( I made an integration and fonts got lost⦠Iâm reviving issue, and working on it :(
Esteban
On 02 Dec 2014, at 12:47, Sven Van Caekenberghe <sven@stfx.eu <mailto:sven@stfx.eu>> wrote:
On 02 Dec 2014, at 12:12, Esteban Lorenzano <estebanlm@gmail.com <mailto:estebanlm@gmail.com>> wrote:
On 02 Dec 2014, at 12:02, Sven Van Caekenberghe <sven@stfx.eu <mailto:sven@stfx.eu>> wrote:
On 02 Dec 2014, at 11:46, Tudor Girba <tudor@tudorgirba.com <mailto:tudor@tudorgirba.com>> wrote:
There is no Source Code Sans :). There is only "Source Sans Pro" or "Source Code Pro".
Yes, right now in the latest 4.0.
But there used to be a different one, that is the one I am using, see screenshot (http://www.google.com/fonts/specimen/Open+Sans <http://www.google.com/fonts/specimen/Open+Sans>). I don't remember where I got it from (Igor is the author), but I have been using it for months.
no, it was me the author⦠and it was a mistake I made first time thatâs why I removed it (but I can package it and put it somewhere anyway⦠I was even thinking on create a âFont Repositoryâ where put different fonts, until I found this: http://smalltalkhub.com/#!/~girba/FreeFonts <http://smalltalkhub.com/#!/~girba/FreeFonts> which is a cool repo, but does not works completely along our version⦠we will need to merge :P)
Maybe it would be even better if there was code in the image to make these embedded fonts yourself (or a comment).
My question was, why choose one above the other ?
I replaced it with the Source Sans Pro because same family fonts works better together (Source * Pro)
OK. It seems to have a smaller width, we'll see.
cheers, Esteban
<Screen Shot 2014-12-02 at 11.57.13.png>
Doru
On Tue, Dec 2, 2014 at 11:35 AM, Sven Van Caekenberghe <sven@stfx.eu <mailto:sven@stfx.eu>> wrote: What is the difference between 'Open Sans' and 'Source Code Sans' ?
I am using the former in my 3.0 image, and I like it a bit more, it seems a bit wider.
On 02 Dec 2014, at 11:27, Tudor Girba <tudor@tudorgirba.com <mailto:tudor@tudorgirba.com>> wrote:
Great!
Doru
p.s. Finally :)
On Tue, Dec 2, 2014 at 9:48 AM, Esteban Lorenzano <estebanlm@gmail.com <mailto:estebanlm@gmail.com>> wrote: Hi,
We changed the default fonts in Pharo for the ones that are used normally in Moose. They are: Source Sans Pro and Source Code Pro. We needed to do it for several reasons:
1) TxText (the new text model) is cairo based, and cairo just can work with real fonts, so we need them as default (now we will be able to integrate TxText and start the replace of old editors) 2) Current fonts takes too much space and do not scales fine (at least that Iâve been told)
So, well, that⦠you will see âsomething differentâ when you download latest image version :)
cheers, Esteban
-- www.tudorgirba.com <http://www.tudorgirba.com/>
"Every thing has its own flow"
-- www.tudorgirba.com <http://www.tudorgirba.com/>
"Every thing has its own flow"
-- www.tudorgirba.com <http://www.tudorgirba.com/>
"Every thing has its own flow"
Esteban, Did you look/read what Juraj Kubelka did ? Like this issue, but there are others too: https://pharo.fogbugz.com/f/cases/13967 I vaguely remember he found something wrt initialization, maybe Marcus remembers. Sven
On 02 Dec 2014, at 13:10, Esteban Lorenzano <estebanlm@gmail.com> wrote:
⦠and I lost fonts again :( I made an integration and fonts got lost⦠Iâm reviving issue, and working on it :(
Esteban
On 02 Dec 2014, at 12:47, Sven Van Caekenberghe <sven@stfx.eu> wrote:
On 02 Dec 2014, at 12:12, Esteban Lorenzano <estebanlm@gmail.com> wrote:
On 02 Dec 2014, at 12:02, Sven Van Caekenberghe <sven@stfx.eu> wrote:
On 02 Dec 2014, at 11:46, Tudor Girba <tudor@tudorgirba.com> wrote:
There is no Source Code Sans :). There is only "Source Sans Pro" or "Source Code Pro".
Yes, right now in the latest 4.0.
But there used to be a different one, that is the one I am using, see screenshot (http://www.google.com/fonts/specimen/Open+Sans). I don't remember where I got it from (Igor is the author), but I have been using it for months.
no, it was me the author⦠and it was a mistake I made first time thatâs why I removed it (but I can package it and put it somewhere anyway⦠I was even thinking on create a âFont Repositoryâ where put different fonts, until I found this: http://smalltalkhub.com/#!/~girba/FreeFonts which is a cool repo, but does not works completely along our version⦠we will need to merge :P)
Maybe it would be even better if there was code in the image to make these embedded fonts yourself (or a comment).
My question was, why choose one above the other ?
I replaced it with the Source Sans Pro because same family fonts works better together (Source * Pro)
OK. It seems to have a smaller width, we'll see.
cheers, Esteban
<Screen Shot 2014-12-02 at 11.57.13.png>
Doru
On Tue, Dec 2, 2014 at 11:35 AM, Sven Van Caekenberghe <sven@stfx.eu> wrote: What is the difference between 'Open Sans' and 'Source Code Sans' ?
I am using the former in my 3.0 image, and I like it a bit more, it seems a bit wider.
On 02 Dec 2014, at 11:27, Tudor Girba <tudor@tudorgirba.com> wrote:
Great!
Doru
p.s. Finally :)
On Tue, Dec 2, 2014 at 9:48 AM, Esteban Lorenzano <estebanlm@gmail.com> wrote: Hi,
We changed the default fonts in Pharo for the ones that are used normally in Moose. They are: Source Sans Pro and Source Code Pro. We needed to do it for several reasons:
1) TxText (the new text model) is cairo based, and cairo just can work with real fonts, so we need them as default (now we will be able to integrate TxText and start the replace of old editors) 2) Current fonts takes too much space and do not scales fine (at least that Iâve been told)
So, well, that⦠you will see âsomething differentâ when you download latest image version :)
cheers, Esteban
-- www.tudorgirba.com
"Every thing has its own flow"
-- www.tudorgirba.com
"Every thing has its own flow"
2014-12-02 13:36 GMT+01:00 Sven Van Caekenberghe <sven@stfx.eu>:
Esteban,
Did you look/read what Juraj Kubelka did ?
Like this issue, but there are others too:
https://pharo.fogbugz.com/default.asp?14048#110249 and cleanupForRelease reinitialize the font providers.
I vaguely remember he found something wrt initialization, maybe Marcus remembers.
Sven
On 02 Dec 2014, at 13:10, Esteban Lorenzano <estebanlm@gmail.com> wrote:
⦠and I lost fonts again :( I made an integration and fonts got lost⦠Iâm reviving issue, and working on it :(
Esteban
On 02 Dec 2014, at 12:47, Sven Van Caekenberghe <sven@stfx.eu> wrote:
On 02 Dec 2014, at 12:12, Esteban Lorenzano <estebanlm@gmail.com>
wrote:
On 02 Dec 2014, at 12:02, Sven Van Caekenberghe <sven@stfx.eu> wrote:
On 02 Dec 2014, at 11:46, Tudor Girba <tudor@tudorgirba.com> wrote:
There is no Source Code Sans :). There is only "Source Sans Pro" or
"Source Code Pro".
Yes, right now in the latest 4.0.
But there used to be a different one, that is the one I am using, see
screenshot (http://www.google.com/fonts/specimen/Open+Sans). I don't remember where I got it from (Igor is the author), but I have been using it for months.
no, it was me the author⦠and it was a mistake I made first time thatâs why I removed it (but I can package it and put it somewhere anyway⦠I was even thinking on create a âFont Repositoryâ where put different fonts, until I found this: http://smalltalkhub.com/#!/~girba/FreeFonts which is a cool repo, but does not works completely along our version⦠we will need to merge :P)
Maybe it would be even better if there was code in the image to make these embedded fonts yourself (or a comment).
My question was, why choose one above the other ?
I replaced it with the Source Sans Pro because same family fonts works better together (Source * Pro)
OK. It seems to have a smaller width, we'll see.
cheers, Esteban
<Screen Shot 2014-12-02 at 11.57.13.png>
Doru
On Tue, Dec 2, 2014 at 11:35 AM, Sven Van Caekenberghe <sven@stfx.eu>
wrote:
What is the difference between 'Open Sans' and 'Source Code Sans' ?
I am using the former in my 3.0 image, and I like it a bit more, it seems a bit wider.
On 02 Dec 2014, at 11:27, Tudor Girba <tudor@tudorgirba.com> wrote:
Great!
Doru
p.s. Finally :)
On Tue, Dec 2, 2014 at 9:48 AM, Esteban Lorenzano < estebanlm@gmail.com> wrote: Hi,
We changed the default fonts in Pharo for the ones that are used normally in Moose. They are: Source Sans Pro and Source Code Pro. We needed to do it for several reasons:
1) TxText (the new text model) is cairo based, and cairo just can work with real fonts, so we need them as default (now we will be able to integrate TxText and start the replace of old editors) 2) Current fonts takes too much space and do not scales fine (at least that Iâve been told)
So, well, that⦠you will see âsomething differentâ when you download latest image version :)
cheers, Esteban
-- www.tudorgirba.com
"Every thing has its own flow"
-- www.tudorgirba.com
"Every thing has its own flow"
I am not sure if I follow the discussion, but next week I am planning to extract embedded fonts and make a new embedded provider. The current solution I have made recently is too tight, there are cyclic dependencies between free font type provider and embedded fonts and it causes problems. Cheers, Juraj
On Dec 2, 2014, at 9:36 AM, Sven Van Caekenberghe <sven@stfx.eu> wrote:
Esteban,
Did you look/read what Juraj Kubelka did ?
Like this issue, but there are others too:
https://pharo.fogbugz.com/f/cases/13967
I vaguely remember he found something wrt initialization, maybe Marcus remembers.
Sven
On 02 Dec 2014, at 13:10, Esteban Lorenzano <estebanlm@gmail.com> wrote:
⦠and I lost fonts again :( I made an integration and fonts got lost⦠Iâm reviving issue, and working on it :(
Esteban
On 02 Dec 2014, at 12:47, Sven Van Caekenberghe <sven@stfx.eu> wrote:
On 02 Dec 2014, at 12:12, Esteban Lorenzano <estebanlm@gmail.com> wrote:
On 02 Dec 2014, at 12:02, Sven Van Caekenberghe <sven@stfx.eu> wrote:
On 02 Dec 2014, at 11:46, Tudor Girba <tudor@tudorgirba.com> wrote:
There is no Source Code Sans :). There is only "Source Sans Pro" or "Source Code Pro".
Yes, right now in the latest 4.0.
But there used to be a different one, that is the one I am using, see screenshot (http://www.google.com/fonts/specimen/Open+Sans). I don't remember where I got it from (Igor is the author), but I have been using it for months.
no, it was me the author⦠and it was a mistake I made first time thatâs why I removed it (but I can package it and put it somewhere anyway⦠I was even thinking on create a âFont Repositoryâ where put different fonts, until I found this: http://smalltalkhub.com/#!/~girba/FreeFonts which is a cool repo, but does not works completely along our version⦠we will need to merge :P)
Maybe it would be even better if there was code in the image to make these embedded fonts yourself (or a comment).
My question was, why choose one above the other ?
I replaced it with the Source Sans Pro because same family fonts works better together (Source * Pro)
OK. It seems to have a smaller width, we'll see.
cheers, Esteban
<Screen Shot 2014-12-02 at 11.57.13.png>
Doru
On Tue, Dec 2, 2014 at 11:35 AM, Sven Van Caekenberghe <sven@stfx.eu> wrote: What is the difference between 'Open Sans' and 'Source Code Sans' ?
I am using the former in my 3.0 image, and I like it a bit more, it seems a bit wider.
On 02 Dec 2014, at 11:27, Tudor Girba <tudor@tudorgirba.com> wrote:
Great!
Doru
p.s. Finally :)
On Tue, Dec 2, 2014 at 9:48 AM, Esteban Lorenzano <estebanlm@gmail.com> wrote: Hi,
We changed the default fonts in Pharo for the ones that are used normally in Moose. They are: Source Sans Pro and Source Code Pro. We needed to do it for several reasons:
1) TxText (the new text model) is cairo based, and cairo just can work with real fonts, so we need them as default (now we will be able to integrate TxText and start the replace of old editors) 2) Current fonts takes too much space and do not scales fine (at least that Iâve been told)
So, well, that⦠you will see âsomething differentâ when you download latest image version :)
cheers, Esteban
-- www.tudorgirba.com
"Every thing has its own flow"
-- www.tudorgirba.com
"Every thing has its own flow"
Hi Juraj Excellent. I would like to have a nice way to import ttf and install not an horrible method full of binary data but a method that load a ttf and that creates font description directly. And as Pharo we should have a simple font ttf file server. Stef Le 2/12/14 15:02, Juraj Kubelka a écrit :
I am not sure if I follow the discussion, but next week I am planning to extract embedded fonts and make a new embedded provider. The current solution I have made recently is too tight, there are cyclic dependencies between free font type provider and embedded fonts and it causes problems.
Cheers, Juraj
On Dec 2, 2014, at 9:36 AM, Sven Van Caekenberghe <sven@stfx.eu> wrote:
Esteban,
Did you look/read what Juraj Kubelka did ?
Like this issue, but there are others too:
https://pharo.fogbugz.com/f/cases/13967
I vaguely remember he found something wrt initialization, maybe Marcus remembers.
Sven
On 02 Dec 2014, at 13:10, Esteban Lorenzano <estebanlm@gmail.com> wrote:
⦠and I lost fonts again :( I made an integration and fonts got lost⦠Iâm reviving issue, and working on it :(
Esteban
On 02 Dec 2014, at 12:47, Sven Van Caekenberghe <sven@stfx.eu> wrote:
On 02 Dec 2014, at 12:12, Esteban Lorenzano <estebanlm@gmail.com> wrote:
On 02 Dec 2014, at 12:02, Sven Van Caekenberghe <sven@stfx.eu> wrote:
On 02 Dec 2014, at 11:46, Tudor Girba <tudor@tudorgirba.com> wrote:
There is no Source Code Sans :). There is only "Source Sans Pro" or "Source Code Pro". Yes, right now in the latest 4.0.
But there used to be a different one, that is the one I am using, see screenshot (http://www.google.com/fonts/specimen/Open+Sans). I don't remember where I got it from (Igor is the author), but I have been using it for months. no, it was me the author⦠and it was a mistake I made first time thatâs why I removed it (but I can package it and put it somewhere anyway⦠I was even thinking on create a âFont Repositoryâ where put different fonts, until I found this: http://smalltalkhub.com/#!/~girba/FreeFonts which is a cool repo, but does not works completely along our version⦠we will need to merge :P) Maybe it would be even better if there was code in the image to make these embedded fonts yourself (or a comment).
My question was, why choose one above the other ? I replaced it with the Source Sans Pro because same family fonts works better together (Source * Pro) OK. It seems to have a smaller width, we'll see.
cheers, Esteban
<Screen Shot 2014-12-02 at 11.57.13.png>
Doru
On Tue, Dec 2, 2014 at 11:35 AM, Sven Van Caekenberghe <sven@stfx.eu> wrote: What is the difference between 'Open Sans' and 'Source Code Sans' ?
I am using the former in my 3.0 image, and I like it a bit more, it seems a bit wider.
On 02 Dec 2014, at 11:27, Tudor Girba <tudor@tudorgirba.com> wrote:
Great!
Doru
p.s. Finally :)
On Tue, Dec 2, 2014 at 9:48 AM, Esteban Lorenzano <estebanlm@gmail.com> wrote: Hi,
We changed the default fonts in Pharo for the ones that are used normally in Moose. They are: Source Sans Pro and Source Code Pro. We needed to do it for several reasons:
1) TxText (the new text model) is cairo based, and cairo just can work with real fonts, so we need them as default (now we will be able to integrate TxText and start the replace of old editors) 2) Current fonts takes too much space and do not scales fine (at least that Iâve been told)
So, well, that⦠you will see âsomething differentâ when you download latest image version :)
cheers, Esteban
-- www.tudorgirba.com
"Every thing has its own flow"
-- www.tudorgirba.com
"Every thing has its own flow"
Hi Juraj Excellent. I would like to have a nice way to import ttf and install not an horrible method full of binary data but a method that load a ttf and that creates font description directly. And as Pharo we should have a simple font ttf file server. Stef Le 2/12/14 15:02, Juraj Kubelka a écrit :
I am not sure if I follow the discussion, but next week I am planning to extract embedded fonts and make a new embedded provider. The current solution I have made recently is too tight, there are cyclic dependencies between free font type provider and embedded fonts and it causes problems.
Cheers, Juraj
On Dec 2, 2014, at 9:36 AM, Sven Van Caekenberghe<sven@stfx.eu> wrote:
Esteban,
Did you look/read what Juraj Kubelka did ?
Like this issue, but there are others too:
https://pharo.fogbugz.com/f/cases/13967
I vaguely remember he found something wrt initialization, maybe Marcus remembers.
Sven
On 02 Dec 2014, at 13:10, Esteban Lorenzano<estebanlm@gmail.com> wrote:
⦠and I lost fonts again :( I made an integration and fonts got lost⦠Iâm reviving issue, and working on it :(
Esteban
On 02 Dec 2014, at 12:47, Sven Van Caekenberghe<sven@stfx.eu> wrote:
On 02 Dec 2014, at 12:12, Esteban Lorenzano<estebanlm@gmail.com> wrote:
On 02 Dec 2014, at 12:02, Sven Van Caekenberghe<sven@stfx.eu> wrote:
On 02 Dec 2014, at 11:46, Tudor Girba<tudor@tudorgirba.com> wrote:
There is no Source Code Sans :). There is only "Source Sans Pro" or "Source Code Pro". Yes, right now in the latest 4.0.
But there used to be a different one, that is the one I am using, see screenshot (http://www.google.com/fonts/specimen/Open+Sans). I don't remember where I got it from (Igor is the author), but I have been using it for months. no, it was me the author⦠and it was a mistake I made first time thatâs why I removed it (but I can package it and put it somewhere anyway⦠I was even thinking on create a âFont Repositoryâ where put different fonts, until I found this:http://smalltalkhub.com/#!/~girba/FreeFonts which is a cool repo, but does not works completely along our version⦠we will need to merge :P) Maybe it would be even better if there was code in the image to make these embedded fonts yourself (or a comment).
My question was, why choose one above the other ? I replaced it with the Source Sans Pro because same family fonts works better together (Source * Pro) OK. It seems to have a smaller width, we'll see.
cheers, Esteban
<Screen Shot 2014-12-02 at 11.57.13.png>
Doru
On Tue, Dec 2, 2014 at 11:35 AM, Sven Van Caekenberghe<sven@stfx.eu> wrote: What is the difference between 'Open Sans' and 'Source Code Sans' ?
I am using the former in my 3.0 image, and I like it a bit more, it seems a bit wider.
On 02 Dec 2014, at 11:27, Tudor Girba<tudor@tudorgirba.com> wrote:
Great!
Doru
p.s. Finally :)
On Tue, Dec 2, 2014 at 9:48 AM, Esteban Lorenzano<estebanlm@gmail.com> wrote: Hi,
We changed the default fonts in Pharo for the ones that are used normally in Moose. They are: Source Sans Pro and Source Code Pro. We needed to do it for several reasons:
1) TxText (the new text model) is cairo based, and cairo just can work with real fonts, so we need them as default (now we will be able to integrate TxText and start the replace of old editors) 2) Current fonts takes too much space and do not scales fine (at least that Iâve been told)
So, well, that⦠you will see âsomething differentâ when you download latest image version :)
cheers, Esteban
-- www.tudorgirba.com
"Every thing has its own flow"
-- www.tudorgirba.com
"Every thing has its own flow"
It would be good to avoid to duplicate the font description as binary and the font description as object. It would be nice to also have a nice way to import font from the ttf description files. This is what we should put on a server not pharo method containaing binary that after creates object and create duplication. Stef
It would be good to avoid to duplicate the font description as binary and the font description as object. It would be nice to also have a nice way to import font from the ttf description files. This is what we should put on a server not pharo method containaing binary. Stef
On 02 Dec 2014, at 11:35, Sven Van Caekenberghe <sven@stfx.eu> wrote:
What is the difference between 'Open Sans' and 'Source Code Sans' ?
well, they are different fonts ;) now we have two FT fonts in image: - Source Sans Pro: proportional - Source Code Pro: monospaced cheers, Esteban
I am using the former in my 3.0 image, and I like it a bit more, it seems a bit wider.
On 02 Dec 2014, at 11:27, Tudor Girba <tudor@tudorgirba.com> wrote:
Great!
Doru
p.s. Finally :)
On Tue, Dec 2, 2014 at 9:48 AM, Esteban Lorenzano <estebanlm@gmail.com> wrote: Hi,
We changed the default fonts in Pharo for the ones that are used normally in Moose. They are: Source Sans Pro and Source Code Pro. We needed to do it for several reasons:
1) TxText (the new text model) is cairo based, and cairo just can work with real fonts, so we need them as default (now we will be able to integrate TxText and start the replace of old editors) 2) Current fonts takes too much space and do not scales fine (at least that Iâve been told)
So, well, that⦠you will see âsomething differentâ when you download latest image version :)
cheers, Esteban
-- www.tudorgirba.com
"Every thing has its own flow"
On 02 Dec 2014, at 11:27, Tudor Girba <tudor@tudorgirba.com> wrote:
Great!
Doru
p.s. Finally :)
yeah, it took far too much time :(
On Tue, Dec 2, 2014 at 9:48 AM, Esteban Lorenzano <estebanlm@gmail.com <mailto:estebanlm@gmail.com>> wrote: Hi,
We changed the default fonts in Pharo for the ones that are used normally in Moose. They are: Source Sans Pro and Source Code Pro. We needed to do it for several reasons:
1) TxText (the new text model) is cairo based, and cairo just can work with real fonts, so we need them as default (now we will be able to integrate TxText and start the replace of old editors) 2) Current fonts takes too much space and do not scales fine (at least that Iâve been told)
So, well, that⦠you will see âsomething differentâ when you download latest image version :)
cheers, Esteban
-- www.tudorgirba.com <http://www.tudorgirba.com/>
"Every thing has its own flow"
participants (9)
-
Esteban Lorenzano -
Juraj Kubelka -
kilon alios -
Nicolai Hess -
Santiago Bragagnolo -
stepharo -
Sven Van Caekenberghe -
Tudor Girba -
Yuriy Tymchuk