Extension talk:UnitsFormatter

Unit Names
One area which probably needs some work is in the names of units. For example, can we do something less cumbersome than "British gallons" and "US gallons", while still being unambiguous? One huge piece of nastiness in the unit table is the calories and BTUs. It would make sense to have one unit just called "calorie", but I could not find any evidence that there is one particular version which is predominant. Any ideas? JohanTheGhost 16:15, 21 June 2007 (UTC)


 * I would love it if you could include a user preference that allowed for always using the abbreviation instead of the full unit name for the primary unit. I administrate a wiki that has a lot of plant data with leaf measurements, and seeing the full names of centimeters and inches over and over makes the reading more cumbersome than seeing the abbreviations.  Overall, though, I love this extension!
 * --76.215.127.150 (WildeRix) 21:02, 13 July 2007 (UTC)

Parser Function
I think this extension would be useful as a Parser Function in addtion to (or instead of) an extension tag. The calling could be akin to  . This way you gain the ability to interpret template parameters and extend the functionality. -- Jimbojw 16:42, 21 June 2007 (UTC)


 * Aha! That nicety (interpreted parameters) had escaped me.  I actualy started with it as a function (   for 67 celcius, 1 digit, alternate units kelvin), but thought a tag would be less cumbersome.  Of course, I could call the parser to process the input at the beginning -- is a function more efficient than that?


 * Or how about:


 * ie.
 * scrap the "digits" parameter, just use the input precision (which I do by default anyhow)
 * alt units just specified as additional units (here us gal and litres)
 * second parameter for realm
 * ...? JohanTheGhost 18:27, 21 June 2007 (UTC)