[josm-dev] true/false against yes/no

[Mark Williams]

Andy Robinson (blackadder-lists) wrote:
> 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 doesn’t matter if
> its changed or not.
> 
> Cheers
> 
> Andy

Apart, of course, from Maplint complaining about it.
If you like to use tools like Maplint & the Validator plugin, it would
be nice if they actually agreed with one-another & the presets.

Mark

>> -----Original Message-----
>> From: josm-dev-bounces at openstreetmap.org [mailto:josm-dev-
>> bounces at openstreetmap.org] On Behalf Of Dirk Stöcker
>> Sent: 10 July 2008 3:01 PM
>> To: josm-dev at openstreetmap.org
>> 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)