Trachinus radiatus

-mul- template test

Purpose: verify rendering consistency in multilingual contexts, minimal single-word inputs compatibility, and interactions with other multilingual templates.

Basic cases (single-word input)

• Input: → Expectation: multilingual label mul wrapping "Hello"
• Input: → Expectation: multilingual label mul wrapping "Bonjour"
• Input: → Expectation: multilingual label mul wrapping "你好"

With language parameter (override)

• Input: → Expectation: if override allowed, use es; otherwise fallback to mul
• Input: → Expectation: same logic as above

Empty and whitespace

• Input: → Expectation: no render or empty placeholder; log a warning if applicable
• Input: → Expectation: same; template should avoid throwing errors

Special characters

• Input: → Expectation: diacritics rendered correctly
• Input: → Expectation: diaeresis preserved
• Input: → Expectation: full-width characters preserved

Interaction with other multilingual templates

• Input:

Purpose

The {{Mul}} template is a lightweight tool for listing several language versions of the same name or expression side by side. Typical use cases include:

• Giving a person's name in the original language and in common transliterations;
• Showing multiple names for a place in different languages;
• Listing original and translated titles of works, institutions or organizations.

Compared with manually writing brackets and separators in every article, {{Mul}} helps to:

• Keep formatting and ordering consistent across pages;
• Make it easier to change the separator or style globally;
• Keep article wikitext cleaner and more readable.

Basic syntax

The general syntax is:

{{Mul
|lang1 = text 1
|lang2 = text 2
|lang3 = text 3
|sep   = custom separator (optional)
|wrap  = wrapping style (optional)
}}

This template is intentionally generic. It does not force specific languages into specific parameters. Instead, you fill in numbered parameters with any content you need, including your own language labels if desired.

Parameters

Required parameters

At least one language-text parameter is required:

|lang1=, |lang2=, |lang3=, …

The actual text to be displayed (for example, an Arabic form of a name, an English form, a Chinese form, etc.).

 The parameter number does not itself indicate a language – you may include labels such as "Arabic:", "English:" directly in the text.

Example:

{{Mul
|lang1 = Arabic: ماهر الأسد
|lang2 = English: Maher al-Assad
}}

Renders as (depending on local implementation):

Optional parameters

|sep=

Custom separator between language items.

 * If omitted, a default such as  •  (space–middle dot–space) is used.  
 * You can set it to any text, for example /, ,  or a localized word.

|wrap=

Controls optional wrapping around the whole list. Suggested values:

 * brackets – wrap with fullwidth square brackets, such as ［...］
 * parentheses – wrap with round brackets, such as (...)
 * none (or left empty) – no extra wrapping

Example:

{{Mul
|lang1 = Arabic: ماهر الأسد
|lang2 = English: Maher al-Assad
|sep   = /
|wrap  = parentheses
}}

Might display as: (Arabic: ماهر الأسد / English: Maher al-Assad)

Examples

Person name example

In the lead of a biographical article, you might write:

'''Maher al-Assad''' ({{Mul
  |lang1 = Arabic: ماهر الأسد
  |lang2 = Transliteration: Maher al-Assad
  |wrap  = parentheses
}}; born 8 December 1967) is a Syrian military officer...

This keeps all language forms neatly grouped after the bolded name, in a style commonly used for biographies.

Place name example

'''Damascus''' ({{Mul
  |lang1 = Arabic: دمشق
  |lang2 = English: Damascus
  |wrap  = brackets
}}) is the capital of Syria...

Which may display as: Damascus［Arabic: دمشق • English: Damascus］

Work title example

The novel ''Example Book'' ({{Mul
  |lang1 = Original title: عنوان مثال
  |lang2 = English title: Example Book
}}) was first published in...

Behaviour and design

The {{Mul}} template is designed to be:

• **Inline** – it does not introduce line breaks by itself;
• **Lightweight** – it does not perform complex logic or language detection;
• **Flexible** – it does not enforce any particular language codes or ordering.

Important characteristics:

• It does not automatically add <span lang="xx"> tags;
• It does not automatically link to language help pages;
• It does not assume which languages are being used – all visible labeling is up to the editor.

If you need strict language markup (for screen readers, accessibility, or typography reasons), consider combining {{Mul}} with other language-specific templates or modules, or using explicit HTML language tags in the parameter contents.

Template code

The following is a sample implementation. Local wikis may adapt this to their own conventions, add more parameters, or integrate with Lua modules if needed.

{{#vardefine:sep|{{#if:{{{sep|}}}|{{{sep}}}| • }} }}

{{#vardefine:wrap-open|
  {{#switch:{{lc:{{{wrap|none}}}}}
    |brackets     = ［
    |parentheses  = (
    |#default     =
  }}
}}

{{#vardefine:wrap-close|
  {{#switch:{{lc:{{{wrap|none}}}}}
    |brackets     = ］
    |parentheses  = )
    |#default     =
  }}
}}

{{#if:{{{lang1|}}}|
  {{#var:wrap-open}}
  {{{lang1}}}
  {{#if:{{{lang2|}}}|{{#var:sep}}{{{lang2}}}|}}
  {{#if:{{{lang3|}}}|{{#var:sep}}{{{lang3}}}|}}
  {{#if:{{{lang4|}}}|{{#var:sep}}{{{lang4}}}|}}
  {{#if:{{{lang5|}}}|{{#var:sep}}{{{lang5}}}|}}
  {{#var:wrap-close}}
}}

This sample supports |lang1= through |lang5=. To support more languages, extend the pattern with additional lang6, lang7, etc., lines.

• {{Lang}} – commonly used to tag text with a specific language
• {{IPA}} – for displaying the International Phonetic Alphabet
• {{Tnavbar}} – template navigation bar
• Help:Template – general help on templates
• Help:Multilingual – guidance on handling multilingual content → Compare rendering (Meta’s

Purpose

The {{Mul}} template is a lightweight tool for listing several language versions of the same name or expression side by side. Typical use cases include:

• Giving a person's name in the original language and in common transliterations;
• Showing multiple names for a place in different languages;
• Listing original and translated titles of works, institutions or organizations.

Compared with manually writing brackets and separators in every article, {{Mul}} helps to:

• Keep formatting and ordering consistent across pages;
• Make it easier to change the separator or style globally;
• Keep article wikitext cleaner and more readable.

Basic syntax

The general syntax is:

{{Mul
|lang1 = text 1
|lang2 = text 2
|lang3 = text 3
|sep   = custom separator (optional)
|wrap  = wrapping style (optional)
}}

This template is intentionally generic. It does not force specific languages into specific parameters. Instead, you fill in numbered parameters with any content you need, including your own language labels if desired.

Parameters

Required parameters

At least one language-text parameter is required:

|lang1=, |lang2=, |lang3=, …

The actual text to be displayed (for example, an Arabic form of a name, an English form, a Chinese form, etc.).

 The parameter number does not itself indicate a language – you may include labels such as "Arabic:", "English:" directly in the text.

Example:

{{Mul
|lang1 = Arabic: ماهر الأسد
|lang2 = English: Maher al-Assad
}}

Renders as (depending on local implementation):

Optional parameters

|sep=

Custom separator between language items.

 * If omitted, a default such as  •  (space–middle dot–space) is used.  
 * You can set it to any text, for example /, ,  or a localized word.

|wrap=

Controls optional wrapping around the whole list. Suggested values:

 * brackets – wrap with fullwidth square brackets, such as ［...］
 * parentheses – wrap with round brackets, such as (...)
 * none (or left empty) – no extra wrapping

Example:

{{Mul
|lang1 = Arabic: ماهر الأسد
|lang2 = English: Maher al-Assad
|sep   = /
|wrap  = parentheses
}}

Might display as: (Arabic: ماهر الأسد / English: Maher al-Assad)

Examples

Person name example

In the lead of a biographical article, you might write:

'''Maher al-Assad''' ({{Mul
  |lang1 = Arabic: ماهر الأسد
  |lang2 = Transliteration: Maher al-Assad
  |wrap  = parentheses
}}; born 8 December 1967) is a Syrian military officer...

This keeps all language forms neatly grouped after the bolded name, in a style commonly used for biographies.

Place name example

'''Damascus''' ({{Mul
  |lang1 = Arabic: دمشق
  |lang2 = English: Damascus
  |wrap  = brackets
}}) is the capital of Syria...

Which may display as: Damascus［Arabic: دمشق • English: Damascus］

Work title example

The novel ''Example Book'' ({{Mul
  |lang1 = Original title: عنوان مثال
  |lang2 = English title: Example Book
}}) was first published in...

Behaviour and design

The {{Mul}} template is designed to be:

• **Inline** – it does not introduce line breaks by itself;
• **Lightweight** – it does not perform complex logic or language detection;
• **Flexible** – it does not enforce any particular language codes or ordering.

Important characteristics:

• It does not automatically add <span lang="xx"> tags;
• It does not automatically link to language help pages;
• It does not assume which languages are being used – all visible labeling is up to the editor.

If you need strict language markup (for screen readers, accessibility, or typography reasons), consider combining {{Mul}} with other language-specific templates or modules, or using explicit HTML language tags in the parameter contents.

Template code

The following is a sample implementation. Local wikis may adapt this to their own conventions, add more parameters, or integrate with Lua modules if needed.

{{#vardefine:sep|{{#if:{{{sep|}}}|{{{sep}}}| • }} }}

{{#vardefine:wrap-open|
  {{#switch:{{lc:{{{wrap|none}}}}}
    |brackets     = ［
    |parentheses  = (
    |#default     =
  }}
}}

{{#vardefine:wrap-close|
  {{#switch:{{lc:{{{wrap|none}}}}}
    |brackets     = ］
    |parentheses  = )
    |#default     =
  }}
}}

{{#if:{{{lang1|}}}|
  {{#var:wrap-open}}
  {{{lang1}}}
  {{#if:{{{lang2|}}}|{{#var:sep}}{{{lang2}}}|}}
  {{#if:{{{lang3|}}}|{{#var:sep}}{{{lang3}}}|}}
  {{#if:{{{lang4|}}}|{{#var:sep}}{{{lang4}}}|}}
  {{#if:{{{lang5|}}}|{{#var:sep}}{{{lang5}}}|}}
  {{#var:wrap-close}}
}}

This sample supports |lang1= through |lang5=. To support more languages, extend the pattern with additional lang6, lang7, etc., lines.

See also

• {{Lang}} – commonly used to tag text with a specific language
• {{IPA}} – for displaying the International Phonetic Alphabet
• {{Tnavbar}} – template navigation bar
• Help:Template – general help on templates
• Help:Multilingual – guidance on handling multilingual content )
• Input:

Template:For-multi is a small test template used to demonstrate how non‑Latin characters and inline HTML can be handled in wikitext.

Minimal example:

α γ A

In raw wikitext, this is simply:

α
&gamma; <span lang="de">A</span>

• α is the Greek small letter alpha, written directly as a Unicode character.
• γ is an HTML character entity for the Greek small letter gamma.
• <span lang="de">A</span> wraps the character A in a <span> with a language attribute (lang="de" for German).

Usage

A typical usage on a test page might be:

{{For-multi}}

which could expand, for testing purposes, to something like:

α γ A

This is useful to verify that:

• Greek characters display correctly;
• HTML entities like γ render as expected;
• language‑tagged spans are preserved and interpreted correctly by the software and by assistive technologies.

• Help:HTML in wikitext
• Help:Special characters → Verify hatnote templates do not conflict with -mul- styling

Internal data container reference

• Input: ffnonesenseword catapult pickles anotherword

{{{1}}}

Categoria:Template senza TemplateData

Usage

This template is used to define a short description for the current page. The description is typically:

• brief – usually fewer than 40 characters;
• neutral and descriptive;
• supplementary to the article title, not simply a repeat of it.

Short descriptions are mainly consumed by tools and skins (for example, mobile views and search interfaces) and are not always shown in the normal desktop view.

Basic usage

To add a short description to a page:

{{Short description|Encyclopedia of free educational textbooks}}

This stores the description Encyclopedia of free educational textbooks for the current page.

Preventing replacement

If a description is already supplied (for example, from a higher level template) and you want to make sure that a local call does not overwrite it, use the noreplace parameter:

{{Short description|Free-content textbook project|noreplace=yes}}

In this case, if a short description has already been set elsewhere on the page, this call will be ignored.

Specifying a page type

You may optionally supply a page type. This can be helpful for tools that group or filter pages:

{{Short description|Open-content textbook collection|pagetype=project}}

or

{{Short description|Polynomial invariant measuring multiple roots|pagetype=mathematics}}

Notes

• The short description should normally be in sentence case, without a final period:

 
Correct: Online free-content textbook collection  
 Avoid: online FREE-CONTENT TEXTBOOK COLLECTION.

• Avoid adding links, HTML tags or wikicode. The value is intended to be plain text.
• Do not add maintenance notes, talk-page comments or other discussion content to the short description.

See also

• Help:Short description
• Wikipedia:Short description
• Template:Long description

UCI team code is a short alphanumeric identifier used to uniquely represent a team in certain sports, especially in cycling disciplines such as Road bicycle racing and Track cycling. The code appears in entry lists, official results, rankings and technical documents to provide a language‑independent way to identify the same team across different events and data systems.

Purpose

UCI‑style team codes are primarily used to:

• uniquely identify a team in registration systems;
• shorten long team names in official results;
• serve as a stable key in rankings and statistical databases;
• appear on on‑screen graphics and scoreboards alongside rider names.

While spectators usually see full team names or commercial names, officials, Sports data providers and technical officials rely heavily on a consistent team code in order to avoid ambiguity.

Format

The exact format can vary between governing bodies, but common characteristics include:

• composed mainly of uppercase Latin letters, often 2–4 characters long;
• chosen to avoid collisions with existing team or country codes;
• designed to have some mnemonic link to the team name, sponsor or home country;
• kept stable within a season so that statistics remain comparable.

In some frameworks, digits or prefixes may be added to distinguish different levels of teams or to separate codes used in different disciplines with similar team names.

Allocation and management

Team codes are usually assigned and maintained by a central authority to prevent conflicts:

• teams propose one or more preferred codes during registration;
• the governing body checks for conflicts with existing codes;
• once approved, the code is entered into the official registry;
• when a team changes its commercial name, the original code may be kept to preserve historical continuity in statistics.

Event organizers frequently reproduce the official list of valid team codes in their technical guides so that delegations, commentators and media can rely on the same identifiers.

Relation to other identifiers

UCI‑style team codes are distinct from several other commonly used codes:

• National Olympic Committee (NOC) codes such as the three‑letter codes used at the Olympic Games, which represent delegations or countries rather than professional teams;
• internal numerical IDs used inside a specific registration or timing system, which are not intended for public display;
• marketing abbreviations or sponsor‑driven short names that may change more frequently than technical identifiers.

In detailed technical documents, it is common to list the full team name, nationality, country code and team code together so that readers can cross‑reference them.

Example

The following is a purely illustrative example showing how a team code might be used:

• Full team name: Example Cycling Team
• Country: France
• Country code: FRA
• Team code: EXC

In an official result sheet, only "EXC" might appear in the team column, while a separate legend or team list maps EXC to the full team name.

See also

• Sports league
• International sports federation
• Sports statistics

→ Expectation: no conflict with the data-container template Cycling data MUL (namespace isolation)

Regression test script (pseudo)

• Word list: Hello/Bonjour/Hola/Hallo/Café/naïve/日本語/مرحبا
• Batch rendering: inject sequentially; compare DOM fragment class/lang attributes
• Assertions:
  • Output contains lang="mul" attribute
  • No error when lang parameter omitted
  • Special characters rendered via entities or UTF-8 correctly

Compatibility and fallback

• If does not exist: fallback to plain text output
• If site does not support lang="mul": fallback to a without lang attribute

Maintenance recommendations

• Document: purpose, parameters (text, lang), examples, common issues
• Avoid name collisions with other language-label templates
• Keep this “StemmingSingleWords style” testcase set in template sandbox and testcases pages for CI

---

References:

• Template:-mul- (Wiktionary-om) alignment of multilingual label usage
• Template:Mul (Meta) as a comparator
• For-multi (hatnote) for interaction regression

Template:Categoritza

_{Template documentation}

The template Categoritza is a utility template on test2.wikipedia used to assist editors in the organization and maintenance of category pages. It provides a standardised way to display category-related information, helper links, and maintenance notes for pages in the category namespace.

Categories are one of the core mechanisms to structure content on a wiki and to help readers navigate between related pages. On test wikis such as test2.wikipedia, templates like Categoritza are often used for experimenting with category layouts and tools before deploying ideas to production projects.

File:Category management icon.svg

Example icon often used on category-related templates

Purpose

The main purposes of Template:Categoritza include:

• Providing a consistent header or information box on category pages.
• Documenting the scope and inclusion criteria of a category.
• Linking to relevant help pages, guidelines, and related categories.
• Highlighting maintenance information (e.g. categories that are under discussion, being cleaned up, or used for tracking).
• Offering tools for patrollers and bots to process categories in a predictable format.

In practice, such templates help standardise how categories look and behave, making it easier for both new and experienced editors to understand what a category is meant for.

Usage

Basic usage

The simplest way to use the template is to place it at the very top of a category page:

{{Categoritza
| description = Pages related to example topics used for testing.
| parent      = [[Category:Example parent category]]
| tracking    = [[Category:Tracking categories]]
}}

Typical parameters include:

• description – short description of what the category contains.
• parent – one or more parent categories, usually displayed as links.
• tracking – tracking or maintenance categories that the current category belongs to.
• notes – optional free-form notes or local instructions.

When the template is transcluded on a page in the [[:Category:]] namespace, it usually renders a small information box or a formatted block of text at the top of the category, above the list of pages.

Example

An example usage on a testing category could look like:

{{Categoritza
| description = This is a test category used for experimenting with category-related templates on test2.wikipedia.
| parent      = [[Category:Test categories]]
| tracking    = [[Category:Maintenance categories]]
| notes       = Do not rely on the content of this category for serious work; it may be changed or emptied at any time.
}}

This might result in a visible box summarising what the category is for, how it should be used, and which broader category tree it belongs to.

Parameters

Required parameters

description

A concise explanation of the scope of the category. This helps both readers and editors decide whether a particular page belongs in the category.

Optional parameters

parent

One or more parent categories. These are generally shown as links and may be separated by commas or line breaks.

tracking

One or more hidden or visible tracking categories, typically used for maintenance and automated reports.

notes

Any supplementary notes, local warnings, or instructions. For example, notes can explain that a category is only for articles that meet certain criteria.

style

Optional parameter to adjust the visual style (for example, background colour or icon choice) on test wikis where CSS experimentation is common.

Technical details

Internally, Template:Categoritza may make use of:

• Parser functions like and to check whether parameters are set.
• Category-specific magic words such as when a category is meant to be hidden from readers by default.
• Subtemplates for icons, colour schemes, and documentation.

Many test templates are also designed to be robust against being transcluded on non-category pages, either by producing a warning or by rendering a neutral message.

Relation to other templates

On large projects, there are numerous templates associated with categories, such as:

• Navigation templates for browsing within a topic.
• Maintenance templates that mark categories for deletion, renaming, or discussion.
• Project-specific banners that indicate a category belongs to a particular WikiProject.

Categoritza can coexist with such templates and may be placed alongside them, usually at the top of the category page.

Maths and formatting tests

Because test wikis often serve as sandboxes, Template:Categoritza (and its documentation) may also include examples of formatting elements:

• Simple formulas such as $\pi$ to demonstrate how mathematical content appears in category descriptions.
• Preformatted blocks:

Preformatted example text

• Test images for thumbs and alignment:

Example map used for testing

Alternative test image

These examples help editors see how different visual components interact on category pages, especially when combined with long lists of pages.

References

1. aranya de cap negre

• {e|mul|Trachinus Cirrosus}

Referències

Line1

Change A to link to the related project:

• Viquiespècies – the sister project dedicated to species information.

Example usage:

{{Viquiespècies|''Panthera leo''}}

This would generate a link to the corresponding page on Viquiespècies for the given taxon.

• FRTV IE0`2G FMTDG IR KGIIOU RDGHFLKJGOYFJGIPO0G8BVKFJGMJKJLFIUHGDFOUMGFOHDOUHGNJKNH

DHGFDFOIUFY8GERJBRGUIGFHGIYFNKJUHFJKHIYGFJSFD8JD F YJCUCBDKJUFHGDFOI80JDSHFUOHDSUTJUFDSUFD

Template:Categoritza is a maintenance and navigation template on test2.wikipedia designed to help editors quickly add one or more categories to a page in a consistent way.

This template is usually used on talk pages, user pages, documentation subpages, and other non-mainspace pages where lightweight categorization is helpful. It can also serve as a wrapper around more complex categorization systems.

Usage

Place the template at the bottom of the page you want to categorize:

{{Categoritza|Category name 1|Category name 2|...}}

Example:

{{Categoritza|Example maintenance templates|Sandbox pages}}

This will add the page to:

• [[Category:Example maintenance templates]]
• [[Category:Sandbox pages]]

Parameters

1, 2, 3, ...

Unnamed positional parameters. Each parameter is treated as the name of a category.

nocat

Optional flag. When set to yes, the template will not categorize the page but will instead display the category names as plain text. This is often useful in documentation and examples.

Example:

{{Categoritza|Example maintenance templates|nocat=yes}}

Examples

Basic example

{{Categoritza|Template documentation|Test templates}}

Result:

• The page is added to
• The page is added to

With many categories

{{Categoritza | Experimental templates | Internal documentation | Test2-only templates }}

Result:

In documentation pages

On template documentation subpages (/doc pages), you can combine this template with <includeonly>...</includeonly> so that categorization only applies to the template itself and not to pages that transclude the documentation.

Example on Template:Example/doc:

<includeonly>{{Categoritza|Example templates|Template examples}}</includeonly>

Technical details

Internally, this template takes each positional parameter and wraps it in a standard category link of the form:

[[Category:{{{1}}}]]

It then repeats this for all additional parameters (2, 3, 4, etc.). Parameters that are empty or contain only whitespace are ignored.

The nocat parameter is checked before any categories are emitted. If nocat=yes, the template outputs the list of categories in a human-readable form for demonstration and testing purposes.

See also

• Template:Category handler – a more advanced system for conditional categorization
• Help:Category – help page about categories on test2.wikipedia
• Special:Categories – list of all categories
• Wikipedia:Maintenance – overview of maintenance-related tools and templates