Settings and activity
40 results found
-
199 votes
Zaxonov
supported this idea
·
-
231 votesZaxonov
supported this idea
·
-
254 votesZaxonov
supported this idea
·
-
392 votesZaxonov
supported this idea
·
-
838 votesZaxonov
supported this idea
·
-
4,622 votesZaxonov
supported this idea
·
-
428 votesZaxonov
supported this idea
·
-
1,635 votesZaxonov
supported this idea
·
-
669 votesZaxonov
supported this idea
·
-
1,946 votesZaxonov
supported this idea
·
-
737 votesZaxonov
supported this idea
·
-
3,082 votesZaxonov
supported this idea
·
-
1,377 votesZaxonov
supported this idea
·
-
21 votes
An error occurred while saving the comment Zaxonov
supported this idea
·
-
143 votesZaxonov
supported this idea
·
-
14 votesZaxonov
supported this idea
·
-
906 votesZaxonov
supported this idea
·
-
65 votesZaxonov
supported this idea
·
-
1 voteZaxonov
shared this idea
·
-
5,239 votes
The reason why the PDF files are so big is because the writing is drawn by a series of plain circles of different sizes that are linked together (image 1 in attached file). That's a nice trick for a nice handwriting fidelity, getting different kinds of pen and for the eraser to work like intended.
In order to reduce the PDF, Goodnotes would have to :
- identify every single character or drawn forms. (I don't think that a trivial routine to code...)
- merge circles that form that particular shape (image 2 in attached file) and everyone who worked in a vector based program like Illustrator or Affinity Designer would know that there are cases where merging doesn't work like we want...
- simplify the path by removing the while still being faithful to the path (image 3 in attached file).
All that in an automatic exporting routing. When simplifying path in an app that can do the job, the artist has control over the procedure. So making a flawless simplifying curve routine would be a very difficult beast to tacle :)
But I still have voted for this suggestion :D