Template talk:Copied
Template:Copied is permanently protected from editing because it is a heavily used or highly visible template. Substantial changes should first be proposed and discussed here on this page. If the proposal is uncontroversial or has been discussed and is supported by consensus, editors may use {{edit template-protected}} to notify an administrator or template editor to make the requested edit. Usually, any contributor may edit the template's documentation to add usage notes or categories.
Any contributor may edit the template's sandbox. Functionality of the template can be checked using test cases. |
Text has been copied to or from this page; see the list below. The source pages now serve to provide attribution for the content in the destination pages and must not be deleted as long as the copies exist. For attribution and to access older versions of the copied text, please see the history links below.
|
|
|
This page has archives. Sections older than 90 days may be automatically archived by Lowercase sigmabot III when more than 4 sections are present. |
Template-protected edit request on 28 September 2023
[edit]This edit request to Module:Copied has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Please change:
image = '[[File:Splitsection.svg|50px]]',
To:
image = '[[File:Splitsection.svg|frameless|upright=0.23|link=|alt=]]',
...per MOS:BLANKALT and MOS:UPRIGHT. Thanks! HouseBlastertalk 03:49, 28 September 2023 (UTC), edited to add |frameless
15:41, 28 September 2023 (UTC)
- Examples now on Template:Copied/testcases. The image is now smaller and you dropped the 50px. Is that intentional? — Martin (MSGJ · talk) 12:11, 28 September 2023 (UTC)
- Per MOS:UPRIGHT,
"px works the same as upright for users with the usual base width setting of 220px, but works counterintuitively for readers whose base width is set to a different value... For example, an image coded 275px—presumably to make it wider than most images on a particular page—is actually rendered smaller than most images if the user has changed their base width to 300px"
(emphasis in original). To convert between the two, you divide the value in pixels by 220, which in this case gives us 0.22727272727... However, because I forgot the frameless param (thank you for sandboxing this... goes to show you even trivial changes should realllllly be tested first), the upright param had no effect on resizing the image. I have edited the sandbox to reflect this, and it should be working now. HouseBlastertalk 15:41, 28 September 2023 (UTC)
- Per MOS:UPRIGHT,
- Done that looks better — Martin (MSGJ · talk) 16:57, 28 September 2023 (UTC)
Template-protected edit request on 1 April 2024
[edit]This edit request to Module:Copied has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Make the change as described in this diff Toadette (April Fools Day!) 22:15, 1 April 2024 (UTC)
- Wait, not the template, but the module. Should've posted at Module talk:Copied Toadette (April Fools Day!) 22:17, 1 April 2024 (UTC)
- Done Module talk:Copied redirects here so this is in the right place. * Pppery * it has begun... 02:29, 2 April 2024 (UTC)
Clarify where the template should go
[edit]Clarify if this template should go in the main article or the talk page. I think this is meant to be used in the talk page but it isn't very clear. I see at least one example of an article that used it in the main page see Chivalry Bookshelf. There is this line but it is not explicit enough in my opinion: "Adding this template on the talk page is not a substitute for attribution in the page history using edit summaries." J2UDY7r00CRjH (talk) 20:27, 18 July 2024 (UTC)
Merged-from nesting
[edit]This edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
A previous template was made by Flatscan at the request of Otherlleft - now deleted, with reasoning of being 'redundant' with this template - to act as a nested version of {Merged-from}.
For this reason, I propose to change the default value of the to
parameter to the article {Copied} is invoked on. Additionally/as a result, to
should not need to be specified for each from1
, from2
, etc.. This way, the template would act easier as a nested version of {Merged-from}. It might also be accompanied by a stylistic change - such as removing the ambiguity of 'to or from' in the displayed tag.
As an example, see the {copied} tag at Talk:Customer relationship management. Tule-hog (talk) 02:26, 25 July 2024 (UTC)
- Not done: it's not clear what changes you want to be made. Please mention the specific changes in a "change X to Y" format and provide a reliable source if appropriate. —andrybak (talk) 14:27, 4 August 2024 (UTC)
- Request is in 'change... to...' format, so I am assuming it is only the full meaning thats unclear.
Text has been copied to or from this page; see the list below. The source pages now serve to provide attribution for the content in the destination pages and must not be deleted as long as the copies exist. For attribution and to access older versions of the copied text, please see the history links below. |
- Observe {copied} requires values for
to1
,to2
, andto3
. I propose (if possible) to automatically use the ARTICLENAME of the page the template is called on as either all theto
orfrom
values, when only the other type of values are provided. For example, if I only specify (to1
,to2
,to3
), ARTICLENAME should be automatically assigned to (from1
,from2
,from3
) - similarly in the reverse case. Tule-hog (talk) 15:14, 4 August 2024 (UTC)
- Observe {copied} requires values for