Closed davelab6 closed 10 years ago
This is how both these libs working with canvases. I can't do anything about it.
Opentype creating counter like point by point path, and in paperjs we are rendering it like bunch of bezier curves path. So i can't do opentype sharper, without modifying it. But !maybe! building with paperjs like opentype does will do same fuzzy effect if guys from paperjs don't do anything with canvas rendering it self.
Paperjs build glyph function if somebody interested: https://github.com/nodebox/opentype.js/blob/master/opentype.js#L441
I dont want fuzzy - I want opentype to be sharp :)
It looks like the paperjs version is stroked...
I'm curious if https://github.com/metapolator/metapolator/issues/91 will give a 3rd different result given the same data :) Let's finish that one first
Canvas size is different, so shape is jumping. But main is that we get the same shape precision on all methods.
Following https://github.com/metapolator/metapolator/issues/62 ... :)
On Mac OS X, the PaperJS rendering of the 'a' at the top of metapolator.com is sharp:
and the OpenTypeJS 'a' below it is fuzzy:
But the PaperJS version is darker than the OpenTypJS version -- which is most accurate?
![preview003](https://cloud.githubusercontent.com/assets/261579/2535216/e32a5d38-b58a-11e3-83ec-722f07f2a682.png)