(bug 235) parser function for conversion of units of measurement.
[[Template:Convert]] on enwiki is a behemoth of a construction that just about manages to do this sort of conversion, taking {{convert|5|mi|km}} and outputting "5 miles (8 km)", etc. To port this to another wiki requires copying over three and a half thousand subtemplates. The additional load produced by including numerous copies of this template is measurable on large pages on enwiki, and it eats voraciously into the template limits.
This revision introduces {{#convert: 5 mi | km }}, outputting "8 km" or thereabouts. See http://www.mediawiki.org/wiki/User:Happy-melon/Convert for more details, or look at the examples in the parser tests.
In a very rough profile, comparing 50 calls to {{convert}} verses the same 50 calls to the wrapper template shown at the link above, the parser function implementation reduces page load time by 72%, preprocessor node count by 83%, post-expand include size by 86% and template argument size by 97%. More detailed profiling would probably reveal places where extra caching could improve performance further.
The primary reason for putting it in ParserFunctions instead of its own extension is availability: PFs are already available across the cluster, and it's accepted as an essential extension for any wiki wishing to emulate or mirror WMF content. One less separate extension installed on the cluster is one less extension which has to be matched by reusers.
It's still missing a lot of units, which I ran out of patience to copy from {{convert}}; I thought I'd get some feedback on the infrastructure first.
2011-01-27 00:13:10 +00:00
|
|
|
!! test
|
|
|
|
|
Simple conversion
|
|
|
|
|
!! input
|
|
|
|
|
{{#convert: 10 m | km }}
|
|
|
|
|
!!result
|
2011-01-29 15:45:07 +00:00
|
|
|
<p>0.01 kilometers
|
(bug 235) parser function for conversion of units of measurement.
[[Template:Convert]] on enwiki is a behemoth of a construction that just about manages to do this sort of conversion, taking {{convert|5|mi|km}} and outputting "5 miles (8 km)", etc. To port this to another wiki requires copying over three and a half thousand subtemplates. The additional load produced by including numerous copies of this template is measurable on large pages on enwiki, and it eats voraciously into the template limits.
This revision introduces {{#convert: 5 mi | km }}, outputting "8 km" or thereabouts. See http://www.mediawiki.org/wiki/User:Happy-melon/Convert for more details, or look at the examples in the parser tests.
In a very rough profile, comparing 50 calls to {{convert}} verses the same 50 calls to the wrapper template shown at the link above, the parser function implementation reduces page load time by 72%, preprocessor node count by 83%, post-expand include size by 86% and template argument size by 97%. More detailed profiling would probably reveal places where extra caching could improve performance further.
The primary reason for putting it in ParserFunctions instead of its own extension is availability: PFs are already available across the cluster, and it's accepted as an essential extension for any wiki wishing to emulate or mirror WMF content. One less separate extension installed on the cluster is one less extension which has to be matched by reusers.
It's still missing a lot of units, which I ran out of patience to copy from {{convert}}; I thought I'd get some feedback on the infrastructure first.
2011-01-27 00:13:10 +00:00
|
|
|
</p>
|
|
|
|
|
!! end
|
|
|
|
|
|
|
|
|
|
!! test
|
|
|
|
|
Position and formatting of numbers and units
|
|
|
|
|
!! input
|
|
|
|
|
*{{#convert: 10 m | km }}
|
|
|
|
|
*{{#convert: 10m | km }}
|
|
|
|
|
*{{#convert: 10 km | m }}
|
|
|
|
|
*{{#convert: 10-km | m }}
|
|
|
|
|
*{{#convert: 10E2 km | m }}
|
|
|
|
|
*{{#convert: 10E-2 km | m }}
|
|
|
|
|
*{{#convert: 10.0E2 km | m }}
|
|
|
|
|
*{{#convert: 10.0E2.5 km | m }}
|
|
|
|
|
!! result
|
2011-01-29 15:59:17 +00:00
|
|
|
<ul><li>0.01 kilometers
|
|
|
|
|
</li><li>0.01kilometers
|
2011-01-29 15:45:07 +00:00
|
|
|
</li><li>10,000 meters
|
2011-01-29 15:59:17 +00:00
|
|
|
</li><li>10,000-meters
|
2011-01-29 15:45:07 +00:00
|
|
|
</li><li>1,000,000 meters
|
|
|
|
|
</li><li>100 meters
|
|
|
|
|
</li><li>1,000,000 meters
|
|
|
|
|
</li><li>1,000,000.5,000 meters
|
(bug 235) parser function for conversion of units of measurement.
[[Template:Convert]] on enwiki is a behemoth of a construction that just about manages to do this sort of conversion, taking {{convert|5|mi|km}} and outputting "5 miles (8 km)", etc. To port this to another wiki requires copying over three and a half thousand subtemplates. The additional load produced by including numerous copies of this template is measurable on large pages on enwiki, and it eats voraciously into the template limits.
This revision introduces {{#convert: 5 mi | km }}, outputting "8 km" or thereabouts. See http://www.mediawiki.org/wiki/User:Happy-melon/Convert for more details, or look at the examples in the parser tests.
In a very rough profile, comparing 50 calls to {{convert}} verses the same 50 calls to the wrapper template shown at the link above, the parser function implementation reduces page load time by 72%, preprocessor node count by 83%, post-expand include size by 86% and template argument size by 97%. More detailed profiling would probably reveal places where extra caching could improve performance further.
The primary reason for putting it in ParserFunctions instead of its own extension is availability: PFs are already available across the cluster, and it's accepted as an essential extension for any wiki wishing to emulate or mirror WMF content. One less separate extension installed on the cluster is one less extension which has to be matched by reusers.
It's still missing a lot of units, which I ran out of patience to copy from {{convert}}; I thought I'd get some feedback on the infrastructure first.
2011-01-27 00:13:10 +00:00
|
|
|
</li></ul>
|
|
|
|
|
|
|
|
|
|
!! end
|
|
|
|
|
|
|
|
|
|
!! test
|
|
|
|
|
Precision 1
|
|
|
|
|
!! input
|
|
|
|
|
*{{#convert: 10 m | km }}
|
|
|
|
|
*{{#convert: 11 m | km }}
|
|
|
|
|
*{{#convert: 12 m | km }}
|
|
|
|
|
*{{#convert: 13 m | km }}
|
|
|
|
|
*{{#convert: 14 m | km }}
|
|
|
|
|
*{{#convert: 15 m | km }}
|
|
|
|
|
*{{#convert: 16 m | km }}
|
|
|
|
|
*{{#convert: 17 m | km }}
|
|
|
|
|
*{{#convert: 18 m | km }}
|
|
|
|
|
*{{#convert: 19 m | km }}
|
|
|
|
|
*{{#convert: 20 m | km }}
|
|
|
|
|
!! result
|
2011-01-29 15:45:07 +00:00
|
|
|
<ul><li>0.01 kilometers
|
|
|
|
|
</li><li>0.011 kilometers
|
|
|
|
|
</li><li>0.012 kilometers
|
|
|
|
|
</li><li>0.013 kilometers
|
|
|
|
|
</li><li>0.014 kilometers
|
|
|
|
|
</li><li>0.015 kilometers
|
|
|
|
|
</li><li>0.016 kilometers
|
|
|
|
|
</li><li>0.017 kilometers
|
|
|
|
|
</li><li>0.018 kilometers
|
|
|
|
|
</li><li>0.019 kilometers
|
|
|
|
|
</li><li>0.02 kilometers
|
(bug 235) parser function for conversion of units of measurement.
[[Template:Convert]] on enwiki is a behemoth of a construction that just about manages to do this sort of conversion, taking {{convert|5|mi|km}} and outputting "5 miles (8 km)", etc. To port this to another wiki requires copying over three and a half thousand subtemplates. The additional load produced by including numerous copies of this template is measurable on large pages on enwiki, and it eats voraciously into the template limits.
This revision introduces {{#convert: 5 mi | km }}, outputting "8 km" or thereabouts. See http://www.mediawiki.org/wiki/User:Happy-melon/Convert for more details, or look at the examples in the parser tests.
In a very rough profile, comparing 50 calls to {{convert}} verses the same 50 calls to the wrapper template shown at the link above, the parser function implementation reduces page load time by 72%, preprocessor node count by 83%, post-expand include size by 86% and template argument size by 97%. More detailed profiling would probably reveal places where extra caching could improve performance further.
The primary reason for putting it in ParserFunctions instead of its own extension is availability: PFs are already available across the cluster, and it's accepted as an essential extension for any wiki wishing to emulate or mirror WMF content. One less separate extension installed on the cluster is one less extension which has to be matched by reusers.
It's still missing a lot of units, which I ran out of patience to copy from {{convert}}; I thought I'd get some feedback on the infrastructure first.
2011-01-27 00:13:10 +00:00
|
|
|
</li></ul>
|
|
|
|
|
|
|
|
|
|
!! end
|
|
|
|
|
|
|
|
|
|
!! test
|
|
|
|
|
Precision 2
|
|
|
|
|
!! input
|
|
|
|
|
*{{#convert: 10.0 m | km }}
|
|
|
|
|
*{{#convert: 10.1 m | km }}
|
|
|
|
|
*{{#convert: 10.2 m | km }}
|
|
|
|
|
*{{#convert: 10.3 m | km }}
|
|
|
|
|
*{{#convert: 10.4 m | km }}
|
|
|
|
|
*{{#convert: 10.5 m | km }}
|
|
|
|
|
*{{#convert: 10.6 m | km }}
|
|
|
|
|
*{{#convert: 10.7 m | km }}
|
|
|
|
|
!! result
|
2011-01-29 15:45:07 +00:00
|
|
|
<ul><li>0.0100 kilometers
|
|
|
|
|
</li><li>0.0101 kilometers
|
|
|
|
|
</li><li>0.0102 kilometers
|
|
|
|
|
</li><li>0.0103 kilometers
|
|
|
|
|
</li><li>0.0104 kilometers
|
|
|
|
|
</li><li>0.0105 kilometers
|
|
|
|
|
</li><li>0.0106 kilometers
|
|
|
|
|
</li><li>0.0107 kilometers
|
(bug 235) parser function for conversion of units of measurement.
[[Template:Convert]] on enwiki is a behemoth of a construction that just about manages to do this sort of conversion, taking {{convert|5|mi|km}} and outputting "5 miles (8 km)", etc. To port this to another wiki requires copying over three and a half thousand subtemplates. The additional load produced by including numerous copies of this template is measurable on large pages on enwiki, and it eats voraciously into the template limits.
This revision introduces {{#convert: 5 mi | km }}, outputting "8 km" or thereabouts. See http://www.mediawiki.org/wiki/User:Happy-melon/Convert for more details, or look at the examples in the parser tests.
In a very rough profile, comparing 50 calls to {{convert}} verses the same 50 calls to the wrapper template shown at the link above, the parser function implementation reduces page load time by 72%, preprocessor node count by 83%, post-expand include size by 86% and template argument size by 97%. More detailed profiling would probably reveal places where extra caching could improve performance further.
The primary reason for putting it in ParserFunctions instead of its own extension is availability: PFs are already available across the cluster, and it's accepted as an essential extension for any wiki wishing to emulate or mirror WMF content. One less separate extension installed on the cluster is one less extension which has to be matched by reusers.
It's still missing a lot of units, which I ran out of patience to copy from {{convert}}; I thought I'd get some feedback on the infrastructure first.
2011-01-27 00:13:10 +00:00
|
|
|
</li></ul>
|
|
|
|
|
|
|
|
|
|
!! end
|
|
|
|
|
|
|
|
|
|
!! test
|
|
|
|
|
String interpolation
|
|
|
|
|
!! input
|
|
|
|
|
{{#convert: 25, 26, 27, 28, 29, and 30 km }}
|
|
|
|
|
!! result
|
2011-01-29 15:45:07 +00:00
|
|
|
<p>25,000, 26,000, 27,000, 28,000, 29,000, and 30,000 meters
|
(bug 235) parser function for conversion of units of measurement.
[[Template:Convert]] on enwiki is a behemoth of a construction that just about manages to do this sort of conversion, taking {{convert|5|mi|km}} and outputting "5 miles (8 km)", etc. To port this to another wiki requires copying over three and a half thousand subtemplates. The additional load produced by including numerous copies of this template is measurable on large pages on enwiki, and it eats voraciously into the template limits.
This revision introduces {{#convert: 5 mi | km }}, outputting "8 km" or thereabouts. See http://www.mediawiki.org/wiki/User:Happy-melon/Convert for more details, or look at the examples in the parser tests.
In a very rough profile, comparing 50 calls to {{convert}} verses the same 50 calls to the wrapper template shown at the link above, the parser function implementation reduces page load time by 72%, preprocessor node count by 83%, post-expand include size by 86% and template argument size by 97%. More detailed profiling would probably reveal places where extra caching could improve performance further.
The primary reason for putting it in ParserFunctions instead of its own extension is availability: PFs are already available across the cluster, and it's accepted as an essential extension for any wiki wishing to emulate or mirror WMF content. One less separate extension installed on the cluster is one less extension which has to be matched by reusers.
It's still missing a lot of units, which I ran out of patience to copy from {{convert}}; I thought I'd get some feedback on the infrastructure first.
2011-01-27 00:13:10 +00:00
|
|
|
</p>
|
|
|
|
|
!! end
|
|
|
|
|
|
|
|
|
|
!! test
|
|
|
|
|
Precision 3
|
|
|
|
|
!! input
|
|
|
|
|
{{#convert: 25, 26, 27, 28, 29, and 30 miles }}
|
|
|
|
|
!! result
|
2011-01-29 15:45:07 +00:00
|
|
|
<p>40,000, 42,000, 43,000, 45,000, 47,000, and 50,000 meters
|
(bug 235) parser function for conversion of units of measurement.
[[Template:Convert]] on enwiki is a behemoth of a construction that just about manages to do this sort of conversion, taking {{convert|5|mi|km}} and outputting "5 miles (8 km)", etc. To port this to another wiki requires copying over three and a half thousand subtemplates. The additional load produced by including numerous copies of this template is measurable on large pages on enwiki, and it eats voraciously into the template limits.
This revision introduces {{#convert: 5 mi | km }}, outputting "8 km" or thereabouts. See http://www.mediawiki.org/wiki/User:Happy-melon/Convert for more details, or look at the examples in the parser tests.
In a very rough profile, comparing 50 calls to {{convert}} verses the same 50 calls to the wrapper template shown at the link above, the parser function implementation reduces page load time by 72%, preprocessor node count by 83%, post-expand include size by 86% and template argument size by 97%. More detailed profiling would probably reveal places where extra caching could improve performance further.
The primary reason for putting it in ParserFunctions instead of its own extension is availability: PFs are already available across the cluster, and it's accepted as an essential extension for any wiki wishing to emulate or mirror WMF content. One less separate extension installed on the cluster is one less extension which has to be matched by reusers.
It's still missing a lot of units, which I ran out of patience to copy from {{convert}}; I thought I'd get some feedback on the infrastructure first.
2011-01-27 00:13:10 +00:00
|
|
|
</p>
|
|
|
|
|
!! end
|
|
|
|
|
|
|
|
|
|
!! test
|
|
|
|
|
Precision 4
|
|
|
|
|
!! input
|
|
|
|
|
{{#convert:35000, 35E3, 35.0E3, 350E2, 3.500E4, 35000E0, 350000E-1 m | km }}
|
|
|
|
|
!! result
|
2011-01-29 15:45:07 +00:00
|
|
|
<p>35, 35, 35.0, 35, 35.00, 35, 35 kilometers
|
(bug 235) parser function for conversion of units of measurement.
[[Template:Convert]] on enwiki is a behemoth of a construction that just about manages to do this sort of conversion, taking {{convert|5|mi|km}} and outputting "5 miles (8 km)", etc. To port this to another wiki requires copying over three and a half thousand subtemplates. The additional load produced by including numerous copies of this template is measurable on large pages on enwiki, and it eats voraciously into the template limits.
This revision introduces {{#convert: 5 mi | km }}, outputting "8 km" or thereabouts. See http://www.mediawiki.org/wiki/User:Happy-melon/Convert for more details, or look at the examples in the parser tests.
In a very rough profile, comparing 50 calls to {{convert}} verses the same 50 calls to the wrapper template shown at the link above, the parser function implementation reduces page load time by 72%, preprocessor node count by 83%, post-expand include size by 86% and template argument size by 97%. More detailed profiling would probably reveal places where extra caching could improve performance further.
The primary reason for putting it in ParserFunctions instead of its own extension is availability: PFs are already available across the cluster, and it's accepted as an essential extension for any wiki wishing to emulate or mirror WMF content. One less separate extension installed on the cluster is one less extension which has to be matched by reusers.
It's still missing a lot of units, which I ran out of patience to copy from {{convert}}; I thought I'd get some feedback on the infrastructure first.
2011-01-27 00:13:10 +00:00
|
|
|
</p>
|
|
|
|
|
!! end
|
|
|
|
|
|
|
|
|
|
!! test
|
|
|
|
|
#sourceunit
|
|
|
|
|
!!input
|
|
|
|
|
*{{#convert: 25 | #sourceunit = km }}
|
|
|
|
|
*{{#convert: 25 | #sourceunit=km }}
|
|
|
|
|
*{{#convert: 25 | #sourceunit = km | #sourceunit = mm }}
|
|
|
|
|
*{{#convert: 25 | #sourceunit = km | cm }}
|
|
|
|
|
!! result
|
2011-01-29 15:45:07 +00:00
|
|
|
<ul><li>25,000 meters
|
|
|
|
|
</li><li>25,000 meters
|
|
|
|
|
</li><li>0.025 meters
|
|
|
|
|
</li><li>2,500,000 centimeters
|
(bug 235) parser function for conversion of units of measurement.
[[Template:Convert]] on enwiki is a behemoth of a construction that just about manages to do this sort of conversion, taking {{convert|5|mi|km}} and outputting "5 miles (8 km)", etc. To port this to another wiki requires copying over three and a half thousand subtemplates. The additional load produced by including numerous copies of this template is measurable on large pages on enwiki, and it eats voraciously into the template limits.
This revision introduces {{#convert: 5 mi | km }}, outputting "8 km" or thereabouts. See http://www.mediawiki.org/wiki/User:Happy-melon/Convert for more details, or look at the examples in the parser tests.
In a very rough profile, comparing 50 calls to {{convert}} verses the same 50 calls to the wrapper template shown at the link above, the parser function implementation reduces page load time by 72%, preprocessor node count by 83%, post-expand include size by 86% and template argument size by 97%. More detailed profiling would probably reveal places where extra caching could improve performance further.
The primary reason for putting it in ParserFunctions instead of its own extension is availability: PFs are already available across the cluster, and it's accepted as an essential extension for any wiki wishing to emulate or mirror WMF content. One less separate extension installed on the cluster is one less extension which has to be matched by reusers.
It's still missing a lot of units, which I ran out of patience to copy from {{convert}}; I thought I'd get some feedback on the infrastructure first.
2011-01-27 00:13:10 +00:00
|
|
|
</li></ul>
|
|
|
|
|
|
|
|
|
|
!! end
|
|
|
|
|
|
|
|
|
|
!! test
|
|
|
|
|
Precision overrides
|
|
|
|
|
!!input
|
|
|
|
|
*{{#convert: 1 mi | #dp = 0 }}
|
|
|
|
|
*{{#convert: 1 mi | #dp=1 }}
|
|
|
|
|
*{{#convert: 1 mi | #dp = -2 }}
|
|
|
|
|
*{{#convert: 1 mi | #dp = 5 }}
|
|
|
|
|
*{{#convert: 1 mi | #dp = -8 }}
|
|
|
|
|
*{{#convert: 1 mi | #sf = 0 }}
|
|
|
|
|
*{{#convert: 1 mi | #sf=1 }}
|
|
|
|
|
*{{#convert: 1 mi | #sf = 3 }}
|
|
|
|
|
*{{#convert: 1 mi | #sf = 5 }}
|
|
|
|
|
*{{#convert: 1 mi | #sf = -8 }}
|
|
|
|
|
!! result
|
2011-01-29 15:45:07 +00:00
|
|
|
<ul><li>1,609 meters
|
|
|
|
|
</li><li>1,609.3 meters
|
|
|
|
|
</li><li>1,600 meters
|
|
|
|
|
</li><li>1,609.344 meters
|
|
|
|
|
</li><li>0 meters
|
|
|
|
|
</li><li>2,000 meters
|
|
|
|
|
</li><li>2,000 meters
|
|
|
|
|
</li><li>1,610 meters
|
|
|
|
|
</li><li>1,609.3 meters
|
|
|
|
|
</li><li>2,000 meters
|
(bug 235) parser function for conversion of units of measurement.
[[Template:Convert]] on enwiki is a behemoth of a construction that just about manages to do this sort of conversion, taking {{convert|5|mi|km}} and outputting "5 miles (8 km)", etc. To port this to another wiki requires copying over three and a half thousand subtemplates. The additional load produced by including numerous copies of this template is measurable on large pages on enwiki, and it eats voraciously into the template limits.
This revision introduces {{#convert: 5 mi | km }}, outputting "8 km" or thereabouts. See http://www.mediawiki.org/wiki/User:Happy-melon/Convert for more details, or look at the examples in the parser tests.
In a very rough profile, comparing 50 calls to {{convert}} verses the same 50 calls to the wrapper template shown at the link above, the parser function implementation reduces page load time by 72%, preprocessor node count by 83%, post-expand include size by 86% and template argument size by 97%. More detailed profiling would probably reveal places where extra caching could improve performance further.
The primary reason for putting it in ParserFunctions instead of its own extension is availability: PFs are already available across the cluster, and it's accepted as an essential extension for any wiki wishing to emulate or mirror WMF content. One less separate extension installed on the cluster is one less extension which has to be matched by reusers.
It's still missing a lot of units, which I ran out of patience to copy from {{convert}}; I thought I'd get some feedback on the infrastructure first.
2011-01-27 00:13:10 +00:00
|
|
|
</li></ul>
|
|
|
|
|
|
|
|
|
|
!! end
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
!! test
|
|
|
|
|
Errors
|
|
|
|
|
!! input
|
|
|
|
|
*{{#convert: 25 | km }}
|
|
|
|
|
*{{#convert: 25 foobars | mi }}
|
|
|
|
|
*{{#convert: 25 mi | #sourceunit = foobar }}
|
|
|
|
|
*{{#convert: 25 km | s }}
|
|
|
|
|
*{{#convert: 25 km/Pa | m/Pa }}
|
|
|
|
|
*{{#convert: 25 km/s/l }}
|
|
|
|
|
*{{#convert: 25 km/m3 }}
|
|
|
|
|
!! result
|
|
|
|
|
<ul><li><strong class="error">Error: no source unit given</strong>
|
|
|
|
|
</li><li><strong class="error">Error: unknown unit "foobars"</strong>
|
|
|
|
|
</li><li><strong class="error">Error: unknown unit "foobar"</strong>
|
|
|
|
|
</li><li><strong class="error">Error: cannot convert between units of "length" and "time"</strong>
|
|
|
|
|
</li><li><strong class="error">Error: invalid compound unit "length/pressure"</strong>
|
|
|
|
|
</li><li><strong class="error">Error: cannot parse double compound units like "km/s/l"</strong>
|
|
|
|
|
</li><li><strong class="error">Error: invalid compound unit "length/volume"</strong>
|
|
|
|
|
</li></ul>
|
|
|
|
|
|
|
|
|
|
!! end
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
!! test
|
|
|
|
|
#sourceunit = #targetunit
|
|
|
|
|
!! input
|
|
|
|
|
*{{#convert: 25 km | #targetunit = #sourceunit }}
|
|
|
|
|
*{{#convert: 25 km | #sourceunit = #targetunit }}
|
|
|
|
|
!! result
|
2011-01-29 15:45:07 +00:00
|
|
|
<ul><li>25 kilometers
|
|
|
|
|
</li><li>25 kilometers
|
|
|
|
|
</li></ul>
|
|
|
|
|
|
|
|
|
|
!! end
|
|
|
|
|
|
|
|
|
|
!! test
|
|
|
|
|
#language
|
|
|
|
|
!! input
|
|
|
|
|
*{{#convert: 10 m | km | #language=en-gb }}
|
|
|
|
|
*{{#convert: 10m | km | #language = en-gb }}
|
|
|
|
|
*{{#convert: 10 km | m |#language=en-gb}}
|
|
|
|
|
*{{#convert: 10 pa | mmhg | #language = en-gb }}
|
|
|
|
|
*{{#convert: 10 pa | mmhg | #language = /../evil/attack }}
|
|
|
|
|
!! result
|
2011-01-29 15:59:17 +00:00
|
|
|
<ul><li>0.01 kilometres
|
|
|
|
|
</li><li>0.01kilometres
|
2011-01-29 15:45:07 +00:00
|
|
|
</li><li>10,000 metres
|
|
|
|
|
</li><li>0.1 milimetres of mercury
|
|
|
|
|
</li><li>0.1 milimeters of mercury
|
(bug 235) parser function for conversion of units of measurement.
[[Template:Convert]] on enwiki is a behemoth of a construction that just about manages to do this sort of conversion, taking {{convert|5|mi|km}} and outputting "5 miles (8 km)", etc. To port this to another wiki requires copying over three and a half thousand subtemplates. The additional load produced by including numerous copies of this template is measurable on large pages on enwiki, and it eats voraciously into the template limits.
This revision introduces {{#convert: 5 mi | km }}, outputting "8 km" or thereabouts. See http://www.mediawiki.org/wiki/User:Happy-melon/Convert for more details, or look at the examples in the parser tests.
In a very rough profile, comparing 50 calls to {{convert}} verses the same 50 calls to the wrapper template shown at the link above, the parser function implementation reduces page load time by 72%, preprocessor node count by 83%, post-expand include size by 86% and template argument size by 97%. More detailed profiling would probably reveal places where extra caching could improve performance further.
The primary reason for putting it in ParserFunctions instead of its own extension is availability: PFs are already available across the cluster, and it's accepted as an essential extension for any wiki wishing to emulate or mirror WMF content. One less separate extension installed on the cluster is one less extension which has to be matched by reusers.
It's still missing a lot of units, which I ran out of patience to copy from {{convert}}; I thought I'd get some feedback on the infrastructure first.
2011-01-27 00:13:10 +00:00
|
|
|
</li></ul>
|
|
|
|
|
|
|
|
|
|
!! end
|