X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com Date: Wed, 6 Feb 2019 03:53:52 +0100 (CET) X-X-Sender: igor2 AT igor2priv To: "Girvin Herr (gherrl AT fastmail DOT com) [via geda-user AT delorie DOT com]" X-Debug: to=geda-user AT delorie DOT com from="gedau AT igor2 DOT repo DOT hu" From: gedau AT igor2 DOT repo DOT hu Subject: [geda-user] dxf export, vector formats (was Re: PCB 4.1.3 png export acting weird) In-Reply-To: <02221dee-bb68-95bd-c28f-93db1f85043a@fastmail.com> Message-ID: References: <34d4880c-3aa0-26a2-0d02-ab740ccda6be AT fastmail DOT com> <1993f267-eaba-d065-2a84-11d33a165b8e AT fastmail DOT com> <02221dee-bb68-95bd-c28f-93db1f85043a AT fastmail DOT com> User-Agent: Alpine 2.00 (DEB 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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 Tue, 5 Feb 2019, Girvin Herr (gherrl AT fastmail DOT com) [via geda-user AT delorie DOT com] wrote: >reasonable amount, the image disappeared! I later read that LC prefers >vector graphics to raster bit-maps, of which PNG is, and suggests converting >the raster file to DXF using inkscape. I have tried that in the past, but >with less than successful results. For anyone interested in more vector export paths that don't convert to raster on the way: pcb-rnd can export to DXF directly (since summer 2017). Also can export to svg (probably not useful with LibreCad, tho). The optional cam syntax (where you can specify what layers should go in what file) works with both (just as with png and ps and eps), so you don't need to work around ancient heuristics^1 and code bugs that differ from exporter to exporter. On the input side, pcb-rnd can load HPGL, which most mech CADs can plot - layer info preserved through pens. Regards, Igor2 Footnote: ^1: there are heuristics inherited from gEDA/pcb that make some exporters do real strange things depending on whether layers are empty and/or visible. Empty not as in "has nothing on it", but as in "has nothing but side effects on it". Side effects are outline and padstack (was pin/via/pad in pcb). These mechanisms and how they interact with exporter options unfortunately tend to vary from exporter to exporter. I decided not to throw them out because there are user scripts/makefiles/musclememory depending on these. Instead I've introduced the optional cam syntax that solves this for all exporter the same way, without having to change the old ways. Ever since, I recommend users to try the exporter as is, because defaults most often do what they want; but if it's not the case, it's the easiest to use the cam syntax and just provide an explicit list on what layers should go in which file instead of learning how to work around the heuristics on a per exporter basis.