Re: [ft] How can I render monospace text in any font?

just use whatever fixed size you want between characters instead of that returned by the font? It's certainly easier to go to monospace than to variable space from a mono font On Wed, Oct 1, 2014 at 5:17 AM, John Owen johnowen...@gmail.com wrote: Given any typical font, not necessarily a

Re: [ft] New ttfautohint release soon

I have a similar issue with 'rod.ttf' that comes with windows ( I think ) It renders mono fine, but antialiasing on diagonales makes it blotchy when rendered higher grey scale. any chance you can try that one too? On Sat, Oct 4, 2014 at 6:37 AM, Werner LEMBERG w...@gnu.org wrote: Folks,

Re: [ft] New ttfautohint release soon

sorry; I guess I'm wrong, there's something specific about that rendering maybe I'm overdrawing the string too many times... my tester program had no issues. On Sat, Oct 4, 2014 at 9:34 AM, Werner LEMBERG w...@gnu.org wrote: I have a similar issue with 'rod.ttf' that comes with windows (

Re: [ft] Possible issue in FreeType

On Wed, May 27, 2015 at 3:44 PM, Guzman Mosqueda, Jose R jose.r.guzman.mosqu...@intel.com wrote: Hi all I'm Jose Guzman from a security team at Intel. We're using freetype in a GNU-Linux project and I'm analyzing the code to try to find possible issues/gaps/risks. Since I'm not too

Re: [ft] Possible issue in FreeType

On Thu, May 28, 2015 at 1:09 AM, Jan Engelhardt jeng...@inai.de wrote: On Thursday 2015-05-28 05:43, J Decker wrote: Stack space for variables is also only allocated at the subroutine prefix code and deallocated at the suffix That is a false statement. gcc expands the stack

Re: [ft] Freetype x86

On Mon, May 18, 2015 at 4:06 AM, Semeriak, AleksandraX aleksandrax.semer...@intel.com wrote: Hello Werner, We have been looking into the use of Freetype and the compatibility with x86 devices, and as you noted in your first email, it should run on any platform, as it creates

Re: [ft] Missing glyphs vs. invisible glyphs for certain characters

Yes 'invisible' glyphs use the default 0 index character. This is true for any missing character. Control characters have to be handled by the renderer On Fri, Dec 4, 2015 at 5:48 AM, Preet wrote: > Hi all > > I've tried a few fonts out and I seem to be getting

Re: [ft] Does Freetype support Android x86?

just out of curiosity... Have you actually run the ARM build? I have no issues building freetype for x86 x64, arm, etc... (though I haven't built it for android in quite a few months) I've often found that what shows as a proper link time error in x86 builds sometimes doesn't show in arm until

Re: [ft] The fastest way to query size of a rendered bitmap

from just loadglyph you get metrics of it, so you don't need to render it at all to get how big it is... THe advance is how wide the overall character is; that doesn't count how big the bitmap actually is if you're trying to get the actual rendered size of the character... but rather the cell size

Re: [ft] FT_Done_Face Should Not Return An Error

On Sat, May 5, 2018 at 11:10 AM, Werner LEMBERG wrote: > > >> It is common for object-disposal routines to never return error > >> statuses. The archetypal example is free(3) > >> . If this is passed a valid > >> pointer, it disposes of the

Re: [ft] Fw: Could you help me for debugging FreeType library?

On Fri, May 3, 2019 at 6:14 PM Lawrence D'Oliveiro wrote: > On Fri, 3 May 2019 03:00:25 +, suzuki toshiya wrote: > > > BTW, does cmake have any hardwired database for > > the available flags for each compilers? I can check > > for gcc and clang, but I'm not sure about other > > proprietary

[ft-devel] Freetype 2.8 bitmap font no linear advance

On the font 'c:/windows/fonts/c8514fix.fon' This is basically the code I used... FT_Library library; FT_Face face; int error; error = FT_Init_FreeType( ); error = FT_New_Face( , 'c:/windows/fonts/c8514fix.fon' , 0 , ); error = FT_Load_Glyph( , 53 , 0 ); face.glyph->linearHoriAdvance

Re: [ft-devel] Freetype 2.8 bitmap font no linear advance

okay; this also seems to work. face->glyph->linearHoriAdvance? (face->glyph->linearHoriAdvance >> 16) :( face->glyph->advance.x >> 6 ) On Tue, Aug 22, 2017 at 1:42 PM, Alexei Podtelezhnikov wrote: > > I had basically standardized on using linearHoriAdvance but it isn't >

Re: [ft-devel] [ft] Announcing FreeType 2.8.1

I guess CMakeLists.txt isn't really used by anyone? I'm pretty sure that these are missing from the latest. src/otvalid/otvalid.c src/gxvalid/gxvmod.c (I have my own version I keep updated) On Sat, Sep 16, 2017 at 11:04 AM, Werner LEMBERG wrote: > > FreeType 2.8.1 has been

Re: [ft-devel] [ft] Announcing FreeType 2.8.1

On Wed, Sep 20, 2017 at 11:50 AM, Werner LEMBERG wrote: > > > I guess CMakeLists.txt isn't really used by anyone? > > > > I'm pretty sure that these are missing from the latest. > > > > src/otvalid/otvalid.c > > src/gxvalid/gxvmod.c > > No, they are not missing. Leaving out