Adobe contributed a CFF backend to Freetype - it fits into their overall CFF (vs truetype) strategy, but somewhat unrelated either at the strategic level or tech/ABI level to open-source-ing the rest of their tool set, say, the proprietary part of AKDKO further. That does not go towards (partially) open-sourcing Indesign/Illustrator etc.
My (private) proposal involves untangling the Microsoft Apple cross-licensing mess regarding truetype.
This thread began with a representative of Google, from time to time the richest, most powerful and resourceful company on the planet, soliciting requests as to how they might allocate upcomng time and money in the realm of type and typography
[…]
The point of my comment was that Google can likely more efficiently finance the further development of existing open source illustration and layout projects, to more benefit for Google Fonts type users, than other alternatives.
This is a great point.
@Dave Crossland On Google docs and slides, is there a plan to include missing Noto fonts and/or improve the rendering for some scripts (e.g. Nastliq)?
@Dave Crossland On Google docs and slides, is there a plan to include missing Noto fonts and/or improve the rendering for some scripts (e.g. Nastliq)?
There is, and it has occupied my life for the past three months! We are currently loading all of Noto into Workspace, and aim to have this done by the end of the year. I've also fixed quite a number of Noto bugs, but if you have any problems with rendering (especially Nastaliq) please let me know via the bug reporter.
Comments
My (private) proposal involves untangling the Microsoft Apple cross-licensing mess regarding truetype.
@Dave Crossland On Google docs and slides, is there a plan to include missing Noto fonts and/or improve the rendering for some scripts (e.g. Nastliq)?