Template talk:Bracket
(Redirected from Template talk:Bracket/testcases)
end bracket
[edit]Please add a way for this template to produce just the end bracket just like it can produce just the start bracket. CapnZapp (talk) 09:25, 21 April 2022 (UTC)
COinS pollution
[edit]How (and why) does this template pollute COinS? Doesn't it just add plain text? Hairy Dude (talk) 13:18, 2 May 2023 (UTC)
Template edit request
[edit] | This edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Please replace the code of this template
[{{#if:{{{1|}}}|{{{1}}}]}}(example output: [xxx ])
with
{{#if:{{{1|}}}|[{{{1}}}]|[}}(example output: [ xxx ])
The reason is that the current code trims leading whitespace but not trailing whitespace if the first (unnamed) parameter is present. Not trimming either will making it consistent with the way in which template parameters work generally. —Quondum 21:15, 19 December 2024 (UTC)
- Why not trim at both ends? — Martin (MSGJ · talk) 00:04, 21 December 2024 (UTC)
- Because (a) that makes it atypical template behaviour (as I already indicated), (b) it removes agency of the editor in terms of adding spaces, and (c) it would pointlessly add complexity to the template implementation. —Quondum 00:33, 21 December 2024 (UTC)
- I agree with Quondum's concerns. Not trimming spaces is particularly beneficial where the bracketed term is italicised: [ XXX ] is better and more consistent than
{{bracket| ''XXX'' }}-> [ XXX ]. -- Michael Bednarek (talk) 00:50, 21 December 2024 (UTC)
- I agree with Quondum's concerns. Not trimming spaces is particularly beneficial where the bracketed term is italicised: [ XXX ] is better and more consistent than
- Because (a) that makes it atypical template behaviour (as I already indicated), (b) it removes agency of the editor in terms of adding spaces, and (c) it would pointlessly add complexity to the template implementation. —Quondum 00:33, 21 December 2024 (UTC)
