X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com X-Mailer: exmh version 2.8.0 04/21/2012 (debian 1:2.8.0-6) with X-Exmh-Isig-CompType: repl X-Exmh-Isig-Folder: inbox From: karl AT aspodata DOT se To: geda-user AT delorie DOT com Subject: Re: [geda-user] Scope of the hires flag in PCB file format? In-reply-to: References: <20180203160317 DOT GR12911 AT raven DOT inka DOT de> Comments: In-reply-to "Chad Parker (parker DOT charles AT gmail DOT com) [via geda-user AT delorie DOT com]" message dated "Sat, 03 Feb 2018 13:39:25 -0500." Mime-Version: 1.0 Content-Type: text/plain; charset="utf-8" Message-Id: <20180203192414.D5B84804CEFA@turkos.aspodata.se> Date: Sat, 3 Feb 2018 20:24:14 +0100 (CET) X-Virus-Scanned: ClamAV using ClamSMTP 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 Chad: > The pcb file format is a little difficult to interpret and work with. If you want to write to a pcb file it is straightforward, but parsing a random pcb/fp file can be a little problematic, I found some surprising examples while scanning through [1] for pin data which i saved to [2]. Examples: Long lines: Pin(0 0 70 36 "1" 257)Pin(0 100 70 36 "2" 1)Pin(0 200 70 36 "3" 1)Pin(0 300 70 36 "4" 1)Pin(0 400 70,,, Handling of ": Pin[15200 -15200 15000 2000 16200 7500 """10" 0x001] Numerical flags in [ ] notation Pin[0 20000 6000 2000 6600 3500 "" "1" 0x00004001] and possible a few more. A simple parser in perl for just "Pin" is in [3]. Regards, /Karl Hammar [1] :pserver:anonymous AT cvs DOT gedasymbols DOT org:/cvs/gedasymbols/ [2] http://aspodata.se/git/openhw/share/pcb/data_from_cvs.gedasymbols.org/all_pins [3] http://aspodata.se/git/openhw/share/pcb/data_from_cvs.gedasymbols.org/pins.pl ----------------------------------------------------------------------- Aspö Data Lilla Aspö 148 S-742 94 Östhammar Sweden +46 173 140 57