X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com X-Authenticated-IP: 207.224.51.38 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Apple Message framework v1084) Subject: Re: [geda-user] Text formatting From: John Doty In-Reply-To: <4F5AFCE8.9030901@neurotica.com> Date: Sat, 10 Mar 2012 02:21:44 -0700 Message-Id: References: <1331337138 DOT 10630 DOT 1 AT kwak> <1331339779 DOT 2533 DOT 43 DOT camel AT AMD64X2 DOT fritz DOT box> <20120309165553 DOT 727c8400 AT svelte> <1331342109 DOT 2533 DOT 48 DOT camel AT AMD64X2 DOT fritz DOT box> <20120309225208 DOT 3c1a07a7 AT svelte> <4F5AFCE8 DOT 9030901 AT neurotica DOT com> To: geda-user AT delorie DOT com X-Mailer: Apple Mail (2.1084) Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id q2A9e8eg007649 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 Mar 10, 2012, at 12:04 AM, Dave McGuire wrote: > On 03/10/2012 01:52 AM, Colin D Bennett wrote: >> I'm not opposed to an optional feature that makes use of TeX, >> however. > > Just to jump in for a moment (I'm busy...in the middle of designing a board with gschem!)...I would absolutely LOVE this. I've no idea of how it could be implemented, though. TeX can pretty easily render to arbitrary-resolution output devices, but though I've used it forever I've never written any output support for it. Would we somehow talk TeX into generating vectors/strokes that gschem would then be made to understand? > > Does anyone have any thoughts of how that could be done? > Well, at Noqsi we have discussed making a gschem->TikZ filter based on lambda-geda (https://github.com/xcthulhu/lambda-geda). I use TikZ for timing diagrams in the LaTeX project docs already, so it's an obvious step. But Matt's off at grad school, so lambda-geda development is stalled. In general, I think the tricky problem with all of these schemes is going to be to keep content separate from presentation. Schematics feed a variety of things downstream, and, for example, a circuit simulator is likely to be confused if you feed it presentation metadata embedded in simulation code. John Doty Noqsi Aerospace, Ltd. http://www.noqsi.com/ jpd AT noqsi DOT com