Supporting an option deforming algorithm for <textPath>?

Hi all

A recent question on SO highlighted the fact that cursive alphabets may not
be well-served by the current textPath algorithm.

Supporting cursive languages may not have been a high priority 15-20 years
ago when the original spec was written, but it is probably more desirable

Should the idea of adding a new alternative algorithm be considered?
Perhaps one that specifies glyph deformation rather than simple rotation?


Received on Monday, 13 July 2015 10:37:07 UTC