Re: [ft] writing fonts

> On Jan 25, 2018, at 12:32 PM, Shawn Riordan wrote: > > Can Freetype write font files, as well as read them? I browsed the code and > nothing jumped out at me. > > I need to write any font to a WOFF file. So I can then insert that into an > SVG file. I don't think

Re: [ft-devel] Freetype 2.6.3 and Visual Studio versions...

We compile Freetype with VS2015 by using FreeTypeAmalgam.c, which makes it very easy. Unfortunately, the amalgamation is three years out of date, version 2.4.12. Maybe it would be easier to maintain an amalgamation than to maintain projects for various compilers. Tom > On Jun 17, 2016, at

Re: [ft-devel] gamma correction demo images

It's about 1.65 on my MacBook Pro (Retina, 13-inch, Late 2013, Intel Iris 1536 MB). Tom > On Oct 27, 2015, at 11:25 PM, Alexei Podtelezhnikov > wrote: > > On Mon, Oct 26, 2015 at 10:26 AM, Alexei Podtelezhnikov > wrote: >> On Sun, Oct 25, 2015 at 2:35

Re: [ft-devel] integer suffix abuse

On Jun 24, 2015, at 11:52 AM, Alexei Podtelezhnikov apodt...@gmail.com wrote: Hi All, I think we abuse the suffix L in integer constants. I understand the desire to make sure that very common 0x1L is 32-bit to represent a unit in 16.16 fixed-point representation. On modern 64-bit

Re: [ft-devel] integer suffix abuse

On Jun 24, 2015, at 11:52 AM, Alexei Podtelezhnikov apodt...@gmail.com wrote: Hi All, I think we abuse the suffix L in integer constants. I understand the desire to make sure that very common 0x1L is 32-bit to represent a unit in 16.16 fixed-point representation. On modern 64-bit

Re: [ft-devel] integer suffix abuse

On Jun 24, 2015, at 2:36 PM, Alexei Podtelezhnikov apodt...@gmail.com wrote: On Wed, Jun 24, 2015 at 1:12 PM, Tom Bishop, Wenlin Institute wen...@wenlin.com wrote: I would have guessed that with a 64-bit compiler the resulting executable code would be the same with or without L

Re: [ft-devel] integer suffix abuse

On Jun 24, 2015, at 4:00 PM, Alexei Podtelezhnikov apodt...@gmail.com wrote: Here it is (I hope!). -Tom Alright, your version of FreeTypeAmalgam.c is not this one: https://github.com/vinniefalco/FreeTypeAmalgam It looks like only two pieces of code affected: about 30 lines here from

Re: [ft] Building FT2 for embedded architectures

On Apr 19, 2013, at 11:06 AM, Wolfgang Draxinger wolfgang.draxin...@physik.uni-muenchen.de wrote: Hi, I'd like to build FT2 for the ARM Cortex-M3 architecture to use it for text output on a display. My naive attempt to make it use the available cross-compiler by passing the --host

Re: [ft-devel] FreeType 2.4.11 amalgamation RC1

On Dec 20, 2012, at 3:49 PM, Vinnie Falco vinnie.fa...@gmail.com wrote: I've updated the FreeType amalgamation to the recently released version of FreeType, 2.4.11. It is available in the develop branch of the official amalgamation repository: https://github.com/vinniefalco/FreeTypeAmalgam

Re: [ft-devel] Amalgamation: Aftermath.

On Apr 13, 2012, at 5:41 AM, Alan Coopersmith wrote: On 04/13/12 07:30 AM, Vinnie wrote: From: http://rawmaterialsoftware.com/viewtopic.php?f=6t=8654 those amalgamations are pretty convenient imo, i don't get why you got so much hostility on the freetype dev list A pretty convenient way

Re: [ft-devel] FreeType Amalgamation first draft

It works! Awesome! Thank you Vinnie! One question: my application normally includes ftoutln.h, for directly calling FT_Outline_Render(), etc. With FreeTypeAmalgam.h and FreeTypeAmalgam.c, I don't include ftoutln.h and I get: warning: implicit declaration of function ‘FT_Outline_Render’

Re: [ft-devel] FreeType Amalgamation

On Jan 19, 2012, at 8:32 AM, Vinnie wrote: I'm interested in building an amalgamated version of FreeType. I would love to be able to use that. Currently I don't build FreeType as a library, I add twenty-five FreeType C files directly to the project or makefile in which they are used. (For

Re: [ft-devel] FreeType Amalgamation

On Jan 19, 2012, at 8:32 AM, Vinnie wrote: I'm interested in building an amalgamated version of FreeType. I would love to be able to use that. Currently I don't build FreeType as a library, I add twenty-five FreeType C files directly to the project or makefile in which they are used. (For

Re: [ft-devel] avoiding a longjmp crash in ftgrays.c

On Jan 9, 2011, at 12:07 AM, Werner LEMBERG wrote: ... This won't compile. You need -DFT2_BUILD_LIBRARY also. I forgot to mention that I had set up FreeType 2.4.4 as follows: Ran ./configure, make, and sudo make install. Added this line to ft2build.h: #define FT2_BUILD_LIBRARY Adding

Re: [ft-devel] avoiding a longjmp crash in ftgrays.c

On Jan 1, 2011, at 11:31 PM, Werner LEMBERG wrote: ... Which font is it? Maybe I already have it. Otherwise, please send me the font privately for further investigation. I've reproduced the crash with a different font: mssong.ttf, glyph number 1006. This font is available for free from

Re: [ft-devel] avoiding a longjmp crash in ftgrays.c

Dear FreeTypers, A very short program (freetype_debug_gray.c) demonstrates the crash: #include stdio.h #include string.h #include ft2build.h #include FT_FREETYPE_H static char *DebugFreeType(void) { FT_Library ttEngine; if (FT_Init_FreeType(ttEngine) != 0) {

[ft-devel] avoiding a longjmp crash in ftgrays.c

Dear FreeTypers, This was happening on MS-Windows 7/XP/Vista when trying to display a large, intricate character: Program received signal SIGSEGV, Segmentation fault. 0x77c337c9 in msvcrt!_abnormal_termination () from C:\WINDOWS\system32\msvcrt.dll (gdb) bt #0 0x77c337c9 in

Re: [ft-devel] suspicious code in FT_Set_Renderer

On Dec 12, 2010, at 9:13 PM, Werner LEMBERG wrote: While browsing freetype code I notice following code in FT_Set_Renderer (src/base/ftobjs.c, v2.4.4 release): if ( num_params 0 ) { FT_Renderer_SetModeFunc set_mode = renderer-clazz-set_mode; for ( ; num_params 0;

Re: [ft] FT_Outline_Render makes different bitmaps in 32-bit and 64-bit programs?

The bug appears to be here in ftraster.c: /* FMulDiv means `Fast MulDiv'; it is used in case where `b' is */ /* typically a small value and the result of a*b is known to fit into */ /* 32 bits. */ #define FMulDiv( a, b, c ) (

Re: [ft] FT_Outline_Render makes different bitmaps in 32-bit and 64-bit programs?

On Oct 25, 2010, at 10:05 PM, suzuki toshiya wrote: Hi, Since 2.3.8? I'm really interested in, because I had committed many changes for 16-bit/64-bit platforms between 2.3.9 and 2.3.10. In your observation, 2.3.8 is ok but 2.3.9 is not ok? Or, 2.3.7 is ok but 2.3.8 is not ok? This

Re: [ft] Using SVG Font Glyph Data In FreeType

On Apr 8, 2010, at 7:05 AM, Werner LEMBERG wrote: If I understand Andy correctly, he'd like to map these primitive outline commands to the corresponding FreeType rules (the FT_outline_Functs structures) and then hand off the set of rules for FreeType to work its magic on. I've had a look

Re: [ft] Using SVG Font Glyph Data In FreeType

On Apr 8, 2010, at 12:14 PM, Andy Kellett wrote: Hi, Tom Thank-you for your example. A small piece of code speaks a thousand words :) Im able to better make sense of that command now I have seen your example. Good! I'm guessing that GRID_SIZE is just a numeric value to depict a

Re: [ft] Using SVG Font Glyph Data In FreeType

On Apr 7, 2010, at 10:05 AM, Andy Kellett wrote: Hi, Yes, I did see this response. While it did answer some questions, I still had more based on it, this example assumes the path data is already converted for example. If you're looking for sample code that reads SVG, I don't think

Re: [ft] Using SVG Font Glyph Data In FreeType

On Apr 6, 2010, at 4:34 AM, Andy Kellett wrote: Hi, My SVG file already has all the custom defined glyphs that I need in it, all I need to be able to do is extract the glyph data from the SVG file, and convert it into something that I can then get freetype to display on the screen. I

Re: [ft] Porting Freetype to Go

On Apr 1, 2010, at 4:19 PM, Nigel Tao wrote: Hello. I'm porting the Freetype library to the Go programming language Very interesting! I hope you'll post some progress reports here. Good luck! Tom 文林 Wenlin Institute, Inc.Software for Learning Chinese E-mail: wen...@wenlin.com

Re: [ft] Pixel_Mode

On Jan 27, 2010, at 9:11 AM, samaram s wrote: Anybody Please... Hi, I am getting used to freetype API with the examples given.Where in example1 gives, FT_PIXEL_MODE_GRAY. I would like to get a monochrome bitmap, using 1 bit per pixel. Can anyone please explain me where we

Re: [ft] Pixel_Mode

On Jan 27, 2010, at 11:15 AM, samaram s wrote: Thanks Tom..will workout on it. Do you have any idea in the example how is it defaultly considering PT_PIXEL_MODE_GRAY? http://www.freetype.org/freetype2/docs/reference/ft2-base_interface.html#FT_Render_Mode FT_RENDER_MODE_NORMAL This is

Re: [ft] Re: Can i get array of bytes for a glyph

On Jan 21, 2010, at 12:23 PM, samaram s wrote: Array of bytes which represents the glyph.I mean given a glyph to convert into the given ttf file format,Which should result in binary representation of 8bits (means a byte) Maybe this is part of what you want: FT_Set_Pixel_Sizes(...);