Q: When using {{convert}} why does the answer sometimes seem a bit off?
A: This template takes into account the precision of the supplied value and generally rounds the output to the same level of precision. If you need to change from the default output precision, see rounding.
Note: This can cause whole numbers that end in one or more zeroes to be converted less accurately than expected.
Q: What are all the possible units (kg, lb, m, cm, ft, in, °C, °F, km, mi, nmi, mph, km/h, and so on)?
Q: I've been using Convert for some time and am pretty comfortable with its basic features. Does it have other features which it would be worth my while to learn about?
Template:Convert is permanently protected from editing because it is a heavily used or highly visible template. Substantial changes should first be proposed and discussed here on this page. If the proposal is uncontroversial or has been discussed and is supported by consensus, editors may use {{edit template-protected}} to notify an administrator or template editor to make the requested edit. Usually, any contributor may edit the template's documentation to add usage notes or categories.
Any contributor may edit the template's sandbox. Functionality of the template can be checked using test cases.
Can we please get suf1 and suff2 parameters added to this template, like done at Template:Change, so that we can add references or notes to the first and second numbers in the template, respectively? Cheers, Hwy43 (talk) 20:10, 26 December 2024 (UTC)[reply]
The purpose of convert is to take a single number and convert it into the equivalent in different units of measurement. All numbers displayed come from that single input. So why would we need a second reference?
Likewise, why would we have different notes for each unit of measurement? Surely a single reference and/or note cover all the units used. Can you give an example? Stepho talk23:42, 26 December 2024 (UTC)[reply]
Good point re: single input. Rather, a suffix parameter is desired just for after the first number because it is the one that can be sourced, whereas the second is a product of the template. Same with notes being based on the first number. See the Flin Flon and Lloydminster rows at List of cities in Saskatchewan#List. In those two cases, I want the notes to be displayed after the first number, not after the second (conversion) number as currently shown. Cheers, Hwy43 (talk) 00:29, 27 December 2024 (UTC)[reply]
Fair enough, this only applies to tables. The |pre= option (with the ref as the next field) can be twisted into doing what you want. {{convert|2.01|km2|sqmi|disp=table|sortable=on|adj=pre|<ref group=SK>col1 note</ref>}} gives:
I suppose so but after all these years without it, I wonder if a new unit would be much benefit. Would cmil be used in any other articles or would it only be used for the approximate values shown in this article? Any thoughts from watchers? Johnuniq (talk) 00:23, 29 December 2024 (UTC)[reply]
Some units not getting localized/translated
Hello, new to this, but any idea why units might not be getting correctly transliterated? Didn't get any response on Bengali wikipedia so decided to ask here.
The issue is on the top of this page: bn:স্থানীয়_গোষ্ঠী. What I want is megaparsec and light-year to be correctly transliterated as মেগাপারসেক and আলোকবর্ষ, just like kilometer is being transliterated as কিলোমিটার. Those articles do exist on the BN wikipedia.
Thanks! Babaisarkar2 (talk) 10:48, 1 January 2025 (UTC)[reply]
