Re: Creating a FreeType GitLab merge request

2024-01-22 Thread David Saltzman
> > this seems to duplicate functionality in harfbuzz, and also a mere subset, > for that matter? > Yes, that's a good question. For the product I'm working on, we wanted to add kerning support, and we already used FreeType but not HarfBuzz, and our font had GPOS kerning but not a kern table. We

Re: Creating a FreeType GitLab merge request

2024-01-24 Thread David Saltzman
Done On Tue, Jan 23, 2024 at 10:50 AM David Saltzman wrote: > Sounds good; I'll look at walking over the feature list for 'kern' > features when I get a chance and push an update. (That may not be today, as > I'll need to do other work). > > On Tue, Jan 23, 2024 at 10:45 AM

Re: Creating a FreeType GitLab merge request

2024-01-23 Thread David Saltzman
ng I like to see you address is, > instead of walking all subtables, only walk subtables from 'kern' features. > > behdad > > On Tue, Jan 23, 2024 at 10:43 AM David Saltzman > wrote: > >> it might be useful to add (also) either compile-time or runtime switch to >>>

Re: Creating a FreeType GitLab merge request

2024-01-23 Thread David Saltzman
lready have conditionals on harfbuzz being available, etc, so it is > probably easy enough to just piggyback on that conditional. > > On Monday, 22 January 2024 at 20:35:17 GMT, David Saltzman < > davidbsaltz...@gmail.com> wrote: > > > this seems to duplicate functionality

Creating a FreeType GitLab merge request

2024-01-19 Thread David Saltzman
Hi, I'd like to submit a feature to FreeType. https://freetype.org/developer.html recommends doing so via GitLab merge requests. But when I tried pushing to a branch on the command line, git said "ERROR: You are not allowed to push code to this project." Then I tried clicking edit->web IDE, and

Re: Creating a FreeType GitLab merge request

2024-01-22 Thread David Saltzman
; On Fri, Jan 19, 2024 at 9:03 PM David Saltzman > wrote: > > > > Hi, > > > > I'd like to submit a feature to FreeType. > https://freetype.org/developer.html recommends doing so via GitLab merge > requests. But when I tried pushing to a branch on the co

[ft-devel] Why is FT_Fixed a long instead of FT_Int32?

2019-08-26 Thread David Saltzman via Freetype-devel
Noticed a discrepancy that when compiling on a 32 bit system, FT_Fixed is 32 bit; but on a 64 bit system, FT_Fixed is 64 bit. FT_Fixed is supposed to be a 16.16 number, so why doesn't it use `FT_Int32` instead of `signed long`? Thanks, David ___

Re: [ft-devel] Why is FT_Fixed a long instead of FT_Int32?

2019-08-26 Thread David Saltzman via Freetype-devel
Thanks Alexei, good to know about FreeType sticking to C89, and that it should be ok to redefine. Though I do see a FT_Int32 type defined in FreeType in ftconfig.h? On Mon, Aug 26, 2019 at 5:34 PM Alexei Podtelezhnikov wrote: > > > > > > FT_Fixed is supposed to be a 16.16 number, so why

Re: [ft-devel] Why is FT_Fixed a long instead of FT_Int32?

2019-08-26 Thread David Saltzman via Freetype-devel
Fair enough. Thanks. On Mon, Aug 26, 2019, 9:11 PM Werner LEMBERG wrote: > > > Thanks Alexei, good to know about FreeType sticking to C89, and that > > it should be ok to redefine. > > > > Though I do see a FT_Int32 type defined in FreeType in ftconfig.h? > > While `FT_Int32' gets used for more