Template:Anchor/doc

The template inserts one or more HTML anchors in a page. Those locations can then be linked to using  syntax.

Examples
1.
 * could be linked to with  ...  from within the same article,
 * or it could be linked to with  ...  from other articles and from redirects.

2. Anchors can be more suitable for inter-article linking than section titles are. For example,
 * Section title ==
 * Here, links via  articlename  would remain valid even if the section were renamed. Consider using  beneath the section title to generate an HTML comment alerting other editors to the purpose of anchors used in this manner.

3. The template can be used to create up to ten anchors with a single call. For example,
 * will create three anchors that can then be linked to with  ,    and   .
 * Specifying more than 10 anchors will cause an error message to be displayed.
 * Specifying more than 10 anchors will cause an error message to be displayed.

Limitations

 * Anchor names that contain any character shown in the table on the right will not work as expected. However, any of these characters can be replaced with the "&amp;#" codes shown for them here. Or, the pipe symbol and equals sign can be worked around with ! and =, respectively. Markup code such as and  (superscript and subscript) cannot be used. Most other characters, including white space and punctuation, are not a problem.
 * The template can create a maximum of 10 anchors. Specifying more than 10 anchors will result in an error message.
 * Unlike with most templates, putting each anchor name on separate lines, for example
 * will not work as expected.
 * will not work as expected.


 * Anchor names should be unique on a page, and should not duplicate any heading titles. Duplicate anchors will not work as expected since the #links go to the first anchor with that name. Duplicate anchors also result in invalid HTML; you can check for duplicate anchors by running the page through the W3C Markup Validation Service.
 * If the template is added to a section title then the code will appear in the edit summary when that section is edited, as in "/* Limitations */ New issue" . This can be fixed by deleting the template code from the edit summary before the changes are saved. Consider using beneath the section title to generate an HTML comment alerting other editors to the purpose of anchors used in this manner, so they do not move the anchor out of the section heading when they notice the deleterious effects on their edit summary.
 * Anchor links are case sensitive in some browsers, so treat all anchor link as case sensitive.

Related pages

 * Anchored list
 * Anchor comment
 * Shortcut
 * WP:ANCHOR
 * WP:TARGET
 * WP:TARGET

ar:قالب:أنجر bar:Vorlage:Anker be:Шаблон:Anchor be-x-old:Шаблён:Якар bg:Шаблон:Anchor bjn:Citakan:Anchors ca:Plantilla:Àncora cs:Šablona:Kotva cy:Nodyn:Angor da:Skabelon:Anchor de:Vorlage:Anker dsb:Pśedłoga:Anchor el:Πρότυπο:Anchor en:Template:Anchor eo:Ŝablono:Ankro es:Plantilla:Ancla et:Mall:Ankur eu:Txantiloi:Aingura fa:الگو:لنگر fr:Modèle:Ancre jv:Cithakan:Anchors ko:틀:Anchor hsb:Předłoha:Anchor hu:Sablon:Horgony hy:Կաղապար:Խարիսխ id:Templat:Anchor is:Snið:Anchor it:Template:Anchor he:תבנית:עוגן2 ks:Template:Anchor sw:Template:Anchor la:Formula:Ancora mk:Шаблон:Котва ml:ഫലകം:Anchor mi:Template:Anchor nl:Sjabloon:Anker ja:Template:Anchors no:Mal:Anchor nn:Mal:Anchor oc:Modèl:Ancòra ps:کينډۍ:Anchor nds:Vörlaag:Anchor os:Шаблон:Anchor pl:Szablon:Anchor pt:Predefinição:Âncora ro:Format:Anchor rmy:Sikavno:Anchor ru:Шаблон:Якорь tn:Template:Anchor sq:Stampa:Anchor simple:Template:Anchor sd:Template:Anchor se:Málle:Anchor sl:Predloga:Sidro sr:Шаблон:Anchor fi:Malline:Anchor sv:Mall:Anchor te:మూస:Anchor tpi:Template:Anchor tr:Şablon:Anchor vi:Tiêu bản:Anchor uk:Шаблон:Якірець yi:מוסטער:Anchor zh:Template:Anchor