![]() | 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. |
Here are some fixes. Frankly, I hope that you don't spend hours on this, because the "two-way" conversion of hands to only inches or cm/m is strongly discouraged per WP:MEASUREMENT and the active members of WikiProject Equine strongly support a "three-way" conversion of hands to both inches and centimeters, per the {{ hands}} template. The only thing that is needed here, really, is JLAN's request for a reverse conversion from cm first (or, I suppose, inches, though we've yet to do that one) into hands. His specific concern is that some European horse registries, and the FEI, use metric measurements, while most English speaking nations use hands. This, where the centimeter/meter measurement is "official," he makes an argument that the measurement should first be given in metric measurements, with convert used to give us hands and inches. While I do not agree 100% with his position, it is actually reasonable for him to ask for that flexibility, and so long as the conversion is used, I am willing to support it happening. However, what you have needs some fixes, listed below Montanabw (talk) 21:43, 10 October 2013 (UTC)
Rounding 15.38 hands to 16 hands: @ Montanabw, I will need to fix the rounding so that above 0.3+1/2 rounds to 1 extra hand. Currently, rounding to 1 decimal works, but 2 should show fractions of hands:
However, I am working to use new Template:Rndhands, which allows rounding to the nearest half-inch, such as {rndhands|12.143} as 12.11⁄2, or {rndhands|3.26} as 3.21⁄2. The rounding is extremely tedious to retrofit into {convert} with format restrictions in Lua, and so that is why it has taken years to address, but I think we are getting close to a solution. - Wikid77 ( talk) 00:58/03:13/ 03:53, 11 October 2013 (UTC)
Currently, using the adj=on function in combination with ranges does not produce the desired result:
{{convert|1|to|2|ft|adj=on}}
should produce (ideally)
or even (as an alternative)
but instead actually leaves you with 1-to-2-foot (0.30 to 0.61 m), screwing up the hyphenation involved. I know this thing is kind of a beast, but kindly fix it when you have a minute. — LlywelynII 14:07, 29 September 2013 (UTC)
Hawkeye7 ( talk) 20:25, 1 October 2013 (UTC)
If you have a 29-hectare (72-acre) lake, the "acres" should be "acre". — Sladen ( talk) 19:31, 29 September 2013 (UTC)
Would it be possible to provide a means of converting Tesla - Gauss? I was surprised to that there doesn't currently appear to be a way of doing so. Many thanks. Jamesx 12345 17:47, 30 September 2013 (UTC)
Unit code | Symbol | US symbol | Scale | Extra | Name | Plural name | US name | US plural name | Prefix | Default | Link |
---|---|---|---|---|---|---|---|---|---|---|---|
T | T | 1 | tesla | SI | G | Tesla (unit) | |||||
G | G | 0.0001 | gauss | gauss | T | Gauss (unit) |
{{convert/sandboxlua|2|T}}
→ 2 teslas (20,000 G){{convert/sandboxlua|2|G}}
→ 2 gauss (0.00020 T){{convert/sandboxlua|1|kT|G}}
→ 1 kilotesla (10,000,000 G){{convert/sandboxlua|1|MT|G}}
→ 1 metric ton (
convert: unit mismatch){{convert/sandboxlua|1|MT}}
→ 1 metric ton (0.98 long tons; 1.1 short tons){{convert|1|kT|G}}
→ 1 kilotesla (10,000,000 G){{convert|1|MT|G}}
→ 1 metric ton (
convert: unit mismatch){{convert|1|MT}}
→ 1 metric ton (0.98 long tons; 1.1 short tons)Comment Note that a tesla is a really big unit to begin with.
Our article mentions the magnets in the
LHC at
CERN are 8 T. Lack of support for kT or MT is unlikely to be noticed
. —[
AlanM1(
talk)]—
01:36, 3 October 2013 (UTC)
How do I convert compound units, such as "ton-miles per day"? The obvious ST*mi/day does not work. StephenTX ( talk) 22:54, 5 October 2013 (UTC)
For Tropical Storm Marco (2008)#Preparations, impact and records 1 inch per hour (25 mm/h). Peter Horn User talk 16:19, 6 October 2013 (UTC)
Currently
module:convert/extra
code does not correspond with
module:convert/extra/doc. So I cannot make testcases/demos. We really need discipline in this. "/extra" is a great way to improve convert, but it should not be treated as a private sandbox. -
DePiep (
talk)
19:39, 6 October 2013 (UTC)
I've encountered some problems managing hands and centimetres with disp=flip.
For example:
{{convert|16.3|hand|cm}}
16.3
hands (170 cm)
{{convert|16.3|hand|cm|disp=flip}}
170 centimetres (16.3 h)
In other words, the template does not work when the input unit is hands, the output unit is centimetres and there's disp=flip (useful when dealing with non UK-related horse articles).
Best regards and thanks in advance.--
Carnby (
talk)
08:49, 7 October 2013 (UTC)
There seem to be other problems with hand conversions too. Some people think it necessary to convert metric units to both hands and inches for horse height (I'm not one of those people, btw). If I've understood correctly, we are supposed to use {{ convert/show2 }} for this kind of thing, rather than request yet another three-way convert. However, at the moment neither appears to work:
{{convert/show2 |165|cm|hand|in}}
—> 165 centimetres (16.1 4.0 hands (41 cm); 65 in){{convert/show2 |1.65|m|hand|in}}
—> 1.65 metres (16.10 4.0 hands (41 cm); 65 in){{convert|165|cm|h in|2|lk=out}}
—> an error messageAny advice? Justlettersandnumbers ( talk) 18:22, 8 October 2013 (UTC)
Because the symbol "h" (for "hands") is rarely used in general writing (often as "h" for "hours"), then
Template:Convert/hand has been reset to default the unit as the wikilinked unit name "hands"
Similar settings will be needed in the Lua version, which now shows:
For most cases, Template:Hands can be used instead. - Wikid77 05:26, 9 October 2013 (UTC)
lk=off
does not seem to work)? An article with several hand conversions should not link each of the occurrences, and if anyone ever wanted to add some convert templates to
Hand (unit), they would not want them linked.{{convert/sandboxlua|14.1|hand|in cm|lk=in}}
→ 14.1
hands (57 inches; 145 cm){{convert/sandboxlua|88|in|hand|abbr=off|lk=out}}
→ 88 inches (22.0
hands){{convert/sandboxlua|13.3|-|14.2|hand|in|lk=in}}
→ 13.3–14.2
hands (55–58 inches){{convert/sandboxlua|77|in|hand+cm|lk=out}}
→ 77 inches (19.1
hands; 200
cm)hand+cm
for a user-specified combination, but has the defect that
cm is linked.
Johnuniq (
talk)
08:50, 9 October 2013 (UTC)
It looks like the WPEQ people are happy with {{ hands}}, but as Montanabw says, the templates should not contradict each other, so I fixed the module to interpret fractions of a hand as fractions of an inch. It could be argued that the default rounding from the module is not optimum, but I'm going to pass on tweaking that at the moment.
{{hands|14.1+3/4}}
→ 14.1 3⁄4
hands (57.75 inches, 147 cm){{convert/sandboxlua|14.1+3/4|hand}}
→ 14.1+3⁄4
hands (57.75 inches; 147 cm){{convert/sandboxlua|14.1+3/4|hand|in+cm}}
→ 14.1+3⁄4
hands (57.75 inches; 147 cm){{convert/sandboxlua|14.1+3/4|hand|in+cm|lk=in}}
→ 14.1+3⁄4
hands (57.75 inches; 147 cm)The above numbers are from the lead of Theodore O'Connor. Johnuniq ( talk) 00:32, 11 October 2013 (UTC)
{{convert/sandboxlua|57.75|in|hand}}
→ 57.75 inches (14.2
hands)147cm
to produce like 14.1 3⁄4
hands (57.75 inches, 147 cm) or so. Any actual example for the need? Well, since it does not work today (by any documentation promise), it won't happen tomorrow with new module. -
DePiep (
talk)
22:26, 12 October 2013 (UTC)I've done what's easy, namely added a unit called "handlk" which is the same as hand but which always links to the article.
{{convert/sandboxlua|14.1+3/4|handlk|in+cm}}
→ 14.1+3⁄4 handlk
convert: unknown unit{{convert/sandboxlua|147|cm|hand+in}}
→ 147 centimetres (14.2
hands; 58 in){{convert/sandboxlua|147|cm|handlk+in}}
→ 147 centimetres (
convert: unknown unit){{convert/sandboxlua|147|cm|handlk+in|lk=on}}
→ 147
centimetres (
convert: unknown unit)Later, and as DePiep mentions, if there is an actual need, I could make the hand unit always output to the nearest quarter inch, instead of the 14.2 shown above. Johnuniq ( talk) 01:09, 13 October 2013 (UTC)
@ Montanabw: The issue concerns what output is wanted from the following:
{{convert/sandboxlua|147|cm|handlk+in}}
→ 147 centimetres (
convert: unknown unit) (the "h" is wikilinked to
Hand (unit))Should the output show "h" or "hand"? Should the output show "14.2" or "14.1 3⁄4"? Johnuniq ( talk) 04:33, 14 October 2013 (UTC)
After all this, there is the one thing needed that started this discussion and it's the one thing we don't have: a way to convert three ways with the following results: 137–162 cm (13.2–16 hands; 54 to 64 in.) (option for abbrev on or off, I suppose) Possibly an inches first to hands and cm also useful, though will rarely be used, most likely never. It's the folks who feel it is terribly important to provide horse measurements with cm first that's the concern. {{ hands}} takes care of everything else Montanabw (talk) 23:16, 16 October 2013 (UTC)
Prior to using the Convert template, THIS table seemed to be sorting fine by height. Now, it is no longer sorting correctly. For example, when sorting by increasing height, since Cerro de Punta is taller than Cerro Maravilla it should appear before Cerro Maravilla in the list, but it doesn't. It seems that the Convert template may be the culprit. Has anyone here experienced this before? Thanks, Mercy11 ( talk) 18:49, 8 October 2013 (UTC)
For Avocado production in Mexico#Production, how would one convert metric tons or tonnes per hectare (MT/ha or t/ha) into a dual conversion of short tons per acre and long tons per acre (ST/acre and LT/acre) eg {{ convert}}? Peter Horn User talk 18:04, 12 October 2013 (UTC)
Thanks to Wikid77 for the comparisons in the previous section because when I started looking at adding the "MT/ha" missing unit I found errors in the pressure units defined in the module, and have spent most of the last few hours completely befuddled. I have fixed the problems (I think) so the unit definitions in the module do not produce incorrect outputs, but there are some problems...
First, here are some simple errors which became apparent during testing:
{{convert|1|g/cm2|abbr=on}}
→ 1 g/cm2 (2.0 lb/sq ft) [currently shows "1 g/m²"]{{convert/sandboxlua|1|g/cm2|abbr=on}}
→ 1 g/cm2 (2.0 lb/sq ft){{convert|1|oz/sqft|abbr=on}}
→ 1 oz/sq ft (310 g/m2) [currently shows "1 oz/sq yd"]{{convert/sandboxlua|1|oz/sqft|abbr=on}}
→ 1 oz/sq ft (310 g/m2)The serious problem concerns confusion between units for pressure and units for mass per unit area (such as "application rate", or paper "weight").
These units (and a few other similar units) have scales that are correct only for "mass per unit area":
These units have scales that are correct only for "pressure":
An example of incorrect output is shown below. The kg/cm2 (pressure) values are correct, while the kg/m2 (mass per unit area) outputs are incorrect by a factor of 9.8 (70e-4 kg/cm2 = 70 kg/m2).
{{convert|70e-4|kg/cm2|MPa|abbr=on|sigfig=4}}
→ 70×10−4 kg/cm2 (6.865×10−4 MPa){{convert|70e-4|kg/cm2|psi|abbr=on|sigfig=4}}
→ 70×10−4 kg/cm2 (0.09956 psi){{convert|70e-4|kg/cm2|MPa psi|abbr=on|sigfig=4}}
→ 70×10−4 kg/cm2 (6.865×10−4 MPa; 0.09956 psi){{convert|70|kg/m2|MPa|abbr=on|sigfig=4}}
→ 70 kg/m2 (0.0006865 MPa) [currently output is equivalent to 0.00007 MPa]{{convert|70|kg/m2|psi|abbr=on|sigfig=4}}
→ 70 kg/m2 (0.09956 psi){{convert|70|kg/m2|MPa psi|abbr=on|sigfig=4}}
→ 70 kg/m2 (0.0006865 MPa; 0.09956 psi)The module used to have the same error, but I have recently fixed the unit definitions and it's now giving:
{{convert/sandboxlua|70e-4|kg/cm2|MPa|abbr=on|sigfig=4}}
→ 70×10−4 kg/cm2 (6.865×10−4 MPa){{convert/sandboxlua|70e-4|kg/cm2|psi|abbr=on|sigfig=4}}
→ 70×10−4 kg/cm2 (0.09956 psi){{convert/sandboxlua|70e-4|kg/cm2|MPa psi|abbr=on|sigfig=4}}
→ 70×10−4 kg/cm2 (6.865×10−4 MPa; 0.09956 psi){{convert/sandboxlua|70|kg/m2|MPa|abbr=on|sigfig=4}}
→ 70 kg/m2 (0.0006865 MPa){{convert/sandboxlua|70|kg/m2|psi|abbr=on|sigfig=4}}
→ 70 kg/m2 (0.09956 psi){{convert/sandboxlua|70|kg/m2|MPa psi|abbr=on|sigfig=4}}
→ 70 kg/m2 (0.0006865 MPa; 0.09956 psi)The module currently defines the following as mass per unit area (and so will not convert these to pressure):
{{convert/sandboxlua|1|g/cm2}}
→ 1 gram per square centimetre (2.0 lb/sq ft){{convert/sandboxlua|1|g/m2}}
→ 1 gram per square metre (0.00020 lb/sq ft){{convert/sandboxlua|1|kg/m2}}
→ 1 kilogram per square metre (0.20 lb/sq ft){{convert/sandboxlua|1|lb/1000sqft}}
→ 1 pound per thousand square feet (4.9 g/m2){{convert/sandboxlua|1|lb/sqft}}
→ 1 pound per square foot (4.9 kg/m2){{convert/sandboxlua|1|lb/sqyd}}
→ 1 pound per square yard (0.54 kg/m2){{convert/sandboxlua|1|LT/acre}}
→ 1 long ton per acre (2.5 t/ha){{convert/sandboxlua|1|MT/ha}}
→ 1 metric ton per hectare (0.40 long ton/acre; 0.45 short ton/acre){{convert/sandboxlua|1|oz/sqft}}
→ 1 ounce per square foot (310 g/m2){{convert/sandboxlua|1|oz/sqyd}}
→ 1 ounce per square yard (34 g/m2){{convert/sandboxlua|1|ST/acre}}
→ 1 short ton per acre (2.2 t/ha){{convert/sandboxlua|1|t/ha|LT/acre ST/acre}}
→ 1 tonne per hectare (0.40 long ton/acre; 0.45 short ton/acre){{convert/sandboxlua|1|t/ha|LT ST/acre}}
→ 1 tonne per hectare (
convert: unknown unit)Pressure units include:
{{convert/sandboxlua|1|kg/cm2|Pa}}
→ 1 kilogram per square centimetre (98,000 Pa){{convert/sandboxlua|1|lbf/in2|Pa}}
→ 1 pound-force per square inch (6,900 Pa){{convert/sandboxlua|1|psi|Pa}}
→ 1 pound per square inch (6,900 Pa)The problem is that my searching finds only a couple of articles using kg/m2 as mass per unit area. By contrast, thousands use it as pressure, mostly via {{ aircraft specs}}. My preference would be to educate the world that "kg/m2" really cannot be used for pressure, but it looks like that's not going to be productive. A benefit of making kg/m2 pressure is that it would then be consistent with kg/cm2 which is pressure.
I can't get any further at the moment, so I'm outlining the current situation. It looks like "kg/m2" and perhaps some others will have to be pressure, so new unit codes will be needed for "kg-mass/m2", and eventually a few articles will need editing to use those unit codes. As far as I can tell, only a very small number of incorrect conversions are currently visible in articles—in principle, many conversions are wrong, but in practice the numbers work out to be correct for the particular units actually in use (for example, using the current templates to convert the pressure kg/m2 to lb/sqft works because both are incorrectly defined, but converting kg/m2 to Pa would give an incorrect value).
I could only find one error, and that's in Russian locomotive class Ye which uses:
{{convert|70|kg/m2|MPa psi|abbr=on}}
→ 70 kg/m2 (0.00069 MPa; 0.100 psi)The following result is correct (70e-4 kg/cm2 = 70 kg/m2):
{{convert|70e-4|kg/cm2|MPa psi|abbr=on}}
→ 70×10−4 kg/cm2 (6.9×10−4 MPa; 0.100 psi)Perhaps I'll think of a gigantic kludge so kg/m2 can be used for pressure and for mass-per-unit-area, but I'd prefer not to. Johnuniq ( talk) 08:42, 15 October 2013 (UTC)
Let us get away from the incorrect usage of "kg/m2", "t/ha", "oz/sq in", "lb/sq ft", etc. to refer to pressure units ("kgf/m2", "tf/ha", "ozf/sq in", "lbf/sq ft", etc.) So, no, the b in {{convert/kg/m2}} should remain as 1 and this shouldn't be used for pressure, it's a mass per unit area, how else would we be able to convert area densities (mass per area production rates, etc.)? So, I say do educate the world that kg/cm2 is not a pressure (let the template give an error message whenever this is attempted). It might not look like it'll be productive but, in the long term, not doing so is going to be hugely problematic. We should insist that kilograms-force, pounds-force, etc. be explicitly stated and thus too weight per area (this is more a MOSNUM issue). Let's get started on fixing the problem; thousands of articles may be misusing kg/m2
but it's not so daunting if it's mostly through another template: fix that and the problem will mostly vanish.
Jimp
08:47, 16 October 2013 (UTC)
kg/m2
and lb/sqft
(where each is a pressure). For example,
Bell Sidewinder shows "Wing loading: 3.25 lb/sq ft (15.9 kg/m2)". I put a proposal to change the template so it works with "kgf" and "lbf" instead of plain "kg" and "lb" at
Template talk:Aircraft specs#Symbols for pressure (with a mention at the
aviation project). I'm hoping there won't be any opposition, and that Jimp would do the edit required at {{
aircraft specs}} to make the change. Let's work towards getting that done, then tackle kg/cm2
and possibly others.
Johnuniq (
talk)
10:57, 16 October 2013 (UTC)
We need to keep the units in line with the way the world uses the terminology, and make the template auto-adjust in cross conversions. The core conversion could be:
FIXED: I put outer parentheses brackets in factor "b=((45359237/9290304)*9.80665)" inside Template:Convert/lbf/sqft. When all the b factors are correct, then 1.0 lbf/sqin = 144 lbf/sqft = 1.0 psi, and similar. Afterward, the subtemplates should use auto-correction and put a superscript note "[fix unit]" to indicate the problem in archived talk-pages, or older revisions of a page. - Wikid77 ( talk) 14:12, 16 October, 14:59, 17 October 2013 (UTC)
Having changed my mind about what to do every day, a response from Redrose64 at the trains project has pushed me towards the "give the customer what they want" path. Wikid77's above suggestion to fiddle the scales has now been implemented so all the converts work. All the units which were "mass per unit area" are now "pressure", and I think all the converts are correct. The only issue is that, for example, "kg/m2" is now a pressure, when "kgf/m2" would be more correct. Examples:
{{convert/sandboxlua|1|kg/m2|Pa|5}}
→ 1 kilogram per square metre (9.80665 Pa){{convert/sandboxlua|70|kg/m2|Pa+psi|abbr=on|4}}
→ 70 kg/m2 (686.4655 Pa; 0.0996 psi){{convert/sandboxlua|0.007|kg/cm2|Pa+psi|abbr=on|4}}
→ 0.007 kg/cm2 (686.4655 Pa; 0.0996 psi){{convert/sandboxlua|1|g/cm2|Pa|4}}
→ 1 gram per square centimetre (98.0665 Pa){{convert/sandboxlua|1|g/cm2|N/m2|6}}
→ 1 gram per square centimetre (98.066500 N/m2){{convert/sandboxlua|1|lbf/in2|lb/sqft|2}}
→ 1 pound-force per square inch (144.00 lb/sq ft){{convert/sandboxlua|1|lb/sqft|Pa|2}}
→ 1 pound per square foot (47.88 Pa){{convert/sandboxlua|1000|lb/1000sqft|Pa|2}}
→ 1,000 pounds per thousand square feet (47.88 Pa)The code changes were amazingly simple ( convert diff and makeunits diff), although changing everything to pressue was more messy ( conversion data diff). Johnuniq ( talk) 06:32, 22 October 2013 (UTC)
I am planning to update the temperature ranges, as Template:Convert/Dual/LoffAoffDxSoffT, to provide the following improvements:
For years, users have asked for the true minus signs in negative temperature ranges, and I found a method to insert them without exceeding the template-expansion depth limit. Example:
If there are no other requested changes, then I will update that subtemplate after midnight UTC. - Wikid77 ( talk) 18:12, 18 October 2013 (UTC)
Any demand for this? Andy Dingley ( talk) 15:20, 19 October 2013 (UTC)
{{convert/old|5 Aug|date|day}}
. Plus we have 12/24-hour time: {{convert/old|9:23 pm|time|24}} → {{convert/old|9:23 pm|time|24}}
. However, for articles which cross events from the Catholic culture to other calendars, then the date-conversion would be useful, and currently an editor would forced to cite a website which does
Gregorian-Julian-
Hijri conversions to note the equivalent dates: 31,
Tir, 1403. Because the Lua version prevents date conversions, then we would modify the {convert/old} to keep expanding our coverage of dates. Meanwhile,
Template:Inflation handles some major currency conversions. -
Wikid77 (
talk)
20:48, 19 October 2013 (UTC)The new unit-code "hand in" is a special, custom combination to show horse hands and inches as full unit names, rather than the typical abbreviated symbols with output amounts. Examples:
Due to the complexity of rounding to fractional inches, the range only works in {convert/2} not in {convert}. - Wikid77 ( talk) 21:36, 19 October 2013 (UTC)
The new unit-code "ftinfrac" (like "ftin") converts to feet and fractional inches, with a quarter-inch (1⁄4, 3⁄4) or half-inch fraction. The unit-code is new, and was not in the original Lua version. Examples:
See Template:Convert/ftinfrac for more examples. - Wikid77 ( talk) 21:36, 19 October 2013 (UTC)
I noticed that the templates do something that is inconsistent but good with a range involving ftin, as shown in this table (which shows " 
" where a space occurs).
Convert | Result | Range in output |
---|---|---|
{{convert|2|by|9|m|ft}} |
2 by 9 metres (6.6 by 29.5 ft) | by
|
{{convert|2|by|9|m|ftin}} |
2 by 9 metres (6 ft 7 in by 29 ft 6 in) | × 
|
{{convert|2|x|9|m|ft}} |
2 by 9 metres (6.6 ft × 29.5 ft) |  ×
|
{{convert|2|x|9|m|ftin}} |
2 by 9 metres (6 ft 7 in × 29 ft 6 in) | × 
|
{{convert|2|to|9|m|ft}} |
2 to 9 metres (6.6 to 29.5 ft) | to
|
{{convert|2|to|9|m|ftin}} |
2 to 9 metres (6 ft 7 in to 29 ft 6 in) |  to 
|
There are two minor issues:
Both of these seem desirable and I'm wondering what the module should do.
Re #1: I don't think the way "by" works should magically change if the output happens to be ftin (or other output multiple unit), and I'm thinking there should be a new word to use for those who want "by" for the input and "×" for the output. Simplicity is good so I was thinking of "byx".
Re #2: Perhaps " × 
" should be used instead of " ×
" for all units?
Any thoughts? Johnuniq ( talk) 03:55, 21 October 2013 (UTC)
This 500 thousand barrels per day (
convert: unit mismatch) ({{
convert|500|koilbbl/d|tonne}}
) seems a bit (very) off. Is there a division by 1,000 happening instead of a multiplication? —
Sladen (
talk)
10:32, 23 October 2013 (UTC)
I have finally simplified most non-abbreviated unit-codes to omit the hundreds of "-Na" subtemplates, such as for acre, furlong, and dram, which do not use internal parameter {{{u}}}. This reduction has been ongoing for 2 years, where formerly over 51,400 pages had used Template:Convert/LoffAoffDbSoffNa and related "-Na" subtemplates. The affected unit-codes include more than 40:
Because there are so many unit-codes which omit {{{u}}}, the reduction has taken years to implement, while changing the underlying Convert subtemplates to detect a null {u}. There might still be some cases which show an undefined "{{{u}}}" and those subtemplates can be corrected to display values of parameters {n}, {l}, or {h}. - Wikid77 ( talk) 15:21, 24 October 2013 (UTC)
The "next generation" of conversions includes the use of free-form text, rather than the prior constrained pairs or ranges of numbers. Now, Template:Convert/text3 allows the insertion of free-form descriptive text which is omitted in the results portion. Example:
Note how all the input text is omitted, from the output portion, which defaults to simply show "×" separators. However, new output parameters "out=" or "out2=" or "out3=" allow specifying the alternate text to show between the result amounts.
Before the advent of {convert/text3}, and { convert/text2}, a conversion of a set of numbers (a range) would repeat the input separator-text between the output units, but now {convert/text3} allows a free-form mode which can insert extra description, while omitted in the results, or allows totally unique wording to be inserted among the output amounts. Beyond the major parameters, new options x0-x14 allow custom text to also be inserted between any numbers/units anywhere. These free-form conversions are designed to also work with the Lua-based Convert. The overall goal is to allow more flexibility in wording, as users have requested for tiresome conversions, beyond the monotonous prior forms of: amount (converted), amount (converted), amount (converted), etc. More later. - Wikid77 15:16, 25 October 2013 (UTC)
For SR USA class: {{convert|41|ST|9|Scwt|lk=on}} 41 short tons 9 hundredweight (37.6 t). Can some one fix this? Peter Horn User talk 21:00, 27 October 2013 (UTC) Peter Horn User talk 21:02, 27 October 2013 (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. |
Here are some fixes. Frankly, I hope that you don't spend hours on this, because the "two-way" conversion of hands to only inches or cm/m is strongly discouraged per WP:MEASUREMENT and the active members of WikiProject Equine strongly support a "three-way" conversion of hands to both inches and centimeters, per the {{ hands}} template. The only thing that is needed here, really, is JLAN's request for a reverse conversion from cm first (or, I suppose, inches, though we've yet to do that one) into hands. His specific concern is that some European horse registries, and the FEI, use metric measurements, while most English speaking nations use hands. This, where the centimeter/meter measurement is "official," he makes an argument that the measurement should first be given in metric measurements, with convert used to give us hands and inches. While I do not agree 100% with his position, it is actually reasonable for him to ask for that flexibility, and so long as the conversion is used, I am willing to support it happening. However, what you have needs some fixes, listed below Montanabw (talk) 21:43, 10 October 2013 (UTC)
Rounding 15.38 hands to 16 hands: @ Montanabw, I will need to fix the rounding so that above 0.3+1/2 rounds to 1 extra hand. Currently, rounding to 1 decimal works, but 2 should show fractions of hands:
However, I am working to use new Template:Rndhands, which allows rounding to the nearest half-inch, such as {rndhands|12.143} as 12.11⁄2, or {rndhands|3.26} as 3.21⁄2. The rounding is extremely tedious to retrofit into {convert} with format restrictions in Lua, and so that is why it has taken years to address, but I think we are getting close to a solution. - Wikid77 ( talk) 00:58/03:13/ 03:53, 11 October 2013 (UTC)
Currently, using the adj=on function in combination with ranges does not produce the desired result:
{{convert|1|to|2|ft|adj=on}}
should produce (ideally)
or even (as an alternative)
but instead actually leaves you with 1-to-2-foot (0.30 to 0.61 m), screwing up the hyphenation involved. I know this thing is kind of a beast, but kindly fix it when you have a minute. — LlywelynII 14:07, 29 September 2013 (UTC)
Hawkeye7 ( talk) 20:25, 1 October 2013 (UTC)
If you have a 29-hectare (72-acre) lake, the "acres" should be "acre". — Sladen ( talk) 19:31, 29 September 2013 (UTC)
Would it be possible to provide a means of converting Tesla - Gauss? I was surprised to that there doesn't currently appear to be a way of doing so. Many thanks. Jamesx 12345 17:47, 30 September 2013 (UTC)
Unit code | Symbol | US symbol | Scale | Extra | Name | Plural name | US name | US plural name | Prefix | Default | Link |
---|---|---|---|---|---|---|---|---|---|---|---|
T | T | 1 | tesla | SI | G | Tesla (unit) | |||||
G | G | 0.0001 | gauss | gauss | T | Gauss (unit) |
{{convert/sandboxlua|2|T}}
→ 2 teslas (20,000 G){{convert/sandboxlua|2|G}}
→ 2 gauss (0.00020 T){{convert/sandboxlua|1|kT|G}}
→ 1 kilotesla (10,000,000 G){{convert/sandboxlua|1|MT|G}}
→ 1 metric ton (
convert: unit mismatch){{convert/sandboxlua|1|MT}}
→ 1 metric ton (0.98 long tons; 1.1 short tons){{convert|1|kT|G}}
→ 1 kilotesla (10,000,000 G){{convert|1|MT|G}}
→ 1 metric ton (
convert: unit mismatch){{convert|1|MT}}
→ 1 metric ton (0.98 long tons; 1.1 short tons)Comment Note that a tesla is a really big unit to begin with.
Our article mentions the magnets in the
LHC at
CERN are 8 T. Lack of support for kT or MT is unlikely to be noticed
. —[
AlanM1(
talk)]—
01:36, 3 October 2013 (UTC)
How do I convert compound units, such as "ton-miles per day"? The obvious ST*mi/day does not work. StephenTX ( talk) 22:54, 5 October 2013 (UTC)
For Tropical Storm Marco (2008)#Preparations, impact and records 1 inch per hour (25 mm/h). Peter Horn User talk 16:19, 6 October 2013 (UTC)
Currently
module:convert/extra
code does not correspond with
module:convert/extra/doc. So I cannot make testcases/demos. We really need discipline in this. "/extra" is a great way to improve convert, but it should not be treated as a private sandbox. -
DePiep (
talk)
19:39, 6 October 2013 (UTC)
I've encountered some problems managing hands and centimetres with disp=flip.
For example:
{{convert|16.3|hand|cm}}
16.3
hands (170 cm)
{{convert|16.3|hand|cm|disp=flip}}
170 centimetres (16.3 h)
In other words, the template does not work when the input unit is hands, the output unit is centimetres and there's disp=flip (useful when dealing with non UK-related horse articles).
Best regards and thanks in advance.--
Carnby (
talk)
08:49, 7 October 2013 (UTC)
There seem to be other problems with hand conversions too. Some people think it necessary to convert metric units to both hands and inches for horse height (I'm not one of those people, btw). If I've understood correctly, we are supposed to use {{ convert/show2 }} for this kind of thing, rather than request yet another three-way convert. However, at the moment neither appears to work:
{{convert/show2 |165|cm|hand|in}}
—> 165 centimetres (16.1 4.0 hands (41 cm); 65 in){{convert/show2 |1.65|m|hand|in}}
—> 1.65 metres (16.10 4.0 hands (41 cm); 65 in){{convert|165|cm|h in|2|lk=out}}
—> an error messageAny advice? Justlettersandnumbers ( talk) 18:22, 8 October 2013 (UTC)
Because the symbol "h" (for "hands") is rarely used in general writing (often as "h" for "hours"), then
Template:Convert/hand has been reset to default the unit as the wikilinked unit name "hands"
Similar settings will be needed in the Lua version, which now shows:
For most cases, Template:Hands can be used instead. - Wikid77 05:26, 9 October 2013 (UTC)
lk=off
does not seem to work)? An article with several hand conversions should not link each of the occurrences, and if anyone ever wanted to add some convert templates to
Hand (unit), they would not want them linked.{{convert/sandboxlua|14.1|hand|in cm|lk=in}}
→ 14.1
hands (57 inches; 145 cm){{convert/sandboxlua|88|in|hand|abbr=off|lk=out}}
→ 88 inches (22.0
hands){{convert/sandboxlua|13.3|-|14.2|hand|in|lk=in}}
→ 13.3–14.2
hands (55–58 inches){{convert/sandboxlua|77|in|hand+cm|lk=out}}
→ 77 inches (19.1
hands; 200
cm)hand+cm
for a user-specified combination, but has the defect that
cm is linked.
Johnuniq (
talk)
08:50, 9 October 2013 (UTC)
It looks like the WPEQ people are happy with {{ hands}}, but as Montanabw says, the templates should not contradict each other, so I fixed the module to interpret fractions of a hand as fractions of an inch. It could be argued that the default rounding from the module is not optimum, but I'm going to pass on tweaking that at the moment.
{{hands|14.1+3/4}}
→ 14.1 3⁄4
hands (57.75 inches, 147 cm){{convert/sandboxlua|14.1+3/4|hand}}
→ 14.1+3⁄4
hands (57.75 inches; 147 cm){{convert/sandboxlua|14.1+3/4|hand|in+cm}}
→ 14.1+3⁄4
hands (57.75 inches; 147 cm){{convert/sandboxlua|14.1+3/4|hand|in+cm|lk=in}}
→ 14.1+3⁄4
hands (57.75 inches; 147 cm)The above numbers are from the lead of Theodore O'Connor. Johnuniq ( talk) 00:32, 11 October 2013 (UTC)
{{convert/sandboxlua|57.75|in|hand}}
→ 57.75 inches (14.2
hands)147cm
to produce like 14.1 3⁄4
hands (57.75 inches, 147 cm) or so. Any actual example for the need? Well, since it does not work today (by any documentation promise), it won't happen tomorrow with new module. -
DePiep (
talk)
22:26, 12 October 2013 (UTC)I've done what's easy, namely added a unit called "handlk" which is the same as hand but which always links to the article.
{{convert/sandboxlua|14.1+3/4|handlk|in+cm}}
→ 14.1+3⁄4 handlk
convert: unknown unit{{convert/sandboxlua|147|cm|hand+in}}
→ 147 centimetres (14.2
hands; 58 in){{convert/sandboxlua|147|cm|handlk+in}}
→ 147 centimetres (
convert: unknown unit){{convert/sandboxlua|147|cm|handlk+in|lk=on}}
→ 147
centimetres (
convert: unknown unit)Later, and as DePiep mentions, if there is an actual need, I could make the hand unit always output to the nearest quarter inch, instead of the 14.2 shown above. Johnuniq ( talk) 01:09, 13 October 2013 (UTC)
@ Montanabw: The issue concerns what output is wanted from the following:
{{convert/sandboxlua|147|cm|handlk+in}}
→ 147 centimetres (
convert: unknown unit) (the "h" is wikilinked to
Hand (unit))Should the output show "h" or "hand"? Should the output show "14.2" or "14.1 3⁄4"? Johnuniq ( talk) 04:33, 14 October 2013 (UTC)
After all this, there is the one thing needed that started this discussion and it's the one thing we don't have: a way to convert three ways with the following results: 137–162 cm (13.2–16 hands; 54 to 64 in.) (option for abbrev on or off, I suppose) Possibly an inches first to hands and cm also useful, though will rarely be used, most likely never. It's the folks who feel it is terribly important to provide horse measurements with cm first that's the concern. {{ hands}} takes care of everything else Montanabw (talk) 23:16, 16 October 2013 (UTC)
Prior to using the Convert template, THIS table seemed to be sorting fine by height. Now, it is no longer sorting correctly. For example, when sorting by increasing height, since Cerro de Punta is taller than Cerro Maravilla it should appear before Cerro Maravilla in the list, but it doesn't. It seems that the Convert template may be the culprit. Has anyone here experienced this before? Thanks, Mercy11 ( talk) 18:49, 8 October 2013 (UTC)
For Avocado production in Mexico#Production, how would one convert metric tons or tonnes per hectare (MT/ha or t/ha) into a dual conversion of short tons per acre and long tons per acre (ST/acre and LT/acre) eg {{ convert}}? Peter Horn User talk 18:04, 12 October 2013 (UTC)
Thanks to Wikid77 for the comparisons in the previous section because when I started looking at adding the "MT/ha" missing unit I found errors in the pressure units defined in the module, and have spent most of the last few hours completely befuddled. I have fixed the problems (I think) so the unit definitions in the module do not produce incorrect outputs, but there are some problems...
First, here are some simple errors which became apparent during testing:
{{convert|1|g/cm2|abbr=on}}
→ 1 g/cm2 (2.0 lb/sq ft) [currently shows "1 g/m²"]{{convert/sandboxlua|1|g/cm2|abbr=on}}
→ 1 g/cm2 (2.0 lb/sq ft){{convert|1|oz/sqft|abbr=on}}
→ 1 oz/sq ft (310 g/m2) [currently shows "1 oz/sq yd"]{{convert/sandboxlua|1|oz/sqft|abbr=on}}
→ 1 oz/sq ft (310 g/m2)The serious problem concerns confusion between units for pressure and units for mass per unit area (such as "application rate", or paper "weight").
These units (and a few other similar units) have scales that are correct only for "mass per unit area":
These units have scales that are correct only for "pressure":
An example of incorrect output is shown below. The kg/cm2 (pressure) values are correct, while the kg/m2 (mass per unit area) outputs are incorrect by a factor of 9.8 (70e-4 kg/cm2 = 70 kg/m2).
{{convert|70e-4|kg/cm2|MPa|abbr=on|sigfig=4}}
→ 70×10−4 kg/cm2 (6.865×10−4 MPa){{convert|70e-4|kg/cm2|psi|abbr=on|sigfig=4}}
→ 70×10−4 kg/cm2 (0.09956 psi){{convert|70e-4|kg/cm2|MPa psi|abbr=on|sigfig=4}}
→ 70×10−4 kg/cm2 (6.865×10−4 MPa; 0.09956 psi){{convert|70|kg/m2|MPa|abbr=on|sigfig=4}}
→ 70 kg/m2 (0.0006865 MPa) [currently output is equivalent to 0.00007 MPa]{{convert|70|kg/m2|psi|abbr=on|sigfig=4}}
→ 70 kg/m2 (0.09956 psi){{convert|70|kg/m2|MPa psi|abbr=on|sigfig=4}}
→ 70 kg/m2 (0.0006865 MPa; 0.09956 psi)The module used to have the same error, but I have recently fixed the unit definitions and it's now giving:
{{convert/sandboxlua|70e-4|kg/cm2|MPa|abbr=on|sigfig=4}}
→ 70×10−4 kg/cm2 (6.865×10−4 MPa){{convert/sandboxlua|70e-4|kg/cm2|psi|abbr=on|sigfig=4}}
→ 70×10−4 kg/cm2 (0.09956 psi){{convert/sandboxlua|70e-4|kg/cm2|MPa psi|abbr=on|sigfig=4}}
→ 70×10−4 kg/cm2 (6.865×10−4 MPa; 0.09956 psi){{convert/sandboxlua|70|kg/m2|MPa|abbr=on|sigfig=4}}
→ 70 kg/m2 (0.0006865 MPa){{convert/sandboxlua|70|kg/m2|psi|abbr=on|sigfig=4}}
→ 70 kg/m2 (0.09956 psi){{convert/sandboxlua|70|kg/m2|MPa psi|abbr=on|sigfig=4}}
→ 70 kg/m2 (0.0006865 MPa; 0.09956 psi)The module currently defines the following as mass per unit area (and so will not convert these to pressure):
{{convert/sandboxlua|1|g/cm2}}
→ 1 gram per square centimetre (2.0 lb/sq ft){{convert/sandboxlua|1|g/m2}}
→ 1 gram per square metre (0.00020 lb/sq ft){{convert/sandboxlua|1|kg/m2}}
→ 1 kilogram per square metre (0.20 lb/sq ft){{convert/sandboxlua|1|lb/1000sqft}}
→ 1 pound per thousand square feet (4.9 g/m2){{convert/sandboxlua|1|lb/sqft}}
→ 1 pound per square foot (4.9 kg/m2){{convert/sandboxlua|1|lb/sqyd}}
→ 1 pound per square yard (0.54 kg/m2){{convert/sandboxlua|1|LT/acre}}
→ 1 long ton per acre (2.5 t/ha){{convert/sandboxlua|1|MT/ha}}
→ 1 metric ton per hectare (0.40 long ton/acre; 0.45 short ton/acre){{convert/sandboxlua|1|oz/sqft}}
→ 1 ounce per square foot (310 g/m2){{convert/sandboxlua|1|oz/sqyd}}
→ 1 ounce per square yard (34 g/m2){{convert/sandboxlua|1|ST/acre}}
→ 1 short ton per acre (2.2 t/ha){{convert/sandboxlua|1|t/ha|LT/acre ST/acre}}
→ 1 tonne per hectare (0.40 long ton/acre; 0.45 short ton/acre){{convert/sandboxlua|1|t/ha|LT ST/acre}}
→ 1 tonne per hectare (
convert: unknown unit)Pressure units include:
{{convert/sandboxlua|1|kg/cm2|Pa}}
→ 1 kilogram per square centimetre (98,000 Pa){{convert/sandboxlua|1|lbf/in2|Pa}}
→ 1 pound-force per square inch (6,900 Pa){{convert/sandboxlua|1|psi|Pa}}
→ 1 pound per square inch (6,900 Pa)The problem is that my searching finds only a couple of articles using kg/m2 as mass per unit area. By contrast, thousands use it as pressure, mostly via {{ aircraft specs}}. My preference would be to educate the world that "kg/m2" really cannot be used for pressure, but it looks like that's not going to be productive. A benefit of making kg/m2 pressure is that it would then be consistent with kg/cm2 which is pressure.
I can't get any further at the moment, so I'm outlining the current situation. It looks like "kg/m2" and perhaps some others will have to be pressure, so new unit codes will be needed for "kg-mass/m2", and eventually a few articles will need editing to use those unit codes. As far as I can tell, only a very small number of incorrect conversions are currently visible in articles—in principle, many conversions are wrong, but in practice the numbers work out to be correct for the particular units actually in use (for example, using the current templates to convert the pressure kg/m2 to lb/sqft works because both are incorrectly defined, but converting kg/m2 to Pa would give an incorrect value).
I could only find one error, and that's in Russian locomotive class Ye which uses:
{{convert|70|kg/m2|MPa psi|abbr=on}}
→ 70 kg/m2 (0.00069 MPa; 0.100 psi)The following result is correct (70e-4 kg/cm2 = 70 kg/m2):
{{convert|70e-4|kg/cm2|MPa psi|abbr=on}}
→ 70×10−4 kg/cm2 (6.9×10−4 MPa; 0.100 psi)Perhaps I'll think of a gigantic kludge so kg/m2 can be used for pressure and for mass-per-unit-area, but I'd prefer not to. Johnuniq ( talk) 08:42, 15 October 2013 (UTC)
Let us get away from the incorrect usage of "kg/m2", "t/ha", "oz/sq in", "lb/sq ft", etc. to refer to pressure units ("kgf/m2", "tf/ha", "ozf/sq in", "lbf/sq ft", etc.) So, no, the b in {{convert/kg/m2}} should remain as 1 and this shouldn't be used for pressure, it's a mass per unit area, how else would we be able to convert area densities (mass per area production rates, etc.)? So, I say do educate the world that kg/cm2 is not a pressure (let the template give an error message whenever this is attempted). It might not look like it'll be productive but, in the long term, not doing so is going to be hugely problematic. We should insist that kilograms-force, pounds-force, etc. be explicitly stated and thus too weight per area (this is more a MOSNUM issue). Let's get started on fixing the problem; thousands of articles may be misusing kg/m2
but it's not so daunting if it's mostly through another template: fix that and the problem will mostly vanish.
Jimp
08:47, 16 October 2013 (UTC)
kg/m2
and lb/sqft
(where each is a pressure). For example,
Bell Sidewinder shows "Wing loading: 3.25 lb/sq ft (15.9 kg/m2)". I put a proposal to change the template so it works with "kgf" and "lbf" instead of plain "kg" and "lb" at
Template talk:Aircraft specs#Symbols for pressure (with a mention at the
aviation project). I'm hoping there won't be any opposition, and that Jimp would do the edit required at {{
aircraft specs}} to make the change. Let's work towards getting that done, then tackle kg/cm2
and possibly others.
Johnuniq (
talk)
10:57, 16 October 2013 (UTC)
We need to keep the units in line with the way the world uses the terminology, and make the template auto-adjust in cross conversions. The core conversion could be:
FIXED: I put outer parentheses brackets in factor "b=((45359237/9290304)*9.80665)" inside Template:Convert/lbf/sqft. When all the b factors are correct, then 1.0 lbf/sqin = 144 lbf/sqft = 1.0 psi, and similar. Afterward, the subtemplates should use auto-correction and put a superscript note "[fix unit]" to indicate the problem in archived talk-pages, or older revisions of a page. - Wikid77 ( talk) 14:12, 16 October, 14:59, 17 October 2013 (UTC)
Having changed my mind about what to do every day, a response from Redrose64 at the trains project has pushed me towards the "give the customer what they want" path. Wikid77's above suggestion to fiddle the scales has now been implemented so all the converts work. All the units which were "mass per unit area" are now "pressure", and I think all the converts are correct. The only issue is that, for example, "kg/m2" is now a pressure, when "kgf/m2" would be more correct. Examples:
{{convert/sandboxlua|1|kg/m2|Pa|5}}
→ 1 kilogram per square metre (9.80665 Pa){{convert/sandboxlua|70|kg/m2|Pa+psi|abbr=on|4}}
→ 70 kg/m2 (686.4655 Pa; 0.0996 psi){{convert/sandboxlua|0.007|kg/cm2|Pa+psi|abbr=on|4}}
→ 0.007 kg/cm2 (686.4655 Pa; 0.0996 psi){{convert/sandboxlua|1|g/cm2|Pa|4}}
→ 1 gram per square centimetre (98.0665 Pa){{convert/sandboxlua|1|g/cm2|N/m2|6}}
→ 1 gram per square centimetre (98.066500 N/m2){{convert/sandboxlua|1|lbf/in2|lb/sqft|2}}
→ 1 pound-force per square inch (144.00 lb/sq ft){{convert/sandboxlua|1|lb/sqft|Pa|2}}
→ 1 pound per square foot (47.88 Pa){{convert/sandboxlua|1000|lb/1000sqft|Pa|2}}
→ 1,000 pounds per thousand square feet (47.88 Pa)The code changes were amazingly simple ( convert diff and makeunits diff), although changing everything to pressue was more messy ( conversion data diff). Johnuniq ( talk) 06:32, 22 October 2013 (UTC)
I am planning to update the temperature ranges, as Template:Convert/Dual/LoffAoffDxSoffT, to provide the following improvements:
For years, users have asked for the true minus signs in negative temperature ranges, and I found a method to insert them without exceeding the template-expansion depth limit. Example:
If there are no other requested changes, then I will update that subtemplate after midnight UTC. - Wikid77 ( talk) 18:12, 18 October 2013 (UTC)
Any demand for this? Andy Dingley ( talk) 15:20, 19 October 2013 (UTC)
{{convert/old|5 Aug|date|day}}
. Plus we have 12/24-hour time: {{convert/old|9:23 pm|time|24}} → {{convert/old|9:23 pm|time|24}}
. However, for articles which cross events from the Catholic culture to other calendars, then the date-conversion would be useful, and currently an editor would forced to cite a website which does
Gregorian-Julian-
Hijri conversions to note the equivalent dates: 31,
Tir, 1403. Because the Lua version prevents date conversions, then we would modify the {convert/old} to keep expanding our coverage of dates. Meanwhile,
Template:Inflation handles some major currency conversions. -
Wikid77 (
talk)
20:48, 19 October 2013 (UTC)The new unit-code "hand in" is a special, custom combination to show horse hands and inches as full unit names, rather than the typical abbreviated symbols with output amounts. Examples:
Due to the complexity of rounding to fractional inches, the range only works in {convert/2} not in {convert}. - Wikid77 ( talk) 21:36, 19 October 2013 (UTC)
The new unit-code "ftinfrac" (like "ftin") converts to feet and fractional inches, with a quarter-inch (1⁄4, 3⁄4) or half-inch fraction. The unit-code is new, and was not in the original Lua version. Examples:
See Template:Convert/ftinfrac for more examples. - Wikid77 ( talk) 21:36, 19 October 2013 (UTC)
I noticed that the templates do something that is inconsistent but good with a range involving ftin, as shown in this table (which shows " 
" where a space occurs).
Convert | Result | Range in output |
---|---|---|
{{convert|2|by|9|m|ft}} |
2 by 9 metres (6.6 by 29.5 ft) | by
|
{{convert|2|by|9|m|ftin}} |
2 by 9 metres (6 ft 7 in by 29 ft 6 in) | × 
|
{{convert|2|x|9|m|ft}} |
2 by 9 metres (6.6 ft × 29.5 ft) |  ×
|
{{convert|2|x|9|m|ftin}} |
2 by 9 metres (6 ft 7 in × 29 ft 6 in) | × 
|
{{convert|2|to|9|m|ft}} |
2 to 9 metres (6.6 to 29.5 ft) | to
|
{{convert|2|to|9|m|ftin}} |
2 to 9 metres (6 ft 7 in to 29 ft 6 in) |  to 
|
There are two minor issues:
Both of these seem desirable and I'm wondering what the module should do.
Re #1: I don't think the way "by" works should magically change if the output happens to be ftin (or other output multiple unit), and I'm thinking there should be a new word to use for those who want "by" for the input and "×" for the output. Simplicity is good so I was thinking of "byx".
Re #2: Perhaps " × 
" should be used instead of " ×
" for all units?
Any thoughts? Johnuniq ( talk) 03:55, 21 October 2013 (UTC)
This 500 thousand barrels per day (
convert: unit mismatch) ({{
convert|500|koilbbl/d|tonne}}
) seems a bit (very) off. Is there a division by 1,000 happening instead of a multiplication? —
Sladen (
talk)
10:32, 23 October 2013 (UTC)
I have finally simplified most non-abbreviated unit-codes to omit the hundreds of "-Na" subtemplates, such as for acre, furlong, and dram, which do not use internal parameter {{{u}}}. This reduction has been ongoing for 2 years, where formerly over 51,400 pages had used Template:Convert/LoffAoffDbSoffNa and related "-Na" subtemplates. The affected unit-codes include more than 40:
Because there are so many unit-codes which omit {{{u}}}, the reduction has taken years to implement, while changing the underlying Convert subtemplates to detect a null {u}. There might still be some cases which show an undefined "{{{u}}}" and those subtemplates can be corrected to display values of parameters {n}, {l}, or {h}. - Wikid77 ( talk) 15:21, 24 October 2013 (UTC)
The "next generation" of conversions includes the use of free-form text, rather than the prior constrained pairs or ranges of numbers. Now, Template:Convert/text3 allows the insertion of free-form descriptive text which is omitted in the results portion. Example:
Note how all the input text is omitted, from the output portion, which defaults to simply show "×" separators. However, new output parameters "out=" or "out2=" or "out3=" allow specifying the alternate text to show between the result amounts.
Before the advent of {convert/text3}, and { convert/text2}, a conversion of a set of numbers (a range) would repeat the input separator-text between the output units, but now {convert/text3} allows a free-form mode which can insert extra description, while omitted in the results, or allows totally unique wording to be inserted among the output amounts. Beyond the major parameters, new options x0-x14 allow custom text to also be inserted between any numbers/units anywhere. These free-form conversions are designed to also work with the Lua-based Convert. The overall goal is to allow more flexibility in wording, as users have requested for tiresome conversions, beyond the monotonous prior forms of: amount (converted), amount (converted), amount (converted), etc. More later. - Wikid77 15:16, 25 October 2013 (UTC)
For SR USA class: {{convert|41|ST|9|Scwt|lk=on}} 41 short tons 9 hundredweight (37.6 t). Can some one fix this? Peter Horn User talk 21:00, 27 October 2013 (UTC) Peter Horn User talk 21:02, 27 October 2013 (UTC)