Module:Road data/strings/doc: Difference between revisions

Revision as of 03:47, 20 December 2021

Revision as of 04:09, 20 December 2021

Line 38:

*<code>banner</code> stores the name of the special route plate, such as <code>[[:File:Business plate.svg|Business plate.svg]]</code>. Can be omitted when unused.

*<code>width</code> stores a code representing the width of the shield. It is most often helpful when used with <code>banner</code>. Can be omitted entirely when unused.; Commoncommon values are <code>square</code> and <code>expand</code>.

*<code>section</code> stores the specific section number for those routes that are defined by law.

*<code>width</code> stores a code representing the width of the shield. It is most often helpful when used with <code>banner</code>. Can be omitted entirely when unused. Common values are <code>square</code> and <code>expand</code>.

*<code>translation</code> specifies the native language name of the route displayed by an infobox

Once a type is defined, it can be referred to later in the code. As seen here, it is common to define all parameters for main types like <code>US</code> and then to use aliases for subtypes such as <code>US-Alt</code>.

*<code>lang</code> is the [[List of ISO 639-2 codes|ISO 639-2]] code of the native language; this code is used by {{tl|Lang}} and {{tl|Lang-xx}}.

<syntaxhighlight lang="lua">

PER.RN = {

shield = "PE-%route% route sign.svg",

name = "National Route %route%",

link = "Peru Highway %route%",

abbr = "PE-%route%",

translation = "Ruta nacional %route%",

lang = "es-pe"

}

</syntaxhighlight>

Once a type is defined, it can be referred toreferenced later in the code. As seen here, it is common to define all parameters for main types like <code>US</code> and then to use aliases for subtypes such as <code>US-Alt</code>.

<syntaxhighlight lang="lua">