>>> * For backward compability, it should continue to return
>>> FT_Err_Ok.
>>
>> It should return what it already returns.
>
> But it returns an error code. But above you said it “shouldn’t
> return an error code at all”. So here you saying it *should* return
> an error code.
You sound as
On Fri, 11 May 2018 10:03:26 +0900, suzuki toshiya wrote:
> ... the maintainer cannot introduce the change breaking
> the backward compatibility ...
Which is why I suggested a change that would *not* break backward
incompatibility. Whatever code that might actually exist that checks for
an error
> Otherwise it’s going to be very difficult conducting
> a coherent conversation with you.
What Werner think as the best design could be different from
what the current implementation does. Even if it is not the
best design, the maintainer cannot introduce the change breaking
the backward
Hi Richard,
FreeType rasterizer is designed to be portable, low-level and self-
standing for ANSI C, it does not invoke other graphic libraries.
I'm interested in who told you as "FreeType on OpenGL" idea...?
Have you read something like
https://learnopengl.com/In-Practice/Text-Rendering
???
Hi,
Will this Library work in modern OpenGL, ie. OpenGL version 4.4 using
shaders?
If so are there any examples of use with shaders available?
Regards
Richard
___
Freetype mailing list
Freetype@nongnu.org
On Thu, 10 May 2018 00:55:42 +0200 (CEST), Werner LEMBERG wrote:
> On Thu, 10 May 2018 10:29:11 +1200, Lawrence D'Oliveiro wrote:
>>
>> On Wed, 09 May 2018 14:11:19 +0200 (CEST), Werner LEMBERG wrote:
>>>
>>> IMHO, `FT_Done_Face' shouldn't return an error code
>>> at all.
>>
>> Glad you
> I'm using freetype 2.8 with the Emoji One font, [...]
>
> [...] But something goes sideways with U+0020 and U+200d.
Please retry with FreeType 2.9.1 – there were some fixes for empty
bitmaps.
Werner
___
Freetype mailing list
Freetype@nongnu.org
I'm using freetype 2.8 with the Emoji One font, which appears to come from
https://github.com/eosrei/emojione-color-font and I'm seeing the following
problem with some but not all characters when trying to get a bitmap for
some of the font's glyphs.
Using fontconfig to retrieve FC_Charset
On Thu, May 10, 2018 at 11:45 AM, Parth Wazurkar
wrote:
> In the `FT_Module_Class` structure the module version has been defined as
> `0x1L` and the required FT version as `0x2L`. Is there any specific
> significance of numbering the versions in hex?
Hexadecimal
Hi all,
In the `FT_Module_Class` structure the module version has been defined as
`0x1L` and the required FT version as `0x2L`. Is there any specific
significance of numbering the versions in hex?
Please help.
Thank you
--
Regards
Parth
___
> AC_COMPILE_IFELSE only tries to compile a *.c to a *.o. [...]
Thanks a lot! I've committed this (with very minor changes).
Werner
___
Freetype-devel mailing list
Freetype-devel@nongnu.org
> I have been working on the conversion of header comments to the
> lighter format. [...]
Very nice!
> The code is available on GitHub [1]. This seems to be working for
> most cases now (I'm not sure if there are any rare differences in
> the rectangular block formatting in some of the
> The `FT_Module_Class` structure has a `module_init` function. Some
> font drivers have this function defined and some do not (`pcf` has
> it defined but `bdf` do not). I cannot understand the meaning and
> use of this function for font drivers.
If the driver needs a separate driver record
13 matches
Mail list logo