> I just want to clarify source control / merging workflow around
> here. Is it only using difference files via mail? I have made a
> fork onto Github, but I'm not sure if you'd like to use that for any
> vetting/review purposes.
I think it's better that I give you write access to the FreeType
Thanks for the link! It shall be helpful.
> any information you need or want?
Yes, I just want to clarify source control / merging workflow around
here. Is it only using difference files via mail? I have made a fork
onto Github, but I'm not sure if you'd like to use that for any
vetting/review pu
>> In general, I like a conservative approach so that C++ code can be
>> compiled even on older boxes. Admittedly, I'm not a big fan of C++
>> (and not a big C++ coder either), but given that FreeType itself is
>> written in quite conservative code, `qtinspect' should probably use
>> a similar pat
> I'd just like to point out a couple of resources for the rendering
> testing framework. [...]
Thanks!
Ewald, any information you need or want? I just want to point out
that the `fonttools' project might also give you further pointers for
the Type1->CFF transition.
https://github.com/font
C++98 might compile on older boxes, but Qt5 might not ;) I'd keep using
C++11 (and higher) for the nice things I hear about it and because of
Qt5.
___
Freetype-devel mailing list
Freetype-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/freetyp
2017-05-06 (土) の 19:47 +0200 に Werner LEMBERG さんは書きました:
> > The commits were made starting at 1dd90ae. I can rebase if needed.
>
> Please do so!
OK, I'll send it to the list again once I get around to do it.
> Some remarks.
>
> . Is C++11 really necessary? Or to ask differently, are the new
>
