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.

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 &#35; (hash, &amp;#36;), &#124; (pipe, &amp;#124), &#61; (equals, &amp#61;), &quot; (straight double quote, &amp;quot;) will not work as expected. However, the latter can be worked around with =; a redirect with "=" in its name will link properly to an anchor with = . Any of these characters can be replaced with the "&amp;#" codes shown for them here. Markup code such as undefined and undefined (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.
 * Putting each anchor name on separate lines, for example
 * will probably not work as expected.
 * will probably not work as expected.


 * Anchor names should be unique on a page, and should not duplicate any heading titles. Duplicate anchors won't work as expected since the #links go to the first anchor with that name. Duplicate anchors also result in invalid HTML, so you can check for duplicate anchors by consulting 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.