emo
> You, can directly go here:
> https://github.com/preversewharf45/freetype2-sdf-demo/blob/master/vendor/freetype2-sdf/src/sdfgen.c#L485
> to see the subdivision code. And yeah currently I'm subdividing equally
> which might
> not be good. So using a more efficient algorithm to subdivide the curve
> will be better.
>
> Sorry for a large mail and Thanks for your time,
> Anuj
>
--
Jim Van Verth | Software Engineer | jvanve...@google.com | 919-210-7664
> >
> > Thanks Jim.
> >
> > A 2.14 representation when 1 unit = 1em is sufficient. If we are
> talking pixels then 10.6 or better 8.8 makes more sense. And I agree that
> the pixel values are more useful to clients than em values.
> >
> > On Thu, Jun 4, 202
point or similar at least as an option. In your
>> 3.5 fixed-point, does one unit reflect 1em, or 1 pixel at the SDF size?
>>
>> I think we do want a 8bit representation at least, and possible a higher
>> one.
>>
>> On Wed, Jun 3, 2020 at 10:26 AM Jim Van Verth
&g
Forgive me for coming into this late -- a colleague pointed me to this
thread a couple of days ago and I'm just catching up. I work on Skia, and
we've been generating SDFs from glyphs for quite some time now, so the
possibility of just getting them from Freetype is pretty exciting.
I hope you don'