<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Image Vectorization: a Review · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/2306.06441/</link><description>Collected HN comments and submissions linking this paper.</description><language>en</language><lastBuildDate>Mon, 02 Nov 2026 11:16:22 GMT</lastBuildDate><atom:link href="https://hackerpaper.kaipfister.de/p/2306.06441/feed.xml" rel="self" type="application/rss+xml" /><item><title>Image Vectorization: a Review — mentioned by IuMaker</title><link>https://news.ycombinator.com/item?id=37495663</link><guid isPermaLink="false">urn:hackerpapers:mention:2306.06441:37495663</guid><pubDate>Wed, 13 Sep 2023 12:12:03 GMT</pubDate><description>&lt;p&gt;I considered running the vectorization before showing any of the elements to the user, so the user would be editing everything as a vector. I didn&amp;#x27;t go with this approach since the results of the vectorization weren&amp;#x27;t consistently good for all the images. But I&amp;#x27;m aware that the vectorization step is the step that requires more work, the problem is that it already has received most of it. The main options for the vecotrization are: - Straighter lines / smoother curvy lines - Less noise / more details [Advanced] - Number of colours: simpler vector / more details [Basic] I even looked for deep…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2306.06441/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.CV</category></item></channel></rss>
