Re: Removal of plugins and collab from FontForge

We should try to keep native and python features similar.
The FontAnvil fork happened because someone suggested deleting the native 
script tree.

On April 1, 2019 02:03:08 AM [email protected] wrote:
> Better yet, why not just add the equivalent of AddEncoding to the python
> interface and redo it there? We already have the callback model in
> registerImportExport ...
> 
> Skef
> 
> On 4/1/19 1:50 AM, T J wrote:
> > As for gb12345, instead of having it as a plugin, we might as well
> > convert it to an in-source compile option, like every other feature
> > that FontForge has.


_______________________________________________
fontforge-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fontforge-devel
http://fontforge.10959.n7.nabble.com/Developer-f3.html