Re: [Freetype-devel] Re: GSOC - Distance Fields

[Anuj Verma]

Thank you all for the comments.

I too agree with Werner.

I think comparing both the types seems to be a good option, So, I'm gonna do as Suzuki suggested

and use floats for my initial draft and later without floats.

And I'm not gonna focus on the saving part because the user can always do a conversion.

Also, can I directly use *float* or use FT_Fixed?

Thanks,

Anuj

On Wed, May 13, 2020 at 5:47 AM suzuki toshiya <address@hidden> wrote:

Dear Anuj,

I agree with Werner's comment.

It might be uncomfortable for you to leave an untested question, something
like "if I use a floating point calculation, the result could be better?".

Please use a floating point in your initial draft (if you want),
and let's discuss about the trade-off with the implementation
with no floating point, in later.

Regards,
mpsuzuki

On 2020/05/13 6:14, Alexei Podtelezhnikov wrote:
> I'll just add references below.
>
> On Tue, May 12, 2020 at 4:15 PM Werner LEMBERG <address@hidden> wrote:
>>> I can't decide which format to use for storing the SDF(signed
>>> distance fields).  I think using floating-point values (fixed-point
>>> in this case) for generation will be more accurate than using
>>> integer, but then saving the SDF to a file will require a
>>> conversion.
>
> The basic types are described here:
> https://jpn01.safelinks.protection.outlook.com/?url="">
> The computations are described here:
> https://jpn01.safelinks.protection.outlook.com/?url="">
> Saving files is not of FreeType's business. We just return data.
>
>> The basic question is whether the accuracy is really needed.
>> Currently, FreeType doesn't use floating-point arithmetics.
>> Personally, I would favour a solution without floats, but maybe there
>> are good reasons for using them.
>
>