Template talk:TemplateBox/Archive 2

Categorization

Hi! New automatic categories have been made, but we already have similar ones:

• Templates using LangSwitch for internationalisation – Internationalization templates using LangSwitch
• Templates using MediaWiki messages from Translatewiki for internationalisation‎ (or local) – Internationalization templates using MediaWiki messages
• Templates using Autotranslate for internationalisation – Autotranslated templates

Can they be merged? --tacsipacsi (talk) 18:24, 17 March 2014 (UTC)

We've implemented that this way because the categorization will be according to how the approach is documented, allowing to use, for example category intersections to spot errors in documentation. Category:Commons templates by documented internationalization approach is a maintenance category. -- Rillke^(q?) 19:19, 17 March 2014 (UTC)

Suggestion for copy code

How about display automatically the source code (en) to copy (as it is often used before Autotranslate) for the new language subpage (for example Template:Apache/en)!?

{{Apache/layout
|text=Copyright © {{#if:{{{2|}}}|{{{2}}}|{{#expr:{{CURRENTYEAR}}}}}} {{#if:{{{1|}}}|{{{1}}}|The author}}<br />

Licensed under the '''[[w:Apache License|Apache License]], Version 2.0''' (the "License"); you may not use this file except in compliance with the License. 

You may obtain a copy of the License at https://www.apache.org/licenses/LICENSE-2.0. 

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an '''"as is" basis, without warranties or conditions of any kind''', either express or implied. 

See the License for the specific language governing permissions and limitations under the License.
|lang=en
}}<noinclude>
{{translated tag|license}}
</noinclude>

And then mention that

- |lang=en
+ |lang={{subst:SUBPAGENAME}}

is to replace. -- Perhelion 21:41, 26 May 2014 (UTC)

Oh I see now the source code is automatically in the new subpage (so it's almost not needed). I've never done this. :-P But is it not possible to replace the static "en" to {{subst:SUBPAGENAME}}? -- Perhelion 21:54, 26 May 2014 (UTC)

If you tell me how, I'll do it. Apart from that, please create new templates using the translate extension for translation. -- Rillke^(q?) 22:30, 26 May 2014 (UTC)

Explicit translatewiki.net link

{{Editprotected}} Please replace:

These can be translated at [[:translatewiki:MediaWiki:{{#if:{{{i18n-mediawiki-msg|}}}|{{{i18n-mediawiki-msg|}}}|Wm-license-{{lc:{{BASEPAGENAME}}}}-text}}|translatewiki.net]]

with:

These can be [[|translated at translatewiki.net]]

--Nemo 18:13, 3 July 2014 (UTC)

@Nemo bis: This will make the i18n-mediawiki-msg parameter superfluous. Is it intentionally dropped? -- Rillke^(q?) 18:29, 3 July 2014 (UTC)

Yes and no, I'm not aware of substantial use of messages by templates on Commons other than those in the WikimediaMessages extension and linking MediaWiki namespace pages doesn't work very well anyway. However if you're not sure I'm too lazy to check hundreds templates and we can keep it, like

These can be [[<tvar|twn-wm>translatewiki:{{#if:{{{i18n-mediawiki-msg|}}}|MediaWiki:{{{i18n-mediawiki-msg|}}}|Special:Translate/ext-wikimediamessages}}|translated at translatewiki.net]]

--Nemo 17:27, 5 July 2014 (UTC)

So'll be it. Thank you. -- Rillke^(q?) 19:19, 5 July 2014 (UTC)

Category:Pages using duplicate arguments in template calls

Rillke There is a problem with {{TemplateBox}} using "Example" variable as it shows up in Category:Pages using duplicate arguments in template calls for example {{TemplateBox|name=CopyvioOTRS|example=0000}} is enough to be added to that category. Is there a way to fix it? --Jarekt (talk) 13:01, 13 November 2014 (UTC)

Needs debugging. First we have to find out which template is called with duplicate arguments. -- Rillke^(q?) 19:16, 13 November 2014 (UTC)

FWIW, Tdoc on Meta (a vintage 2010 {{TemplateBox}} simplified by Patrick) also puts lots of templates in this new tracking category. –Be..anyone (talk) 18:40, 26 December 2014 (UTC)

example2

Hi, a second example won't show up whenever I try to use the example2 parameter here. What am I doing wrong? // WikiPhoenix ^[Talk] 00:33, 9 December 2014 (UTC)

Artefacts in template data

The template data shown for "status" contains three unescaped  . Similar "translation method" contains three unescaped {{[[link]]}} constructs, apparently some escaped {{tl|autotranslate}} links. mw:Help:TemplateData mumbles something about "no wiki markup in JSON, svp", maybe these are copy and paste issues. There are more (similar) issues in the template data. –Be..anyone (talk) 18:25, 26 December 2014 (UTC)

i18n-method = module

Some of the internationalization pages are slowly moving from {{LangSwitch}} blocks in templates to tables in Lua, see [1]. We should probably have an i18n-method option that matches that. --Jarekt (talk) 20:50, 27 January 2015 (UTC)

 Support, needed. --Zolo (talk) 08:16, 29 January 2015 (UTC)

Would also require a specifier where the module can be found. -- Rillke^(q?) 11:26, 19 March 2015 (UTC)

@Rillke: , Yes actually both LangSwitch blocks and lua based equivalents could use such parameter. --Jarekt (talk) 18:36, 23 April 2015 (UTC)

"Or use the shorthand"

It is what shows up in the shorthand spot. Could this be changed to:

• Shorthand and redirects

People are deleting some info about redirects because some redirects are not always shorter names (shorthand). People create all kinds of redirects, both longer and shorter than the original template name. Anything that helps people remember and use the templates is a good thing. We all remember different things, different spellings (British, American, etc.), different phrasing, etc.. --Timeshifter (talk) 00:22, 5 February 2015 (UTC)

 Oppose based on my comment on your talk page. I have no problem at all with, say, {{Igen}} as desirable shorthand for {{Image generation}}, 4 vs. 16 characters. Not the same as {{CatCat}}, where a "see also" redirects is good enough to cover its "longhand" redirects. –Be..anyone (talk) 05:50, 5 February 2015 (UTC)

There is nothing to oppose. As I said, you obviously are clueless as to how many people actually use redirects concerning templates. They, like shorthand, are used for convenience and memory. The number of characters is not necessarily what makes a redirect convenient. It is the fact that one easily remembers certain redirects. This is the traditional reason many people use these template redirects on the Commons. I have created many template redirects, and many template shorthands. "Shorthand" in TemplateBox is just a one-word entry in the form. With one-word entries one must choose one word. Traditionally we have listed both redirects and shorthand in the documentation. TemplateBox is a more recent creation. Thus we need to align it with tradition by using my suggestion or something similar. Separating shorthand and longhand redirects in different parts of the documentation is just stupid. Spelling and punctuation variations are common reasons for template redirects. --Timeshifter (talk) 02:01, 6 February 2015 (UTC)

If you almost always want a "redirects" link (WhatLinksHere hiding links and transclusions) {{TemplateBox}} could almost always generate it and put it into its "see also" section or similar. The shorthand position is at the top of the documentation, it's for advertizing, same idea as {{Shortcut2}}. But learning that {{MetaCat}} has an alias without camel-case, plus a link to check that this in fact the only redirect to MetaCat is a distraction from what's relevant, the syntax and parameters of {{MetaCat}}.

For {{CatCat}} it is similar, but it actually has some (longer) aliases, which might be interesting for users who don't want to click WhatLinksHere + hide links + hide transclusions. The construction of one link for this business is fun, but at the end of the day, how often do you plan to check all redirects to {{CatCat}}, and why must that be at the top of the documentation? –Be..anyone (talk) 02:30, 6 February 2015 (UTC)

{{Shortcut2}} is not the same as the shorthand and redirects for templates. Most {{Shortcut2}} shortcuts I see consist of the first letter of each word in the title of a page. Shorthand and redirects for templates consist of many variations of the template name. Both short and long. Separating them to different parts of the documentation page serves no purpose except to confuse users of templates. Users may create more redirects, not knowing what already exists. Some users may be less likely to use the templates. Because they can't remember the exact original name of the template. I think the "redirects" link (WhatLinksHere hiding links and transclusions) should be on all template pages. Automatically created by TemplateBox. Sometimes the "redirects" link (WhatLinksHere hiding links and transclusions) is added to a template page, but the additional redirects disappear because some clueless admin deleted the redirects, and then it seems like it serves no purpose. Some people go around changing the name of redirects on the pages where they are being used. A big mistake. Then it seems like the redirect is not being used. So it gets deleted. The person who created the redirect then stops contributing to the Commons, at least as concerns that template, because people are ruining their work, and they can no longer remember the name of the template. Many people don't know how to look for redirects. The point is to make it easy for users to use templates. The "redirects" link (WhatLinksHere hiding links and transclusions) makes using templates easier. --Timeshifter (talk) 08:38, 7 February 2015 (UTC)

FWIW: {{TemplateBox|shorthand={{redirects|Metacat}}}} should works as documented for {{Redirects}}, and all bare {{TemplateBox|shorthand={{tl|Metacat}}}} constructs should be updated by a bot. Only the remaining cases should be kept as is. This will have your desired backlink effect on explicitly enumerated aliases, i.e., the alias gets a link from the /doc subpage.

I still doubt that listing {{ucfirst:{{lc:CamelCase}}}} is necessary, only a maniac would delete Camelcase. Example, there are three {{Cc-by-sa-3.0-igo}} spelling variations (invented by the ESA), all tagged as redirects to a license template. Counter-example, I created {{EmptyCatGood}} as redirect to {{Empty category}}, because I like the funny mediawikiwiki name, but I'd have no objection to an import of the real thing. After all redirects can be expanded into separate pages in all namespaces. –Be..anyone (talk) 20:49, 9 February 2015 (UTC)

Redirects don't have anything to do with the template itself, and listing them doesn't provide users with any useful additional information. Therefore, they shouldn't be added to /doc pages, and this edit should be reverted.    FDMS  4    20:18, 16 February 2015 (UTC)

The docs have long had redirects. The template is a more recent invention. And shorthand redirects are still redirects. Shorter redirects are not necessarily easier to remember than longer redirects. And that is the point of all of these redirects, easy memory. --Timeshifter (talk) 00:13, 18 February 2015 (UTC)

I'm not going to use the {{Esoteric}} {{TemplateBox}} in any past, present, or future shape anywhere, the "template data manager" i18n now passes "good enough" and is available on all WikiMedia projects. This also solves the "seealso=" conflict, without the {{TemplateBox}} abomination {{Redirects}} works as designed. –Be..anyone (talk) 04:06, 18 February 2015 (UTC)

Empty parameters

Because the > 40 SVG created with ... templates have almost the same decription, it seems reasonable to have one and not > 40 documentations for them. This is done with the unified template documentation {{SVG created with/doc}}, kind of meta docu. So far, so good.

Unfortunateley they are not absolutely identical. Most are for only SVG, some create also PNG. About a dozen of them can show the code. And a few ones have the parameter IMPORTANT. It would be nice if these special cases can be handled with conditional decriptions.

At the moment I cannot see a possibility for a construct like |4={{#if:...}} because the template box module will in this case show the empty parameter 4.

{{TemplateBox
|1=1
|1d=description of 1{{exp|st}} parameter 
|1stat=optional-
|2=2
|2d=description of 2{{exp|nd}} parameter 
|2stat=optional-

|3=
|3d=
|3stat=

|4={{#if:{{{4|}}}|show parameter}}
|4d={{#if:{{{4|}}}|describe parameter}}
|4def={{#if:{{{4|}}}|describe default}}
|4stat={{#if:{{{4|}}}|}optional-}}

}}

The empty parameters 3 and 4 show up in "Usage" and in the table. {{edit request|technical=1}} The display of parameters without content in the parameter name should be suppressed. sarang♥사랑 13:45, 8 March 2015 (UTC)

Your example, or rather, {{TemplateBox}}, clobbered the section edit links on this talk page, and it took me some hours to fix this. Certainly not your fault, it might be a missing magic word __FORCEEDITSECTION__ to overrule a generated __NOEDITSECTION__. Your box also makes sense (for me) as <pre>-formatted code instead of an embedded <div>-example, therefore I picked s/div/pre/ to enable the edit links again.

Otherwise  Oppose, there are too many hopeless {{TemplateBox}} "features" for piecemeal patches. Your best option after not using {{TemplateBox}} at all might be useTemplateData=only, or simply use only the template data manager and not its {{TemplateBox}} predecessor. The template data manager is what everybody outside of commons + Meta will know, and meanwhile it supports i18n. If you don't want to document parameters 3+4 just klick on "remove" in the suggested parameters, or remove what you don't like in the generated JSON. –Be..anyone (talk) 03:38, 9 March 2015 (UTC)

 Not done — I don't think this a maintainable change to TemplateBox. —RP88 (talk) 06:16, 7 November 2015 (UTC)

add 1sort parameter

one of the most painful operations I seem to be performing a lot is adding new parameters to templates. The working with templates goes fast but adding new parameters to the documentation that already have 30 of them is quite painful, since it often involves need to reorder and rename parameters describing template parameters (1=, 1d=, 1stats, etc.). In the old days there were only 4 so it was not so bad but now with the translations we can have 10+ parameters per each of 30 template parameters, so there is potential to a lot of renames and a lot of manual mistakes. I would like to propose 1sort, 2sort, ..., etc. which by default would be 1, 2, ..., etc. but 1sort=2 and 2sort=1, would swap the displayed order of the fields. --Jarekt (talk) 02:33, 16 March 2015 (UTC)

I'd prefer having a script that does re-ordering over adding another confusing parameter. -- Rillke^(q?) 11:28, 19 March 2015 (UTC)

Rillke and Jarekt, I've played this game today on Template:Artwork/doc with some regex fiddling. It is not fun, neither would it be with a script. Also, using a script or whatever, changing all the numbers leads to the same page history pollution.

On the other hand, 1sort, 2sort, ..., etc. is indeed again 1 parameter per parameter more. What do you think about adding just one parameter for the whole box, |paramOrder= as used by mw:Extension:TemplateData#TemplateData object? Cheers, (pings appreciated) --Marsupium (talk) 14:27, 22 May 2021 (UTC)

I would be fine with |paramOrder=. I just do not want to be renaming parameters anymore. --Jarekt (talk) 01:40, 23 May 2021 (UTC)

example (4) - bug

Is it possible to remove please the default pipe "|" symbole from example value? In many examples there is no considerable display possible (see example). This could also be the reason for the bot doing by Leyo in fixing hundreds of templates (for example in Category:Pages using Information template with incorrect parameter) because the examples are wrong...

The description says “Example use (works with a single unnamed parameter only). I guess there is no possible without a bot to fix all existing usage of this bad awkwardness. ↔ User: Perhelion (Commons: = crap?)  10:41, 19 March 2015 (UTC)

Please provide a diff or the desired new version unless it's too complicated for you. -- Rillke^(q?) 11:24, 19 March 2015 (UTC)

Is it possible to have a word (null, none, empty, ...) to indicate that the model has no parameter, and delete the | useless? thank you --Camulogene77 (talk) 13:18, 15 October 2017 (UTC)

Any of them is a valid parameter. It’s possible that omitting the |example= and using |example-value= would be a resolution, but why do we need it? If there are no parameters, just omitting the <includeonly> tags makes the template content appear above the documentation. --Tacsipacsi (talk) 13:57, 15 October 2017 (UTC)

The problem is in the documentation, the "example-value" field makes it possible to force the result of the example but if the "example" field is empty, the model does not show example. how to display an example without parameters in the "example" field. For example: {{Collective}}. --Camulogene77 (talk) 18:20, 15 October 2017 (UTC)

I know that it doesn’t work currently, I meant that it might be a solution to be implemented. However, as I said, I don’t see any point in just repeating what’s already visible on the top of the page. (Please don’t mark your comments as minor edits. They aren’t, and people might not notice them if you mark them as such.) --Tacsipacsi (talk) 11:35, 16 October 2017 (UTC)

msg-shorthand-params-possible translation

Please add msg-shorthand-params-possible translation.

|msg-shorthand-params-possible= <translate>
… parameters as described … </translate>

{{Edit request}} Thanks in advance. --FRacco (talk) 12:05, 4 April 2015 (UTC)

 Done Awesome! Thank you! Rillke^(q?) 12:45, 4 April 2015 (UTC)

Options for TemplateBox parameter "type"?

I am trying to create my first template, and as one might expect, am getting somewhat lost in meta-code-stuff and the parameter of the parameter level of complexity of it all. I am creating the /doc page for my template, and am stuck on what happens when I specify a particular "type" for one of my parameters under, for example, the 1type parameter (...which is confusing to even say never mind understand, but I do get it, so far, I think). I understand that I need to choose between number, string, string/wiki-user-name, string/wiki-page-name, and string/line (or ignore it and allow it to be the default value of unknown), but though I can guess what selecting certain values here will do— if I choose the value number for my 1type parameter, this will require the user of the template to use a number value for this parameter when actually using the template (will it reject other types of entries? With a warning of some kind?) and that using string will allow a user to enter text for that parameter— what are the effects of string/wiki-user-name, etc.? Do these enforce the use of the current template's user's name in the parameter? Do they only enforce the formatting of such a name? Or something else? And what is string/line supposed to do? Is there a place where I can get some explanatory documentation about these values? I've been looking up and down and just found nuthin' so far. Thanks! KDS4444 (talk) 10:44, 16 August 2015 (UTC)

I've changed the doc, is this more helpful? ↔ User: Perhelion (Commons: = crap?)  15:35, 17 August 2015 (UTC)

Yes, thank you! KDS4444 (talk) 07:48, 18 August 2015 (UTC)

New translation method needed:Wikidata

Parameter i18n-method should also take Wikidata parameter to indicate pages translated by using Wikidata, the way {{Authority control}} is and there are few other templates also using it. --Jarekt (talk) 18:22, 30 May 2016 (UTC)

I second this request! --Reinhard Müller (talk) 11:05, 11 November 2019 (UTC)

Also Module:i18n subpages are missing. This may even be mixed with Wikidata, like Module:i18n/institution is. —Tacsipacsi (talk) 09:29, 19 May 2018 (UTC)

Another bug

The example {{Image generation/doc}} describes 27 parameters (number 7, 10 and 13 are left empty for future use). It concludes a lot of more descriptions, they are not so easy to insert due to restrictions and missing options in the TemplateBox.
After displaying the descriptions for parameters 1 to 16 the following descriptions are not in sequence, after 16 comes 27, then 17 and 18, then 24 and so on. Is there a possibility to correct the sequence? sarang♥사랑 08:45, 28 September 2016 (UTC)

Example

The example seems misleading.

{{En|1=Abcdefghijklmnopqrstuwxyz}}

displays:

English: Abcdefghijklmnopqrstuwxyz

not:

English: Abcdefghijklmnopqrstuwxyz

I think this is in Template:TemplateBox/layout. Perhaps it should look more like this:

{{En|1=Abcdefghijklmnopqrstuwxyz}}

displays:

English: Abcdefghijklmnopqrstuwxyz

Hyacinth (talk) 19:12, 7 June 2017 (UTC)

Fail on i18n-subpage

If this is empty, it gives a fail link to subpage: Template:/ As this value is default inserted on a new doc creation, this is a heavy undocumented error cause. -- User: Perhelion 14:14, 18 October 2017 (UTC)

 Done Its seems there was also an empty name parameter. -- User: Perhelion 19:24, 26 October 2017 (UTC)

What are different "type"s of templates?

Does parameter |type= have any semantic meaning? I'm not sure that it has any effect. Documentation only mentions types "infobox, formatting, licence tag". —⁠andrybak (talk) 07:58, 3 September 2018 (UTC)

@Andrybak: From looking at all the code, only |type=infobox has any effect in that it changes the default of |print=line to |print=multi, but other values don’t actually do anything, and aren’t even standardised at all, thus making it hard to even know which values are used in the wild.

I’ve began collecting all the values that I’ve encountered to the “suggestedvalues” TemplateData field for the parameter with the hope that it eventually ends up documented like {{Convert to SVG}}’s parameter 1 — ExE Boss (talk) 07:00, 28 June 2021 (UTC)

References

How to make code to copy vertical

How do I set up the easy-to-copy code sample generated by {{TemplateBox}} to be vertical? That is, I want:

{{Example
  | parameter1 = 
  | parameter2 = 
  | parameter3 = 
}}

instead of {{Example| parameter1 = | parameter2 = | parameter3 = }}. —⁠andrybak (talk) 19:57, 9 September 2018 (UTC)

You can use |print=multi if you want exactly one space before the equal signs, and |print=infobox or |type=infobox if you want the equal signs to be below each other. —Tacsipacsi (talk) 22:05, 9 September 2018 (UTC)

Thank you, Tacsipacsi. —⁠andrybak (talk) 05:10, 10 September 2018 (UTC)

No support for suggested parameters

According to the documentation, this template doesn't support "suggested" as a parameter status. That should be added. Kaldari (talk) 15:15, 20 May 2019 (UTC)

@Kaldari: the value "suggested" is possible and can be used - just the documentation does not know yet. -- sarang♥사랑 13:36, 2 August 2019 (UTC)

Another "stat" option wanted

I would appreciate an option which does not display anything in the Status field, but works like #stat=optional-. How about #stat=none ?
It is possible e.g. to group sets of parameters with an empty line, but currently the Status field of that line cannot be left empty. -- sarang♥사랑 13:36, 2 August 2019 (UTC)

usage-notes not transateable

Would it be possible to also allow the parameter usage-notes in different languages? Thanks --Reinhard Müller (talk) 11:06, 11 November 2019 (UTC)

Of course it’s translatable—you can use {{LangSwitch}}, {{Mld}} etc. Other parameters use the language code suffixes in parameter names because need to (they are exported in TemplateData, which requires the module to have access to all translations), but that’s not the case for usage notes. Other free text parameters not used in TemplateData (e.g. i18n-desc) don’t have this suffixed parameter translation either. Using dedicated templates like {{LangSwitch}} is also more flexible than what we use for the parameter descriptions, for example they let us keep parts of the parameter value untranslated without having to repeat it in every translation. —Tacsipacsi (talk) 19:41, 11 November 2019 (UTC)

Param 'example2' not passed to /layout

{{Edit request}}

According to the template documentation, a parameter called example2 should be supported. There is code in {{TemplateBox/layout}} that makes use of this parameter; however, it looks like someone forgot to have {{TemplateBox/i18n}} pass the example2 parameter along to the layout template. Line 4 of {{TemplateBox/i18n}} should be changed from this...

|name={{{name|}}}|desc={{{desc|}}}|namespace={{{namespace|}}}|usergroup={{{usergroup|}}}|placement={{{placement|}}}|usage-notes={{{usage-notes|}}}|type={{{type|}}}|example={{{example|}}}|example-value={{{example-value|}}}|i18n-method={{{i18n-method|}}}|i18n-subpage={{{i18n-subpage|}}}|i18n-desc={{{i18n-desc|}}}|seealso={{{seealso|}}}|setscats={{{setscats|}}}|lines={{{lines|}}}|shorthand={{{shorthand|}}}|relieson={{{relieson|}}}|docsub-override={{{docsub-override|}}}|docsub-page={{{docsub-page|}}}|mustbesubst={{{mustbesubst|}}}|templateData={{{templateData|}}}|JSONFM={{{JSONFM|}}}|useTemplateData={{{useTemplateData|}}}|paramTable={{{paramTable|}}}|templateDataInfo={{{templateDataInfo|}}}|usageSample={{{usageSample|}}}|argCount={{{argCount|}}}

...to this...

|name={{{name|}}}|desc={{{desc|}}}|namespace={{{namespace|}}}|usergroup={{{usergroup|}}}|placement={{{placement|}}}|usage-notes={{{usage-notes|}}}|type={{{type|}}}|example={{{example|}}}|example-value={{{example-value|}}}|example2={{{example2|}}}|i18n-method={{{i18n-method|}}}|i18n-subpage={{{i18n-subpage|}}}|i18n-desc={{{i18n-desc|}}}|seealso={{{seealso|}}}|setscats={{{setscats|}}}|lines={{{lines|}}}|shorthand={{{shorthand|}}}|relieson={{{relieson|}}}|docsub-override={{{docsub-override|}}}|docsub-page={{{docsub-page|}}}|mustbesubst={{{mustbesubst|}}}|templateData={{{templateData|}}}|JSONFM={{{JSONFM|}}}|useTemplateData={{{useTemplateData|}}}|paramTable={{{paramTable|}}}|templateDataInfo={{{templateDataInfo|}}}|usageSample={{{usageSample|}}}|argCount={{{argCount|}}}

Thanks, IagoQnsi (talk) 20:26, 7 July 2020 (UTC)

 Done Regards, ZI Jony ^(Talk) 17:40, 27 September 2020 (UTC)

@ZI Jony: It’s done now. Nothing happens until a translation administrator (like me) marks the page for translation; Template:TemplateBox/i18n is not used directly anywhere. (In light of this, I’m not really convinced whether it really deserves full protection—no one (except for a translation administrator) can really make damage on their own.) —Tacsipacsi (talk) 00:55, 28 September 2020 (UTC)

Another "stat" option wanted

My question one year ago didn't get any answer yet, so I repeat it:
I would appreciate an option which does not display anything in the Status field but works like #stat=optional-. How about #stat=none – or #stat=optional-- ?
Reason: some templates use many parameters, e.g. {{File generation description}} contains about 70, therefore some grouping seems helpful.
Formatting items like e.g. thicker border lines for the table cells are not offered, but it is possible e.g. to group sets of parameters with an empty line, by abusing the description for a parameter, but currently the Status field of that line cannot be left empty and will always be displayed.
-- sarang♥사랑 13:36, 2 August 2019 (UTC) WWWWWW renewed: -- sarang♥사랑 06:05, 5 August 2020 (UTC)