قالب:Sc2/doc

{{Smallcaps2}} will display the lowercase part of your text as a soft format of typographical small caps.
For example: {{smallcaps2|Beware of Dog}} → Beware of Dog.

This template should be avoided or used sparingly in articles, as the Manual of Style advises that small caps should be avoided and reduced to one of the other title cases or normal case and markup should be kept simple.

Smallcaps should not be used for BC, AD, BCE, CE, etc., per MOS:ERA, though they are used in the below examples.

Usage

Your source text is not altered in the output, only the way it is displayed on the screen: a copy-paste of the text will give the small caps sections in their original form; similarly, an older or non-CSS browser will only display the original text on screen.

Code

Your Text in 4004 {{Smallcaps2|BCE}}

Displayed

Your Text in 4004 BCE

Pasted

Your Text in 4004 BCE

Because it reduces the font size so that the capital letters marked up with the template are smaller than those of the running text, and makes the lower-case content smaller still, this template should only be used for acronyms or other material which is supposed to be capitalized regardless of style (e.g. Unicode character names). It is not intended for the use of small caps as a general typographic style, such as rendering family names in bibliographies in small caps to distinguish them from given names. For such cases, use {{Smallcaps}}.

Technical notes

{{TOC right}} forces the auto-generated Table of Contents for a page to appear in a table that is floated to the right side of the page, in order to improve page layout.

Usage

Insert {{TOC right}} at the point in the page where you want the top of the Table of Contents box to appear. Use with {{-}} or {{clear}} to prevent collision with text; use the clear parameter (see below) to prevent collision with images.

Parameters (optional)

clear

Sets the CSS clear property, which forces this float underneath the side specified with this attribute. So, clear=right (which is the default) will place the element after all the right floating elements before it. Options are left, right, both, or none.

width

Set the CSS width.

limit

Limits the depth of subheadings shown. For instance using limit=4 will hide the fourth level and deeper subheadings in the hierarchy. And limit=2 will hide all subheadings leaving only the main headings. This is implemented as a CSS class in the MediaWiki:Common.css/toc.css.

• Avoid placing the TOC in a visually poor location. Crossing a section division is probably a poor idea.
• If the TOC is floated left of a bulleted list, the bullets will be hidden.

Cautions

Do not place this template so that the TOC aligns with a large image or infobox; this breaks the layout on narrow screens (even users with screens as wide as 1024px wide can have problems). Also, a TOC that crosses a section division is probably a poor idea, if that can be avoided.

Unless the section in which the {{TOC right}} is placed is long enough, the result may well be undesirable.

It should only be used in cases where the TOC gets in the way of other content or is detrimental to the layout of the page. See Help:Editing#Floating the TOC for further guidelines.

See also

• {{TOC}}
• {{TOC left}}

The template {{anchor}} inserts one or more HTML anchors in a page. Those locations can then be linked to using [[#link|...]] syntax.

Examples

1. {{sc2|foo}}

could be linked to with [[#foo|...]] from within the same page,

or it could be linked to with [[pagename#foo|...]] from other pages and from redirects.

2. Anchors can be more suitable for inter-page linking than section titles are. For example,

=={{sc2|foo}} Section title ==

Here, links via [[articlename#foo]] 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,

{{sc2|foo|bar|baz}}

will create three anchors that can then be linked to with [[#foo]], [[#bar]] and [[#baz]].

Specifying more than 10 anchors will cause an error message to be displayed.

Limitations

• Anchor names that contain # (hash), | (pipe), = (equal) will not work as expected. 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

{{sc2

|humpty
|dumpty}}

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 "/* {{anchor|Issues}}Limitations */ New issue". This can be fixed by deleting the template code from the edit summary before the changes are saved.

• Diacritics (å, ç, é, ğ, ı, ñ, ø, ş, ü, etc.) are handled. However, because the job is performed by each reader's browser and fonts, inconsistencies in CSS implementations can lead to some browsers not converting certain rare diacritics.
• Use of this template does not generate any automatic categorization. As with most templates, if the argument contains an = sign, the sign should be replaced with {{=}}, or the whole argument be prefixed with |1=. And for wikilinks, you need to use piping. There is a parsing problem with MediaWiki which causes unexpected behavior when a template with one style is used within a template with another style.
• There is a problem with dotted and dotless I. {{Lang|tr|{{Smallcaps2|ı i}}}} may gives you ı ı, although the language is set to Turkish, unless the font including localized glyphs for small caps variant.
• Do not use this inside Citation Style 1 or Citation Style 2 templates, or this template's markup will be included in the COinS metadata. This means that reference management software such as Zotero will have entries corrupted by the markup. For example, if {{smallcaps}} is used to format the surname of Bloggs, Joe in {{cite journal}}, then Zotero will store the name as <span class="smallcaps smallcaps-smaller">Bloggs</span>, Joe. This is incorrect metadata. If the article that you are editing uses a citation style that includes small caps, either format the citation manually (see examples below) or use a citation template that specifically includes small caps in its formatting, like {{Cite LSA}}.
• This template will not affect the use of HTML character entities like  .
• A potential alternative CSS approach, font-variant: small-caps; text-transform: lowercase;, has not been used because it forced transform all letters to be lowercase.

Suppressing small caps

If you wish to suppress the display of small caps in your browser, as a logged-in user, you can make an edit to your common.css reading: body .mw-parser-output span.smallcaps { font-variant: normal; }

If you wish to avoid the size change: body .mw-parser-output span.smallcaps-smaller { font-size: inherit; }

Comparison of the case transformation templates

Template	Shortcut	Purpose	Example	Output	Copy-pastes as
{{Smallcaps}}	{{sc1}} {{SC}}	No conversion, small-caps display, mixed case. No font size change (acronyms are unaffected). Common mixed-case heading style (not in Wikipedia). Uses: Rendering publication titles in citation styles that require them in small-caps.	{{sc1|UNICEF}} and 312 {{sc1|BCE}}	UNICEF and 312 BCE Mixed Case	UNICEF and 312 BCE Mixed Case
{{Smallcaps2}}	{{sc2}}	No conversion, small-caps display, mixed case. Slightly reduced font size. This is the conventional display of smallcaps for acronyms/initialisms in modern book typography. Other uses: Unicode character names.	{{sc2|UNICEF}} and 312 {{sc2|BCE}}	UNICEF and 312 BCE Mixed Case	UNICEF and 312 BCE Mixed Case
{{Smallcaps all}}	{{sc}}	Lowercase conversion, small-caps display, all uppercase. The size of lowercase letters. Uses: Stressed syllables (in {{Respell}}); and ???. : Default use will permanently change UPPER- or Mixed-Case data, does not work consistently across different browsers, and is not compatible with named HTML character entities.	{{sc|UNICEF}} and 312 {{sc|BCE}}	UNICEF and 312 BCE MIXED CASE	unicef and 312 bce mixed case (in many browsers)
{{Allcaps}}	{{caps}}	No conversion, all-caps display. The size of uppercase letters. Uses: ???.	{{caps|UNICEF}} and 312 {{caps|BCE}}	UNICEF and 312 BCE Mixed Case	UNICEF and 312 BCE Mixed Case
{{Nocaps}}		No conversion, all-lowercase display. The size of lowercase letters. Uses: ???.	{{nocaps|UNICEF}} and 312 {{nocaps|BCE}}	UNICEF and 312 BCE Mixed Case	UNICEF and 312 BCE Mixed Case

TemplateData

This is the TemplateData for this template used by TemplateWizard, VisualEditor and other tools. Click here to see a monthly parameter usage report for this template based on this TemplateData.

TemplateData for Sc2

لا وصف.

وسائط القالب

وسيط		وصف	نوع	حالة
1	1	دون وصف	غير معروف	اختياري

See also

• {{Smallcaps}}
• {{R from other capitalisation}} – for categorizing WP:Redirects from titles to article (or other pages) where the redirect is just a different capitalization
• {{Template capitalization}} – ??
• Module:String2

Magic words that rewrite the output (copy-paste will get the text as displayed, not as entered):

• {{lc:}} – lower case output of the full text
• {{uc:}} – upper case output of the full text
• {{lcfirst:}} – lower case output of the first character only
• {{ucfirst:}} – upper case output of the first character only