This page is an archive of past discussions. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page. |
|
A discussion in July 2020 ( permalink) gave the result:
The rationale was that the amount of discussion is greatly reduced from earlier years and it would be desirable for a year's worth of discussion to be archived on one page rather than twelve. Johnuniq ( talk) 01:18, 21 July 2020 (UTC)
It seems there is no support for points, picas etc. yet. Abbreviations can be a bit iffy, because pt can mean picoton or pint (different dimension) and pc (i.e. pica = 12 point) also stands for parsec (same dimension). Furthermore, pt means something different in Tex (100/7227 in) than in CSS (1/72 in; bp in Tex). Besides the Postscript or DTP point, 1 pt = 1/72 in, I would also add quarter-millimeter q = 0.25 mm, Didot point dd = 0.375 mm or 0.376065 mm or 1/2660 m or 254/675 mm, cicero cc = 12 dd, twip = 1/20 pt. — Christoph Päper 00:23, 29 December 2019 (UTC)
The documentation notes that |xx|
(as in "2 × 3 in (5.1 × 7.6 cm)" vs. "2 in × 3 in (5.1 cm × 7.6 cm)") is deprecated because it does not conform to Wikipedia's Manual of Style (nor international standards). However, there does not seem to be an option to get the acceptable notation with area units: "2 × 3 in² (5.1 × 7.6 cm²)".
I believe this should be added, but I'm not sure how.
Another, less preferable variant would use parentheses: "(2 × 3) in×in ((5.1 × 7.6) cm×cm)". —
Christoph
Päper 13:13, 2 January 2020 (UTC)
When using |disp=table
or |disp=tablecen
with products like 2|x|3
or 2|by|3
, the template should add an automatically calculated sort value in the data-sort-value
attribute of the td
table cell element. —
Christoph
Päper 13:22, 2 January 2020 (UTC)
sortable
parameter:
off
: no explicit sort keyon
: default sort key, same as either product
or first
product
: sort by the result of the multiplication of two or three numeric valuesfirst
, 1st
, 1
, 12
, 123
: sort key is the first numeric value, possibly followed by the other(s)second
, 2nd
, 2
, 21
: sort key is the second numeric value, possibly followed by the other of twothird
, 3rd
, 3
, 321
: sort key is the third numeric value, possibly followed by the others of threemin
: sort key is the smallest of up to three numeric values, perhaps secondary sort by the medium of three valuesmax
: sort key is the largest of up to three numeric values, perhaps secondary sort by the medium of three valuesavg
, mid
: sort key is the arithmetic mean, i.e. the average, of up to three numeric values; usually yielding the same sort order as product
If you have, say, a rectangle 11 ft 8 in by 7 ft 4 in and want to put its dimensions into a single template, is there any way of doing what I would intuitively want to write as {{convert|11|ft|8|in|by|7|ft|4|in|m}}, or is this simply not supported by the template? Archon 2488 ( talk) 12:40, 22 January 2020 (UTC)
{{convert|2|by|3|by|12|ft|m}}
→ 2 by 3 by 12 feet (0.61 by 0.91 by 3.66 m)I haven't been able to find any documentation about support for photometry units (lumen, candela, etc). Is there any plan to add support for these? Archon 2488 ( talk) 12:38, 22 January 2020 (UTC)
I would like to know whether there is a way to calculate to the nearest multiple of 5 in case of decimal numbers. For example {{convert|10|yd|m|2}} gives out 10 yards (9.14 m). Is it possible to get 9.15 m (as used by the International Football Association Board for the penalty kick arc)? In this case |round=5 doesn't work. Thanks in advance.-- Carnby ( talk) 13:24, 30 January 2020 (UTC)
Hi, I have been trying to use disp=table in cells that sit across several rows, and this is what happens:
kilograms | pounds | stone and pounds | |
---|---|---|---|
Why??? | style="text-align:right;"|10 | 22 | 1 st 8 lb |
some | text | here |
Any way to get "rowspan" to also apply to the output? Thanks, Mr.choppers | ✎ 02:47, 30 January 2020 (UTC)
kilograms | pounds | stone and pounds | |
---|---|---|---|
Why??? | |||
10 | 22 | 1 st 8 lb | |
some | text | here |
@ Johnuniq: - No, I was looking for output to be displayed across two rows. I realize that my attempted example was non-functional (I didn't test it first, my bad), so here is what I want the table to look like (left) and what happens when I use the disp=table function (right):
kilograms | pounds | |
---|---|---|
10 | 22 | |
kilograms | pounds | |
---|---|---|
style="text-align:right;"|10 | 22 | |
I can make it work manually, I was just hoping to be able to use the template (the automatic alignment is nice, for instance). Thanks. Mr.choppers | ✎ 04:43, 30 January 2020 (UTC)
stylein
and styleout
. As the example at that link shows, you can set the style for the input and output, but there is no equivalent for rowspan.
Johnuniq (
talk) 06:05, 30 January 2020 (UTC)stylein
and styleout
may prove useful in other ways. Cheers,
Mr.choppers |
✎ 13:11, 30 January 2020 (UTC)
|disp=table
generates10
|22
10 || 22
|disp=table2
that puts out double bars on the same line instead of single bars on separate lines?
Stepho
talk 21:47, 31 January 2020 (UTC)
||
, and whether there was any difference. I decided to stick with what the old system did in case certain usages in tables required the two-line version. I have never noticed a difference and a quick test now does not show any difference.I replaced {{convert|10|kg|lb|disp=table}}
in the table above with what the one-line output would be, namely style="text-align:right;"|10||style="text-align:right;"|22
. Preview shows no difference to the table.
Johnuniq (
talk) 22:42, 31 January 2020 (UTC)
rowspan="2" | 10 | rowspan="2" | 22
rowspan="2" | 10 || rowspan="2" | 22
Is there a template which protects numbers from being converted? Example: the Standard Ten is named after the tax horsepower rating, so one has to write "10 hp" a lot. But then well-meaning editors convert this to kilowatts, even though a tax hp ≠ actual horsepower. Similarly, car wheels are nearly always measured in inches ( exception here), and are never expressed in millimetres. Is there a nifty template I can apply to this sort of data or should I just add hidden messages at all these instances? I feel that bots don't care much about my messages, so I was hoping for something similar to Template:Proper name. I am sure that these are not the only examples of nominal values which should not undergo conversion. Best, Mr.choppers | ✎ 06:57, 1 February 2020 (UTC)
Would it be possible to add a conversion for g-force? It would essentially be the same as {{convert|1|g0}} but would display as g and link to the g-force article. Thanks! — Huntster ( t @ c) 23:14, 2 February 2020 (UTC)
g
is gram, so what unit code should be used? Perhaps g-force
would be clearest? The name for g0 is standard gravity
. What name (abbr=off) should be used? You're saying the symbol (abbr=on) should be g
so perhaps g-force
could be the name? Or gravitational force equivalent
?
Johnuniq (
talk) 02:50, 3 February 2020 (UTC)
g-force
is the logical unit code, and g
(with italics) is the abbreviation, but you never see this as anything but the abbreviation. The long form can be g-force
/g-forces
, but it would be really strange to see it written like that anywhere. Is there a way to make the abbreviation the default, requiring abbr=off to be used to see the long form?g0
unit, the abbreviation should use the code ''g''<sub>0</sub>
. —
Huntster (
t
@
c) 03:34, 3 February 2020 (UTC)
I added two temporary units for testing. g0-temp
shows how g0
will work in the next release. g-force
is the new unit. Re the latter, there is no way to default to abbr=on and only show a unit name if abbr=off is used so the new unit uses g for the symbol and name. Examples:
{{convert|100|g0-temp}}
→ 100 g0-temp
convert: unknown unit{{convert|100|g0-temp|abbr=on|lk=in}}
→ 100
g0-temp
convert: unknown unit{{convert|100|g-force}}
→ 100 g (980 m/s2){{convert|100|g-force|abbr=on|lk=in}}
→ 100
g (980 m/s2)Let me know if this works. Assuming g-force is used it will be changed to a permanent unit in the next release. Johnuniq ( talk) 06:12, 3 February 2020 (UTC)
Appears to have problems. E.g., {{convert|1000000000|e6ha}} 1,000,000,000 million hectares (2.5×109×10 6 acres) Cheers. Lfstevens ( talk) 20:50, 4 February 2020 (UTC)
{{convert|125|e6ha}}
→ 125 million hectares (310×10 6 acres){{convert|125|e6ha|abbr=off}}
→ 125 million hectares (310 million acres){{convert|1000000000|e6ha|e15acre}}
→ 1,000,000,000 million hectares (2.5×10 15 acres){{convert|1000000000|e6ha|acre}}
→ 1,000,000,000 million hectares (2.5×1015 acres){{convert|1000000000|e6ha|e15acre|abbr=off}}
→ 1,000,000,000 million hectares (2.5 quadrillion acres){{convert|1000000000|e6ha|acre|abbr=off}}
→ 1,000,000,000 million hectares (2.5×1015 acres)The module was last updated in May 2019 and I'm planning a new update soon to cover some unit changes discussed since then. The first issue is that several energy units link to
Atmosphere (unit) (if lk=on
is used) but that article is about pressure and seems irrelevant. No units currently link to
Standard cubic foot which concerns a volume (actually, an amount) of gas.
The energy units that link to Atmosphere (unit) follow (full list is here).
unitcode default symbol name1
ccatm mJ cc⋅atm cubic centimetre-atmosphere
cm3atm mJ cm<sup>3</sup>⋅atm cubic centimetre-atmosphere
cufootatm kJ cu ft atm cubic foot of atmosphere
cuftatm kJ cu ft atm cubic foot of atmosphere
cuydatm kJ cu yd atm cubic yard of atmosphere
GLatm GJ GL⋅atm gigalitre-atmosphere
Glatm GJ Gl⋅atm gigalitre-atmosphere
impgalatm J imp gal⋅atm imperial gallon-atmosphere
kLatm kJ kL⋅atm kilolitre-atmosphere
klatm kJ kl⋅atm kilolitre-atmosphere
Latm J L⋅atm litre-atmosphere
latm J l⋅atm litre-atmosphere
m3atm kJ m<sup>3</sup>⋅atm cubic metre-atmosphere
MLatm MJ ML⋅atm megalitre-atmosphere
Mlatm MJ Ml⋅atm megalitre-atmosphere
mLatm mJ L⋅atm millilitre-atmosphere
mlatm mJ l⋅atm millilitre-atmosphere
scc mJ scc standard cubic centimetre
scf kJ scf standard cubic foot
scfoot kJ scf standard cubic foot
scy kJ scy standard cubic yard
sl J sl standard litre
USgalatm J US gal⋅atm US gallon-atmosphere
I think these units relate to how much energy can be obtained by burning a certain amount of a certain fuel. The issue was raised by Ws1920 for scf here.
What should the link be for the above energy units? Presumably Atmosphere (unit) is wrong? Should it be changed to Standard cubic foot? Johnuniq ( talk) 08:37, 4 February 2020 (UTC)
I plan to remove all the above listed units, along with scf2 and scfoot2 that were temporarily added on 9 December 2019 to Module:Convert/extra as tests (those units have not been used in articles). Johnuniq ( talk) 06:57, 19 February 2020 (UTC)
This template's notes say (in the Output with horizontal fraction bar section) that using a double slash (//) returns a horizontal bar fraction:
{{convert|1//2|in|mm|1}}→ 1/2 inch (12.7 mm) {{convert|2+1//2|in|mm|1}} → 2+1/2 inches (63.5 mm)
That's lovely, but it only addresses the input value. What is to be done if the input value is metric (say, 12.7 mm) and what I want is the converted figure to be one-half inch expressed as a fraction with a horizontal divider bar? 173.180.13.37 ( talk) 03:30, 20 February 2020 (UTC)
{{convert|12.7|mm|frac=-2}}
→ 12.7 millimetres (1/2 in)Speed isn't always a manifestation of energy waste
The conversion template page appears to be slanted towards fuel efficiency, ignoring rate of speed in favour of fuel consumption rate in examples of rates (x per y). This slant shouldn't be applied to wind speed. Note that wind is not a consumer of fossil fuels. Indeed, the wind is a manifestation of solar energy, and it will not be convinced to switch to a more politically correct fuel source, if such exists. Not everything fast causes climate change. Please add some speed examples to your conversion templates page (and, better yet, to your Help:Convert page, as well), so that other novice or occasional conversion templaters won't waste time as I did. Thanks-- Quisqualis ( talk) 01:00, 6 February 2020 (UTC)
I wondered if anyone can tell me if (and if so, how) this template can be used to display a speed which, from the source is known to be about 30 m/s, as "70 mph (110 km/h)". Thanks for any help. -- DeFacto ( talk). 18:23, 22 February 2020 (UTC)
{{convert|30|m/s|mph km/h|1|abbr=on}}
→ 30 m/s (67.1 mph; 108.0 km/h){{convert|30|m/s|mph km/h|abbr=on|order=out}}
→ 67 mph (110 km/h){{convert|30|m/s|mph km/h|abbr=on|order=out|round=5}}
→ 65 mph (110 km/h){{convert|30|m/s|mph km/h|abbr=on|order=out|round=10}}
→ 70 mph (110 km/h)A construction like {{convert| 8|km|0}}
produces 8 kilometres (5 mi). What I would expect is either 8 km (5 mi) or 8 kilometres (5 miles), not this odd mixture of unabbreviated and abbreviated, which looks amateurish. Of course I know we can get round it using {{convert| 8|km|0|abbr=on}}
[for 8 km (5 mi)], or {{convert| 8|km|0|abbr=off}}
[for 8 kilometres (5 miles)], but that is really not the point, it requires extra work just to do the right thing. The default when abbr is not used should be one or the other, not somewhere in between. Comments? --
Red King (
talk) 00:01, 22 February 2020 (UTC)
km
if they only saw that – of course, this is far more likely with uncommon units like 8
millisiemens (abbreviation 8 mS
).Hi, all. I would like to request the addition of the area unit feddan (or feddan masri lit. 'Egyptian feddan', for more details about the history of the unit, see this website). This is the last non-SI unit still used in Egypt. As an official source, this recent press release by the Egyptian CAPMAS (a government agency) lists the area of cultivated land in Egypt as 9.2 million feddans. The unit is also used in Sudan, Syria and Oman. ( source1 and source2). The addition of this unit was approved in August 2015 but it appears that it was removed later. It should be added with the other non-SI area units to this table. Conversion:
The unit can be used on many articles such as: Economy of Egypt, Agriculture in Egypt, etc. Note also that Egypt was an important country when studying the history of agriculture. Thank you. -- Meno25 ( talk) 15:59, 4 March 2020 (UTC)
In Syria, the feddan ranges from 2295 square metres (m²) to 3443 square metres (m²).What value could be legitimately assigned for the conversion? Tarl N. ( discuss) 23:50, 4 March 2020 (UTC)
{{convert|1.28|m}}
1.28 metres (4 ft 2 in){{convert|4.22|m}}
4.22 metres (13.8 ft)On my disply (1) returns 1.28 metres (4 ft 2 in)
(2) returns 4.22 metres (13.8 ft)
Why are they not consistent? --
PBS (
talk) 18:10, 21 January 2020 (UTC)
OK I found the answer in Template talk:Convert/Archive February 2015#Convert metric to feet and inches?
Indeed it is in the section Module:Convert/documentation/conversion_data#Length 24 lines down ten columns in.
Why the built in inconsistency? It is a real got-yer and not the behaviour of least surprise. -- PBS ( talk) 18:20, 21 January 2020 (UTC)
I came across it in a new article I have created called Widebeam. There there are draft measurements of under 4 feet and lengths of about 70 feet. I will go through and fix then to be one or the other. However I agree with User:Hawkeye7 comment "I don't see any call for the use of decimals" with feet (ie the default ought to be ftin for all of them). However I think that either decimal feet or feet and inches for all is preferable to the current inconsistency. -- PBS ( talk) 11:46, 22 January 2020 (UTC)
{{convert|2.16|to|3.24|m}}
and those over {{convert|3.24|m}}
{{convert|3.24|to|2.16|m}}
and those under {{convert|3.24|m}}
{{convert|2.16|to|3.24|m|ftin}}
→ 2.16 to 3.24 metres (7 ft 1 in to 10 ft 8 in){{convert|3.24|m|ftin}}
→ 3.24 metres (10 ft 8 in){{convert|2.16|to|3.24|m|ftin|order=flip}}
→ 7 feet 1 inch to 10 feet 8 inches (2.16 to 3.24 m){{convert|80|kg}}
then it should display in stones and pounds because the weight is under 30 stones, or if something is 4 inches or higher and less than 81 inches it ought to be in hands and inches (because I measure horses that way). Why on earth do you "prefer to see metres converted to feet and inches for things that are the same size as me, and decimal feet for things that are much bigger"? Is it a cultural thing? --
PBS (
talk) 16:46, 22 January 2020 (UTC)
ftin
to ft
at a predetermined value. Most uses of the template for lengths under about 3 metres will be heights of people, and for as long as I've been alive, imperial units have measured those in feet and inches. Once you start measuring larger objects such as the length of a ship, for example, it is fairly likely that you'll see a decimal representation if anything less than one foot is significant. I don't believe that is anything cultural. That's my preference and it depends on my perception of how I've seen measurements quoted, especially when I was younger. Why do prefer to see people's height measured in the same units as the length of a ship?.I think this behavior is undesirable in a collaborative encyclopedia. Someone comes along to fix an article that they're not deeply involved with; perhaps they saw a change in some value in a reliable source, and are cleaning up places that link to that source. The editor isn't aware of the ins and outs of converting meters to feet, so isn't aware the format will change when updating a value from 2.9 m to 3.1 m. Jc3s5h ( talk) 20:36, 22 January 2020 (UTC)
I don't mind which we use but the convert should avoid inconsistencie
{{convert|2.16|to|3.24|m}}
and {{convert|3.24|m}}
I would prefer the default to be feet and inches, but would prefer feet and decimal feet to the current mix. The convert template should fail safe when using default values, so that the output displayed in an article is consistent. -- PBS ( talk) 16:46, 27 January 2020 (UTC)
{{convert|2.16|to|3.24|m|ftin}}
and {{convert|3.24|m|ftin}}
ftin
with ft
for decimal feet. If you don't like the defaults, you specify the units. What situation can't be catered for by that? --
RexxS (
talk) 23:33, 27 January 2020 (UTC)
If you don't like the defaults, you specify the units.– Sure, after you’ve spent an hour trying to understand why some rows in a table are coming out in ft+in while others, coded the same way, come out in decimal feet, all the time wondering if you’re losing your mind. Not worth it, not nearly. Is there anything else in {convert} that works this way? Does kg come out in decimal lbs for large masses, but lbs+oz for anything under 15 lb, because that might be the weight of a newborn? E Eng 06:41, 28 January 2020 (UTC)
{{
convert}}
was used to add imperial measurements early on in the article, so not being really aware of how it works, (s)he will copy the original altering the number as appropriate. If the second {{
convert}}
is a scrollable distance down the article from the first, the chances are that a change to (or from) inches to decimal feet will not be noticed. This is why this template ought to fail safe, to protect the visual appearance of articles from editors who are not as familiar with the current quirks of this template as
User:RexxS is. As EEng asked, I too would like to know "Is there anything else in {convert} that works this way?" --
PBS (
talk) 12:56, 30 January 2020 (UTC)
I believe the majority view (I won't say consensus) is that the output should be consistently either ft+in or decimal feet (but not the second-guessing behavor) though there's disagreement as to which of those two is the better default, and it's unclear how much trouble it would be to change the behavior. Are we all together so far? E Eng 03:56, 3 February 2020 (UTC)
I have left it a few days to see if anyone else wished to add anything—it seems not.
@ Jc3s5h your post was facinating for me. In Britain all length measures commonly sold in hardware haberdashery and stationary shops are sold with metric and imperial either on one side (eg steel measuring tapes and rulers) or metric on one side and imperial on the other (eg measuring tapes sold in habadasheries). They are always in [yards occasionally], feet and inches, I have never seen a decimal foot measure. The only place I have seen 10ths used with imperial measurements in Britain is in a road vehicle's odometer/ Speedometer and Google maps which vacillates between yards and 10th of a mile. However because wood is cut in metric units, many timber merchants are unhappy selling short lengths of timber in imperial lengths (because they end up with unsellable offcuts) so some are willing to sell a colloquial "metric foot" which is 30cm or a "metric yard" (90cm) for those who can/will not think in metric measurements. The same is done with with width and bredth if the item is up to about 4x6", the merchants refer to the metric width and depth as "planed" so 2x1" planed is a actually manufactured as 50x25mm—ie about 1/64" per inch smaller than the old imperial size. With timber this works reasonably well, but is more problomatic with materials such as steel. However a similar rule of thumb is used for the length of wood screws, bolts etc.
It seems to me that in this thread there is a consensus to use one consistent conversion for all lengths. Everyone who has expressed an opinion on the conversion of peoples heights favours using feet and inches, therefore that has to be the default. @ Johnuniq can you and will you make the change? Further I suggest that if after the change is made if there are howles of anguish over the loss of decimal feet, then the change can be reverted and a bot can be run to make all the lenths that currently use decimal feet explicit, before remaking the change. -- PBS ( talk) 18:33, 14 February 2020 (UTC)
After enhancing some scripts I use, I have examined the converts that would be affected by a change in default output. I used the April 2019 database dump because that is the most recent I have.
For example, Auschwitz concentration camp#Auschwitz III-Monowitz uses the following, which would change to the second line:
Many "list" articles have tables that assume ft is the output unit. Examples:
I would be very reluctant to silently change how 128,777 converts behave without a widely advertised central discussion. By "silently", I mean that there would be no indication in an article's history that something had happened, and only a very observant page-watcher would notice that something needed to be fixed. Johnuniq ( talk) 03:52, 19 February 2020 (UTC)
Taking the first measurement in the first list example List of longest runways
removing the table parameter produces:
The 0 parameter controlling the rounding, which in this case AFAICT is the same as the default ( Template:Convert#Default rounding):
I don't think anyone would want that changed that default to either decimal feet or feet and inches.
but if the default displays decimal feet then convert it:
I understood the consensus above was to change thoses entries that by default display "decimal feet" to "feet and inches" (without messing around with the default rounding — which is a seperate issue). Infact the default rounding affect makes this proposition less invasive as most longer lenths will not be alted unless greater presision has been explicitly requested. -- PBS ( talk) 10:04, 5 March 2020 (UTC)
{{convert|5500|m}}
→ 5,500 metres (18,000 ft){{convert|5500|m|0}}
→ 5,500 metres (18,045 ft){{convert|5500|m|ftin}}
→ 5,500 metres (18,044 ft 7 in){{convert|5500|m|ftin|0}}
→ 5,500 metres (18,044 ft 7 in){{convert|5500|m|ft|1}}
→ 5,500 metres (18,044.6 ft){{convert|5500|m|ftin|1}}
→ 5,500 metres (18,044 ft 7.4 in)I had a look for converts which might give rounding problems if the output is changed to ftin. There are quite a lot of them although I didn't do a count. Examples:
Article | Convert | Current output (ft) | Output with ftin |
---|---|---|---|
MV Loch Sunart | {{convert|13.87|m|1|abbr=on}} | 13.87 m (45.5 ft) | 13.87 m (45 ft 6.1 in) |
Berlin Wall | {{convert|3.6|m|1|abbr=on}} | 3.6 m (11.8 ft) | 3.6 m (11 ft 9.7 in) |
Black Sea | {{convert|2212|m|2|abbr=off}} | 2,212 metres (7,257.22 feet) | 2,212 metres (7,257 feet 2.61 inches) |
Brasília | {{convert|70|m|2|abbr=on}} | 70 m (229.66 ft) | 70 m (229 ft 7.91 in) |
Frankfurt | {{convert|660|m|2|abbr=on}} | 660 m (2,165.35 ft) | 660 m (2,165 ft 4.25 in) |
Papua (province) | {{convert|4000|m|-3}} | 4,000 metres (13,000 ft) | 4,000 metres (13,123 ft 4 in) |
Mauritius | {{Convert|300|-|800|m|abbr=on|round=50}} | 300–800 m (1,000–2,600 ft) | 300–800 m (984 ft 3 in–2,624 ft 8 in) |
Several of the above (and a lot more not shown) are probably mistakes but they need to be handled somehow. Johnuniq ( talk) 06:49, 6 March 2020 (UTC)
|sigfig=
rather than |round=
or |(unnamed)=
. I've also changed the output to be actual conversions, not cut-and-paste as well as adding an extra column with the number of significant figures reduced by one:Article | Convert | Current output (ft) | Output with ftin | sigfig-1 |
---|---|---|---|---|
MV Loch Sunart | {{convert|13.87|m|abbr=on|sigfig=4}} | 13.87 m (45.51 ft) | 13.87 m (45 ft 6.1 in) | 13.87 m (45 ft 6 in) |
Berlin Wall | {{convert|3.6|m|abbr=on|sigfig=2}} | 3.6 m (12 ft) | 3.6 m (11 ft 10 in) | 3.6 m (11 ft 10 in) |
Black Sea | {{convert|2212|m|abbr=off|sigfig=4}} | 2,212 metres (7,257 feet) | 2,212 metres (7,257 feet 3 inches) | 2,212 metres (7,257 feet 3 inches) |
Brasília | {{convert|70|m|abbr=on|sigfig=2}} | 70 m (230 ft) | 70 m (229 ft 8 in) | 70 m (229 ft 8 in) |
Frankfurt | {{convert|660|m|abbr=on|sigfig=2}} | 660 m (2,200 ft) | 660 m (2,165 ft 4 in) | 660 m (2,165 ft 4 in) |
Papua (province) | {{convert|4000|m|sigfig=2}} | 4,000 metres (13,000 ft) | 4,000 metres (13,123 ft 4 in) | 4,000 metres (13,123 ft 4 in) |
Mauritius | {{Convert|300|-|800|m|abbr=on|sigfig=2}} | 300–800 m (980–2,600 ft) | 300–800 m (984 ft 3 in – 2,624 ft 8 in) | 300–800 m (984 ft 3 in – 2,624 ft 8 in) |
Is there a way to convert 1/64th of an ounce into metric units?-- Carnby ( talk) 17:43, 5 March 2020 (UTC)
{{convert|1/64|oz}}
→ 1⁄64 ounce (0.44 g) --
RexxS (
talk) 19:28, 5 March 2020 (UTC)Is there a way to put some text after the first part and before the second part of the unit to convert?-- Carnby ( talk) 20:46, 7 March 2020 (UTC)
Does this unit really exist?-- Carnby ( talk) 20:50, 7 March 2020 (UTC)
{{convert|1|ftlb/lbf|J/kgf|lk=on}}
→ 1
foot-pound per
pound-force (3.0
J/
kgf)Looking for a conversion of ton miles into kilometre-tonnes (kmt) tonne-kilometres.
Hawkeye7
(discuss) 05:45, 9 March 2020 (UTC)
I didn't find in Module:Convert/documentation/conversion data and any unit of information. I was looking for it for importing block size data from wikidata in hewiki, and before adding it to the Hebrew version of Module:Convert/documentation/conversion data I would like to raise it here. Eran ( talk) 16:15, 6 March 2020 (UTC)
Is there any chance of a time-zone conversion for date and time? In particular, converting from an arbitrary time-zone to UTC would be handy for things like {{unsigned}} which require a time in UTC. It wouldn't be quite the same as the units conversions here, so perhaps this is not the right place to ask; but then where is? Zero talk 04:47, 16 March 2020 (UTC)
The units 'short ton
', 'long ton
', and 'metric ton
' (not the unit 'tonne
') are unrecognised as parameter entries in plural form: {{convert|2|short tons|}}
returns as 2 short tons
convert: unknown unit
; {{convert|2|long tons|}}
returns as 2 long tons
convert: unknown unit
; and {{convert|2|metric tons|}}
returns as 2 metric tons
convert: unknown unit
.
Can anyone fix this please, next time there's an update? WT79 The Engineer ( talk) 18:12, 20 March 2020 (UTC)
I was looking for a conversion from "1 ft 11 5/8", a regular ft,in in writing. However, I could not find how to enter this, into a useful result. We shoud improve the /doc for this! - DePiep ( talk) 23:09, 2 April 2020 (UTC)
{{convert|1|ft|11+5/8|in}}
→ 1 foot 11+5⁄8 inches (0.600 m) --
RexxS (
talk) 23:37, 2 April 2020 (UTC)
Is there a way to output ftin with a non-breaking space between the feet value and the inches value?
As in, 2 metres (6 ft 7 in) where the space between "ft" and "7" is non-breaking? — Joeyconnick ( talk) 21:48, 12 April 2020 (UTC)
to get 2 metres (6 ft 7 in)
, or perhaps better:2 metres ({{
nowrap|6 ft 7 in}}
)
? Surely you wouldn't need to do it very often? --
RexxS (
talk) 00:37, 13 April 2020 (UTC){{
convert|7|ft|m|2}}
to give me the correct conversion of "7 feet (2.13 m)".{{
nowrap}}
suggestion is good.
Stepho
talk 11:34, 13 April 2020 (UTC){{convert|2|m|m|disp=out}}
→ 2.0 m{{nowrap|1=({{convert|2|m|ftin|disp=out}})}}
→ (6 ft 7 in)|disp=in
?), current workaround even changes the value (.0 added in the example). I have no opinion on the usefullnes of these changes (vs. time spend). -
DePiep (
talk) 15:02, 18 April 2020 (UTC)
{{
convert|2|m|ftin|abbr=on}}
"2 m (6 ft 7 in)" and it would be fine to break as:|disp=br
adds a line-break and omits brackets.
|disp=br()
adds a line-break and does add brackets to the converted value. This may be useful in tables:
|disp=br |
|disp=br()
| |||
---|---|---|---|---|
10 kilometres 6.2 miles |
10 kilometres (6.2 miles) |
1 km (0.62 mi) |
1 km 0.62 mi |
1 km (0.62 mi) |
Category:Convert errors now lists eight power station articles, eg Ace Embilipitiya Power Station. They use {{ Infobox power station}}, which pulls all data from WikiData.
The error occurs in row data59, "Site area" (WD area (P2046)). The example article has WD value "44 acre", OK. Somehow the unit is read as "ac" by Convert, throwing the error. All articles have this property in "acre". I was unable to do more research. ;-) - DePiep ( talk) 14:59, 18 April 2020 (UTC)
table#1 { table#2 { ["id"] = "Q25056880$2034aad9-4077-8f80-64e2-494f403e607f", ["mainsnak"] = table#3 { ["datatype"] = "quantity", ["datavalue"] = table#4 { ["type"] = "quantity", ["value"] = table#5 { ["amount"] = "+44", ["unit"] = " http://www.wikidata.org/entity/Q81292", }, }, ["property"] = "P2046", ["snaktype"] = "value", }, ["qualifiers"] = table#6 { ["P518"] = table#7 { table#8 { ["datatype"] = "wikibase-item", ["datavalue"] = table#9 { ["type"] = "wikibase-entityid", ["value"] = table#10 { ["entity-type"] = "item", ["id"] = "Q159719", ["numeric-id"] = 159719, }, }, ["hash"] = "92e50222d46cdef57f722b435fbab6b3e919014b", ["property"] = "P518", ["snaktype"] = "value", }, }, }, ["qualifiers-order"] = table#11 { "P518", }, ["rank"] = "normal", ["type"] = "statement", }, }
Quantity | Unit | Symbol | Derivation | Year | SI equivalent |
---|---|---|---|---|---|
Activity (A) | becquerel | Bq | s−1 | 1974 | SI unit |
curie | Ci | 3.7 × 1010 s−1 | 1953 | 3.7×1010 Bq | |
rutherford | Rd | 106 s−1 | 1946 | 1,000,000 Bq | |
Exposure (X) | coulomb per kilogram | C/kg | C⋅kg−1 of air | 1974 | SI unit |
röntgen | R | esu / 0.001293 g of air | 1928 | 2.58 × 10−4 C/kg | |
Absorbed dose (D) | gray | Gy | J⋅kg−1 | 1974 | SI unit |
erg per gram | erg/g | erg⋅g−1 | 1950 | 1.0 × 10−4 Gy | |
rad | rad | 100 erg⋅g−1 | 1953 | 0.010 Gy | |
Equivalent dose (H) | sievert | Sv | J⋅kg−1 × WR | 1977 | SI unit |
röntgen equivalent man | rem | 100 erg⋅g−1 × WR | 1971 | 0.010 Sv | |
Effective dose (E) | sievert | Sv | J⋅kg−1 × WR × WT | 1977 | SI unit |
röntgen equivalent man | rem | 100 erg⋅g−1 × WR × WT | 1971 | 0.010 Sv |
/info/en/?search=Template:Radiation_related_quantities — Preceding unsigned comment added by 2001:a62:1570:301:4449:56ee:9d2b:e309 ( talk) 12:23, 21 April 2020 (UTC)
This source gives the maximum elevation of the Ansel Adams Wilderness as 13,157 ft, and the minimum elevation as 3,500 feet. Let's say I want to convert that range to meters:
{{convert|3,500|–|13,157|feet|m|0|abbr=on|sortable=on}} outputs this: 3,500–13,157 ft (1,067–4,010 m)
I can't figure out how to specify different sigfig values for the two elevations. I'd like -2 sigfigs for the first number, and 0 sigfigs for the second number. CJK09 ( talk) 00:25, 30 April 2020 (UTC)
|0
is used, each output number is rounded to the nearest integer. In this example, that gives "(1,067–4,010 m)". If no rounding is specified, convert uses the highest precision of each item in the range on each item. Use |round=each
to have convert calculate the precision for each item separately. Fortunately that achieves what you want but it sometimes gives bad results.
{{convert|3,500|-|13,157|feet|m|abbr=on|round=each}}
→ 3,500–13,157 ft (1,100–4,010 m)Is there a way to render "an inch"/"a feetfoot"/"a mile" instead of "one inch"/"one feetfoot"/"one mile" when using |spell=on parameter? It would be useful when in a text caption there's "an inch"/"a feetfoot"/"a mile."--
Carnby (
talk) 14:15, 18 April 2020 (UTC)
|txt=
, and replaces One/one with A/An/a/an as appropriate. Here are some examples:
{{one2a |one foot. One mile. One inch.One amp. one foot. one mile. one inch. Alone at last.}}
→ a foot. A mile. An inch.An amp. a foot. a mile. an inch. Alone at last.{{convert|1|ft|spell=on}}
→ one foot (zero point three zero metres){{one2a|{{convert|1|ft|spell=on}}}}
→ a foot (zero point three zero metres){{convert|2.54|cm|0|disp=out|spell=on}}
→ one inch{{one2a|{{convert|2.54|cm|0|disp=out|spell=on}}}}
→ an inchI appreciate that a template can't enforce MOS requirements in every instance, but if there is a style that is clearly proscribed in every context then (providing there is no good reason not to) it seems reasonable to me to disallow output such as 7+1⁄4 miles (11+5⁄8 km). Either raising an exception or ignoring the frac option would seem sensible. What say? Archon 2488 ( talk) 11:58, 1 May 2020 (UTC)
{{convert|7600|ft|mi km|frac=8}}
→ 7,600 feet (1+1⁄2 mi; 2.3 km). --
RexxS (
talk) 22:27, 1 May 2020 (UTC){{cvt|9876.5|coulomb|A.h|frac=8}}
→ 9,876.5 C (2+3⁄4 A⋅h){{cvt|2+7/8|km}}
→ 2+7⁄8 km (1.8 mi){{cvt|2+7/8|km|frac=8}}
→ 2+7⁄8 km (1+3⁄4 mi)Can I use positional parameters from another template (for example, {{{1}}}). Imagine a template calle kcal and it is used in the same way in a page : {{kcal|1}} . The {{kcal}} code is: {{convert|{{{1}}}|kcal|kJ}} . Why does not it work?. It ask for a number (perhaps instead of a positional parameter as {{{1}}}}. But this type of functionality is also needed. -- BoldLuis ( talk) 18:40, 8 May 2020 (UTC)
<includeonly>
but with convert you could use:
{{convert|{{{1|NNNN}}}|kcal|kJ}}
Is there a modifier to get {{convert|1|m|ft|0|spell=in|abbr=off}}
to output "a" rather than "one", as in "about a metre (3 feet)" rather than "about one metre (3 feet)"? --
DeFacto (
talk). 15:59, 8 May 2020 (UTC)
about {{one2a|{{convert|1|m|ft|0|spell=in|abbr=off}}}}
→ about a metre (3 feet)How do I set the comma thing to both "gaps" and "5"?
{{convert|5000|ft||abbr=|order=flip|comma=5|comma=gaps}} didn't work. 146.255.181.208 ( talk) 21:04, 25 April 2020 (UTC)
comma=gaps5
used to do what you want (use gaps, but only if 5 or more digits before decimal point). However, it was disabled in
June 2015 and later removed. That followed a couple of discussions, at least one of which can be found by searching that archive for "gaps5". I believe that no converts used that option at the time—if there were any, it was a very small number.
Johnuniq (
talk) 01:19, 26 April 2020 (UTC)
My dear MOS warriors. In my travels I have realised that a despicable heresy, namely the abuse of imperial unit abbreviations as if they were SI symbols, is permitted by the template: 150 cm2 (23 in2). Compare, however, 150 cm2 (23 sq in), and 150 km2 (58 sq mi) – in the last case, the user's request for "mi2" is rejected in favour of the MOS-sanctioned abbreviation "sq mi". Is there a reason why "in2" is permitted? I appreciate that my pedantry is extreme, but it is in the name of a righteous cause. Archon 2488 ( talk) 22:22, 17 May 2020 (UTC)
in2
→ in2sqin
→ sq inmi2
→ sq misqmi
→ sq milbf/in2
(
example) although, for example,
Pump action#Rifles has two in2. If mi2 is needed (example?), it's easy to add.
Johnuniq (
talk) 23:54, 17 May 2020 (UTC)
Hi, noting that this:
{{convert|10e33|erg|J}}
produces this:
but this:
{{convert|10e33.5|erg|J}}
As of 21 May 2020 [update], it gets this error:
When I preview, this is an approximation in HTML of what I am seeing:
Please let me know if this gets fixed. There is a use for a corrected version at Proxima Centauri b.
Peaceray ( talk) 18:11, 21 May 2020 (UTC)
e
(exponent) notation is not identical to ^
(power) notation: 10^33.5 means "ten to the power 33.5", which is 1 × 1033.5 (optionally written as 1e33.5) – which is the same as 3.2 × 1033 (optionally written as 3.2e33). Hope that helps avoid any confusion. Cheers --
RexxS (
talk) 23:37, 21 May 2020 (UTC){{convert|{{#expr:10^33.5}}|erg|J|adj=ri1|sigfig=2}}
→ 3.2×10+33 ergs (3.2×1026 J)The documentation says:
"Value ranges can be entered using |to|...
or |-|...
:
{{convert|2|to|5|km|mi}}
→ 2 to 5 kilometres (1.2 to 3.1 mi){{convert|2|-|5|km|mi}}
→ 2–5 kilometres (1.2–3.1 mi)"which is useful in situations such as "from 1 to 3 meters (3 to 10 ft)" or "between 1 and 3 meters (3 and 10 ft)", which are rather common.
The problem is, I can't find the way to do that in VisualEditor. The feature seems to rely on position and doesn't seem to have a named parameter (or rather, I couldn't find it). If there is a named parameter for the "-", "to", "and" and perhaps other indicators, what is it called? And if not, could we have such a named parameter, please? -- Jhertel ( talk) 10:32, 5 June 2020 (UTC)
-
for a range, another 10,000 using x
, and 34,000 using to
. There are 600 like {{convert|28|x|34|x|15|cm|in|abbr=on}}
(in
Enigma machine). No one has devised a better syntax.
Johnuniq (
talk) 23:39, 5 June 2020 (UTC)
This example:
{{convert|1|to|3|m|ftin|abbr=on|sigfig=1}}
should render as "1 to 3 m (3 to 10 feet)", but renders as "1 to 3 m (3 ft 3 in to 9 ft 10 in)", which of course is more than 1 significant digit.
The documentation doesn't mention this bug.
-- Jhertel ( talk) 10:43, 5 June 2020 (UTC)
{{convert|1|to|3|m|ft|abbr=on|sigfig=1}}
→ 1 to 3 m (3 to 10 ft)|sigfig=
parameter applies to the smallest unit, because it wouldn't make sense to apply it to the larger units. Specifying a single unit allows the |sigfig=
parameter to apply to that unit, allowing any display desired. --
RexxS (
talk) 19:36, 5 June 2020 (UTC)Convert now links to a disambig — Preceding unsigned comment added by 85.242.253.165 ( talk) 17:37, 21 June 2020 (UTC)
Done
[6] (not by me, DePiep) -
DePiep (
talk) 02:46, 22 June 2020 (UTC)
I was recently reading Naval Air Station Joint Reserve Base Fort Worth, and I noticed that the “s” in “nautical miles” was not linked like the rest of the unit. The article appears to be using this template, so I believe this is a bug. Olea Capita ( talk) 07:04, 16 June 2020 (UTC)
This problem seems to occur only on the Wikipedia iOS app. Olea Capita ( talk) 07:30, 16 June 2020 (UTC)
{{convert|5|NM|0|lk=in}}
→ 5
nautical miles (9 km; 6 mi)5 [[nautical mile]]s (9 km; 6 mi)
= 5
nautical miles (9 km; 6 mi)Hi - the template puts a space before the units, which is usually correct, but in the case of degrees symbols there should not be a space (as outlined in the table at MOS:UNITSYMBOLS). Example: 120 °C (248 °F). Is there any way this can be rectified? Cheers GirthSummit (blether) 14:27, 27 June 2020 (UTC)
I was using Shaku (unit) and it works in the conversion template, although it is nowhere listed in the units available. Should be added, I think. Thanks, Mr.choppers | ✎ 03:09, 3 July 2020 (UTC)
An oddity:
Have I failed to understand something? Same for
E Eng 17:35, 2 June 2020 (UTC) E Eng 17:35, 2 June 2020 (UTC)
There is a tiny note above regarding angle units, but solid angle is needed too, and deserves its own discussion. There are many links to (non-SI) square degree which should have conversions to SI steradian. Gah4 ( talk) 00:52, 10 July 2020 (UTC)
I have noticed this in my travels:
{{convert|10|/L|/USgal|abbr=off}}
→ 10 per litre (38 per gallon) [i.e. the output does not disambiguate which gallon is meant]but
{{convert|10|/L|/impgal|abbr=off}}
→ 10 per litre (45 per imperial gallon).This issue seems to arise only with the reciprocal units – 10 litres (2.6 US gallons). Is this a known bug? Archon 2488 ( talk) 09:49, 15 July 2020 (UTC)
It seems that {{ inflation}} doesn't have a sigfig option, only a -r, and often enough gives numbers with too much precision. I mentioned it in the talk page for {{ inflation}}, but thought I should mention it here, too, especially since people here know how it works. Gah4 ( talk) 18:24, 17 July 2020 (UTC)
This page is an archive of past discussions. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page. |
|
A discussion in July 2020 ( permalink) gave the result:
The rationale was that the amount of discussion is greatly reduced from earlier years and it would be desirable for a year's worth of discussion to be archived on one page rather than twelve. Johnuniq ( talk) 01:18, 21 July 2020 (UTC)
It seems there is no support for points, picas etc. yet. Abbreviations can be a bit iffy, because pt can mean picoton or pint (different dimension) and pc (i.e. pica = 12 point) also stands for parsec (same dimension). Furthermore, pt means something different in Tex (100/7227 in) than in CSS (1/72 in; bp in Tex). Besides the Postscript or DTP point, 1 pt = 1/72 in, I would also add quarter-millimeter q = 0.25 mm, Didot point dd = 0.375 mm or 0.376065 mm or 1/2660 m or 254/675 mm, cicero cc = 12 dd, twip = 1/20 pt. — Christoph Päper 00:23, 29 December 2019 (UTC)
The documentation notes that |xx|
(as in "2 × 3 in (5.1 × 7.6 cm)" vs. "2 in × 3 in (5.1 cm × 7.6 cm)") is deprecated because it does not conform to Wikipedia's Manual of Style (nor international standards). However, there does not seem to be an option to get the acceptable notation with area units: "2 × 3 in² (5.1 × 7.6 cm²)".
I believe this should be added, but I'm not sure how.
Another, less preferable variant would use parentheses: "(2 × 3) in×in ((5.1 × 7.6) cm×cm)". —
Christoph
Päper 13:13, 2 January 2020 (UTC)
When using |disp=table
or |disp=tablecen
with products like 2|x|3
or 2|by|3
, the template should add an automatically calculated sort value in the data-sort-value
attribute of the td
table cell element. —
Christoph
Päper 13:22, 2 January 2020 (UTC)
sortable
parameter:
off
: no explicit sort keyon
: default sort key, same as either product
or first
product
: sort by the result of the multiplication of two or three numeric valuesfirst
, 1st
, 1
, 12
, 123
: sort key is the first numeric value, possibly followed by the other(s)second
, 2nd
, 2
, 21
: sort key is the second numeric value, possibly followed by the other of twothird
, 3rd
, 3
, 321
: sort key is the third numeric value, possibly followed by the others of threemin
: sort key is the smallest of up to three numeric values, perhaps secondary sort by the medium of three valuesmax
: sort key is the largest of up to three numeric values, perhaps secondary sort by the medium of three valuesavg
, mid
: sort key is the arithmetic mean, i.e. the average, of up to three numeric values; usually yielding the same sort order as product
If you have, say, a rectangle 11 ft 8 in by 7 ft 4 in and want to put its dimensions into a single template, is there any way of doing what I would intuitively want to write as {{convert|11|ft|8|in|by|7|ft|4|in|m}}, or is this simply not supported by the template? Archon 2488 ( talk) 12:40, 22 January 2020 (UTC)
{{convert|2|by|3|by|12|ft|m}}
→ 2 by 3 by 12 feet (0.61 by 0.91 by 3.66 m)I haven't been able to find any documentation about support for photometry units (lumen, candela, etc). Is there any plan to add support for these? Archon 2488 ( talk) 12:38, 22 January 2020 (UTC)
I would like to know whether there is a way to calculate to the nearest multiple of 5 in case of decimal numbers. For example {{convert|10|yd|m|2}} gives out 10 yards (9.14 m). Is it possible to get 9.15 m (as used by the International Football Association Board for the penalty kick arc)? In this case |round=5 doesn't work. Thanks in advance.-- Carnby ( talk) 13:24, 30 January 2020 (UTC)
Hi, I have been trying to use disp=table in cells that sit across several rows, and this is what happens:
kilograms | pounds | stone and pounds | |
---|---|---|---|
Why??? | style="text-align:right;"|10 | 22 | 1 st 8 lb |
some | text | here |
Any way to get "rowspan" to also apply to the output? Thanks, Mr.choppers | ✎ 02:47, 30 January 2020 (UTC)
kilograms | pounds | stone and pounds | |
---|---|---|---|
Why??? | |||
10 | 22 | 1 st 8 lb | |
some | text | here |
@ Johnuniq: - No, I was looking for output to be displayed across two rows. I realize that my attempted example was non-functional (I didn't test it first, my bad), so here is what I want the table to look like (left) and what happens when I use the disp=table function (right):
kilograms | pounds | |
---|---|---|
10 | 22 | |
kilograms | pounds | |
---|---|---|
style="text-align:right;"|10 | 22 | |
I can make it work manually, I was just hoping to be able to use the template (the automatic alignment is nice, for instance). Thanks. Mr.choppers | ✎ 04:43, 30 January 2020 (UTC)
stylein
and styleout
. As the example at that link shows, you can set the style for the input and output, but there is no equivalent for rowspan.
Johnuniq (
talk) 06:05, 30 January 2020 (UTC)stylein
and styleout
may prove useful in other ways. Cheers,
Mr.choppers |
✎ 13:11, 30 January 2020 (UTC)
|disp=table
generates10
|22
10 || 22
|disp=table2
that puts out double bars on the same line instead of single bars on separate lines?
Stepho
talk 21:47, 31 January 2020 (UTC)
||
, and whether there was any difference. I decided to stick with what the old system did in case certain usages in tables required the two-line version. I have never noticed a difference and a quick test now does not show any difference.I replaced {{convert|10|kg|lb|disp=table}}
in the table above with what the one-line output would be, namely style="text-align:right;"|10||style="text-align:right;"|22
. Preview shows no difference to the table.
Johnuniq (
talk) 22:42, 31 January 2020 (UTC)
rowspan="2" | 10 | rowspan="2" | 22
rowspan="2" | 10 || rowspan="2" | 22
Is there a template which protects numbers from being converted? Example: the Standard Ten is named after the tax horsepower rating, so one has to write "10 hp" a lot. But then well-meaning editors convert this to kilowatts, even though a tax hp ≠ actual horsepower. Similarly, car wheels are nearly always measured in inches ( exception here), and are never expressed in millimetres. Is there a nifty template I can apply to this sort of data or should I just add hidden messages at all these instances? I feel that bots don't care much about my messages, so I was hoping for something similar to Template:Proper name. I am sure that these are not the only examples of nominal values which should not undergo conversion. Best, Mr.choppers | ✎ 06:57, 1 February 2020 (UTC)
Would it be possible to add a conversion for g-force? It would essentially be the same as {{convert|1|g0}} but would display as g and link to the g-force article. Thanks! — Huntster ( t @ c) 23:14, 2 February 2020 (UTC)
g
is gram, so what unit code should be used? Perhaps g-force
would be clearest? The name for g0 is standard gravity
. What name (abbr=off) should be used? You're saying the symbol (abbr=on) should be g
so perhaps g-force
could be the name? Or gravitational force equivalent
?
Johnuniq (
talk) 02:50, 3 February 2020 (UTC)
g-force
is the logical unit code, and g
(with italics) is the abbreviation, but you never see this as anything but the abbreviation. The long form can be g-force
/g-forces
, but it would be really strange to see it written like that anywhere. Is there a way to make the abbreviation the default, requiring abbr=off to be used to see the long form?g0
unit, the abbreviation should use the code ''g''<sub>0</sub>
. —
Huntster (
t
@
c) 03:34, 3 February 2020 (UTC)
I added two temporary units for testing. g0-temp
shows how g0
will work in the next release. g-force
is the new unit. Re the latter, there is no way to default to abbr=on and only show a unit name if abbr=off is used so the new unit uses g for the symbol and name. Examples:
{{convert|100|g0-temp}}
→ 100 g0-temp
convert: unknown unit{{convert|100|g0-temp|abbr=on|lk=in}}
→ 100
g0-temp
convert: unknown unit{{convert|100|g-force}}
→ 100 g (980 m/s2){{convert|100|g-force|abbr=on|lk=in}}
→ 100
g (980 m/s2)Let me know if this works. Assuming g-force is used it will be changed to a permanent unit in the next release. Johnuniq ( talk) 06:12, 3 February 2020 (UTC)
Appears to have problems. E.g., {{convert|1000000000|e6ha}} 1,000,000,000 million hectares (2.5×109×10 6 acres) Cheers. Lfstevens ( talk) 20:50, 4 February 2020 (UTC)
{{convert|125|e6ha}}
→ 125 million hectares (310×10 6 acres){{convert|125|e6ha|abbr=off}}
→ 125 million hectares (310 million acres){{convert|1000000000|e6ha|e15acre}}
→ 1,000,000,000 million hectares (2.5×10 15 acres){{convert|1000000000|e6ha|acre}}
→ 1,000,000,000 million hectares (2.5×1015 acres){{convert|1000000000|e6ha|e15acre|abbr=off}}
→ 1,000,000,000 million hectares (2.5 quadrillion acres){{convert|1000000000|e6ha|acre|abbr=off}}
→ 1,000,000,000 million hectares (2.5×1015 acres)The module was last updated in May 2019 and I'm planning a new update soon to cover some unit changes discussed since then. The first issue is that several energy units link to
Atmosphere (unit) (if lk=on
is used) but that article is about pressure and seems irrelevant. No units currently link to
Standard cubic foot which concerns a volume (actually, an amount) of gas.
The energy units that link to Atmosphere (unit) follow (full list is here).
unitcode default symbol name1
ccatm mJ cc⋅atm cubic centimetre-atmosphere
cm3atm mJ cm<sup>3</sup>⋅atm cubic centimetre-atmosphere
cufootatm kJ cu ft atm cubic foot of atmosphere
cuftatm kJ cu ft atm cubic foot of atmosphere
cuydatm kJ cu yd atm cubic yard of atmosphere
GLatm GJ GL⋅atm gigalitre-atmosphere
Glatm GJ Gl⋅atm gigalitre-atmosphere
impgalatm J imp gal⋅atm imperial gallon-atmosphere
kLatm kJ kL⋅atm kilolitre-atmosphere
klatm kJ kl⋅atm kilolitre-atmosphere
Latm J L⋅atm litre-atmosphere
latm J l⋅atm litre-atmosphere
m3atm kJ m<sup>3</sup>⋅atm cubic metre-atmosphere
MLatm MJ ML⋅atm megalitre-atmosphere
Mlatm MJ Ml⋅atm megalitre-atmosphere
mLatm mJ L⋅atm millilitre-atmosphere
mlatm mJ l⋅atm millilitre-atmosphere
scc mJ scc standard cubic centimetre
scf kJ scf standard cubic foot
scfoot kJ scf standard cubic foot
scy kJ scy standard cubic yard
sl J sl standard litre
USgalatm J US gal⋅atm US gallon-atmosphere
I think these units relate to how much energy can be obtained by burning a certain amount of a certain fuel. The issue was raised by Ws1920 for scf here.
What should the link be for the above energy units? Presumably Atmosphere (unit) is wrong? Should it be changed to Standard cubic foot? Johnuniq ( talk) 08:37, 4 February 2020 (UTC)
I plan to remove all the above listed units, along with scf2 and scfoot2 that were temporarily added on 9 December 2019 to Module:Convert/extra as tests (those units have not been used in articles). Johnuniq ( talk) 06:57, 19 February 2020 (UTC)
This template's notes say (in the Output with horizontal fraction bar section) that using a double slash (//) returns a horizontal bar fraction:
{{convert|1//2|in|mm|1}}→ 1/2 inch (12.7 mm) {{convert|2+1//2|in|mm|1}} → 2+1/2 inches (63.5 mm)
That's lovely, but it only addresses the input value. What is to be done if the input value is metric (say, 12.7 mm) and what I want is the converted figure to be one-half inch expressed as a fraction with a horizontal divider bar? 173.180.13.37 ( talk) 03:30, 20 February 2020 (UTC)
{{convert|12.7|mm|frac=-2}}
→ 12.7 millimetres (1/2 in)Speed isn't always a manifestation of energy waste
The conversion template page appears to be slanted towards fuel efficiency, ignoring rate of speed in favour of fuel consumption rate in examples of rates (x per y). This slant shouldn't be applied to wind speed. Note that wind is not a consumer of fossil fuels. Indeed, the wind is a manifestation of solar energy, and it will not be convinced to switch to a more politically correct fuel source, if such exists. Not everything fast causes climate change. Please add some speed examples to your conversion templates page (and, better yet, to your Help:Convert page, as well), so that other novice or occasional conversion templaters won't waste time as I did. Thanks-- Quisqualis ( talk) 01:00, 6 February 2020 (UTC)
I wondered if anyone can tell me if (and if so, how) this template can be used to display a speed which, from the source is known to be about 30 m/s, as "70 mph (110 km/h)". Thanks for any help. -- DeFacto ( talk). 18:23, 22 February 2020 (UTC)
{{convert|30|m/s|mph km/h|1|abbr=on}}
→ 30 m/s (67.1 mph; 108.0 km/h){{convert|30|m/s|mph km/h|abbr=on|order=out}}
→ 67 mph (110 km/h){{convert|30|m/s|mph km/h|abbr=on|order=out|round=5}}
→ 65 mph (110 km/h){{convert|30|m/s|mph km/h|abbr=on|order=out|round=10}}
→ 70 mph (110 km/h)A construction like {{convert| 8|km|0}}
produces 8 kilometres (5 mi). What I would expect is either 8 km (5 mi) or 8 kilometres (5 miles), not this odd mixture of unabbreviated and abbreviated, which looks amateurish. Of course I know we can get round it using {{convert| 8|km|0|abbr=on}}
[for 8 km (5 mi)], or {{convert| 8|km|0|abbr=off}}
[for 8 kilometres (5 miles)], but that is really not the point, it requires extra work just to do the right thing. The default when abbr is not used should be one or the other, not somewhere in between. Comments? --
Red King (
talk) 00:01, 22 February 2020 (UTC)
km
if they only saw that – of course, this is far more likely with uncommon units like 8
millisiemens (abbreviation 8 mS
).Hi, all. I would like to request the addition of the area unit feddan (or feddan masri lit. 'Egyptian feddan', for more details about the history of the unit, see this website). This is the last non-SI unit still used in Egypt. As an official source, this recent press release by the Egyptian CAPMAS (a government agency) lists the area of cultivated land in Egypt as 9.2 million feddans. The unit is also used in Sudan, Syria and Oman. ( source1 and source2). The addition of this unit was approved in August 2015 but it appears that it was removed later. It should be added with the other non-SI area units to this table. Conversion:
The unit can be used on many articles such as: Economy of Egypt, Agriculture in Egypt, etc. Note also that Egypt was an important country when studying the history of agriculture. Thank you. -- Meno25 ( talk) 15:59, 4 March 2020 (UTC)
In Syria, the feddan ranges from 2295 square metres (m²) to 3443 square metres (m²).What value could be legitimately assigned for the conversion? Tarl N. ( discuss) 23:50, 4 March 2020 (UTC)
{{convert|1.28|m}}
1.28 metres (4 ft 2 in){{convert|4.22|m}}
4.22 metres (13.8 ft)On my disply (1) returns 1.28 metres (4 ft 2 in)
(2) returns 4.22 metres (13.8 ft)
Why are they not consistent? --
PBS (
talk) 18:10, 21 January 2020 (UTC)
OK I found the answer in Template talk:Convert/Archive February 2015#Convert metric to feet and inches?
Indeed it is in the section Module:Convert/documentation/conversion_data#Length 24 lines down ten columns in.
Why the built in inconsistency? It is a real got-yer and not the behaviour of least surprise. -- PBS ( talk) 18:20, 21 January 2020 (UTC)
I came across it in a new article I have created called Widebeam. There there are draft measurements of under 4 feet and lengths of about 70 feet. I will go through and fix then to be one or the other. However I agree with User:Hawkeye7 comment "I don't see any call for the use of decimals" with feet (ie the default ought to be ftin for all of them). However I think that either decimal feet or feet and inches for all is preferable to the current inconsistency. -- PBS ( talk) 11:46, 22 January 2020 (UTC)
{{convert|2.16|to|3.24|m}}
and those over {{convert|3.24|m}}
{{convert|3.24|to|2.16|m}}
and those under {{convert|3.24|m}}
{{convert|2.16|to|3.24|m|ftin}}
→ 2.16 to 3.24 metres (7 ft 1 in to 10 ft 8 in){{convert|3.24|m|ftin}}
→ 3.24 metres (10 ft 8 in){{convert|2.16|to|3.24|m|ftin|order=flip}}
→ 7 feet 1 inch to 10 feet 8 inches (2.16 to 3.24 m){{convert|80|kg}}
then it should display in stones and pounds because the weight is under 30 stones, or if something is 4 inches or higher and less than 81 inches it ought to be in hands and inches (because I measure horses that way). Why on earth do you "prefer to see metres converted to feet and inches for things that are the same size as me, and decimal feet for things that are much bigger"? Is it a cultural thing? --
PBS (
talk) 16:46, 22 January 2020 (UTC)
ftin
to ft
at a predetermined value. Most uses of the template for lengths under about 3 metres will be heights of people, and for as long as I've been alive, imperial units have measured those in feet and inches. Once you start measuring larger objects such as the length of a ship, for example, it is fairly likely that you'll see a decimal representation if anything less than one foot is significant. I don't believe that is anything cultural. That's my preference and it depends on my perception of how I've seen measurements quoted, especially when I was younger. Why do prefer to see people's height measured in the same units as the length of a ship?.I think this behavior is undesirable in a collaborative encyclopedia. Someone comes along to fix an article that they're not deeply involved with; perhaps they saw a change in some value in a reliable source, and are cleaning up places that link to that source. The editor isn't aware of the ins and outs of converting meters to feet, so isn't aware the format will change when updating a value from 2.9 m to 3.1 m. Jc3s5h ( talk) 20:36, 22 January 2020 (UTC)
I don't mind which we use but the convert should avoid inconsistencie
{{convert|2.16|to|3.24|m}}
and {{convert|3.24|m}}
I would prefer the default to be feet and inches, but would prefer feet and decimal feet to the current mix. The convert template should fail safe when using default values, so that the output displayed in an article is consistent. -- PBS ( talk) 16:46, 27 January 2020 (UTC)
{{convert|2.16|to|3.24|m|ftin}}
and {{convert|3.24|m|ftin}}
ftin
with ft
for decimal feet. If you don't like the defaults, you specify the units. What situation can't be catered for by that? --
RexxS (
talk) 23:33, 27 January 2020 (UTC)
If you don't like the defaults, you specify the units.– Sure, after you’ve spent an hour trying to understand why some rows in a table are coming out in ft+in while others, coded the same way, come out in decimal feet, all the time wondering if you’re losing your mind. Not worth it, not nearly. Is there anything else in {convert} that works this way? Does kg come out in decimal lbs for large masses, but lbs+oz for anything under 15 lb, because that might be the weight of a newborn? E Eng 06:41, 28 January 2020 (UTC)
{{
convert}}
was used to add imperial measurements early on in the article, so not being really aware of how it works, (s)he will copy the original altering the number as appropriate. If the second {{
convert}}
is a scrollable distance down the article from the first, the chances are that a change to (or from) inches to decimal feet will not be noticed. This is why this template ought to fail safe, to protect the visual appearance of articles from editors who are not as familiar with the current quirks of this template as
User:RexxS is. As EEng asked, I too would like to know "Is there anything else in {convert} that works this way?" --
PBS (
talk) 12:56, 30 January 2020 (UTC)
I believe the majority view (I won't say consensus) is that the output should be consistently either ft+in or decimal feet (but not the second-guessing behavor) though there's disagreement as to which of those two is the better default, and it's unclear how much trouble it would be to change the behavior. Are we all together so far? E Eng 03:56, 3 February 2020 (UTC)
I have left it a few days to see if anyone else wished to add anything—it seems not.
@ Jc3s5h your post was facinating for me. In Britain all length measures commonly sold in hardware haberdashery and stationary shops are sold with metric and imperial either on one side (eg steel measuring tapes and rulers) or metric on one side and imperial on the other (eg measuring tapes sold in habadasheries). They are always in [yards occasionally], feet and inches, I have never seen a decimal foot measure. The only place I have seen 10ths used with imperial measurements in Britain is in a road vehicle's odometer/ Speedometer and Google maps which vacillates between yards and 10th of a mile. However because wood is cut in metric units, many timber merchants are unhappy selling short lengths of timber in imperial lengths (because they end up with unsellable offcuts) so some are willing to sell a colloquial "metric foot" which is 30cm or a "metric yard" (90cm) for those who can/will not think in metric measurements. The same is done with with width and bredth if the item is up to about 4x6", the merchants refer to the metric width and depth as "planed" so 2x1" planed is a actually manufactured as 50x25mm—ie about 1/64" per inch smaller than the old imperial size. With timber this works reasonably well, but is more problomatic with materials such as steel. However a similar rule of thumb is used for the length of wood screws, bolts etc.
It seems to me that in this thread there is a consensus to use one consistent conversion for all lengths. Everyone who has expressed an opinion on the conversion of peoples heights favours using feet and inches, therefore that has to be the default. @ Johnuniq can you and will you make the change? Further I suggest that if after the change is made if there are howles of anguish over the loss of decimal feet, then the change can be reverted and a bot can be run to make all the lenths that currently use decimal feet explicit, before remaking the change. -- PBS ( talk) 18:33, 14 February 2020 (UTC)
After enhancing some scripts I use, I have examined the converts that would be affected by a change in default output. I used the April 2019 database dump because that is the most recent I have.
For example, Auschwitz concentration camp#Auschwitz III-Monowitz uses the following, which would change to the second line:
Many "list" articles have tables that assume ft is the output unit. Examples:
I would be very reluctant to silently change how 128,777 converts behave without a widely advertised central discussion. By "silently", I mean that there would be no indication in an article's history that something had happened, and only a very observant page-watcher would notice that something needed to be fixed. Johnuniq ( talk) 03:52, 19 February 2020 (UTC)
Taking the first measurement in the first list example List of longest runways
removing the table parameter produces:
The 0 parameter controlling the rounding, which in this case AFAICT is the same as the default ( Template:Convert#Default rounding):
I don't think anyone would want that changed that default to either decimal feet or feet and inches.
but if the default displays decimal feet then convert it:
I understood the consensus above was to change thoses entries that by default display "decimal feet" to "feet and inches" (without messing around with the default rounding — which is a seperate issue). Infact the default rounding affect makes this proposition less invasive as most longer lenths will not be alted unless greater presision has been explicitly requested. -- PBS ( talk) 10:04, 5 March 2020 (UTC)
{{convert|5500|m}}
→ 5,500 metres (18,000 ft){{convert|5500|m|0}}
→ 5,500 metres (18,045 ft){{convert|5500|m|ftin}}
→ 5,500 metres (18,044 ft 7 in){{convert|5500|m|ftin|0}}
→ 5,500 metres (18,044 ft 7 in){{convert|5500|m|ft|1}}
→ 5,500 metres (18,044.6 ft){{convert|5500|m|ftin|1}}
→ 5,500 metres (18,044 ft 7.4 in)I had a look for converts which might give rounding problems if the output is changed to ftin. There are quite a lot of them although I didn't do a count. Examples:
Article | Convert | Current output (ft) | Output with ftin |
---|---|---|---|
MV Loch Sunart | {{convert|13.87|m|1|abbr=on}} | 13.87 m (45.5 ft) | 13.87 m (45 ft 6.1 in) |
Berlin Wall | {{convert|3.6|m|1|abbr=on}} | 3.6 m (11.8 ft) | 3.6 m (11 ft 9.7 in) |
Black Sea | {{convert|2212|m|2|abbr=off}} | 2,212 metres (7,257.22 feet) | 2,212 metres (7,257 feet 2.61 inches) |
Brasília | {{convert|70|m|2|abbr=on}} | 70 m (229.66 ft) | 70 m (229 ft 7.91 in) |
Frankfurt | {{convert|660|m|2|abbr=on}} | 660 m (2,165.35 ft) | 660 m (2,165 ft 4.25 in) |
Papua (province) | {{convert|4000|m|-3}} | 4,000 metres (13,000 ft) | 4,000 metres (13,123 ft 4 in) |
Mauritius | {{Convert|300|-|800|m|abbr=on|round=50}} | 300–800 m (1,000–2,600 ft) | 300–800 m (984 ft 3 in–2,624 ft 8 in) |
Several of the above (and a lot more not shown) are probably mistakes but they need to be handled somehow. Johnuniq ( talk) 06:49, 6 March 2020 (UTC)
|sigfig=
rather than |round=
or |(unnamed)=
. I've also changed the output to be actual conversions, not cut-and-paste as well as adding an extra column with the number of significant figures reduced by one:Article | Convert | Current output (ft) | Output with ftin | sigfig-1 |
---|---|---|---|---|
MV Loch Sunart | {{convert|13.87|m|abbr=on|sigfig=4}} | 13.87 m (45.51 ft) | 13.87 m (45 ft 6.1 in) | 13.87 m (45 ft 6 in) |
Berlin Wall | {{convert|3.6|m|abbr=on|sigfig=2}} | 3.6 m (12 ft) | 3.6 m (11 ft 10 in) | 3.6 m (11 ft 10 in) |
Black Sea | {{convert|2212|m|abbr=off|sigfig=4}} | 2,212 metres (7,257 feet) | 2,212 metres (7,257 feet 3 inches) | 2,212 metres (7,257 feet 3 inches) |
Brasília | {{convert|70|m|abbr=on|sigfig=2}} | 70 m (230 ft) | 70 m (229 ft 8 in) | 70 m (229 ft 8 in) |
Frankfurt | {{convert|660|m|abbr=on|sigfig=2}} | 660 m (2,200 ft) | 660 m (2,165 ft 4 in) | 660 m (2,165 ft 4 in) |
Papua (province) | {{convert|4000|m|sigfig=2}} | 4,000 metres (13,000 ft) | 4,000 metres (13,123 ft 4 in) | 4,000 metres (13,123 ft 4 in) |
Mauritius | {{Convert|300|-|800|m|abbr=on|sigfig=2}} | 300–800 m (980–2,600 ft) | 300–800 m (984 ft 3 in – 2,624 ft 8 in) | 300–800 m (984 ft 3 in – 2,624 ft 8 in) |
Is there a way to convert 1/64th of an ounce into metric units?-- Carnby ( talk) 17:43, 5 March 2020 (UTC)
{{convert|1/64|oz}}
→ 1⁄64 ounce (0.44 g) --
RexxS (
talk) 19:28, 5 March 2020 (UTC)Is there a way to put some text after the first part and before the second part of the unit to convert?-- Carnby ( talk) 20:46, 7 March 2020 (UTC)
Does this unit really exist?-- Carnby ( talk) 20:50, 7 March 2020 (UTC)
{{convert|1|ftlb/lbf|J/kgf|lk=on}}
→ 1
foot-pound per
pound-force (3.0
J/
kgf)Looking for a conversion of ton miles into kilometre-tonnes (kmt) tonne-kilometres.
Hawkeye7
(discuss) 05:45, 9 March 2020 (UTC)
I didn't find in Module:Convert/documentation/conversion data and any unit of information. I was looking for it for importing block size data from wikidata in hewiki, and before adding it to the Hebrew version of Module:Convert/documentation/conversion data I would like to raise it here. Eran ( talk) 16:15, 6 March 2020 (UTC)
Is there any chance of a time-zone conversion for date and time? In particular, converting from an arbitrary time-zone to UTC would be handy for things like {{unsigned}} which require a time in UTC. It wouldn't be quite the same as the units conversions here, so perhaps this is not the right place to ask; but then where is? Zero talk 04:47, 16 March 2020 (UTC)
The units 'short ton
', 'long ton
', and 'metric ton
' (not the unit 'tonne
') are unrecognised as parameter entries in plural form: {{convert|2|short tons|}}
returns as 2 short tons
convert: unknown unit
; {{convert|2|long tons|}}
returns as 2 long tons
convert: unknown unit
; and {{convert|2|metric tons|}}
returns as 2 metric tons
convert: unknown unit
.
Can anyone fix this please, next time there's an update? WT79 The Engineer ( talk) 18:12, 20 March 2020 (UTC)
I was looking for a conversion from "1 ft 11 5/8", a regular ft,in in writing. However, I could not find how to enter this, into a useful result. We shoud improve the /doc for this! - DePiep ( talk) 23:09, 2 April 2020 (UTC)
{{convert|1|ft|11+5/8|in}}
→ 1 foot 11+5⁄8 inches (0.600 m) --
RexxS (
talk) 23:37, 2 April 2020 (UTC)
Is there a way to output ftin with a non-breaking space between the feet value and the inches value?
As in, 2 metres (6 ft 7 in) where the space between "ft" and "7" is non-breaking? — Joeyconnick ( talk) 21:48, 12 April 2020 (UTC)
to get 2 metres (6 ft 7 in)
, or perhaps better:2 metres ({{
nowrap|6 ft 7 in}}
)
? Surely you wouldn't need to do it very often? --
RexxS (
talk) 00:37, 13 April 2020 (UTC){{
convert|7|ft|m|2}}
to give me the correct conversion of "7 feet (2.13 m)".{{
nowrap}}
suggestion is good.
Stepho
talk 11:34, 13 April 2020 (UTC){{convert|2|m|m|disp=out}}
→ 2.0 m{{nowrap|1=({{convert|2|m|ftin|disp=out}})}}
→ (6 ft 7 in)|disp=in
?), current workaround even changes the value (.0 added in the example). I have no opinion on the usefullnes of these changes (vs. time spend). -
DePiep (
talk) 15:02, 18 April 2020 (UTC)
{{
convert|2|m|ftin|abbr=on}}
"2 m (6 ft 7 in)" and it would be fine to break as:|disp=br
adds a line-break and omits brackets.
|disp=br()
adds a line-break and does add brackets to the converted value. This may be useful in tables:
|disp=br |
|disp=br()
| |||
---|---|---|---|---|
10 kilometres 6.2 miles |
10 kilometres (6.2 miles) |
1 km (0.62 mi) |
1 km 0.62 mi |
1 km (0.62 mi) |
Category:Convert errors now lists eight power station articles, eg Ace Embilipitiya Power Station. They use {{ Infobox power station}}, which pulls all data from WikiData.
The error occurs in row data59, "Site area" (WD area (P2046)). The example article has WD value "44 acre", OK. Somehow the unit is read as "ac" by Convert, throwing the error. All articles have this property in "acre". I was unable to do more research. ;-) - DePiep ( talk) 14:59, 18 April 2020 (UTC)
table#1 { table#2 { ["id"] = "Q25056880$2034aad9-4077-8f80-64e2-494f403e607f", ["mainsnak"] = table#3 { ["datatype"] = "quantity", ["datavalue"] = table#4 { ["type"] = "quantity", ["value"] = table#5 { ["amount"] = "+44", ["unit"] = " http://www.wikidata.org/entity/Q81292", }, }, ["property"] = "P2046", ["snaktype"] = "value", }, ["qualifiers"] = table#6 { ["P518"] = table#7 { table#8 { ["datatype"] = "wikibase-item", ["datavalue"] = table#9 { ["type"] = "wikibase-entityid", ["value"] = table#10 { ["entity-type"] = "item", ["id"] = "Q159719", ["numeric-id"] = 159719, }, }, ["hash"] = "92e50222d46cdef57f722b435fbab6b3e919014b", ["property"] = "P518", ["snaktype"] = "value", }, }, }, ["qualifiers-order"] = table#11 { "P518", }, ["rank"] = "normal", ["type"] = "statement", }, }
Quantity | Unit | Symbol | Derivation | Year | SI equivalent |
---|---|---|---|---|---|
Activity (A) | becquerel | Bq | s−1 | 1974 | SI unit |
curie | Ci | 3.7 × 1010 s−1 | 1953 | 3.7×1010 Bq | |
rutherford | Rd | 106 s−1 | 1946 | 1,000,000 Bq | |
Exposure (X) | coulomb per kilogram | C/kg | C⋅kg−1 of air | 1974 | SI unit |
röntgen | R | esu / 0.001293 g of air | 1928 | 2.58 × 10−4 C/kg | |
Absorbed dose (D) | gray | Gy | J⋅kg−1 | 1974 | SI unit |
erg per gram | erg/g | erg⋅g−1 | 1950 | 1.0 × 10−4 Gy | |
rad | rad | 100 erg⋅g−1 | 1953 | 0.010 Gy | |
Equivalent dose (H) | sievert | Sv | J⋅kg−1 × WR | 1977 | SI unit |
röntgen equivalent man | rem | 100 erg⋅g−1 × WR | 1971 | 0.010 Sv | |
Effective dose (E) | sievert | Sv | J⋅kg−1 × WR × WT | 1977 | SI unit |
röntgen equivalent man | rem | 100 erg⋅g−1 × WR × WT | 1971 | 0.010 Sv |
/info/en/?search=Template:Radiation_related_quantities — Preceding unsigned comment added by 2001:a62:1570:301:4449:56ee:9d2b:e309 ( talk) 12:23, 21 April 2020 (UTC)
This source gives the maximum elevation of the Ansel Adams Wilderness as 13,157 ft, and the minimum elevation as 3,500 feet. Let's say I want to convert that range to meters:
{{convert|3,500|–|13,157|feet|m|0|abbr=on|sortable=on}} outputs this: 3,500–13,157 ft (1,067–4,010 m)
I can't figure out how to specify different sigfig values for the two elevations. I'd like -2 sigfigs for the first number, and 0 sigfigs for the second number. CJK09 ( talk) 00:25, 30 April 2020 (UTC)
|0
is used, each output number is rounded to the nearest integer. In this example, that gives "(1,067–4,010 m)". If no rounding is specified, convert uses the highest precision of each item in the range on each item. Use |round=each
to have convert calculate the precision for each item separately. Fortunately that achieves what you want but it sometimes gives bad results.
{{convert|3,500|-|13,157|feet|m|abbr=on|round=each}}
→ 3,500–13,157 ft (1,100–4,010 m)Is there a way to render "an inch"/"a feetfoot"/"a mile" instead of "one inch"/"one feetfoot"/"one mile" when using |spell=on parameter? It would be useful when in a text caption there's "an inch"/"a feetfoot"/"a mile."--
Carnby (
talk) 14:15, 18 April 2020 (UTC)
|txt=
, and replaces One/one with A/An/a/an as appropriate. Here are some examples:
{{one2a |one foot. One mile. One inch.One amp. one foot. one mile. one inch. Alone at last.}}
→ a foot. A mile. An inch.An amp. a foot. a mile. an inch. Alone at last.{{convert|1|ft|spell=on}}
→ one foot (zero point three zero metres){{one2a|{{convert|1|ft|spell=on}}}}
→ a foot (zero point three zero metres){{convert|2.54|cm|0|disp=out|spell=on}}
→ one inch{{one2a|{{convert|2.54|cm|0|disp=out|spell=on}}}}
→ an inchI appreciate that a template can't enforce MOS requirements in every instance, but if there is a style that is clearly proscribed in every context then (providing there is no good reason not to) it seems reasonable to me to disallow output such as 7+1⁄4 miles (11+5⁄8 km). Either raising an exception or ignoring the frac option would seem sensible. What say? Archon 2488 ( talk) 11:58, 1 May 2020 (UTC)
{{convert|7600|ft|mi km|frac=8}}
→ 7,600 feet (1+1⁄2 mi; 2.3 km). --
RexxS (
talk) 22:27, 1 May 2020 (UTC){{cvt|9876.5|coulomb|A.h|frac=8}}
→ 9,876.5 C (2+3⁄4 A⋅h){{cvt|2+7/8|km}}
→ 2+7⁄8 km (1.8 mi){{cvt|2+7/8|km|frac=8}}
→ 2+7⁄8 km (1+3⁄4 mi)Can I use positional parameters from another template (for example, {{{1}}}). Imagine a template calle kcal and it is used in the same way in a page : {{kcal|1}} . The {{kcal}} code is: {{convert|{{{1}}}|kcal|kJ}} . Why does not it work?. It ask for a number (perhaps instead of a positional parameter as {{{1}}}}. But this type of functionality is also needed. -- BoldLuis ( talk) 18:40, 8 May 2020 (UTC)
<includeonly>
but with convert you could use:
{{convert|{{{1|NNNN}}}|kcal|kJ}}
Is there a modifier to get {{convert|1|m|ft|0|spell=in|abbr=off}}
to output "a" rather than "one", as in "about a metre (3 feet)" rather than "about one metre (3 feet)"? --
DeFacto (
talk). 15:59, 8 May 2020 (UTC)
about {{one2a|{{convert|1|m|ft|0|spell=in|abbr=off}}}}
→ about a metre (3 feet)How do I set the comma thing to both "gaps" and "5"?
{{convert|5000|ft||abbr=|order=flip|comma=5|comma=gaps}} didn't work. 146.255.181.208 ( talk) 21:04, 25 April 2020 (UTC)
comma=gaps5
used to do what you want (use gaps, but only if 5 or more digits before decimal point). However, it was disabled in
June 2015 and later removed. That followed a couple of discussions, at least one of which can be found by searching that archive for "gaps5". I believe that no converts used that option at the time—if there were any, it was a very small number.
Johnuniq (
talk) 01:19, 26 April 2020 (UTC)
My dear MOS warriors. In my travels I have realised that a despicable heresy, namely the abuse of imperial unit abbreviations as if they were SI symbols, is permitted by the template: 150 cm2 (23 in2). Compare, however, 150 cm2 (23 sq in), and 150 km2 (58 sq mi) – in the last case, the user's request for "mi2" is rejected in favour of the MOS-sanctioned abbreviation "sq mi". Is there a reason why "in2" is permitted? I appreciate that my pedantry is extreme, but it is in the name of a righteous cause. Archon 2488 ( talk) 22:22, 17 May 2020 (UTC)
in2
→ in2sqin
→ sq inmi2
→ sq misqmi
→ sq milbf/in2
(
example) although, for example,
Pump action#Rifles has two in2. If mi2 is needed (example?), it's easy to add.
Johnuniq (
talk) 23:54, 17 May 2020 (UTC)
Hi, noting that this:
{{convert|10e33|erg|J}}
produces this:
but this:
{{convert|10e33.5|erg|J}}
As of 21 May 2020 [update], it gets this error:
When I preview, this is an approximation in HTML of what I am seeing:
Please let me know if this gets fixed. There is a use for a corrected version at Proxima Centauri b.
Peaceray ( talk) 18:11, 21 May 2020 (UTC)
e
(exponent) notation is not identical to ^
(power) notation: 10^33.5 means "ten to the power 33.5", which is 1 × 1033.5 (optionally written as 1e33.5) – which is the same as 3.2 × 1033 (optionally written as 3.2e33). Hope that helps avoid any confusion. Cheers --
RexxS (
talk) 23:37, 21 May 2020 (UTC){{convert|{{#expr:10^33.5}}|erg|J|adj=ri1|sigfig=2}}
→ 3.2×10+33 ergs (3.2×1026 J)The documentation says:
"Value ranges can be entered using |to|...
or |-|...
:
{{convert|2|to|5|km|mi}}
→ 2 to 5 kilometres (1.2 to 3.1 mi){{convert|2|-|5|km|mi}}
→ 2–5 kilometres (1.2–3.1 mi)"which is useful in situations such as "from 1 to 3 meters (3 to 10 ft)" or "between 1 and 3 meters (3 and 10 ft)", which are rather common.
The problem is, I can't find the way to do that in VisualEditor. The feature seems to rely on position and doesn't seem to have a named parameter (or rather, I couldn't find it). If there is a named parameter for the "-", "to", "and" and perhaps other indicators, what is it called? And if not, could we have such a named parameter, please? -- Jhertel ( talk) 10:32, 5 June 2020 (UTC)
-
for a range, another 10,000 using x
, and 34,000 using to
. There are 600 like {{convert|28|x|34|x|15|cm|in|abbr=on}}
(in
Enigma machine). No one has devised a better syntax.
Johnuniq (
talk) 23:39, 5 June 2020 (UTC)
This example:
{{convert|1|to|3|m|ftin|abbr=on|sigfig=1}}
should render as "1 to 3 m (3 to 10 feet)", but renders as "1 to 3 m (3 ft 3 in to 9 ft 10 in)", which of course is more than 1 significant digit.
The documentation doesn't mention this bug.
-- Jhertel ( talk) 10:43, 5 June 2020 (UTC)
{{convert|1|to|3|m|ft|abbr=on|sigfig=1}}
→ 1 to 3 m (3 to 10 ft)|sigfig=
parameter applies to the smallest unit, because it wouldn't make sense to apply it to the larger units. Specifying a single unit allows the |sigfig=
parameter to apply to that unit, allowing any display desired. --
RexxS (
talk) 19:36, 5 June 2020 (UTC)Convert now links to a disambig — Preceding unsigned comment added by 85.242.253.165 ( talk) 17:37, 21 June 2020 (UTC)
Done
[6] (not by me, DePiep) -
DePiep (
talk) 02:46, 22 June 2020 (UTC)
I was recently reading Naval Air Station Joint Reserve Base Fort Worth, and I noticed that the “s” in “nautical miles” was not linked like the rest of the unit. The article appears to be using this template, so I believe this is a bug. Olea Capita ( talk) 07:04, 16 June 2020 (UTC)
This problem seems to occur only on the Wikipedia iOS app. Olea Capita ( talk) 07:30, 16 June 2020 (UTC)
{{convert|5|NM|0|lk=in}}
→ 5
nautical miles (9 km; 6 mi)5 [[nautical mile]]s (9 km; 6 mi)
= 5
nautical miles (9 km; 6 mi)Hi - the template puts a space before the units, which is usually correct, but in the case of degrees symbols there should not be a space (as outlined in the table at MOS:UNITSYMBOLS). Example: 120 °C (248 °F). Is there any way this can be rectified? Cheers GirthSummit (blether) 14:27, 27 June 2020 (UTC)
I was using Shaku (unit) and it works in the conversion template, although it is nowhere listed in the units available. Should be added, I think. Thanks, Mr.choppers | ✎ 03:09, 3 July 2020 (UTC)
An oddity:
Have I failed to understand something? Same for
E Eng 17:35, 2 June 2020 (UTC) E Eng 17:35, 2 June 2020 (UTC)
There is a tiny note above regarding angle units, but solid angle is needed too, and deserves its own discussion. There are many links to (non-SI) square degree which should have conversions to SI steradian. Gah4 ( talk) 00:52, 10 July 2020 (UTC)
I have noticed this in my travels:
{{convert|10|/L|/USgal|abbr=off}}
→ 10 per litre (38 per gallon) [i.e. the output does not disambiguate which gallon is meant]but
{{convert|10|/L|/impgal|abbr=off}}
→ 10 per litre (45 per imperial gallon).This issue seems to arise only with the reciprocal units – 10 litres (2.6 US gallons). Is this a known bug? Archon 2488 ( talk) 09:49, 15 July 2020 (UTC)
It seems that {{ inflation}} doesn't have a sigfig option, only a -r, and often enough gives numbers with too much precision. I mentioned it in the talk page for {{ inflation}}, but thought I should mention it here, too, especially since people here know how it works. Gah4 ( talk) 18:24, 17 July 2020 (UTC)