Template talk:Australian dollar

Noting something for possible use later

Today I discovered that {{A$}} wasn't linking as it should to Australian dollar. Somewhat strangely, this must have been the case since this edit, which was made in June 2010, and which nobody has noticed until now. Despite later discussion at WT:AUSTYLE#Currency abbreviation revisited, nobody seems to have noticed that the template wasn't linking as per the WP:AUSTYLE currency statement that was agreed to and the template documentation. I've fixed the template for now, but I also discovered a discussion at Category talk:Currency templates#Overlinking that seems relevant. Although there has been no attempt to stop this template linking in the ensuing 2 months, probably because it already wasn't linking, I thought it best to note all this for future reference, should the need arise. The upshot is that since there is consensus at WT:AUSTYLE to have this template link, and this is reflected in WP:AUSTYLE, no changes should be made to stop linking without first consulting the Australian project. --AussieLegend (talk) 00:11, 15 October 2011 (UTC)[reply]

Why can't link=True work?

It's gotta be "yes"? why can't "True" also work? and why does it haft to be lower case "yes"? why why??? Anthony2106 (talk) 15:18, 10 November 2024 (UTC)[reply]

When I added that feature in 2013, I was copying the same parameters among a lot of currency templates and other templates. |link=yes was common to many templates, so it was an obvious choice. Making every template use similar parameters makes it easier to remember which template uses which parameter. On the flip side, we could make all templates support all variations of "yes", "true", "active", "link" and whatever other word of the month comes up - plus their upper/lowercase variations like "true", "True", "TRUE". That's a lot of work that needlessly complicates the template code (making a difficult editing job even more difficult - just look at the template source to see this). And trying to make all the templates by different authors agree is also hard work.

Is there a pressing need to have "true"? Stepho talk 23:41, 10 November 2024 (UTC)[reply]

No I just got used to using {{plot|section=True}}. Maybe there should be a template the returns true or false from a string and that template could be used in all the other templates that need a True/False, that way we could add all the variations one time and reuse them in other templates, or would that be too slow or something. Anthony2106 (talk) 02:28, 11 November 2024 (UTC)[reply]

A common yes/no/true/false template is a good idea. Not sure where to raise the idea though. But to play devil's advocate, some studies say that allowing too many variations just makes it more complicated to support - eg bot's modifying articles would now have to know about all variations instead of just yes/no. Stepho talk 02:41, 11 November 2024 (UTC)[reply]

But the bots can use the same words as the yes/no/true/false template and this could be asked on the village pump as that's for more complex questions, at least that's what Wikipedia:Questions says. Anthony2106 (talk) 03:23, 11 November 2024 (UTC)[reply]

After asking the village pump I learnt there is a yesno template it's called {{yesno}}. That should be used instead. Anthony2106 (talk) 03:46, 20 November 2024 (UTC)[reply]

What people usually do (nowadays?) is to interpret any value passed to the parameter as true by using the #if parser function. What people also do is create metatemplates so all variations of the reused code update the variants as well. The latter would indeed be time-consuming, though. Aaron Liu (talk) 04:12, 20 November 2024 (UTC)[reply]