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-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to;
        bh=H2wifZz8eFowBz1XCuT3r5Q5f0wxt/Z28Tmtx9equC8=;
        b=r/Ys/J5zKgeVSQuIWhZlTFJSFLJ+qidActF9e2yrrqpsYTHFK+4J4MDABM4IVlOjy4
         YLgTdBheul9522Lu95FgcDXjfn3qY5XCl3BTTVPC6qKSNDMnKn7pmtsv5YnfwpGJJ5eE
         DOdGg60rGXjPOj2Qc6V1uft4Dt8Qfmk7JuFAKnYv+AsYQN/4GID0QvzB90Xx1fILL1u4
         HS42mTKDk+Lss3bKFnXsO+8PHAtr9/0TOSl0eYFbyOiWhrndCqmDEgfmAEOGoisxVaXm
         nwP1yKI7P/8Zi04zCNJmRn7lVR7Rf44HyGWy9LkOMvfWWSix6IMKRUBW1mNy9+XEx3vW
         g5sg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20130820;
        h=x-gm-message-state:mime-version:in-reply-to:references:date
         :message-id:subject:from:to;
        bh=H2wifZz8eFowBz1XCuT3r5Q5f0wxt/Z28Tmtx9equC8=;
        b=VPdfWoO1n0U5p5cPYr1iOi+1FDipFJDiGzyswp4G0ywyZMo44av2ISrklbvnwzXfjg
         lxBD8S+k0knqiditF8Quse4XSq5XYOQEI6ftM8O6ZROWgjxNpsHqo3gYFL/dzGciIHJ6
         sulLpFKykAZvtQ3VG6F3ou+qko3MFbrHhG+lsZnoHLqmI/ZA4DWINXKqkfovNt8nUqxF
         vyM72zpMFVwQ0qDgrlb8WvJqJT9c/EZnZoArSeZ1W9Y+4ar7+I3iuruMjkYpSuT7fmww
         80PP6pgIkhBsUp9MZYIA+xxsv00zcERcxIsiUdQfXHmkpuSx4G6g+QTdkucRiCOzQ0+7
         aeYg==
X-Gm-Message-State: AD7BkJKT2TmCBZ80muMW7IUlQ+JIkwNYjEf+pq7lfc2zJ9C45SgSFM4TJqz2LJKkO7bdBUOkctRma0evUcElWQ==
MIME-Version: 1.0
X-Received: by 10.202.59.137 with SMTP id i131mr13641657oia.62.1457356918169;
 Mon, 07 Mar 2016 05:21:58 -0800 (PST)
In-Reply-To: <20160307123849.AF59B8153706@turkos.aspodata.se>
References: <56DCAE39 DOT 7020204 AT m0n5t3r DOT info>
	<nbijrc$t4t$1 AT ger DOT gmane DOT org>
	<CAHUm0tNohrmDf2oLQAWer_LYSPj9DZzquTdYM-kTgpaM9qO5Lg AT mail DOT gmail DOT com>
	<20160307015049 DOT 097EF8153704 AT turkos DOT aspodata DOT se>
	<CAHUm0tNztZc5nNTtC6in0MdihZnmkX0mG4UBmquSc+cT4nzEeQ AT mail DOT gmail DOT com>
	<20160307123849 DOT AF59B8153706 AT turkos DOT aspodata DOT se>
Date: Mon, 7 Mar 2016 23:51:57 +1030
Message-ID: <CAHUm0tPMRfV9ub3PXpKAGs9jEWKLJAZxnnwV_OGt38sHkMVv_g@mail.gmail.com>
Subject: Re: [geda-user] Valve / nixie symbols
From: "Erich Heinzle (a1039181 AT gmail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
To: geda-user <geda-user AT delorie DOT com>
Content-Type: multipart/alternative; boundary=001a113cc7f26ba46b052d755999
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

--001a113cc7f26ba46b052d755999
Content-Type: text/plain; charset=UTF-8

the translate2geda utility has addressed this problem of odd pin spacing by
being able to generate a symbol and a new bounding box from a list of pins
with specified spacing, if told to do so (WIP).

Once I roll the kicad converter code into translate2geda, I will be able to
allow this as an option, plus, I could add some heuristics to determine if
there is an optimal magnification ratio to effect sane pin spacings.

The worst offending kicad symbols seem to be those converted to kicad from
Eagle.

The problem with re-spacing a symbol's pins, or exporting tragesym or
similar definitions, is you may lose appropriate positioning of additional
drawn eye candy, i.e. the symbol in the middle of a mixer module.

I will add export of a symbol definition format(s), as you suggest, as this
should not be too hard with my pinlist data structure.

Cheers,

Erich.

--001a113cc7f26ba46b052d755999
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div><div><div><div><div><div>the translate2geda utility h=
as addressed this problem of odd pin spacing by being able to generate a sy=
mbol and a new bounding box from a list of pins with specified spacing, if =
told to do so (WIP).<br><br></div>Once I roll the kicad converter code into=
 translate2geda, I will be able to allow this as an option, plus, I could a=
dd some heuristics to determine if there is an optimal magnification ratio =
to effect sane pin spacings.<br><br></div>The worst offending kicad symbols=
 seem to be those converted to kicad from Eagle.<br><br></div>The problem w=
ith re-spacing a symbol&#39;s pins, or exporting tragesym or similar defini=
tions, is you may lose appropriate positioning of additional drawn eye cand=
y, i.e. the symbol in the middle of a mixer module.<br><br></div>I will add=
 export of a symbol definition format(s), as you suggest, as this should no=
t be too hard with my pinlist data structure.<br><br></div>Cheers,<br><br><=
/div>Erich.<br></div>

--001a113cc7f26ba46b052d755999--