THE OWL
discussion page.To add a new message, click on "Add Topic/Reply" button below, and set the "Subject".
To add a Reply, do the same as above, but leave the "Subject" blank.
Should we use the original engine branch or current engine branch on software page template?
{{Src13}}
and others don't give exact information about what exactly the game is based on. If you specify {{Src13}}
for the conditional Half-Life 2, it turns out that the game is based on both versions at once - Singleplayer and Multiplayer.
I don't see any problems in using {{Src13}}
, {{hl2}}
and others if it will give enough information to understand what a person should use to create a similar game.
Restoring Template:Param to the Wikipedia import from revision 230178
This is an inquiry as to why Template:Param has regressed first and a recommendation for revertion second.
As of this message, Template:Param has regressed significantly from revision 230178:
{{[safe]subst:param}}
will substitute in the wrapping tag (here,<code>
);- the template always uses
<code>
instead of allowing the editor to specify a tag via{{{tag}}}
, which may be semantically incorrect in some situations;
- a noticeable side-effect is that most template documentation pages specify parameters with the invocation
{{code|{{param|foo}}}}
which could be simplified to{{param|foo|tag=whatever}}
, wheretag
is optional
- this saves space and reduces template expansion depths
- a noticeable side-effect is that most template documentation pages specify parameters with the invocation
- specifying the parameter value now requires a user-specified pipe character (e.g.,
{{Param|2=|text}}
or{{Param|2={{!}}text
);
- this is unintuitive behaviour since this template is used to describe template parameters and not other WikiText syntax
- because the pipe character is no-longer transcluded, editors can misuse this template to notate non-template parameters (e.g., {{{
- if|:syntax abuse}}})
- nesting parameters becomes tedious and potentionally unmanageable (e.g.,
{{param|foo|{{param|bar|{{param|baz|derp}}}}}}
results in {{{foo|{{{bar|{{{baz|derp}}}}}}}}}; needs{{param|foo|{{!}}{{param|bar|{{!}}{{param|baz|{{!}}derp}}}}}}
to produce {{{foo||{{{bar||{{{baz||derp}}}}}}}}})
- nesting parameters becomes tedious and potentionally unmanageable (e.g.,
- there is spurious functionality inappropriate for contexts outside of template documentation (selection, bold styles)
- this situation-dependent and should be left to the editor’s discretion
For these reasons, I would recommend reverting the template to revision 230178 (already tried; you’ve immediately reverted it). Understandably, editors have already updated other pages with these regressions in mind, so a revert will need tooling to maintain backwards-compatibility until all pages can be sanitized.
I can't work on these templates right now, so I'll ask you to talk to him about it. You can also talk to him about {{Code}}
, which seemed broken to me after your changes.