On Sat, Jun 6, 2015 at 12:26 AM, Justin Lecher (jlec) <j...@gentoo.org> wrote:
> -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA512 > > Hi everyone, > > Can we get an agreement on how we are indenting metadata.xml? > > I like to properly format and indent metadata.xml, but without having > an agreement or policy on the indention, I make unhappy by choosing > the wrong. > I was going to stay out of this, but I want to kind of circle back a bit. You want to 'properly format' the documents. I guess part of my question is, what would you do if the proper format was basically undefined? "Properly formatted" XML files isn't really what I consider a goal. Do you have other goals? For instance: "I would like to standardize on spaces or tabs so that we can better automate the tooling around metadata." Or perhaps more clearly: "I am writing tools that manipulate metadata.xml; while I can easily ingest metadata.xml, producing the correct output is difficult when spaces or tabs are mixed, can we consistently use one or the other?" Or another take: "I am trying to write a tool that manipulates metadata.xml and I am having difficulty parsing entries that mix spaces and tabs, please help me." Some of these problems are solved by code (I'm pretty sure the latter problem just requires a sane XML parser for instance.) I believe mgorny already provided code that tried to solve problem 2. Problem 1 is sufficiently generic that it is hard to solve with a code snippet I think. The point is these are all goals other than "I want to standardize on tabs or spaces because I like starting tabs vs spaces flamewars on gentoo-dev." This is not meant to be accusatory; merely that standardizing the format "because" doesn't really solve anything (there is no problem statement.) Perhaps there is an implied statement (consistency is generally better for all parties.) But even that being clearly stated would be nice. -A > > The two options which are already suggested are > > * 2 spaces > * single tab > > So what should it be? > Jusitn > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2.0 > > iQJ8BAEBCgBmBQJVcqCPXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w > ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ0QUU0N0I4NzFERUI0MTJFN0EyODE0NUFF > OTQwMkE3OUIwMzUyOUEyAAoJEOlAKnmwNSmivxIP/3Vdv8fLVThtEdjknncX8txq > DSEj1m+pEqVw53noSQscbvjRkiAiGg50xtZFC5zcJVC7cRSIAADGUByakt7w+Lmk > D2cHWfQLJr5ZqGMholHdHJC7G7PXDJZ4D90Rt8qL7I1aGjMzWtGXzkzx2+OD+j8F > jy8XAa2I30/Rgof+fsUp1mgglv5c4Y94CbJcnkbERuyxA5miB2d1E3i3iiIcoLmB > M2fs0DN3oOQT8Fhwp2fJhoRH+aXlayC8o5PbBEKc6xGU5nfvtfvqqGHa9eoqLgXv > vpZXIwKm9vujXoPi7DDBMKAPPqDD1OSKBV0fvbwx0Q94H7XzmSmtFW45gPdAyrF2 > rwL3dlLcswDsblv46LHmj+m3/VFJagSccrKaH/I4uf4z2+RhjwNO2R+Z66/EYH3n > hvoYWQTx0Y+YI2kKKpXymK5e9ZgO7x+dxBHwLpa13JcJP0sMESQbN4jmJ5Rob0xV > bqtTsn+/O/rB1iMMC2V1fq3cQT9AQZT3OKnyiXM6nwLDgae30cY4gCUkOqc/ULxp > Eakb5D82HlSWIo840BXNAoGOWI7vFrtaKndDukWn+kKk1SeKm3j2ocwzQ7Rzxsa8 > 60hfE2tsuo0wQBLxslxYyZnv/kPBS9PS8RtZrLpS5V6D4BGS/32zuBVhN1eP9dQ0 > dz0kj1uvehcz5/Dhgms4 > =e7QN > -----END PGP SIGNATURE----- > >
