Re: [ft] default LCD rendering to bounding box

2018-11-06 Thread Werner LEMBERG
> let me reformulate: is "glyph hinted bounding box" always the output > bitmap of any render operation? It's still not clear to me what you are after, sorry. Are you talking about the metrics? The actual bitmap dimensions? Again: Please provide an example what you want to achieve.

Re: [ft] What is the use of the right FT_Property_Set function intended by the Freetype?

2018-11-06 Thread Werner LEMBERG
>>> I think it would be possible for FT_Load_Glyph to implement this >>> operation on its own without FT_Property_Set. Is there any plan >>> that the Freetype will provide this characteristic? >> >> This is issue https://savannah.nongnu.org/bugs/?43380. > > I would like to ask you to solve

Re: [ft] default LCD rendering to bounding box

2018-11-06 Thread sylvain . bertrand
On Tue, Nov 06, 2018 at 05:25:25PM +0100, Werner LEMBERG wrote: > > > let me reformulate: is "glyph hinted bounding box" always the output > > bitmap of any render operation? > > It's still not clear to me what you are after, sorry. Are you talking > about the metrics? The actual bitmap

Re: [ft] default LCD rendering to bounding box

2018-11-06 Thread Werner LEMBERG
> The bitmap dimensions. For a 'g' glyph opentype outline for > instance, if I load it and render it using the LCD(RGB) related > options, the resulting bitmap dimensions are the bounding box of the > glyph. Is this true for any glyph outline rendering mode > (monochrome, grayscale..)? I

[ft] This is the "perfect" Makefile for FreeType library building on an AmigaOne

2018-11-06 Thread Nagy Károly
Hello Werner, I write a "new" Makefile (freed from a lot of "brick-a-brack" and tested) for building FreeType Library easily on an AmigaOne (AmigaOS 4.1 Final Edition Update 1): attached "Makefile". It makes a "libfreetype.a" (linked with ftinit.ppc.o and ftsystem.ppc.o, too) static library

Re: [ft] What is the use of the right FT_Property_Set function intended by the Freetype?

2018-11-06 Thread Werner LEMBERG
> In the runtime, what is the appropriate way to render the MS legacy > fonts(Tahoma, Arial, ...) as v35 and the MS ClearType > fonts(Consolas, ...) as v40? Microsoft Windows GDI displays two > types of fonts at the same time. > > PSEUDO CODE: > > gasp_version = get_gasp_version( font

Re: [ft] default LCD rendering to bounding box

2018-11-06 Thread Werner LEMBERG
> Is this expected that lcd loading and rendering is done on the R/G/B > glyph biggest bounding boxes or am I using freetype wrongly? I don't understand the question. Please give an example. Werner ___ Freetype mailing list Freetype@nongnu.org

Re: [ft] default LCD rendering to bounding box

2018-11-06 Thread sylvain . bertrand
On Tue, Nov 06, 2018 at 12:19:13PM +0100, Werner LEMBERG wrote: > > > Is this expected that lcd loading and rendering is done on the R/G/B > > glyph biggest bounding boxes or am I using freetype wrongly? > > I don't understand the question. Please give an example. Hi, let me reformulate: is

Re: [ft] What is the use of the right FT_Property_Set function intended by the Freetype?

2018-11-06 Thread Byeongsik Jeon
On Tue, 06 Nov 2018 11:53:10 +0100 (CET), Werner Lemberg wrote: > >> In the runtime, what is the appropriate way to render the MS legacy >> fonts(Tahoma, Arial, ...) as v35 and the MS ClearType >> fonts(Consolas, ...) as v40? Microsoft Windows GDI displays two >> types of fonts at the same