X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com X-Injected-Via-Gmane: http://gmane.org/ To: geda-user AT delorie DOT com From: Kai-Martin Knaak Subject: Re: [geda-user] Apollon Date: Wed, 23 Sep 2015 11:04:17 +0200 Organization: Institut =?UTF-8?B?ZsO8cg==?= Quantenoptik Lines: 23 Message-ID: References: <20150913140631 DOT 1da1b78d AT jive DOT levalinux DOT org> <20150913190132 DOT 1926c471 AT jive DOT levalinux DOT org> <20150913204337 DOT 1e58475a AT jive DOT levalinux DOT org> <20150913231213 DOT 0a829971 AT jive DOT levalinux DOT org> <201509132244 DOT t8DMia3n005526 AT envy DOT delorie DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7Bit X-Complaints-To: usenet AT ger DOT gmane DOT org X-Gmane-NNTP-Posting-Host: 130.75.102.197 User-Agent: KNode/4.14.1 Reply-To: geda-user AT delorie DOT com DJ Delorie wrote: >> > xml is the most painful of the plain-text options. >> >> Yes. > > And yet, everyone begged for it back when... :-P > IMHO, xml it is a bit like C. The syntax supports painfully obfuscated but still syntactically legal and content. But nothing stops the programmer to write nicely formated, readable code. In the same vain, nothing stops geda tools from writing very legible XML files. A XML based format syntax could/should impose style standards in addition to the bare bones given by the tags. Again, this is very much like style conventions for coding. However, a parser would not need to know about the style. I would only have to look for the bare bone tags. ---<)kaimartin(>--- -- Kai-Martin Knaak