11 ms·
Good for Processing.js, but those desiring a replacement for sIFR or @font-face will be disappointed. Every browser that supports the Canvas does or is expected
by GHFigs 17y ago
Good for Processing.js, but those desiring a replacement for sIFR or @font-face will be disappointed. Every browser that supports the Canvas does or is expected to support @font-face as well, so there is no advantage there, and the required conversion to SVG only shifts the embedding rights problem one step away from the browser.
- iamcalledrob 17y agoWell, true, IE doesn't support <canvas> out of the box, but you can make it support it with something like excanvas. http://excanvas.sourceforge.net/ http://excanvas.sourceforge.net/
- f1lt3r 17y agoIt was not intended to be a solution to text on the canvas for anyone but people using the Processing.js language. There are already great tools for TTF rendering for websites like Cufon.
- f1lt3r 17y agoWhen you talk about shifting the rights problem one step further away, I wonder what exactly you mean? Surely the issue is the same regardless of the application layer in which the font's path data is being presented? The only issue being of course that the font's path data is publicly available. Am I missing something?