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:content-transfer-encoding; bh=LbUXWNYh8scL2govVA5QCrWw4oCDnpcGGln71htiN9M=; b=kwdqtnJJyi5WP1Ub4Oh6VLBh88DypviNmNDf63vlaoxT7wc62++f33Br33KzDnT47t pE4fNIdANFYKCx68sGKRMR9lSsdfJ1k/Wj07ft2eZxpcWGDMGrCByUW64PtRa7sPDcvu 3740luAwX80w1UKqPQPhppdW+Rwa76brTAafBjOwUdOtV2Nt/JtR+pTP301tLz9VvUku 1ooxY3YqHUN7owzVXeAD0tbuTNv8PooGhxUnb8sc/uyPg6SHP6zebdR5MgPp9Ai4M77r QwOaDcBLZco2IED4K7RrT7kqDrNxek/P9OlGXEacRrAVKWRMgWiNIlAKQWVnCVuNnXjq So2g== 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 11:05:25 -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=UTF-8 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id qAJG5UW2028700 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 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. On Mon, Nov 19, 2012 at 11:02 AM, Evan Foss wrote: > Seriously? You put an Omega at the end of a value for a resistance and > people know what that means. Ditto for the mu before a capital F. Why > would anyone put an SI unit for distance on an symbol in gschem? I > have put max. distance values on some nets to remind myself not to > make some signal paths too long but for that I usually use a comment= > which the netlister strips off. I would prefer that there be a > trace_length_max= or some such flag in gschem but it does not make any > sense to add it until... > 1. There is a C coded tool to bridge the meta data issue to PCB > 2. There is a mechanism in PCB to use said information. > Be we have already had this discussion. > > On Mon, Nov 19, 2012 at 9:31 AM, John Doty wrote: >> >> On Nov 19, 2012, at 6:50 AM, Evan Foss wrote: >> >>> Oh when I used Omega on resistors the old ones would fail. SDB might >>> have fixed it but there was some reason that I can not remember for >>> not using it. >> >> How should "mΩ" be translated? What about "MΩ"? Should "m" by itself represent "meter" (SI) or "0.001" (SPICE). Is there a simple, comprehensible rule to distinguish SI unit designations needing translation from strings that might resemble them but shouldn't be translated? >> >> 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/ -- Home http://evanfoss.googlepages.com/ Work http://forge.abcd.harvard.edu/gf/project/epl_engineering/wiki/