From Wikipedia, the free encyclopedia
Content deleted Content added
|
 |
|||
| Line 50: | Line 50: | ||
|
=== AFCH creates DEFAULTSORT conflicts, adds duplicate categories === |
=== AFCH creates DEFAULTSORT conflicts, adds duplicate categories === |
||
|
I’ve seen this happen a number of times previously. |
|||
|
* 2025-12-03 [[special:diff/1325482849]] |
* 2025-12-03 [[special:diff/1325482849]] |
||
|
:* added {{code|{{((}}DEFAULTSORT:Wooley, John C.{{))}}|lang=wikitext}} despite :{{code|{{((}}DEFAULTSORT:Wooley, John Culver{{))}}|lang=wikitext}} already existing |
:* added {{code|{{((}}DEFAULTSORT:Wooley, John C.{{))}}|lang=wikitext}} despite :{{code|{{((}}DEFAULTSORT:Wooley, John Culver{{))}}|lang=wikitext}} already existing |
||
Latest revision as of 16:40, 3 December 2025
- 2025-02-11 Kek626 registered in 2006 and has been active for almost 19 years now, at a rate of ~3.5 edits/year. No edits in 2010, 2013, 2020, 2022-2024.
- 2025-09-26 Tropicalgeek registered in 2009, did two edits in 2013, one in 2015, one in 2023, then did 30 edits drafting Draft:Stephen Robert Lloyd in the past 24 hours.
Template preview script
[edit]
- Parking this here for the time being.
- 2025-08-26 (couple of weeks previously) using the
classattribute of aspanelement for semantic markup may not be optimal. Shouldn’t this be done be defining custom XML/HTML tags?- 2025-09-09 Custom (HTML5) elements: begin with a letter, must contain a “-” hypen minus. Currently not allowed.
- 2025-08-26 Semantic markup: “pajeet” was italicized in the lead, which I interpreted as a WP:FOREIGNITALIC and removed, as the word is English. I then realized that it might have been a case of MOS:WORDSASWORDS, and added quotes instead. That’s why we need semantic markup.
- heading for RfC, clearly
What to do in cases where a word is from several languages simultaneously?
- 2025-06-22 “zakaznik” is both ru-Latn and be-Latn
I can’t simply wrap these first in one {{lang}} and then another, as the inner language tags will override the outer languages: zakaznik. Paradoctor (talk) 15:52, 22 June 2025 (UTC)
The Strange Case of the Vanishing noerror
[edit]
Several times now, I noticed edits that included removing |noerror= from a DISPLAYTITLE. I chalked this up to editor error. Having just asked BrDen for their rationale, it turns out he wasn’t aware of having done this. Now I’m wondering if this is an issue with Visual Editor.
Waiting for the next incident…
Reported as T410848 (VisualEditor removes noerror from DISPLAYTITLE and DEFAULTSORT calls)
Removal of source alignment whitespace
[edit]
Reported as T410847 (VisualEditor removes whitespace used by source editors), was closed as duplicate of T179259 (Visual Editor removing whitespace from infoboxes by default)
DraftCleaner vs. Draft categories
[edit]
ResolvedAFCH creates DEFAULTSORT conflicts, adds duplicate categories
[edit]
I’ve seen this happen a number of times previously.
VisualEditor adding magic words?
[edit]
- 2025-12-03 special:diff/1325531563: DISPLAYTITLE was added by temp account, together with
__INDEX__and__NEWSECTIONLINK__. I wonder…
After DISPLAYTITLEs?
[edit]
