Closed HinTak closed 7 years ago
I kept dotnet 2 support mostly because dotnet2 runs under wine and the older FontVal 1.0's rasterization test requires genuine dotnet2 (i.e. not wine-mono). It is easier for comparison if both 1.0 and 2.0 run under the same-ish environment.
One action I contemplate, is to rename the current embedded-python branch as master and master as dotnet2 (this would upset most people who has a clone, on renaming branches). Or fork master into dotnet2 then merge embedded-python branch to master.
I like the former as it is neater, but it is rather upsetting to anybody who has already got a clone.
Upstream changed their mind a little after v4.0, so the FontVal v2.1 will be based on SharpFont v4.0+backports. See https://github.com/Robmaister/SharpFont/issues/95
SharpFont ( https://github.com/HinTak/SharpFont ) v4.0.0 started depending on net 3.5+ Linq . IronPython did the same with 2.7 . Mono 4.4 also starts to drop support below dotnet 4.5 .
I have stayed with mono 4.2 for building FontVal 2.0 for that reason.
My current master at mine has a patched SharpFont 3.x , and my hybrid+empy.2016-05-06 has IronPython 2.6, to stay dotnet 2.x compatible.
Currently the incentive to break dotnet 2.x support is not strong - you'll still need to patch SharpFont v4.0 to use it with FontVal anyway, so it is just from patching version x to patching version y. It would be more persuasive if all 3 of the issues form my 4 SharrpFont patches are incorporated upstream:
https://github.com/Robmaister/SharpFont/issues/82 https://github.com/Robmaister/SharpFont/issues/87 https://github.com/Robmaister/SharpFont/issues/88