Template talk:G

Item separation

Normally templates get their parameters separated with pipes "|"; but for galleries the file names
are traditionally separated by linefeeds. This template accepts both separation methods,
everybody may use the own preferred method of arranging the input items.
Each existing <gallery>...</gallery> coding can be replaced by {{G|...}} without necessity to change anything else.

Technical view

There can be an unlimited number of unnamed parameters p₁ to p_z;
each one eof these unnamed parameter p_n can have the structure that it
consists of m linefeed-separated items: (p_n= is represented by the n^th pipe)
G ┃ item_n1

item_n2

⠄ ⠄ ⠄

item_nm

Optical view

This structure can as well be seen in another view, that each linefeed-separated line consists of 1 to n pipe-separated items:
G ┃ item_a1 | item_a2 | ⠄ ⠄ ⠄ | item_an

item_b1 | item_b2 | item_b3

⠄ ⠄ ⠄

item_x1 | item_x2 | ⠄ ⠄ ⠄ ⠄ ⠄ ⠄ | item_xm

Parsing

However the input parameters are organized, with linefeeds or pipes or a mixture of both,
for the program (template, module) it does not matter - finally will be a series of all items:
item_a1 – item_a2 – ⠄ ⠄ – item_an - item_b1 – item_b2 – item_b3 - ⠄ ⠄ - item_x1 – item_x2 – ⠄ ⠄ – item_xm
As the program does, first all pipe-separated input is convered to strings; when there are linefeed-separations, then these strings are divided into the items.

In the special case of format=2 the obvious arrangement may be for the best overview how the names are assigned to the files:
G ┃

file₁ | name₁

file₂ | name₂ WWWWWWWWWWWWWWWWWWWWWWWW for this arrangement, format=2 will be defaulted

⠄ ⠄ ⠄

file_n | name_n

The program builds first the strings: file₁, name₁ file₂, name₂ ..., ... file_n, name_n.
The second separation breaks the strings into items at the linefeeds: file₁, name₁, file₂, name₂, ..., ..., file_n, name_n.
Finally all the items will be grouped to tupels: file₁ - name₁, file₂ - name₂, ... - ..., file_n - name_n,
because format=2 is valid – whether specified explicitely, or as the default.

When for a file_n a name_n should be missing it can be shown with an empty name_n (a pipe followed by nothing);
this pipe is not necessary because it is checked whether some text, or the next file name follows a file name:
missing caption text is substituted by the file name (as-it-is, only understrokes are replaced by spaces).
Because of that, caption text must not look like a valid file name, i.e. end with dot + valid extension.
Repeating the file name itself does not disturb but is normally useless (except e.g. changes into lower/upper case).

When a valid file name should be used as a caption, different possibilities exist to avoid its treatment as the next file name, e.g.:
   ■ enclosing it into {{F|...}} brackets, either to use it as a link, or with the {{F}} 'nolink' option n
   ■ enclosing it into <nowiki> brackets; or adding a single <nowiki/> tag

-- ♥사랑16:27, 14 October 2019 (UTC)

Template inappropriately wraps gallery in small tags

When called like this:

{{G|Glaskugel_--_2022_--_9832.jpg|t=small}}

this template wraps the entire gallery in small tags, which produces invalid HTML. ‎<small>...‎</small> can wrap only in-line content, and galleries are block content. Please adjust I have adjusted this template so that it does not accept in-line formatting as a wrapper for gallery tags. Jonesey95 (talk) 06:19, 27 October 2022 (UTC)