X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com 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 :content-type; bh=zn7xKB6SoSyn9mAWA+S3UlAOrYuccEJBEFbUNJuQKmo=; b=z43ZQ2SjZpOWRKLB6OPveO/E2GcgExUW8ugJEJMJnd7e/Tax9M2LBjz38KJ9aVlnLS BlnWoWuvVoj4p15Kxv2iLhSdLBNcxak8hB7nIoG4jUU6QPNjtZoVT7zux0UpPYCTHG/A L3w01Pm6vbak9U5Y9l2YbkCLG3W0HBSTtxe8vmkj2KBUdVIyclp5XPftiiUFsc6VKOW5 a5yTDnGzgYepAhqIqsCjj927ojnoBfUyMtjCF2et7iwYOCacNliBaA29dXqLG+gVVmpg YPVLbm8aX1UOhVnLNluxsJN3mafw/Td04s31AZGkaEn56JxsyslEQ2KhVsN9Jb8yK2CD YUeQ== MIME-Version: 1.0 In-Reply-To: References: <20121116030224 DOT 5c7750ee AT akka> <201211160225 DOT qAG2PrVD005630 AT envy DOT delorie DOT com> <20121116035513 DOT 14519 DOT qmail AT stuge DOT se> <201211160357 DOT qAG3vUXo017504 AT envy DOT delorie DOT com> <20121116041216 DOT 16057 DOT qmail AT stuge DOT se> <201211160428 DOT qAG4Sh3h018631 AT envy DOT delorie DOT com> <20121117163351 DOT 14988 DOT qmail AT stuge DOT se> <5C6FC5CD-A358-476D-A8CA-C9AF2E72A914 AT noqsi DOT com> <20121117185520 DOT 25698 DOT qmail AT stuge DOT se> <9C626D0F-7D63-4FBE-8D63-37A2FFAD96FE AT noqsi DOT com> <71EA2CF8-8F64-4A51-B7C4-5F26EE8F4088 AT noqsi DOT com> <25B41A6E-E2ED-4EEB-ADAE-558B8BCFB993 AT noqsi DOT com> Date: Mon, 19 Nov 2012 14:03:40 -0500 Message-ID: Subject: Re: [geda-user] git mirror of gedasymbols.org From: Evan Foss To: geda-user AT delorie DOT com Content-Type: text/plain; charset=ISO-8859-1 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 Mon, Nov 19, 2012 at 11:24 AM, John Doty wrote: > > On Nov 19, 2012, at 9:05 AM, Evan Foss wrote: > >> I will concede that right now the current mechanisms have a kind of >> honesty in that what you enter into the gschem is very literally >> translated into the SPICE code. However, the values as written in >> SPICE are just a shorthand invented because of the primitive days >> SPICE was written in. We don't typically write schematics for >> documentation using that notation. > > I'm not objecting to that. I am pointing out that it may be nontrivial to decide what strings to translate. The thing I won't implement is a sloppy heuristic approach. A clear, easily explainable set of rules is necessary. You don't know me but I don't do half baked architecture. I was just suggesting we think about it. I do not care for appending everything with the SI at the end. I need to think on this idea more. > John Doty Noqsi Aerospace, Ltd. > http://www.noqsi.com/ > jpd AT noqsi DOT com > > > -- Home http://evanfoss.googlepages.com/ Work http://forge.abcd.harvard.edu/gf/project/epl_engineering/wiki/