Settings and activity
40 results found
-
201 votes
Zaxonov supported this idea ·
-
233 votes
Zaxonov supported this idea ·
-
259 votes
Zaxonov supported this idea ·
-
406 votes
Zaxonov supported this idea ·
-
903 votes
Zaxonov supported this idea ·
-
4,721 votes
Zaxonov supported this idea ·
-
434 votes
Zaxonov supported this idea ·
-
1,698 votes
Zaxonov supported this idea ·
-
681 votes
Zaxonov supported this idea ·
-
2,071 votes
Zaxonov supported this idea ·
-
744 votes
Zaxonov supported this idea ·
-
3,267 votes
Zaxonov supported this idea ·
-
1,400 votes
Zaxonov supported this idea ·
-
22 votes
An error occurred while saving the comment Zaxonov supported this idea ·
-
143 votes
Zaxonov supported this idea ·
-
15 votes
Zaxonov supported this idea ·
-
946 votes
Zaxonov supported this idea ·
-
66 votes
Zaxonov supported this idea ·
-
1 vote
Zaxonov shared this idea ·
-
5,297 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