X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
X-Virus-Scanned: amavisd-new at neurotica.com
X-Original-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=neurotica.com;
	s=default; t=1468786883;
	bh=KBMuoaDsdVYsDp+3mJRh0VWZGjCwEBOj3s6ECWAEj8w=;
	h=Subject:To:References:From:Date:In-Reply-To;
	b=OM/nozkvKZvNCG/SvXDVe8FCQd2KyIFvpn1kogxDZPDZZGXUn020OTQHRedTEvgBk
	 q4m53Hda9u6VjbreLu8k7RvkaEAG3T6qkVO3Ge5z5I954wDKMtKhyAt4yykPGJewf0
	 YiCNAUAQg8gaslrK6RfK4lQ4htiTaUxRMrAnVrik=
Subject: Re: [geda-user] New XML file format for schematics and symbols
To: geda-user AT delorie DOT com
References: <alpine DOT DEB DOT 2 DOT 11 DOT 1607171601340 DOT 19102 AT nimbus>
 <nmgo92$hdq$1 AT ger DOT gmane DOT org>
From: "Dave McGuire (mcguire AT neurotica DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
Message-ID: <578BE8C2.7010407@neurotica.com>
Date: Sun, 17 Jul 2016 16:21:22 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101
 Thunderbird/38.8.0
MIME-Version: 1.0
In-Reply-To: <nmgo92$hdq$1@ger.gmane.org>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
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 07/17/2016 04:02 PM, Kai-Martin Knaak wrote:
>> I just merged a branch which adds support for an alternative,
>> XML-based
>> file format for gEDA schematic and symbol files.  You can find a
>> description of the new file format here:
>>
>>    http://hedmen.org/xorn/doc/api/html/geda-xml-format.html
> 
> cite:
> 
> /--------------------------
> B 0 0 17000 11000 15 0 0 0 -1 -1 0 -1 -1 -1 -1 -1
> 
> becomes
> 
> <box x="0" y="0" width="170" height="110" color="lock" width="0"/>
> \--------------------------
> 
> This is great! 
> A truly human readable format that I can successfully edit without 
> having the manual open at all times. 
> 
> What happens if xorn is presented with a box command that has the 
> parameters x= and y= swapped?

  It seems to me that it should be trivial to write a "normalize"
program through which one could pipe such an XML file, that would parse
the fields and output the file with the fields rearranged to conform to
the expected order.  The end result would be logically equivalent, and
an XML parser would treat it the same way, but then it could still be
processed by scripts which rely on hard-set positions for parameters
that aren't actually otherwise parsing the XML.

                 -Dave

-- 
Dave McGuire, AK4HZ
New Kensington, PA