User talk:ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ/Archive 3

Please do not subst legacy course templates which need to be cleared up
As you did at Talk:Rwandan genocide. This course is long-gone, and the template should be deleted as per Templates_for_discussion/Log/2022_May_10. Substing it means we will have no means of tracking the instances that need deleting going forward. Cheers &mdash; Amakuru (talk) 11:42, 27 December 2022 (UTC)


 * @Amakuru it is to be deleted after it is substed, as listed at WP:TFDH. ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ (talk) 11:44, 27 December 2022 (UTC)
 * No, the template serves no purpose at this point. The course mentioned was ten years ago and is long finished. The decision at the TFD was to delete it. &mdash; Amakuru (talk) 11:47, 27 December 2022 (UTC)
 * Continued at Templates for discussion/Holding cell. ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ (talk) 12:22, 27 December 2022 (UTC)
 * That said Malnadach, substing them in place was not the intent. WAP assignment was converted to a 'message' template and then substed, which was the intention here, which is likely why it has sat so long at TFDH. I can see that was not clear anywhere. Izno (talk) 17:02, 27 December 2022 (UTC)
 * Well it's hard to grasp intentions over the internet :-) If the regular TFD botops aren't willing to handle this, I can submit a BRFA to get this done. ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ (talk) 13:31, 29 December 2022 (UTC)
 * You're probably going to want to replace the versions you already substed, whenever your discussion with Primefac is done. Izno (talk) 04:43, 30 December 2022 (UTC)
 * ✅ for the record. ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ (talk) 15:37, 7 January 2023 (UTC)
 * @Amakuru, if you have a concern about substing them, the correct user to approach was the closer @Explicit, who listed it in the subst section at WP:TFDH. The likely reason is that a previous TFD for this template's successor was also substed, which I noted in my listing at TFD. Having subst and delete in the actual TFD is not required to actually end at a subst, and then delete, result. Izno (talk) 16:59, 27 December 2022 (UTC)
 * @Amakuru, if you have a concern about substing them, the correct user to approach was the closer @Explicit, who listed it in the subst section at WP:TFDH. The likely reason is that a previous TFD for this template's successor was also substed, which I noted in my listing at TFD. Having subst and delete in the actual TFD is not required to actually end at a subst, and then delete, result. Izno (talk) 16:59, 27 December 2022 (UTC)

Happy New Year, ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ!


Happy New Year! ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ, Have a prosperous, productive and enjoyable New Year, and thanks for your contributions to Wikipedia.

— Moops  ⋠ T ⋡ 16:59, 2 January 2023 (UTC)

Send New Year cheer by adding {{subst:Happy New Year fireworks}} to user talk pages.

— Moops  ⋠ T ⋡ 16:59, 2 January 2023 (UTC)


 * Thanks! ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ (talk) 03:36, 3 January 2023 (UTC)

Sudden replacement with ?
Template:Infobox television and Template:Infobox film requires the use of per their "native_name" parameters. Kindly raise it first to the linked templates' talk pages for concensus before going on an infobox change spree in TV and film articles. Thank you. Centcom08 (talk) 15:53, 11 January 2023 (UTC)
 * @Centcom08 you could at least read the page Infobox name module before reverting many edits. I have restored them from your blind reverts done without due diligence. There is already consensus from TFM, more info at Templates for discussion/Holding cell. Redundant parameters are being replaced with subtemplates as appropriate. ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ (talk) 15:55, 11 January 2023 (UTC)

About the Traffic Report
Don't feel the need to make that comment section any longer, but just wanted to acknowledge that we of the WP:TOP25 are probably not the best people to talk about India, living far from it (whether in America, Europe or New Zealand) and being a bunch of goofballs who among other things aren't above using song lyrics instead of proper write-ups. I always think if our approach compensating ignorance with irreverence might instead be insensitive. If so, I'm deeply sorry if what you read of our work in the Signpost soured your opinion on the whole newspaper (who at times even unearth people doing worse things with Wikipedia). igordebraga ≠ 01:47, 18 January 2023 (UTC)

Your recent changes to various South Korea-related articles
Hi ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ, you recently made changes to various South Korea-related articles, in particularly, the Infobox by changing  to , however this changes causes issues to the Infobox presentation due to the subheader (Korean name) that was included automatically by Infobox Korean hence causing parameters (genre, based_on, developed_by, etc) that are part of Infobox television to be wrongly displayed as if it's part of the Korean name grouping which is misleading. I have reverted the edits you had made. While I understand your intention, you should temporarily stop your extremely speedy replacement till a resolution (which is to resolve the misleading automatic subheader) is put in place otherwise you're simply causing thousands of television/film-related articles that uses Infobox television or Infobox film to have their parameters misleadingly be grouped under Infobox Korean.  — Paper9oll  (🔔 • 📝)  17:32, 20 January 2023 (UTC)


 * @Paper9oll What do you mean "as if it's part of the Korean name grouping"? They are not bolded unlike other infobox params. Do you really think people consdider genre, based on etc,. as beng part of Korean language? Infobox name module has long been deprecated and is set for complete overhaul. No wonder the merger has been pending for so long if every effort to replace it is reverted. ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ (talk) 17:43, 20 January 2023 (UTC)
 * @ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ Before and After, do you happened to see the differences? Fyi, Extraordinary Attorney Woo wasn't reverted by me but by Revirvlkodlaku hence it isn't just me opposing it. This isn't about common sense or not but about the presentation. Merger are perfectly okay if they serve the purpose without breaking anything including presentation in particularly Infobox presentation.  — Paper9oll  (🔔 • 📝)  17:48, 20 January 2023 (UTC)
 * Yes, I do. That is how the replacement template is designed to be, grouping all the different scripts and romaniazations under Korean name. ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ (talk) 17:51, 20 January 2023 (UTC)
 * @ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ Yes I know, unfortunately this causes presentation issues which needs to be resolve, I had the raise the same issues on WP:TFD/H which I believe you're aware of, hence I would like you to hold on till there are further comments on how to resolve there. In my pov, it's misleading to have "Korean name" using the same before and after example as there's also "Production" and "Release" subheading in the Infobox. The merger (noting that the end result of 2017 TFD was merge instead of replace) should take into account the behaviour of Infobox name module and tune the destination template accordingly either by adding new param or adding some sort of condition statements.  — Paper9oll  (🔔 • 📝)  18:07, 20 January 2023 (UTC)
 * You think it is unnecessary, others think it is better and explicitly wanted the template that way. Anyway per my comments at TFDH, I'm done spending time on this. To anyone who might be tempted to carry out the TFD - just forget about it and spend your time on something more productive. ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ (talk) 19:14, 20 January 2023 (UTC)
 * @ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ I'm not sure, we are even on the same bandwidth. But I found a solution, which is to modify your replacement scripts to replace  with   instead of   hence it would have the same before and after presentation. I appreciated your hardwork and time spent, I have presented you a solution to the concern that me and multiple editors like Revirvlkodlaku has raised on, whether or not, you're happy with continuing using the solution is up to you to decide on, I can't force it on you if you decided to move away, not much harm (if not, no harm at all) whether it's merged or not. Thanks!  —  Paper9oll  (🔔 • 📝)  05:27, 21 January 2023 (UTC)
 * @Paper9oll Thanks for that. Had a bad day IRL and when topped with many edits getting reverted it put me off, apologies for my rudeness last night. I'm a bit busy over the weekend, will go back and add those params with Infobox Chinese/Korean when free. are you okay with replacing them like this instead? ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ (talk) 06:42, 21 January 2023 (UTC)
 * @ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ No worries, glad to see you accepted the solution. Keep the good work, happy editing!  — Paper9oll  (🔔 • 📝)  08:38, 21 January 2023 (UTC)
 * @ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ, I'm still not clear on what benefit that kind of change confers to the infobox. Would you mind explaining? Sorry if I'm missing something that has already been covered in separate conversations... Revirvlkodlaku (talk) 15:12, 21 January 2023 (UTC)
 * Okay, so the original reason given in the merger proposal in March 2017 is that Infobox name module is inferior to Infobox Chinese and its subtemplates which covered Korean, Japanese and other East and South-east Asian languages with multiple writing systems and romanization conventions. They had the same function along with support for more options that Infobox name module doesn't have. At that point most usage of Infobox name module seemed to involve languages covered by Infobox Chinese and its subtemplates.Having multiple templates providing similar functionality is unhelpful both for template maintainers and editors who would be confused about what to use when there are multiple options for similar things. However there was a delay in fully implementing the merger at the template level due to complicated coding involved. During this time there was a significant increase in the usage of Infobox name module for European, Middle eastern and Indian languages. These are clearly inappropriate for merging with Infobox Chinese. So what we are doing now is replacing the template at the article level by deprecating its usage for languages better covered by the Infobox Chinese family of templates, which would put them in Category:Infobox name module using deprecated parameters. Once we bring the number of articles in the category to zero, we would be removing support for these languages and retain Infobox name module for all other languages not covered by better templates. ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ (talk) 15:10, 23 January 2023 (UTC)

The page User:MalnadachBot is totally illegible
If you want people to be able to know what your bot is for or what it is doing, you shouldn’t use a ridiculous zany font or an absurdly tiny font size. It is entirely impossible for ordinary humans to read any of the text on the page User:MalnadachBot. –jacobolus (t) 05:57, 1 February 2023 (UTC)


 * I thought your name was familiar, just remembered you were involved in a recent dispute with me, casting aspersions and editing disruptively following which you were briefly blocked, as seen here and here. Opening a discussion at BOTN with meritless arguments about how mediawiki works and now this. Since you are obviously grinding your axe hoping something will stick, I am forbidding you from posting in my talk page again. ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ (talk) 06:23, 1 February 2023 (UTC)
 * , sorry that you seem to be having a rough day. When I check the font size on that page with my browser's inspector, it shows that the font is rendering at 100% of the normal size for page content, the same as normal article text. If the font is rendering too small for you, I can suggest something that I do in my browser settings: go to Preferences -> Appearance -> Fonts -> Advanced, or something similar, and set the minimum allowable font size. It messes with the intended display of some pages when accessibility-unfriendly editors have set very small font sizes, but I find it helpful overall. – Jonesey95 (talk) 06:26, 1 February 2023 (UTC)

Not having any of your stylesheet's typefaces installed on my machine, I just get your regular fallback serif font, which makes it look like the page hasn't loaded properly. As this user is a bot, some people are going to be looking to that page for a straightforward explanation of the work that it's doing: I don't think that information should be served to some users in a hard-to-read decorative typeface like Samarkan. --Belbury (talk) 18:58, 2 February 2023 (UTC)


 * I switched it to an alternate style which has only borders. ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ (talk) 04:54, 3 February 2023 (UTC)
 * This is a big improvement. Thanks. –jacobolus (t) 09:50, 3 February 2023 (UTC)

Typeface on user talk archives
Might you consider changing your user talk archive pages so that the default typeface for the body text is used, rather than overriding it with a cursive-style typeface? I feel that it's more difficult to read large passages of text when they are set in cursive. Your consideration would be appreciated! isaacl (talk) 21:57, 6 February 2023 (UTC)


 * Restored plain font. ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ (talk) 16:29, 7 February 2023 (UTC)
 * Thanks; I appreciate the change. isaacl (talk) 02:22, 8 February 2023 (UTC)

RfC on your bot
Hello, I just wanted to let you know that I've started an RfC that relates to MalnadachBot's mass fixing of lint errors and deprecated HTML tags. You can find it here: Village_pump (policy). Thanks.  —&#8288;Scotty Wong &#8288;— 08:39, 7 February 2023 (UTC)


 * Noted, thanks. ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ (talk) 16:30, 7 February 2023 (UTC)