Athens and StrikeFont ( again )
If I take a fresh pharo image I always have to reenable FT fonts before doing any athens rendering with text (RMOD StrikeFont(Object)>>doesNotUnderstand: #getPreciseHeight). Ok, I know I have to open settings disable then enable FreeType and choose a FreeType font. But what exactly is the problem with Athens rendering and non FT fonts? Nicolai
Times to times, font are displayed in a very weir fashion: small and big letter. Width is not properly computed in addition. Alexandre
Le 19-06-2014 à 18:26, Nicolai Hess <nicolaihess@web.de> a écrit :
If I take a fresh pharo image I always have to reenable FT fonts before doing any athens rendering with text (RMOD StrikeFont(Object)>>doesNotUnderstand: #getPreciseHeight).
Ok, I know I have to open settings disable then enable FreeType and choose a FreeType font.
But what exactly is the problem with Athens rendering and non FT fonts?
Nicolai
On 20 June 2014 02:01, Alexandre Bergel <alexandre.bergel@me.com> wrote:
Times to times, font are displayed in a very weir fashion: small and big letter. Width is not properly computed in addition.
that should be fixed already.. i will check.
Alexandre
Le 19-06-2014 à 18:26, Nicolai Hess <nicolaihess@web.de> a écrit :
If I take a fresh pharo image I always have to reenable FT fonts before doing any athens rendering with text (RMOD StrikeFont(Object)>>doesNotUnderstand: #getPreciseHeight).
Ok, I know I have to open settings disable then enable FreeType and choose a FreeType font.
But what exactly is the problem with Athens rendering and non FT fonts?
Nicolai
-- Best regards, Igor Stasenko.
We thought so, too. But the problem manifests itself again on the latest Pharo 3.0. Thanks for checking and let us know if we can do something! Doru On Fri, Jun 20, 2014 at 12:53 PM, Igor Stasenko <siguctua@gmail.com> wrote:
On 20 June 2014 02:01, Alexandre Bergel <alexandre.bergel@me.com> wrote:
Times to times, font are displayed in a very weir fashion: small and big letter. Width is not properly computed in addition.
that should be fixed already.. i will check.
Alexandre
Le 19-06-2014 à 18:26, Nicolai Hess <nicolaihess@web.de> a écrit :
If I take a fresh pharo image I always have to reenable FT fonts before doing any athens rendering with text (RMOD StrikeFont(Object)>>doesNotUnderstand: #getPreciseHeight).
Ok, I know I have to open settings disable then enable FreeType and choose a FreeType font.
But what exactly is the problem with Athens rendering and non FT fonts?
Nicolai
-- Best regards, Igor Stasenko.
-- www.tudorgirba.com "Every thing has its own flow"
On 20 June 2014 13:40, Tudor Girba <tudor@tudorgirba.com> wrote:
We thought so, too. But the problem manifests itself again on the latest Pharo 3.0.
Thanks for checking and let us know if we can do something!
Sure, you can do: make sure you don't render text with same font in Morphic UI and Athens, so they don't interfere with each other. There's no easy way to get rid of interference, because it would require changing Freetype package and its plugin in order to establish a single font management point and funnel all requests to freetype library through it.
Doru
On Fri, Jun 20, 2014 at 12:53 PM, Igor Stasenko <siguctua@gmail.com> wrote:
On 20 June 2014 02:01, Alexandre Bergel <alexandre.bergel@me.com> wrote:
Times to times, font are displayed in a very weir fashion: small and big letter. Width is not properly computed in addition.
that should be fixed already.. i will check.
Alexandre
Le 19-06-2014 à 18:26, Nicolai Hess <nicolaihess@web.de> a écrit :
If I take a fresh pharo image I always have to reenable FT fonts before doing any athens rendering with text (RMOD StrikeFont(Object)>>doesNotUnderstand: #getPreciseHeight).
Ok, I know I have to open settings disable then enable FreeType and choose a FreeType font.
But what exactly is the problem with Athens rendering and non FT fonts?
Nicolai
-- Best regards, Igor Stasenko.
-- www.tudorgirba.com
"Every thing has its own flow"
-- Best regards, Igor Stasenko.
I do not understand. I think we are talking about two different things. Alex and I are talking about wrong rendering of FT fonts in Athens. A problem that looks similar to what we had before. Our issue has nothing to do with StrikeFont. Cheers, Doru On Fri, Jun 20, 2014 at 3:32 PM, Igor Stasenko <siguctua@gmail.com> wrote:
On 20 June 2014 13:40, Tudor Girba <tudor@tudorgirba.com> wrote:
We thought so, too. But the problem manifests itself again on the latest Pharo 3.0.
Thanks for checking and let us know if we can do something!
Sure, you can do: make sure you don't render text with same font in Morphic UI and Athens, so they don't interfere with each other. There's no easy way to get rid of interference, because it would require changing Freetype package and its plugin in order to establish a single font management point and funnel all requests to freetype library through it.
Doru
On Fri, Jun 20, 2014 at 12:53 PM, Igor Stasenko <siguctua@gmail.com> wrote:
On 20 June 2014 02:01, Alexandre Bergel <alexandre.bergel@me.com> wrote:
Times to times, font are displayed in a very weir fashion: small and big letter. Width is not properly computed in addition.
that should be fixed already.. i will check.
Alexandre
Le 19-06-2014 à 18:26, Nicolai Hess <nicolaihess@web.de> a écrit :
If I take a fresh pharo image I always have to reenable FT fonts before doing any athens rendering with text (RMOD StrikeFont(Object)>>doesNotUnderstand: #getPreciseHeight).
Ok, I know I have to open settings disable then enable FreeType and choose a FreeType font.
But what exactly is the problem with Athens rendering and non FT fonts?
Nicolai
-- Best regards, Igor Stasenko.
-- www.tudorgirba.com
"Every thing has its own flow"
-- Best regards, Igor Stasenko.
-- www.tudorgirba.com "Every thing has its own flow"
+1 -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. On Jun 20, 2014, at 10:32 AM, Tudor Girba <tudor@tudorgirba.com> wrote:
I do not understand.
I think we are talking about two different things. Alex and I are talking about wrong rendering of FT fonts in Athens. A problem that looks similar to what we had before. Our issue has nothing to do with StrikeFont.
Cheers, Doru
On Fri, Jun 20, 2014 at 3:32 PM, Igor Stasenko <siguctua@gmail.com> wrote:
On 20 June 2014 13:40, Tudor Girba <tudor@tudorgirba.com> wrote: We thought so, too. But the problem manifests itself again on the latest Pharo 3.0.
Thanks for checking and let us know if we can do something!
Sure, you can do: make sure you don't render text with same font in Morphic UI and Athens, so they don't interfere with each other. There's no easy way to get rid of interference, because it would require changing Freetype package and its plugin in order to establish a single font management point and funnel all requests to freetype library through it.
Doru
On Fri, Jun 20, 2014 at 12:53 PM, Igor Stasenko <siguctua@gmail.com> wrote:
On 20 June 2014 02:01, Alexandre Bergel <alexandre.bergel@me.com> wrote: Times to times, font are displayed in a very weir fashion: small and big letter. Width is not properly computed in addition.
that should be fixed already.. i will check.
Alexandre
Le 19-06-2014 à 18:26, Nicolai Hess <nicolaihess@web.de> a écrit :
If I take a fresh pharo image I always have to reenable FT fonts before doing any athens rendering with text (RMOD StrikeFont(Object)>>doesNotUnderstand: #getPreciseHeight).
Ok, I know I have to open settings disable then enable FreeType and choose a FreeType font.
But what exactly is the problem with Athens rendering and non FT fonts?
Nicolai
-- Best regards, Igor Stasenko.
-- www.tudorgirba.com
"Every thing has its own flow"
-- Best regards, Igor Stasenko.
-- www.tudorgirba.com
"Every thing has its own flow"
On Fri, Jun 20, 2014 at 7:32 AM, Tudor Girba <tudor@tudorgirba.com> wrote:
I do not understand.
I think we are talking about two different things. Alex and I are talking about wrong rendering of FT fonts in Athens. A problem that looks similar to what we had before. Our issue has nothing to do with StrikeFont.
You can (and Pharo does) use FT fonts in Morphic. I think he is asking that the font you want to use in Athens be something different than what is already chosen to be used in the rest of the system used in Morphic (such as browser/workspace fonts). -cbc
Cheers, Doru
On Fri, Jun 20, 2014 at 3:32 PM, Igor Stasenko <siguctua@gmail.com> wrote:
On 20 June 2014 13:40, Tudor Girba <tudor@tudorgirba.com> wrote:
We thought so, too. But the problem manifests itself again on the latest Pharo 3.0.
Thanks for checking and let us know if we can do something!
Sure, you can do: make sure you don't render text with same font in Morphic UI and Athens, so they don't interfere with each other. There's no easy way to get rid of interference, because it would require changing Freetype package and its plugin in order to establish a single font management point and funnel all requests to freetype library through it.
Doru
On Fri, Jun 20, 2014 at 12:53 PM, Igor Stasenko <siguctua@gmail.com> wrote:
On 20 June 2014 02:01, Alexandre Bergel <alexandre.bergel@me.com> wrote:
Times to times, font are displayed in a very weir fashion: small and big letter. Width is not properly computed in addition.
that should be fixed already.. i will check.
Alexandre
Le 19-06-2014 à 18:26, Nicolai Hess <nicolaihess@web.de> a écrit :
If I take a fresh pharo image I always have to reenable FT fonts before doing any athens rendering with text (RMOD StrikeFont(Object)>>doesNotUnderstand: #getPreciseHeight).
Ok, I know I have to open settings disable then enable FreeType and choose a FreeType font.
But what exactly is the problem with Athens rendering and non FT fonts?
Nicolai
-- Best regards, Igor Stasenko.
-- www.tudorgirba.com
"Every thing has its own flow"
-- Best regards, Igor Stasenko.
-- www.tudorgirba.com
"Every thing has its own flow"
Why is that? Doru On Fri, Jun 20, 2014 at 7:46 PM, Chris Cunningham <cunningham.cb@gmail.com> wrote:
On Fri, Jun 20, 2014 at 7:32 AM, Tudor Girba <tudor@tudorgirba.com> wrote:
I do not understand.
I think we are talking about two different things. Alex and I are talking about wrong rendering of FT fonts in Athens. A problem that looks similar to what we had before. Our issue has nothing to do with StrikeFont.
You can (and Pharo does) use FT fonts in Morphic. I think he is asking that the font you want to use in Athens be something different than what is already chosen to be used in the rest of the system used in Morphic (such as browser/workspace fonts). -cbc
Cheers, Doru
On Fri, Jun 20, 2014 at 3:32 PM, Igor Stasenko <siguctua@gmail.com> wrote:
On 20 June 2014 13:40, Tudor Girba <tudor@tudorgirba.com> wrote:
We thought so, too. But the problem manifests itself again on the latest Pharo 3.0.
Thanks for checking and let us know if we can do something!
Sure, you can do: make sure you don't render text with same font in Morphic UI and Athens, so they don't interfere with each other. There's no easy way to get rid of interference, because it would require changing Freetype package and its plugin in order to establish a single font management point and funnel all requests to freetype library through it.
Doru
On Fri, Jun 20, 2014 at 12:53 PM, Igor Stasenko <siguctua@gmail.com> wrote:
On 20 June 2014 02:01, Alexandre Bergel <alexandre.bergel@me.com> wrote:
Times to times, font are displayed in a very weir fashion: small and big letter. Width is not properly computed in addition.
that should be fixed already.. i will check.
Alexandre
Le 19-06-2014 à 18:26, Nicolai Hess <nicolaihess@web.de> a écrit :
If I take a fresh pharo image I always have to reenable FT fonts before doing any athens rendering with text (RMOD StrikeFont(Object)>>doesNotUnderstand: #getPreciseHeight).
Ok, I know I have to open settings disable then enable FreeType and choose a FreeType font.
But what exactly is the problem with Athens rendering and non FT fonts?
Nicolai
-- Best regards, Igor Stasenko.
-- www.tudorgirba.com
"Every thing has its own flow"
-- Best regards, Igor Stasenko.
-- www.tudorgirba.com
"Every thing has its own flow"
-- www.tudorgirba.com "Every thing has its own flow"
Gi Igor, For DrGeo it is not a workable option to have different fonts in Morphic widget and Athens canvas (I explained earlier why). However I found the scaling trick of draw text to work reasonably well. Not full perfect as from time to time I can see some artifact. Thanks Hilaire Le 20/06/2014 15:32, Igor Stasenko a écrit :
Sure, you can do: make sure you don't render text with same font in Morphic UI and Athens, so they don't interfere with each other. There's no easy way to get rid of interference, because it would require changing Freetype package and its plugin in order to establish a single font management point and funnel all requests to freetype library through it.
-- Dr. Geo http://drgeo.eu iStoa - https://launchpad.net/istoa
The real question was: Why can't we draw a text with StrikeFont and with Athens. Igor, can't we use AthensCairoText (cairo toy text api) for non-truetype fonts? 2014-06-21 1:20 GMT+02:00 Hilaire Fernandes <hilaire.fernandes@gmail.com>:
Gi Igor,
For DrGeo it is not a workable option to have different fonts in Morphic widget and Athens canvas (I explained earlier why). However I found the scaling trick of draw text to work reasonably well. Not full perfect as from time to time I can see some artifact.
Thanks
Hilaire
Le 20/06/2014 15:32, Igor Stasenko a écrit :
Sure, you can do: make sure you don't render text with same font in Morphic UI and Athens, so they don't interfere with each other. There's no easy way to get rid of interference, because it would require changing Freetype package and its plugin in order to establish a single font management point and funnel all requests to freetype library through it.
-- Dr. Geo http://drgeo.eu iStoa - https://launchpad.net/istoa
On 30 June 2014 21:36, Nicolai Hess <nicolaihess@web.de> wrote:
The real question was: Why can't we draw a text with StrikeFont and with Athens.
Igor, can't we use AthensCairoText (cairo toy text api) for non-truetype fonts?
Because strike fonts are stored in special format which you cannot render directly by cairo library. Because strike fonts are not scalable. Because it will be horribly slow. Choose one.
2014-06-21 1:20 GMT+02:00 Hilaire Fernandes <hilaire.fernandes@gmail.com>:
Gi Igor,
For DrGeo it is not a workable option to have different fonts in Morphic widget and Athens canvas (I explained earlier why). However I found the scaling trick of draw text to work reasonably well. Not full perfect as from time to time I can see some artifact.
Thanks
Hilaire
Le 20/06/2014 15:32, Igor Stasenko a écrit :
Sure, you can do: make sure you don't render text with same font in Morphic UI and Athens, so they don't interfere with each other. There's no easy way to get rid of interference, because it would require changing Freetype package and its plugin in order to establish a single font management point and funnel all requests to freetype library through it.
-- Dr. Geo http://drgeo.eu iStoa - https://launchpad.net/istoa
-- Best regards, Igor Stasenko.
2014-07-01 3:16 GMT+02:00 Igor Stasenko <siguctua@gmail.com>:
On 30 June 2014 21:36, Nicolai Hess <nicolaihess@web.de> wrote:
The real question was: Why can't we draw a text with StrikeFont and with Athens.
Igor, can't we use AthensCairoText (cairo toy text api) for non-truetype fonts?
Because strike fonts are stored in special format which you cannot render directly by cairo library. Because strike fonts are not scalable. Because it will be horribly slow. Choose one.
I choose the first one, horrible slow or not scaleable is better than a drawing error :) If someday all rendering is done through Athens, how do we solve this problem with the StrikeFont?
2014-06-21 1:20 GMT+02:00 Hilaire Fernandes <hilaire.fernandes@gmail.com> :
Gi Igor,
For DrGeo it is not a workable option to have different fonts in Morphic widget and Athens canvas (I explained earlier why). However I found the scaling trick of draw text to work reasonably well. Not full perfect as from time to time I can see some artifact.
Thanks
Hilaire
Le 20/06/2014 15:32, Igor Stasenko a écrit :
Sure, you can do: make sure you don't render text with same font in Morphic UI and Athens, so they don't interfere with each other. There's no easy way to get rid of interference, because it would require changing Freetype package and its plugin in order to establish a single font management point and funnel all requests to freetype library through it.
-- Dr. Geo http://drgeo.eu iStoa - https://launchpad.net/istoa
-- Best regards, Igor Stasenko.
On 01.07.2014 22:05, Nicolai Hess wrote:
2014-07-01 3:16 GMT+02:00 Igor Stasenko <siguctua@gmail.com <mailto:siguctua@gmail.com>>:
On 30 June 2014 21:36, Nicolai Hess <nicolaihess@web.de <mailto:nicolaihess@web.de>> wrote:
The real question was: Why can't we draw a text with StrikeFont and with Athens.
Igor, can't we use AthensCairoText (cairo toy text api) for non-truetype fonts?
Because strike fonts are stored in special format which you cannot render directly by cairo library. Because strike fonts are not scalable. Because it will be horribly slow. Choose one.
I choose the first one, horrible slow or not scaleable is better than a drawing error :)
If someday all rendering is done through Athens, how do we solve this problem with the StrikeFont?
You would have to implement a special rendering path for StrikeFonts utilizing essentially the same method used for rendering bitmaps. In theory, if cairo bitmap perf is about the same as traditional bitmap perf, that'd be about as slow as FT-rendering is in non-cairo images, if there's no scaling involved. Scaled, it would probably look horrible, take a screenshot of this mail, zoom to 400% in Paint or something, that's what to expect. (Though, one *could* do some tricks translating point size /scale factor to another font with point size closer to the final result (if one exists) and get slightly less horrible results) Cheers, Henry
2014-07-02 10:00 GMT+02:00 Henrik Sperre Johansen < henrik.s.johansen@veloxit.no>:
On 01.07.2014 22:05, Nicolai Hess wrote:
2014-07-01 3:16 GMT+02:00 Igor Stasenko <siguctua@gmail.com>:
On 30 June 2014 21:36, Nicolai Hess <nicolaihess@web.de> wrote:
The real question was: Why can't we draw a text with StrikeFont and with Athens.
Igor, can't we use AthensCairoText (cairo toy text api) for non-truetype fonts?
Because strike fonts are stored in special format which you cannot render directly by cairo library. Because strike fonts are not scalable. Because it will be horribly slow. Choose one.
I choose the first one, horrible slow or not scaleable is better than a drawing error :)
If someday all rendering is done through Athens, how do we solve this problem with the StrikeFont?
You would have to implement a special rendering path for StrikeFonts utilizing essentially the same method used for rendering bitmaps. In theory, if cairo bitmap perf is about the same as traditional bitmap perf, that'd be about as slow as FT-rendering is in non-cairo images, if there's no scaling involved. Scaled, it would probably look horrible, take a screenshot of this mail, zoom to 400% in Paint or something, that's what to expect. (Though, one *could* do some tricks translating point size /scale factor to another font with point size closer to the final result (if one exists) and get slightly less horrible results)
another solution in: 13458 <https://pharo.fogbugz.com/default.asp?13458> Rendering text with Athens and StrikeFonts Here I use Athens/Cairos simple text api. Maybe not a good solution, but it is better than the drawing error, I think.
Cheers, Henry
I am not quite convinced we should solve it, actually. We survived for a long time without TT fonts. Now that we finally have them, I think we can manage to survive without Bitmap fonts, too :) Cheers, Doru On Tue, Jul 1, 2014 at 10:05 PM, Nicolai Hess <nicolaihess@web.de> wrote:
2014-07-01 3:16 GMT+02:00 Igor Stasenko <siguctua@gmail.com>:
On 30 June 2014 21:36, Nicolai Hess <nicolaihess@web.de> wrote:
The real question was: Why can't we draw a text with StrikeFont and with Athens.
Igor, can't we use AthensCairoText (cairo toy text api) for non-truetype fonts?
Because strike fonts are stored in special format which you cannot render directly by cairo library. Because strike fonts are not scalable. Because it will be horribly slow. Choose one.
I choose the first one, horrible slow or not scaleable is better than a drawing error :)
If someday all rendering is done through Athens, how do we solve this problem with the StrikeFont?
2014-06-21 1:20 GMT+02:00 Hilaire Fernandes <hilaire.fernandes@gmail.com
:
Gi Igor,
For DrGeo it is not a workable option to have different fonts in Morphic widget and Athens canvas (I explained earlier why). However I found the scaling trick of draw text to work reasonably well. Not full perfect as from time to time I can see some artifact.
Thanks
Hilaire
Le 20/06/2014 15:32, Igor Stasenko a écrit :
Sure, you can do: make sure you don't render text with same font in Morphic UI and Athens, so they don't interfere with each other. There's no easy way to get rid of interference, because it would require changing Freetype package and its plugin in order to establish a single font management point and funnel all requests to freetype library through it.
-- Dr. Geo http://drgeo.eu iStoa - https://launchpad.net/istoa
-- Best regards, Igor Stasenko.
-- www.tudorgirba.com "Every thing has its own flow"
On 20/6/14 00:26, Nicolai Hess wrote:
If I take a fresh pharo image I always have to reenable FT fonts before doing any athens rendering with text (RMOD StrikeFont(Object)>>doesNotUnderstand: #getPreciseHeight).
Ok, I know I have to open settings disable then enable FreeType and choose a FreeType font.
But what exactly is the problem with Athens rendering and non FT fonts?
StrikeFonts and FT are different beasts. I should take the time concentrate and go over my roadmap (it feels to me like a "chemin de croix" :(
Nicolai
participants (8)
-
Alexandre Bergel -
Chris Cunningham -
Henrik Sperre Johansen -
Hilaire Fernandes -
Igor Stasenko -
Nicolai Hess -
stepharo -
Tudor Girba