![]() | 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. |
I see that section editing is possible for the /doc subpage, but why is is there no edit tags for the main page documentation? Why do I have to View /doc first, before I can edit the section I'm reading? — Cpiral Cpiral 06:07, 1 August 2015 (UTC)
{{documentation|page=Template:Convert}}
does show the edit links in a sandbox once that sandbox is saved. And for example {{
Val}} does show the edit links as it should. —
Cpiral
Cpiral
19:55, 1 August 2015 (UTC)
I'm only very slightly proficient with template markup, and I'd appreciate someone adding the feddan (I edit Egypt articles from time to time).
The Egyptian standard feddan is 4200 square meters, or 0.42 hectares, or 1.038 acres. Sudan uses the same unit. Syria uses a smaller feddan, but it is less used as the dunam is also a common unit of land measurement there. I don't know which definition Oman uses. Lockesdonkey ( talk) 21:58, 5 August 2015 (UTC)
{{convert|1|feddan}}
→ 1 feddan
convert: unknown unit{{convert|200|feddan|ha|lk=in}}
→ 200
feddan
convert: unknown unitSome changes to the convert modules are in the sandbox, and I intend switching the main modules to use the sandbox soon.
The changes are:
lk=on
applies (discussed
here):
abbr=mos
has a misleading name but it is used in a handful of articles and seems reasonable. If used, it causes the input unit name to be repeated for a range. An example is at
Commodore Nutt#Death:
Nutt had grown from his original {{convert|29|to|43|in|cm|abbr=mos}}
→ Nutt had grown from his original 29 to 43 inches (74 to 109 cm)
*x
is now MOS-compliant in that it always repeats the unit symbol when displaying a multiply symbol (×). Previously, that only occurred for a range of two items. For compatibility with current usage (x
is used over 6,000 times in articles), the range shows "×" when units are abbreviated and "by" when they are in full. Displaying "by" means convert defaults to using natural language such as "2 by 3 feet" for the input.by(x)
range is for those who prefer showing more clearly that "by" is intended for the values first displayed. Examples:
{{convert/sandbox|1x2x3|m|cm|abbr=on}}
→ 1 m × 2 m × 3 m (100 cm × 200 cm × 300 cm){{convert/sandbox|1|by(x)|2|m|cm}}
→ 1 by 2 metres (100 cm × 200 cm){{convert/sandbox|1|by(x)|2|m|cm|abbr=on}}
→ 1 by 2 m (100 cm × 200 cm){{convert/sandbox|1|by(x)|2|m|cm|order=flip}}
→ 100 by 200 centimetres (1 m × 2 m){{convert/sandbox|1.2|mi|adj=ri0}}
→ 1 mile (1.9 km) (result has "1 mile" rather than "1 miles")round=0.5
option to round the output to the nearest half, with the display being either N or N.5 where N is an integer (discussed
here):
{{convert/sandbox|7x8x12|ft|abbr=on|round=0.5}}
→ 7 ft × 8 ft × 12 ft (2 m × 2.5 m × 3.5 m) (7 ft rounds to 2 m while 8 ft rounds to 2.5 m}_unit
) is exported and may be used by other modules to access convert's data (discussed
here).sortable=on
is now the same as that produced by {{
ntsh}}.
Module:Val uses the _unit
function which can also produce a span element with a hidden sort key.Module version history 1 (Dec 2013) • 2 (Jan 2014) • 3 (April 2014) • 4 (July 2014) • 5 (Sep 2014) • 6 (Nov 2014) • 7 (Dec 2014) • 8 (Feb 2015) • 9 (Feb 2015) • 10 (May 2015) • 11 (June 2015)
Johnuniq ( talk) 09:43, 10 August 2015 (UTC)
The use of the template to convert mm to in produces 7 mm × 40 mm (0.28 in × 1.57 in). Is there a way to delete the first unit-output, & the spaces, & get 7x40mm (.28x1.57in), instead? It would be very useful in metric ammunition designations. TREKphiler any time you're ready, Uhura 18:41, 21 July 2015 (UTC)
With the multiplication sign, each number should be followed by a unit name or symbol (if appropriate)." Perhaps ask at the talk page of WP:UNIT whether the guideline must apply for the example you mentioned, with links to one or more articles showing the issue. The question for MoS is whether those articles should repeat the unit, or whether an exception should be made due to [insert reason here]. I recently noticed Adrastea which includes "Adrastea has an irregular shape and measures 20×16×14 km across" as an example where WP:UNIT seems excessive. Johnuniq ( talk) 22:32, 21 July 2015 (UTC)
Shouldn't "500 metres (1,600 ft)" (ie, {{convert|500|m|ft}}
) be MORE (*NOT* LESS) than "492 metres (1,614 ft)" (ie, {{convert|492|m|ft}}
? - iac - Enjoy! :)
Drbogdan (
talk)
01:45, 24 August 2015 (UTC)
|0
in the third of the following examples overrides the default to round the output to zero decimal places. The last example shows that a range is handled correctly—that provides a clue to convert that extra precision is wanted.
{{convert|492|m|ft}}
→ 492 metres (1,614 ft){{convert|500|m|ft}}
→ 500 metres (1,600 ft){{convert|500|m|ft|0}}
→ 500 metres (1,640 ft){{convert|492-500|m|ft}}
→ 492–500 metres (1,614–1,640 ft)Is there any way to make this template work along with the {{fraction}} template? -- John ( talk) 20:23, 25 August 2015 (UTC)
{{convert|2+1//2|in|mm|1}}
→ 2+1/2 inches (63.5 mm) or {{convert|2+1/2|in|mm|1}}
→ 2+1⁄2 inches (63.5 mm).{{frac|2|1|2}}
→ 2+1⁄2" which is actually 1=<span class="frac nowrap">2<span class="visualhide"> </span><sup>1</sup>⁄<sub>2</sub></span>
, won't be supported.{{convert|1+7/8|in|mm|1}}
→ 1+7⁄8 inches (47.6 mm) or {{convert|1+3/4|in|mm}}
→ 1+3⁄4 inches (44 mm) would do what you wanted.
Imzadi 1979
→
22:44, 25 August 2015 (UTC)
{{convert|48|mm|in|frac=8}}
→ 48 millimetres (1+7⁄8 in){{convert|44|mm|in|frac=8}}
→ 44 millimetres (1+3⁄4 in) (frac=4 or frac=8 give the same result here)![]() | 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. |
I see that section editing is possible for the /doc subpage, but why is is there no edit tags for the main page documentation? Why do I have to View /doc first, before I can edit the section I'm reading? — Cpiral Cpiral 06:07, 1 August 2015 (UTC)
{{documentation|page=Template:Convert}}
does show the edit links in a sandbox once that sandbox is saved. And for example {{
Val}} does show the edit links as it should. —
Cpiral
Cpiral
19:55, 1 August 2015 (UTC)
I'm only very slightly proficient with template markup, and I'd appreciate someone adding the feddan (I edit Egypt articles from time to time).
The Egyptian standard feddan is 4200 square meters, or 0.42 hectares, or 1.038 acres. Sudan uses the same unit. Syria uses a smaller feddan, but it is less used as the dunam is also a common unit of land measurement there. I don't know which definition Oman uses. Lockesdonkey ( talk) 21:58, 5 August 2015 (UTC)
{{convert|1|feddan}}
→ 1 feddan
convert: unknown unit{{convert|200|feddan|ha|lk=in}}
→ 200
feddan
convert: unknown unitSome changes to the convert modules are in the sandbox, and I intend switching the main modules to use the sandbox soon.
The changes are:
lk=on
applies (discussed
here):
abbr=mos
has a misleading name but it is used in a handful of articles and seems reasonable. If used, it causes the input unit name to be repeated for a range. An example is at
Commodore Nutt#Death:
Nutt had grown from his original {{convert|29|to|43|in|cm|abbr=mos}}
→ Nutt had grown from his original 29 to 43 inches (74 to 109 cm)
*x
is now MOS-compliant in that it always repeats the unit symbol when displaying a multiply symbol (×). Previously, that only occurred for a range of two items. For compatibility with current usage (x
is used over 6,000 times in articles), the range shows "×" when units are abbreviated and "by" when they are in full. Displaying "by" means convert defaults to using natural language such as "2 by 3 feet" for the input.by(x)
range is for those who prefer showing more clearly that "by" is intended for the values first displayed. Examples:
{{convert/sandbox|1x2x3|m|cm|abbr=on}}
→ 1 m × 2 m × 3 m (100 cm × 200 cm × 300 cm){{convert/sandbox|1|by(x)|2|m|cm}}
→ 1 by 2 metres (100 cm × 200 cm){{convert/sandbox|1|by(x)|2|m|cm|abbr=on}}
→ 1 by 2 m (100 cm × 200 cm){{convert/sandbox|1|by(x)|2|m|cm|order=flip}}
→ 100 by 200 centimetres (1 m × 2 m){{convert/sandbox|1.2|mi|adj=ri0}}
→ 1 mile (1.9 km) (result has "1 mile" rather than "1 miles")round=0.5
option to round the output to the nearest half, with the display being either N or N.5 where N is an integer (discussed
here):
{{convert/sandbox|7x8x12|ft|abbr=on|round=0.5}}
→ 7 ft × 8 ft × 12 ft (2 m × 2.5 m × 3.5 m) (7 ft rounds to 2 m while 8 ft rounds to 2.5 m}_unit
) is exported and may be used by other modules to access convert's data (discussed
here).sortable=on
is now the same as that produced by {{
ntsh}}.
Module:Val uses the _unit
function which can also produce a span element with a hidden sort key.Module version history 1 (Dec 2013) • 2 (Jan 2014) • 3 (April 2014) • 4 (July 2014) • 5 (Sep 2014) • 6 (Nov 2014) • 7 (Dec 2014) • 8 (Feb 2015) • 9 (Feb 2015) • 10 (May 2015) • 11 (June 2015)
Johnuniq ( talk) 09:43, 10 August 2015 (UTC)
The use of the template to convert mm to in produces 7 mm × 40 mm (0.28 in × 1.57 in). Is there a way to delete the first unit-output, & the spaces, & get 7x40mm (.28x1.57in), instead? It would be very useful in metric ammunition designations. TREKphiler any time you're ready, Uhura 18:41, 21 July 2015 (UTC)
With the multiplication sign, each number should be followed by a unit name or symbol (if appropriate)." Perhaps ask at the talk page of WP:UNIT whether the guideline must apply for the example you mentioned, with links to one or more articles showing the issue. The question for MoS is whether those articles should repeat the unit, or whether an exception should be made due to [insert reason here]. I recently noticed Adrastea which includes "Adrastea has an irregular shape and measures 20×16×14 km across" as an example where WP:UNIT seems excessive. Johnuniq ( talk) 22:32, 21 July 2015 (UTC)
Shouldn't "500 metres (1,600 ft)" (ie, {{convert|500|m|ft}}
) be MORE (*NOT* LESS) than "492 metres (1,614 ft)" (ie, {{convert|492|m|ft}}
? - iac - Enjoy! :)
Drbogdan (
talk)
01:45, 24 August 2015 (UTC)
|0
in the third of the following examples overrides the default to round the output to zero decimal places. The last example shows that a range is handled correctly—that provides a clue to convert that extra precision is wanted.
{{convert|492|m|ft}}
→ 492 metres (1,614 ft){{convert|500|m|ft}}
→ 500 metres (1,600 ft){{convert|500|m|ft|0}}
→ 500 metres (1,640 ft){{convert|492-500|m|ft}}
→ 492–500 metres (1,614–1,640 ft)Is there any way to make this template work along with the {{fraction}} template? -- John ( talk) 20:23, 25 August 2015 (UTC)
{{convert|2+1//2|in|mm|1}}
→ 2+1/2 inches (63.5 mm) or {{convert|2+1/2|in|mm|1}}
→ 2+1⁄2 inches (63.5 mm).{{frac|2|1|2}}
→ 2+1⁄2" which is actually 1=<span class="frac nowrap">2<span class="visualhide"> </span><sup>1</sup>⁄<sub>2</sub></span>
, won't be supported.{{convert|1+7/8|in|mm|1}}
→ 1+7⁄8 inches (47.6 mm) or {{convert|1+3/4|in|mm}}
→ 1+3⁄4 inches (44 mm) would do what you wanted.
Imzadi 1979
→
22:44, 25 August 2015 (UTC)
{{convert|48|mm|in|frac=8}}
→ 48 millimetres (1+7⁄8 in){{convert|44|mm|in|frac=8}}
→ 44 millimetres (1+3⁄4 in) (frac=4 or frac=8 give the same result here)