Wikipedia talk:WikiProject Redirect

This is the talk page for discussing WikiProject Redirect and anything related to its purposes and tasks.

Put new text under old text. Click here to start a new topic.
New to Wikipedia? Welcome! Learn to edit; get help.

Shortcut

WT:REWT:RE

Archives (index): 1, 2, 3, 4, 5, 6, 7: 4 months

Redirect

This page is within the scope of WikiProject Redirect, a collaborative effort to improve the standard of redirects and their categorization on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.
Note: This banner should be placed on the talk pages of project, template and category pages that exist and operate to maintain redirects.
This banner is not designed to be placed on the talk pages of most redirects and almost never on the talk pages of mainspace redirects. For more information see the template documentation.RedirectWikipedia:WikiProject RedirectTemplate:WikiProject Redirectredirect

This is the talk page for WikiProject Redirect. Please feel free to create a sub-page in order to branch out from this page if you wish to create a new proposal. If you do so, please leave a comment here so that other editors know of its existence!

Discussion at Wikipedia:Templates for discussion/Log/2025 May 26 § Template:R from non-preferred capitalisation

You are invited to join the discussion at Wikipedia:Templates for discussion/Log/2025 May 26 § Template:R from non-preferred capitalisation. Hey man im josh (talk) 15:35, 26 May 2025 (UTC)[reply]

Requested move at Talk:Chinese language#Requested move 20 June 2025

An editor has requested that Chinese language be moved to Chinese languages, which may be of interest to this WikiProject. You are invited to participate in the move discussion. Pineapple Storage (talk) 21:10, 24 June 2025 (UTC)[reply]

Proposed move of Bahamian Creole to Bahamian DialectBahamian Dialect

You are invited to join the discussion at Talk:Bahamian Creole § Page move proposed. The discussion concerns a proposal to move Bahamian Creole to Bahamian DialectBahamian Dialect, which currently redirects to Bahamian Creole. Outside opinions will be very much appreciated. Thank you in advance! Pineapple Storage (talk) 12:50, 31 August 2025 (UTC) Pineapple Storage (talk) 12:50, 31 August 2025 (UTC)[reply]

Redirects to/from ampersands

I've noticed that there seems to be a lack of specific RCATs to cover redirects to and from titles that use "&" or spell out "and". For instance, AT and TAT and T currently has {{R from alternative spelling}} (along with a notice that a more specific category may be available), Hale & PaceHale & Pace has {{R from alternative punctuation}} (even though an ampersand isn't punctuation), and redirects such as Marks and SpencerMarks and Spencer, Tiffany and Co.Tiffany and Co., Hootie and the BlowfishHootie and the Blowfish, Key and PeeleKey and Peele etc. are uncategorised. Template:R from ampersand and Template:R from &Template:R from & currently redirect to Template:R from railroad name with ampersand, which would be inaccurate if used on non–railway-related redirects such as Vic & BobVic & Bob, Cannon & BallCannon & Ball, Eli Lilly & CompanyEli Lilly & Company, etc. Template:R to ampersand and Template:R to &Template:R to & don't currently exist.

I just created Audie Award for Literary Fiction and Classics, and I was looking for relevant rcat templates to use; I considered using {{R to ligature}}, but the ampersand is a logogram rather than a ligature (according to Ligature (writing)#Symbols originating as ligatures, Because of its ubiquity, it is generally no longer considered a ligature, but a logogram.) so redirects from "&" to "and" (and vice versa) would be out-of-place in Category:Redirects from titles with/without ligatures.

I'm interested to hear what people think about the possibility of creating {{R to ampersand}}/{{R to &}}, and repurposing {{R from ampersand}}/{{R from &}} for use with non–railway-related redirects (while leaving Category:Redirects from railroad names with ampersands as a subcategory of Category:Redirects from titles with ampersands, which would itself be a subcategory of Category:Redirects from modifications and/or Category:Redirects from alternative spellings). Pineapple Storage (talk) 13:25, 2 September 2025 (UTC)[reply]

That all seems like a very good idea to me, but I'll do my usual ping of Paine Ellsworth who I regard as more expert than me when it comes to redirect categorisations. Thryduulf (talk) 14:27, 2 September 2025 (UTC)[reply]

Seems like a good idea to me too. May as well also ping @NE2 who created the redirects to Template:R from railroad name with ampersand and is still active. Anomie ⚔ 15:48, 2 September 2025 (UTC)[reply]

I recommend creating {{R from logogram}} and {{R to logogram}} as well}, with Category:Redirects to titles with logograms and Category:Redirects from titles with logograms subcategories of appropriate broader categories. -- Shmuel (Seymour J.) Metz Username:Chatul (talk) 16:06, 2 September 2025 (UTC)[reply]

I considered suggesting this, but I couldn't actually think of any other logograms that are used in English. Now that I've given it a bit more thought, maybe @ would count, and potentially currency symbols, but I don't know whether this is supported by sources. Are there any other logograms I'm missing? I think ampersands would probably make up the majority of uses, in any case. Pineapple Storage (talk) 17:26, 2 September 2025 (UTC)[reply]

"Logogram" seems a lot more difficult to remember than "ampersand" when dealing with a "&". -- Beland (talk) 07:05, 6 September 2025 (UTC)[reply]

There's nothing in the proposal that requires you to remembr the word; yould be using the ampersand templates, not the logogram templates. -- Shmuel (Seymour J.) Metz Username:Chatul (talk) 12:07, 8 September 2025 (UTC)[reply]

Then what would logogram be used for? -- Beland (talk) 21:48, 8 September 2025 (UTC)[reply]

Presumably you'd use it for logograms other than the ampersand. For example, it could be added to Chinese character redirects like ㆖. Warudo (talk) 22:07, 8 September 2025 (UTC)[reply]

My understanding was that redirects where the title is a single character, like ㆖, @ or even & itself, use {{R from Unicode character}} (and therefore Category:Redirects from Unicode characters). {{R from ampersand}}/{{R to ampersand}} and {{R from logogram}}/{{R to logogram}} are for when those characters are part of the title, and can be substituted for a spelled-out word (for instance AT and T redirecting to AT&T, or Vic & Bob to Vic and Bob). So the ampersand/logogram categories are for when the characters are used in the title, and {{R from Unicode character}} when the character itself is the title of the redirect. Have I got this wrong? I'm not very familiar with rcats etc., but this is how I've interpreted it so far. Pineapple Storage (talk) 23:50, 8 September 2025 (UTC)[reply]

So yeah, it makes sense to clean up ampersands so the templates aren't weirdly assuming articles are about railroads. "Logogram" does sound related enough to use for Chinese characters, but I'm not sure we'd actually need either from or to templates for that.

I agree {{R from Unicode character}} is probably sufficient for single-character titles. We use English-language names for article titles, or at the very least romanizations, so there shouldn't be any logograms in the titles of non-redirect articles.

Where we redirect from a whole word or phrase in a non-alphabetic writing system, presumably we would use {{R from alternative language}}? Sometimes non-Latin writing systems use logograms but sometimes they use alphabetic letters, like kana, or syllabic systems like hangul. I'm not sure it's all that useful to distinguish what kind of writing system is being used given that we already distinguish which language is being used. We also have {{R to ASCII-only}} to cover non-words.

Category:Redirects from titles without logograms and Category:Redirects from titles with logograms are empty except for the ampersand subcategories; I think these should probably be deleted after re-homing. -- Beland (talk) 03:00, 9 September 2025 (UTC)[reply]

Here are some disorganised thoughts from me: (feel free to collapse if this is unhelpful)

For non-English logograms, I feel like (for instance) Category:Redirects from Chinese characters (as a more specific subcategory within Category:Redirects from Chinese-language terms, which currently includes both titles written in Chinese characters and romanizations) would probably be more useful than grouping them in subcategories of Category:Redirects from titles with logograms.

Because of the lack of a list generated by (for instance) {{R from @}}/{{R to @}}, I'm having trouble finding many pages (other than @ sign and @ symbol, which are both currently uncategorised) that contain "@" but aren't just @. (Is it possible the WP:Search syntax doesn't pick up that character for some reason? It's not a WP:FORBIDDEN character...) By following links from At sign, it seems there are a few Locus (genetics)-related articles that use it (some or all are in Category:Human genes), such as IGL@; in theory, if we could establish that @ is a logogram, then either {{R to @}}/{{R to at sign}} or {{R to logogram}} could be used for redirects to these articles. Similarly, if it were established that ♯ and ♭ are logograms, then redirects like G♯ major (whose target is G-sharp major) could maybe have {{R from logogram}}.

In researching this comment, I've realised that the situation is complicated by Ideograms... According to that article, ideograms are symbols that don't have one specific phonetic reading, and logograms are symbols that do. By that definition alone, I think &, @, ♯ and ♭ could be classified as logograms (as their "pronunciations" are 'and', 'at', 'sharp' and 'flat' respectively). However, if we can't agree on a specific set of characters that count as logograms used in English (ie. where Category:Redirects from non-English-language terms—or more specific subcategories like Chinese characters—wouldn't be relevant), then "logogram"-based rcats feel like a bit of a can of worms. Pineapple Storage (talk) 08:38, 9 September 2025 (UTC)[reply]

Just a small correction, if Category:Redirects from Chinese characters were to be made, it could not be a subcategory of Category:Redirects from Chinese-language terms because Japanese and Korean also use Chinese characters. These are called kanji and hanja respectively. Warudo (talk) 09:09, 9 September 2025 (UTC)[reply]

You make a good point. I guess it would be too clunky to have kanji, hanja and (for instance) hanzi be subcategories of Japanese-language, Korean-language and Chinese-language terms... So Category:Redirects from Chinese characters as its own subcategory of Category:Redirects from non-English-language terms then? Pineapple Storage (talk) 09:25, 9 September 2025 (UTC)[reply]

(To be clear, I think pages in Category:Redirects from Chinese characters should also each have a language category, ie. Japanese-language, Korean-language or Chinese-language terms, as appropriate.) Pineapple Storage (talk) 09:31, 9 September 2025 (UTC)[reply]

I also think it would be too clunky, especially if you consider that hanzi would almost certainly need to be split into traditional Chinese and simplified Chinese categories. We should just put all Chinese character redirects in one category just like Category:Disambiguation pages with Chinese character titles does for dab pages. Warudo (talk) 10:07, 9 September 2025 (UTC)[reply]

Then again, having a traditional and a simplified Chinese rcat might be useful for editors who want to keep them in sync. Perhaps an {{R from traditional Chinese}}/{{R from simplified Chinese}} pair would be useful (but now I'm getting really off-topic). Warudo (talk) 10:09, 9 September 2025 (UTC)[reply]

You're right, this would be a good idea—but a separate discussion is probably needed! :) Pineapple Storage (talk) 10:21, 9 September 2025 (UTC)[reply]

As of the August 20 database dump, there are 1989 mainspace pages with "@" in the title. Not all of these are pronounced "at". For example:

-- Beland (talk) 11:27, 9 September 2025 (UTC)[reply]

Thank you for listing these, this certainly gives us some further data points to consider! Most of those would be pronounced as "at" (3D@Home Consortium, 3 @ 3, @-mention, @AerLingus, @ladygaga, LHC@Home, כהן@מושון, なあ坊豆腐@那奈), but my gut feeling is that R@dio Barça would be more Category:Redirects from stylizations, and I wouldn't know where to start in terms of categorising $@!% and ^@... Maybe {{R to technical name}}? Pineapple Storage (talk) 14:02, 9 September 2025 (UTC)[reply]

Many of these are covered by {{R from Twitter username}}. $@!% seems like {{R from alternate name}} for Grawlix and ^@ the same for null character. Redirects that simply point to a version of the title where "@" is spelled "at" might form a coherent group, but I don't think all redirects with "@" in them actually do. If anyone needs a list of such, they can simply search the database. But redirect tags seems to mostly be used to make semantic categories rather than typographic ones. For example, it's useful to know if a redirect represents an incorrectly spelled word or a non-English word or a Twitter username when automatically deciding whether or not it is printworthy or should be ignored by an English spell-checker. -- Beland (talk) 14:25, 9 September 2025 (UTC)[reply]

This all makes sense! Pineapple Storage (talk) 15:34, 9 September 2025 (UTC)[reply]

@Beland Sorry if this is an obvious question but how/where did you make that search? Pineapple Storage (talk) 14:06, 9 September 2025 (UTC)[reply]

I happen to have preprocessed copies of recent database dumps on local disk because I run code for the moss project, including a list of all mainspace titles. You can also try to use the live search engine to look for these pages with intitle:/\@/, but unfortunately the search takes too long and times out before giving complete results. I'm happy to send a full list if anyone needs one. -- Beland (talk) 14:28, 9 September 2025 (UTC)[reply]

Ah okay! No worries, thank you for explaining. Pineapple Storage (talk) 15:29, 9 September 2025 (UTC)[reply]

You can also use quarry: if you're familiar with SQL. — Qwerfjkl talk 12:38, 11 September 2025 (UTC)[reply]

Per my suggestion, I nominated both logogram redirect categories for deletion. See Wikipedia:Categories for discussion/Log/2025 September 16. -- Beland (talk) 20:18, 16 September 2025 (UTC)[reply]

{{R from ampersand}}/{{R to ampersand}} and {{R from logogram}}/{{R to logogram}} are for when those characters are part of the title, and can be substituted for a spelled-out word (for instance AT and T redirecting to AT&T, or Vic & Bob to Vic and Bob). After thinking about this more, I realised that this argument ignores that, unlike wikt:@ and wikt:&, Chinese characters like wikt:上 are spelled-out words already. Consider 町 which targets List of towns in Japan. This character, wikt:町, is the word for town in Japanese. So in my opinion it should be tagged as both {{R from Unicode character}} and as {{R from logogram}} or {{R from Chinese character}}. Warudo (talk) 11:17, 9 September 2025 (UTC)[reply]

Apologies, I think my original wording might have been a bit ambiguous, and there may have been some crossed wires.

Firstly, in my comment above, the ㆖ isn't 上, but a character from the Kanbun (Unicode block) which indicate reading order (see also Kanbun#Terminology). I don't know whether Kanbun have a phonetic reading or whether they're purely visual markers (I don't know much about Japanese unfortunately!), so now that I'm aware of the issue of distinguishing between logograms and ideograms (see above), I actually have no idea whether or not they're technically logograms; the only reason I linked it in my previous comment was because @Warudo had given it as an example.

What I meant by when those characters are part of the title, and can be substituted for a spelled-out word and is "when the logogram in question isn't the whole title, and that logogram by itself can either be spelled out or not". (By spelled out, I mean phonetically using Latin script, because it's the main script in use on the English Wikipedia; when discussing Chinese characters specifically—which wasn't the case above—the more accurate term would obviously be "romanized".)

For example, 町 is the whole title, and can be romanized as Machi; you might also see this word in titles like 日本町 or Nihonmachi. However, (AFAIK) you're unlikely to see it in a redirect title like Nihon町 or Nihon 町. It isn't common (again, AFAIK) to drop a certain character in the middle of a romanized term; because of this, the distinction between the titles in this case isn't "logogram or no logogram", it's "Chinese characters or romanization", in which case the fact that Chinese characters are logograms isn't as relevant as the fact that it's a non-Latin script.

Meanwhile, with an ampersand, you are likely to see it interspersed with non-logograms in titles; often, the use of an ampersand or the word "and" is largely unpredictable (why is Key & Peele the common name but Jake and Amir is also the common name?), which is why the important distinction is "logogram or no logogram" in that case.

I don't think this explanation is very helpful, because in all honesty, I think I'm more confused now than I was at the beginning of this discussion... But can you see roughly what I mean? Pineapple Storage (talk) 13:38, 9 September 2025 (UTC)[reply]

A crude search on zhwiki and jawiki suggests that mixing Latin characters and Han characters is not as rare as you think it is. Warudo (talk) 14:31, 9 September 2025 (UTC)[reply]

Okay, but how common is it on enwiki? If it is a frequent format for redirect titles on this wiki—such that it needs its own rcat etc.—then fair enough, I'm not going to question that! As I have said, I don't know a lot about any of this. Pineapple Storage (talk) 15:27, 9 September 2025 (UTC)[reply]

I searched the August 20 database dump, and found 2163 titles where English letters (A-Z) are mixed with Unicode characters with class "Lo" which are described as "other letters, including syllables and ideographs". Examples:

Some of these redirect to non-English titles (like the Brazilian football article) with different typography. Many are mixed English/non-English redirecting to English, which would fit {{R to English}}. I see we have Category:Templates for redirects involving diacritics or language change where any new templates to handle character weirdness might belong. Maybe including ampersands? -- Beland (talk) 15:35, 9 September 2025 (UTC)[reply]

{{R from ampersand}}/{{R to ampersand}} and {{R from logogram}}/{{R to logogram}} are for when those characters are part of the title, and can be substituted for a spelled-out word. This makes sense to me. It is similar to {{R from diacritic}} which is short for Category:Redirects from titles with diacritics. Thus, to/from diacritic and to/from ampersand does not indicate that the diacritic or ampersand is the only glyph in the redirect, rather that it is a defining part. The rule of thumb that it can be substituted for a spelled-out word sounds right, though I haven't thought through every possible exception. Beland's comment about Rcats being semantic categories and not purely typographical is a nice way to think about this. --MYCETEAE 🍄‍🟫—talk 21:36, 10 September 2025 (UTC)[reply]

I agree this is a good idea. --MYCETEAE 🍄‍🟫—talk 21:53, 4 September 2025 (UTC)[reply]

@Thryduulf @Anomie @Chatul @Myceteae @Paine Ellsworth @NE2

Thank you for the feedback, it looks like there's general agreement that this is a good idea. What do people think about where Category:Redirects from titles with/without ampersands should be categorised? I think they come under Category:Redirects from modifications, but are there more specific subcategories that should be used as well/instead? For instance, it kind of feels like Category:Redirects from alternative spellings might be an option. Does anyone have any thoughts on this? Pineapple Storage (talk) 09:24, 5 September 2025 (UTC)[reply]

Category:Redirects from modifications looks more appropriate than spellings. Although technically, as I learned from this thread, these are more accurately a subcategory of R from logogram. I'm pretty new to thinking about Rcats so I'm curious what others think. --MYCETEAE 🍄‍🟫—talk 15:30, 5 September 2025 (UTC)[reply]

I would say that redirects to/from any of !, @, #, $, ¢, £, &, *, =, + or -, if they are defined, should be subcategories of logograms. -- ~ ~— Preceding unsigned comment added by Chatul (talk • contribs) 12:40, 16 September 2025 (UTC)[reply]

I hadn't thought this would touch on any of my areas of interest, but with + and - mentioned, that brings to mind × (multiplication symbol) used in the names of hybrid plants. There are a bunch of redirects for hybrid plants that use the letter x instead of ×, that don't have any rcat that seems relevant to me. Would Musa x paradisiaca->Musa × paradisiaca be an "R to logogram"? Plantdrew (talk) 15:53, 16 September 2025 (UTC)[reply]

I think a "logogram" is referring to the case where the symbol stands for a word or part of the word, not just a stylized letter. So "Foo × bar" ↔ "Foo times bar" or "Foo cross bar" would be an R to/from a logogram, while "Foo × bar" ↔ "Foo x bar" would be {{R from ASCII-only}} or {{R to ASCII-only}} instead. Similarly, something like Ke$ha → Kesha wouldn't be a logogram, it's correctly tagged as-is with {{R from stylization}}. Things like "@kins" ↔ "Atkins" and "¼maine" → "Quartermaine" would be similar logogram redirects. Anomie ⚔ 17:10, 16 September 2025 (UTC)[reply]

They do stand for words

! - Excalmation
@ - At
# - Pound, Number
$ - Dollars
¢ - Cents
£ - Pound
& - And
* - Times
× - Times
= - Equals
+ - Plus
- - Minus

There might be some ambiguity about * and ×, as they have other uses. For all of these, the category should depend on the use, e.g., K@$h@ → Kasha would be stylized but C@ → Cat would be logogram. -- Shmuel (Seymour J.) Metz Username:Chatul (talk) 18:05, 16 September 2025 (UTC)[reply]

I would disagree with ! in the sense of "exclamation", because when it's used as an exclamation mark it's punctuation (rather than a literal substitute for the word "exclamation"), so {{R from alternative punctuation}} would apply. It's more like a logogram in its other uses such as n! and 0! (both redirects currently uncategorised), where it stands for the word "factorial".

While we're on the subject, is it worth mentioning {{R from mathematical symbol}}? How does that fit into the equation?^[a] Pineapple Storage (talk) 18:42, 16 September 2025 (UTC) Pineapple Storage (talk) 18:42, 16 September 2025 (UTC)[reply]

Also, I think the example of "C@" as a substitute for "cat" is probably {{R from stylization}} in most cases (even if it's {{R from logogram}} as well, which I'm not sure about...) Pineapple Storage (talk) 18:46, 16 September 2025 (UTC)[reply]

Thanks again for the ping, editor Thryduulf! These all sound like good ideas with just a few wrinkles to be ironed out. Sometimes we don't realize that when we create rcat templates and their associated categories, someone has to monitor those categories. And that can take up a significant amount of an editor's time. It's a commitment. So we ask ourselves, 'How important is it that we keep track of this particular type of redirect?' And then go from there. Thank you all very much for your contributions and your dedication to this reference work! P.I. Ellsworth , ed. – welcome! – 15:38, 8 September 2025 (UTC)[reply]

References

^ Pun acknowledged but not originally intended :)

Help clean up {{R to related}} redirects before it's deleted ⚠️

Hi there, could you kindly assist cleaning up the 1,000 transclusion of {{R to related}} since it's getting deleted by TfD? Convert to {{R from related word}} or {{R to related topic}} or other appropriate rcat template.

Thanks! waddie96 ★ (talk) 01:49, 5 September 2025 (UTC)[reply]

Requested move at Talk:Etats-Unis § Requested move 7 October 2025

An editor has requested that Etats-Unis be moved to another page, which may be of interest to this WikiProject. You are invited to participate in the move discussion. --MYCETEAE 🍄‍🟫—talk 23:34, 7 October 2025 (UTC)[reply]

Note: Etats-Unis and États-Unis have been the subject of three prior RfD discussions and the RM proposal includes suggested primary redirects. Thus, this may be of interest to members of this project and would benefit from your input. --MYCETEAE 🍄‍🟫—talk 23:36, 7 October 2025 (UTC)[reply]

Discussion at Template talk:R from drug trade name § Generic or nonproprietary name instead of INN

You are invited to join the discussion at Template talk:R from drug trade name § Generic or nonproprietary name instead of INN. —Myceteae‍🍄‍🟫‍(talk) 03:45, 19 October 2025 (UTC)[reply]

This concerns a proposal to change the wording that appears when {{R from drug trade name}} is used. —Myceteae‍🍄‍🟫‍(talk) 03:45, 19 October 2025 (UTC)[reply]

Question at Wikipedia:Village pump (miscellaneous)/Archive 85#Redirects tagged for RfD but not put up for discussion

I responded to the editor's question at Wikipedia:Village pump (miscellaneous)/Archive 85#Redirects tagged for RfD but not put up for discussion. I have not encountered this before and I think it would benefit from input from those with more RfD experience. —Myceteae‍🍄‍🟫 (talk) 21:18, 30 October 2025 (UTC)[reply]

Pageviews ("stats") link broken at WP:RFD

Tracked in Phabricator
Task T409493

At RFD, the "stats" link to pageviews is broken. I don't recall if I first noticed this yesterday or this morning. I assumed the site was down and moved on the first time but upon further investigation the site is up so the error appears to originate from how the URL is formatted in the template. For example, at Wikipedia:Redirects for discussion/Log/2025 November 6#Twisted Metal PS3 (working title) the stats link opens this error page but I was able to access the pageviews stats here. I spot checked a few listings going back to Nov 1 and they all produced the same error but I'm pretty sure the error is newer than that or would have been noticed sooner. I'm not sure how the RfD page template is managed but I'm hoping this is the right place to report this issue. —Myceteae‍🍄‍🟫 (talk) 20:48, 6 November 2025 (UTC)[reply]

This logic comes from Module:PageLinks, which hasn't been changed in years and in this regard doesn't depend on anything that's been changed recently. Let's try something... a link long enough that it trips the bit where PageLinks uses an external link instead of a toolforge: one.

012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234 → whatever (talk · links · history · stats) [ Closure: keep/retarget/delete ]
Mmmkay, yeah, as expected, that works alright. So my guess is that something changed recently in how Toolforge handles inbound links containing URL parameters, where it's now escaping the question marks and ampersands, breaking things. I'll file a Phab task. -- Tamzin^{[cetacean needed]} (they|xe|🤷) 20:59, 6 November 2025 (UTC)[reply]

Note: In the meantime this can be patched by having PageLinks just use an external link always, which I can do in the morning when I trust myself not to break 70k pages more than they're already broken, but maybe that's the sort of thing a newer and awaker admin like Chaotic Enby would like to hotfix. -- Tamzin^{[cetacean needed]} (they|xe|🤷) 21:13, 6 November 2025 (UTC)[reply]

Got it, looking at it! Chaotic Enby (talk · contribs) 21:14, 6 November 2025 (UTC)[reply]

Done. Should work now, except that {{Page-multi}} is substituted (not transcluded) on that page so existing links won't be affected by the hotfix. Chaotic Enby (talk · contribs) 21:24, 6 November 2025 (UTC)[reply]

Sweet! I will check the stats link when I see a new listing and let you know if there are any issues. Thank you both for your attention to this! —Myceteae‍🍄‍🟫 (talk) 22:28, 6 November 2025 (UTC)[reply]

The link works as expected in the new listings. Thanks again! @Chaotic Enby @Tamzin 😊 —Myceteae‍🍄‍🟫 (talk) 03:30, 7 November 2025 (UTC)[reply]

Speaking of, does anyone know if the double question mark in the generated URL is intentional? I don't want to remove it as it seems to work fine and I prefer not to take the risk, but just curious. Chaotic Enby (talk · contribs) 07:27, 7 November 2025 (UTC)[reply]

Yeah I think that's just my mistake from when setting up the >255-char special case, which was never noticed because it's such a rare case. I noticed it last night and figured it was harmless, but actually, looks like it was eating the start param, which per [1] seems to be because the param got traeted as ?start. I've removed the second question mark in the module, which should fix it. -- Tamzin^{[cetacean needed]} (they|xe|🤷) 07:35, 7 November 2025 (UTC)[reply]

Oh, that makes sense, thanks a lot! Chaotic Enby (talk · contribs) 07:40, 7 November 2025 (UTC)[reply]

Discussion at Wikipedia:Templates for discussion/Log/2025 November 5 § Redirect comics templates

You are invited to join the discussion at Wikipedia:Templates for discussion/Log/2025 November 5 § Redirect comics templates. PK2 (talk; contributions) 00:21, 9 November 2025 (UTC)[reply]

Discussion at Wikipedia:Redirects for discussion/Log/2025 November 14 § Lower Frisian

You are invited to join the discussion at Wikipedia:Redirects for discussion/Log/2025 November 14 § Lower Frisian. PK2 (talk; contributions) 10:12, 14 November 2025 (UTC)[reply]

[1] Pun acknowledged but not originally intended :)

[a]