It makes not a jot of difference. Since true/false and yes/no are used to mean the same then it will always be necessary for data consumers to look for either response on an element. personally I've been using my own preset file since JOSM has had that capability and all mine are true/false, plus I normally use the same when I manually add tags, especially for bridge=true. Not everyone will use the default presets so in reality it doesnt matter if its changed or not.
Cheers Andy >-----Original Message----- >From: [EMAIL PROTECTED] [mailto:josm-dev- >[EMAIL PROTECTED] On Behalf Of Dirk Stöcker >Sent: 10 July 2008 3:01 PM >To: [email protected] >Subject: [josm-dev] true/false against yes/no > >Hello, > >the Tagging Preset menu uses the values true/false for boolean elements, >whereas the majority of mappers seems to use the human strings yes/no. > >I would like to fix the code accordingly and switch to using yes/no. >Objections against this? > >To clearify: This does not affect existing tags, but only newly created >ones. > >Rationale: Get the stuff unified a bit more :-) > >Ciao >-- >http://www.dstoecker.eu/ (PGP key available) > >_______________________________________________ >josm-dev mailing list >[email protected] >http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/josm-dev > >No virus found in this incoming message. >Checked by AVG - http://www.avg.com >Version: 8.0.138 / Virus Database: 270.4.7/1543 - Release Date: 09/07/2008 >6:32 PM _______________________________________________ josm-dev mailing list [email protected] http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/josm-dev
