X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com X-Original-DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sendgrid.net; h=subject:to:references:from:mime-version:in-reply-to:content-type:content-transfer-encoding; s=smtpapi; bh=A0Ko8GTFBQfl6bEwkpBFR9QVFNg=; b=GNvdiPoEuXwuQVHE3+ Wsp8CZ++bwqn4GiHO7p7D3cBxAZdV77vRVK1Krbkd4wHjq7ktl3l9sycdQunJYSv 1hF77RxTIBF389U+pHRkoSqHrF3ZeHnCaf2vPS8t+7Z2cjGt5eKKMsgASTT5jKbE V1uXImVIZJ4nOlWTMJLNxsxCc= Subject: Re: [geda-user] A workflow for gEDA PCB font symbol/glyph creation To: geda-user AT delorie DOT com References: <20161213135952 DOT 3756D81075A5 AT turkos DOT aspodata DOT se> From: "John Griessen (john AT ecosensory DOT com) [via geda-user AT delorie DOT com]" Message-ID: <1eea1753-da43-c43c-3f41-fc67aac496bf@ecosensory.com> Date: Tue, 13 Dec 2016 18:16:23 -0600 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Icedove/45.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-SG-EID: V53lTA/kUP1+IqXnzXuv0M/cu/N8aMtf7nxyAyKnAkuW49Mf+OCaX6M2EHC31RyRJLUdyN7DF110vI 6lJM8yw80qV95lE5ROroAF4aaOnMGnW9+Q5iZqpyCQu6bJVW0Q1hpH0EzJJZypl3tJeC39mbucXkhZ kOpBacIx5QBwyU9DK/bAPGwg/jakOK9Dh+cLzaBkFGq321/LHB98iuYO34iocvaJhhef1x4bvg9ulv k= Reply-To: geda-user AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: geda-user AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk On 12/13/2016 03:27 PM, Erich Heinzle (a1039181 AT gmail DOT com) [via geda-user AT delorie DOT com] wrote: > I have made a bit of progress in automatically converting an outline > into a set of offset paths, but the end caps of the ascending and > descending limbs still need a bit of work, particularly for serif > fonts.... While you are thinking in this mode of converting outline to centerline based, do you think your code is close to usable to make a trace-from-outlines importer? That is, not importing fonts, but circuit traces from a raster scanned image, that is converted to outlines, maybe svg, maybe postscript? If the code created many short segments of different widths and seemed useless as is, that kind of "scanned in" result could become useful with pcb-rnd's every trace segment has attributes features. One could make programs that averaged out some of the noise, and chose a single value for a wavering line's center, and a single value for thickness also. Then the number of segments would go drastically down, and some human editing could clean it up quick.