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=laserlinc-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=28W9ysMZAlDnCubXJmnshUdAYPoVU4tPMxhKWrRoaTk=; b=WHobJSJqZEoyg7lvY/kjodp7PyZNYbo5TnrU+BEcz9vEHRJNDMp4UR/HgZSNRXjU4z 0TxuQfdVmXNZEG6I7497vQD5pAhyJFE3a7y9dMPA6EZ3SoBeA/keSti4mfFw9owccPql 3kjFzkt6ZqDSDwfQYoJ5SvHS4JwJraF819p6dCxtqQQdVd+uYgcdF6z5UXNCCsDKtxxV Q0PN7D2YeyCMbsGTikRTO5nizzLoqwYjz0dfRkPhoDpN6XrKBuX6O0n/HNjzungb4Wg2 Sv6SiFTlvSuLYqmnlb82etyVp1swUJsG7LyPrYeph8yUZxHievQuiXq6MaLNqF5ZZiwe w8iw== 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:from:date :message-id:subject:to:content-type; bh=28W9ysMZAlDnCubXJmnshUdAYPoVU4tPMxhKWrRoaTk=; b=YW+sjv2fAeqhfrxE9hrCZ3DKKdn9avGjd+NOVppLc21YCXnFuXjJUcsjs+bxGeTGRH 8YFlrEcHgJX7WV5oP2g80ZWS2Y7t3XNKERfBMFF5lZdAv8W40/6+2DlGPqQ8yhUABKa/ b59f+1Yhkv5CFbzk7cJ9zZEEoRrybWnPbaGN6XSmg7spqfVn8zlnAwYA/V+Y+6/IAXMP n6juaGUWLi1Ez9xh2kXUhNwLgtwtZIGyqDSHY44il8fUhkTJAxYPbAGeiI9W9bsZyILu UT6SVMsE0Vlkil5SD0oaXGylg6mLMIPqsNV7nmFL6di+I+e9wcLV9+3rjkFoFKof/Kwt rgZw== X-Gm-Message-State: ALoCoQkfV7+Y9Lr4z2FMbUcq0p035eB91VSSMCXnvHYJfz+fMniYjHyEsN2apXVFMgaGlP2aeIksOZkbgtgRKYXkzmXVX4nDAg== X-Received: by 10.50.176.161 with SMTP id cj1mr2381850igc.57.1450440112330; Fri, 18 Dec 2015 04:01:52 -0800 (PST) MIME-Version: 1.0 In-Reply-To: References:

From: "Joshua Lansford (joshua DOT lansford AT laserlinc DOT com) [via geda-user AT delorie DOT com]" Date: Fri, 18 Dec 2015 07:01:33 -0500 Message-ID: Subject: Re: [geda-user] Interesting blog post from a commercial EDA vendor - pdf To: geda-user AT delorie DOT com Content-Type: multipart/alternative; boundary=089e0122a9f0a9f58a05272ae7be 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 --089e0122a9f0a9f58a05272ae7be Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Sat, Sep 5, 2015 at 12:57 AM, Russell Nelson (russnelson AT gmail DOT com) [via geda-user AT delorie DOT com] wrote: > > Now, there's no way we're going to wean the chip vendors off PDFs. What w= e > need to do instead is provide them with tools (like they're using now) > which can generate PDFs AND which can generate machine-readable specs. Th= at > means two things: > o Somebody has to define the specifications. Pin numbers, voltage > ranges, current consumption, frequency responses, etc. > o Once those specifications have been defined, the software has to be > written which can take that input data, and write out a PDF that looks > mostly like what they're sending out now, and generate the machine-readab= le > spec file. > > =E2=80=8BI know this is an old thread, but I had a thought. One such too= l which could produce the PDFs could be LaTeX. If a standardized template for a LaTeX data sheet for chips where defined perhaps even using a package of TeX macros, the TeX source itself would become a machine parsable chip datasheet format. As a bonus TeX produces HTML and perhaps other formats besides PDFs as well has having a very mature community surrounding it. ~Joshua --089e0122a9f0a9f58a05272ae7be Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

On Sat, Sep 5, 2015 at 12:57 AM, Russell Nelson (russnelson AT gmail DOT com) [via geda-user AT delorie DOT com] <geda-user AT delorie DOT com> wrote:

=

Now, there's no way we're going to wean the chip ven= dors off PDFs. What we need to do instead is provide them with tools (like = they're using now) which can generate PDFs AND which can generate machi= ne-readable specs. That means two things:
=C2=A0 o Somebody has to= define the specifications. Pin numbers, voltage ranges, current consumptio= n, frequency responses, etc.
=C2=A0 o Once those specifications ha= ve been defined, the software has to be written which can take that input d= ata, and write out a PDF that looks mostly like what they're sending ou= t now, and generate the machine-readable spec file.

=E2=80=8BI know this is an old thread, but I had a thought.=C2= =A0 One such tool which could produce the PDFs could be LaTeX.=C2=A0 If a s= tandardized template for a LaTeX data sheet for chips where defined perhaps= even using a package of TeX macros, the TeX source itself would become a m= achine parsable chip datasheet format.=C2=A0 As a bonus TeX produces HTML a= nd perhaps other formats besides PDFs as well has having a very mature comm= unity surrounding it.

~Joshua

--089e0122a9f0a9f58a05272ae7be--