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 wrote: > Given any typical font, not necessarily a monospace one, how can I >

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 wrote: > > Folks, > > > I'm going

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 wrote: > > > I have a similar issue with 'rod.ttf' that comes with windows ( I > > thin

Re: [ft] Determining pixel dimensions for bitmap

it seems most of my calculations for freetype are based on ceil() so yes... if any fraction round up... do you keep the original freetype bitmap? Or are you moving it to an internal format? I use FT_Render_Glyph( face->glyph, FT_RENDER_MODE_NORMAL ); which has a bitmap in the face->glyph structure

Re: [ft] Included header files location

g++ -Ifreetype2 main.cpp -lglut -lGLEW -lGL -o main On Mon, Dec 22, 2014 at 8:39 PM, Dave Coventry wrote: > On 22 December 2014 at 22:07, Khaled Hosny wrote: > > It should be > > That doesn't work either: > > $ make > g++ main.cpp -lglut -lGLEW -lGL -o main > In file included from mai

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 Libs/arm

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 to

Re: [ft] Possible issue in FreeType

On Thu, May 28, 2015 at 1:09 AM, Jan Engelhardt 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

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 the same behaviour: The > zer

Re: [ft] Independent Project Help

I assume it's these... which are already supported by freetype http://corefonts.sourceforge.net/ An easy way to install Microsoft's TrueType core fonts on linux https://en.wikipedia.org/wiki/Core_fonts_for_the_Web and probably it's more the drawing process that needs to be updatred from TextOut

Re: [ft] Windows font driver Parser

On Wed, Aug 2, 2017 at 7:21 AM, Ammar ul hassan wrote: > 1) How windows font driver recognizes a window font file so that it can > parse it. > > Like in Type 1 driver module case there is a file t1parse.c which actually > checks the header of a file that, if it starts with some specific text tha

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] 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 you

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 object; if it is pass

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 co