Re: [ft-devel] Outline dumper for windows

Werner knew this. I don't know how he knew though :-) Using FontForge to single-step through the bytecode instructions! This makes great fun (and drives George crazy because of my many bug reports and feature suggestions). Werner is good at that kind of stuff. :-) And I did not know that

Re: [ft-devel] multithreading and 64 bits

The long integer type on Windows 64 is 4 bytes wide, not 8 bytes wide. Thank you, MS! You will have to use ptrdiff_t if you want a full 8 byte wide integer type. Werner, I have not looked at the code recently, but I assume FT_PtrDist is like ptrdiff_t. Tom Werner LEMBERG wrote: Sorry for the

[ft-devel] git

Hi, I am looking at getting back into the FreeType project after a five or so year hiatus. I see things have moved from cvs to git (skipped svn?) Does anyone know of a good tutorial on git? Tom ___ Freetype-devel mailing list

Re: [ft-devel] questions about OpenType fonts with CFF data

http://www.adobe.com/devnet/font/pdfs/5176.CFF.pdf should give you more information on CFF. AS for your assumptions: (1) Most OpenTpe/CFF fonts I have seen have only one font in the FontSet (2) There are other font encoding methods that can be used besides CID keyed fonts (3) I've never

Re: [ft-devel] sfnt version 0x00020000UL

I recall there being a few fonts from Apple that one could get if they installed a foreign language kit. It was either the Japanese or Korean kit that had these. But these were back in the Mac OS 9 (and earlier) days. On 2009/10/11, at 12:40 , Werner LEMBERG wrote: I noted in the

Re: [ft-devel] freetype.com

I missed Behdad's solution. Not sure if freetype-devel got CCed on his response. On 2010/02/24, at 01:04 , Werner LEMBERG wrote: I vote for a professional letter to them, and if that doesn't work, use slashdot... Yeah, sounds reasonable. However, my English is probably not

[ft-devel] Greetings

Howdy all! I know I said a while ago that I was back to FreeType development, but then I dropped it. This time I think it is going to stick. I need to get into font programming again. I've been working on finite element analysis software for the last eight years as a build support specialist,

[ft-devel] bootstrapping from git source

I think the docs are a little out of date with respect to bootstrapping FreeType builds from git source. I need to get autoconf, automake, and libtool built on Mac OS X before I could run autogen.sh. The docs as far I as could tell only refer to autoconf. Tom

Re: [ft-devel] bootstrapping from git source

Thanks. Obviously, I missed that. Tom On Sun, Feb 17, 2013 at 9:23 PM, Alexei Podtelezhnikov apodt...@gmail.comwrote: On Sun, Feb 17, 2013 at 12:20 PM, Tom Kacvinsky tkacv...@gmail.com wrote: I think the docs are a little out of date with respect to bootstrapping FreeType builds from

Re: [ft-devel] Fonts with unusual CFF operators sought!

Wener, I don't know if there is OpenType/CFF equivalents of the Blue Sky Research/YY based Computer Modern fonts, but if they exist, you'll want to check them out. They use the div operator (which isn't really that exotic, it's in the Type 1 spec and is used in the Type 1 flavor of the above

Re: [ft-devel] ft2build.h being regenerated each time.

I think the issue here might be related to the fact that Mac Os X uses the BSD install program, but Linux uses the GNU install program. On Fri, Apr 5, 2013 at 8:14 AM, Werner LEMBERG w...@gnu.org wrote: I have noticed similar behaviour from libpng, but I'm also planning to switch to CMake

Re: [ft-devel] ft2build.h being regenerated each time.

You can try building the GNU install program (or get it from macports or fink or some such) and adding the location to it to your path and try again. On Fri, Apr 5, 2013 at 10:12 AM, Tom Kacvinsky tkacv...@gmail.com wrote: I think the issue here might be related to the fact that Mac Os X uses

Re: [ft-devel] Fwd: buiding ttfautohint with cmake?

Have you considered CFFI? [1] This might make things a little easier, but I am not sure since I don't have as much experience with that as I do ctypes. Or are you more or less married to ctypes? [1] https://cffi.readthedocs.io/en/latest/ On Wed, Dec 13, 2017 at 7:23 AM, Werner LEMBERG

Re: [ft-devel] Fwd: buiding ttfautohint with cmake?

Agreed. Windows is fussy about memory allocated in one DLL being freed in another. On Wed, Dec 13, 2017 at 9:57 AM, Cosimo Lupo wrote: > IMO, what matters is not which specific memory allocator/deallocator is > used (whether the defaults, or user provided ones), but

[ft-devel] Meltdown and Spectre

Anyone here know if FreeType is immune to Spectre and Meltdown? Or is there something we have to do? ___ Freetype-devel mailing list Freetype-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/freetype-devel

Re: [ft-devel] LD version script

We should be careful to notify downstream consumers of FreeType as some Linux vendors may already do symbol versioning in their implementations of it - any changes we make may have an effect on what they're doing. On Wed, Jan 24, 2018 at 7:33 AM, Werner LEMBERG wrote: > > >

Re: [ft-devel] LD version script

<vincent.to...@gmail.com> wrote: > On Tue, Jan 30, 2018 at 1:45 PM, Tom Kacvinsky <tkacv...@gmail.com> wrote: > > Hi all, > > > > I'll see what I can do. To be honest, the only platforms that really > > support this > > are Linux and Solaris

Re: [ft-devel] LD version script

Hi all, I'll see what I can do. To be honest, the only platforms that really support this are Linux and Solaris. I definitely have access to Linux machines, but not a Solaris machine. I might be able to get access to the latter. Despite all of the talk about whether symbol versioning is

Re: [ft-devel] LD version script

Type binaries to come with the same > headaches that libpng and openssl cause every time they bump soname. > > On Tue, Jan 30, 2018 at 4:45 AM, Tom Kacvinsky <tkacv...@gmail.com> wrote: > >> Hi all, >> >> I'll see what I can do. To be honest, the only platforms

Re: [ft-devel] LD version script

Well, that is inspirational enough - let's be the first to do historical versioning instead of slapping a single version on each symbol with each iteration of the API. I mean, I am willing to do the work, so I am guessing your hesitance is more based on the principle of the matter, not the

Re: [ft-devel] LD version script

I looked aver the changes apinames.c to see how the GNU and Solaris linker version script is handled. The question I have is how are we going to add the actual symbol versions - read in a version tag or something else?. Also, how are we going to handle inheritance?, For instance, using 1.2 as a

Re: [ft-devel] LD version script

Hi Werner, Alexei, I have the latest master repository cloned. and cannot find a symvergen script it in. I pulled again to make sure I had the latest, and didn't see it. Moreover I ran "git branch" to see if there was a different branch into which the symvergen script would go, and did not see

Re: [ft-devel] LD version script

I am really stupid, I see it was attached to this mail thread. On Sat, Feb 3, 2018 at 8:04 AM, Werner LEMBERG wrote: > > > I have the latest master repository cloned. and cannot find a > > symvergen script it in. I pulled again to make sure I had the > > latest, and didn't see

Re: [ft-devel] LD version script

Hat side of things. Tom On Sat, Feb 3, 2018 at 8:05 AM, Tom Kacvinsky <tkacv...@gmail.com> wrote: > I am really stupid, I see it was attached to this mail thread. > > > On Sat, Feb 3, 2018 at 8:04 AM, Werner LEMBERG <w...@gnu.org> wrote: > >> >> >

Re: [ft-devel] LD version script

I suggest you read Ulrich Drepper's article on what symbol versioning addresses. FreeType is not known for frequently changing its ABI or API (I don't think I've ever recalled the former happening), so some of these things are not relevant to the FreeType project. Still, I think it would be a

Re: [ft-devel] LD version script

Ah, I was reading the following and came across something that is an argument against version scripts. https://gcc.gnu.org/wiki/Visibility In particular: "Furthermore, using linker version scripts doesn't permit GCC to better optimise the code." On Wed, Jan 31, 2018 at 3:41 PM, Tom

Re: [ft-devel] LD version script

Just let me know if you want me to proceed. I am not going to spend the time on this if the consensus (sans me) is that we don't need/want it. On Wed, Jan 31, 2018 at 3:22 AM, Werner LEMBERG wrote: > > > I also hated the frontend of the symbol versions which requires GCC > >

Re: [ft-devel] Time for a new FreeType release

What I was thinking of doing is finalizing the work necessary to get a symbol versioning linker script in place, but it is not necessary for this release. It is just a "nice to have" So I'd say the lack of such feature won't delay the release. On Sun, Apr 8, 2018 at 11:37 AM, Nikolaus Waxweiler

Re: [ft-devel] Time for a new FreeType release

Hi, I dropped the ball. I meant to get to the symbol versioning stuff we talked about so we'd have it for this release, but I've been swamped with work. Tom On Sun, Apr 8, 2018 at 9:21 AM, Werner LEMBERG wrote: > > > Got it working :) Tested with CMake 3.10.2 on Win 10 x64.

Problems building freetype-2.10.4 on CentOS 5 with GCC 8.3.0

I see this -bash-3.2$ make ./builds/unix/libtool --mode=compile gcc -pedantic -ansi -I/home/LOCAL/tjk/freetype-2.10.4/objs -I./builds/unix -I/home/LOCAL/tjk/freetype-2.10.4/include -c -Wall -g -O2 -fvisibility=hidden -I -DFT_CONFIG_CONFIG_H="" -DFT_CONFIG_MODULES_H="" -DFT_CONFIG_OPTIONS_H=""

Re: help needed for cmake problem (FreeType issue #897)

Hi Werner, I work extensively with cmake at my day job. If the end consumer of FreeType wants to build their project using cmake, the there would be a need to make cmake module that could be used with cmake (which, to my delight, already exists). The the user could know how to link in bzip2