>> I don't think so – at least, I hope that this won't happen.
>> Ideally, the OpenType specifications gets updated to use the
>> forthcoming W3C standard as soon it is finished.
>
> Given that we make SVG renderers "pluggable", even if this does
> happen, won't we be able to just resort to some
Hi Werner,
> I don't think so – at least, I hope that this won't happen. Ideally,
> the OpenType specifications gets updated to use the forthcoming W3C
> standard as soon it is finished.
>
Given that we make SVG renderers "pluggable", even if this does happen,
won't we be able to just resort
On Wed, May 8, 2019 at 10:19 PM Werner LEMBERG wrote:
>
> >> It's not completely off the table, but it seems to me that
> >> `svgnative' is preferable.
> >
> > Given that we want a pluggable renderer, the whole discussion is
> > moot.
>
> It's not moot at all IMHO. I want to have a default that
Dear Toshiya,
Thank you for taking the time to write so much. It's really helpful.
I already know about how callbacks in languages like JS and Python work and
I am also familiar with how function pointers can be used to implement
callbacks in languages like C. Your explanation made it even more
Dear Werner,
On 2019/05/09 14:47, Werner LEMBERG wrote:
at least, I hope that this won't happen.
Me too!!!
Regards,
mpsuzuki
___
Freetype-devel mailing list
Freetype-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/freetype-devel
