delorie.com/archives/browse.cgi   search  
Mail Archives: geda-user/2013/01/15/12:29:57

X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
Date: Tue, 15 Jan 2013 09:28:50 -0800
From: Larry Doolittle <ldoolitt AT recycle DOT lbl DOT gov>
To: geda-user AT delorie DOT com
Subject: [geda-user] Data Sheets (was: Lowering the cost of a starting a gEDA project)
Message-ID: <20130115172850.GA5543@recycle.lbl.gov>
References: <87wqvhd4tw DOT fsf AT gmail DOT com>
<kd21ao$j6j$1 AT ger DOT gmane DOT org>
<20130115013756 DOT 9917 DOT qmail AT stuge DOT se>
<CAOP4iL0yLZ-gvovCy5zCmJyjOXUUaoOB5U1+6CqcD20BM15FiQ AT mail DOT gmail DOT com>
<50F4E4D1 DOT 3010802 AT ecosensory DOT com>
<CAOP4iL1f=3TV5UKUjyJtpUw_5oBDxpk=5S2F=dEcUC2UYiNhVQ AT mail DOT gmail DOT com>
<878v7uv4gl DOT fsf AT gmail DOT com>
<50F58A89 DOT 1040004 AT ecosensory DOT com>
MIME-Version: 1.0
In-Reply-To: <50F58A89.1040004@ecosensory.com>
User-Agent: Mutt/1.5.20 (2009-06-14)
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

On Tue, Jan 15, 2013 at 10:57:45AM -0600, John Griessen wrote:
> What is a good place to keep datasheets handy for redesign/reuse, and is there any optimum
> compression method for them?  Are there tools that will disassemble pdfs, apply
> best compression, and reassemble them so they are equivalent?  Some are compressed more than others.
> Should we just leave them as their creators published them to be a legal document specification?
> They're almost always public.

I recommend only storing meta-information about the datasheets:
  upstream URL, and date fetched
  possibly private backup URL
  sha1sum
plus whatever index information is appropriate, like manufacturer
and part numbers described.

Thus someone copying the design, who wants to look at a datasheet,
can invoke a scripted (or GUI push-button) procedure: download from
the upstream URL, check the sha1sum, and 99% of the time, just show
the datasheet exactly as the original designer saw it.  If the
download fails or the sha1sum changed, try the backup and/or show
a warning that something changed.

PDF is a nice standard in some ways, but uniformity of structure
is not there.  If you do want to monkey around with the insides,
which I don't recommend, you should look at PoDoFo and pdftk.
I don't think compression is the issue.

  - Larry

- Raw text -


  webmaster     delorie software   privacy  
  Copyright 2019   by DJ Delorie     Updated Jul 2019