2017-04-04 12:18 GMT+02:00 William_J_G Overington <[email protected] >:
> > ... developers prefer investing time in SVG renderers or existing font > technologies for OpenType (SVG fonts will come later when it will be > capable of doing the same things as OpenType, for now it does not cover all > the existing needs). > > Well, I do not know what developers prefer. There seems to be a need to > send custom emoji in interoperable Unicode plain text and I have put > forward an idea for how to do it. > You just know what you isolately prefer: can't you see that what you propose is even less powerfull than a **STANDARD** SVG path ? it already has eveything you 'propose", except that it is already widely implemented and developers will prefer reuing them directly. A SVG path looks like "M100,100h800v800h-800z" to draw a square 800-sized centered in a 1000-sized square, there's no need for "x" or "y", there are shortcuts already defined for horizontal or vertical strokes (using relative or absolute coordinates) and path closure, and it supports straight segments, cubic and quadratic splines and elliptic arcs. Its internal "machine" is very well documented (with extensive conformance tests for renderers, including for all supported geometric transforms and conversion of paths for creating stroke styles instead of filling them directly).
