Talk:Spanking

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia

German Subject[edit]

Hello everyone, the German article can be found as following:

https://de.wikipedia.org/wiki/K%C3%B6rperstrafe#K%C3%B6rperstrafen_in_der_Kindererziehung

I don't have the time to add the language link myself (or find out how to do it in the first place), could someone else please do it? --2001:8003:4E77:D900:106E:6651:EE0A:E22A (talk) 01:48, 16 November 2019 (UTC)[reply]

"Gray mare" listed at Redirects for discussion[edit]

An editor has asked for a discussion to address the redirect Gray mare. Please participate in the redirect discussion if you wish to do so. SpicyMilkBoy (talk) 22:04, 13 March 2020 (UTC)[reply]

Double brackets[edit]

There is an excessive use of brackets in this article, especially a very poor use of doubled-up brackets. I rewrote the section to remove these, and it was reverted with a comment of "Its [sic] just fine, revert to good".

Let us not count the ironic nature of using poor grammar to justify the reinstatement of poor grammar, but I also resent the implication that by "revert to good" my edit was not good.

It is very poor use of English to have nested brackets, and simply replacing them with square brackets dose not remove the problem, nor is the use of square brackets supported by the MOS

Can you please explain why such a state should be considered acceptable? Thank you. Curved Space (talk) 08:18, 6 June 2020 (UTC)[reply]

If you don't like it, then fix it (see WP:FIXTHEPROBLEM). The wholesale removal was inappropriate. It's really a rather minor point and it feels like a mountain is being made out of a molehill here. It's necessary to give a thorough explanation in that paragraph and the information is well-sourced. If you have a better way to rephrase it that doesn't sacrifice any of the content's meaning, then by all means do it. Also, if you're going to say it's "very poor English", then please be sure to cite a reliable source that backs that up. Thanks. I won't be discussing this further. TylerDurden8823 (talk) 09:40, 6 June 2020 (UTC)[reply]
Unhelpful response. You cannot tell me to fix the problem when you revert my fixing of the problem and then say you will not discuss any further. How can BRD progress when an editor explicitly states they will not D?
Given there will be no response, then the following is for the record:
You say that the information is well-sourced. This does not seem to be the case -- the entire setion under contention is referenced only once, by "Corporal punishment". Pediatric Clinics of North America (Review) which is not available to view. Besides, there is no dispute over the validity of the comments, only that they are excessive and disrupt the flow of work. However, I will let the current source stand, even though it cannot be verified, but have also tagged that a better or corroborating source needs to be found as well.
If you wish sources to show that it is poor English, structure -- here you are:
You may consider this a small point, but that does not mean that others will do so. As you have said you will not respond, I will re-edit the article again, and try to meet your standards, even if they are not necessarily the same as my or Wikipedia standards. Curved Space (talk) 13:06, 6 June 2020 (UTC)[reply]

"Flogging frame" listed at Redirects for discussion[edit]

A discussion is taking place to address the redirect Flogging frame. The discussion will occur at Wikipedia:Redirects for discussion/Log/2021 July 4#Flogging frame until a consensus is reached, and readers of this page are welcome to contribute to the discussion. -- Tamzin (she/they) | o toki tawa mi. 07:30, 4 July 2021 (UTC)[reply]

The redirect Ass-whuppin' has been listed at redirects for discussion to determine whether its use and function meets the redirect guidelines. Readers of this page are welcome to comment on this redirect at Wikipedia:Redirects for discussion/Log/2023 July 10 § Ass-whuppin' until a consensus is reached. Hey man im josh (talk) 16:37, 10 July 2023 (UTC)[reply]