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=date:from:to:subject:message-id:in-reply-to:references:mime-version
	:content-type:content-transfer-encoding;
	bh=qO8MZYjKgQZdKJ8ujqbflntIaqM2e3YvD/QphPKwng4=;
	b=nbRJfUcsnVyXbjNNryztpvBa/zp5trrHkScegYXfkNuLq2mgG3TMrPz8KSlZKK4RUn
	xZo8Iv4c1d5vl6+w+4msM07qsh45ceb+HKUEmGBu+NQ1fUHJIAWnmNGLM25qZKWI16RS
	ZgPfa9iRvPj4wKbgsawWeexovDd0d7QqGm/fxz8V0mcCNaKK25FPV2im0fEUSlm5PXAc
	3FqJ/qzeR/JCGwqe2Gz1L3++npr0DLKSeTdEjXX739MsSz6Hu35xjc8ijFcvlbeg9gos
	kJQHgGLavAR1p6dvRLvHojRsAnbTSlcsspEn3HCs00U5LzwMCR9CaLglpQbRKovI9u14
	hrLw==
X-Received:	by 10.28.33.136 with SMTP id h130mr3159742wmh.93.1450442122370;
	Fri, 18 Dec 2015 04:35:22 -0800 (PST)
Date:	Fri, 18 Dec 2015 13:35:20 +0100
From:	"Nicklas Karlsson (nicklas DOT karlsson17 AT gmail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
To:	geda-user AT delorie DOT com
Subject:	Re: [geda-user] Interesting blog post from a commercial EDA vendor
	- pdf
Message-Id:	<20151218133520.6c7ee40aecd35085e54774aa@gmail.com>
In-Reply-To:	<CAGRhJMbTJ73uD1pOWDJ1C4G2UzH8dqMdFtNWQW578AoYKbitsw@mail.gmail.com>
References:	<CAOP4iL3YWQ_MH3HNnyDHMGCGeYFBmazwcw7Af_GATQzAUQJ57g AT mail DOT gmail DOT com>
	<alpine DOT DEB DOT 2 DOT 00 DOT 1509040545240 DOT 6924 AT igor2priv>
	<CAOP4iL16nduLqgjYrNm-2vTVdG4rYDAHSCY5Y9jQF-iUZKCW-g AT mail DOT gmail DOT com>
	<CA+uY=MQtXXofEd+3h396fL28R4LETJ2tf82ovKTZgrrVx=5K0A AT mail DOT gmail DOT com>
	<CAGRhJMbTJ73uD1pOWDJ1C4G2UzH8dqMdFtNWQW578AoYKbitsw AT mail DOT gmail DOT com>
X-Mailer:	Sylpheed 3.5.0beta1 (GTK+ 2.24.25; x86_64-pc-linux-gnu)
Mime-Version:	1.0
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

> > Now, there's no way we're going to wean the chip vendors 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 machine-readable specs. That
> > 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-readable
> > spec file.
> >
> > ​I know this is an old thread, but I had a thought.  One such tool 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

I would say LaTeX is very good for generation of PDFs only question is from what?

Ibis files provide quite a lot of detailed electrical information about the chip. Some chips also have BSDL files. CANopen use *.eds Electronic Data Sheet files and Profibus use *.gsd file but this kind of "automatic" configuration from eletronic datasheets is sensitive to errors.


Nicklas Karlsson

- Raw text -