https://wikicars.org/api.php?action=feedcontributions&feedformat=atom&user=HybridBoyWikicars - User contributions [en]2026-05-18T17:04:12ZUser contributionsMediaWiki 1.38.4https://wikicars.org/index.php?title=Baset_trailer&diff=50586Baset trailer2007-04-19T17:42:33Z<p>HybridBoy: </p>
<hr />
<div>A '''baset trailer''' is a range extending device for use with [[battery electric vehicle]]s consisting of a [[battery pack]]. The batteries <ref>I.e.[http://enviromotors.com/wiki/index.php/Sparrow/Batteries "D34M" Optima Blue-Top and Yellow-Top batteries]. </ref>can be [[wikt:replace|replace]]d by recharged ones. Most small to midsized passenger vehicles would require 15 to 20 [[wikipedia:kW|kW]]. Larger vehicles could require 30 kW or more of power depending on how heavy and/or un-aerodynamic they happen to be. <br />
<br />
They can be also used with [[electric bus]]es: bus companies can store recharged batteries in route strategic points ([[wikipedia:bus station|bus station]]s, [[filling station]]s, [[wikipedia:parking lot|parking lot]]s, [[wikipedia:electric utility|electric utility]] facilities, ad-hoc facilities and so on).<br />
<br />
In [[wikipedia:renting|renting]], the maintenance costs of baset trailers can be deferred to the agency.<br />
<br />
==See also==<br />
* [[Epusher trailer]]<br />
* [[Genset trailer]]<br />
* [[Green tuning]]<br />
* [[Pusher trailer]]<br />
* [[Plug-in hybrid]]<br />
* [[Trailer]]<br />
== References ==<br />
<references /><br />
== External links ==<br />
* [http://apple-trailers.com/custom.htm Custom trailers].<br />
<br />
<br />
[[Category:Electric vehicles]]<br />
[[Category:Trailers]]<br />
<br />
{{automotive-tech-stub}}</div>HybridBoyhttps://wikicars.org/index.php?title=Baset_trailer&diff=50585Baset trailer2007-04-19T17:42:13Z<p>HybridBoy: </p>
<hr />
<div>A '''baset trailer''' is a range extending device for use with [[battery electric vehicle]]s consisting of a [[battery pack]]. The batteries <ref>I.e.[http://enviromotors.com/wiki/index.php/Sparrow/Batteries "D34M" Optima Blue-Top and Yellow-Top batteries]. </ref>can be [[wikt:replace|replace]]d by recharged ones. Most small to midsized passenger vehicles would require 15 to 20 [[kW]]. Larger vehicles could require 30 kW or more of power depending on how heavy and/or un-aerodynamic they happen to be. <br />
<br />
They can be also used with [[electric bus]]es: bus companies can store recharged batteries in route strategic points ([[wikipedia:bus station|bus station]]s, [[filling station]]s, [[wikipedia:parking lot|parking lot]]s, [[wikipedia:electric utility|electric utility]] facilities, ad-hoc facilities and so on).<br />
<br />
In [[wikipedia:renting|renting]], the maintenance costs of baset trailers can be deferred to the agency.<br />
<br />
==See also==<br />
* [[Epusher trailer]]<br />
* [[Genset trailer]]<br />
* [[Green tuning]]<br />
* [[Pusher trailer]]<br />
* [[Plug-in hybrid]]<br />
* [[Trailer]]<br />
== References ==<br />
<references /><br />
== External links ==<br />
* [http://apple-trailers.com/custom.htm Custom trailers].<br />
<br />
<br />
[[Category:Electric vehicles]]<br />
[[Category:Trailers]]<br />
<br />
{{automotive-tech-stub}}</div>HybridBoyhttps://wikicars.org/index.php?title=Baset_trailer&diff=50584Baset trailer2007-04-19T17:41:43Z<p>HybridBoy: </p>
<hr />
<div>A '''baset trailer''' is a range extending device for use with [[battery electric vehicle]]s consisting of a [[battery pack]]. The batteries <ref>I.e.[http://enviromotors.com/wiki/index.php/Sparrow/Batteries "D34M" Optima Blue-Top and Yellow-Top batteries]. </ref>can be [[wikt:replace|replace]]d by recharged ones. Most small to midsized passenger vehicles would require 15 to 20 [[kW]]. Larger vehicles could require 30 kW or more of power depending on how heavy and/or un-aerodynamic they happen to be. <br />
<br />
They can be also used with [[electric bus]]es: bus companies can store recharged batteries in route strategic points ([[bus station]]s, [[filling station]]s, [[parking lot]]s, [[electric utility]] facilities, ad-hoc facilities and so on).<br />
<br />
In [[wikipedia:renting|renting]], the maintenance costs of baset trailers can be deferred to the agency.<br />
<br />
==See also==<br />
* [[Epusher trailer]]<br />
* [[Genset trailer]]<br />
* [[Green tuning]]<br />
* [[Pusher trailer]]<br />
* [[Plug-in hybrid]]<br />
* [[Trailer]]<br />
== References ==<br />
<references /><br />
== External links ==<br />
* [http://apple-trailers.com/custom.htm Custom trailers].<br />
<br />
<br />
[[Category:Electric vehicles]]<br />
[[Category:Trailers]]<br />
<br />
{{automotive-tech-stub}}</div>HybridBoyhttps://wikicars.org/index.php?title=Baset_trailer&diff=50583Baset trailer2007-04-19T17:41:20Z<p>HybridBoy: </p>
<hr />
<div>A '''baset trailer''' is a range extending device for use with [[battery electric vehicle]]s consisting of a [[battery pack]]. The batteries <ref>I.e.[http://enviromotors.com/wiki/index.php/Sparrow/Batteries "D34M" Optima Blue-Top and Yellow-Top batteries]. </ref>can be [[wikt:replace|replace]]d by recharged ones. Most small to midsized passenger vehicles would require 15 to 20 [[kW]]. Larger vehicles could require 30 kW or more of power depending on how heavy and/or un-aerodynamic they happen to be. <br />
<br />
They can be also used with [[electric bus]]es: bus companies can store recharged batteries in route strategic points ([[bus station]]s, [[fuel station]]s, [[parking lot]]s, [[electric utility]] facilities, ad-hoc facilities and so on).<br />
<br />
In [[wikipedia:renting|renting]], the maintenance costs of baset trailers can be deferred to the agency.<br />
<br />
==See also==<br />
* [[Epusher trailer]]<br />
* [[Genset trailer]]<br />
* [[Green tuning]]<br />
* [[Pusher trailer]]<br />
* [[Plug-in hybrid]]<br />
* [[Trailer]]<br />
== References ==<br />
<references /><br />
== External links ==<br />
* [http://apple-trailers.com/custom.htm Custom trailers].<br />
<br />
<br />
[[Category:Electric vehicles]]<br />
[[Category:Trailers]]<br />
<br />
{{automotive-tech-stub}}</div>HybridBoyhttps://wikicars.org/index.php?title=Baset_trailer&diff=50582Baset trailer2007-04-19T17:41:00Z<p>HybridBoy: </p>
<hr />
<div>A '''baset trailer''' is a range extending device for use with [[battery electric vehicle]]s consisting of a [[battery pack]]. The batteries <ref>I.e.[http://enviromotors.com/wiki/index.php/Sparrow/Batteries "D34M" Optima Blue-Top and Yellow-Top batteries]. </ref>can be [[wikt:replace|replace]]d by recharged ones. Most small to midsized passenger vehicles would require 15 to 20 [[kW]]. Larger vehicles could require 30 kW or more of power depending on how heavy and/or un-aerodynamic they happen to be. <br />
<br />
They can be also used with [[electric bus]]es: bus companies can store recharged batteries in route strategic points ([[bus station]]s, [[fuel station]]s, [[parking lot]]s, [[electric utility]] facilities, ad-hoc facilities and so on).<br />
<br />
In [[w:renting|renting]], the maintenance costs of baset trailers can be deferred to the agency.<br />
<br />
==See also==<br />
* [[Epusher trailer]]<br />
* [[Genset trailer]]<br />
* [[Green tuning]]<br />
* [[Pusher trailer]]<br />
* [[Plug-in hybrid]]<br />
* [[Trailer]]<br />
== References ==<br />
<references /><br />
== External links ==<br />
* [http://apple-trailers.com/custom.htm Custom trailers].<br />
<br />
<br />
[[Category:Electric vehicles]]<br />
[[Category:Trailers]]<br />
<br />
{{automotive-tech-stub}}</div>HybridBoyhttps://wikicars.org/index.php?title=Baset_trailer&diff=50581Baset trailer2007-04-19T17:40:45Z<p>HybridBoy: </p>
<hr />
<div>{{OR}}<br />
A '''baset trailer''' is a range extending device for use with [[battery electric vehicle]]s consisting of a [[battery pack]]. The batteries <ref>I.e.[http://enviromotors.com/wiki/index.php/Sparrow/Batteries "D34M" Optima Blue-Top and Yellow-Top batteries]. </ref>can be [[wikt:replace|replace]]d by recharged ones. Most small to midsized passenger vehicles would require 15 to 20 [[kW]]. Larger vehicles could require 30 kW or more of power depending on how heavy and/or un-aerodynamic they happen to be. <br />
<br />
They can be also used with [[electric bus]]es: bus companies can store recharged batteries in route strategic points ([[bus station]]s, [[fuel station]]s, [[parking lot]]s, [[electric utility]] facilities, ad-hoc facilities and so on).<br />
<br />
In [[renting]], the maintenance costs of baset trailers can be deferred to the agency.<br />
<br />
==See also==<br />
* [[Epusher trailer]]<br />
* [[Genset trailer]]<br />
* [[Green tuning]]<br />
* [[Pusher trailer]]<br />
* [[Plug-in hybrid]]<br />
* [[Trailer]]<br />
== References ==<br />
<references /><br />
== External links ==<br />
* [http://apple-trailers.com/custom.htm Custom trailers].<br />
<br />
<br />
[[Category:Electric vehicles]]<br />
[[Category:Trailers]]<br />
<br />
{{automotive-tech-stub}}</div>HybridBoyhttps://wikicars.org/index.php?title=Baset_trailer&diff=50525Baset trailer2007-04-19T16:20:32Z<p>HybridBoy: </p>
<hr />
<div>A '''baset trailer''' is a range extending device for use with [[battery electric vehicle]]s consisting of a [[battery pack]] mounted in a [[trailer]]. The trailer with discharget batteries <ref>I.e.[http://enviromotors.com/wiki/index.php/Sparrow/Batteries "D34M" Optima Blue-Top and Yellow-Top batteries]. </ref> can in this way easily by replace by another one with batteries charged.<br />
<br />
Most small to midsized passenger vehicles would require 15 to 20 [[kW]]. Larger vehicles could require 30 kW or more of power depending on how heavy and/or un-aerodynamic they happen to be. <br />
<br />
They can be also used with [[electric bus]]es: bus companies can store recharged batteries in route strategic points ([[bus station]]s, [[fuel station]]s, [[parking lot]]s, [[electric utility]] facilities, ad-hoc facilities and so on).<br />
<br />
==See also==<br />
* [[Camping]]<br />
* [[Epusher trailer]]<br />
* [[Genset trailer]]<br />
* [[Green tuning]]<br />
* [[Pusher trailer]]<br />
* [[Plug-in hybrid]]<br />
* [[Trailer]]<br />
== References ==<br />
<references /><br />
== External links ==<br />
* [http://apple-trailers.com/custom.htm Custom trailers].<br />
<br />
[[Category:Electric vehicles]]<br />
[[Category:Trailers]]<br />
<br />
{{automotive-tech-stub}}</div>HybridBoyhttps://wikicars.org/index.php?title=Baset_trailer&diff=50504Baset trailer2007-04-19T15:56:26Z<p>HybridBoy: </p>
<hr />
<div>A '''baset trailer''' is a range extending device for use with [[battery electric vehicle]]s consisting of a [[battery pack]] mounted in a [[trailer]]. The trailer with discharget batteries <ref>I.e.[http://enviromotors.com/wiki/index.php/Sparrow/Batteries "D34M" Optima Blue-Top and Yellow-Top batteries]. </ref> can in this way easily by replace by another one with batteries charged.<br />
<br />
Most small to midsized passenger vehicles would require 15 to 20 [[kW]]. Larger vehicles could require 30 kW or more of power depending on how heavy and/or un-aerodynamic they happen to be. <br />
<br />
They can be also used with [[electric bus]]es: bus companies can store recharged batteries in route strategic points ([[bus station]]s, [[fuel station]]s, [[parking lot]]s, [[electric utility]] facilities, ad-hoc facilities and so on).<br />
<br />
==See also==<br />
* [[Camping]]<br />
* [[Epusher trailer]]<br />
* [[Genset trailer]]<br />
* [[Green tuning]]<br />
* [[Pusher trailer]]<br />
* [[Plug-in hybrid]]<br />
* [[Trailer]]<br />
== References ==<br />
<references /><br />
<br />
[[Category:Electric vehicles]]<br />
[[Category:Trailers]]<br />
<br />
{{automotive-tech-stub}}</div>HybridBoyhttps://wikicars.org/index.php?title=Baset_trailer&diff=50503Baset trailer2007-04-19T15:54:58Z<p>HybridBoy: </p>
<hr />
<div>A '''baset trailer''' is a range extending device for use with [[battery electric vehicle]]s consisting of a [[battery pack]] mounted in a [[trailer]]. The trailer with discharget batteries <ref>I.e.[http://enviromotors.com/wiki/index.php/Sparrow/Batteries "D34M" Optima Blue-Top and Yellow-Top batteries]. </ref> can in this way easily by replace by another one with batteries charged.<br />
<br />
Most small to midsized passenger vehicles would require 15 to 20 [[kW]]. Larger vehicles could require 30 kW or more of power depending on how heavy and/or un-aerodynamic they happen to be. <br />
<br />
They can be also used with [[electric bus]]es: bus companies can store recharged batteries in route strategic points ([[bus station]]s, [[fuel station]]s, [[parking lot]]s, [[electric utility]] facilities, ad-hoc facilities and so on).<br />
<br />
==See also==<br />
* [[Camping]]<br />
* [[Epusher trailer]]<br />
* [[Genset trailer]]<br />
* [[Green tuning]]<br />
* [[Pusher trailer]]<br />
* [[Plug-in hybrid]]<br />
* [[Trailer]]<br />
== References ==<br />
<references /><br />
<br />
[[Category:Electric vehicles]]<br />
[[Category:Trailers]]<br />
<br />
{{automotive-tech-stub}}<br />
<br />
<br />
{{stub}}</div>HybridBoyhttps://wikicars.org/index.php?title=Plug-in_hybrid&diff=50502Plug-in hybrid2007-04-19T15:54:41Z<p>HybridBoy: </p>
<hr />
<div>A '''plug-in hybrid''' electric vehicle (PHEV) is any vehicle powered by a combination of [[internal combustion engine]] and [[electric motor]] with storage [[Battery (electricity)|batteries]] that can be recharged by connecting the vehicle by plug to an external [[Electricity generation|electrical power source]]. Plug-in hybrids typically have characteristics of both conventional [[Hybrid vehicle|hybrid electric vehicles]] and of [[battery electric vehicle]]s. While PHEVs are usually passenger vehicles, plug-in hybrid technology has been implemented or proposed in delivery vans, trucks, buses, military vehicles, and other medium- to heavy-duty vehicles. <br />
<br />
The cost for electricity to power PHEVs in California is about one fourth the cost of gasoline. If their batteries are charged from [[renewable energy]] such as [[Wind power|wind]] or [[hydropower]], PHEVs use minimal amounts of [[fossil fuel]] for their [[all-electric range]], and may thereby reduce dependence on [[petroleum]] and mitigate [[global warming]] by alleviating the [[greenhouse effect]]. Plug-in hybrids have been identified as having significant potential as alternative fuel vehicles.<ref>Simpson, A. (2006) [http://www.nrel.gov/docs/fy07osti/40485.pdf "Cost-Benefit Analysis of Plug-in Hybrid Electric Vehicle Technology"] National Renewable Energy Laboratory conference report CP-540-40485</ref> <br />
<br />
Plug-in hybrid passenger vehicles are not in mass production as of early 2007, although some manufacturers have indicated that they intend to introduce PHEV production models. Prototypes have been built to demonstrate the technology and to encourage its widespread adaptation. Conversions of production model [[hybrid vehicle]]s may be available from conversion kits and conversion services pending commercial production. Most existing PHEVs are conversions of [[Toyota Prius]] hybrid cars. These prototypes retain the Prius's "idle-off" capability and [[regenerative braking]], among other characteristics, while adding extended electric-only drive capability, and electrical plug charging. <br />
<br />
All-electric range is designated by the form PHEV-(number) representing the number of miles the vehicle can travel on electric power alone. For example, a PHEV-10 can travel ten miles without the use of petroleum gasoline.<br />
<br />
==History==<br />
<br />
In 1969, ''[[Popular Science]]'' did an article on the [[General Motors]] XP-883. This prototype was a commuter car with a plug-in hybrid electric drive system. It housed six 12-volt lead acid batteries in the trunk area and had a transverse mounted DC electric motor mounted to a front-wheel drive trans-axle. The gasoline powered engine was connected to the trans-axle via a worm gear.<ref>Popular Science (July, 1969) [http://www.finkbuilt.com/blog/hybrid-car-ready-in-1969 "Hybrid Car Ready in 1969"] pp. 86-7</ref> The car could be plugged into a standard 110 Volt AC outlet for recharging. Although not very fast or a long-ranged, hybrids were off and rolling.<br />
<br />
In about 1990, Prof. [[Andrew A. Frank|Andy Frank]] of the [[University of California]] at Davis used student teams to begin building operating prototype Plug-in hybrid electric vehicles. His work attracted industry support and funding from [[Nissan]], [[Koyo Seiko]], [[General Motors]], [[Saturn]], [[Ford]], [[Visteon]], [[JATCO]], [[Ovonics]], [[Defense Advanced Research Project Agency]] (DARPA), [[Sacramento Municipal Utility District]], [[Southern California Edison]], U.S. [[Department of Energy]], and others. The UC Davis PHEVs won several DOE/USCAR "Future Car" and "Future Truck" national competitions. In 1994, the [[Esoro H301]] was built in Switzerland.<ref>Esoro (2005) [http://www.esoro.ch/english/content/kernk/nhanst/h301/h.htm "The First Hypercar"] ''www.esoro.ch'' retrieved 2007</ref> Four such prototypes are still on the road.<br />
<br />
By 2000, the [[Electric Power Research Institute]] (EPRI) sponsored the broad-based [[Hybrid Electric Vehicle Alliance]] (HEVA) under the leadership of Bob Graham, to promote and develop Original Equipment Manufacturer commercialization of plug-in hybrid electric vehicles. Alliance members include major automakers, national labs, utilities, and the University of California at Davis. The Hybrid Electric Vehicle Working Group (HEVWG) published its landmark studies and reports on PHEV attractiveness. Dr. Frank received new support from Commission of the European Communities, Southern California Air Quality Management District, Yolo-Solano Air Quality Management District, [[CARB]], and other governmental agencies. In 2001, the U.S. [[Department of Energy]] created the National Center of Hybrid Excellence at UC Davis, with Dr. Frank as Director, and Frank also obtained substantial GM funds to hybridize and plug-in GM's EV1, and EPRI funded Dr. Frank's work. In 2002, entrepreneurs, environmentalists and engineers created the [http://www.calcars.org/ California Cars Initiative], a non-profit PHEV advocacy and technology development group.<br />
<br />
In 2003, Dr. Frank's vehicles are shown at the Paris International Auto Show and demonstrated to about 200 Renault engineers at a corporate event at their Paris headquarters. During the same year, Toyota shipped a University of California Davis Coulomb Plug-in Hybrid Electric Vehicles to Toyota City to demonstrate it to about 250 engineers and executives at two of [[Toyota]]'s primary Tier 1 suppliers, [[Koyo Seiko]], and Aisin AW (Aisin builds the [[Toyota Prius]] transmission system, which also is used in the Ford Escape and Nissan Hybrid). In 2003, [[Renault]] produced the "Elect'Road," a Plug-in Hybrid Electric Vehicle variant of its "Electri'cite" [[Kangoo]] battery electric van (50-80 km range) with a small gasoline "limp-home" engine able to drive 100 km before refueling. Renault discontinued the Elect'Road after selling about 500, mainly in France, Norway and a few in the UK, for about 25,000 euros. By 2004, Dr. Frank's student teams had built and operated seven proof-of-concept and proof-of-demonstration prototype Plug-in Hybrid Electric Vehicles, including 6-passenger sedans (Taurus and Sable), Sport Utility Vehicles (Suburban, Explorer), two-seater sports car (GM EV1), and two ground-up 80 mpg sports cars, and the CalCars PRIUS+ prototype and EDrive Systems conversions were demonstrated. In 2005, DaimlerChrysler Sprinter Van PHEV prototypes were completed.<ref>California Cars Initiative (2005-7) [http://www.calcars.org/history.html "Plug-In Hybrids: State Of Play, History & Players"] (CalCars' PHEV History) accessed 18 April 2007</ref><br />
<br />
===Production models, prototypes, and conversions===<br />
One production PHEV has gone on sale, the [[Renault Kangoo]], in France in 2003. In addition, [[DaimlerChrysler]] is currently building PHEVs based on the [[Mercedes-Benz Sprinter]] [[van]]. Light Trucks are also offered by Micro-Vett SPA<ref>{{cite web | title=Hybrid Daily: Technical Data | work=Micro-Vett | url=http://www.micro-vett.it/english/bimodaleing2.html | accessdate=January 11 | accessyear=2006}}</ref> the so called Daily Bimodale. A number of prototypes have been created. At the [[UC Davis Hybrid Center]], a team led by Prof. [[Andrew A. Frank]] {{cite web | title=(interview) | url=http://www.inoculatedmind.com/?p=81}} have been designing and building working prototypes, the most recent of which is currently being installed into a GM Equinox for the Challenge X competition. {{cite web | title=Team Fate | work=UC-Davis Hybrid Electric Vehicles Group | url=http://www.team-fate.net/ | accessdate=January 11 | accessyear=2006}} Some independent researchers have demonstrated conversions of vehicles such as the [[Toyota Prius]], while leaving the majority of the stock [[Hybrid Synergy Drive]] intact and unchanged by simply adding battery capacity and a grid charger. <br />
<br />
The California Cars Initiative, a non-profit advocacy and technology development group in California, has converted the '04 and newer Toyota Prius to become a prototype of what it calls the PRIUS+. With the addition of 130 kg (300 lb) of [[lead-acid batteries]], the PRIUS+ achieves roughly double the gasoline [[mileage]] of a standard Prius and can make trips of up to 15 km (10 miles) using only electric power.<ref>{{cite web | title=How We Green-Tuned an '04 Prius into a PRIUS+ Plug-In Hybrid!| work=CalCars.com - The California Cars Initiative | url=http://www.priusplus.org | accessdate=January 11 | accessyear=2006}}</ref> It is now working with EDrive Systems, a new Southern California company that plans to install aftermarket conversions for Priuses with a target fuel efficiency of 1.0 L/100 km (230 mpg). <br />
<br />
The [[Electric Power Research Institute]] of Palo Alto, along with a number of utilities and government agencies, is working with DaimlerChrysler to deliver three plug-in hybrids built on the [[Mercedes Sprinter]] platform (a 15-passenger van). The Electric Auto Association is sponsoring the [http://www.eaa-phev.org/wiki/Main_Page EAA-PHEV project], a "Do-It-Yourself" approach to enable those who are comfortable working with high wattage DC systems to do their own [[Electric vehicle conversion|conversion]]. [http://www.hymotion.com Hymotion], a Canadian company, introduced plug-in hybrid upgrade kits in February 2006. Designed for the Toyota Prius and the Ford Escape and Mariner Hybrids, these kits will be offered to fleet buyers at first and should be available to the general public in 2007.<br />
<br />
Press reports on Nov 29, 2006, indicate GM's plans to introduce a production plug-in hybrid version of Saturn's Greenline Vue SUV in 2009<ref>General Motors (11/29/2006) [http://www.webwire.com/ViewPressRel.asp?aId=24308 "GM Announces Intention to Produce Plug-in Hybrid SUV"] ''WebWire'' internet press release</ref> to be a PHEV-10.<ref>Magda, M. (November 29, 2006) [http://www.autobloggreen.com/2006/11/29/la-auto-show-saturn-vue-green-line-will-offer-2-mode-and-plug-i/ "LA Auto Show: Saturn Vue Green Line will offer 2-mode and plug-in hybrid technology"] ''[http://www.autobloggreen.com AutoblogGreen]'' accessed 18 April 2007</ref> Motorcycle and small car manufacturer [[Suzuki]] has produced several prototype light sports cars capable of operation in this mode. The first of these used a 400&nbsp;cc motorcycle engine to give a primarily electric vehicle a "limp home" capability. A subsequent model was more capable of general operation over a wide range of conditions and ranges. PML built prototypes that it claims achieve 80 mpg; 0 to 60mph in 4.5 seconds; top speed of over 150mph; and a range of 1,000 miles.<ref>PML Flightlink Ltd. (August 2006) [http://www.pmlflightlink.com/archive/news_mini.html "MINI QED - A demonstration vehicle"] accessed 18 April 2007</ref><br />
<br />
==Technology==<br />
<br />
A plug-in hybrid may be capable of [[charge-depleting]], [[charge-sustaining]], and [[blended mode]]s of operation. They may drive for an extended range in [[all-electric mode]], either only at low speeds or at all speeds, with the internal combustion engine used secondarily for power-assist, and/or for longer range travel. <br />
<br />
As with hybrid electric vehicles, the two major classifications are series and parallel. In a parallel hybrid the internal combustion engine (ICE) and the electric motor can both contribute to torque at the wheels. Coupling the ICE directly to the drive shaft bypasses inefficiencies associated with having the ICE generate electrical energy for motive power. However, parallel hybrids currently available automatically engage the ICE if the vehicle is driven beyond a particular electric only performance envelope, a matter of some concern with the Prius conversions mentioned below, since these will require conservative driving to avoid starting the ICE. Parallel implementations may use a common drivetrain for the two power sources or may be "road coupled", with different wheel sets operated by the motors.<br />
<br />
In a series hybrid the ICE drives a generator to recharge the batteries and/or provide power to the electric motor, depending upon the load demand. This type is especially attractive to implementation as a plug-in hybrid, since such vehicles will ideally have an electric motor and battery capable of satisfying all performance needs of the vehicle and so will not require use of the ICE until the batteries have been discharged to a substantial level, and not at all if recharged between trips of electric-only range. In one recent (non-production) announcement of the series hybrid [[Chevrolet Volt]],<ref>Abuelsamid, S. (January 7, 2007) [http://www.autobloggreen.com/2007/01/07/detroit-auto-show-its-here-gms-plug-in-hybrid-is-the-chevy-v/ "Detroit Auto Show: It's here. GM's plug-in hybrid is the Chevy Volt Concept"] ''AutoBlogGreen''</ref> a 40% remaining charge has been proposed for at least one vehicle as the start point for the ICE, the number of miles for electric-only operation will depend upon the battery capacity relative to the vehicle drag and weight, in this particular case projected at 40 miles (64km). In such a system the ICE and generator capacity, in concert with vehicle characteristics, will determine the maximum continuous performance without external recharge. Owing to the efficient fixed-speed operation of the relatively small (1 liter displacement) ICE and regenerative energy recovery, substantial economy of operation remains even without external power recharge of the batteries, in this example projected at 50 mpg (4.7 l/100 km).<br />
<br />
===Conversion===<br />
Some early non-production plug-in hybrid electric vehicle [[Electric vehicle conversion|conversions]] have been based on the version of [[Hybrid Synergy Drive]] (HSD) found in the 2004+ model year [[Toyota]] [[Toyota Prius|Prius]]. Early [[Lead-acid battery|Pba]] conversions by [http://www.calcars.org CalCars] demonstrated 10 miles (15 km) of EV-only and 20 miles (30 km) of double mileage mixed-mode range. A company offering conversions to consumers named [http://hybrids-plus.com/ Hybrids Plus] is using [http://www.a123systems.com/ A123] [[Lithium ion polymer battery|Li-ion]] batteries and has 15 or 30 miles of electric range. A company planning to offer conversions to consumers named [http://www.edrivesystems.com EDrive systems] will be using [http://www.valence.com Valence] [[Lithium ion polymer battery|Li-ion]] batteries and have 40-50 miles of electric range. Another company offering a plug-in module for the Toyota Prius is [http://www.hymotion.com Hymotion]. <br />
<br />
All of the above systems replace the original battery and its ECU (Electronic Control Unit), while leaving the existing HSD system unchanged. This technology would be fairly simple to apply to other hybrid configurations. A conversion to plug-in mode involves increasing the capacity of the [[battery pack]] (in some cases the stock [[Nickel metal hydride|NiMH]] battery is retained), and adding an on-board AC powered charger to recharge the larger pack from mains power. Additionally, a method is required to encourage the vehicle to make full use the greater available electrical energy.<br />
<br />
==Advantages==<br />
===Cost savings===<br />
In California, as of 2006, the cost to plug in at night is equivalent to $0.75 per gallon of gasoline,<ref>HEV Center (2007) [http://www.team-fate.net/phev.html "What are Plug-In Hybrids?"] Department of Mechanical and Aeronautical Engineering, UC Davis; retrieved 18 April 2007</ref> where gasoline sells for over $3 per gallon The cost of electricity for a Prius PHEV is about $0.03/mi ($0.019/km), based on 0.262 kilowatt hours per mile and a cost of electricity of $0.10 per kilowatt hour.<ref>California Cars Initiative (April 20, 2006) [http://www.calcars.org/conversions-factsheet.pdf#search=%22Prius%20262%20kWh%20mile%22 "Fact Sheet: PHEV Conversions"] page 2, accessed 18 April 2006</ref><ref>Bluejay, M. (2006?) [http://michaelbluejay.com/electricity/cost.html "How much does electricity cost?"] accessed 18 April 2007</ref> Current PHEV conversions install a higher capacity battery than common hybrids like the Toyota Prius in order to extend the range. This additional cost is offset by fuel operating cost savings because just $1.00 worth of electricity from the wall (at $0.09/kW·h) is sufficient to drive the same distance as a gallon of gasoline. During the year 2007, many government and industry researchers will focus on determining what level of all-electric range is economically optimum for the design.<br />
<br />
===Fuel efficiency===<br />
A 70-mile range HEV-70 may annually require only about 25% as much gasoline as a similarly designed HEV-0, depending on how it will be driven and the trips for which will be used. A further advantage of PHEVs is that they have potential to be even more efficient than their HEV-0 cousins because more limited use of the PHEV's internal combustion engines may allow the engine to be used at closer to its maximum efficiency. While a Prius is likely to convert fuel to motive energy on average at about 30% efficiency (well below the engine's 38% peak efficiency) the engine of a PHEV-70 would likely operate far more often near its peak efficiency because it is not needed during transient operation conditions. These architectures would be highly likely to employ a parallel hybrid configuration whereby mechanical engine power is allowed to transfer most efficiently directly to the wheels (when the engine is activated).<br />
<br />
===Electricity infrastructure===<br />
PHEV and fully electric cars may allow for more efficient use of existing electric production capacity, much of which sits idle as operating reserve most of the time. This assumes that vehicles are charged primarily during off-peak periods (i.e., at night), or equipped with technology to shut off charging during periods of peak demand. Another advantage of a gridable vehicle is their potential ability to load balance or help the grid during peak loads. By using excess battery capacity to send power back into the grid and then recharge during [[off peak]] using cheaper power such vehicles are actually advantageous to utilities as well as their owners. This is accomplished with what is known as V2G or [[Vehicle to Grid]] technology. <br />
<br />
Even if such vehicles just led to an increase in the use of night time electricity they would even out electricity demand (which is typically higher in the day time) and provide a greater return on capital for electricity infrastructure. [[Pacific Gas and Electric]] has shown PHEVs suggesting that they could be used as a source of emergency home power in the event of an electrical power failure. Regulations intended to protect electricians against power other than from grid sources would need to be changed, or regulations requiring consumers to disconnect from the grid when connected to non-grid sources will be required before such backup power solutions would be feasible.{{Fact|date=April 2007}}<br />
<br />
===Carbon emissions===<br />
Yet another advantage of PHEVs is a predicted reduction in [[carbon emissions]] should PHEV use become widespread. Increased drivetrain efficiency results in significant reduction of greenhouse gas emissions, even taking into account energy lost to inefficiency in the production and distribution of grid power and charging of batteries. A study by the American Council for an Energy Efficient Economy (ACEEE) predicts that, on average, a typical American driver is expected to achieve about a 15% reduction in net [[Carbon dioxide|CO<sub>2</sub>]] emissions compared to a regular hybrid, based on the 2005 distribution of power sources feeding the US electrical grid. <br />
<br />
Additionally, for PHEV’s recharged in areas where the grid is fed by power sources with lower CO<sub>2</sub> emissions than the current average, net CO<sub>2</sub> emissions associated with PHEVs will decrease correspondingly. The same study predicts that in areas where more than 80% of grid-power comes from coal-burning power plants, local net CO<sub>2</sub> emissions will increase.<ref>Kliesch, J. and Langer, T. (September 2006) [http://www.aceee.org/store/proddetail.cfm?CFID=1941952&CFTOKEN=35186425&ItemID=418&CategoryID=7 "Plug-In Hybrids: an Environmental and Economic Performance Outlook"] American Council for an Energy-Efficient Economy</ref> However, given the global nature of problems associated with CO<sub>2</sub> emissions, specifically those related to [[Global Warming|global warming]], localized increases in CO<sub>2</sub> emissions are not considered a significant problem if global CO<sub>2</sub> emissions are decreased.<br />
<br />
==Disadvantages==<br />
Disadvantages include the additional weight and cost of a larger battery pack. The cost of a battery pack is especially relevant because with current technology battery packs may need to be replaced before the car itself is replaced.{{Fact|date=April 2007}} The fuel economy increase for a PHEV are highly dependent upon the way a vehicle is used (its [[duty cycle]]) and the opportunities to recharge by connecting to the electrical grid. In the most extreme of circumstances a PHEV might get worse mileage than an HEV. For example, in vehicles being used continuously without opportunities for recharging by connecting to the electrical grid the larger battery capacity (as compared to an HEV) might lack any advantage, while the greater battery weight (than in a corresponding HEV) would reduce fuel economy.<br />
<br />
The study by the ACEEE also predicts that widespread PHEV use in heavily coal-dependent areas would result in an increase in local net sulfur dioxide and mercury emissions, given emissions levels from most coal plants currently supplying power to the grid.<ref>Clayton, M. (September 25, 2006) [http://www.csmonitor.com/2006/0925/p03s02-usgn.html "A reality check on plug-in hybrids"] ''The Christian Science Monitor''</ref><ref>Kanellos, M. (April 28, 2006) [http://news.com.com/Plug+in+your+hybrid,+pollute+less/2100-11389_3-6066360.html "Plug in your hybrid, pollute less?"] ''cNet News.com''</ref> Although "[[clean coal]]" technologies could create power plants which supply grid power from coal without emitting significant amounts of such pollutants, the higher cost of the application of these technologies may increase the price of coal-generated electricity dramatically. There is debate about whether or not PHEV or electric vehicle technology reduces pollution or simply "shifts" the pollution to another physical location. The net effect on pollution is dependent on the fuel source of the electrical grid (fossil or renewable, for example) and the pollution profile of the powerplants themselves. Identifying, regulating and upgrading "single point" pollution source such as a powerplant -- or replacing a plant altogether -- may also be more practical. From a human health perspective, "shifting" pollution away from large urban areas may be considered a significant advantage.<br />
<br />
==Commercialization==<br />
[[Image:New Vehicle Purchase Preference.gif|right|thumb|300px|The number of US survey respondents willing to pay $4,000 more for a plug-in hybrid car increased from 17% in 2005 to 26% in 2006.]]<br />
<br />
While PHEV concepts and research have been neglected for many years by industry and government, interest increased in 2006 to such a level that the architecture was included as an area of research in President George W. Bush's advanced energy initiative. The "addiction to oil" mentioned in his [[2006 State of the Union Address]] could be largely eliminated by PHEVs and this fact is the most dramatic advantage of the architecture.<br />
<br />
===Batteries===<br />
PHEVs involve frequent battery charging and discharging cycles. Because the number of such cycles influences battery lifetime, battery life may be less than in HEVs which don't fully discharge. However, some authors argue that PHEVs will soon become standard in the automobile industry.<ref>Roim, J. and Frank, A. (April 2006) [http://faculty.dbcc.edu/tulsian/interestingReading/energy/Hybrid_vehicles.pdf "Hybrid Vehicles Gain Traction"] ''Scientific American'' pp. 72-9</ref> Design issues and trade-offs concerning battery life, capacity, heat dissipation, weight, costs, and safety need to be solved.<ref>Bullis, K. (August 3, 2006) [http://www.technologyreview.com/read_article.aspx?id=17250&ch=biztech&sc=&pg=1 "Are Lithium-Ion Electric Cars Safe?"] ''Technology Review'' (Cambridge, Mass.: MIT)</ref><br />
<br />
Advanced battery technology is under development.<ref>Fleissner, C. (8/14/06) [http://wistechnology.com/article.php?id=3228 "Johnson Controls partnership wins new contract"] ''Wisconsin Technology Network''</ref><ref>Lithium Technology Corp. (August 15, 2006) [http://www.prnewswire.com/cgi-bin/stories.pl?ACCT=104&STORY=/www/story/08-15-2006/0004416273&EDATE= "Lithium Technology Corporation to Develop Highest Power and Highest-Energy Lithium-Ion Battery Solutions"] ''PR Newswire'' press release</ref><ref>MIT News Service (August 10, 2006) [http://renewableenergyaccess.com/rea/news/story?id=45679 "Researchers Fired Up over New Battery" ''RenewableEnergyAccess.com'']</ref> Battery life expectancy is expected to increase.<ref>Altair Nanotechnologies Inc. (September 7, 2006) [http://www.marketwire.com/mw/release_html_b1?release_id=160603 "Altair Nanotechnologies Details Long Life Features of Its Nano-Titanate Battery"] ''MarketWire'' press release</ref> For [[Lithium ion battery|lithium-ion (Li-ion) batteries]], Toyota has reported a heat dissipation issue.<ref>Flint, J. (05.30.06) [http://www.forbes.com/2006/05/26/toyota-prius-hybrid-cx_jf_0530flint.html "The Frankenstein Hybrid"] ''Forbes.com''</ref> The next major update to the Toyota Prius, is said to use Li-ion batteries,<ref>Garcia, D. (May 10, 2006) [http://vtec.net/news/news-item?news_item_id=553701 "Japanese mag update"] ''VTEC.com''</ref> and have a 15 km (9 mile) electric only range,<ref>Gow, D. (March 31, 2006) [http://www.guardian.co.uk/japan/story/0,,1743808,00.html "Ten years down the road: car giant foresees the non-polluting, accident-proof saloon"] ''The Guardian''</ref> which according to the 2000 U.S. Census is enough to power the entire daily commute of 29% of U.S. workers.<ref>US Bureau of the Census (March 2004) [http://www.census.gov/prod/2004pubs/c2kbr-33.pdf "Journey to Work: 2000"] ''Census 2000 Brief''</ref><br />
<br />
===Patent protection on NiMH batteries===<br />
The oil company Chevron invests in key battery technologies and battery manufacturing facilities, through its subsidiary, [http://www.cobasys.com/solutions/technology.htm Cobasys]. According to the website [http://ev1.org ev1.org], during the development of the [[Battery electric vehicle|battery-electric vehicle (BEV)]] [[EV1]], General Motors made a controlling investment in Ovonics's battery development and manufacturing, with particular interest in the patents and trade secrets controlling the manufacturing of large [[Nickel metal hydride battery|nickel-metal hydride (NiMH) batteries]]. This interest was subsequently sold to the oil company Texaco, which was acquired in its entirety by another oil company, Chevron. The book "[http://www.newsociety.com/bookid/3934| Plug-In Hybrids, The Cars That Will Recharge America]" presents the argument that large-format NiMH batteries are commercially viable and ready for mass production, but that Chevron and other oil-related interests are suppressing this technology to forestall the introduction of plug-in hybrids. However, in December, 2006 General Motors announced that they will be using Cobasys NiMH batteries in the upcoming Saturn Aura hybrid model.<ref>Abuelsamid, S. (Dec 5th 2006) [http://www.autobloggreen.com/2006/12/05/cobasys-providing-nimh-batteries-for-saturn-aura-hybrid/ "Cobasys providing NiMH batteries for Saturn Aura hybrid"] ''AutoblogGreen''</ref><br />
<br />
==References==<br />
<div class="references-small" style="-moz-column-count:2; column-count:2;"><br />
{{reflist}}<br />
</div><br />
<br />
==See also==<br />
<br />
;General: [[Future of the car]], [[Petroleum electric hybrid vehicle]], [[Blended mode]], [[The Hype about Hydrogen]], [[Hydrogen vehicle]], [[Future energy development]], [[Mitigation of global warming]], [[Hypermiler]], [[Automotive design terminology]], [[Alternative fuel]], [[Partial zero-emissions vehicle]]<br />
<br />
;Components: [[Lithium-ion battery]], [[Nickel metal hydride battery]], [[Plug in]], [[Hybrid Synergy Drive]], [[Ecodriving]], [[Green tuning]]<br />
<br />
;Car types: [[List of hybrid vehicles]], [[Ford Airstream]], [[Mercedes-Benz Sprinter]], [[Toyota Prius]], [[Saturn VUE]], [[Chevrolet Volt]]<br />
<br />
;[[Transport]]ation: [[Automobile]], [[Bicycle]], [[Public transport]], [[Trolleybus]], [[Air car]], [[Hydrogen vehicle]], [[Bus rapid transit]], [[Flexible-fuel vehicle]], [[Low-energy vehicle]]<br />
<br />
; [[Electric Vehicle]]: [[Battery electric vehicle]] ([[State of charge]], [[All-electric range]], [[Charge-depleting]], and [[Charge-sustaining]]), [[Production battery electric vehicle]], [[Hybrid vehicle drivetrains]], [[Vehicle propulsion]], [[Who Killed the Electric Car?]], [[Plug In America]]<br />
<br />
;Trailers: [[Genset trailer]], [[Pusher trailer]]<br />
<br />
==External links==<br />
===News===<br />
<div style="-moz-column-count:2; column-count:2;"><br />
<br />
*[http://news.com.com/PGE+sees+plug-in+hybrids+as+potential+profit+centers/2100-11392_3-6174672.html PG&E sees plug-in hybrids as potential profit centers] -- News.com, April 9, 2007<br />
**[http://cbs5.com/local/local_story_099151602.html PG&E Unveils Hybrid Car That Can Power Your House] -- CBS5.com, April 9, 2007 <br />
* [http://www.reuters.com/article/businessNews/idUSN0223226920070302 Toyota developing plug-in hybrid, researching market] -- Reuters, March 2, 2007<br />
* [http://www.spectrum.ieee.org/jan07/4848 GM Announces Chevrolet Volt series hybrid concept vehicle] IEEE 2007-01-07, [http://link.brightcove.com/services/player/bcpid416542521 6 minute video]<br />
* [http://www.webwire.com/ViewPressRel.asp?aId=24308 Saturn VUE plug-in hybrid in 2009] - webwire 11/29/06, [http://www.autobloggreen.com/2006/11/29/la-auto-show-saturn-vue-green-line-will-offer-2-mode-and-plug-i/ 10 mile range] AutoblogGreen 11/29/06<br />
* [http://www.csmonitor.com/2006/0925/p03s02-usgn.html A reality check on plug-in hybrids] - Christian Science Monitor, 9/25/2006<br />
* [http://www.synovate.com/current/news/article/2006/08/study-shows-strong-consumer-consideration-for-flex-fuel-vehicles-including-e85-plug-in-hybrids-peak-interest.html Survey shows 49% of consumers would consider buying a plug-in hybrid] - Synovate, 8/16/06<br />
* [http://www.detnews.com/apps/pbcs.dll/article?AID=/20060728/AUTO01/607280363/1148 President Bush: U.S. progress on better plug-in hybrids speeds along] - Detnews 7/28/06<br />
* [http://www.forbesautos.com/news/features/2006/phevs/plug-in-hybrids_1.html Prepare to Plug in for 100-mpg Hybrids] - Forbes Autos, 7/31/2006<br />
* [http://www.csmonitor.com/2006/0720/p02s01-ussc.html Toyota moves to corner the 'plug-in' market] - Christian Science Monitor, 7/21/06 <br />
*On [[July 18]], [[2006]], [[Toyota]] announced that it "plans to develop a hybrid vehicle that will run locally on batteries charged by a typical 120-volt outlet before switching over to a gasoline engine for longer hauls."<ref>{{cite news | last=Thomas | first=Ken | title=Toyota charging ahead with plans for plug-in hybrid | date=[[19 July]], [[2006]] | publisher=Chicago Sun-Times/Associated Press| url=http://www.suntimes.com/output/business/cst-fin-plug19.html}}</ref><br />
* [http://www.evworld.com/view.cfm?section=article&storyid=1042 Report from the Advanced Automotive Battery Conference] - 6/6/06<br />
</div><br />
<br />
===Related groups===<br />
<div style="-moz-column-count:2; column-count:2;"><br />
*''[http://www.calcars.org/vehicles.html California Cars Initiative (CalCars.org)]'', [[non-profit]] promoter of PHEV technology: [http://groups.yahoo.com/group/calcars-news groups.yahoo calcars-news], [http://www.priusplus.org Prius+: Info on converting Prius to plug in] ([http://groups.yahoo.com/group/priusplus groups.yahoo priusplus])<br />
*''[http://www.eaa-phev.org Electric and Plug-In Hybrid Electric Vehicles Wiki]''<br />
*''[http://www.eaa-phev.org/wiki/Template:Prius_PHEV_Options Eaa-phev.org Wiki table comparing all known Prius conversion options]<br />
*''[http://www.hybridconsortium.org Hybridconsortium.org]''<br />
*[http://www.pluginpartners.com A market for PHEVs exists today!]'': [http://www.SetAmericaFree.org energy security via plug-in hybrids], [http://www.SecureEnergy.org Oil Crisis Simulations lead to PHEVs], Windows Media Video (wmv) [http://www.pluginpartners.org/includes/images/PHEV%20Video%2010%20Best.wmv promoting plug-ins]<br />
*''[http://auto.howstuffworks.com/100-mpg-news.htm HowStuffWorks: Modified Hybrid Gets 100 MPG]''.<br />
</div><br />
<br />
===Websites===<br />
* [http://www.daimlerchrysler.com/dccom/0,,0-5-7165-1-456546-1-0-0-0-0-0-243-7165-0-0-0-0-0-0-0,00.html Description of DaimlerChrysler's plug-in hybrid Sprinter van]<br />
*[http://faculty.dbcc.edu/tulsian/interestingReading/energy/Hybrid_vehicles.pdf "Hybrid Vehicles Gain Traction"] Scientific American, April 2006 (Copy can be found on [http://www.calcars.org/calcars-news/329.html Calcars site])<br />
*[http://www.treehugger.com/files/2006/10/tesla_motors_th.php Tesla Motors: The Pros and Cons of Plug-In Hybrids]<br />
*Interview: [http://www.inoculatedmind.com/?p=81 "Inventor Andy Frank explains his Plug-in Hybrid Electric Vehicle design,"] The Inoculated Mind Radio & Mindcast, April 2006.<br />
*[http://fora.tv/fora/showthread.php?t=777 Sherry Boschert, president of the San Francisco Electric Vehicle Association, speaks about Plug-in Hybrids]<br />
<br />
[[Category:Alternative propulsion]]<br />
[[Category:Automotive technologies]]<br />
[[Category:Electric vehicles]]<br />
[[Category:Hybrid vehicles|*]]<br />
[[Category:Sustainable technologies]]</div>HybridBoyhttps://wikicars.org/index.php?title=Baset_trailer&diff=50501Baset trailer2007-04-19T15:47:12Z<p>HybridBoy: </p>
<hr />
<div> '''baset trailer''' is a range extending device for use with [[battery electric vehicle]]s consisting of a [[battery pack]] mounted in a [[trailer]]. The trailer with discharget batteries <ref>I.e.[http://enviromotors.com/wiki/index.php/Sparrow/Batteries "D34M" Optima Blue-Top and Yellow-Top batteries]. </ref> can in this way easily by replace by another one with batteries charged.<br />
<br />
Most small to midsized passenger vehicles would require 15 to 20 [[kW]]. Larger vehicles could require 30 kW or more of power depending on how heavy and/or un-aerodynamic they happen to be. <br />
<br />
They can be also used with [[electric bus]]es: bus companies can store recharged batteries in route strategic points ([[bus station]]s, [[fuel station]]s, [[parking lot]]s, [[electric utility]] facilities, ad-hoc facilities and so on).<br />
<br />
==See also==<br />
* [[Camping]]<br />
* [[Epusher trailer]]<br />
* [[Genset trailer]]<br />
* [[Green tuning]]<br />
* [[Pusher trailer]]<br />
* [[Plug-in hybrid]]<br />
* [[Trailer]]<br />
== References ==<br />
<references /><br />
<br />
[[Category:Electric vehicles]]<br />
[[Category:Trailers]]<br />
<br />
{{automotive-tech-stub}}<br />
<br />
<br />
{{stub}}</div>HybridBoyhttps://wikicars.org/index.php?title=Category:Three-wheeled_motor_vehicles&diff=50354Category:Three-wheeled motor vehicles2007-04-17T19:56:50Z<p>HybridBoy: </p>
<hr />
<div>[[Category:Vehicles]]</div>HybridBoyhttps://wikicars.org/index.php?title=Piaggio_MP3&diff=50353Piaggio MP32007-04-17T19:56:32Z<p>HybridBoy: </p>
<hr />
<div>The '''Piaggio MP3''' is a [[tilting three wheeler|tilting three-wheeled scooter]] from the Italian manufacturer [[Piaggio]]. It was first brought to market in [[2006]].<br />
<br />
Because of its unique three-wheel mechanism, it can be brought to a stop and parked like a car, without concern for a traditional [[kickstand]] or centerstand. The front suspension/steering consists of two regular Vespa style suspensions, linked by an alloy [[parallellogram]] and a central steering arm. The whole system is adjustment, hence maintenance free.<br />
<br />
125 and 250cc versions are available, with 400cc models coming during late 2007. Piaggio may produce a similar 500cc machine under the sporty [[Gilera]] brand, possibly to be called the Fuoco 500.<ref>[http://scooters.en.dailymotos.com/new/7930/1/gilera/fuoco/three/wheels Piaggio press kit]</ref><br />
<br />
==References==<br />
<references/><br />
<br />
==External links==<br />
*[http://www.mp3.piaggio.com Manufacturer information]<br />
<br />
[[Category:Three-wheeled motor vehicles]]<br />
{{motorcycle-stub}}</div>HybridBoyhttps://wikicars.org/index.php?title=Hybrid_electric_vehicle&diff=49946Hybrid electric vehicle2007-04-10T14:15:57Z<p>HybridBoy: </p>
<hr />
<div>A '''hybrid vehicle''' (HV) is a vehicle that uses two or more distinct power sources such as:<br />
*An on-board [[rechargeable energy storage system]] (RESS) and a fueled power source for vehicle [[Ground propulsion|propulsion]]<br />
*Human powered bicycle with battery assist<br />
*A sail boat with electric power[http://www.autobloggreen.com/2006/11/28/heard-of-regenerative-braking-how-about-regenerative-sailing/]<br />
<br />
The term most commonly refers to a [[petroleum electric hybrid vehicle]], also called '''Hybrid-electric vehicle (HEV)''' which use [[internal combustion]] engines and [[electric battery|electric batteries]] to power [[electric motor]]s. See also [[Hybrid Vehicle Drivetrains|"Hybrid Vehicle Drivetrains"]] and [[List_of_hybrid_vehicles|"List of hybrid vehicles"]].<br />
<br />
==History==<br />
One of the earliest hybrid vehicles were simply boats with both sails and oars, such as the [[Trireme|Greek/Phoenician trireme warships]]. These used a sail for traveling with the wind, and the oars for when there was insufficient wind, or in circumstances that the sail was unfavorable (such as naval combat, in the case of the triremes).<br />
<br />
==Two-wheeled and cycle-type vehicles==<br />
[[Moped]]s and [[Motorized bicycles|electric bicycles]] are a simple form of a hybrid, as power is delivered both via an [[internal combustion|internal combustion engine]] or [[electric motor]] and the rider's muscles. <br />
<br />
* In a '''parallel hybrid bicycle''' human and motor power are mechanically coupled at the pedal drive train or at the rear or the front wheel, e.g. using a hub motor, a roller pressing onto a tire, or a connection to a wheel using a transmission element. Human and motor torques are added together. Almost all manufactured models are of this type. See [[Motorized bicycles]], [[Moped|Mopeds]] and <ref>{{cite web | title=Das Powerbike (German), ISBN 3895951234 | url=http://gso.gbv.de/DB=2.1/SET=1/TTL=1/SHW?FRST=1&PRS=HOL&HILN=888#888 | accessdate=february 27 | accessyear=2007}}</ref> for more information.<br />
<br />
* In a '''series hybrid bicycle''' (SH) the user powers a generator using the pedals. This is converted into electricity and can be fed directly to the motor giving a [[chainless bicycle]] but also to charge a battery. The motor draws power from the battery and must be able to deliver the full mechanical torque required because none is available from the pedals. SH bicycles are not yet commercially available. They will become feasible if extremely high-efficiency generators and motors are available at competitive prices, especially for recumbent bicycles and tandems, where problems associated with the complexity of a long chain drive can be avoided. <ref>{{cite web | title=Velomobile Seminar 1999, ISBN 3-9520694-1-8 | url=http://www.futurebike.ch/page.asp?DH=2305 | accessdate=January 11 | accessyear=2006}} </ref>.<br />
<br />
::The first known prototype and publication of a SH bicycle is by Augustus Kinzel (US Patent 3'884'317) in 1975. In 1994 Bernie Macdonalds conceived the [http://www.mcn.org/a/omni/ELiteBro95.htm Electrilite] SH lightweight vehicle which used power electronics allowing regenerative braking and pedaling while stationary. In 1995 Thomas Müller designed a "Fahrrad mit elektromagnetischem Antrieb" in his 1995 diploma thesis and built a functional vehicle. In 1996 Jürg Blatter and Andreas Fuchs of Berne University of Applied Sciences built a SH bicycle and in 1998 mounted the system onto a [[Leitra]] tricycle (European patent EP 1165188). In 1999 Harald Kutzke described his concept of the "active bicycle": the aim is to approach the ideal bicycle weighing nothing and having no drag by electronic compensation. Until 2005 Fuchs and colleagues built several prototype SH tricycles and quadricycles. [http://mypage.bluewin.ch/fuchsbau/Fuchs2006.pdf]<br />
<br />
==Heavy vehicles==<br />
Hybrid [[power train]]s are used for [[diesel-electric]] or [[turbo-electric]] railway locomotives, buses, heavy goods vehicles, mobile [[hydraulic machinery]], and ships. Some form of heat engine drives an electric generator or hydraulic pump which power one or several electric or hydraulic motors. There are advantages in distributing power through wires or pipes rather than mechanical elements especially when multiple drives - e.g. driven wheels or propellers - are required. There are disadvantages due to the power lost in the double conversion. With large vehicles the advantages often outweigh especially as the relative conversion losses decrease with size. Generally there is no or relatively little energy storage capacity, e.g. auxiliary and emergency batteries and [[hydraulic accumulator]]s.<br />
<br />
==Petroleum-electric hybrids==<br />
[[Image:Hybrid-bus.jpg|thumbnail|Hybrid [[New Flyer]] [[Metrobus]]|300px]]<br />
{{main|Petroleum electric hybrid vehicle}}<br />
When the term ''hybrid vehicle'' is used, it most often refers to a [[Petroleum electric hybrid vehicle]]. These encompass such vehicles as the [[Toyota Prius]], [[Toyota Camry Hybrid]], [[Ford Escape Hybrid]], [[Honda Insight]] and others. A petroleum-electric hybrid most commonly uses [[internal combustion]] engines (generally gasoline or [[Diesel engine]]s, powered by a variety of fuels) and [[electric battery|electric batteries]] to power [[electric motor]]s. There are many [[Hybrid Vehicle Drivetrains|types of petroleum-electric hybrid drivetrains]] from '''Full hybrid''' to '''Mild hybrid''' which offer varying advantages and disadvantages <ref>[http://automobiles.honda.com/tools/calculators/mileage_calculator.asp?ModelNa,e=Civic+Hybrid# Fuel Saving Calculator]</ref>.<br />
<br />
==Hybrid fuel (dual mode)==<br />
In addition to vehicles that use two or more different devices for [[Ground propulsion|propulsion]], some also consider vehicles that use distinct energy input types ("[[fuel]]s") using the same tank and engine to be hybrids, although to avoid confusion with hybrids as described above and to use correctly the terms, these are described as [[dual mode]] vehicles:<br />
* Some [[electric trolleybus]]es can switch between an on board [[diesel engine]] and overhead electrical power depending on conditions (see [[dual mode bus]]). In principle, this could be combined with a battery subsystem to create a true plug-in hybrid trolleybus, although [[as of 2006]], no such design seems to have been announced.<br />
* [[Flexible-fuel vehicle]]s can use a mixture of input fuels (petroleum and [[biofuel]]s) in one tank &mdash; typically [[gasoline]] and [[bioethanol]] or [[biobutanol]], though diesel-[[biodiesel]] vehicles would also qualify. [[Liquified petroleum gas]] and [[natural gas]] are very different from each other and cannot be used in the same tanks, so it would be impossible to build an (LPG-NG) flexible fuel system.<br />
* Some vehicles have been modified to use another fuel source if it is available, such as cars modified to run on [[Autogas|autogas (LPG)]] and diesels modified to run on [[waste vegetable oil]] that has not been processed into bio-diesel.<br />
* Power-assist mechanisms for [[bicycle]]s and other [[human]]-powered vehicles are also included.<br />
<br />
==Continuously Recharged BEVs==<br />
<br />
Given suitable infrastructure, BEVs can be '''recharged'''<br />
'''while the user drives'''. The [[BEV]] establishes contact with an electrified rail, plate or overhead wires on the highway via an attached conducting wheel or other similar mechanism (see [[Conduit current collection]]). The BEV's batteries are recharged by this process - on the highway - and can then be used normally on other roads.<br />
<br />
This provides the advantage of '''virtually unrestricted highway'''<br />
'''range'''. Since most destinations are within 100 km of a major <br />
highway, this '''reduces the need for expensive battery systems'''.<br />
<br />
The technology for such infrastructure is old and well established -<br />
(see [[Conduit current collection]], [[trams]], [[electric rail]], [[trolley]]s, [[third rail]]). Electricity and infrastructure costs can be funded by toll revenue, gasoline taxes or other sources.<br />
<br />
==See also==<br />
{{Portal|Energy}}<br />
{{Portal|Ecology}}<br />
{|<br />
|- valign=top<br />
| width=250 align=left |<br />
* [[Alternative propulsion]]<br />
* [[Bivalent (engine)]]<br />
* [[Diesel-electric]] and [[diesel-electric locomotive]]<br />
* [[Electric vehicle]]<br />
* [[:Category:Hybrid buses|Hybrid buses]]<br />
* [[:Category:Hybrid trucks|Hybrid trucks]]<br />
<br />
| width=250 align=left |<br />
<br />
* [[Hybrid Locomotive|Hybrid Locomotive]]<br />
* [[Hybrid Vehicle Drivetrains]]<br />
* [[List of hybrid vehicles]]<br />
* [[OScar (open source car)]]<br />
* [[Petroleum electric hybrid vehicle]]<br />
* [[Plug-in hybrid electric vehicle]]<br />
* [[Tribrid vehicle]]<br />
|}<br />
<br />
==References==<br />
<div class="references-small"><br />
<references/><br />
</div><br />
<br />
==External links==<br />
===News===<br />
[http://cyclesantamonica.blogspot.com/2006/09/hybrid-bike.html Man Motors On Hybrid Bicycle video] - Sept 2006<br />
<br />
[[Category:Alternative propulsion]]<br />
[[Category:Hybrid vehicles]]<br />
[[Category:Engines]]<br />
[[Category:Electric vehicles]]</div>HybridBoyhttps://wikicars.org/index.php?title=Green_tuning&diff=49945Green tuning2007-04-10T14:14:37Z<p>HybridBoy: /* See also */</p>
<hr />
<div>{{Portal|Green tuning}}<br />
<br />
Green tuned cars are cars that has been [[car tuning|tuned]] to use [[alternative propulsion]] or deeper alternative propulsion.<br />
<br />
Types of green tunning includes: <br />
<br />
*[[Electric vehicle conversion]]. An electric vehicle conversion is the modification of a conventional internal combustion engine (ICE) driven vehicle to battery electric propulsion, creating a battery electric vehicle. In some cases the vehicle may be built by the converter, or assembled from a kit car, and vehicles of this type are also noted below.<br />
*[[Hybridization]]: change to a [[hybrid electric vehicle]]. One can use an [[aftermarket]] kit for the [[powertrain]] or use a [[hybrid adapter]] trailer.<br />
*[[Pluginization]] of hybrid cars. A plug-in hybrid electric vehicle (PHEV) is a hybrid which has additional battery capacity and the ability to be recharged from an external electrical outlet. In addition, modifications are made to the vehicle's control software. The vehicle can be used for short trips of moderate speed without needing the internal combustion engine (ICE) component of the vehicle, thereby saving fuel costs. In this mode of operation the vehicle operates as a pure battery electric vehicle with a weight penalty (the ICE). The long range and additional power of the ICE power train is available when needed.<br />
* Extension: adding a [[baset trailer]] to extend the range of a [[battery electric vehicle]] or a [[plug-in hybrid electric vehicle]].<br />
== See also ==<br />
* [[Glider]].<br />
<br />
== External links ==<br />
{{wikibookspar||Electric Vehicle Conversion}}<br />
*[http://wikicars.org/es/Portal:Green_tuning Wikicars green tuning Portal].<br />
*[http://www.priusplus.org/ Prius+: Info on converting Prius to plug in].<br />
* [http://www.evdl.org/ The Electric Vehicle Discussion List (EVDL) - A helpful resource for all current and future EV owners, converters, and enthusiasts.] <br />
<br />
{{tuning-stub}}<br />
<br />
[[Category:green vehicles]]<br />
[[Category:alternative propulsion]]<br />
[[Category:Tuning]]</div>HybridBoyhttps://wikicars.org/index.php?title=Glider&diff=49944Glider2007-04-10T14:14:19Z<p>HybridBoy: </p>
<hr />
<div>A '''glider''' is an independent converter that purchases new vehicles without motors and related equipment. See Electric vehicle conversion.<br />
<br />
== See also ==<br />
* [[Electric vehicle conversion]]<br />
* [[Green tuning]]<br />
<br />
{{stub}}</div>HybridBoyhttps://wikicars.org/index.php?title=Green_tuning&diff=49943Green tuning2007-04-10T14:12:37Z<p>HybridBoy: </p>
<hr />
<div>{{Portal|Green tuning}}<br />
<br />
Green tuned cars are cars that has been [[car tuning|tuned]] to use [[alternative propulsion]] or deeper alternative propulsion.<br />
<br />
Types of green tunning includes: <br />
<br />
*[[Electric vehicle conversion]]. An electric vehicle conversion is the modification of a conventional internal combustion engine (ICE) driven vehicle to battery electric propulsion, creating a battery electric vehicle. In some cases the vehicle may be built by the converter, or assembled from a kit car, and vehicles of this type are also noted below.<br />
*[[Hybridization]]: change to a [[hybrid electric vehicle]]. One can use an [[aftermarket]] kit for the [[powertrain]] or use a [[hybrid adapter]] trailer.<br />
*[[Pluginization]] of hybrid cars. A plug-in hybrid electric vehicle (PHEV) is a hybrid which has additional battery capacity and the ability to be recharged from an external electrical outlet. In addition, modifications are made to the vehicle's control software. The vehicle can be used for short trips of moderate speed without needing the internal combustion engine (ICE) component of the vehicle, thereby saving fuel costs. In this mode of operation the vehicle operates as a pure battery electric vehicle with a weight penalty (the ICE). The long range and additional power of the ICE power train is available when needed.<br />
* Extension: adding a [[baset trailer]] to extend the range of a [[battery electric vehicle]] or a [[plug-in hybrid electric vehicle]].<br />
== See also ==<br />
* [[Glider (disambiguation)]].<br />
== External links ==<br />
{{wikibookspar||Electric Vehicle Conversion}}<br />
*[http://wikicars.org/es/Portal:Green_tuning Wikicars green tuning Portal].<br />
*[http://www.priusplus.org/ Prius+: Info on converting Prius to plug in].<br />
* [http://www.evdl.org/ The Electric Vehicle Discussion List (EVDL) - A helpful resource for all current and future EV owners, converters, and enthusiasts.] <br />
<br />
{{tuning-stub}}<br />
<br />
[[Category:green vehicles]]<br />
[[Category:alternative propulsion]]<br />
[[Category:Tuning]]</div>HybridBoyhttps://wikicars.org/index.php?title=User_talk:HybridBoy&diff=49942User talk:HybridBoy2007-04-10T13:35:25Z<p>HybridBoy: /* Featured Member Nomination! */</p>
<hr />
<div>Hello HybridBoy!, thank you for [[Special:Contributions/HybridBoy|your contributions]], and welcome to [[Wikicars]]! Thank you for your contributions! If you have any questions, be sure to contact [[Wikicars:Administrators|a sysop]], or a senior user. Now, to create an article, click on "Make Page" or "<font color="red">create this page</font color>". For an article on a model, click on "Model Page" above. To create a model review article click the "Model Review Page" link above. Please remember to sign your name on talk pages by using four tildes (<nowiki>~~</nowiki><nowiki>~~</nowiki>); this will automatically produce your name and the date. Finally, please do your best to '''always fill in the edit summary field''' as this helps to document all of your hard work. Feel free to delete this message from your talk page if you like, or keep it for reference. Happy editing! -- [[User:0-172|Enzo Worshipper]] <sup>([[User talk:0-172|Talk to me]] + [[Special:Contributions/0-172|Contribs]])</sup> 21:33, 20 March 2007 (UTC)<br />
[[Category:Templates]]<br />
<br />
==Infoboxes==<br />
<br />
For future reference, here's wikicars' standardised infobox:<br />
<br />
{{infobox}}<br />
<br />
[[User:Red marquis|Red marquis]] 22:35, 20 March 2007 (UTC)<br />
{{-}}<br />
<br />
Thank you. I would add information about prizes. Regards.--[[Usuario:HybridBoy|HybridBoy]] 14:22 21 Mar 2007 (UTC)<br />
<br />
==Template Tagging==<br />
<br />
When bringing templates here, make sure to tag them with the Templates category(<nowiki>[[Category:Templates]]</nowiki>). You have brought tons of templates here, practically none having the template category. I made that same mistake when I first started importing templates here. [[User:Red marquis|Red marquis]] 23:32, 21 March 2007 (UTC).<br />
: OK. Can you help me import the wikipedia portal templates ? (see [[wikipedia:Wikipedia:Portal/Instructions| How to create a portal]]). Thanks in advance. --[[Usuario:HybridBoy|HybridBoy]] 14:07 25 Mar 2007 (UTC)<br />
<br />
== Featured Member Nomination! ==<br />
<br />
Hi there, [[User:HybridBoy|HybridBoy]]. Just wanted to give you a heads up that you've been nominated for the '''Featured Member''' section of the homepage. You can review the dates [[Featured Member Nominations|here]]. I do ask though, that you build out your [[User:HybridBoy|user page]] in the meantime. Nothing too personal or elaborate, just the basics. Feel free to get ideas from such users like [[User:0-172|Enzo Worshipper]], [[User:Red_marquis|Red_marquis]], [[User:Argen|Argen]], or any of the other [[Featured Member Nominations|past featured members]]. Thanks and happy wiki'ing! -[[User:PNiddy|Nidhi]] 18:02, 4 April 2007 (UTC)<br />
: Thank you this is a honor. I hope work and give ideas to improve Wikicars. --[[Usuario:HybridBoy|HybridBoy]] 13:35 10 Apr 2007 (UTC)</div>HybridBoyhttps://wikicars.org/index.php?title=User:HybridBoy&diff=49940User:HybridBoy2007-04-10T13:34:05Z<p>HybridBoy: </p>
<hr />
<div>{{todo priority|personal}}<br />
{| border=0 cellspacing=0 cellpadding=4 style="float:right; margin:0 0 .5em 1em; width:250px; background:#fff; border-collapse:collapse; border:1px solid #999; font-size:83%; line-height:1.5; " summary="Infobox Automobile"<br />
|- style="text-align:center; background:#f0f0f0;"<br />
| colspan=2 style="padding:0; background:#996; color:#fff; border-bottom:1px solid #999;" |<br />
|- style="color:#fff; background:#996; font-size:larger;"<br />
! colspan=2 | '''HybridBoy'''<br />
|-<br />
! colspan=2 style="text-align:center; font-weight:normal; background:#ddb;" | User<br />
|- style="vertical-align:top;"<br />
| Join Date<br />
| '''2007'''<br />
|- style="vertical-align:top;"<br />
| Location<br />
| '''Spain'''<br />
|- style="vertical-align:top; background:#f0f0f0;"<br />
| Gender<br />
| Male<br />
|- style="vertical-align:top;"<br />
| Current Project(s)<br />
| Various<br />
|- style="vertical-align:top; background:#f0f0f0;"<br />
| Favorite Cars<br />
| [[Toyota Prius]] with plug-in aftermarket kit.<br />
|}<br />
<br />
I love hybrid and pure electric vehicles. My dream vehicle is a micro-hybrid (this is a [[city car|city hybrid vehicle]]) with a [[baset trailer). I love Wikicars because one has the information (articles and review) about green vehicles and events.</div>HybridBoyhttps://wikicars.org/index.php?title=User:HybridBoy&diff=49935User:HybridBoy2007-04-10T13:26:11Z<p>HybridBoy: </p>
<hr />
<div>{{todo priority|personal}}<br />
{| border=0 cellspacing=0 cellpadding=4 style="float:right; margin:0 0 .5em 1em; width:250px; background:#fff; border-collapse:collapse; border:1px solid #999; font-size:83%; line-height:1.5; " summary="Infobox Automobile"<br />
|- style="text-align:center; background:#f0f0f0;"<br />
| colspan=2 style="padding:0; background:#996; color:#fff; border-bottom:1px solid #999;" | [[Image:Maserati Tipo 8C.jpg|400px]]<br />
|- style="color:#fff; background:#996; font-size:larger;"<br />
! colspan=2 | '''HybridBoy'''<br />
|-<br />
! colspan=2 style="text-align:center; font-weight:normal; background:#ddb;" | Admin (sysop)<br />
|- style="vertical-align:top;"<br />
| Join Date<br />
| '''2007'''<br />
|- style="vertical-align:top;"<br />
| Location<br />
| '''Spain'''<br />
|- style="vertical-align:top; background:#f0f0f0;"<br />
| Gender<br />
| Male<br />
|- style="vertical-align:top;"<br />
| Current Project(s)<br />
| Various<br />
|- style="vertical-align:top; background:#f0f0f0;"<br />
| Favorite Cars<br />
| [[Toyota Prius]] with plug-in aftermarket kit.<br />
|}<br />
<br />
I love hybrid and pure electric vehicles. My dream vehicle is a micro-hybrid (this is a [[city car|city hybrid vehicle]]) with a [[baset trailer). I love Wikicars because one has the information (articles and review) about green vehicles and events.</div>HybridBoyhttps://wikicars.org/index.php?title=Wikicars_talk:About&diff=49367Wikicars talk:About2007-04-01T18:36:22Z<p>HybridBoy: Upgrade</p>
<hr />
<div><br />
<br />
== Upgrade ==<br />
<br />
I suggest upgrade to the last MediaWiki version.</div>HybridBoyhttps://wikicars.org/index.php?title=Wikicars:About&diff=49366Wikicars:About2007-04-01T18:35:38Z<p>HybridBoy: </p>
<hr />
<div>Welcome to Wikicars. Please help us build the most comprehensive car guide in the world.<br />
Discuss the site with others on our [[Garage Talk]] page.<br />
<br />
__TOC__<br />
==About Wikicars==<br />
[[image:blessing.jpg|thumb| [[Blessing of the Cars]]]]<br />
Wikicars is impassioned by the role of the automobile as an enabler of personal freedom, exploration, and growth. Wikicars is propelled by car enthusiasts, working collaboratively to create the World's most comprehensive source of information about all things automotive. By all things automotive, we mean information about topics such as:<br />
<br />
* Cars, Trucks, and [[SUVs]]<br />
* [[Hybrid Cars|Hybrid Vehicles]] and other [[green vehicle|Green Vehicles]].<br />
* [[Supercar|Supercars]] <br />
* Vintage and Collectible Cars<br />
* [[Famous Cars]]<br />
* [[Car Shows]]<br />
* Car Accessories<br />
* [[List of Manufacturers|Car Manufacturers]]<br />
* [[:Category:Car designers|Car Designers]]<br />
<br />
Well...you get the idea. The word "cars" and "car culture" are merely shorthand for the wonderful ability to venture out on one's own into the world. We want Wikicars to cover it all: if it primarily moves on wheels, has a means of propulsion, and the ability to transport you or your friends and family-- bring it on.<br />
<br />
And don´t forget [[Garage Talk]].<br />
<br />
==Encyclopedia or Guidebook?==<br />
Wikicars is both. Wikicars aspires to be the most comprehensive source of fact based information about automobiles-- a Wikipedia of cars. At the same time, Wikicars is a guidebook, offering the consensus opinion of our community about the good, the bad, and the ugly of the automotive world. We believe this concensus opinion is very helpful; opinion and reviews that reflect the collective views of many people are much more likely to be accurate and unbiased.<br />
<br />
We have attempted to clearly label the opinion parts of the site. Some pages, such as Car Review Pages, are designed to be primarily opinion. Other pages have specifically labelled sections called "criticisms".<br />
<br />
==Wikicars Founding==<br />
Wikicars was started in June, 2006, by [http://www.internetbrands.com Internet Brands], the parent company of sites that include [http://www.carsdirect.com CarsDirect.com], [http://www.Autos.com Autos.com], [http://www.greenhybrid.com Greenhybrid,]and [http://www.autodatasolutions.com Autodata Solutions]. These sites offer some of the web's richest automotive content, and Wikicars has been seeded with some of Internet Brands' content. Internet Brands family of sites also includes [http://wikitravel.org Wikitravel].<br />
<br />
==Jump In!==<br />
[[image:Herbie.jpg|thumb|right|frame| [[Herbie, The Love Bug]]; Also see [[Famous Cars]]]]<br />
Hundreds of contributors have already begun expanding and improving Wikicars and we hope you will too! If you drive a car, you probably have knowledge or opinions that could help other car shoppers, owners, or enthusiasts.<br />
<br />
If you would like to help, feel free to add to existing articles by clicking the Edit tab at the top of any page, or start a new article by searching on a topic of interest and writing what you want if no entry already exists for that topic. Remember, however, not to use any copyright material; if you're not sure whether something is copyright, err on the safe side and don't use it.<br />
<br />
==FAQ==<br />
Have a question? Check out the [[Wikicars FAQ]] page.<br />
<br />
==Wikicars Templates==<br />
To help you out we've created some templates to get new articles started. <br />
<br />
'''''PLEASE REMEMBER TO KEEP ALL MAKE, MAKE MODEL AND MAKE MODEL REVIEW PAGES IN THIRD-PERSON!'''''<br />
<br />
* [[Wikicars:Model Template]]<br />
* [[Wikicars:Model Review Template]]<br />
* [[Wikicars:Make Template]]<br />
<br />
Thank you for your participating in WikiCars!<br />
<br />
==Wikicars Milestones==<br />
* Public launch: August, 2006<br />
* 2000 Articles: January 25, 2007<br />
* 3000 Articles: March 14, 2007<br />
<br />
== See also ==<br />
* [[Special:Version|MediaWiki version used in Wikicars]], [[http://www.mediawiki.org/wiki/MediaWiki latest MediaWiki version]] and [http://www.mediawiki.org/wiki/Manual:Upgrading upgrading].</div>HybridBoyhttps://wikicars.org/index.php?title=Wikicars:About&diff=49364Wikicars:About2007-04-01T14:43:38Z<p>HybridBoy: /* See also */</p>
<hr />
<div>Welcome to Wikicars. Please help us build the most comprehensive car guide in the world.<br />
Discuss the site with others on our [[Garage Talk]] page.<br />
<br />
__TOC__<br />
==About Wikicars==<br />
[[image:blessing.jpg|thumb| [[Blessing of the Cars]]]]<br />
Wikicars is impassioned by the role of the automobile as an enabler of personal freedom, exploration, and growth. Wikicars is propelled by car enthusiasts, working collaboratively to create the World's most comprehensive source of information about all things automotive. By all things automotive, we mean information about topics such as:<br />
<br />
* Cars, Trucks, and [[SUVs]]<br />
* [[Hybrid Cars|Hybrid Vehicles]] and other [[green vehicle|Green Vehicles]].<br />
* [[Supercar|Supercars]] <br />
* Vintage and Collectible Cars<br />
* [[Famous Cars]]<br />
* [[Car Shows]]<br />
* Car Accessories<br />
* [[List of Manufacturers|Car Manufacturers]]<br />
* [[:Category:Car designers|Car Designers]]<br />
<br />
Well...you get the idea. The word "cars" and "car culture" are merely shorthand for the wonderful ability to venture out on one's own into the world. We want Wikicars to cover it all: if it primarily moves on wheels, has a means of propulsion, and the ability to transport you or your friends and family-- bring it on.<br />
<br />
And don´t forget [[Garage Talk]].<br />
<br />
==Encyclopedia or Guidebook?==<br />
Wikicars is both. Wikicars aspires to be the most comprehensive source of fact based information about automobiles-- a Wikipedia of cars. At the same time, Wikicars is a guidebook, offering the consensus opinion of our community about the good, the bad, and the ugly of the automotive world. We believe this concensus opinion is very helpful; opinion and reviews that reflect the collective views of many people are much more likely to be accurate and unbiased.<br />
<br />
We have attempted to clearly label the opinion parts of the site. Some pages, such as Car Review Pages, are designed to be primarily opinion. Other pages have specifically labelled sections called "criticisms".<br />
<br />
==Wikicars Founding==<br />
Wikicars was started in June, 2006, by [http://www.internetbrands.com Internet Brands], the parent company of sites that include [http://www.carsdirect.com CarsDirect.com], [http://www.Autos.com Autos.com], [http://www.greenhybrid.com Greenhybrid,]and [http://www.autodatasolutions.com Autodata Solutions]. These sites offer some of the web's richest automotive content, and Wikicars has been seeded with some of Internet Brands' content. Internet Brands family of sites also includes [http://wikitravel.org Wikitravel].<br />
<br />
==Jump In!==<br />
[[image:Herbie.jpg|thumb|right|frame| [[Herbie, The Love Bug]]; Also see [[Famous Cars]]]]<br />
Hundreds of contributors have already begun expanding and improving Wikicars and we hope you will too! If you drive a car, you probably have knowledge or opinions that could help other car shoppers, owners, or enthusiasts.<br />
<br />
If you would like to help, feel free to add to existing articles by clicking the Edit tab at the top of any page, or start a new article by searching on a topic of interest and writing what you want if no entry already exists for that topic. Remember, however, not to use any copyright material; if you're not sure whether something is copyright, err on the safe side and don't use it.<br />
<br />
==FAQ==<br />
Have a question? Check out the [[Wikicars FAQ]] page.<br />
<br />
==Wikicars Templates==<br />
To help you out we've created some templates to get new articles started. <br />
<br />
'''''PLEASE REMEMBER TO KEEP ALL MAKE, MAKE MODEL AND MAKE MODEL REVIEW PAGES IN THIRD-PERSON!'''''<br />
<br />
* [[Wikicars:Model Template]]<br />
* [[Wikicars:Model Review Template]]<br />
* [[Wikicars:Make Template]]<br />
<br />
Thank you for your participating in WikiCars!<br />
<br />
==Wikicars Milestones==<br />
* Public launch: August, 2006<br />
* 2000 Articles: January 25, 2007<br />
* 3000 Articles: March 14, 2007<br />
<br />
== See also ==<br />
* [[Special:Version|MediaWiki version used]] and [http://www.mediawiki.org/wiki/Manual:Upgrading upgrading].</div>HybridBoyhttps://wikicars.org/index.php?title=Wikicars:About&diff=49363Wikicars:About2007-04-01T14:43:24Z<p>HybridBoy: /* See also */</p>
<hr />
<div>Welcome to Wikicars. Please help us build the most comprehensive car guide in the world.<br />
Discuss the site with others on our [[Garage Talk]] page.<br />
<br />
__TOC__<br />
==About Wikicars==<br />
[[image:blessing.jpg|thumb| [[Blessing of the Cars]]]]<br />
Wikicars is impassioned by the role of the automobile as an enabler of personal freedom, exploration, and growth. Wikicars is propelled by car enthusiasts, working collaboratively to create the World's most comprehensive source of information about all things automotive. By all things automotive, we mean information about topics such as:<br />
<br />
* Cars, Trucks, and [[SUVs]]<br />
* [[Hybrid Cars|Hybrid Vehicles]] and other [[green vehicle|Green Vehicles]].<br />
* [[Supercar|Supercars]] <br />
* Vintage and Collectible Cars<br />
* [[Famous Cars]]<br />
* [[Car Shows]]<br />
* Car Accessories<br />
* [[List of Manufacturers|Car Manufacturers]]<br />
* [[:Category:Car designers|Car Designers]]<br />
<br />
Well...you get the idea. The word "cars" and "car culture" are merely shorthand for the wonderful ability to venture out on one's own into the world. We want Wikicars to cover it all: if it primarily moves on wheels, has a means of propulsion, and the ability to transport you or your friends and family-- bring it on.<br />
<br />
And don´t forget [[Garage Talk]].<br />
<br />
==Encyclopedia or Guidebook?==<br />
Wikicars is both. Wikicars aspires to be the most comprehensive source of fact based information about automobiles-- a Wikipedia of cars. At the same time, Wikicars is a guidebook, offering the consensus opinion of our community about the good, the bad, and the ugly of the automotive world. We believe this concensus opinion is very helpful; opinion and reviews that reflect the collective views of many people are much more likely to be accurate and unbiased.<br />
<br />
We have attempted to clearly label the opinion parts of the site. Some pages, such as Car Review Pages, are designed to be primarily opinion. Other pages have specifically labelled sections called "criticisms".<br />
<br />
==Wikicars Founding==<br />
Wikicars was started in June, 2006, by [http://www.internetbrands.com Internet Brands], the parent company of sites that include [http://www.carsdirect.com CarsDirect.com], [http://www.Autos.com Autos.com], [http://www.greenhybrid.com Greenhybrid,]and [http://www.autodatasolutions.com Autodata Solutions]. These sites offer some of the web's richest automotive content, and Wikicars has been seeded with some of Internet Brands' content. Internet Brands family of sites also includes [http://wikitravel.org Wikitravel].<br />
<br />
==Jump In!==<br />
[[image:Herbie.jpg|thumb|right|frame| [[Herbie, The Love Bug]]; Also see [[Famous Cars]]]]<br />
Hundreds of contributors have already begun expanding and improving Wikicars and we hope you will too! If you drive a car, you probably have knowledge or opinions that could help other car shoppers, owners, or enthusiasts.<br />
<br />
If you would like to help, feel free to add to existing articles by clicking the Edit tab at the top of any page, or start a new article by searching on a topic of interest and writing what you want if no entry already exists for that topic. Remember, however, not to use any copyright material; if you're not sure whether something is copyright, err on the safe side and don't use it.<br />
<br />
==FAQ==<br />
Have a question? Check out the [[Wikicars FAQ]] page.<br />
<br />
==Wikicars Templates==<br />
To help you out we've created some templates to get new articles started. <br />
<br />
'''''PLEASE REMEMBER TO KEEP ALL MAKE, MAKE MODEL AND MAKE MODEL REVIEW PAGES IN THIRD-PERSON!'''''<br />
<br />
* [[Wikicars:Model Template]]<br />
* [[Wikicars:Model Review Template]]<br />
* [[Wikicars:Make Template]]<br />
<br />
Thank you for your participating in WikiCars!<br />
<br />
==Wikicars Milestones==<br />
* Public launch: August, 2006<br />
* 2000 Articles: January 25, 2007<br />
* 3000 Articles: March 14, 2007<br />
<br />
== See also ==<br />
* [[Special:Version|MediaWiki version used]] and [http://www.mediawiki.org/wiki/Manual:Upgrading Upgrading].</div>HybridBoyhttps://wikicars.org/index.php?title=Wikicars:About&diff=49362Wikicars:About2007-04-01T14:42:57Z<p>HybridBoy: /* See also */</p>
<hr />
<div>Welcome to Wikicars. Please help us build the most comprehensive car guide in the world.<br />
Discuss the site with others on our [[Garage Talk]] page.<br />
<br />
__TOC__<br />
==About Wikicars==<br />
[[image:blessing.jpg|thumb| [[Blessing of the Cars]]]]<br />
Wikicars is impassioned by the role of the automobile as an enabler of personal freedom, exploration, and growth. Wikicars is propelled by car enthusiasts, working collaboratively to create the World's most comprehensive source of information about all things automotive. By all things automotive, we mean information about topics such as:<br />
<br />
* Cars, Trucks, and [[SUVs]]<br />
* [[Hybrid Cars|Hybrid Vehicles]] and other [[green vehicle|Green Vehicles]].<br />
* [[Supercar|Supercars]] <br />
* Vintage and Collectible Cars<br />
* [[Famous Cars]]<br />
* [[Car Shows]]<br />
* Car Accessories<br />
* [[List of Manufacturers|Car Manufacturers]]<br />
* [[:Category:Car designers|Car Designers]]<br />
<br />
Well...you get the idea. The word "cars" and "car culture" are merely shorthand for the wonderful ability to venture out on one's own into the world. We want Wikicars to cover it all: if it primarily moves on wheels, has a means of propulsion, and the ability to transport you or your friends and family-- bring it on.<br />
<br />
And don´t forget [[Garage Talk]].<br />
<br />
==Encyclopedia or Guidebook?==<br />
Wikicars is both. Wikicars aspires to be the most comprehensive source of fact based information about automobiles-- a Wikipedia of cars. At the same time, Wikicars is a guidebook, offering the consensus opinion of our community about the good, the bad, and the ugly of the automotive world. We believe this concensus opinion is very helpful; opinion and reviews that reflect the collective views of many people are much more likely to be accurate and unbiased.<br />
<br />
We have attempted to clearly label the opinion parts of the site. Some pages, such as Car Review Pages, are designed to be primarily opinion. Other pages have specifically labelled sections called "criticisms".<br />
<br />
==Wikicars Founding==<br />
Wikicars was started in June, 2006, by [http://www.internetbrands.com Internet Brands], the parent company of sites that include [http://www.carsdirect.com CarsDirect.com], [http://www.Autos.com Autos.com], [http://www.greenhybrid.com Greenhybrid,]and [http://www.autodatasolutions.com Autodata Solutions]. These sites offer some of the web's richest automotive content, and Wikicars has been seeded with some of Internet Brands' content. Internet Brands family of sites also includes [http://wikitravel.org Wikitravel].<br />
<br />
==Jump In!==<br />
[[image:Herbie.jpg|thumb|right|frame| [[Herbie, The Love Bug]]; Also see [[Famous Cars]]]]<br />
Hundreds of contributors have already begun expanding and improving Wikicars and we hope you will too! If you drive a car, you probably have knowledge or opinions that could help other car shoppers, owners, or enthusiasts.<br />
<br />
If you would like to help, feel free to add to existing articles by clicking the Edit tab at the top of any page, or start a new article by searching on a topic of interest and writing what you want if no entry already exists for that topic. Remember, however, not to use any copyright material; if you're not sure whether something is copyright, err on the safe side and don't use it.<br />
<br />
==FAQ==<br />
Have a question? Check out the [[Wikicars FAQ]] page.<br />
<br />
==Wikicars Templates==<br />
To help you out we've created some templates to get new articles started. <br />
<br />
'''''PLEASE REMEMBER TO KEEP ALL MAKE, MAKE MODEL AND MAKE MODEL REVIEW PAGES IN THIRD-PERSON!'''''<br />
<br />
* [[Wikicars:Model Template]]<br />
* [[Wikicars:Model Review Template]]<br />
* [[Wikicars:Make Template]]<br />
<br />
Thank you for your participating in WikiCars!<br />
<br />
==Wikicars Milestones==<br />
* Public launch: August, 2006<br />
* 2000 Articles: January 25, 2007<br />
* 3000 Articles: March 14, 2007<br />
<br />
== See also ==<br />
* [[Special:Version|MediaWiki version used in Wikicars.]] and [http://www.mediawiki.org/wiki/Manual:Upgrading Upgrading].</div>HybridBoyhttps://wikicars.org/index.php?title=Wikicars:About&diff=49361Wikicars:About2007-04-01T14:42:38Z<p>HybridBoy: /* See also */</p>
<hr />
<div>Welcome to Wikicars. Please help us build the most comprehensive car guide in the world.<br />
Discuss the site with others on our [[Garage Talk]] page.<br />
<br />
__TOC__<br />
==About Wikicars==<br />
[[image:blessing.jpg|thumb| [[Blessing of the Cars]]]]<br />
Wikicars is impassioned by the role of the automobile as an enabler of personal freedom, exploration, and growth. Wikicars is propelled by car enthusiasts, working collaboratively to create the World's most comprehensive source of information about all things automotive. By all things automotive, we mean information about topics such as:<br />
<br />
* Cars, Trucks, and [[SUVs]]<br />
* [[Hybrid Cars|Hybrid Vehicles]] and other [[green vehicle|Green Vehicles]].<br />
* [[Supercar|Supercars]] <br />
* Vintage and Collectible Cars<br />
* [[Famous Cars]]<br />
* [[Car Shows]]<br />
* Car Accessories<br />
* [[List of Manufacturers|Car Manufacturers]]<br />
* [[:Category:Car designers|Car Designers]]<br />
<br />
Well...you get the idea. The word "cars" and "car culture" are merely shorthand for the wonderful ability to venture out on one's own into the world. We want Wikicars to cover it all: if it primarily moves on wheels, has a means of propulsion, and the ability to transport you or your friends and family-- bring it on.<br />
<br />
And don´t forget [[Garage Talk]].<br />
<br />
==Encyclopedia or Guidebook?==<br />
Wikicars is both. Wikicars aspires to be the most comprehensive source of fact based information about automobiles-- a Wikipedia of cars. At the same time, Wikicars is a guidebook, offering the consensus opinion of our community about the good, the bad, and the ugly of the automotive world. We believe this concensus opinion is very helpful; opinion and reviews that reflect the collective views of many people are much more likely to be accurate and unbiased.<br />
<br />
We have attempted to clearly label the opinion parts of the site. Some pages, such as Car Review Pages, are designed to be primarily opinion. Other pages have specifically labelled sections called "criticisms".<br />
<br />
==Wikicars Founding==<br />
Wikicars was started in June, 2006, by [http://www.internetbrands.com Internet Brands], the parent company of sites that include [http://www.carsdirect.com CarsDirect.com], [http://www.Autos.com Autos.com], [http://www.greenhybrid.com Greenhybrid,]and [http://www.autodatasolutions.com Autodata Solutions]. These sites offer some of the web's richest automotive content, and Wikicars has been seeded with some of Internet Brands' content. Internet Brands family of sites also includes [http://wikitravel.org Wikitravel].<br />
<br />
==Jump In!==<br />
[[image:Herbie.jpg|thumb|right|frame| [[Herbie, The Love Bug]]; Also see [[Famous Cars]]]]<br />
Hundreds of contributors have already begun expanding and improving Wikicars and we hope you will too! If you drive a car, you probably have knowledge or opinions that could help other car shoppers, owners, or enthusiasts.<br />
<br />
If you would like to help, feel free to add to existing articles by clicking the Edit tab at the top of any page, or start a new article by searching on a topic of interest and writing what you want if no entry already exists for that topic. Remember, however, not to use any copyright material; if you're not sure whether something is copyright, err on the safe side and don't use it.<br />
<br />
==FAQ==<br />
Have a question? Check out the [[Wikicars FAQ]] page.<br />
<br />
==Wikicars Templates==<br />
To help you out we've created some templates to get new articles started. <br />
<br />
'''''PLEASE REMEMBER TO KEEP ALL MAKE, MAKE MODEL AND MAKE MODEL REVIEW PAGES IN THIRD-PERSON!'''''<br />
<br />
* [[Wikicars:Model Template]]<br />
* [[Wikicars:Model Review Template]]<br />
* [[Wikicars:Make Template]]<br />
<br />
Thank you for your participating in WikiCars!<br />
<br />
==Wikicars Milestones==<br />
* Public launch: August, 2006<br />
* 2000 Articles: January 25, 2007<br />
* 3000 Articles: March 14, 2007<br />
<br />
== See also ==<br />
* [[Special:Version|MediaWiki version used in Wikicars.]] and [http://www.mediawiki.org/wiki/Manual:Upgrading|Upgrading].</div>HybridBoyhttps://wikicars.org/index.php?title=Wikicars:About&diff=49360Wikicars:About2007-04-01T14:37:14Z<p>HybridBoy: </p>
<hr />
<div>Welcome to Wikicars. Please help us build the most comprehensive car guide in the world.<br />
Discuss the site with others on our [[Garage Talk]] page.<br />
<br />
__TOC__<br />
==About Wikicars==<br />
[[image:blessing.jpg|thumb| [[Blessing of the Cars]]]]<br />
Wikicars is impassioned by the role of the automobile as an enabler of personal freedom, exploration, and growth. Wikicars is propelled by car enthusiasts, working collaboratively to create the World's most comprehensive source of information about all things automotive. By all things automotive, we mean information about topics such as:<br />
<br />
* Cars, Trucks, and [[SUVs]]<br />
* [[Hybrid Cars|Hybrid Vehicles]] and other [[green vehicle|Green Vehicles]].<br />
* [[Supercar|Supercars]] <br />
* Vintage and Collectible Cars<br />
* [[Famous Cars]]<br />
* [[Car Shows]]<br />
* Car Accessories<br />
* [[List of Manufacturers|Car Manufacturers]]<br />
* [[:Category:Car designers|Car Designers]]<br />
<br />
Well...you get the idea. The word "cars" and "car culture" are merely shorthand for the wonderful ability to venture out on one's own into the world. We want Wikicars to cover it all: if it primarily moves on wheels, has a means of propulsion, and the ability to transport you or your friends and family-- bring it on.<br />
<br />
And don´t forget [[Garage Talk]].<br />
<br />
==Encyclopedia or Guidebook?==<br />
Wikicars is both. Wikicars aspires to be the most comprehensive source of fact based information about automobiles-- a Wikipedia of cars. At the same time, Wikicars is a guidebook, offering the consensus opinion of our community about the good, the bad, and the ugly of the automotive world. We believe this concensus opinion is very helpful; opinion and reviews that reflect the collective views of many people are much more likely to be accurate and unbiased.<br />
<br />
We have attempted to clearly label the opinion parts of the site. Some pages, such as Car Review Pages, are designed to be primarily opinion. Other pages have specifically labelled sections called "criticisms".<br />
<br />
==Wikicars Founding==<br />
Wikicars was started in June, 2006, by [http://www.internetbrands.com Internet Brands], the parent company of sites that include [http://www.carsdirect.com CarsDirect.com], [http://www.Autos.com Autos.com], [http://www.greenhybrid.com Greenhybrid,]and [http://www.autodatasolutions.com Autodata Solutions]. These sites offer some of the web's richest automotive content, and Wikicars has been seeded with some of Internet Brands' content. Internet Brands family of sites also includes [http://wikitravel.org Wikitravel].<br />
<br />
==Jump In!==<br />
[[image:Herbie.jpg|thumb|right|frame| [[Herbie, The Love Bug]]; Also see [[Famous Cars]]]]<br />
Hundreds of contributors have already begun expanding and improving Wikicars and we hope you will too! If you drive a car, you probably have knowledge or opinions that could help other car shoppers, owners, or enthusiasts.<br />
<br />
If you would like to help, feel free to add to existing articles by clicking the Edit tab at the top of any page, or start a new article by searching on a topic of interest and writing what you want if no entry already exists for that topic. Remember, however, not to use any copyright material; if you're not sure whether something is copyright, err on the safe side and don't use it.<br />
<br />
==FAQ==<br />
Have a question? Check out the [[Wikicars FAQ]] page.<br />
<br />
==Wikicars Templates==<br />
To help you out we've created some templates to get new articles started. <br />
<br />
'''''PLEASE REMEMBER TO KEEP ALL MAKE, MAKE MODEL AND MAKE MODEL REVIEW PAGES IN THIRD-PERSON!'''''<br />
<br />
* [[Wikicars:Model Template]]<br />
* [[Wikicars:Model Review Template]]<br />
* [[Wikicars:Make Template]]<br />
<br />
Thank you for your participating in WikiCars!<br />
<br />
==Wikicars Milestones==<br />
* Public launch: August, 2006<br />
* 2000 Articles: January 25, 2007<br />
* 3000 Articles: March 14, 2007<br />
<br />
== See also ==<br />
* [[Special:Version|MediaWiki version used in Wikicars.]]</div>HybridBoyhttps://wikicars.org/index.php?title=Portal:Portal&diff=48680Portal:Portal2007-03-26T13:17:32Z<p>HybridBoy: </p>
<hr />
<div>{{browsebar}}<br />
<br />
To create a new portal on the topic "Topic" using the {{tl|box portal skeleton}} template, create a new page using <nowiki>[[Portal:Topic]]</nowiki> as the title of the page (where "Topic" is the subject of your portal) and enter the following text<br />
<nowiki>{{subst:box portal skeleton}}</nowiki><br />
Save</div>HybridBoyhttps://wikicars.org/index.php?title=Template:Reqphoto&diff=48677Template:Reqphoto2007-03-26T13:04:04Z<p>HybridBoy: </p>
<hr />
<div>It is requested that a '''photograph''' or '''photographs''' be [[wikipedia:Wikipedia:Uploading images|included]] in this article to [[wikipedia:Wikipedia:Article development|improve its quality]].<br />
<br />
[[Category:Wikicars requested photographs]]<br />
<noinclude>[[Category:Templates]] </noinclude></div>HybridBoyhttps://wikicars.org/index.php?title=Template:Reqphoto&diff=48676Template:Reqphoto2007-03-26T13:03:02Z<p>HybridBoy: </p>
<hr />
<div>It is requested that a '''photograph''' or '''photographs''' be [[wikipedia:Wikipedia:Uploading images|included]] in this article to [[wikipedia:Wikipedia:Article development|improve its quality]].<br />
<br />
[[Category:Wikicars requested photographs]]<br />
[[Category:Templates]]</div>HybridBoyhttps://wikicars.org/index.php?title=Template:Reqphoto&diff=48675Template:Reqphoto2007-03-26T13:02:48Z<p>HybridBoy: </p>
<hr />
<div>It is requested that a '''photograph''' or '''photographs''' be [[wikipedia:Wikipedia:Uploading images|included]] in this article to [[wikipedia:Wikipedia:Article development|improve its quality]].<br />
<br />
[[Category:Wikipedia requested photographs]]<br />
[[Category:Templates]]</div>HybridBoyhttps://wikicars.org/index.php?title=Category:Vehicles&diff=48670Category:Vehicles2007-03-26T12:59:59Z<p>HybridBoy: </p>
<hr />
<div>[[Category:Root]]</div>HybridBoyhttps://wikicars.org/index.php?title=Category:Green_vehicles&diff=48668Category:Green vehicles2007-03-26T12:59:47Z<p>HybridBoy: </p>
<hr />
<div>[[Category:Vehicles]]</div>HybridBoyhttps://wikicars.org/index.php?title=Category:Templates&diff=48667Category:Templates2007-03-26T12:59:00Z<p>HybridBoy: </p>
<hr />
<div>This is a category for all templates. When a template is created, it should be tagged with the <nowiki>[[Category:Templates]]</nowiki><br />
<br />
If possible use a more specific subcategory.</div>HybridBoyhttps://wikicars.org/index.php?title=Template:Portal:Green_tuning/Intro&diff=48571Template:Portal:Green tuning/Intro2007-03-25T19:04:15Z<p>HybridBoy: </p>
<hr />
<div>See [[green tuning]]</div>HybridBoyhttps://wikicars.org/index.php?title=Template:Portal:box-footer&diff=48570Template:Portal:box-footer2007-03-25T19:01:01Z<p>HybridBoy: </p>
<hr />
<div><div class="noprint" style="text-align:right; margin:0.3em 0.2em 0.2em 0.3em; padding:0.3em 0.2em 0.2em 0.3em;"><b>{{{1|}}}</b></div><div style="clear:both;"></div></div><noinclude><br />
</noinclude></div>HybridBoyhttps://wikicars.org/index.php?title=Category:Demo_templates&diff=48557Category:Demo templates2007-03-25T15:38:24Z<p>HybridBoy: </p>
<hr />
<div>[[Category:Templates]]</div>HybridBoyhttps://wikicars.org/index.php?title=Template:Chess_position&diff=48556Template:Chess position2007-03-25T15:38:08Z<p>HybridBoy: </p>
<hr />
<div>[[Image:Chess_{{{1}}}l40.png|{{{65}}}px|{{{1}}}]] [[Image:Chess_{{{2}}}d40.png|{{{65}}}px|{{{2}}}]] [[Image:Chess_{{{3}}}l40.png|{{{65}}}px|{{{3}}}]] [[Image:Chess_{{{4}}}d40.png|{{{65}}}px|{{{4}}}]] [[Image:Chess_{{{5}}}l40.png|{{{65}}}px|{{{5}}}]] [[Image:Chess_{{{6}}}d40.png|{{{65}}}px|{{{6}}}]] [[Image:Chess_{{{7}}}l40.png|{{{65}}}px|{{{7}}}]] [[Image:Chess_{{{8}}}d40.png|{{{65}}}px|{{{8}}}]] <br />
[[Image:Chess_{{{9}}}d40.png|{{{65}}}px|{{{9}}}]] [[Image:Chess_{{{10}}}l40.png|{{{65}}}px|{{{10}}}]] [[Image:Chess_{{{11}}}d40.png|{{{65}}}px|{{{11}}}]] [[Image:Chess_{{{12}}}l40.png|{{{65}}}px|{{{12}}}]] [[Image:Chess_{{{13}}}d40.png|{{{65}}}px|{{{13}}}]] [[Image:Chess_{{{14}}}l40.png|{{{65}}}px|{{{14}}}]] [[Image:Chess_{{{15}}}d40.png|{{{65}}}px|{{{15}}}]] [[Image:Chess_{{{16}}}l40.png|{{{65}}}px|{{{16}}}]] <br />
[[Image:Chess_{{{17}}}l40.png|{{{65}}}px|{{{17}}}]] [[Image:Chess_{{{18}}}d40.png|{{{65}}}px|{{{18}}}]] [[Image:Chess_{{{19}}}l40.png|{{{65}}}px|{{{19}}}]] [[Image:Chess_{{{20}}}d40.png|{{{65}}}px|{{{20}}}]] [[Image:Chess_{{{21}}}l40.png|{{{65}}}px|{{{21}}}]] [[Image:Chess_{{{22}}}d40.png|{{{65}}}px|{{{22}}}]] [[Image:Chess_{{{23}}}l40.png|{{{65}}}px|{{{23}}}]] [[Image:Chess_{{{24}}}d40.png|{{{65}}}px|{{{24}}}]] <br />
[[Image:Chess_{{{25}}}d40.png|{{{65}}}px|{{{25}}}]] [[Image:Chess_{{{26}}}l40.png|{{{65}}}px|{{{26}}}]] [[Image:Chess_{{{27}}}d40.png|{{{65}}}px|{{{27}}}]] [[Image:Chess_{{{28}}}l40.png|{{{65}}}px|{{{28}}}]] [[Image:Chess_{{{29}}}d40.png|{{{65}}}px|{{{29}}}]] [[Image:Chess_{{{30}}}l40.png|{{{65}}}px|{{{30}}}]] [[Image:Chess_{{{31}}}d40.png|{{{65}}}px|{{{31}}}]] [[Image:Chess_{{{32}}}l40.png|{{{65}}}px|{{{32}}}]] <br />
[[Image:Chess_{{{33}}}l40.png|{{{65}}}px|{{{33}}}]] [[Image:Chess_{{{34}}}d40.png|{{{65}}}px|{{{34}}}]] [[Image:Chess_{{{35}}}l40.png|{{{65}}}px|{{{35}}}]] [[Image:Chess_{{{36}}}d40.png|{{{65}}}px|{{{36}}}]] [[Image:Chess_{{{37}}}l40.png|{{{65}}}px|{{{37}}}]] [[Image:Chess_{{{38}}}d40.png|{{{65}}}px|{{{38}}}]] [[Image:Chess_{{{39}}}l40.png|{{{65}}}px|{{{39}}}]] [[Image:Chess_{{{40}}}d40.png|{{{65}}}px|{{{40}}}]] <br />
[[Image:Chess_{{{41}}}d40.png|{{{65}}}px|{{{41}}}]] [[Image:Chess_{{{42}}}l40.png|{{{65}}}px|{{{42}}}]] [[Image:Chess_{{{43}}}d40.png|{{{65}}}px|{{{43}}}]] [[Image:Chess_{{{44}}}l40.png|{{{65}}}px|{{{44}}}]] [[Image:Chess_{{{45}}}d40.png|{{{65}}}px|{{{45}}}]] [[Image:Chess_{{{46}}}l40.png|{{{65}}}px|{{{46}}}]] [[Image:Chess_{{{47}}}d40.png|{{{65}}}px|{{{47}}}]] [[Image:Chess_{{{48}}}l40.png|{{{65}}}px|{{{48}}}]] <br />
[[Image:Chess_{{{49}}}l40.png|{{{65}}}px|{{{49}}}]] [[Image:Chess_{{{50}}}d40.png|{{{65}}}px|{{{50}}}]] [[Image:Chess_{{{51}}}l40.png|{{{65}}}px|{{{51}}}]] [[Image:Chess_{{{52}}}d40.png|{{{65}}}px|{{{52}}}]] [[Image:Chess_{{{53}}}l40.png|{{{65}}}px|{{{53}}}]] [[Image:Chess_{{{54}}}d40.png|{{{65}}}px|{{{54}}}]] [[Image:Chess_{{{55}}}l40.png|{{{65}}}px|{{{55}}}]] [[Image:Chess_{{{56}}}d40.png|{{{65}}}px|{{{56}}}]] <br />
[[Image:Chess_{{{57}}}d40.png|{{{65}}}px|{{{57}}}]] [[Image:Chess_{{{58}}}l40.png|{{{65}}}px|{{{58}}}]] [[Image:Chess_{{{59}}}d40.png|{{{65}}}px|{{{59}}}]] [[Image:Chess_{{{60}}}l40.png|{{{65}}}px|{{{60}}}]] [[Image:Chess_{{{61}}}d40.png|{{{65}}}px|{{{61}}}]] [[Image:Chess_{{{62}}}l40.png|{{{65}}}px|{{{62}}}]] [[Image:Chess_{{{63}}}d40.png|{{{65}}}px|{{{63}}}]] [[Image:Chess_{{{64}}}l40.png|{{{65}}}px|{{{64}}}]] <br />
<noinclude>[[Category:demo templates]]</noinclude></div>HybridBoyhttps://wikicars.org/index.php?title=Help:Template&diff=48554Help:Template2007-03-25T15:36:04Z<p>HybridBoy: </p>
<hr />
<div>In [[wikipedia:MediaWiki|MediaWiki]], a '''template''' is a page which can be inserted into another page via a process called [[wikipedia:transclusion|transclusion]]. It can be considered a wiki [[w:en:subroutine|subroutine]] facility and is comparable to a #include statement or [[wikt:en:macro#Noun|macro]] that is expanded at page view time. [[Help:Substitution|Substitution]] allows templates to be used as a macro facility.<br />
<br />
This page and its extension '''[[Help:Advanced templates]]''' provide a reference manual on templates in MediaWiki. For an introduction, see ''[[Help:A quick guide to templates|A quick guide to templates]]'' and [[mw:Help:Templates]]. For syntax often used within templates, see [[m:ParserFunctions]] and other "Advanced functioning" help pages listed below.<br />
<br />
'''Note:''' The master version of this page is the page [[m:Help:Template]] on Meta-Wikipedia; template demos work there, but may not work if you are viewing a copy of this page on another project.<br />
<br />
==General==<br />
The '''template namespace''' is the [[Help:Namespace|namespace]] with prefix "'''Template:'''" (this prefix can be used in all languages, but the canonical prefixes in languages other than English include Vorlage, Modèle, Sjabloon, with colon; the site WikiFAQ calls it Snippet).<br />
<br />
A page in this namespace is called a '''template'''. The contents of such a page (either fixed or depending on [[w:en:Parameter (computer science)|parameters]] and/or [[Help:Variable|variable]]s) is designed to be useful for insertion in other pages ([[en:transclusion|transclusion]], creating a [[w:compound document|compound document]]).<br />
<br />
The syntax for insertion of the page "Template:''name''" is <nowiki>{{</nowiki>''name''<nowiki>}}</nowiki>. This is called a template tag. <br />
<br />
'''Example:''' <nowiki>abc{{tc}}def</nowiki> <br />
<br />
{{ut1|tc}} <br />
<br />
'''Gives:''' abc{{tc}}def.<br />
<br />
This reference in the wikitext causes insertion of the template content when the referring page is rendered. Various equivalent terms are:<br />
*calling the template<br />
*including the template<br />
*transcluding the template<br />
*using the template<br />
*embedding the template<br />
<br />
Depending on context "including" can be used as opposed to ''substituting'' the template. <br />
<br />
To create a hyperlink to a template page, use the usual wikilink syntax <nowiki>[[</nowiki>Template:''name'']].<br />
<br />
If the page "Template:''name''" does not exist, then <nowiki>{{</nowiki>''<nowiki>name</nowiki>''<nowiki>}}</nowiki> works as <nowiki>[[</nowiki>Template:''name''<nowiki>]]</nowiki>, a link to a non-existing page, leading to the edit page. Thus, one way of making a template is putting the tag first, and then following the link.<br />
<br />
If ''name'' starts with a valid namespace prefix, or a colon, then it is not prefixed with "Template:". This way any page can be used as template (a colon at the start refers to the main namespace). <br />
<br />
Also it provides an alternative way of calling a template, which can be used in the case of a name conflict with a variable, e.g. [[m:Template:Ns:3|Template:Ns:3]] and [[m:Template:PAGENAME|Template:PAGENAME]].<br />
<br />
Using a page outside the template namespace as template can be useful for:<br />
*quoting interface messages in the MediaWiki namespace<br />
*templates for personal use in subpages of one's userpage, e.g. for experimenting<br />
*inclusion of pages in other pages in the same namespace, e.g. having an extra page associated with each page, such as a to-do list, with a simple name correspondence; it can be created and included with <nowiki>{{{{NAMESPACE}}:{{PAGENAME}}/todo}}</nowiki>.<br />
<br />
As usual the template name is case sensitive except (on most projects) for the first letter, and a blank space is equivalent with an underscore (as opposed to parameter names, see below: they are case-sensitive, even with respect to the first letter, and spaces are distinguished from underscores).<br />
<br />
One can call a template that calls another template. If a template calls itself directly or indirectly, inclusion works only on one level for each template. However, with templates redirecting to the template that one would want to call recursively, one can achieve recursion without having to make copies of the whole template content, with the number of levels limited by the number of redirects. See also [[Help:Template#Repetition_within_a_page|Repetition within a page]] and {{tim|List of template calls}}.<br />
<br />
A [[Help:Variable|variable]] in a template is evaluated after insertion in the referring page, i.e. if <nowiki>{{PAGENAME}}</nowiki> occurs in the wikitext of a template, it is rendered as the name of the referring page, not the name of the template.<br />
<br />
A list of pages embedded in a page (as recorded in the [[m:templatelinks table|templatelinks table]]), all with links, is given on the edit page. Notes:<br />
*on a section edit page first the whole list is given, i.e. also the templates used in other sections; after pressing preview only those in the section, updated for the edits made, if any; preview on first edit gives the full list;<br />
*similarly, when editing an old version of a page, the list is first given for the current version, while after pressing preview the templates that used to be included are shown, updated for the edits on the old version made in the current session, if any; <br />
*if a page is conditionally embedded through #if, #ifeq, #ifexist, #ifexpr, or #switch, it is counted as embedded, even if the condition is not fulfilled<br />
*if the name of an embedded page is an expression, e.g. <nowiki>{{abc{{CURRENTDAY}}}}</nowiki>, currently giving {{abc{{CURRENTDAY}}}}, or <nowiki>{{{{#ifexist:Template:A|A|x1}}|Template does not exist}}</nowiki>, currently giving {{{{#ifexist:Template:A|A|x1}}|Template does not exist}}, the current template name is shown.<br />
<br />
Thus, to use "What links here" to find the pages that actually embed template A, instead of using e.g.<br />
<br />
:<nowiki>{{#if:..|{{a|pa1}}|{{b|pb1}}}}</nowiki><br />
<br />
one has to use an alternative, e.g., duplicating the condition:<br />
<br />
:<nowiki>{{{{#if:..|a|b}}|{{#if:..|pa1|pb1}}}}</nowiki><br />
<br />
or, using {{tim|echo}}:<br />
<br />
:<nowiki>{{{{#if:..|a|echo}}|1=pa1|echo={{b|pb1}}}}</nowiki><br />
<br />
Only with the first of the two alternatives "What links here" also finds the pages that actually embed template B. In the second alternative the page is anyway considered embedded. If we replace "b" by "<nowiki>{{if:1|b}}</nowiki>" the page is never considered embedded.<br />
<br />
(''Supported in version 1.4 and higher.'')<br />
<br />
When saving a page without newline at the end, and going to the edit page again, there is a newline at the end. However, this does not seem to have effect, see the example above and the following example:<br />
<br />
<pre>{{Numbered list demo}}{{Numbered list demo}}<br />
{{Numbered list demo}}</pre><br />
<br />
using [[Template:Numbered list demo]], gives<br />
<br />
{{Numbered list demo}}{{Numbered list demo}}<br />
{{Numbered list demo}}<br />
<br />
In a template name the character "#" and any characters after that are ignored: <nowiki>{{tc#abc}}</nowiki> gives {{tc#abc}}. This is used in {{tiw|en|hif}}.<br />
<br />
A wikitext with consecutive double opening braces and consecutive double closing braces is interpreted as containing a template parameter tag with triple braces. To avoid that, use a space in at least one of the two quadruples. For example, <nowiki>{{{{tc}}}}</nowiki> gives {{{{tc}}}}, while <nowiki>{{ {{tc}}}}</nowiki> gives {{ {{tc}}}}. <br />
<br />
With [[Special:ExpandTemplates]] one can view the expanded wikitext a template call produces, as intermediate step toward rendering. The same is also produced with a URL like {{fullurl:{{FULLPAGENAME}}|action=raw&templates=expand}}.<br />
<br />
==Use of templates across projects==<br />
A template only works when referred to from a page in the same project. To use it in another project, one has to copy it to there. [[Bugzilla:1126]] is a request to lift that restriction, i.e. allow interwiki use of templates.<br />
<br />
The adjustments needed in the copy, to work on the other project, can be reduced by using <nowiki>{{</nowiki>SERVER}}, localurl, and generic namespace names, and writing links in a way that works on multiple projects, e.g. [[m:Help:Table]]. For copying multiple templates, [[Help:Export|export]] and [[Help:Import|import]] can be helpful. It is also convenient if the template names can be the same on the other project. Therefore, when choosing template names, check which names are in use on other projects to which people might want to copy the templates. Note that if a template is referred to by something like abc<nowiki>{{</nowiki>NAMESPACE}}, a project with different namespace names requires a different template name, or a redirect.<br />
<br />
Transclusion across projects, hence changing contents from a central place, is only possible:<br />
*for content in the form of an image on Commons, to any page,<br />
*for editable content on an image page on Commons, including content transcluded from other pages on Commons, to the corresponding local image pages, if there is no local image with the same name<br />
<br />
Templates on the central Wikia work in the separate Wikia projects, provided that the prefix "wikia:" is used, see <span class="plainlinks">[http://www.wikia.com/wiki/Help:Shared_templates shared templates on wikia]</span>. (Please note that these external Wikia projects are NOT hosted and managed by the Wikimedia Foundation.)<br />
<br />
Sometimes multiple projects require pages which are partly the same and partly different. For example, on some projects "m:" is used as interwiki link to Meta, and on some projects "MetaWikipedia:". In this case a common wikitext can be used, calling project-specific templates. In the example the wikitext of the page could contain <nowiki>{{meta}}</nowiki>, and we would have on each wiki a Template:Meta containing the required prefix.<br />
<br />
==Parameters==<br />
<br />
Template parameters are either named or numbered. They are [[w:en:Parameter (computer science)#Calling conventions|called-by-value]], and therefore input parameters only.<br />
<br />
In the template ''definition'', the formal parameter (the [[w:en:Free variables and bound variables|placeholder]] for the parameter value) is a parameter name with three pairs of braces. So, for example, you would write {{{myVariableName}}} for a template parameter which you wanted to call ''myVariableName''.<br />
<br />
{{MW 1.6|(for parameters defaults)}} <br />
In the template ''call'', the syntax is either<br />
*<tt><nowiki>{{templatename|parname1=parvalue1|parname2=parvalue2}}</nowiki></tt> with tags <tt><nowiki>{{{parname1|default}}}</nowiki></tt>, <tt><nowiki>{{{parname2|default}}}</nowiki></tt>, etc. in the template, or<br />
*<tt><nowiki>{{templatename|parvalue1|parvalue2}}</nowiki></tt> with tags <tt><nowiki>{{{1|default}}}</nowiki></tt>, <tt><nowiki>{{{2|default}}}</nowiki></tt>, etc. in the template. <br />
<br />
The default (optional, together with the pipe character in front) can be different for every occurrence, and applies if no value is specified when calling the template, not to be confused with the case that the empty value is specified.<br />
<br />
A way to determine whether a parameter is defined is by comparing the results of two occurrences with different defaults, e.g. with <tt><nowiki>{{#ifeq: {{{a|+}}}|{{{a|-}}}|1|0}}</nowiki></tt>.<br />
<br />
In the case of [[Help:Substitution|page substitution]] with an undefined parameter, not the default but the parameter itself with default is substituted into the wikitext.<br />
<br />
===Example: named parameter substitution ===<br />
Let's create a template called '''Name-example''' (that is, the template will be '''[[Template:Name-example]]'''), with a parameter for the first name which we will call ''firstName'', and a parameter for the last name which we will call ''lastName''.<br><br />
<br />
Type the following in the new [[Template:Name-example]]: <br />
<br />
<pre><br />
:I am a template example, my first name is '''{{{firstName}}}''' and my last name is '''{{{lastName}}}'''.<br />
:<br />
:You can reference my page at [[{{{lastName}}}, {{{firstName}}}]].<br />
</pre><br />
<br />
On a second page, type this: <nowiki>{{Name-example}}</nowiki><br />
<br />
The result is: {{Name-example}}<br />
<br />
Because the template has no parameters.<br />
<br />
But if we type this on the second page: <nowiki>{{Name-example | firstName=John | lastName=Smith}}</nowiki> <br />
<br />
The result will looks like this:<br><br />
{{Name-example | firstName=John | lastName=Smith}}<br />
<br />
To analyse the working, one can apply [[Special:ExpandTemplates]] to see the expanded wikitext as intermediate result:<br />
<br />
<pre><br />
:I am a template example, my first name is '''John''' and my last name is '''Smith'''.<br />
:<br />
:You can reference my page at [[Smith, John]].<br />
</pre><br />
<br />
When this wikitext is applied directly the resulting rendering is the same.<br />
<br />
===Example: numeric parameter substitution===<br />
An example of how the contents of a parameter function.<br />
<br />
====The simplest case====<br />
Let us first ''define'' a template with the name ''t0'', which will <br />
*expect a single argument<br />
*give back the text of that argument, with no spaces before or after it, between "start-" and "-end":<br />
:'''<nowiki>start-{{{1}}}-end</nowiki>'''<br />
the definition of course being on page '''[[Template:t0]]'''.<br />
<br />
#Calling the template named ''t0'' with a parameter value of "''a''", i.e., <br />
#::<nowiki>{{t0|a}}</nowiki> <br />
#:gives <br />
#::"{{t0|a}}"<br />
#Calling the template named ''t0'' with a parameter value of " " (a blank space), i.e., <br />
#::<nowiki>{{t0| }}</nowiki><br />
#:gives <br />
#::"{{t0| }}" .<br />
#Calling the template named ''t0'' with a parameter value of "" (an empty string), i.e., <br />
#::<nowiki>{{t0|}}</nowiki> <br />
#:gives <br />
#::"{{t0|}}".<br />
#Calling the template named ''t0'' and not passing any parameters, i.e., <br />
#::<nowiki>{{t0}}</nowiki> <br />
#:gives <br />
#::"{{t0}}".<br />
If something like '''{{{1}}}''' or in fact any '''{{{name}}}''' is visible on an ordinary page it typically indicates that a mandatory parameter of a template used on this page isn't defined.<br />
<br />
Calling the template named ''t0'' with a parameter which consists of two newlines, i.e.,<br />
<br />
<nowiki> {{t0| </nowiki>}}<br />
<br />
gives <br />
<br />
{{t0| }}<br />
<br />
<nowiki>{{t0|</nowiki><br />
<br />
}}<br />
<br />
gives <br />
<br />
{{t0|<br />
<br />
}}.<br />
<br />
Thus, unlike in the case of parser functions, there are no complications with spaces and newlines, compare [[ParserFunctions#Conditional_whitespace|conditional whitespace]].<br />
<br />
====Declaring a default value====<br />
Now let us ''define'' a similar template with the name ''t'' which contains a single numbered parameter 1 with a default of ''pqr''. The only difference between the effects of t and t0 appears when they are called with no parameter (and no "|"):<br />
<br />
:'''<nowiki>start-{{{1|pqr}}}-end</nowiki>'''<br><br />
the definition of course being on page '''[[Template:t]]'''.<br><br />
#Calling the template named ''t'' with a parameter value of "''a''", i.e.,<br />
#::<nowiki>{{t|a}}</nowiki> <br />
#:gives <br />
#::"{{t|a}}".<br />
#Calling the template named ''t'' with a parameter value of " ", i.e.,<br />
#::<nowiki>{{t| }}</nowiki> <br />
#:gives <br />
#::"{{t| }}".<br />
#Calling the template named ''t'' with a parameter value of "", i.e.,<br />
#::<nowiki>{{t|}}</nowiki> <br />
#:gives <br />
#::"{{t|}}".<br />
#Calling the template named ''t'' with named parameter '''1=''', i.e.,<br />
#::<nowiki>{{t|1=no surprise}}</nowiki> <br />
#:gives<br />
#::"{{t|1=no surprise}}".<br />
#Calling the template named ''t'' with '''1=''' after an unnamed parameter, i.e.,<br />
#::<nowiki>{{t|no|1=surprise}}</nowiki> <br />
#:gives<br />
#::"{{t|no|1=surprise}}".<br />
#Calling the template named ''t'' with '''1=''' before an unnamed parameter, i.e.,<br />
#::<nowiki>{{t|1=no|surprise}}</nowiki> <br />
#:gives<br />
#::"{{t|1=no|surprise}}".<br />
#Calling the template named ''t'' and no parameter at all, i.e.,<br />
#::<nowiki>{{t}}</nowiki> <br />
#:gives<br />
#::"{{t}}".<br />
#Calling the template named ''t'' and no named or unnamed parameter '''1''', i.e.,<br />
#::<nowiki>{{t|2=two}}</nowiki> <br />
#:gives<br />
#::"{{t|2=two}}".<br />
<br />
===Restrictions on parameter values===<br />
* If a parameter value contains an equals sign, the parameter name must be put explicitly, even when it is 1, 2, 3, etc.<br />
<br />
* If the expression for a parameter value contains two consecutive closing braces which are not part of a variable or parameter tag, they have to be put in nowiki tags.<br />
<br />
* The expression for a parameter value cannot contain the variable localurl with query string, due to the pipe character. <br />
<br />
*A parameter value can be quite long, see [[m:Help:Long parameter demo|Help:Long parameter demo]].<br />
<br />
*A parameter value can contain pairs of square brackets or text to be used within a link, but not a closing part of one link and an opening part of another link: <nowiki>{{</nowiki>tlis|abc]]def[[ghi}} using {{timc|tlis}} gives {{tlis|abc]]def[[ghi}} rather than the expected aabc]]def[[ghib.<br />
<br />
====Pipe character====<br />
To define a parameter value containing a pipe character (|) which is not part of a template call, parser function call, piped link or image tag, use [[Template:!]] containing "<span style="background-color:#c8f0ff; padding:0 3px 2px 3px;">|</span>". Using {{tcw|t0}}, compare <nowiki>{{t0|a{{!}}b}}</nowiki> giving {{t0|a{{!}}b}}, <nowiki>{{t0|a&amp;#124;b}}</nowiki> giving {{t0|a&#124;b}} and <nowiki>{{t0|a|b}}</nowiki> giving {{t0|a|b}}. The difference between the first and the second is that in the first case the expanded wikitext is start-a|b-end, while in the second case it is start-a&amp;#124;b-end. This is rendered the same in final output but makes a difference when used in table syntax: this requires the "real" pipe character. <br />
<br />
<pre>{{x2|{{{!}} <br />
{{!}} A <br />
{{!}} B<br />
{{!}}- <br />
{{!}} C<br />
{{!}} D<br />
{{!}}}<br />
}}</pre><br />
<br />
gives<br />
<br />
{{x2|{{{!}} <br />
{{!}} A <br />
{{!}} B<br />
{{!}}- <br />
{{!}} C<br />
{{!}} D<br />
{{!}}}<br />
}}<br />
<br />
while<br />
<br />
<pre>{{x2|{&amp;#124; <br />
&amp;#124; A <br />
&amp;#124; B<br />
&amp;#124;- <br />
&amp;#124; C<br />
&amp;#124; D<br />
&amp;#124;}<br />
<br />
}}</pre><br />
<br />
gives <br />
<br />
{{x2|{&#124; <br />
&#124; A <br />
&#124; B<br />
&#124;- <br />
&#124; C<br />
&#124; D<br />
&#124;}<br />
}}<br />
<br />
and<br />
<br />
<pre>{{x2|{| <br />
| A <br />
| B<br />
|- <br />
| C<br />
| D<br />
|}<br />
}}</pre><br />
<br />
gives<br />
<br />
{{x2|{| <br />
| A <br />
| B<br />
|- <br />
| C<br />
| D<br />
|}<br />
}}<br />
<br />
===Equals sign in parameter value===<br />
When a parameter value contains an equals sign, the parameter name must be stated explicitly, otherwise the part of the parameter value before the equals sign is taken as the parameter name. If that happens accidentally, this parameter is likely to be unused, hence harmless, but the intended implicit parameter 1, 2, or 3, etc., gets no value. <br />
<br />
:Example: <nowiki>{{TTT|a=b|c}}</nowiki> {{ut1|TTT}} gives {{TTT|a=b|c}} (unused parameter a is assigned the value b, the first parameter value for which no parameter name is specified is assigned to the parameter with the implicit name "1" &mdash; it reads like so: Use template TTT, assign "b" to the parameter "a", use the value "c" for your first ''implicit'' parameter <nowiki>{{{1}}}</nowiki>.), while <nowiki>{{TTT|1=a=b|2=c}}</nowiki> gives {{TTT|1=a=b|2=c}} (the first parameter is assigned the value "a=b" &mdash; it reads like so: Use template TTT, assign "a=b" to the ''expressed'' parameter "1", assign "c" to the ''expressed'' parameter "2"). <nowiki>{{TTT|1=a=b|2=c|d}}</nowiki> gives {{TTT|1=a=b|2=c|d}}, "d" is assigned to "1" as first ''implicit'' parameter, overwriting the value "a=b".<br />
<br />
A parameter definition (between pipe characters or a pipe character and template end tags) may depend on a template, parser function, variable, or template parameter. The explicit or implicit name of the parameter is determined after expansion. For example, a template call <nowiki>{{t2|{{{a}}}}}</nowiki> assigns the value of {{{a}}} to implicit parameter 1 if that value does not contain an equals sign, but if it has the value "b=c", c is assigned to b. If we anyway want to assign the value of {{{a}}} to 1 we have to use an explicit parameter 1: <nowiki>{{t2|1={{{a}}}}}</nowiki>.<br />
<br />
Compare:<br />
<br />
*<nowiki>{{t2a1|1=x=y}}</nowiki> (using {{tcw|t2a1}}) gives {{t2a1|1=x=y}}.<br />
*<nowiki>{{t2a2|1=x=y}}</nowiki> (using {{tcw|t2a2}}) gives {{t2a2|1=x=y}}.<br />
<br />
Similarly, parameter definition {{{a}}}=b where {{{a}}} has value "c=d" results in "d=b" being assigned to c, for example:<br />
*<nowiki>{{t5|a=2=d}}</nowiki> (using {{tcw|t5}}) gives {{t5|a=2=d}}.<br />
<br />
===Mix of named and unnamed parameters===<br />
In the case of a mix of named and unnamed parameters in a template tag, the unnamed parameters are numbered 1,2,3,.., so they are ''not'' numbered according to the position in the mixed list as a whole.<br />
<br />
For example, <nowiki>{{</nowiki>t sup|3=1|2|1=3|4|5|6|7}} using {{tcw|t sup}} gives {{t sup|3=1|2|1=3|4|5|6|7}}.<br />
<br />
===When parameters do not expand===<br />
{{MW 1.6|(for parameters defaults)}}<br />
Parameters do not get expanded when they are inside tags (HTML, wiki, or extension),<br />
or between <nowiki><html></html></nowiki> tags<br />
<br />
The following will not work within a template, because the parameter is not expanded<br />
<br />
<nowiki><br />
<myextension xparam={{{tparam}}}> ... </myextension><br />
<html><span onmouseover="return escape('foobar')"> {{{1}}} </span></html><br />
</nowiki><br />
<br />
This continues to be true into version 1.8.2, though [[Template:Hidden]] provides a puzzling exception. Any explanation?<br />
<br />
==Template mechanism==<br />
The template mechanism involves the following steps:<br />
<br />
*The pipe characters in template calls determine the separation into template name and parameter definitions. This separation does not depend on possible pipe characters in the expanded form of the text between the opening and closing braces of the template. For example, <nowiki>{{ {{t6}} }}</nowiki> using {{tcw|t6}} gives {{ {{t6}} }}, not the result of <nowiki>{{ t2demo|a }}</nowiki> which is {{ t2demo|a }}. This is because "t2demo|a" is not a valid template name (not to be confused with a template with a valid name that does not exist), so the template call is not expanded.<br />
<br />
::Note that in this case partial or successive substitution does not give the same result as without substitution: <nowiki>{{ {{subst:t6}} }}</nowiki> gives the wikitext <nowiki>{{ t2demo|a }}</nowiki>, rendered as {{ t2demo|a }}.<br />
<br />
*The template name and each of the parameter definitions is evaluated. The leftmost equals sign, if any, in each parameter definition separates the parameter name from the parameter value.<br />
*The values are assigned to the parameters from left to right (the result can not be directly viewed), meaning that a named or numbered parameter may be specified several times, the last one being the actual value that will be kept when passing the parameter during the final instantiation of the template below.<br />
*Template calls are replaced by template content, where the parameter tags with matching names are replaced by their values or defaults (the result of this step can be viewed by applying subst either again, or directly to the template and the variables).<br />
<br />
The process is applied recursively until there are no more template calls to replace.<br />
<br />
All whitespaces before and after a parameter value are ignored if "=" is used.<br />
<br />
:<nowiki>"{{t|1= a}}"</nowiki> gives "{{t|1= a}}".<br />
:<nowiki>"{{t|1=a }}"</nowiki> gives "{{t|1=a }}".<br />
:<nowiki>"{{t| a}}"</nowiki> gives "{{t| a}}".<br />
:<nowiki>"{{t|a }}"</nowiki> gives "{{t|a }}".<br />
<br />
A parameter value can contain a piped link; the "|" in such a link is not taken as parameter separator.<br />
<br />
:Example: <nowiki>"{{t|[[a|b]]}}"</nowiki> gives "{{t|[[a|b]]}}".<br />
:Example: <nowiki>"{{t|[[a|b]] }}"</nowiki> gives "{{t|[[a|b]] }}".<br />
<br />
(In this case the space ''has'' effect.)<br />
<br />
On rendering, surplus parameter values (including named parameters that do not occur in the template) are ignored: <nowiki>{{t|a|b}}</nowiki> gives {{t|a|b}}.<br />
<br />
Parameters without names (i.e. that don't contain an equal sign) are numbered implicitly starting by 1, from left to right.<br />
<br />
:Example: <nowiki>"{{t|a|b|c}}"</nowiki> is equivalent to <nowiki>"{{t|1=a|2=b|3=c}}"</nowiki><br />
<br />
Numbered parameters can also be skipped or can be specified in alternate order by numbering them explicitly.<br />
<br />
:Example: <nowiki>"{{t|3=c|2=b|1=a}}"</nowiki> is equivalent to <nowiki>"{{t|1=a|2=b|3=c}}"</nowiki><br />
:Example: <nowiki>"{{t|a|b|c|10=j}}"</nowiki> is equivalent to <nowiki>"{{t|1=a|2=b|3=c|10=j}}"</nowiki><br />
<br />
This also makes it possible to apply a default value for parameter 1, while specifying a value for parameter 2:<br />
<br />
<nowiki>{{t2d|2=a}}</nowiki>, using {{timc|t2d}}, gives {{t2d|2=a}}.<br />
<br />
Template calls can contain multiple occurrences of the same named parameter, and a numbered parameter can be specified multiple times by using its number explicitly. The effective value of parameters is the value of the last occurrence (from left to right) of the parameter with the same name, once the parameter names have been evaluated.<br />
<br />
:Example: <nowiki>"{{t|a|b|c|2=B}}"</nowiki> is equivalent to <nowiki>"{{t|a|B|c}}"</nowiki><br />
<br />
The final list of formal parameters before the template itself is instantiated is then unordered because the list is indexed by the evaluated parameter named (this list is an [[:en:Associative array|associative array]]).<br />
<br />
When [[m:ParserFunctions|ParserFunctions]] were not available yet, multiple assignments of parameters with the same name (and thus allowing parameter overrides) were ingeniously used to perform branching, e.g. in the now deleted [[:en:Template:If defined]]. <br />
<br />
See also [[Help:Parameter default]].<br />
<br />
== Template tag lay-out ==<br />
<br />
To have a desired template tag lay-out, especially in the case of many parameters, additional dummy parameters can be used with a newline, spaces, and/or comments. In the case of unnamed parameters, this means that some parameter numbers are not used in the template content, so that their values, present in the template tag, do not affect the rendering of the template. For example, using {{Tcw|t3d}},<br />
<br />
<pre><br />
{{t3d |a|b|c| 1<br />
|d|e|f| 2<br />
|g|h|i| 3<br />
}}<br />
</pre><br />
<br />
gives:<br />
<br />
{{t3d |a|b|c| 1<br />
|d|e|f| 2<br />
|g|h|i| 3<br />
}}<br />
<br />
If parameters are named, dummy parameters can easily be inserted at any time. If they are unnamed, then, to avoid renumbering, one can insert named parameters: any text including an equals sign will do, if the text on the left is not one of the parameter numbers: this text is interpreted as the name of an unused parameter, hence ignored.<br />
<br />
Example:<br />
<br />
Using {{tim|Chess position}}<br />
<br />
<pre><br />
{{chess position|=<br />
<br />
8 |rd|nd|bd|qd|kd|bd|nd|rd|=<br />
7 | |pd|pd|pd|pd|pd|pd|pd|=<br />
6 |pd| | | | | | | |=<br />
5 | | | | | | | | |=<br />
4 | |pl| | | | |pl| |=<br />
3 | | | | | | | |bl|=<br />
2 |pl| |pl|pl|pl|pl| |pl|=<br />
1 |rl|nl|bl|ql|kl| |nl|rl|=<br />
a b c d e f g h<br />
<br />
|30}}<br />
</pre><br />
<br />
which gives<br />
<br />
{{chess position|=<br />
<br />
8 |rd|nd|bd|qd|kd|bd|nd|rd|=<br />
7 | |pd|pd|pd|pd|pd|pd|pd|=<br />
6 |pd| | | | | | | |=<br />
5 | | | | | | | | |=<br />
4 | |pl| | | | |pl| |=<br />
3 | | | | | | | |bl|=<br />
2 |pl| |pl|pl|pl|pl| |pl|=<br />
1 |rl|nl|bl|ql|kl| |nl|rl|=<br />
a b c d e f g h<br />
<br />
|30}}<br />
<br />
In this example, the 1 to 8 row numbers and a to h column numbers (as well as their surrounding spaces and newlines) in the parameter list are hidden within a dummy parameter (with an empty name before the equal sign).<br />
<br />
The template generates a HTML table where each cell contains an image whose name is dynamically generated from the 64 first automatically numbered parameters (there are intermediate parameters within the numbered list, but as these dummy parameters are named explicitly, they don't increment the parameter number used to generate default parameter names. So the parameter with autogenerated name "1" effectively contains the "rd" value).<br />
<br />
The template is then called with a parameter list that contains:<br />
* 65 parameters automatically named from "1" to "65" (64 parameters for the cells content, and the 65th for the image width),<br />
* and a dummy named parameter (whose name is an empty string, and whose effective value results from the last assignment with the chessboard column names a to h and the surrounding spaces and newlines), which is not used in the internal template content.<br />
<br />
Note also that all parameters are trimmed, so the parameter with autogenerated name "9" (at position a7 on the chessboard above) is assigned the empty string value.<br />
<br />
==Template page==<br />
Without noinclude and includeonly parts the following are identical:<br />
*the rendering of the wikitext of the template (this is on the template page, and would be the same in other pages with that wikitext, except for page-dependent variables)<br />
*the rendering of the template on a page that calls it without parameters<br />
<br />
Thus the defaults are shown, e.g. {{timc|T 1}} shows the same as <nowiki>{{</nowiki>t 1}}: "{{t 1}}".<br />
<br />
===Template page if no defaults have been specified===<br />
In simple cases this corresponds to treating the parameter tags as ordinary text, for example:<br />
<br />
<nowiki>"{{t2demo}}"</nowiki> (using [[Template:t2demo]] containing {{msgnw:t2demo}}) gives {{t2demo}}<br />
<br />
Similarly, if part of the parameters is undefined, only those show up as {{{''parameter number or name''}}}. <br />
<br />
However, some templates produce an error message when called without parameters, so unless includeonly is used (see below) the template page also shows this message, suggesting that there is something wrong with the template. For example, a template that doubles parameter {{{1}}} with the wikitext <nowiki>{{#expr:2*{{{1}}}}}</nowiki> gives {{#expr:2*{{{1}}}}}. In such cases includeonly can be used to avoid uninformative and messy rendering on the template page, but either way a disadvantage during template development is that preview does not (meaningfully) reflect changes in the parts of the page outside the noinclude tags (i.e. the included parts). Therefore it can be useful to provide representative default values, even if that is only done temporarily during development of the template.<br />
<br />
Note also that variable tags are not shown, but evaluated.<br />
<br />
With noinclude an informative template page can be produced, containing more demos and test cases than just the single default set. Typically, the noinclude-part of a template page contains examples including or [[Help:substitution|substituting]] the template. Changes in the working of the template (i.e. changes outside the noinclude-part) are not yet effective in these examples in preview and, in the case of [[Help:substitution|substitution]], in "show changes".<br />
However, they are reflected in the rendered page after saving.<br />
<br />
Some formatting aspects may show up which are not readily seen from the edit box.<br />
<br />
==A parameter value depending on parameters==<br />
As mentioned above, if a parameter is left undefined, the triple braced parameter name in the result does not function as a parameter if the page is called as a template from another page; if it should, do not omit the parameter value but specify it in terms of a parameter of the calling page; compare:<br />
*<nowiki>{{t2ademo|b}}</nowiki> (using [[Template:t2ademo]] containing {{msgnw:t2ademo}}) gives {{t2ademo|b}}<br />
*<nowiki>{{t2a1|b}}</nowiki> (using [[Template:t2a1]] containing {{msgnw:t2a1}}) gives {{t2a1|b}}.<br />
*Similarly, <nowiki>{{t2a2|b}}</nowiki> (using [[Template:t2a2]] containing {{msgnw:t2a2}}) gives {{t2a2|b}}. See also below.<br />
<br />
The most straightforward way of expressing a parameter value in terms of a parameter is using the same name and making it equal, e.g. <nowiki>{{</nowiki>Lan is|lr=af|le={{{le}}}}} in [[Template:Lan is mr]].<br />
<br />
==Empty vs. undefined==<br />
<nowiki>{{t2demo||a}}</nowiki> makes the first parameter equal to the empty string rather than leaving it undefined: it gives {{t2demo||a}}. By treating the second unnamed parameter as a parameter with the name "2", the first unnamed parameter can be left undefined.<br />
<br />
:Example: <nowiki>{{t2demo|2=a}}</nowiki> gives {{t2demo|2=a}}.<br />
<br />
If the parameter is used in a tag like <nowiki><font size></nowiki> the default text may give invalid code that is conveniently ignored, rather than resulting in perhaps ugly code being rendered (but this may depend on the browser). See e.g. [[Template talk:Fontsize]].<br />
<br />
Parameter names (as opposed to template names) are case-sensitive, even with respect to the first letter, and spaces are distinguished from underscores. The [[w:en:String_%28computer_science%29#Formal_theory|empty string]] is also a valid parameter name, see [[Template:T empty string as parameter name]].<br />
<br />
Parameter 02 is distinguished from parameter 2: using {{timc|t pl0}}, <nowiki>{{</nowiki>t pl0|5|6|7}} gives {{t pl0|5|6|7}} <br />
<br />
Note that parameters in the [[MediaWiki namespace]] (interface messages) are written differently: as $1, $2, etc., see [[Meta-Wikimedia:MediaWiki namespace text]].<br />
<br />
==msgnw==<br />
<br />
The prefix '''msgnw''' (short for "message, nowiki") is used to display the uninterpreted wikitext of a template (the same thing you'd see if you were editing the page) on another page. An exception is that numbered and unnumbered lists are rendered as such instead of displaying # or * signs. Parameter values are ignored.<br />
<br />
With the introduction of noinclude and includeonly tags, allowing template pages to take care of definition as well as displaying information, msgnw displays no longer just the technical information about what the template does when included, but a mix of that with wikitext for rendering the template page itself, with the tags. This limits the usefulness of applying this.<br />
<br />
Examples:<br />
<br />
[[Template:en]]<br />
*<nowiki>{{msgnw:en}}</nowiki> gives {{msgnw:en}} <br />
*<nowiki>{{en}}</nowiki> gives {{en}}<br />
<br />
{{tim|t}}<br />
<br />
<nowiki>{{msgnw:t|a}}</nowiki> gives <br />
*{{msgnw:t|a}} <br />
<br />...which is much more than just the formal info about what the template does when included:<br />
*<nowiki>start-{{{1|pqr}}}-end</nowiki><br />
<br />
[[Template:Numbered list demo]]<br />
<br />
<nowiki>{{msgnw:Numbered list demo}}</nowiki> gives:<br />
{{msgnw:Numbered list demo}} <br />
<br />
<nowiki>{{Numbered list demo}}</nowiki> gives:<br />
{{Numbered list demo}}<br />
<br />
The edit box for [[Template:Numbered list demo]] shows:<br />
<pre><br />
#Amsterdam<br />
#Rotterdam<br />
#The Hague<br />
</pre><br />
<br />
==Usage==<br />
<br />
Templates are useful for any text for which one wants a copy in two or more pages, and there is no need for each copy to be edited independently to adapt it to the page it is in. Since parameters can be used, versions may to that extent even be different, and parameter values can be edited independently for each. Templates are not only convenient, but they can also "force" a useful uniformity. See also [[w:en:Subroutine|advantages of subprograms]].<br />
<br />
Typical applications are:<br />
*[[w:Wikipedia:Template messages|template messages]] such as [[w:en:Template:stub]]<br />
*[[m:help:Navigational template|Navigational template]]s such as [[w:en:Template:europe]], sometimes listed in a directory such as [[w:Wikipedia:navigational templates]]<br />
*[[w:Wikipedia:Infobox|infoboxes]], each time showing the same kind of information in the same format, but each time for a different case, using parameters, e.g. the [[w:en:Template:Infobox Countries]].<br />
*provide cross-language portability of texts which are largely internationally the same, but contain some standard terms different in each language; the standard terms are replaced by {{..}} referring to template pages which have the same name but localised content in each language. This is [[m:Using templates in Wiktionary|applied in Wiktionaries]] for names of languages, terms like "noun", etc.; it is also [[w:Wikipedia:Template messages#Taxobox_components_.28Taxons.29|applied for taxoboxes]], see e.g. [[w:en:Template:Familia]] and [[w:fr:Modèle:Familia]].<br />
*allow a composite image, composed of a table of images, to be specified by a template tag which itself has a corresponding table-like lay-out, see [[w:Template:Chess position]] and [[w:Template:Game of Go Position]] (the latter example also shows that the number of parameters a template can have is quite large, in this case 362). Newlines in parameter values provide the lay-out of the template tag, but they are not allowed in image names, therefore they are put within comment tags; alternatively, dummy parameters could be used on these positions.<br />
<br />
Various combinations are possible. E.g., the last two could be combined, so that e.g. every language version of Wikipedia has the same Infobox Countries template (for each project a copy, because the template mechanism can not import across projects), which has parameters for the data, and refers to templates with translations of standard terms.<br />
<br />
See also '''[[Help:Advanced templates]]'''.<br />
<br />
===Composite pages===<br />
The wikitext of a page may (partly or fully) consist of tags for the inclusion of component pages. The "templates" are not necessarily in the template namespace, and may be more or less self-contained pages by themselves. An advantage of putting the components in the template namespace is that they are then included in the list of templates used on the composite page, all with links, on its edit page. On the other hand, the component page may, by itself, be of a nature that it belongs in e.g. the main namespace, while the prefix would suggest otherwise; also the prefix would clutter the pagename.<br />
<br />
Examples are:<br />
*[[m:Help:A simple composite example]]<br />
*[[w:Wikipedia:Village pump]] with six component pages, e.g. [[w:Wikipedia:Village pump (technical)]]<br />
*daily a page like [[w:en:Wikipedia:Votes for deletion/Log/2005 May 31]] where each component page consists of the discussion on the deletion of one Wikipedia page, e.g. [[w:en:Wikipedia:Votes for deletion/Sp3tt]] (for this day there are 75 of such component pages)<br />
*[[m:Meta:Translation/Coordination]], mainly containing <br />
**[[m:Meta:Translation/Coordination/List/Meta]]<br />
**[[m:Meta:Translation/Coordination/List/Main]]<br />
*[http://en.wikipedia.org/w/index.php?title=2005_English_cricket_season_%281-14_June%29&diff=27917447&oldid=27330886] - rejection of composite page by w:en<br />
<br />
This allows the user the choice between viewing the component pages separately or combinedly. One may want to view a page separately if one has a slow connection; also sometimes people have sentimental reasons for having a separate page about a topic, e.g. a village. Viewing the combined page is much more convenient if there are many small component pages; even if a subbtopic page does not provide additional info, if it exists anyway, and is linked to, it is useful to display the content (making clear that the whole content is shown), it saves the trouble of checking the contents by following the link.<br />
<br />
In the latter case the search function of the browser can be used for searching in the combined page. Similar to the section editing feature, it allows editing a component page; however, there is no possibility to have the combined wikitext in the edit box.<br />
<br />
Edit history, recent changes, watching pages, and "what links here" work separately for the component pages and the ''composition'' page, not for the ''composite'' page. Related changes works for the component pages and for the composite page. Page protection can be set for selected component pages and for the composition page, not directly for the composite page.<br />
<br />
The talk page of a composition page is used to talk about the composition and the page in general, and could in addition be a composite page of the talk pages of the component pages.<br />
<br />
A composite page has an integrated TOC and section numbering; the numbering is not reset for each component page.<br />
<br />
Editing a section of a component page can be done directly from the composite page, see [[Help:Section#Editing sections of included templates|editing sections of included templates]]. After saving, one ends up at the page for the component page to which the section belongs.<br />
<br />
On projects with the [[Help:Interwiki linking#Interlanguage_link_.28software_feature.29|interlanguage link feature]] the composite page shows the combined interlanguage links of all component pages, hence possibly multiple links for one language or even for one page.<br />
<br />
For easy access to the component pages, links to them on the composite page (for example by self-links on the component pages) are convenient. Alternatively, access is through section editing, or, if the component pages are in the template namespace, through the list of templates called from the composite page, at its edit page.<br />
<br />
Conversely, for easy access from a component page to the composite page(s) that call(s) it (if there are not too many of them) it is convenient to link the component page to them (on a composite page one becomes a self-link).<br />
<br />
See also [[w:Wikipedia talk:Template namespace#transcluding prose]].<br />
<br />
===Pages with a common section===<br />
A section on the relationship of the subjects A and B, or a subtopic equally relevant for A as for B, can be put both in page A and in page B, by making it a separate page C, called as a template from A and B.<br />
<br />
Remarks:<br />
*For readers reading both A and B, it is useful that the duplication be indicated by a message or a special lay-out; otherwise it is confusing and inconvenient. One can for example use {{tim|cs}}: {{cs|Help:Template}}<br />
*After saving one ends up viewing the template page. For easy access to the calling pages it is convenient to link the called page to them (on a calling page one becomes a self-link). This may well be integrated in the message about the duplication. It is even more convenient than the two-step link as shown above.<br />
*The section level of the embedded section(s) has to be the same in each embedding page. The same applies to lay-out and style.<br />
*Pages like C can be put in<br />
**the same namespace as A and B; advantage:<br />
***the kind of content of C is the same as that of A and B<br />
**the template namespace; advantages:<br />
***C appears in the list of templates called from A and B, at their edit pages<br />
***C by itself may not satisfy the standards for pages in the namespace of A and B, such as providing context (however, the message about the duplication explains it)<br />
<br />
Examples:<br />
*{{pim|Help|Editing sections of included templates}}<br />
*{{pim|Help|Alphabetic order}}<br />
<br />
For various remarks which also apply here, see also the previous section.<br />
<br />
===Repetition within a page===<br />
For a succession of similar pieces of content, as in a list, a computer program would use a [[w:en:Conditional_branching#Loops|loop]]. What comes closest in MediaWiki is putting the loop body in a template, and calling the template repeatedly, usually with a varying parameter value. This is somewhat primitive for a loop:<br />
*instead of "for i=1 to 5" we need to enumerate the values 1, 2, 3, 4, 5; on the other hand, this gives the versatility to use just as easily less regular values such as de, en, fr ([[w:en:Conditional_branching#Collection-controlled_loops|collection-controlled loop]]).<br />
*repetition of code is minimized by the template, but the template call itself has to be repeated each time (but see also the next section)<br />
<br />
Example:<br />
*[[Template:List of Languages]] - the "loop body" is in [[Template:Lang def]]; compared with putting the content of the latter directly in the list the advantage is that the variable part (the value of "code") occurs once each time in the code, although it is used twice. This is important because the fixed part of the list item code can be copied while the variable part is typically inserted manually.<br />
<br />
For repetition of the same text the loop body can be a parameter, e.g. [[Template:X5]] (see [http://meta.wikimedia.org/w/index.php?title=Special%3AAllpages&from=X&namespace=10 list]).<br />
<br />
A double loop is achieved by a second template that repeatedly calls the first. Similarly for a triple loop, etc. See e.g. [[w:Template:Ld]], [[w:Template:L2d]], and [[w:Template:L3d]].<br />
<br />
An example where the same template is used for different loop levels is [[Template:Loop 2]]. Because the software has a built-in protection against infinite nesting (if there is, there will be an error e.g. <code>Fatal error: Maximum execution time of 30 seconds exceeded in /w/includes/Parser.php on line 775</code>), a redirect is used for each level. The number of levels that the template can handle is determined by the number of parameters specified in the two template calls it comprises (because going up a level requires an extra parameter) and the number of existing redirects.<br />
<br />
Similarly [[Template:Lanlp 1]] is used for both the inner and the outer of a double loop. Adding an item (here a language) adds to each row and also adds an extra row.<br />
<br />
'''Providing effective repetition without repetition of similar template calls in the wikitext'''<br />
<br />
A technique for repetition of similar template calls without actually putting this list in the wikitext is demonstrated in {{tim|for}}, and a more primitive method described below.<br />
<br />
Example {{ut1|t2}}:<br />
<br />
<nowiki>{{for|call=t2|pc1=constant|abc|def|ghi}}</nowiki> gives:<br />
<br />
{{for|call=t2|pc1=2=constant|abc|def|ghi}}<br />
<br />
Description of the old {{tim|List of template calls}}:<br />
<br />
For an arbitrary template with up to three nameless parameters, it is equivalent to calling the template repeatedly, with the first parameter varying, and the possible other parameters fixed: one specifies the name, the values of the fixed parameters, and the list of values the first parameter should have in consecutive template calls, with a sequential number each, and ending with "end". The technique requires redirects like [[Template:List of template calls 3]], as many as the maximum number of repetitions.<br />
<br />
If e.g. the second parameter varies, or two parameters, then a similar template can be made, but each version requires its own set of redirects.<br />
<br />
Example {{ut1|t2}}:<br />
<br />
<nowiki>{{List of template calls|t2|constant||abc|1|def|2|ghi|end|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||}}</nowiki><br />
<br />
gives:<br />
<br />
{{List of template calls|t2|constant||abc|1|def|2|ghi|end|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||}}<br />
<br />
The empty parameters are needed in accordance with the maximum number of parameters the repeated template can have (currently three) and the maximum number of repetitions. Putting more empty parameters than needed at the end does not matter, but the number of empty parameters in the beginning of the list should be correct.<br />
<br />
==Ambiguity of a reference to "this page"==<br />
If a page is included in another page, a reference to "this page" on the included page is ambiguous. Use noinclude or includeonly tags depending on what is meant. Alternatively, mention the page name explicitly, without using <nowiki>{{</nowiki>PAGENAME}}.<br />
<br />
==Internal links==<br />
<br />
In the case of an internal link in a template with the target depending on a parameter, and in the case of a link with the target depending on a template, existence detection works as usual. <br />
<br />
Examples:<br />
<br />
*<nowiki>{{tli|insert in target|insert in label}}</nowiki> {{ut1|tli}} gives {{tli|insert in target|insert in label}}<br />
*<nowiki>[[a{{tciit}}b|c{{tciil}}d]]</nowiki> {{ut2|tciit|tciil}} gives [[a{{tciit}}b|c{{tciil}}d]]<br />
<br />
*<nowiki>{{tli|insert also in target|insert in label}}</nowiki> (using [[Template:tli]]) gives {{tli|insert also in target|insert in label}} {{ne}}<br />
*<nowiki>[[a{{tciit}}e|c{{tciil}}d]]</nowiki> (using [[Template:tciit]] and [[Template:tciil]]) gives [[a{{tciit}}e|c{{tciil}}d]] {{ne}}<br />
<br />
*<nowiki>{{la|Help:Tabl|tabl}}</nowiki> {{ut1|la}} gives: {{la|Help:Tabl|tabl}}<br />
<br />
*[[Template:Pvn]]<br />
<br />
==Templates and external links==<br />
<br />
Examples:<br />
<br />
*<nowiki>{{tle|insert in target|insert in label}}</nowiki> {{ut1|tle}}} gives {{tle|insert in target|insert in label}}<br />
*<nowiki>{{tle2|insert in target}}</nowiki> {{ut1|tle2}}} gives "{{tle2|insert in target}}"; note that brackets separated from the http:// are not recognized as belonging together:<br />
**<nowiki>[{{tle2|insert in target}} label]</nowiki> gives [{{tle2|insert in target}} label]<br />
**<nowiki>[{{tle2|insert in target}}]</nowiki> gives [{{tle2|insert in target}}]<br />
*<nowiki>{{tle3|insert in target}}</nowiki> {{ut1|tle3}}} gives {{tle3|insert in target}}<br />
*<nowiki>[http://a{{tciit}}b c{{tciil}}d]</nowiki> gives [http://a{{tciit}}b c{{tciil}}d]<br />
*<nowiki>http://a{{tciit}}b</nowiki> gives "http://a{{tciit}}b"<br />
*<nowiki>[http://a{{tciit}}b]</nowiki> gives [http://a{{tciit}}b]<br />
<br />
However, a URL can not be composed of:<br />
*a first part in a parameter and a second part added by the template (although we have seen above that reversed it works: a second part in a parameter and a first part prefixed by the template) <br />
*a first part in a template and a second part after the template (although we have seen above that reversed it works: the second part in a template and the first part before the template) <br />
<br />
Example of first restriction:<br />
<br />
*<nowiki>{{tae|http://www.}}</nowiki> {{ut1|tae}}} gives {{tae|http://www.}}<br />
<br />
Examples of second restriction:<br />
<br />
*<nowiki>[{{th}}add at the end]</nowiki> {{ut1|th}}} gives [{{th}}add at the end]<br />
*"<nowiki>{{th}}add at the end</nowiki>" gives "{{th}}add at the end"<br />
<br />
==Noinclude and includeonly==<br />
<br />
This feature is not available before version 1.6.<br />
<br />
Anything between <nowiki><noinclude> and </noinclude></nowiki> will be processed and displayed only when the page is being viewed directly; it will not be included or substituted.<br />
Possible applications are:<br />
<br />
# Categorising templates, see [[Help:template documentation|template documentation]].<br />
# [[Help:Interwiki_linking|Interlanguage link]]s to similar templates in other languages.<br />
# Pages in the [[Help:MediaWiki namespace|MediaWiki namespace]].<br />
<br />
<nowiki>The converse is <includeonly>. Text between <includeonly> and<br />
</includeonly></nowiki> will be processed and displayed only when the page is<br />
being included. Applications include:<br />
<br />
# Adding all pages containing a given template to a category, but not the template itself.<br />
# Avoiding messy rendering on the template page, e.g. {{evaldemo|#expr:{{{1}}}}}.<br />
<br />
Note that spaces and newlines between the general content and the tagged part belong to the general content. If they are not desired the include tag should directly follow the content on the same line:<br />
&lt;noinclude&gt;this is &lt;/noinclude&gt;fine&lt;includeonly&gt;, closing tags are<br />
&lt;/includeonly&gt;&lt;noinclude&gt;<br />
less critical, but must be specified.&lt;/noinclude&gt;<br />
<br />
Attempts to nest split pairs of these tags, or the similar <tt>&lt;nowiki&gt;</tt> and <tt>&lt;/nowiki&gt;</tt> pair, won't work as expected. If say <tt>&lt;nowiki&gt;</tt> begins within the general content,<br />
or in a "noinclude" part, or in an "includeonly" part, then it also has to be closed within the same part.<br />
<br />
The code <code><nowiki>~<includeonly>~</includeonly>~~</nowiki></code> will be displayed as <nowiki>~~~</nowiki> when the template is not included, <nowiki>~~~~</nowiki> when the template is included, and it will be expanded as the active user when the template is subst'd.<br />
<br />
== Wiki markup at the beginning of a template==<br />
If the first included character of a template is one of the Wiki markup characters '''<tt>:;*#</tt>''', then it's interpreted as being at the begin of the line (even when the template call is not).<br />
<br />
To avoid this effect use <tt>&lt;nowiki&gt;#&lt;/nowiki&gt;</tt> or a [[w:en:Numeric character reference|NCR]] like say <tt>&amp;#58;</tt> for a colon, this NCR is also useful in conjunction with definition [[Help:list|list]]s.<br />
<br />
==Substitution==<br />
<br />
:''Main article: '''[[Help:Substitution]]'''''<br />
<br />
Putting "subst:" after the double opening braces causes an [[Help:Automatic conversion of wikitext|automatic conversion of wikitext]] when the referring page is saved: the subst tag is replaced by the wikitext of the template, with the parameter values substituted for the parameters.<br />
<br />
==Redirection==<br />
<br />
When a page called for inclusion is a redirect page, the redirect target is included instead. As usual, a double redirect does not work.<br />
<br />
A page that consists of nothing else than the inclusion of another page as a template, shows similarities to a redirect to that other page, but also many differences, including:<br />
<br />
*the result has as header the name of the referring page<br />
*there is no redirect message<br />
*the buttons such as edit (for editing the whole page), watch, talk, history, "what links here", and "last modified", etc., refer to the referring page (to go to the target page, a section edit link can be used, from there the whole page can be accessed)<br />
*the referring page is in the same categories as the target page, except when includeonly and/or noinclude tags are used.<br />
*"double redirects", with one or both being this kind of "pseudo-redirect", work.<br />
<br />
Compare [[Help:Template namespace]] with [[Help:Template namespace - demo of alternative for redirect]].<br />
<br />
In a page that in turn includes such a referring page there is no difference.<br />
<br />
<br />
Note that embedding works for all pages where [[Help:Redirect|redirecting]] works, and it also fails for all pages where a redirect won't work.<br />
<br />
==Comparison of linking and embedding==<br />
Linking and embedding have in common:<br />
*if the page does not exist, a link to the edit page is shown; the links are identical if it is not a piped link; the link does not show parameters and does not show whether, after creation, the new page will be linked or embedded.<br />
*the name can depend on variables and parameters<br />
<br />
==Predefined templates==<br />
[[Help:Variable|Variable]]s and [[help:parser function|parser function]]s can be considered predefined templates. They do not have a page that defines in terms of wikitext what they do, because their action is something extra that cannot be constructed from more basic wikitext functionality.<br />
<br />
Some additional differences:<br />
*Parser functions use ":" instead of the first "|".<br />
*An edit page does not list predefined templates used on the page.<br />
*No "What links here" is available for predefined templates, to find the pages where they are used.<br />
*Apart from #switch, predefined templates don't allow you to define named parameters, and therefore equal signs generally have no special effect, comparison:<br />
*:<tt>{&#123; #if: not blank | 2=abc &#125;}</tt> gives '''{{ #if: not blank | 2=abc }}'''<br />
*:<tt>{&#123; ifdef | not blank | 2=abc &#125;}</tt> gives '''{{ ifdef | not blank | 2=abc }}'''<br />
*It's however possible to corrupt the value shown for undefined parameters without default, for more examples see {{tim|ifeq demo}}:<br />
*:<tt>{&#123; #if: {&#123;ns:0&#125;} | 2=xy | {&#123;{2|blank}&#125;} &#125;}</tt> gives '''{{ #if: {{ns:0}} | 2=xy | {{{2|blank}}} }}'''<br />
*:<tt>{&#123; #if: {&#123;ns:0&#125;} | 2=xy | {&#123;{2 }&#125;} &#125;}</tt> gives '''{{ #if: {{ns:0}} | 2=xy | {{{2 }}} }}'''<br />
*:<tt>{&#123; #if: {&#123;ns:0&#125;} | oops | {&#123;{1|blank}&#125;} &#125;}</tt> gives '''{{ #if: {{ns:0}} | oops | {{{1|blank}}} }}'''<br />
*:<tt>{&#123; #if: {&#123;ns:0&#125;} | oops | {&#123;{1 }&#125;} &#125;}</tt> gives '''{{ #if: {{ns:0}} | oops | {{{1 }}} }}'''<br />
<br />
Ordinary and predefined templates have in common that their parameter values can depend on ordinary and predefined templates. In the case of named parameters, the names used in the template call can also depend on ordinary and predefined templates. This applies also for the named parameters of #switch.<br />
<br />
==Code execution==<br />
"Evaluating" a template call internally involves, to start with, evaluating the template name, the parameter names, and the parameter values. Evaluating a predefined template involves the same, as far as applicable. This is relevant even if the wikitext resulting from these subevaluations cannot have effect on the overall wikitext, as in the case of #ifexpr etc. for either the then-part or the else-part, and in the case of an unused template parameter:<br />
<br />
*Subevaluations involving template calls add to the pre-expand include size (see [[w:Wikipedia:Template limits]]).<br />
*[[w:Side effect (computer science)|Side effects]]:<br />
**Subevaluations producing links add on the target page to the list of incoming links ([[Help:What links here|What links here]]), based on the [[mw:pagelinks table|pagelinks table]], even if there is no link on the resulting page.<br />
**Subevaluations involving template calls add on the template page in "What links here" and on the edit page of the page concerned to inclusion items, based on the [[mw:templatelinks table|templatelinks table]].<br />
**Some extensions may perform some action during a subevaluation, e.g. with [[VariablesExtension]] a subevaluation may involve assignment of a value to a variable. <br />
<br />
Thus <nowiki>{{ #ifexpr:.. | {{a|</nowiki>''parameters''}} | <nowiki>{{</nowiki>b |''parameters''}} }} evaluates <nowiki>{{a|</nowiki>''parameters''}} ''and'' <nowiki>{{b|</nowiki>''parameters''}} regardless of the condition. On the other hand, <nowiki>{{ {{</nowiki>#ifexpr:..|a|b}} | ''parameters'' }} just evaluates the expression for the template ''name'' (by evaluating the condition, and resulting in a or b) and the parameters, and the actually included template.<br />
<br />
See also [[ParserFunctions#Code_execution]].<br />
<br />
==Templates in different versions of MediaWiki==<br />
<br />
===Version 1.6===<br />
<br />
* More magic words and the [[Help:parameter default|parameter default]] mechanism were added.<br />
* <tt>&lt;noinclude&gt;</tt> and <tt>&lt;includeonly&gt;</tt> (see above) were added.<br />
<br />
===Version 1.5===<br />
<br />
* More [[Help:magic words|magic words]] were added.<br />
<br />
===Version 1.4===<br />
<br />
*Including the same template more than five times in the same page works from version 1.4, now on all Wikimedia sites. Also new was that subst can be used with parameters.<br />
<br />
===Version 1.3===<br />
<br />
* See, among other things, [{{fullurl:m:Help:Template|oldid=86075}}#Default_values_of_parameters default values of parameters]. Starting with version 1.3 the prefix "msg:" is generally optional. <br />
<br />
===Version 1.2.6===<br />
<br />
* In MediaWiki version 1.2.6, make a page MediaWiki:mytemplate and refer to it with <nowiki>{{msg:mytemplate}}</nowiki>. In this version parameters are not possible.<br />
* Compatibility with 1.3, in the sense of having the content in Template:mytemplate, is possible with a redirect from MediaWiki:mytemplate to Template:mytemplate on the 1.2.6 project.<br />
<br />
== Revision history of pages containing templates ==<br />
<br />
Pages in the stored [[Help:Page history|page history]] consist of wikitext with possible ''references'' to templates and images. When viewing an old version of a page, these refer to the current versions of the templates and images, if these still exist. Thus the former composite page is not reconstructed.<br />
<br />
==See also==<br />
*[[m:Help:Advanced templates|Help:Advanced templates]]<!-- m: not directly portable due to examples --> <br />
*[[Help:Calculation]]<!-- maybe portable, test it --><br />
*[[Help:Parser function]] <br />
*[[m:ParserFunctions|ParserFunctions]]<br />
*[[m:Help:Parameter default|Help:Parameter default]]<!-- m: --><br />
*[[Help:Magic words]]<br />
*[[Help:Substitution]]<!-- maybe portable, test it --><br />
*[[Help:Template documentation]]<br />
*[[Help:Variable]]<br />
*[[Help:What links here]]<br />
*[[mw:Manual:$wgEnableScaryTranscluding|interwiki transclusion]]<br />
*[[m:Help:MediaWiki help policy|MediaWiki help templates]]<br />
*[{{fullurl:Special:Allpages|namespace=10}} List of all templates on this server]<br />
*[[Templates of Wikimedia projects]]<br />
*[[w:Wikipedia:Template namespace]]<br />
*[[Special:ExpandTemplates]] ([http://svn.wikimedia.org/viewvc/mediawiki/trunk/extensions/ExpandTemplates/ download this extension])<br />
*[[mw:Extension:Labeled Section Transclusion]] - transclusion of part of a page<br />
*[[w:Wikipedia:Template doc page pattern]]<br />
*[[w:Wikipedia:Template limits]]<br />
*[[DynamicFunctions##arg:]] - instead of including a page for given parameter values, this allows linking to a page for given parameter values. Syntax for parameter use: <nowiki>{{</nowiki>arg:''parameter name''|''default''}}. Syntax for linking: external link style with "&''parameter name''=''parameter value''" added to the URL.<br />
*[[w:Wikipedia:Transclusion costs and benefits]]<br />
<br />
{{h:f|enname=Template}}</div>HybridBoyhttps://wikicars.org/index.php?title=Help:Template&diff=48553Help:Template2007-03-25T15:35:26Z<p>HybridBoy: </p>
<hr />
<div>In [[w:MediaWiki|MediaWiki]], a '''template''' is a page which can be inserted into another page via a process called [[w:transclusion|transclusion]]. It can be considered a wiki [[w:en:subroutine|subroutine]] facility and is comparable to a #include statement or [[wikt:en:macro#Noun|macro]] that is expanded at page view time. [[Help:Substitution|Substitution]] allows templates to be used as a macro facility.<br />
<br />
This page and its extension '''[[Help:Advanced templates]]''' provide a reference manual on templates in MediaWiki. For an introduction, see ''[[Help:A quick guide to templates|A quick guide to templates]]'' and [[mw:Help:Templates]]. For syntax often used within templates, see [[m:ParserFunctions]] and other "Advanced functioning" help pages listed below.<br />
<br />
'''Note:''' The master version of this page is the page [[m:Help:Template]] on Meta-Wikipedia; template demos work there, but may not work if you are viewing a copy of this page on another project.<br />
<br />
==General==<br />
The '''template namespace''' is the [[Help:Namespace|namespace]] with prefix "'''Template:'''" (this prefix can be used in all languages, but the canonical prefixes in languages other than English include Vorlage, Modèle, Sjabloon, with colon; the site WikiFAQ calls it Snippet).<br />
<br />
A page in this namespace is called a '''template'''. The contents of such a page (either fixed or depending on [[w:en:Parameter (computer science)|parameters]] and/or [[Help:Variable|variable]]s) is designed to be useful for insertion in other pages ([[en:transclusion|transclusion]], creating a [[w:compound document|compound document]]).<br />
<br />
The syntax for insertion of the page "Template:''name''" is <nowiki>{{</nowiki>''name''<nowiki>}}</nowiki>. This is called a template tag. <br />
<br />
'''Example:''' <nowiki>abc{{tc}}def</nowiki> <br />
<br />
{{ut1|tc}} <br />
<br />
'''Gives:''' abc{{tc}}def.<br />
<br />
This reference in the wikitext causes insertion of the template content when the referring page is rendered. Various equivalent terms are:<br />
*calling the template<br />
*including the template<br />
*transcluding the template<br />
*using the template<br />
*embedding the template<br />
<br />
Depending on context "including" can be used as opposed to ''substituting'' the template. <br />
<br />
To create a hyperlink to a template page, use the usual wikilink syntax <nowiki>[[</nowiki>Template:''name'']].<br />
<br />
If the page "Template:''name''" does not exist, then <nowiki>{{</nowiki>''<nowiki>name</nowiki>''<nowiki>}}</nowiki> works as <nowiki>[[</nowiki>Template:''name''<nowiki>]]</nowiki>, a link to a non-existing page, leading to the edit page. Thus, one way of making a template is putting the tag first, and then following the link.<br />
<br />
If ''name'' starts with a valid namespace prefix, or a colon, then it is not prefixed with "Template:". This way any page can be used as template (a colon at the start refers to the main namespace). <br />
<br />
Also it provides an alternative way of calling a template, which can be used in the case of a name conflict with a variable, e.g. [[m:Template:Ns:3|Template:Ns:3]] and [[m:Template:PAGENAME|Template:PAGENAME]].<br />
<br />
Using a page outside the template namespace as template can be useful for:<br />
*quoting interface messages in the MediaWiki namespace<br />
*templates for personal use in subpages of one's userpage, e.g. for experimenting<br />
*inclusion of pages in other pages in the same namespace, e.g. having an extra page associated with each page, such as a to-do list, with a simple name correspondence; it can be created and included with <nowiki>{{{{NAMESPACE}}:{{PAGENAME}}/todo}}</nowiki>.<br />
<br />
As usual the template name is case sensitive except (on most projects) for the first letter, and a blank space is equivalent with an underscore (as opposed to parameter names, see below: they are case-sensitive, even with respect to the first letter, and spaces are distinguished from underscores).<br />
<br />
One can call a template that calls another template. If a template calls itself directly or indirectly, inclusion works only on one level for each template. However, with templates redirecting to the template that one would want to call recursively, one can achieve recursion without having to make copies of the whole template content, with the number of levels limited by the number of redirects. See also [[Help:Template#Repetition_within_a_page|Repetition within a page]] and {{tim|List of template calls}}.<br />
<br />
A [[Help:Variable|variable]] in a template is evaluated after insertion in the referring page, i.e. if <nowiki>{{PAGENAME}}</nowiki> occurs in the wikitext of a template, it is rendered as the name of the referring page, not the name of the template.<br />
<br />
A list of pages embedded in a page (as recorded in the [[m:templatelinks table|templatelinks table]]), all with links, is given on the edit page. Notes:<br />
*on a section edit page first the whole list is given, i.e. also the templates used in other sections; after pressing preview only those in the section, updated for the edits made, if any; preview on first edit gives the full list;<br />
*similarly, when editing an old version of a page, the list is first given for the current version, while after pressing preview the templates that used to be included are shown, updated for the edits on the old version made in the current session, if any; <br />
*if a page is conditionally embedded through #if, #ifeq, #ifexist, #ifexpr, or #switch, it is counted as embedded, even if the condition is not fulfilled<br />
*if the name of an embedded page is an expression, e.g. <nowiki>{{abc{{CURRENTDAY}}}}</nowiki>, currently giving {{abc{{CURRENTDAY}}}}, or <nowiki>{{{{#ifexist:Template:A|A|x1}}|Template does not exist}}</nowiki>, currently giving {{{{#ifexist:Template:A|A|x1}}|Template does not exist}}, the current template name is shown.<br />
<br />
Thus, to use "What links here" to find the pages that actually embed template A, instead of using e.g.<br />
<br />
:<nowiki>{{#if:..|{{a|pa1}}|{{b|pb1}}}}</nowiki><br />
<br />
one has to use an alternative, e.g., duplicating the condition:<br />
<br />
:<nowiki>{{{{#if:..|a|b}}|{{#if:..|pa1|pb1}}}}</nowiki><br />
<br />
or, using {{tim|echo}}:<br />
<br />
:<nowiki>{{{{#if:..|a|echo}}|1=pa1|echo={{b|pb1}}}}</nowiki><br />
<br />
Only with the first of the two alternatives "What links here" also finds the pages that actually embed template B. In the second alternative the page is anyway considered embedded. If we replace "b" by "<nowiki>{{if:1|b}}</nowiki>" the page is never considered embedded.<br />
<br />
(''Supported in version 1.4 and higher.'')<br />
<br />
When saving a page without newline at the end, and going to the edit page again, there is a newline at the end. However, this does not seem to have effect, see the example above and the following example:<br />
<br />
<pre>{{Numbered list demo}}{{Numbered list demo}}<br />
{{Numbered list demo}}</pre><br />
<br />
using [[Template:Numbered list demo]], gives<br />
<br />
{{Numbered list demo}}{{Numbered list demo}}<br />
{{Numbered list demo}}<br />
<br />
In a template name the character "#" and any characters after that are ignored: <nowiki>{{tc#abc}}</nowiki> gives {{tc#abc}}. This is used in {{tiw|en|hif}}.<br />
<br />
A wikitext with consecutive double opening braces and consecutive double closing braces is interpreted as containing a template parameter tag with triple braces. To avoid that, use a space in at least one of the two quadruples. For example, <nowiki>{{{{tc}}}}</nowiki> gives {{{{tc}}}}, while <nowiki>{{ {{tc}}}}</nowiki> gives {{ {{tc}}}}. <br />
<br />
With [[Special:ExpandTemplates]] one can view the expanded wikitext a template call produces, as intermediate step toward rendering. The same is also produced with a URL like {{fullurl:{{FULLPAGENAME}}|action=raw&templates=expand}}.<br />
<br />
==Use of templates across projects==<br />
A template only works when referred to from a page in the same project. To use it in another project, one has to copy it to there. [[Bugzilla:1126]] is a request to lift that restriction, i.e. allow interwiki use of templates.<br />
<br />
The adjustments needed in the copy, to work on the other project, can be reduced by using <nowiki>{{</nowiki>SERVER}}, localurl, and generic namespace names, and writing links in a way that works on multiple projects, e.g. [[m:Help:Table]]. For copying multiple templates, [[Help:Export|export]] and [[Help:Import|import]] can be helpful. It is also convenient if the template names can be the same on the other project. Therefore, when choosing template names, check which names are in use on other projects to which people might want to copy the templates. Note that if a template is referred to by something like abc<nowiki>{{</nowiki>NAMESPACE}}, a project with different namespace names requires a different template name, or a redirect.<br />
<br />
Transclusion across projects, hence changing contents from a central place, is only possible:<br />
*for content in the form of an image on Commons, to any page,<br />
*for editable content on an image page on Commons, including content transcluded from other pages on Commons, to the corresponding local image pages, if there is no local image with the same name<br />
<br />
Templates on the central Wikia work in the separate Wikia projects, provided that the prefix "wikia:" is used, see <span class="plainlinks">[http://www.wikia.com/wiki/Help:Shared_templates shared templates on wikia]</span>. (Please note that these external Wikia projects are NOT hosted and managed by the Wikimedia Foundation.)<br />
<br />
Sometimes multiple projects require pages which are partly the same and partly different. For example, on some projects "m:" is used as interwiki link to Meta, and on some projects "MetaWikipedia:". In this case a common wikitext can be used, calling project-specific templates. In the example the wikitext of the page could contain <nowiki>{{meta}}</nowiki>, and we would have on each wiki a Template:Meta containing the required prefix.<br />
<br />
==Parameters==<br />
<br />
Template parameters are either named or numbered. They are [[w:en:Parameter (computer science)#Calling conventions|called-by-value]], and therefore input parameters only.<br />
<br />
In the template ''definition'', the formal parameter (the [[w:en:Free variables and bound variables|placeholder]] for the parameter value) is a parameter name with three pairs of braces. So, for example, you would write {{{myVariableName}}} for a template parameter which you wanted to call ''myVariableName''.<br />
<br />
{{MW 1.6|(for parameters defaults)}} <br />
In the template ''call'', the syntax is either<br />
*<tt><nowiki>{{templatename|parname1=parvalue1|parname2=parvalue2}}</nowiki></tt> with tags <tt><nowiki>{{{parname1|default}}}</nowiki></tt>, <tt><nowiki>{{{parname2|default}}}</nowiki></tt>, etc. in the template, or<br />
*<tt><nowiki>{{templatename|parvalue1|parvalue2}}</nowiki></tt> with tags <tt><nowiki>{{{1|default}}}</nowiki></tt>, <tt><nowiki>{{{2|default}}}</nowiki></tt>, etc. in the template. <br />
<br />
The default (optional, together with the pipe character in front) can be different for every occurrence, and applies if no value is specified when calling the template, not to be confused with the case that the empty value is specified.<br />
<br />
A way to determine whether a parameter is defined is by comparing the results of two occurrences with different defaults, e.g. with <tt><nowiki>{{#ifeq: {{{a|+}}}|{{{a|-}}}|1|0}}</nowiki></tt>.<br />
<br />
In the case of [[Help:Substitution|page substitution]] with an undefined parameter, not the default but the parameter itself with default is substituted into the wikitext.<br />
<br />
===Example: named parameter substitution ===<br />
Let's create a template called '''Name-example''' (that is, the template will be '''[[Template:Name-example]]'''), with a parameter for the first name which we will call ''firstName'', and a parameter for the last name which we will call ''lastName''.<br><br />
<br />
Type the following in the new [[Template:Name-example]]: <br />
<br />
<pre><br />
:I am a template example, my first name is '''{{{firstName}}}''' and my last name is '''{{{lastName}}}'''.<br />
:<br />
:You can reference my page at [[{{{lastName}}}, {{{firstName}}}]].<br />
</pre><br />
<br />
On a second page, type this: <nowiki>{{Name-example}}</nowiki><br />
<br />
The result is: {{Name-example}}<br />
<br />
Because the template has no parameters.<br />
<br />
But if we type this on the second page: <nowiki>{{Name-example | firstName=John | lastName=Smith}}</nowiki> <br />
<br />
The result will looks like this:<br><br />
{{Name-example | firstName=John | lastName=Smith}}<br />
<br />
To analyse the working, one can apply [[Special:ExpandTemplates]] to see the expanded wikitext as intermediate result:<br />
<br />
<pre><br />
:I am a template example, my first name is '''John''' and my last name is '''Smith'''.<br />
:<br />
:You can reference my page at [[Smith, John]].<br />
</pre><br />
<br />
When this wikitext is applied directly the resulting rendering is the same.<br />
<br />
===Example: numeric parameter substitution===<br />
An example of how the contents of a parameter function.<br />
<br />
====The simplest case====<br />
Let us first ''define'' a template with the name ''t0'', which will <br />
*expect a single argument<br />
*give back the text of that argument, with no spaces before or after it, between "start-" and "-end":<br />
:'''<nowiki>start-{{{1}}}-end</nowiki>'''<br />
the definition of course being on page '''[[Template:t0]]'''.<br />
<br />
#Calling the template named ''t0'' with a parameter value of "''a''", i.e., <br />
#::<nowiki>{{t0|a}}</nowiki> <br />
#:gives <br />
#::"{{t0|a}}"<br />
#Calling the template named ''t0'' with a parameter value of " " (a blank space), i.e., <br />
#::<nowiki>{{t0| }}</nowiki><br />
#:gives <br />
#::"{{t0| }}" .<br />
#Calling the template named ''t0'' with a parameter value of "" (an empty string), i.e., <br />
#::<nowiki>{{t0|}}</nowiki> <br />
#:gives <br />
#::"{{t0|}}".<br />
#Calling the template named ''t0'' and not passing any parameters, i.e., <br />
#::<nowiki>{{t0}}</nowiki> <br />
#:gives <br />
#::"{{t0}}".<br />
If something like '''{{{1}}}''' or in fact any '''{{{name}}}''' is visible on an ordinary page it typically indicates that a mandatory parameter of a template used on this page isn't defined.<br />
<br />
Calling the template named ''t0'' with a parameter which consists of two newlines, i.e.,<br />
<br />
<nowiki> {{t0| </nowiki>}}<br />
<br />
gives <br />
<br />
{{t0| }}<br />
<br />
<nowiki>{{t0|</nowiki><br />
<br />
}}<br />
<br />
gives <br />
<br />
{{t0|<br />
<br />
}}.<br />
<br />
Thus, unlike in the case of parser functions, there are no complications with spaces and newlines, compare [[ParserFunctions#Conditional_whitespace|conditional whitespace]].<br />
<br />
====Declaring a default value====<br />
Now let us ''define'' a similar template with the name ''t'' which contains a single numbered parameter 1 with a default of ''pqr''. The only difference between the effects of t and t0 appears when they are called with no parameter (and no "|"):<br />
<br />
:'''<nowiki>start-{{{1|pqr}}}-end</nowiki>'''<br><br />
the definition of course being on page '''[[Template:t]]'''.<br><br />
#Calling the template named ''t'' with a parameter value of "''a''", i.e.,<br />
#::<nowiki>{{t|a}}</nowiki> <br />
#:gives <br />
#::"{{t|a}}".<br />
#Calling the template named ''t'' with a parameter value of " ", i.e.,<br />
#::<nowiki>{{t| }}</nowiki> <br />
#:gives <br />
#::"{{t| }}".<br />
#Calling the template named ''t'' with a parameter value of "", i.e.,<br />
#::<nowiki>{{t|}}</nowiki> <br />
#:gives <br />
#::"{{t|}}".<br />
#Calling the template named ''t'' with named parameter '''1=''', i.e.,<br />
#::<nowiki>{{t|1=no surprise}}</nowiki> <br />
#:gives<br />
#::"{{t|1=no surprise}}".<br />
#Calling the template named ''t'' with '''1=''' after an unnamed parameter, i.e.,<br />
#::<nowiki>{{t|no|1=surprise}}</nowiki> <br />
#:gives<br />
#::"{{t|no|1=surprise}}".<br />
#Calling the template named ''t'' with '''1=''' before an unnamed parameter, i.e.,<br />
#::<nowiki>{{t|1=no|surprise}}</nowiki> <br />
#:gives<br />
#::"{{t|1=no|surprise}}".<br />
#Calling the template named ''t'' and no parameter at all, i.e.,<br />
#::<nowiki>{{t}}</nowiki> <br />
#:gives<br />
#::"{{t}}".<br />
#Calling the template named ''t'' and no named or unnamed parameter '''1''', i.e.,<br />
#::<nowiki>{{t|2=two}}</nowiki> <br />
#:gives<br />
#::"{{t|2=two}}".<br />
<br />
===Restrictions on parameter values===<br />
* If a parameter value contains an equals sign, the parameter name must be put explicitly, even when it is 1, 2, 3, etc.<br />
<br />
* If the expression for a parameter value contains two consecutive closing braces which are not part of a variable or parameter tag, they have to be put in nowiki tags.<br />
<br />
* The expression for a parameter value cannot contain the variable localurl with query string, due to the pipe character. <br />
<br />
*A parameter value can be quite long, see [[m:Help:Long parameter demo|Help:Long parameter demo]].<br />
<br />
*A parameter value can contain pairs of square brackets or text to be used within a link, but not a closing part of one link and an opening part of another link: <nowiki>{{</nowiki>tlis|abc]]def[[ghi}} using {{timc|tlis}} gives {{tlis|abc]]def[[ghi}} rather than the expected aabc]]def[[ghib.<br />
<br />
====Pipe character====<br />
To define a parameter value containing a pipe character (|) which is not part of a template call, parser function call, piped link or image tag, use [[Template:!]] containing "<span style="background-color:#c8f0ff; padding:0 3px 2px 3px;">|</span>". Using {{tcw|t0}}, compare <nowiki>{{t0|a{{!}}b}}</nowiki> giving {{t0|a{{!}}b}}, <nowiki>{{t0|a&amp;#124;b}}</nowiki> giving {{t0|a&#124;b}} and <nowiki>{{t0|a|b}}</nowiki> giving {{t0|a|b}}. The difference between the first and the second is that in the first case the expanded wikitext is start-a|b-end, while in the second case it is start-a&amp;#124;b-end. This is rendered the same in final output but makes a difference when used in table syntax: this requires the "real" pipe character. <br />
<br />
<pre>{{x2|{{{!}} <br />
{{!}} A <br />
{{!}} B<br />
{{!}}- <br />
{{!}} C<br />
{{!}} D<br />
{{!}}}<br />
}}</pre><br />
<br />
gives<br />
<br />
{{x2|{{{!}} <br />
{{!}} A <br />
{{!}} B<br />
{{!}}- <br />
{{!}} C<br />
{{!}} D<br />
{{!}}}<br />
}}<br />
<br />
while<br />
<br />
<pre>{{x2|{&amp;#124; <br />
&amp;#124; A <br />
&amp;#124; B<br />
&amp;#124;- <br />
&amp;#124; C<br />
&amp;#124; D<br />
&amp;#124;}<br />
<br />
}}</pre><br />
<br />
gives <br />
<br />
{{x2|{&#124; <br />
&#124; A <br />
&#124; B<br />
&#124;- <br />
&#124; C<br />
&#124; D<br />
&#124;}<br />
}}<br />
<br />
and<br />
<br />
<pre>{{x2|{| <br />
| A <br />
| B<br />
|- <br />
| C<br />
| D<br />
|}<br />
}}</pre><br />
<br />
gives<br />
<br />
{{x2|{| <br />
| A <br />
| B<br />
|- <br />
| C<br />
| D<br />
|}<br />
}}<br />
<br />
===Equals sign in parameter value===<br />
When a parameter value contains an equals sign, the parameter name must be stated explicitly, otherwise the part of the parameter value before the equals sign is taken as the parameter name. If that happens accidentally, this parameter is likely to be unused, hence harmless, but the intended implicit parameter 1, 2, or 3, etc., gets no value. <br />
<br />
:Example: <nowiki>{{TTT|a=b|c}}</nowiki> {{ut1|TTT}} gives {{TTT|a=b|c}} (unused parameter a is assigned the value b, the first parameter value for which no parameter name is specified is assigned to the parameter with the implicit name "1" &mdash; it reads like so: Use template TTT, assign "b" to the parameter "a", use the value "c" for your first ''implicit'' parameter <nowiki>{{{1}}}</nowiki>.), while <nowiki>{{TTT|1=a=b|2=c}}</nowiki> gives {{TTT|1=a=b|2=c}} (the first parameter is assigned the value "a=b" &mdash; it reads like so: Use template TTT, assign "a=b" to the ''expressed'' parameter "1", assign "c" to the ''expressed'' parameter "2"). <nowiki>{{TTT|1=a=b|2=c|d}}</nowiki> gives {{TTT|1=a=b|2=c|d}}, "d" is assigned to "1" as first ''implicit'' parameter, overwriting the value "a=b".<br />
<br />
A parameter definition (between pipe characters or a pipe character and template end tags) may depend on a template, parser function, variable, or template parameter. The explicit or implicit name of the parameter is determined after expansion. For example, a template call <nowiki>{{t2|{{{a}}}}}</nowiki> assigns the value of {{{a}}} to implicit parameter 1 if that value does not contain an equals sign, but if it has the value "b=c", c is assigned to b. If we anyway want to assign the value of {{{a}}} to 1 we have to use an explicit parameter 1: <nowiki>{{t2|1={{{a}}}}}</nowiki>.<br />
<br />
Compare:<br />
<br />
*<nowiki>{{t2a1|1=x=y}}</nowiki> (using {{tcw|t2a1}}) gives {{t2a1|1=x=y}}.<br />
*<nowiki>{{t2a2|1=x=y}}</nowiki> (using {{tcw|t2a2}}) gives {{t2a2|1=x=y}}.<br />
<br />
Similarly, parameter definition {{{a}}}=b where {{{a}}} has value "c=d" results in "d=b" being assigned to c, for example:<br />
*<nowiki>{{t5|a=2=d}}</nowiki> (using {{tcw|t5}}) gives {{t5|a=2=d}}.<br />
<br />
===Mix of named and unnamed parameters===<br />
In the case of a mix of named and unnamed parameters in a template tag, the unnamed parameters are numbered 1,2,3,.., so they are ''not'' numbered according to the position in the mixed list as a whole.<br />
<br />
For example, <nowiki>{{</nowiki>t sup|3=1|2|1=3|4|5|6|7}} using {{tcw|t sup}} gives {{t sup|3=1|2|1=3|4|5|6|7}}.<br />
<br />
===When parameters do not expand===<br />
{{MW 1.6|(for parameters defaults)}}<br />
Parameters do not get expanded when they are inside tags (HTML, wiki, or extension),<br />
or between <nowiki><html></html></nowiki> tags<br />
<br />
The following will not work within a template, because the parameter is not expanded<br />
<br />
<nowiki><br />
<myextension xparam={{{tparam}}}> ... </myextension><br />
<html><span onmouseover="return escape('foobar')"> {{{1}}} </span></html><br />
</nowiki><br />
<br />
This continues to be true into version 1.8.2, though [[Template:Hidden]] provides a puzzling exception. Any explanation?<br />
<br />
==Template mechanism==<br />
The template mechanism involves the following steps:<br />
<br />
*The pipe characters in template calls determine the separation into template name and parameter definitions. This separation does not depend on possible pipe characters in the expanded form of the text between the opening and closing braces of the template. For example, <nowiki>{{ {{t6}} }}</nowiki> using {{tcw|t6}} gives {{ {{t6}} }}, not the result of <nowiki>{{ t2demo|a }}</nowiki> which is {{ t2demo|a }}. This is because "t2demo|a" is not a valid template name (not to be confused with a template with a valid name that does not exist), so the template call is not expanded.<br />
<br />
::Note that in this case partial or successive substitution does not give the same result as without substitution: <nowiki>{{ {{subst:t6}} }}</nowiki> gives the wikitext <nowiki>{{ t2demo|a }}</nowiki>, rendered as {{ t2demo|a }}.<br />
<br />
*The template name and each of the parameter definitions is evaluated. The leftmost equals sign, if any, in each parameter definition separates the parameter name from the parameter value.<br />
*The values are assigned to the parameters from left to right (the result can not be directly viewed), meaning that a named or numbered parameter may be specified several times, the last one being the actual value that will be kept when passing the parameter during the final instantiation of the template below.<br />
*Template calls are replaced by template content, where the parameter tags with matching names are replaced by their values or defaults (the result of this step can be viewed by applying subst either again, or directly to the template and the variables).<br />
<br />
The process is applied recursively until there are no more template calls to replace.<br />
<br />
All whitespaces before and after a parameter value are ignored if "=" is used.<br />
<br />
:<nowiki>"{{t|1= a}}"</nowiki> gives "{{t|1= a}}".<br />
:<nowiki>"{{t|1=a }}"</nowiki> gives "{{t|1=a }}".<br />
:<nowiki>"{{t| a}}"</nowiki> gives "{{t| a}}".<br />
:<nowiki>"{{t|a }}"</nowiki> gives "{{t|a }}".<br />
<br />
A parameter value can contain a piped link; the "|" in such a link is not taken as parameter separator.<br />
<br />
:Example: <nowiki>"{{t|[[a|b]]}}"</nowiki> gives "{{t|[[a|b]]}}".<br />
:Example: <nowiki>"{{t|[[a|b]] }}"</nowiki> gives "{{t|[[a|b]] }}".<br />
<br />
(In this case the space ''has'' effect.)<br />
<br />
On rendering, surplus parameter values (including named parameters that do not occur in the template) are ignored: <nowiki>{{t|a|b}}</nowiki> gives {{t|a|b}}.<br />
<br />
Parameters without names (i.e. that don't contain an equal sign) are numbered implicitly starting by 1, from left to right.<br />
<br />
:Example: <nowiki>"{{t|a|b|c}}"</nowiki> is equivalent to <nowiki>"{{t|1=a|2=b|3=c}}"</nowiki><br />
<br />
Numbered parameters can also be skipped or can be specified in alternate order by numbering them explicitly.<br />
<br />
:Example: <nowiki>"{{t|3=c|2=b|1=a}}"</nowiki> is equivalent to <nowiki>"{{t|1=a|2=b|3=c}}"</nowiki><br />
:Example: <nowiki>"{{t|a|b|c|10=j}}"</nowiki> is equivalent to <nowiki>"{{t|1=a|2=b|3=c|10=j}}"</nowiki><br />
<br />
This also makes it possible to apply a default value for parameter 1, while specifying a value for parameter 2:<br />
<br />
<nowiki>{{t2d|2=a}}</nowiki>, using {{timc|t2d}}, gives {{t2d|2=a}}.<br />
<br />
Template calls can contain multiple occurrences of the same named parameter, and a numbered parameter can be specified multiple times by using its number explicitly. The effective value of parameters is the value of the last occurrence (from left to right) of the parameter with the same name, once the parameter names have been evaluated.<br />
<br />
:Example: <nowiki>"{{t|a|b|c|2=B}}"</nowiki> is equivalent to <nowiki>"{{t|a|B|c}}"</nowiki><br />
<br />
The final list of formal parameters before the template itself is instantiated is then unordered because the list is indexed by the evaluated parameter named (this list is an [[:en:Associative array|associative array]]).<br />
<br />
When [[m:ParserFunctions|ParserFunctions]] were not available yet, multiple assignments of parameters with the same name (and thus allowing parameter overrides) were ingeniously used to perform branching, e.g. in the now deleted [[:en:Template:If defined]]. <br />
<br />
See also [[Help:Parameter default]].<br />
<br />
== Template tag lay-out ==<br />
<br />
To have a desired template tag lay-out, especially in the case of many parameters, additional dummy parameters can be used with a newline, spaces, and/or comments. In the case of unnamed parameters, this means that some parameter numbers are not used in the template content, so that their values, present in the template tag, do not affect the rendering of the template. For example, using {{Tcw|t3d}},<br />
<br />
<pre><br />
{{t3d |a|b|c| 1<br />
|d|e|f| 2<br />
|g|h|i| 3<br />
}}<br />
</pre><br />
<br />
gives:<br />
<br />
{{t3d |a|b|c| 1<br />
|d|e|f| 2<br />
|g|h|i| 3<br />
}}<br />
<br />
If parameters are named, dummy parameters can easily be inserted at any time. If they are unnamed, then, to avoid renumbering, one can insert named parameters: any text including an equals sign will do, if the text on the left is not one of the parameter numbers: this text is interpreted as the name of an unused parameter, hence ignored.<br />
<br />
Example:<br />
<br />
Using {{tim|Chess position}}<br />
<br />
<pre><br />
{{chess position|=<br />
<br />
8 |rd|nd|bd|qd|kd|bd|nd|rd|=<br />
7 | |pd|pd|pd|pd|pd|pd|pd|=<br />
6 |pd| | | | | | | |=<br />
5 | | | | | | | | |=<br />
4 | |pl| | | | |pl| |=<br />
3 | | | | | | | |bl|=<br />
2 |pl| |pl|pl|pl|pl| |pl|=<br />
1 |rl|nl|bl|ql|kl| |nl|rl|=<br />
a b c d e f g h<br />
<br />
|30}}<br />
</pre><br />
<br />
which gives<br />
<br />
{{chess position|=<br />
<br />
8 |rd|nd|bd|qd|kd|bd|nd|rd|=<br />
7 | |pd|pd|pd|pd|pd|pd|pd|=<br />
6 |pd| | | | | | | |=<br />
5 | | | | | | | | |=<br />
4 | |pl| | | | |pl| |=<br />
3 | | | | | | | |bl|=<br />
2 |pl| |pl|pl|pl|pl| |pl|=<br />
1 |rl|nl|bl|ql|kl| |nl|rl|=<br />
a b c d e f g h<br />
<br />
|30}}<br />
<br />
In this example, the 1 to 8 row numbers and a to h column numbers (as well as their surrounding spaces and newlines) in the parameter list are hidden within a dummy parameter (with an empty name before the equal sign).<br />
<br />
The template generates a HTML table where each cell contains an image whose name is dynamically generated from the 64 first automatically numbered parameters (there are intermediate parameters within the numbered list, but as these dummy parameters are named explicitly, they don't increment the parameter number used to generate default parameter names. So the parameter with autogenerated name "1" effectively contains the "rd" value).<br />
<br />
The template is then called with a parameter list that contains:<br />
* 65 parameters automatically named from "1" to "65" (64 parameters for the cells content, and the 65th for the image width),<br />
* and a dummy named parameter (whose name is an empty string, and whose effective value results from the last assignment with the chessboard column names a to h and the surrounding spaces and newlines), which is not used in the internal template content.<br />
<br />
Note also that all parameters are trimmed, so the parameter with autogenerated name "9" (at position a7 on the chessboard above) is assigned the empty string value.<br />
<br />
==Template page==<br />
Without noinclude and includeonly parts the following are identical:<br />
*the rendering of the wikitext of the template (this is on the template page, and would be the same in other pages with that wikitext, except for page-dependent variables)<br />
*the rendering of the template on a page that calls it without parameters<br />
<br />
Thus the defaults are shown, e.g. {{timc|T 1}} shows the same as <nowiki>{{</nowiki>t 1}}: "{{t 1}}".<br />
<br />
===Template page if no defaults have been specified===<br />
In simple cases this corresponds to treating the parameter tags as ordinary text, for example:<br />
<br />
<nowiki>"{{t2demo}}"</nowiki> (using [[Template:t2demo]] containing {{msgnw:t2demo}}) gives {{t2demo}}<br />
<br />
Similarly, if part of the parameters is undefined, only those show up as {{{''parameter number or name''}}}. <br />
<br />
However, some templates produce an error message when called without parameters, so unless includeonly is used (see below) the template page also shows this message, suggesting that there is something wrong with the template. For example, a template that doubles parameter {{{1}}} with the wikitext <nowiki>{{#expr:2*{{{1}}}}}</nowiki> gives {{#expr:2*{{{1}}}}}. In such cases includeonly can be used to avoid uninformative and messy rendering on the template page, but either way a disadvantage during template development is that preview does not (meaningfully) reflect changes in the parts of the page outside the noinclude tags (i.e. the included parts). Therefore it can be useful to provide representative default values, even if that is only done temporarily during development of the template.<br />
<br />
Note also that variable tags are not shown, but evaluated.<br />
<br />
With noinclude an informative template page can be produced, containing more demos and test cases than just the single default set. Typically, the noinclude-part of a template page contains examples including or [[Help:substitution|substituting]] the template. Changes in the working of the template (i.e. changes outside the noinclude-part) are not yet effective in these examples in preview and, in the case of [[Help:substitution|substitution]], in "show changes".<br />
However, they are reflected in the rendered page after saving.<br />
<br />
Some formatting aspects may show up which are not readily seen from the edit box.<br />
<br />
==A parameter value depending on parameters==<br />
As mentioned above, if a parameter is left undefined, the triple braced parameter name in the result does not function as a parameter if the page is called as a template from another page; if it should, do not omit the parameter value but specify it in terms of a parameter of the calling page; compare:<br />
*<nowiki>{{t2ademo|b}}</nowiki> (using [[Template:t2ademo]] containing {{msgnw:t2ademo}}) gives {{t2ademo|b}}<br />
*<nowiki>{{t2a1|b}}</nowiki> (using [[Template:t2a1]] containing {{msgnw:t2a1}}) gives {{t2a1|b}}.<br />
*Similarly, <nowiki>{{t2a2|b}}</nowiki> (using [[Template:t2a2]] containing {{msgnw:t2a2}}) gives {{t2a2|b}}. See also below.<br />
<br />
The most straightforward way of expressing a parameter value in terms of a parameter is using the same name and making it equal, e.g. <nowiki>{{</nowiki>Lan is|lr=af|le={{{le}}}}} in [[Template:Lan is mr]].<br />
<br />
==Empty vs. undefined==<br />
<nowiki>{{t2demo||a}}</nowiki> makes the first parameter equal to the empty string rather than leaving it undefined: it gives {{t2demo||a}}. By treating the second unnamed parameter as a parameter with the name "2", the first unnamed parameter can be left undefined.<br />
<br />
:Example: <nowiki>{{t2demo|2=a}}</nowiki> gives {{t2demo|2=a}}.<br />
<br />
If the parameter is used in a tag like <nowiki><font size></nowiki> the default text may give invalid code that is conveniently ignored, rather than resulting in perhaps ugly code being rendered (but this may depend on the browser). See e.g. [[Template talk:Fontsize]].<br />
<br />
Parameter names (as opposed to template names) are case-sensitive, even with respect to the first letter, and spaces are distinguished from underscores. The [[w:en:String_%28computer_science%29#Formal_theory|empty string]] is also a valid parameter name, see [[Template:T empty string as parameter name]].<br />
<br />
Parameter 02 is distinguished from parameter 2: using {{timc|t pl0}}, <nowiki>{{</nowiki>t pl0|5|6|7}} gives {{t pl0|5|6|7}} <br />
<br />
Note that parameters in the [[MediaWiki namespace]] (interface messages) are written differently: as $1, $2, etc., see [[Meta-Wikimedia:MediaWiki namespace text]].<br />
<br />
==msgnw==<br />
<br />
The prefix '''msgnw''' (short for "message, nowiki") is used to display the uninterpreted wikitext of a template (the same thing you'd see if you were editing the page) on another page. An exception is that numbered and unnumbered lists are rendered as such instead of displaying # or * signs. Parameter values are ignored.<br />
<br />
With the introduction of noinclude and includeonly tags, allowing template pages to take care of definition as well as displaying information, msgnw displays no longer just the technical information about what the template does when included, but a mix of that with wikitext for rendering the template page itself, with the tags. This limits the usefulness of applying this.<br />
<br />
Examples:<br />
<br />
[[Template:en]]<br />
*<nowiki>{{msgnw:en}}</nowiki> gives {{msgnw:en}} <br />
*<nowiki>{{en}}</nowiki> gives {{en}}<br />
<br />
{{tim|t}}<br />
<br />
<nowiki>{{msgnw:t|a}}</nowiki> gives <br />
*{{msgnw:t|a}} <br />
<br />...which is much more than just the formal info about what the template does when included:<br />
*<nowiki>start-{{{1|pqr}}}-end</nowiki><br />
<br />
[[Template:Numbered list demo]]<br />
<br />
<nowiki>{{msgnw:Numbered list demo}}</nowiki> gives:<br />
{{msgnw:Numbered list demo}} <br />
<br />
<nowiki>{{Numbered list demo}}</nowiki> gives:<br />
{{Numbered list demo}}<br />
<br />
The edit box for [[Template:Numbered list demo]] shows:<br />
<pre><br />
#Amsterdam<br />
#Rotterdam<br />
#The Hague<br />
</pre><br />
<br />
==Usage==<br />
<br />
Templates are useful for any text for which one wants a copy in two or more pages, and there is no need for each copy to be edited independently to adapt it to the page it is in. Since parameters can be used, versions may to that extent even be different, and parameter values can be edited independently for each. Templates are not only convenient, but they can also "force" a useful uniformity. See also [[w:en:Subroutine|advantages of subprograms]].<br />
<br />
Typical applications are:<br />
*[[w:Wikipedia:Template messages|template messages]] such as [[w:en:Template:stub]]<br />
*[[m:help:Navigational template|Navigational template]]s such as [[w:en:Template:europe]], sometimes listed in a directory such as [[w:Wikipedia:navigational templates]]<br />
*[[w:Wikipedia:Infobox|infoboxes]], each time showing the same kind of information in the same format, but each time for a different case, using parameters, e.g. the [[w:en:Template:Infobox Countries]].<br />
*provide cross-language portability of texts which are largely internationally the same, but contain some standard terms different in each language; the standard terms are replaced by {{..}} referring to template pages which have the same name but localised content in each language. This is [[m:Using templates in Wiktionary|applied in Wiktionaries]] for names of languages, terms like "noun", etc.; it is also [[w:Wikipedia:Template messages#Taxobox_components_.28Taxons.29|applied for taxoboxes]], see e.g. [[w:en:Template:Familia]] and [[w:fr:Modèle:Familia]].<br />
*allow a composite image, composed of a table of images, to be specified by a template tag which itself has a corresponding table-like lay-out, see [[w:Template:Chess position]] and [[w:Template:Game of Go Position]] (the latter example also shows that the number of parameters a template can have is quite large, in this case 362). Newlines in parameter values provide the lay-out of the template tag, but they are not allowed in image names, therefore they are put within comment tags; alternatively, dummy parameters could be used on these positions.<br />
<br />
Various combinations are possible. E.g., the last two could be combined, so that e.g. every language version of Wikipedia has the same Infobox Countries template (for each project a copy, because the template mechanism can not import across projects), which has parameters for the data, and refers to templates with translations of standard terms.<br />
<br />
See also '''[[Help:Advanced templates]]'''.<br />
<br />
===Composite pages===<br />
The wikitext of a page may (partly or fully) consist of tags for the inclusion of component pages. The "templates" are not necessarily in the template namespace, and may be more or less self-contained pages by themselves. An advantage of putting the components in the template namespace is that they are then included in the list of templates used on the composite page, all with links, on its edit page. On the other hand, the component page may, by itself, be of a nature that it belongs in e.g. the main namespace, while the prefix would suggest otherwise; also the prefix would clutter the pagename.<br />
<br />
Examples are:<br />
*[[m:Help:A simple composite example]]<br />
*[[w:Wikipedia:Village pump]] with six component pages, e.g. [[w:Wikipedia:Village pump (technical)]]<br />
*daily a page like [[w:en:Wikipedia:Votes for deletion/Log/2005 May 31]] where each component page consists of the discussion on the deletion of one Wikipedia page, e.g. [[w:en:Wikipedia:Votes for deletion/Sp3tt]] (for this day there are 75 of such component pages)<br />
*[[m:Meta:Translation/Coordination]], mainly containing <br />
**[[m:Meta:Translation/Coordination/List/Meta]]<br />
**[[m:Meta:Translation/Coordination/List/Main]]<br />
*[http://en.wikipedia.org/w/index.php?title=2005_English_cricket_season_%281-14_June%29&diff=27917447&oldid=27330886] - rejection of composite page by w:en<br />
<br />
This allows the user the choice between viewing the component pages separately or combinedly. One may want to view a page separately if one has a slow connection; also sometimes people have sentimental reasons for having a separate page about a topic, e.g. a village. Viewing the combined page is much more convenient if there are many small component pages; even if a subbtopic page does not provide additional info, if it exists anyway, and is linked to, it is useful to display the content (making clear that the whole content is shown), it saves the trouble of checking the contents by following the link.<br />
<br />
In the latter case the search function of the browser can be used for searching in the combined page. Similar to the section editing feature, it allows editing a component page; however, there is no possibility to have the combined wikitext in the edit box.<br />
<br />
Edit history, recent changes, watching pages, and "what links here" work separately for the component pages and the ''composition'' page, not for the ''composite'' page. Related changes works for the component pages and for the composite page. Page protection can be set for selected component pages and for the composition page, not directly for the composite page.<br />
<br />
The talk page of a composition page is used to talk about the composition and the page in general, and could in addition be a composite page of the talk pages of the component pages.<br />
<br />
A composite page has an integrated TOC and section numbering; the numbering is not reset for each component page.<br />
<br />
Editing a section of a component page can be done directly from the composite page, see [[Help:Section#Editing sections of included templates|editing sections of included templates]]. After saving, one ends up at the page for the component page to which the section belongs.<br />
<br />
On projects with the [[Help:Interwiki linking#Interlanguage_link_.28software_feature.29|interlanguage link feature]] the composite page shows the combined interlanguage links of all component pages, hence possibly multiple links for one language or even for one page.<br />
<br />
For easy access to the component pages, links to them on the composite page (for example by self-links on the component pages) are convenient. Alternatively, access is through section editing, or, if the component pages are in the template namespace, through the list of templates called from the composite page, at its edit page.<br />
<br />
Conversely, for easy access from a component page to the composite page(s) that call(s) it (if there are not too many of them) it is convenient to link the component page to them (on a composite page one becomes a self-link).<br />
<br />
See also [[w:Wikipedia talk:Template namespace#transcluding prose]].<br />
<br />
===Pages with a common section===<br />
A section on the relationship of the subjects A and B, or a subtopic equally relevant for A as for B, can be put both in page A and in page B, by making it a separate page C, called as a template from A and B.<br />
<br />
Remarks:<br />
*For readers reading both A and B, it is useful that the duplication be indicated by a message or a special lay-out; otherwise it is confusing and inconvenient. One can for example use {{tim|cs}}: {{cs|Help:Template}}<br />
*After saving one ends up viewing the template page. For easy access to the calling pages it is convenient to link the called page to them (on a calling page one becomes a self-link). This may well be integrated in the message about the duplication. It is even more convenient than the two-step link as shown above.<br />
*The section level of the embedded section(s) has to be the same in each embedding page. The same applies to lay-out and style.<br />
*Pages like C can be put in<br />
**the same namespace as A and B; advantage:<br />
***the kind of content of C is the same as that of A and B<br />
**the template namespace; advantages:<br />
***C appears in the list of templates called from A and B, at their edit pages<br />
***C by itself may not satisfy the standards for pages in the namespace of A and B, such as providing context (however, the message about the duplication explains it)<br />
<br />
Examples:<br />
*{{pim|Help|Editing sections of included templates}}<br />
*{{pim|Help|Alphabetic order}}<br />
<br />
For various remarks which also apply here, see also the previous section.<br />
<br />
===Repetition within a page===<br />
For a succession of similar pieces of content, as in a list, a computer program would use a [[w:en:Conditional_branching#Loops|loop]]. What comes closest in MediaWiki is putting the loop body in a template, and calling the template repeatedly, usually with a varying parameter value. This is somewhat primitive for a loop:<br />
*instead of "for i=1 to 5" we need to enumerate the values 1, 2, 3, 4, 5; on the other hand, this gives the versatility to use just as easily less regular values such as de, en, fr ([[w:en:Conditional_branching#Collection-controlled_loops|collection-controlled loop]]).<br />
*repetition of code is minimized by the template, but the template call itself has to be repeated each time (but see also the next section)<br />
<br />
Example:<br />
*[[Template:List of Languages]] - the "loop body" is in [[Template:Lang def]]; compared with putting the content of the latter directly in the list the advantage is that the variable part (the value of "code") occurs once each time in the code, although it is used twice. This is important because the fixed part of the list item code can be copied while the variable part is typically inserted manually.<br />
<br />
For repetition of the same text the loop body can be a parameter, e.g. [[Template:X5]] (see [http://meta.wikimedia.org/w/index.php?title=Special%3AAllpages&from=X&namespace=10 list]).<br />
<br />
A double loop is achieved by a second template that repeatedly calls the first. Similarly for a triple loop, etc. See e.g. [[w:Template:Ld]], [[w:Template:L2d]], and [[w:Template:L3d]].<br />
<br />
An example where the same template is used for different loop levels is [[Template:Loop 2]]. Because the software has a built-in protection against infinite nesting (if there is, there will be an error e.g. <code>Fatal error: Maximum execution time of 30 seconds exceeded in /w/includes/Parser.php on line 775</code>), a redirect is used for each level. The number of levels that the template can handle is determined by the number of parameters specified in the two template calls it comprises (because going up a level requires an extra parameter) and the number of existing redirects.<br />
<br />
Similarly [[Template:Lanlp 1]] is used for both the inner and the outer of a double loop. Adding an item (here a language) adds to each row and also adds an extra row.<br />
<br />
'''Providing effective repetition without repetition of similar template calls in the wikitext'''<br />
<br />
A technique for repetition of similar template calls without actually putting this list in the wikitext is demonstrated in {{tim|for}}, and a more primitive method described below.<br />
<br />
Example {{ut1|t2}}:<br />
<br />
<nowiki>{{for|call=t2|pc1=constant|abc|def|ghi}}</nowiki> gives:<br />
<br />
{{for|call=t2|pc1=2=constant|abc|def|ghi}}<br />
<br />
Description of the old {{tim|List of template calls}}:<br />
<br />
For an arbitrary template with up to three nameless parameters, it is equivalent to calling the template repeatedly, with the first parameter varying, and the possible other parameters fixed: one specifies the name, the values of the fixed parameters, and the list of values the first parameter should have in consecutive template calls, with a sequential number each, and ending with "end". The technique requires redirects like [[Template:List of template calls 3]], as many as the maximum number of repetitions.<br />
<br />
If e.g. the second parameter varies, or two parameters, then a similar template can be made, but each version requires its own set of redirects.<br />
<br />
Example {{ut1|t2}}:<br />
<br />
<nowiki>{{List of template calls|t2|constant||abc|1|def|2|ghi|end|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||}}</nowiki><br />
<br />
gives:<br />
<br />
{{List of template calls|t2|constant||abc|1|def|2|ghi|end|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||}}<br />
<br />
The empty parameters are needed in accordance with the maximum number of parameters the repeated template can have (currently three) and the maximum number of repetitions. Putting more empty parameters than needed at the end does not matter, but the number of empty parameters in the beginning of the list should be correct.<br />
<br />
==Ambiguity of a reference to "this page"==<br />
If a page is included in another page, a reference to "this page" on the included page is ambiguous. Use noinclude or includeonly tags depending on what is meant. Alternatively, mention the page name explicitly, without using <nowiki>{{</nowiki>PAGENAME}}.<br />
<br />
==Internal links==<br />
<br />
In the case of an internal link in a template with the target depending on a parameter, and in the case of a link with the target depending on a template, existence detection works as usual. <br />
<br />
Examples:<br />
<br />
*<nowiki>{{tli|insert in target|insert in label}}</nowiki> {{ut1|tli}} gives {{tli|insert in target|insert in label}}<br />
*<nowiki>[[a{{tciit}}b|c{{tciil}}d]]</nowiki> {{ut2|tciit|tciil}} gives [[a{{tciit}}b|c{{tciil}}d]]<br />
<br />
*<nowiki>{{tli|insert also in target|insert in label}}</nowiki> (using [[Template:tli]]) gives {{tli|insert also in target|insert in label}} {{ne}}<br />
*<nowiki>[[a{{tciit}}e|c{{tciil}}d]]</nowiki> (using [[Template:tciit]] and [[Template:tciil]]) gives [[a{{tciit}}e|c{{tciil}}d]] {{ne}}<br />
<br />
*<nowiki>{{la|Help:Tabl|tabl}}</nowiki> {{ut1|la}} gives: {{la|Help:Tabl|tabl}}<br />
<br />
*[[Template:Pvn]]<br />
<br />
==Templates and external links==<br />
<br />
Examples:<br />
<br />
*<nowiki>{{tle|insert in target|insert in label}}</nowiki> {{ut1|tle}}} gives {{tle|insert in target|insert in label}}<br />
*<nowiki>{{tle2|insert in target}}</nowiki> {{ut1|tle2}}} gives "{{tle2|insert in target}}"; note that brackets separated from the http:// are not recognized as belonging together:<br />
**<nowiki>[{{tle2|insert in target}} label]</nowiki> gives [{{tle2|insert in target}} label]<br />
**<nowiki>[{{tle2|insert in target}}]</nowiki> gives [{{tle2|insert in target}}]<br />
*<nowiki>{{tle3|insert in target}}</nowiki> {{ut1|tle3}}} gives {{tle3|insert in target}}<br />
*<nowiki>[http://a{{tciit}}b c{{tciil}}d]</nowiki> gives [http://a{{tciit}}b c{{tciil}}d]<br />
*<nowiki>http://a{{tciit}}b</nowiki> gives "http://a{{tciit}}b"<br />
*<nowiki>[http://a{{tciit}}b]</nowiki> gives [http://a{{tciit}}b]<br />
<br />
However, a URL can not be composed of:<br />
*a first part in a parameter and a second part added by the template (although we have seen above that reversed it works: a second part in a parameter and a first part prefixed by the template) <br />
*a first part in a template and a second part after the template (although we have seen above that reversed it works: the second part in a template and the first part before the template) <br />
<br />
Example of first restriction:<br />
<br />
*<nowiki>{{tae|http://www.}}</nowiki> {{ut1|tae}}} gives {{tae|http://www.}}<br />
<br />
Examples of second restriction:<br />
<br />
*<nowiki>[{{th}}add at the end]</nowiki> {{ut1|th}}} gives [{{th}}add at the end]<br />
*"<nowiki>{{th}}add at the end</nowiki>" gives "{{th}}add at the end"<br />
<br />
==Noinclude and includeonly==<br />
<br />
This feature is not available before version 1.6.<br />
<br />
Anything between <nowiki><noinclude> and </noinclude></nowiki> will be processed and displayed only when the page is being viewed directly; it will not be included or substituted.<br />
Possible applications are:<br />
<br />
# Categorising templates, see [[Help:template documentation|template documentation]].<br />
# [[Help:Interwiki_linking|Interlanguage link]]s to similar templates in other languages.<br />
# Pages in the [[Help:MediaWiki namespace|MediaWiki namespace]].<br />
<br />
<nowiki>The converse is <includeonly>. Text between <includeonly> and<br />
</includeonly></nowiki> will be processed and displayed only when the page is<br />
being included. Applications include:<br />
<br />
# Adding all pages containing a given template to a category, but not the template itself.<br />
# Avoiding messy rendering on the template page, e.g. {{evaldemo|#expr:{{{1}}}}}.<br />
<br />
Note that spaces and newlines between the general content and the tagged part belong to the general content. If they are not desired the include tag should directly follow the content on the same line:<br />
&lt;noinclude&gt;this is &lt;/noinclude&gt;fine&lt;includeonly&gt;, closing tags are<br />
&lt;/includeonly&gt;&lt;noinclude&gt;<br />
less critical, but must be specified.&lt;/noinclude&gt;<br />
<br />
Attempts to nest split pairs of these tags, or the similar <tt>&lt;nowiki&gt;</tt> and <tt>&lt;/nowiki&gt;</tt> pair, won't work as expected. If say <tt>&lt;nowiki&gt;</tt> begins within the general content,<br />
or in a "noinclude" part, or in an "includeonly" part, then it also has to be closed within the same part.<br />
<br />
The code <code><nowiki>~<includeonly>~</includeonly>~~</nowiki></code> will be displayed as <nowiki>~~~</nowiki> when the template is not included, <nowiki>~~~~</nowiki> when the template is included, and it will be expanded as the active user when the template is subst'd.<br />
<br />
== Wiki markup at the beginning of a template==<br />
If the first included character of a template is one of the Wiki markup characters '''<tt>:;*#</tt>''', then it's interpreted as being at the begin of the line (even when the template call is not).<br />
<br />
To avoid this effect use <tt>&lt;nowiki&gt;#&lt;/nowiki&gt;</tt> or a [[w:en:Numeric character reference|NCR]] like say <tt>&amp;#58;</tt> for a colon, this NCR is also useful in conjunction with definition [[Help:list|list]]s.<br />
<br />
==Substitution==<br />
<br />
:''Main article: '''[[Help:Substitution]]'''''<br />
<br />
Putting "subst:" after the double opening braces causes an [[Help:Automatic conversion of wikitext|automatic conversion of wikitext]] when the referring page is saved: the subst tag is replaced by the wikitext of the template, with the parameter values substituted for the parameters.<br />
<br />
==Redirection==<br />
<br />
When a page called for inclusion is a redirect page, the redirect target is included instead. As usual, a double redirect does not work.<br />
<br />
A page that consists of nothing else than the inclusion of another page as a template, shows similarities to a redirect to that other page, but also many differences, including:<br />
<br />
*the result has as header the name of the referring page<br />
*there is no redirect message<br />
*the buttons such as edit (for editing the whole page), watch, talk, history, "what links here", and "last modified", etc., refer to the referring page (to go to the target page, a section edit link can be used, from there the whole page can be accessed)<br />
*the referring page is in the same categories as the target page, except when includeonly and/or noinclude tags are used.<br />
*"double redirects", with one or both being this kind of "pseudo-redirect", work.<br />
<br />
Compare [[Help:Template namespace]] with [[Help:Template namespace - demo of alternative for redirect]].<br />
<br />
In a page that in turn includes such a referring page there is no difference.<br />
<br />
<br />
Note that embedding works for all pages where [[Help:Redirect|redirecting]] works, and it also fails for all pages where a redirect won't work.<br />
<br />
==Comparison of linking and embedding==<br />
Linking and embedding have in common:<br />
*if the page does not exist, a link to the edit page is shown; the links are identical if it is not a piped link; the link does not show parameters and does not show whether, after creation, the new page will be linked or embedded.<br />
*the name can depend on variables and parameters<br />
<br />
==Predefined templates==<br />
[[Help:Variable|Variable]]s and [[help:parser function|parser function]]s can be considered predefined templates. They do not have a page that defines in terms of wikitext what they do, because their action is something extra that cannot be constructed from more basic wikitext functionality.<br />
<br />
Some additional differences:<br />
*Parser functions use ":" instead of the first "|".<br />
*An edit page does not list predefined templates used on the page.<br />
*No "What links here" is available for predefined templates, to find the pages where they are used.<br />
*Apart from #switch, predefined templates don't allow you to define named parameters, and therefore equal signs generally have no special effect, comparison:<br />
*:<tt>{&#123; #if: not blank | 2=abc &#125;}</tt> gives '''{{ #if: not blank | 2=abc }}'''<br />
*:<tt>{&#123; ifdef | not blank | 2=abc &#125;}</tt> gives '''{{ ifdef | not blank | 2=abc }}'''<br />
*It's however possible to corrupt the value shown for undefined parameters without default, for more examples see {{tim|ifeq demo}}:<br />
*:<tt>{&#123; #if: {&#123;ns:0&#125;} | 2=xy | {&#123;{2|blank}&#125;} &#125;}</tt> gives '''{{ #if: {{ns:0}} | 2=xy | {{{2|blank}}} }}'''<br />
*:<tt>{&#123; #if: {&#123;ns:0&#125;} | 2=xy | {&#123;{2 }&#125;} &#125;}</tt> gives '''{{ #if: {{ns:0}} | 2=xy | {{{2 }}} }}'''<br />
*:<tt>{&#123; #if: {&#123;ns:0&#125;} | oops | {&#123;{1|blank}&#125;} &#125;}</tt> gives '''{{ #if: {{ns:0}} | oops | {{{1|blank}}} }}'''<br />
*:<tt>{&#123; #if: {&#123;ns:0&#125;} | oops | {&#123;{1 }&#125;} &#125;}</tt> gives '''{{ #if: {{ns:0}} | oops | {{{1 }}} }}'''<br />
<br />
Ordinary and predefined templates have in common that their parameter values can depend on ordinary and predefined templates. In the case of named parameters, the names used in the template call can also depend on ordinary and predefined templates. This applies also for the named parameters of #switch.<br />
<br />
==Code execution==<br />
"Evaluating" a template call internally involves, to start with, evaluating the template name, the parameter names, and the parameter values. Evaluating a predefined template involves the same, as far as applicable. This is relevant even if the wikitext resulting from these subevaluations cannot have effect on the overall wikitext, as in the case of #ifexpr etc. for either the then-part or the else-part, and in the case of an unused template parameter:<br />
<br />
*Subevaluations involving template calls add to the pre-expand include size (see [[w:Wikipedia:Template limits]]).<br />
*[[w:Side effect (computer science)|Side effects]]:<br />
**Subevaluations producing links add on the target page to the list of incoming links ([[Help:What links here|What links here]]), based on the [[mw:pagelinks table|pagelinks table]], even if there is no link on the resulting page.<br />
**Subevaluations involving template calls add on the template page in "What links here" and on the edit page of the page concerned to inclusion items, based on the [[mw:templatelinks table|templatelinks table]].<br />
**Some extensions may perform some action during a subevaluation, e.g. with [[VariablesExtension]] a subevaluation may involve assignment of a value to a variable. <br />
<br />
Thus <nowiki>{{ #ifexpr:.. | {{a|</nowiki>''parameters''}} | <nowiki>{{</nowiki>b |''parameters''}} }} evaluates <nowiki>{{a|</nowiki>''parameters''}} ''and'' <nowiki>{{b|</nowiki>''parameters''}} regardless of the condition. On the other hand, <nowiki>{{ {{</nowiki>#ifexpr:..|a|b}} | ''parameters'' }} just evaluates the expression for the template ''name'' (by evaluating the condition, and resulting in a or b) and the parameters, and the actually included template.<br />
<br />
See also [[ParserFunctions#Code_execution]].<br />
<br />
==Templates in different versions of MediaWiki==<br />
<br />
===Version 1.6===<br />
<br />
* More magic words and the [[Help:parameter default|parameter default]] mechanism were added.<br />
* <tt>&lt;noinclude&gt;</tt> and <tt>&lt;includeonly&gt;</tt> (see above) were added.<br />
<br />
===Version 1.5===<br />
<br />
* More [[Help:magic words|magic words]] were added.<br />
<br />
===Version 1.4===<br />
<br />
*Including the same template more than five times in the same page works from version 1.4, now on all Wikimedia sites. Also new was that subst can be used with parameters.<br />
<br />
===Version 1.3===<br />
<br />
* See, among other things, [{{fullurl:m:Help:Template|oldid=86075}}#Default_values_of_parameters default values of parameters]. Starting with version 1.3 the prefix "msg:" is generally optional. <br />
<br />
===Version 1.2.6===<br />
<br />
* In MediaWiki version 1.2.6, make a page MediaWiki:mytemplate and refer to it with <nowiki>{{msg:mytemplate}}</nowiki>. In this version parameters are not possible.<br />
* Compatibility with 1.3, in the sense of having the content in Template:mytemplate, is possible with a redirect from MediaWiki:mytemplate to Template:mytemplate on the 1.2.6 project.<br />
<br />
== Revision history of pages containing templates ==<br />
<br />
Pages in the stored [[Help:Page history|page history]] consist of wikitext with possible ''references'' to templates and images. When viewing an old version of a page, these refer to the current versions of the templates and images, if these still exist. Thus the former composite page is not reconstructed.<br />
<br />
==See also==<br />
*[[m:Help:Advanced templates|Help:Advanced templates]]<!-- m: not directly portable due to examples --> <br />
*[[Help:Calculation]]<!-- maybe portable, test it --><br />
*[[Help:Parser function]] <br />
*[[m:ParserFunctions|ParserFunctions]]<br />
*[[m:Help:Parameter default|Help:Parameter default]]<!-- m: --><br />
*[[Help:Magic words]]<br />
*[[Help:Substitution]]<!-- maybe portable, test it --><br />
*[[Help:Template documentation]]<br />
*[[Help:Variable]]<br />
*[[Help:What links here]]<br />
*[[mw:Manual:$wgEnableScaryTranscluding|interwiki transclusion]]<br />
*[[m:Help:MediaWiki help policy|MediaWiki help templates]]<br />
*[{{fullurl:Special:Allpages|namespace=10}} List of all templates on this server]<br />
*[[Templates of Wikimedia projects]]<br />
*[[w:Wikipedia:Template namespace]]<br />
*[[Special:ExpandTemplates]] ([http://svn.wikimedia.org/viewvc/mediawiki/trunk/extensions/ExpandTemplates/ download this extension])<br />
*[[mw:Extension:Labeled Section Transclusion]] - transclusion of part of a page<br />
*[[w:Wikipedia:Template doc page pattern]]<br />
*[[w:Wikipedia:Template limits]]<br />
*[[DynamicFunctions##arg:]] - instead of including a page for given parameter values, this allows linking to a page for given parameter values. Syntax for parameter use: <nowiki>{{</nowiki>arg:''parameter name''|''default''}}. Syntax for linking: external link style with "&''parameter name''=''parameter value''" added to the URL.<br />
*[[w:Wikipedia:Transclusion costs and benefits]]<br />
<br />
{{h:f|enname=Template}}</div>HybridBoyhttps://wikicars.org/index.php?title=Wikicars_FAQ&diff=48552Wikicars FAQ2007-03-25T15:34:00Z<p>HybridBoy: </p>
<hr />
<div>Here are some frequently-asked questions about Wikicars, along with answers. You are welcome to post more questions, although we ask you to do so in the Discussion page first.<br />
<br />
<br />
'''Who writes the content on Wikicars?'''<br />
<br />
Car owners and enthusiasts like you create Wikicars content. Car experts in the automotve division of Internet Brands helped launch the project and are ongoing contributors; they drew on their own experience in the automotive industry and as car-owners, as well as publicly available information from Internet Brands' automotive sites, Wikipedia and government sites.<br />
<br />
<br />
'''How does Wikicars make money?'''<br />
<br />
Wikicars was initially created as a labor of love by the car-loving employees of Internet Brands' automotive businesses. Although there are no immediate plans, the site is likely to eventually include non-obtrusive, context sensitive ads, similar to Google adsense.<br />
<br />
<br />
'''Is Wikicars an encyclopedia or a guide?'''<br />
<br />
Wikicars is both. Wikicars aspires to be the most comprehensive source of fact based information about automobiles -- a Wikipedia of cars. At the same time, Wikicars is a guidebook, offering the consensus opinion of our community about the good, the bad, and the ugly of the automotive world. We believe this consensus opinion is very helpful; opinion and reviews that reflect the collective views of many people are much more likely to be accurate and unbiased. We have attempted to clearly label the opinion parts of the site. Some pages, such as Car Review Pages, are designed to be primarily opinion. Other pages have specifically labeled sections called "criticisms".<br />
<br />
<br />
'''How is Wikicars different from Wikipedia?'''<br />
<br />
Wikicars was inspired by Wikipedia and follows many of its policy and style guidelines. But there are differences:<br />
<br />
- Wikicars solicits and offers content that is exclusively focused on automotive, including many contributions from Internet Brands content libraries.<br />
<br />
- Wikicars encourages users to voice their opinions as added color to vehicle history and fact-sets. (See "Is Wikicars an encyclopedia or a guide? question above.)<br />
<br />
- Wikicars is organized to help car-shoppers as much as enthusiasts or historians. For example, information on more recent models is displayed more prominently since most net searchers are interested in more recent years of a given model.<br />
<br />
<br />
'''How comprehensive is Wikicars?'''<br />
<br />
Wikicars offers articles on every major make and model sold in the United States, as well as related topics, such as hybrid technology, common vehicle features, automotive financing and car-buying.<br />
<br />
<br />
'''How does Wikicars ensure the accuracy of its articles?'''<br />
<br />
The best editors in the world are the millions of car owners, shoppers and enthusiasts who regularly use the internet and sites like Wikicars. Mistakes or inaccuracies occur in any automotive content, but the Wiki collaborative editing process ensures that Wikicars content reflects the finely-honed consensus (or clearly-labeled opinions) of the driving public.<br />
<br />
<br />
'''Will Wikicars go international?'''<br />
<br />
Wikicars seeks to be the most authoritative automotive site in the world. Users from outside of the United States are encouraged to start their own country's versions, and Internet Brands can help get them up and running. A discussion about international Wikicars issues is on the discussion page.<br />
<br />
-----<br />
See also : <br />
* [[Help:Template]]</div>HybridBoyhttps://wikicars.org/index.php?title=Category:Demo_template&diff=48551Category:Demo template2007-03-25T15:30:15Z<p>HybridBoy: </p>
<hr />
<div>[[Category:Templates]]</div>HybridBoyhttps://wikicars.org/index.php?title=Category:Demo_template&diff=48550Category:Demo template2007-03-25T15:30:05Z<p>HybridBoy: </p>
<hr />
<div>[[Category:Template]]</div>HybridBoyhttps://wikicars.org/index.php?title=Template:T2demo&diff=48549Template:T2demo2007-03-25T15:29:48Z<p>HybridBoy: </p>
<hr />
<div><!--t2-->start-{{{1}}}-middle-{{{2}}}-end<noinclude>[[Category:Demo template]]</noinclude></div>HybridBoyhttps://wikicars.org/index.php?title=Template:T_sup&diff=48548Template:T sup2007-03-25T15:28:09Z<p>HybridBoy: </p>
<hr />
<div>{{{1}}}-{{{2}}}-{{{3}}}<noinclude>[[category:Handbook templates]]</noinclude></div>HybridBoyhttps://wikicars.org/index.php?title=Template:TTT&diff=48547Template:TTT2007-03-25T15:26:15Z<p>HybridBoy: </p>
<hr />
<div>{{{1}}}{{{2}}}<noinclude>[[category:Handbook templates]]</noinclude></div>HybridBoyhttps://wikicars.org/index.php?title=Template:TTT&diff=48546Template:TTT2007-03-25T15:24:45Z<p>HybridBoy: </p>
<hr />
<div>{{{1}}}{{{2}}}<br />
<noinclude>[[category:Handbook templates]]</noinclude></div>HybridBoyhttps://wikicars.org/index.php?title=Template:Tcw&diff=48545Template:Tcw2007-03-25T15:22:13Z<p>HybridBoy: </p>
<hr />
<div>[[Template:{{{1}}}]] containing "<span style="background-color:#c8f0ff; padding:0 3px 2px 3px;">{{msgnw:{{{1}}}}}</span>"<br />
<noinclude>[[Category:Templates]]</noinclude></div>HybridBoyhttps://wikicars.org/index.php?title=Template:Tcw&diff=48544Template:Tcw2007-03-25T15:21:53Z<p>HybridBoy: </p>
<hr />
<div>[[Template:{{{1}}}]] containing "<span style="background-color:#c8f0ff; padding:0 3px 2px 3px;">{{msgnw:{{{1}}}}}</span>"<br />
<noinclude>[[Catetegory:Templates]]</noinclude></div>HybridBoyhttps://wikicars.org/index.php?title=Template:T&diff=48542Template:T2007-03-25T15:18:23Z<p>HybridBoy: </p>
<hr />
<div><includeonly><!--t-->start-{{{1|pqr}}}-end</includeonly><noinclude><nowiki>start-{{{1|pqr}}}-end</nowiki><br />
<br />
== Examples ==<br />
{| class="wikitable"<br />
! Code<br />
! Result<br />
|- style="vertical-align:top;"<br />
| <pre><br />
{{T}}<br />
</pre><br />
||{{T}}<br />
|- style="vertical-align:top;"<br />
| <pre><br />
{{T|}}<br />
</pre><br />
||{{T|}}<br />
|- style="vertical-align:top;"<br />
| <pre><br />
{{T|abc}}<br />
</pre><br />
||{{T|abc}}<br />
|- style="vertical-align:top;"<br />
| <pre><br />
{{T|abc|def}}<br />
</pre><br />
||{{T|abc|def}}<br />
|- style="vertical-align:top;"<br />
| <pre><br />
{{T|1=abc|1=def}}<br />
</pre><br />
||{{T|1=abc|1=def}}<br />
|- style="vertical-align:top;"<br />
| <pre><br />
{{T|abc|1=def}}<br />
</pre><br />
||{{T|abc|1=def}}<br />
|- style="vertical-align:top;"<br />
| <pre><br />
{{T|1=abc|def}}<br />
</pre><br />
||{{T|1=abc|def}}<br />
|- style="vertical-align:top;"<br />
| <pre><br />
{{T|{{T}}}}<br />
</pre><br />
||{{T|{{T}}}}<br />
|- style="vertical-align:top;"<br />
| <pre><br />
{{T|{{T|{{T}}}}}}<br />
</pre><br />
||{{T|{{T|{{T}}}}}}<br />
|- style="vertical-align:top;"<br />
| <pre><br />
{{T|{{T|{{T|{{T}}}}}}}}<br />
</pre><br />
||{{T|{{T|{{T|{{T}}}}}}}}<br />
|- style="vertical-align:top;"<br />
| <pre><br />
{{T|a{{t|b}}}}<br />
</pre><br />
||{{T|a{{t|b}}}}<br />
|- style="vertical-align:top;"<br />
| <pre><br />
{{T|{{T|a<nowiki>=</nowiki>b}}}}<br />
</pre><br />
||{{T|{{T|a=b}}}}<br />
|- style="vertical-align:top;"<br />
| <pre><br />
{{T|<nowiki>a=b</nowiki>}}<br />
</pre><br />
||{{T|a=b}}<br />
|- style="vertical-align:top;"<br />
| <pre><br />
{{T|1<nowiki>=a=b</nowiki>}}<br />
</pre><br />
||{{T|1=a=b}}<br />
|}<br />
[[Category:Templates]]<br />
</noinclude></div>HybridBoy