Wikipedia:Village pump (technical)

 Policy Technical Proposals Idea lab WMF Miscellaneous 

• Table of contents
• First discussion
• End of page
• New post

The technical section of the village pump is used to discuss technical issues about Wikipedia. Bug reports and feature requests should be made in Phabricator (see how to report a bug). Bugs with security implications should be reported differently (see how to report security bugs).

If you want to report a JavaScript error, please follow this guideline. Questions about MediaWiki in general should be posted at the MediaWiki support desk. Discussions are automatically archived after remaining inactive for five days.

« Archives, 194, 195, 196, 197, 198, 199, 200, 201, 202, 203, 204, 205, 206, 207, 208, 209, 210, 211, 212, 213, 214

How to Find??

Identify political leader pages lacking the Infobox officeholder template, along with a user-friendly filter for sorting them by election or state. I have work on Tamil Nadu state & 2021 Assembly Election. Thanks in advance. - IJohnKennady (talk) 03:36, 6 August 2023 (UTC)

Maybe try Petscan, with a category selected, a high depth of subcategories (e.g. 10), and a "doesn't have template" {{Infobox officeholder}} selected. Example. Perhaps choose more specific categories and templates to reduce the # of results to a manageable level. Hope this helps. –Novem Linguae (talk) 04:39, 6 August 2023 (UTC)

Thank you very much i'll explore this. --IJohnKennady (talk) 13:55, 6 August 2023 (UTC)

And i have one more doubt, how to find, How many pages didnt have Electoral performance heading. _IJohnKennady (talk) 11:52, 9 August 2023 (UTC)

@IJohnKennady, you can combine "doesn't have" (-"your text") with incategory: or hastemplate: searches to find articles like that, e.g., https://en.wikipedia.org/w/index.php?search=hastemplate%3AInfobox_officeholder+-%22electoral+performance%22&title=Special%3ASearch&ns0=1 It won't be perfect, but it should find you a lot of articles. Whatamidoing (WMF) (talk) 16:20, 14 August 2023 (UTC)

Weno

Weno has a broken infobox displaying a giant redlink. I can't figure out how to fix it as it's somehow procedurally generated. Anyone know what to do? Ten Pound Hammer • ^{(What did I screw up now?)} 17:40, 9 August 2023 (UTC)

The template documentation is no help; it just says it "should not be used from article namespace pages". (Didn't we have a whole bunch of giant rfcs all saying not to do the sort of things that template does? Or did they suddenly start going the other way over the last year while I've been mostly inactive?) —Cryptic 17:49, 9 August 2023 (UTC)

I believe the most recent discussion on Wikidata in infoboxes is Wikipedia:Wikidata/2018 Infobox RfC, which came to no consensus. Unfortunately there's been a frozen conflict here, with regular "no consensus" results, for about as long as I've been editing. * Pppery * _{it has begun...} 17:56, 9 August 2023 (UTC)

And I also removed the clearly wrong "This template is rated as pre-alpha" from the documentation, since it has 520 mainspace uses. * Pppery * _{it has begun...} 18:01, 9 August 2023 (UTC)

 Fixed (by abandoning that particular template entirely and switching to ordinary {{infobox settlement}}) * Pppery * _{it has begun...} 17:56, 9 August 2023 (UTC)

It looks like the problem is that Template:Infobox settlement/Wikidata says {{#if: {{#property:P31}} | [[{{#property:P31}}]] }} which then strings the two P31 parameters of wikidata:Q1009384 together and turns them into a link. I am not sure that P31 can always be interpreted as "settlement type", certainly not as something that can be turned into a piped link. Jo-Jo Eumerus (talk) 18:16, 9 August 2023 (UTC)

Per the RFC, that Wikidata property call is invalid, since it does not check to see if the value is sourced. I have expanded the documentation for the template to explain that it should not be used in article space until it is modified to conform to the RFC's sourcing requirement. – Jonesey95 (talk) 18:25, 9 August 2023 (UTC)

I'm honestly inclined to just nominate it for deletion - the chance of the warning you added becoming anything other than dead letter otherwise is negligible and it seems like nobody wants to do the necessary work. * Pppery * _{it has begun...} 18:52, 9 August 2023 (UTC)

No objections from me. The doc has had a note about the template needing to be fixed for three years, and the template has mostly gotten worse since then. It seems to be abandoned. – Jonesey95 (talk) 19:34, 9 August 2023 (UTC)

Does anyone know whether {{#invoke:WikidataIB|getValue|rank=best|qid={{{qid|}}}|Pxxx|fetchwikidata=ALL|> is the right replacement for {{#if: {{#property:Pxxx}} | [[{{#property:Pxxx}}]] }} code? To solve the source thing. Jo-Jo Eumerus (talk) 20:01, 9 August 2023 (UTC)

Yes, in theory. But the fact that nobody has responded to that comment until now strengthens my and Jonesey95's point. * Pppery * _{it has begun...} 11:34, 14 August 2023 (UTC)

Who Wrote That?

Tracked in Phabricator
Task T344011

I don't know where to lodge this information about Wikipedia:WhoWroteThat, since the page is a redirect to mediawiki; perhaps someone here is also active there or knows who to ask on en.wiki about this.

Until Bocaranda, I've found WhoWroteThat to be reliable. Lately, it is glitching at Nelson Bocaranda, and I'm wondering if the interlanguage links are somehow throwing it off (since I started noticing it about the time I added them, but I can't be certain that was it). Today, it is attributing a ton of text that I wrote to WMrapids; as examples, look at the sentence using "knee pain", and the sentence starting with "Contrary to Article 143". And then halfway through the "Responses" section, it stops working entirely. SandyGeorgia (Talk) 15:18, 10 August 2023 (UTC)

@WhatamIdoing: who first told me about WWT, and may know where to put this; I don't do mediawiki. SandyGeorgia (Talk) 15:21, 10 August 2023 (UTC)

Community Tech handles that, so the best person to reach out to is probably MusikAnimal (WMF). WhatamIdoing (talk) 16:16, 10 August 2023 (UTC)

Hmm, I'm not sure what's going wrong here! I have filed phab:T344011 so we can investigate further. Thanks for the bug report, MusikAnimal (WMF) (talk) 18:26, 10 August 2023 (UTC)

Thanks to both, SandyGeorgia (Talk) 23:26, 10 August 2023 (UTC)

In the future, for WhoWroteThat, bugs can be filed directly on Phabricator using this link. Just make sure to put "Who-Wrote-That" in the tags section. This will skip a couple of middlemen and pings. Creating a ticket with the correct tag emails the developers of that tool, such as MusikAnimal. Hope this helps. –Novem Linguae (talk) 12:30, 11 August 2023 (UTC)

I appreciate that info Novem Linguae but I'm unlikely to file a report directly-- not familiar enough to know if something is truly a bug or just me. Instead, I am more likely to ping you directly :) :) SandyGeorgia (Talk) 15:48, 15 August 2023 (UTC)

"AfDs closing today" bug?

Hi everyone! The link Wikipedia:List_of_AfDs_closing_today goes to the log page for AfDs that are a day older than they should be, i.e. from 8 days ago (as opposed to 7). For example, today (11/08), it should open Wikipedia:Articles for deletion/Log/2023 August 4, but it instead opens Wikipedia:Articles for deletion/Log/2023 August 3. Actualcpscm ^{scrutinize, talk} 14:40, 11 August 2023 (UTC)

It's an easy fix, but I wanted to make sure it isn't intentional first. Actualcpscm ^{scrutinize, talk} 14:45, 11 August 2023 (UTC)

Strange one that. It's easy to make it display the list from 7 days ago instead of 8, but it looks like it's always been like that. Is it actually being used anywhere? Black Kite (talk) 15:05, 11 August 2023 (UTC)

Lourdes' AfDs Closing script uses it, which seems to be the primary use case. If there are no objections here, I'll just fix it and see if anyone complains. Actualcpscm ^{scrutinize, talk} 15:13, 11 August 2023 (UTC)

Pinging Lourdes, since the page was apparently created for this script. Actualcpscm ^{scrutinize, talk} 15:16, 11 August 2023 (UTC)

Please go ahead. Thank you for the ping. Lourdes 05:24, 12 August 2023 (UTC)

I think the reason I made it 8 days was because the AfD should be deleted or kept after seven days of discussion (it would be the eighth day when the AfDs would be closed). Just double check and make the change if you think that is prudent. Thanks, Lourdes 05:29, 12 August 2023 (UTC)

Changed it, I think it works better now; it shows the AfDs which are either closeable or will become closeable by the end of the day. Actualcpscm ^{scrutinize, talk} 09:40, 12 August 2023 (UTC)

IIRC it was set at today minus 8 days (instead of today minus 7 days) to ensure that all AFDs listed were those actually eligible for closure. We did have a big problem with people closing non-snowy XfDs early, assuming that the 7 days was counted from midnight. I see that this has happebned today - for example Wikipedia:Articles for deletion/Alternative versions of Robin was raised at 02:56, 5 August 2023 (UTC) and was closed at 02:34, 12 August 2023 (UTC) - that is, 6 days 23 hours 38 minutes later. Whilst 22 minutes can be seen as a technical quibble, it did not run the full 7 days. --Redrose64 🌹 (talk) 16:50, 12 August 2023 (UTC)

That makes sense, but I think -7 days is more useful; the vast majority of AfDs at -8 will already be closed. Maybe a reminder of the 7 day duration on the AfDs closing today page would be warranted? Actualcpscm ^{scrutinize, talk} 17:08, 12 August 2023 (UTC)

I remember when AFDs were only open for 5 days, and we had disputes over people closing them early back then, too.

Expecting people to pay attention to tiny little details, like the exact number of hours/minutes the AFD has been open, is unrealistic. If you want them to not close discussions early, you have to make it difficult for them to make the mistake.

I suggest that you consider whether rushing to close an AFD at the earliest possible moment is something we should be doing. We know that it's actively harmful to close a discussion at half a day early, because that causes disputes between editors. The dispute is unpleasant, and the discouragement to AFD closers is damaging. Is it actually harmful to close a discussion half a day after the first possible minute? Who gets hurt in such a situation, and how? WhatamIdoing (talk) 16:40, 14 August 2023 (UTC)

The primary tool for closing discussions, used by the vast majority of closers, is WP:XFDC. This does in fact prompt closers if the discussion hasn‘t been open for the full seven days, so it‘s very hard for me to imagine how it could happen accidentally.

I don‘t think we should be „rushing to close“ as soon as it‘s been exactly seven days. But the script is more useful if it links to a list of AfDs that are actually „closing today“, i.e. where the seven day period has elapsed or will elapse within a few hours. Actualcpscm ^{scrutinize, talk} 16:50, 14 August 2023 (UTC)

What is more useful about it?

I can understand someone being irritated that the name says "closing today", if they thought that it meant "these AFDs are close later today, so you still have a chance to participate" instead of "these are the AFDs that admins are currently/already in the process of closing today", but that sounds like a reason to change the page title, not to change the contents of the page. WhatamIdoing (talk) 17:16, 14 August 2023 (UTC)

But both apply to the current version. The primary use of this page is, as far as I‘m aware, for closers to see discussions that have recently reached a duration of 7 days. If you go to the deletion log for 8 days ago, most of the time, the vast majority of discussions will already be closed or relisted. I really don‘t see the problem with the 7 day version; if I‘m missing something, please do point it out. Actualcpscm ^{scrutinize, talk} 18:47, 14 August 2023 (UTC)

It sounds like the 7-day version isn't precisely 7 days 0:00 hours through 7 days 23:59 hours. It sounds like the 7-day version includes discussions that are (at the time they first appear on that page) less than seven days old.

"The vast majority of discussions get closed or relisted as soon as they are eligible" is not what I would call a problem. Are you trying to optimize this for the sake of users who want to close more AFDs personally and are feeling disappointed that there are (apparently) plenty of other people already doing this work? WhatamIdoing (talk) 03:18, 16 August 2023 (UTC)

Neither the previous version nor this one are „precisely 7 days 0:00 hours through 7 days 23:59 hours“, the page just transcludes the deletion log for a specific calendar day. I’m not trying to optimize this for users who are disappointed they can’t close more AfDs, I’m trying to optimize it for users who close AfDs in general, because they’re the ones who use this. Actualcpscm ^{scrutinize, talk} 07:15, 16 August 2023 (UTC)

Note: Now the page is broken (see Wikipedia:List_of_AfDs_closing_today) due to WP:PEIS being exceeded. Maybe it could redirect to the appropriate log entry instead of transcluding it? Actualcpscm ^{scrutinize, talk} 18:27, 17 August 2023 (UTC)

Redirects to dynamically-calculated pages don't work, so that would require a bot to edit it every day, which is more effort than value. Perhaps tomorrow there will be fewer AfDs so the page will work again. * Pppery * _{it has begun...} 18:29, 17 August 2023 (UTC)

Redirects to dynamically-calculated pages don't work: Well, that's a disappointing limitation. I presumed that if it can be transcluded, it can be targeted with a redirect. Thanks for pointing this out. Actualcpscm ^{scrutinize, talk} 18:37, 17 August 2023 (UTC)

Ajax rollback

Is it just a conflict with some script also loaded, or is it non-existent here? ~Lofty abyss 08:38, 13 August 2023 (UTC)

Please be more specific. Generic Ajax rollback is now in core ("Show a confirmation prompt when clicking on a rollback link") so you don't have to import any script, and if you use a more elaborate script you most likely have to turn the option off. Nardog (talk) 09:06, 13 August 2023 (UTC)

I mean the functionality that used to be able to rollback on special:contribs, without redirecting to another page... ~Lofty abyss 09:27, 13 August 2023 (UTC)

What about it? Nardog (talk) 10:15, 13 August 2023 (UTC)

@Lofty abyss, have you tried mw:safemode to find out whether you have a conflicting script? Whatamidoing (WMF) (talk) 16:43, 14 August 2023 (UTC)

I still only get the default rollback links.

@Nardog, I haven't seen it in quite some time... ~Lofty abyss 17:07, 14 August 2023 (UTC)

Blank your global.js, common.js, and the .js for whichever skin you're using, and turn on "Show a confirmation prompt when clicking on a rollback link". Nardog (talk) 18:21, 14 August 2023 (UTC)

But confirmations isn't what I'm seeking? There were these [ajax] links which did it with no confirmation or page redirections, once... ~Lofty abyss 19:35, 14 August 2023 (UTC)

On what wiki have you seen it? Whatever it is, it's a user script or gadget, not something from the MediaWiki software or an extension. Nardog (talk) 02:52, 15 August 2023 (UTC)

Row moving over one cell. Table bug using Flagg template (and others)

Tracked in Phabricator
Task T344562

Note: See screenshot farther down. See: T344562.

I am using Firefox on Windows 10 Pro PC. Latest standard versions on both. This does not happen to me on the Edge browser. Whether I am logged in or not. I logged out of Wikipedia and I still have the problem with Firefox. So it is not my JS and CSS files. I also disabled all my Firefox addons and then closed all my Firefox windows. I launched Firefox and I still have the problem with Firefox. No addons and not logged in.

The problem tables all use templates within the table. But it is not a problem with tables using {{flaglist}}.

See List of countries by total health expenditure per capita. Both tables there use {{flagg}}.

Open visual editor. Click to the right of the either of the 2 tables. Note the bizarre result of the row moving over one cell. Click to the right of a different row and note that row moving over one cell. If you click above or below the table the problem goes away.

I opened visual editor for Help:Table and tried clicking to the right of many tables. Closer and farther away. I have noted the problem there with only one table so far. Have to go there to use visual editor on this table:

• Help:Table#Table cell templates

Template output for selected table cell templates

Template usage	{{Yes}}	{{No}}	{{Dunno}}	{{N/A}}	{{N/A|N/A}}	{{n/a|n/a}}
Using template	Yes	No	?	—	N/A	n/a
Without template	Yes	No	?	—	N/A	n/a

I see the problem only with the middle row there. Click to the right of it, and click closer until the row moves over one cell. It doesn't happen all the time.

I removed the templates from a few rows of one of the tables in the list article. This solved the problem. And the small table above only has the bug in the middle row using templates. --Timeshifter (talk) 15:00, 14 August 2023 (UTC)

If you don't get a good reply here, try posting this as a concise bug report on Phab, tagging it as Visual Editor, and maybe with some screenshots to help visualize the problem. Link to make a Phab bug report. –Novem Linguae (talk) 00:01, 15 August 2023 (UTC)

Novem Linguae. See T344562

Posted here too:

Template talk:Flagg#Row moving over one cell. Table bug using Flagg template

--Timeshifter (talk) 22:34, 19 August 2023 (UTC)

Google shows page in WP space

It was my understanding that Google only lists Wikipedia articles that are in article space, also known as mainspace. I also thought that Google only listed articles that have been reviewed by New Page Patrol, but that is not my concern in this post. However, I have seen that a Google search for Zepotha shows Wikipedia:Zepotha. For background, Zepotha is a fictitious movie, apparently originating on TikTok. Multiple pages about it were recently deleted from draft space as a hoax. I tried to search Google for non-Wikipedia mentions of this name or meme. As my screen shot shows, Google displays Wikipedia:Zepotha, which is a red link showing that it has been deleted three times by administrators. So my question is whether anyone is aware of a way that Google lists pages in Wikipedia project (WP) spaceRobert McClenon (talk) 05:16, 14 August 2023 (UTC)

Robert McClenon, Google can display anything that its algorithms decide to display. Wikipedia:Controlling search engine indexing says Respecting the tag, especially in terms of removing already indexed content, is up to the individual search engine, and in theory the tag may be ignored entirely. Cullen328 (talk) 05:31, 14 August 2023 (UTC)

User:Cullen328 - Thank you, sort of. In this case Google was stupid. Articles in spaces other than article space will seldom be of interest to a reader who is using a search engine to search the World Wide Web. Pages in project space are seldom of interest to someone who is not a Wikipedia volunteer. In this case it will just confuse the searcher. Duh. Robert McClenon (talk) 06:07, 14 August 2023 (UTC)

Robert McClenon, the only website that Wikipedia editors have any direct influence on is Wikipedia. As for Google, they are useful 98% of the time, but occasionally, they screw up. For example, their navigation instructions to my neighborhood tell people to drive through a locked gate to get to my house, and when a driver passes by the locked gate, the directions turn into complete nonsense. I have to warn guests. Cullen328 (talk) 06:16, 14 August 2023 (UTC)

It looks like most namespaces are allowed to be indexed by search engines by default, the exceptions being unpatrolled mainspace pages, user pages, and draft pages. (There are also a few more specific exceptions - e.g. AfD, AN, SPI, LTA, RSN, RfA, etc.). I suppose WP: space is hard in that there are a number of pages there that could be legitimately useful, especially to editors. LittlePuppers (talk) 06:27, 14 August 2023 (UTC)

I'm not sure why ppl think that only main space is of interest to Google or people trying to find information on Wikipedia for that matter. They might prioritise main space higher internally in their algorightme of course, but information is information. If you put it on the web, Google will index it and probably should index it. While we exclude some pages that might be used to game the system, or that are more likely to include personal information etc. In general, every single page is indexed. —TheDJ (talk • contribs) 13:36, 14 August 2023 (UTC)

Search length

Help:Searching says the maximum search string is 300 characters, which matches my experience. However, it now seems to be accepting only 255 characters. Has it changed? This breaks some existing searches. (Per phab:T107947, the restriction seems to be an arbitrary one to discourage slow searches, but I'm having to remove optimisations to fit within the lower limit. Has someone scored an own goal?) Certes (talk) 09:38, 14 August 2023 (UTC)

That phab to reduce the max search characters to 255 was closed as resolved in 2015. Are you saying that 300 characters worked from 2015-2023 and recently stopped working? Can you give an example query that recently worked but stopped working? Maybe that info will help someone investigate. –Novem Linguae (talk) 00:00, 15 August 2023 (UTC)

Bizarre template behaviour

Take a look near the bottom of Berliner FC Dynamo, in the sections "References", "Further reading", and "External links". {{reflist}} and {{cite news}} templates are not displaying as intended, but rather as links to the template pages. I cannot see what is causing this. Your help would be appreciated. DuncanHill (talk) 10:45, 14 August 2023 (UTC)

Oh! I just saw aa notice about a template size limit at the top. Never seen one of those before! DuncanHill (talk) 10:47, 14 August 2023 (UTC)

The notice is made with {{Citations broken from PEIS limit}}. The page is in the hidden category Category:Pages where post-expand include size is exceeded. Preview shows a warning at top with a link to Help:Template#Template limits. The category and preview warning are automatic and don't rely on the template. PrimeHunter (talk) 10:55, 14 August 2023 (UTC)

Its got over 1100 references. Many sentences have multiple, so perhaps some can be cut down. The flags could also be cut, but that is only a small amount all up. Graeme Bartlett (talk) 11:55, 14 August 2023 (UTC)

The history section is far too long. I've commented on the talk page. i only went to it to try to fix a Category:Harv and Sfn no-target errors. DuncanHill (talk) 12:04, 14 August 2023 (UTC)

Should probably do WP:SPINOUTs until each article is down to less than 500 references. –Novem Linguae (talk) 00:04, 15 August 2023 (UTC)

There are already four large spinouts with 950 kB total:

• History of Berliner FC Dynamo (1954–1978) (182 kB)
• History of Berliner FC Dynamo (1978–1989) (299 kB)
• History of Berliner FC Dynamo (1989–2004) (236 kB)
• History of Berliner FC Dynamo (2004–present) (233 kB)

The problem is that a user also added a 328 kB history section [1] to the main article. It should be drastically cut. PrimeHunter (talk) 11:05, 15 August 2023 (UTC)

Template:Infobox scientist/Wikidata: thesis parameter causes links in links lint error

See discussion at Template talk:Infobox scientist/Wikidata#Thesis causes links in links lint error. Please continue the discussion there. There are actually two issues. One is with the template and one is I can't figure out how to add an academic thesis in Wikidata. —Anomalocaris (talk) 17:29, 14 August 2023 (UTC)

Edit error

For the past fortnight the text on the edit source page has frequently randomly shrunk so that only three lines are visible and can be edited. I have tried using a diferent browser and a different computer and neither solved the problem.

I have a screenshot but it is in Word and the instructions say it has to be png, so I would have to find out how to convert it if uploading it would be helpful. Thanks if anyone can help. Dudley Miles (talk) 18:44, 14 August 2023 (UTC)

first thing i'd suggest is to try "safemode" (add safemode=1 to browser address line, preceded with ? Or if it already contains ?, then with & ). If the issue goes away in safemode, it means most probably some script or gadget you have installed or activated is the culprit. If it doesn't go away, and presuming windows operating system, use snipping tool (windows key, type snipping tool, and click on the app when you see it), which lets you save as png to capture the screenshot.

Peace. קיפודנחש (aka kipod) (talk) 19:40, 14 August 2023 (UTC)

A screenshot would be very helpful for visualizing the problem, since there was no steps to reproduce provided. To convert a screenshot from Word to PNG, try the following.

1) Open an image editing program such as MS Paint

2) Open your word Document

3) Right click on the image -> copy

4) Switch focus to Paint

5) Paste

6) Save as -> something.png

7) Upload to Wikimedia Commons or your preferred third party image host

8) Link to it here –Novem Linguae (talk) 00:08, 15 August 2023 (UTC)

@Dudley Miles: Or see the box displayed when editing this page, which says

• Would a screenshot help you to describe the problem? If so, please follow the directions at Wikipedia:Screenshots of Wikipedia.

which is a more direct method, not involving Word. --Redrose64 🌹 (talk) 07:39, 15 August 2023 (UTC)

Thanks for the advice. I have uploaded c:File:Edit problem.png. Dudley Miles (talk) 10:53, 15 August 2023 (UTC)

So the edit box has its normal dimensions, but only three lines inside it can be used (as shown by the scrollbar on the right). I've not come across that before. --Redrose64 🌹 (talk) 13:18, 15 August 2023 (UTC)

Something is definitely wrong because you have syntax highlighting enabled but it is not actually highlighting anything. As others have pointed out, you'll want to try safe mode first, i.e. this link. If things look okay there, that means it is very likely a script or gadget that you're using that is causing the problem. Try removing things one by one at Special:MyPage/common.js and/or Special:MyPage/vector.js. — MusikAnimal ^talk 18:06, 15 August 2023 (UTC)

I have followed MusikAnimal's instructions and the problem code appears to be "importScript('User:Lingzhi2/reviewsourcecheck-sb.js'); // Ling's source review script". It is curious that I installed the code in September 2021 and I have not had a problem until now, but I deleted it and trust this will solve the problem. Thanks for all the help. Dudley Miles (talk) 20:04, 15 August 2023 (UTC)

CSS styles for discussion threads

After reading a comment about French Wikipedia's style rules for discussion threads, I created my own user stylesheet to experiment with styling discussion threads. It has CSS style rules to define alternating background colours for each nested reply (up to 18 levels), and to add a vertical line to the left of each list (that is, corresponding to one level of nesting).

If you use a recent version of Safari or a Chromium-based browser such as Chrome or Edge, and are interested in trying it out, see User:Isaacl/style/discussion-threads. It's subject to change as I try different things. It works for any page where the reply tool or topic subscription is enabled. (The stylesheet checks for an HTML attribute that the discussion tool features add to mark comments.) A caveat: the styling is awkward with comments made using bulleted list items. All the same, so far I find it helpful to track threads. isaacl (talk) 01:08, 15 August 2023 (UTC)

For a mockup of the resulting appearance, see User:Isaacl/style/discussion-threads § Example. isaacl (talk) 17:29, 18 August 2023 (UTC)

Styles.css

Hi, y'all! I just created a stripe, but when adding it to one of my pages, User:Tails Wx/genderfluid strip, it stated "Page User:Tails Wx/genderfluid stripe/styles.css must have content model "Sanitized CSS" for TemplateStyles (current model is "CSS")." The link to the code is User:Tails Wx/genderfluid stripe/styles.css. Can anyone assist and help as to why it isn't working? Thanks! Tails Wx (they/them) ⚧ 03:04, 15 August 2023 (UTC)

Should work now. When you create a .css page in the user space, it is treated as a CSS content model. The reasons for that are somewhere in the "security" basket. An interface admin (such as myself) can change the content model to sanitized CSS. Izno (talk) 07:18, 15 August 2023 (UTC)

Alright. Thanks! Tails Wx (they/them) ⚧ 07:19, 15 August 2023 (UTC)

Tech News: 2023-33

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• The Content translation system is no longer using Youdao's machine translation service. The service was in place for several years, but due to no usage, and availability of alternatives, it was deprecated to reduce maintenance overheads. Other services which cover the same languages are still available. [2]

Changes later this week

• The new version of MediaWiki will be on test wikis and MediaWiki.org from 15 August. It will be on non-Wikipedia wikis and some Wikipedias from 16 August. It will be on all wikis from 17 August (calendar).
• Starting on Wednesday, a new set of Wikipedias will get "Add a link" (Latin Wikipedia, Ladino Wikipedia, Luxembourgish Wikipedia, Lak Wikipedia, Lezghian Wikipedia, Lingua Franca Nova Wikipedia, Ganda Wikipedia, Limburgish Wikipedia, Ligurian Wikipedia, Lombard Wikipedia, Lingala Wikipedia, Latgalian Wikipedia, Latvian Wikipedia, Maithili Wikipedia, Basa Banyumasan Wikipedia, Moksha Wikipedia, Malagasy Wikipedia, Armenian Wikipedia, Kyrgyz Wikipedia). This is part of the progressive deployment of this tool to more Wikipedias. The communities can configure how this feature works locally. [3]

Future changes

• A few gadgets/user scripts which add icons to the Minerva skin need to have their CSS updated. There are more details available including a search for all existing instances and how to update them.

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

MediaWiki message delivery 05:57, 15 August 2023 (UTC)

f:unctions broke three redirects

This is a followup to my recently reported (July 30) new fat: project conflicting with a couple English wiki article titles (one was a redirect and the other an article). In that discussion Pppery pointed to another new project which was going to cause trouble: "There's also f:, which is about to become an interwiki prefix for Wikifunctions, and conflicts with three redirects." See phab:T325908.

Unfortunately JD Forrester dismissed these with his "won't fix" comment "Eurgh, yeah, I don't think namespaceDupes will fix those. There are only three, low-value redirects on enwiki, but across the cluster there are likely a few that we'll be sad to lose." and Denny functions closed the task as Resolved.

So once again I find that if you really want to get something done, it's better to ask at the village pump rather than Phabricator (where you're most often dismissed or ignored).

@Taavi: can you work the same magic with f: you did with fat: using the page move API and page IDs queried from the replicas for "F:NV", "F: NV", and "F:F:F"? Thanks, wbm1058 (talk) 14:55, 15 August 2023 (UTC)

Contrary to your claim, I did not dismiss this concern, I complained that we didn't have a way of fixing it automatically, and expressed sadness that we can't fix it automatically, unlike when namespaces are added (because interwikis work in a different way).

You (or someone) will need to make a series of action=edit API calls to manually fix each of them; unlike pages hidden by namespace changes, they're still available via their page ID in the API.

Sorry for the confusion! Jdforrester (WMF) (talk) 03:16, 16 August 2023 (UTC)

Oh, I understood you perfectly. Your team of paid employees had no intention of (manually) fixing the problem they created. You expect volunteers to fix it for you. The first step is to query the page IDs from the replicas. – wbm1058 (talk) 16:20, 16 August 2023 (UTC)

page_id	page_title
17983100	F:F:F
65565106	F:NV
32454679	F:_NV

Then the second step is to use the Special:ApiSandbox to move the pages, filling in the necessary fields in the forms.

 Done – pages moved to F – F – F, F – NV and F - NV.

(and no, I did not need to make a series of action=edit API calls!) – wbm1058 (talk) 17:08, 16 August 2023 (UTC)

Question about talk page blocks and protection

Hypothetical question I can't figure out: if an IP editor is blocked but has not had talk access revoked, and their user talk page is semiprotected, can they edit the page? It would be an unusual situation but I'm wondering what the actual answer is. Ivanvector (^Talk/_Edits) 16:26, 15 August 2023 (UTC)

They can't. The benefit to this is it will allow a longer term block without removing their talk page access for the whole time. ScottishFinnishRadish (talk) 16:30, 15 August 2023 (UTC)

Indeed. See User talk:47.22.21.38 for a non-hypothetical example. -- zzuuzz ^(talk) 16:38, 15 August 2023 (UTC)

If a page is semiprotected, why would an IP ever be able to edit it, regardless of whether it's theirs or they're blocked? (all non-hypothetical examples.) —Cryptic 16:41, 15 August 2023 (UTC)

How to add an academic thesis in Wikidata

I stumbled upon Peter Osborne (philosopher), whose infobox provides his thesis title and URL. I went to his Wikidata page and attempted to add the academic thesis there. Compared to Wikipedia, this page has a strange interface. I found "add statement" at the bottom of the page. I clicked on that, then entered "academic thesis" in the first field, then I entered "The carnival of philosophy : philosophy, politics and science in Hegel and Marx" (with and without a trailing period) and "publish" is grayed out. Then I added 1 Reference with reference URL "https://ethos.bl.uk/OrderDetails.do?uin=uk.bl.ethos.253269". "publish" is still grayed out. How do I get "publish" to be clickable? Do I have to first create the thesis in Wikidata as a separate entry before I can add it to this entry? —Anomalocaris (talk) 17:58, 15 August 2023 (UTC)

@Anomalocaris for a person in wikidata you can add that property academic thesis, but you have to link it to a thesis. For example here is one: wikidata:Q15212501, you can't just type in a name. — xaosflux ^Talk 18:09, 15 August 2023 (UTC)

So "yes" to your second question; the definition of that property is here: wikidata:Property:P1026. — xaosflux ^Talk 18:10, 15 August 2023 (UTC)

Xaosflux: In Wikidaata, I created a new item, The carnival of philosophy : philosophy, politics and science in Hegel and Marx. I tried to add properties, but I kept getting ! in a circle, and the root of the problem is that Wikidata thinks this item is in the wrong class, but there's no obvious way to change an item's class. Anomalocaris (talk) 18:37, 15 August 2023 (UTC)

@Anomalocaris  Works for me, go to Q7176244, add statement academic thesis, and put Q121477887 in there, publish. — xaosflux ^Talk 19:06, 15 August 2023 (UTC)

For more help on this, you may want to try wikidata:Wikidata:Report a technical problem. — xaosflux ^Talk 19:06, 15 August 2023 (UTC)

Xaosflux: Following those directions, after "put Q121477887 in there", there's ! in a circle next to the thesis name, and clicking on it shows "Values of academic thesis statements should be instances of one of the following classes (or of one of their subclasses), but The carnival of philosophy : philosophy, politics and science in Hegel and Marx currently isn't:" followed by a bulleted list that is variations on "thesis". Which is exactly what I said in my previous comment, the thesis entry is miscategorized as something other than a thesis and there's apparent way to to reclass it. —Anomalocaris (talk) 20:06, 15 August 2023 (UTC)

@Anomalocaris it looks like someone on wikidata fixed that. — xaosflux ^Talk 22:29, 15 August 2023 (UTC)

Graphs are temporarily unavailable due to technical issues

Any progress on this? Moxy- 02:08, 16 August 2023 (UTC)

See mw:Extension:Graph/Plans. Not yet. * Pppery * _{it has begun...} 02:10, 16 August 2023 (UTC)

Option to exclude drafts and templates from tracking categories?

I've been fixing citations in articles listed in Category:CS1 maint: numeric names: authors list. It would be nice to be able to exclude drafts and templates from that list. I won't go fixing citation issues in drafts, and it seems that no one else is doing that, either, as for many initial letters there are only drafts left. Templates have numerical parameters on purpose, so they don't belong in that list, either. It would be both more satisfying and easier to find articles in need of fixing if the drafts and templates could be excluded, either from the category entirely or from my view of its article list. Is that possible? Joriki (talk) 12:44, 16 August 2023 (UTC)

Help Talk:CS1 is the right venue for this discussion. You should be able to use petscan to limit your search of the category to article space. – Jonesey95 (talk) 13:50, 16 August 2023 (UTC)

You can also use User:PrimeHunter/Articles in category.js. On Category:CS1 maint: numeric names: authors list it produces Search articles and Not articles. PrimeHunter (talk) 15:12, 16 August 2023 (UTC)

I always wonder the same about Category:Pages with reference errors that has Wikipedia space and draft articles all mixed in, and Category:Pages with broken reference names (which is a subsection of the other category) that has all drafts etc separated out at the end. There's a lot of inconsistencies between different tracking categories. -- LCU ActivelyDisinterested ∆transmissions∆ °co-ords° 21:11, 16 August 2023 (UTC)

Category:Pages with reference errors and other categories at Special:TrackingCategories are added automatically by MediaWiki with no option to sort by namespace. Most of our tracking categories are template-added and this makes it possible to sort by namespace, or omit pages in some namespaces, although we don't always do it. PrimeHunter (talk) 23:18, 16 August 2023 (UTC)

Back in 2018 a change was made to the first category to exclude talk page, see Category talk:Pages with reference errors#Exclusion of user pages, but looking at that I did get the impression it involved changes to MediaWiki. -- LCU ActivelyDisinterested ∆transmissions∆ °co-ords° 11:11, 17 August 2023 (UTC)

Oh, I thought MediaWiki messages with category names like MediaWiki:Cite-tracking-category-cite-error had to be pure text but it allows wikitext. It's undocumented whether a message allows wikitext. That makes it a change local administrators can easily make. We could make subcategories for drafts, templates, project pages, a miscellaneous category, or whatever we want. I doubt sortkeys would be possible but I don't know how MediaWiki processes the message. It's possible that name|sortkey or name{{!}}sortkey would work. I see you have a suggestion at Category talk:Pages with reference errors#Draft, Wikipedia, Template, and Help. If you really want sortkeys to group other namespaces at the end like [4] instead of subcategories then I could make a test at testwiki: without interrupting Wikipedia. PrimeHunter (talk) 13:04, 17 August 2023 (UTC)

I think I followed that, yeah go ahead and let's see how it works on testwiki. -- LCU ActivelyDisinterested ∆transmissions∆ °co-ords° 23:34, 18 August 2023 (UTC)

Could someone report a bug for me?

Tracked in Phabricator
Task T344387

Could someone report a bug for me? As an IP I don't have access to phabricator.

The issue is that the __NONEWSECTIONLINK__ does not properly supress the "new section" tab on certain "action" pages, and that it is still possible to add new sections to the page using discussion tools.

Steps to reproduce:

1. Go to a page containing the __NONEWSECTIONLINK__ magic word, e.g. Talk:Hillary Clinton/April 2015 move request
2. Note that the "Add Topic" tab is correctly hidden in the top ribbon menu.
3. Click on one of the actions in the top ribbon, e.g. "edit", "history", "related changes", "page information"...
4. Note that the "Add Topic" button is incorrectly displayed in the top ribbon menu.
5. Clicking on the button starts the discussion tools new section dialogue

Thank you, 192.76.8.66 (talk) 16:27, 16 August 2023 (UTC)

phab:T344387 * Pppery * _{it has begun...} 22:41, 16 August 2023 (UTC)

That's not how pie charts are supposed to look...

Broken pie chart in question

Hello! I recently read this fascinating edition of the Signpost's Special Report on mobile, (shoutout to WereSpielChequers, the author of the atricle) and I noticed the pie chart was looking strange.

My user agent is Mozilla/5.0 (Android 13; Mobile; rv:109.0) Gecko/115.0 Firefox/115.0, using the Fennec browser on a OnePlus Nord 2 5G, if that is in any way relevant. --QuickQuokka ^{[⁠talk • contribs]} 22:27, 16 August 2023 (UTC)

 Works for me at Wikipedia:Wikipedia Signpost/2023-08-15/Special report. Firefox 116.0.2, Windows 10. --Redrose64 🌹 (talk) 22:33, 16 August 2023 (UTC)

@Redrose64: I didn't ask if it works for anybody else, I wanted to inform the devs of an error. QuickQuokka ^{[⁠talk • contribs]} 22:37, 16 August 2023 (UTC)

@QuickQuokka, Redrose is saying that this bug does not appear for everyone, which can help find its cause. — Qwerfjkltalk 13:14, 17 August 2023 (UTC)

This is a {{Pie chart}}, so that means the developers are your cohorts :). I am somewhat skeptical it can be fixed in a way which works for you and everyone else given what it's doing (Firefox for mobile is not a high-pageview browser). Izno (talk) 23:14, 16 August 2023 (UTC)

Call me a traditionalist, but nowadays I use a Chromebook, and I also have an antideluvian android mobile (now on Android version 10) that I bought second hand several years ago. Both show the pie chart with properly pie shaped slices. So it may just be the fennec browser? ϢereSpielChequers 07:08, 17 August 2023 (UTC)

Looking at the rendered html of that graph makes me want to cry. It's impressive as a hack, sure, but even if it is valid css, it's fragile and opaque; surely the Proper Way To Do This is an svg. —Cryptic 08:53, 17 August 2023 (UTC)

That would be good but then the chart would quickly become obsolete as it's much harder to update a diagram than some fairly clear wikitext. I know svg can be "easily" updated but a comparatively tiny number of editors would feel comfortable doing that and then going through the image upload procedure. Johnuniq (talk) 09:30, 17 August 2023 (UTC)

Today the colors would probably be done with conic-gradient. That's fairly new but should degrade more gracefully than this absolute mess of absolutes. About 0.5% of English Wikipedia page views would not support it (0.13% Chrome/Edge, 0.14% IE, 0.21% Safari). That's probably a reasonable percentage to try and improve things. Izno (talk) 17:34, 17 August 2023 (UTC)

Template problem

What could be the reason for the sudden display of "|work= ignored" in the "{{cite book}}" parameters? –MinisterOfReligion ^(Talk) 01:15, 17 August 2023 (UTC)

The instructions at Category:CS1 errors: unsupported parameter should help (follow the "help" link). See Help Talk:CS1 for discussion about Citation Style 1 templates. In this specific case, there is a good discussion at Trappist the monk's talk page, semi-unfortunately. – Jonesey95 (talk) 03:35, 17 August 2023 (UTC)

|url-status=unfit causes:

Script warning: One or more {{cite web}} templates have maintenance messages; messages may be hidden (help).

<ref>{{cite web|url=http://www.metrolyrics.com/1984-grammy-awards.html|archive-url=https://web.archive.org/web/20080613164619/http://www.metrolyrics.com/1984-grammy-awards.html|archive-date=2008-06-13|url-status=unfit |title=Grammy Awards |publisher=Metrolyrics |date=February 28, 1984 |access-date=April 29, 2009}}</ref>

.... 0mtwb9gd5wx (talk) 07:05, 17 August 2023 (UTC)

The Metrolyrics link isn't unfit, it's dead. Unfit is used when the original source has been taken over by a inappropriate site. There's very few uses where it's appropriate, the common one I see that is appropriate is atimes.com that used to be a news sources but now sells steriods. -- LCU ActivelyDisinterested ∆transmissions∆ °co-ords° 11:16, 17 August 2023 (UTC)

@Owais Al Qarni Why does your signature have to be bigger than anyone else's ? —TheDJ (talk • contribs) 19:44, 17 August 2023 (UTC)

How to avoid collapse template getting indented on t/p

During discussion pages usually I reply by clicking on reply link since that automatically selects requisite indenting. Problem comes when I use Collapse template {{collapse top|Reply with details 1}} .. {{collapse bottom}} in my own comment to keep discussion concise and easy navigable for other users. Indenting is automatically applied before collapse template too and there after subsequent text below {{collapse bottom}} also gets hidden / invisible until remove that extra indenting manually with another edit.

Many times my internet speed slows down or Wikipedia gives error of being busy for maintenance and it takes some time before I succeed in removing such unrequited indenting. (And I am experiencing internet speed problem just now too) And I am always worried some later users may misunderstand me.

Is there any way to update that collapse template so as later text will not become invisible even if indenting is there or any way around for me to avoid such difficult situation?

Bookku (talk) 06:53, 18 August 2023 (UTC)

There is no way to avoid the issues described today. Izno (talk) 19:38, 18 August 2023 (UTC)

Hamm okay shall live with that. Thanks for taking note and reply. Bookku (talk) 05:45, 19 August 2023 (UTC)

Recurrent memory leak

Something keeps leaking memory. It might be one of the scripts I'm using, but I'm not sure. Wikipedia tabs (to the exclusion of all others) inevitably glitch out when left sitting for a while and start using upwards of 1.5G of RAM. How can I find out what exactly is causing this? I'm on Vivaldi 6.1.3035.257, but this has been going on for months. 〜 Festucalex • talk 09:52, 18 August 2023 (UTC)

Does phab:T205127 describe your problem? Unfortunately it doesn't seem like there's been any success figuring out what's causing that. the wub "?!" 10:28, 18 August 2023 (UTC)

@The wub: Oh yes, that looks like it. Shame it's been open since 2018 (!) 〜 Festucalex • talk 11:19, 18 August 2023 (UTC)

Unless there's an endless loop in a user script or something, a script itself shouldn't cause a memory leak, in my opinion. It's my understanding that memory leaks are usually a problem with the browser's code. –Novem Linguae (talk) 01:03, 19 August 2023 (UTC)

Although they're not the same as a traditional memory leak, store gobblers can still occur with Javascript. (I do not know, though, if this is the case in this situation.) For example, a script could continually register new event listeners, thus consuming memory and hampering performance. isaacl (talk) 01:45, 19 August 2023 (UTC)

Not a webdev, but my understanding is that this became untenable after browser makers and web devs came to see the web as a "platform" which be as powerful as, and eventually supplant, a full desktop OS's native runtime environment (e.g. wasm, and recently WebGPU). When Apple changed Safari to auto-crash tabs that used too much memory, people complained that it broke mission-critical sites like Zoom, and even mundane stuff like Disney+, so Apple relented. DFlhb (talk) 10:08, 19 August 2023 (UTC)

Not sure what you are referring to by "this"? Memory leaks for long-running programs have always been seen as a problem to be solved (although the rate of increase will affect how the work gets prioritized). Store gobblers from a Javascript file served by a website can't be fixed by the browser vendor, so the browser can only balance protecting other tabs from being affected by interfering with the resources allocated to the problem-causing tab. isaacl (talk) 13:23, 19 August 2023 (UTC)

"This" = website memory leaks being automatically prevented by browsers. Browsers can't do that without preventing high resource use for legitimate, non-bug purposes. DFlhb (talk) 14:10, 19 August 2023 (UTC)

Thanks for the clarification. (I don't think Novem Linguae was referring to this scenario.) isaacl (talk) 14:15, 19 August 2023 (UTC)

MediaWiki:Gadget-CustomSideBarLinks.js

That's how it looks in Hebrew Wiki (it is in Swedish but never mind). press on the image to see it on full scale

Hello all.

For approximately 16 years (ever since 2007) Hebrew Wikipedia uses a Gadget calls "my links" (look here). It is quite a simple method which let every user to save their own custom side bar links (on the left side of the screen) and makes life much easier.

I ask you, if you approve, to translate this super-easy "pseudo-English" code into WP, as so it would be available for us.

I am here for any further questions.

Thanks in advance, Niles. Anderssøn79 🦔 (talk) 🦔 💛💙 11:55, 18 August 2023 (UTC)

here you may read the code, fully-translated, ready to move if it fits you. Anderssøn79 🦔 (talk) 🦔 💛💙 12:02, 18 August 2023 (UTC)

@Anderssøn79 a good start would be to translate w:he:שיחת מדיה ויקי:Gadget-CustomSideBarLinks, so that our users could read the directions. — xaosflux ^Talk 12:29, 18 August 2023 (UTC)

w:he:שיחת מדיה ויקי:Gadget-CustomSideBarLinks (translated)

The Gadget adds user custom links to a new section above the Community Section (on the left side of the screen). how to use it After one approves “adding user custom links” in the Gadget section inside the Settings, one needs to create “User:<user name> /My links” (i.e. User:Anderssøn79/My links). In order to add a link, one needs to add a new line starting with a “dot/star” (*) and then write down the ref (just as regular [[Page|Alias]] or [URL Alias]). i.e WPVP "Google". My sandbox

Thank you, merged to Wikipedia:CustomSideBarLinks. — xaosflux ^Talk 14:01, 18 August 2023 (UTC)

@xaosflux I think it should be moved to the Talk section, and does it mean I may copy the code to the main page (and make it work)? Anderssøn79 🦔 (talk) 🦔 💛💙 15:34, 18 August 2023 (UTC)

@Anderssøn79 we generally document our gadgets in the project namespace here. The mediawiki talk:x.js pages are primarily redirected to the project talk, or only really used for edit requests. — xaosflux ^Talk 15:57, 18 August 2023 (UTC)

Okay, thanks. So where do we put the actual code and make it available for users? Anderssøn79 🦔 (talk) 🦔 💛💙 16:11, 18 August 2023 (UTC)

Fixing date formats?

Is there some tool which can find all instances of dates in an article and convert them all to a uniform format? For example 2023-08-18 > August 18, 2023? RoySmith (talk) 18:17, 18 August 2023 (UTC)

User:Ohconfucius/script/MOSNUM dates. Izno (talk) 19:34, 18 August 2023 (UTC)

An excellent tool, but beware that it likes to insert {{Use mdy dates}} above {{short description}} so they need to be swapped manually. Certes (talk) 19:51, 18 August 2023 (UTC)

I'm confused by this note in the docs: "Functions converting dates within citation templates has been withdrawn now that WM software engine renders date formats automatically". Fixing the dates in citation templates is exactly what I need this for. So what am I doing wrong that the "WM software engine" isn't rendering things correctly for me? This came up in Talk:Bronx County Bird Club/GA1, and I just went and fixed all the dates manually. Was that not the right thing to do? RoySmith (talk) 19:56, 18 August 2023 (UTC)

WM software engine no such thing. The citation templates will format publication, archive, and access dates according to the presence of {{use dmy dates}} or {{use mdy dates}} neither of which were in Bronx County Bird Club when I looked. That functionality in the cs1|2 templates is there so that no one has to fuss with date style in the template wiki text. See the template documentation for the {{use xxx dates}} for more detail.

—Trappist the monk (talk) 20:05, 18 August 2023 (UTC)

When I've used dates.js, it's formatted all dates, including those within citation templates. I don't recall what combination of existing "use...dates" tags and CS1/2 formats those articles used. I even had to undo the formatting on a couple of dates within URLs to avoid breaking them. Certes (talk) 20:09, 18 August 2023 (UTC)

Oh, my, so I've really made a hash of this then? What I really wanted to do was leave the dates in yyyy-mm-dd format (as the citation tool generated them) in the citation and add {{use dmy dates}} to the top to get them to render the way I wanted them? RoySmith (talk) 20:16, 18 August 2023 (UTC)

From memory there is a function that will leave dates in citations alone. Izno (talk) 20:29, 18 August 2023 (UTC)

RoySmith, that is usually the easiest way to fix the rendering a bunch of dates within citation templates. It works only when editing the entire page. Definitely proofread the output for outliers and errors. – Jonesey95 (talk) 20:38, 18 August 2023 (UTC)

Where can I write the original pronunciation of a surname?

I noticed some pages (Lionel Messi, Javier Mascherano) do not sport the original Italian pronunciation of the persons' surnames anymore. Is there a guideline about where to write the original surname pronunciation? On Wikidata perhaps? In Elias Lönnrot I wrote it in a footnote.-- Carnby (talk) 19:33, 18 August 2023 (UTC)

@Carnby: does anything here in Wikipedia:Manual of Style/Pronunciation help you? As far as wikidata goes, you can store multiple P898 and P443 properites for an item. — xaosflux ^Talk 20:29, 18 August 2023 (UTC)

@Xaosflux Honestly, I can't find anything about non-English names originating in a different country, such as Messi, Mascherano, Di María, Bergoglio, Milei (Argentine people of Italian descent), Antetokounmpo (Greek person of Yoruba descent), Lönnrot (Finnish person of Swedish descent)...-- Carnby (talk) 21:07, 18 August 2023 (UTC)

That's not a technical question. I tend to find it unnecessary unless the subject has strong ties to the "original" language (they're fluent in it, they're a first-gen immigrant, etc.). Nardog (talk) 01:43, 19 August 2023 (UTC)

I decided to store the original pronunciation(s) on Wikidata.-- Carnby (talk) 08:59, 19 August 2023 (UTC)

#:~:text= in Links from Google search results

• #:~:text= on en.wikipedia.org
• the text that follows is not part of the URL and identifies the User
• this occurs in google books citations also, but different NAME=VALUE pairs
• .... 0mtwb9gd5wx (talk) 00:13, 19 August 2023 (UTC)

  automated cleanup ? .... 0mtwb9gd5wx (talk) 00:15, 19 August 2023 (UTC)

  That search query has some false positives. The first entry I found with #:~: is here, but that one seems fine. It doesn't seem to identify the user. Got any other examples? Are you requesting help to clean these up? –Novem Linguae (talk) 01:15, 19 August 2023 (UTC)

  The purpose of this is not to identify users (although I suppose that may be possible?) - rather, it's to link to a specific piece of text on a page. (That said, it is one of those things that Google kind of unilaterally decided to add to Chrome, with varying lack of support across other browsers.) LittlePuppers (talk) 01:30, 19 August 2023 (UTC)

  Template:Citation Style documentation#url says to omit tracking parameters but I wouldn't call this a tracking parameter, and it also says "the link may point to the specific page(s) referenced". I think that mainly refers to PDF files where it's possible to give a page number in the link. Do we have a guideline saying to omit Google's text= in cases where supported browsers will jump directly to the part of the page being used in a reference? I guess nearly all cases where text= was left is just users who clicked a Google link and copied the full url without knowing the meaning, but a guideline could lead to more cleanup where it's removed. PrimeHunter (talk) 08:59, 19 August 2023 (UTC)

  Noticeably this is not supported by Firefox but is supported by Safari. Aaron Liu (talk) 16:05, 19 August 2023 (UTC)

Keyboard Shortcuts

Is there a way to change one's personal keyboard shortcuts? -Proxima Centari (talk) 00:19, 20 August 2023 (UTC)

@Proxima Centari: This page is as close as I can find. LittlePuppers (talk) 00:41, 20 August 2023 (UTC)

Thanks! -Proxima Centari (talk) 00:43, 20 August 2023 (UTC)