Help talk:Citation Style 1

URL for cite document

{{cite document}} under its COinS says url is supported. But at Kaufman, Texas I'm getting "Unknown parameter |url= ignored" How do I specify a URL for {{cite document}}? Jay 💬 14:50, 10 November 2024 (UTC)

Note: This table of metadata is displayed in the documentation of all Citation Style 1 templates. Not all of these parameters are supported by every CS1 template. {{Cite document}} is specifically for offline documents; why not use {{cite web}}? Mackensen (talk) 15:23, 10 November 2024 (UTC)

(edit conflict)

From the first line of text in the {{cite document}} template's documentation:

This ... template is used to create citations for short, stand-alone, off-line documents. (emphasis added)

The COinS documentation at Template:Cite document § COinS has this:

Note: This table of metadata is displayed in the documentation of all Citation Style 1 templates. Not all of these parameters are supported by every CS1 template.

Use an appropriate template.

—Trappist the monk (talk) 15:24, 10 November 2024 (UTC)

Fixed. Folly Mox (talk) 15:39, 10 November 2024 (UTC)

For some documents {{Cite report}}, which takes a URL, is appropriate. Pol098 (talk) 15:56, 10 November 2024 (UTC)

Thanks, but since it was a PDF, I wanted to use a citation that is closest to document. And that PDF is not a report. Jay 💬 07:39, 12 November 2024 (UTC)

I'm open to correction here by the people who actually did the work, but my understanding is that the theory behind the CS1|2 templates is not to taxonomise source types, but to present multiple consistent display formats while constraining parameter sets. Most written media can be construed as "documents". {{Cite web}} is perfectly adequate here: with complete bibliographic information a reader should be able to locate and consult a printed version of this source should the source's current server go dark. If in doubt of the appropriate template, {{Citation}} can be used as an initial implementation, with |mode=cs1 to force stops instead of commas in between displayed parameter values. Folly Mox (talk) 17:16, 17 November 2024 (UTC)

Oh and to provide well-structured metadata for downstream reusers and to infill certain values in some cases and probably other goals. Forgetfully and in ignorance, Folly Mox (talk) 17:19, 17 November 2024 (UTC)

MOS:RANGE violation

MOS:RANGE states: "The en dash in a range is always unspaced, except when either or both elements of the range include at least one space, hyphen, or en dash; in such cases, {{snd}} between them will provide the proper formatting" and it gives the example "pages 5-7 – 5-9". However, the citation templates do not obey this, instead stripping out the spaces from parameters like |pages=12-1 – 12-24

Example:

• {{citation|title=Algorithms and Theory of Computation Handbook: General Concepts and Techniques|editor1-first=Mikhail J.|editor1-last=Atallah|editor2-first=Marina|editor2-last=Blanton|contribution=Chapter 12: Randomized Algorithms|first1=Rajeev|last1=Motwani|author1-link=Rajeev Motwani|first2=Prabhakar|last2=Raghavan|author2-link=Prabhakar Raghavan|edition=2nd|publisher=CRC Press|year=2010|pages=12-1 – 12-24}}
• Motwani, Rajeev; Raghavan, Prabhakar (2010), "Chapter 12: Randomized Algorithms", in Atallah, Mikhail J.; Blanton, Marina (eds.), Algorithms and Theory of Computation Handbook: General Concepts and Techniques (2nd ed.), CRC Press, pp. 12-1–12-24
• SANDBOX: Motwani, Rajeev; Raghavan, Prabhakar (2010), "Chapter 12: Randomized Algorithms", in Atallah, Mikhail J.; Blanton, Marina (eds.), Algorithms and Theory of Computation Handbook: General Concepts and Techniques (2nd ed.), CRC Press, pp. 12-1–12-24

Using the MOS recommendation of {{snd}} is worse, producing "12-1 –&#32, 12–24". Can this be fixed, please? —David Eppstein (talk) 07:22, 11 November 2024 (UTC)

Use of ((…)) will fix that: title, pp. 12-1 – 12-24. -- Michael Bednarek (talk) 09:10, 11 November 2024 (UTC)

There is no need for hacks. If this should be fixed, the module can handle it without that. Gonnym (talk) 11:16, 11 November 2024 (UTC)

I agree this should be fixed but am not sure how to fix it. Maybe this is something Trappist the monk or Folly Mox can help with? Firefangledfeathers (talk / contribs) 13:53, 12 November 2024 (UTC)

Apologies for any confusion: I'm fairly well versed in the behaviour of Module:CS1 and its dependent templates, but I'm almost entirely unfamiliar with the codebase. I've read through parts of it, but Trappist is by far the primary maintainer. Folly Mox (talk) 18:44, 12 November 2024 (UTC)

In the sandbox. Spaced em/en/hyphen separators between hyphenated compound page numbers:

• {{citation/new|title=Title |pages=12-1 – 12-24}} → Title, pp. 12-1 – 12-24
• {{citation/new|title=Title |pages=12-A – 12-X}} → Title, pp. 12-A – 12-X
• {{citation/new|title=Title |pages=A-12 - A-24}} → Title, pp. A-12 – A-24
• {{citation/new|title=Title |pages=A-12 — A-24}} → Title, pp. A-12 – A-24

Unspaced em/en/hyphen separators between hyphenated compound page numbers:

• {{citation/new|title=Title |pages=12-1–12-24}} → Title, pp. 12-1 – 12-24
• {{citation/new|title=Title |pages=12-A–12-X}} → Title, pp. 12-A – 12-X
• {{citation/new|title=Title |pages=A-12-A-24}} → Title, pp. A-12 – A-24
• {{citation/new|title=Title |pages=A-12—A-24}} → Title, pp. A-12 – A-24

Unspaced em/en/hyphen separators between dot-separated compound page numbers:

• {{citation/new|title=Title |pages=12.1–12.24}} → Title, pp. 12.1 – 12.24
• {{citation/new|title=Title |pages=12.A–12.X}} → Title, pp. 12.A – 12.X
• {{citation/new|title=Title |pages=12.A-12.X}} → Title, pp. A.12 – A.24
• {{citation/new|title=Title |pages=12.A—12.X}} → Title, pp. A.12 – A.24

Spaced em/en/hyphen separators between simple numeric page numbers:

• {{citation/new|title=Title |pages=12 – 24}} → Title, pp. 12–24
• {{citation/new|title=Title |pages=12 - 24}} → Title, pp. 12–24
• {{citation/new|title=Title |pages=12 — 24}} → Title, pp. 12–24

Unspaced em/en/hyphen separators between simple numeric page numbers:

• {{citation/new|title=Title |pages=12–24}} → Title, pp. 12–24
• {{citation/new|title=Title |pages=12-24}} → Title, pp. 12–24
• {{citation/new|title=Title |pages=12—24}} → Title, pp. 12–24

Spaced em/en/hyphen separators between simple alpha page numbers:

• {{citation/new|title=Title |pages=xii – xiv}} → Title, pp. xii–xiv
• {{citation/new|title=Title |pages=xii - xiv}} → Title, pp. xii–xiv
• {{citation/new|title=Title |pages=xii — xiv}} → Title, pp. xii–xiv

Unpaced em/en/hyphen separators between simple alpha page numbers:

• {{citation/new|title=Title |pages=xii–xiv}} → Title, pp. xii–xiv
• {{citation/new|title=Title |pages=xii-xiv}} → Title, pp. xii–xiv
• {{citation/new|title=Title |pages=xii—xiv}} → Title, pp. xii–xiv

Spaced and unspaced em/en/hyphen separators between mixed alpha and numeric page numbers; returned unmodified:

• {{citation/new|title=Title |pages=xii – 5}} → Title, pp. xii – 5
• {{citation/new|title=Title |pages=xii - 5}} → Title, pp. xii - 5
• {{citation/new|title=Title |pages=xii — 5}} → Title, pp. xii — 5
• {{citation/new|title=Title |pages=xii–5}} → Title, pp. xii–5
• {{citation/new|title=Title |pages=xii-5}} → Title, pp. xii-5
• {{citation/new|title=Title |pages=xii—5}} → Title, pp. xii—5

—Trappist the monk (talk) 14:51, 15 November 2024 (UTC)

Impressively robust! Would be a cherry on top if the block of "xii–5" cases also worked, though I guess that's not going to come up terribly often.  — SMcCandlish ☏ ¢ 😼  11:49, 21 November 2024 (UTC)

clean up usurped / unfit / deviated

For probably more than a decade, I've been fixing {{cite}} templates with |url-status=usurped or |url-status=unfit, changing those to |url-status=dead. In one place, Template:Cite web/doc offers usurped and unfit as valid values for this parameter and in two other places it additionally offers deviated, which I didn't know about until now, and that value actually works. Template:Cite news/doc has those two other places, but doesn't have the place offering usurped and unfit without also offering deviated. Recommendations: First, all cite template documentation pages be updated to say that usurped and unfit are not supported and to use deviated instead. Second, cite template documentation pages should—for parameters that are identical in name, range of values, and display—explain the parameters using identical language. —Anomalocaris (talk) 22:22, 13 November 2024 (UTC)

What do you mean when you say: usurped and unfit are not supported? Give us an example of that shows how those parameter values not supported. Every cs1|2 template that supports |archive-url= (all but the preprint templates – {{cite arxiv}}, {{cite biorxiv}}, {{cite citeseerx}}, {{cite medrxiv}}, and {{cite ssrn}} – and {{cite document}}) support usurped and unfit for |url-status=.

Most of the cs1|2 documentation comes from Template:Citation Style documentation which is shared amongst the all of the cs1|2 templates. That is the real documentation. If you are talking about that abomination that is TemplateData, that is not the template documentation. Please specify where you think that the documentation is falling short. If you know how the documentation can be improved, please improve it. The documentation is not protected.

—Trappist the monk (talk) 23:08, 13 November 2024 (UTC)

A factual comment, with no opinion: use of usurped and unfit trigger a cs1 warning. As far as I remember without checking they are identical, and the reference renders without link to the original article, while deviated is identical to dead. Best wishes, Pol098 (talk) 11:49, 14 November 2024 (UTC)

It's a maintenance message, not a warning. I'm not super sure of the point, since no maintenance is required and the URL blacklist is a completely separate process. |url-status=bot: unknown is another maintenance message that needs no attention. Folly Mox (talk) 21:40, 14 November 2024 (UTC)

I'm demoralized somebody is intentionally and systematically removing |url-status=usurped. I have spent years adding usurp to hijacked domains (see WP:JUDI). We should remove that maintenance message, it keeps coming up as a source of confusion, and now apparently a source of harm to the system. At the same time, what can be done to improve TemplateData? --GreenC 03:03, 15 November 2024 (UTC)

TemplateData should be collapsed, it's not part of the documentation and any editor who knows what it is and wants to edit it won't be harmed by it being collapsed. At the moment editors mistake it as part of the documentation causing confusion. -- LCU ActivelyDisinterested «@» °∆t° 10:34, 15 November 2024 (UTC)

Yeah I got hung up on the subtopic and failed to engage with the real problem here: well-intentioned but misinformed and deliberate disimprovements that undo the work of others and may lead readers to malware, scams, online gambling spam, etc. @Firefangledfeathers: suggest url-status. Folly Mox (talk) 17:16, 15 November 2024 (UTC) Edited 15:16, 16 November 2024 (UTC)

Comment: the suggested search also finds many pages where "url-status=live", unambiguously incorrect without archive-url, has been deleted by Anomalocaris. I also delete these. Best wishes, Pol098 (talk) 12:02, 16 November 2024 (UTC)

They edited 760 pages, with an edit summary. The JUDI processes has edited about 42,000 pages. About 2%. -- GreenC 00:29, 16 November 2024 (UTC)

That was a bad suggestion, posted in haste slightly after my break was already over. I clicked through to and reviewed about 40 diffs from the first page of 500 results (back to summer 2020) where the edit summary made it ambiguous what action was taken. Most were false positives, and of the five instances I found where |url-status= was changed away from unfit or usurped, today only one is actually a usurped domain, which I fixed at Special:Diff/1257764735. Anomalocaris does a high volume of good and accurate citation gnoming.

@Anomalocaris: could you speculate on the scope of your edits that have removed these statuses?

I'll try looking for other edit summary keywords and reviewing the diffs instead of blindly posting poor suggestions here for others to work through. Folly Mox (talk) 15:16, 16 November 2024 (UTC)

As a follow up here: I'm experiencing an issue with Σ's edit summary search tool, where it claims there are 762 hits, but will only display 501. The 501th, from May 2020, is the earliest diff it will return irrespective of specified date range.

I manually reviewed all the diffs in the displayed results yesterday where it was unclear from the summary whether a usurped or unfit status was being removed, and all the diffs that indicated that was being done (major overlaps with searches for "usurped" and "unfit", which each return four hits). If anyone is able to get the earlier diffs to display, please ping me with a working link to the summary.py results and I'll manually review them.

The majority of the diffs I checked were false positives (usually clearing up |url-status=bot: unknown), and of the true positives the switch of |url-status= was actually correct in most cases: a few US government websites some earlier editor had marked as unfit perhaps as a personal statement, a redirect to a different content page on a safe domain (Salon), and a domain with an expired registration that no one bothered to usurp.

Had no positives with other edit summary searches; out of ideas. I am seeing a very kindred spirit in Anomalocaris. Unless they are able to estimate a broader scope for this particular change, or we're somehow able to find removals of membership in Category:CS1 maint: unfit URL (50,038) with some database query, I'm hesitantly but optimistically suspecting that although the timeframe quoted in the first sentence of the OP is a long one, the volume of this specific change is not particularly high. May this suspicion mollify in particular GreenC. For the record, Folly Mox (talk) 17:05, 17 November 2024 (UTC)

I am sorry for messing up other editors' work and I would like to make amends. Occasionally I mentioned url-status in edit summaries, but most of my edits involving changing url-status would be covered by "improve <ref>s" rather than "url-status". About a third of my edit summaries include "improve <ref>s", so it would take a long time to examine each of those edits for changing unfit or usurped to dead. Is there any tool that can perform, in effect: For all Anomalocaris edits do if (Diff includes removing "usurped" or "unfit") then (report that edit)? I'm putting a line below this edit to reflect that comments below are actually older and I encourage any replies to be above the line. —Anomalocaris (talk) 18:51, 17 November 2024 (UTC)

I don't think that's possible: someone with more technical knowledge may correct me if I'm wrong, but it's my understanding that the database only stores the page revisions, and the diff extension calculates the differences on request.

Fortunately your estimate seems a bit high: edit summary search for "improve <ref" (27 seconds to execute) returns about 4800 hits, pretty close to 1⁄11 of your mainspace contributions. Still rather a lot, but not entirely unmanageable given some time and effort. It's convenient that the change we'll be looking for is simple and requires not much work to address, unlike for example a CCI or ReferenceExpander cleanup. Also I'm sure this activity doesn't occur with that high of a frequency in the target space.

A database query for edit summary matches is something we can request, and might be a better option for generating a worksheet or ten than pounding poor sigma.toolforge over and over.

Thanks for all your work over the years; it's a pity about this misunderstanding, but I'm willing to help wade through the diffs and help repair remaining problem domains. Folly Mox (talk) 13:38, 18 November 2024 (UTC)

Once we have the full diff list, it wouldn't be too difficult to code up a script that would iterate over the results, retrieve the html of the diff, and log the diff if the html matches /url\-status\s*\=\s*u/ or equivalent syntactically correct regex (it's been decades). The resulting positive match subset log could be manually checked with much less labour.

If no one else gets to it first, I'll see about requesting queries and an edit filter later today. Folly Mox (talk) 14:09, 18 November 2024 (UTC)

---

Anomalocaris, it would help to be able to review your edits in which you removed "usurped". I see very few that use "usurped" in the edit summary. The most recent are appropriate, since the urls direct to 404 pages; "dead" is the right argument to use. What other edit summaries might lead us to more "usurped" changes? Firefangledfeathers (talk / contribs) 15:25, 15 November 2024 (UTC)

• A new experiment shows {{cite web}} with |url-status= set to any of {usurped, unfit, deviated} generates the warning {{cite web}}: CS1 maint: url-status (link). When I started this discussion I thought I saw that deviated did not generate the warning. I may have been mistaken. [Update: deviated doesn't seem to generate the warning. Anomalocaris (talk) 00:30, 16 November 2024 (UTC)]
• I misunderstood the warning to mean, "Please change the URL status to dead. I now understand the warning to mean, "Please find a better reference."
• Apologies to editors whose efforts to put in usurped status I undermined.
• But I don't understand why you made those efforts, because I don't see the practical difference between an external link that's invalid because the original domain owner didn't renew it, and an external link that's invalid because the webmaster discontinued the page. Either way, it's a dead link. Yes, sometimes it might be possible to find the page on the same website, now organized differently, but usually, when a page is gone it's gone. (strike by Anomalocaris (talk) 00:30, 16 November 2024 (UTC))
• If someone can suggest a way of searching through my over 87,000 edits for changing |url-status=usurped or |url-status=unfit to |url-status=dead, I can review my work, but this would be a huge project; some of the formerly usurped URLs might be dead by now and some of the references may not be in the current version, so it would be a big process.
• If the meaning of the maintenance tag is "Please find a better reference", I believe the maintenance tag should go away if an archive-url is supplied. (strike by Anomalocaris (talk) 00:30, 16 November 2024 (UTC))
• The documentation should be improved, as I said before, and another improvement is to clarify that the warning message means "Please find a better reference", not "please change the URL status to dead".

—Anomalocaris (talk) 19:24, 15 November 2024 (UTC)

Kindly, the important distinction is that usurped and unfit URLs do not generate a clickable link. Folly Mox (talk) 21:39, 15 November 2024 (UTC)

User:Anomalocaris: I don't understand why you made those efforts. Really? Since we don't want readers to unwittingly click through to gambling and porn, expecting they would arrive at a normal website, we hide those malicious links by setting them to usurped. You have not noticed this before?

"Example with status=dead". Archived from the original on 2024-11-01.

"Example with status=usurped". Archived from the original on 2024-11-01.{{cite web}}: CS1 maint: unfit URL (link)

You see the difference? One displays a link to "the original" and the other does not. It is why |url-status=usurped exists. It serves a function, usurped is not just another word for dead. -- GreenC 23:49, 15 November 2024 (UTC)

GreenC (also Folly Mox): Thank you for making the obvious even more obvious. I see it now. I struck two bullets above. I also confirm Pol098's observation that deviated seems to be identical to dead in this regard. —Anomalocaris (talk) 00:30, 16 November 2024 (UTC)

It's been commented here that "Since we don't want readers to unwittingly click through to gambling and porn, expecting they would arrive at a normal website, we hide those malicious links by setting them to usurped." This makes perfect sense; I suggest that it should be mentioned in the documentation, not just "these parameters suppress the original URL". Maybe add "... because they link to inappropriate sites. A maintenance message is generated to suggest that a better link could be found". I don't actually think that a better link is likely to be available in perhaps most cases, sites are often gone with content only findable, sometimes, on the Wayback Machine; I'm not sure, without statistics, that the maintenance message is even useful. Best wishes, Pol098 (talk) 12:23, 16 November 2024 (UTC)

The statuses live, dead, unfit, usurped, and deviated are all invisible to readers (for whom Wikipedia is intended), and confusing to editors, in particular with different parameters behaving exactly the same (dead, deviated; unfit, usurped). I would suggest deprecating them all (except live, for archived references), and for all future use suggest live, unavailable (but linked), and unsuitable (no link). It would be up to editors to choose; for example, is a link to, say acme.com/rodulator unavailable or unsuitable when the rodulator is discontinued and the link redirected to the acme.com home page? Best wishes, Pol098 (talk) 13:33, 16 November 2024 (UTC)

I think this is a wakeup call that the maintenance message for these |url-status= values should be suppressed. I'm not sure if there's a better tracking route than adding the article to Category:CS1 maint: unfit URL (50,038), but many editors see maintenance categories as problems to fix, rather than just tracking methods. Maybe it could be reparented to Category:CS1 properties? Folly Mox (talk) 15:16, 16 November 2024 (UTC)

"many editors see maintenance categories as problems to fix" - most are problems to fix - missing title, "Editor" as author name or "Archived" as title, and so on. Best wishes, Pol098 (talk) 19:59, 16 November 2024 (UTC)

I should have phrased my words more clearly. Yes, many / most maintenance categories (including subcats of Category:CS1 maintenance) are full of errors that require repair (phone suggested: full of beans). Maybe I should have differentiated between "maintenance" and "tracking" categories? The software doesn't. My point was that, specifically for the "unfit URL" category, usually the case is that the archive snapshot supports the cited claim, but the URL that used to point to the original now points to garbage. There's usually not a repair to be made, and it certainly isn't just changing the |url-status= value to one that doesn't emit a message. The fact that an editor of nineteen years with a huge volume of citation gnoming had such a misunderstanding is a signal for more clarity around unfit / usurped URLs. Folly Mox (talk) 21:00, 16 November 2024 (UTC)

User:Folly Mox, maintenance message for these url-status values should be suppressed. Is this occurring at the MediaWiki level outside our (Enwiki) immediate control? -- GreenC 00:58, 17 November 2024 (UTC)

The message is emitted by Module:CS1. I think it's hidden for people who don't have the custom css set up to display CS1 maintenance messages. Subcats of Category:CS1 properties each seem to require their own custom css, which makes surfacing them even more intentional for interested editors. Presumably such editors would understand that no action is required for this property. Folly Mox (talk) 03:06, 17 November 2024 (UTC)

If there are CS1 maintenance messages when an edit is previewed without CS1 messages set to display, there is a prominent notice like "Script warning: One or more {{cite book}} templates have maintenance messages; messages may be hidden (help).", with no indication of what cites are the cause. And, with CS1 messages displayed, a message like "missing publisher" looks a lot more like an error than just a comment. Best wishes, Pol098 (talk) 20:26, 17 November 2024 (UTC)

User:Folly Mox, that's good. Do you think an RfC to disable it, for some or all, would be appropriate? Otherwise this thread will have no result. I can start it, unless there is strong objection to the idea of even having an RfC. -- GreenC 00:49, 18 November 2024 (UTC)

For something like reparenting Category:CS1 maint: unfit URL under Category:CS1 properties to become Category:CS1 properties: unfit URL (which should make the messages less visible, and I hope make these URLs feel like they're not required action items), we could probably just ask Trappist the monk nicely. They may also have counterarguments. CFD is probably the follow up venue if a polite request fails here. Folly Mox (talk) 02:57, 18 November 2024 (UTC)

A complementary measure might be to request an edit filter that detects removal of usurped or unfit from |url-status= (I wasn't able to find any matching public edit filters, but I'm very inexperienced with them). This could be set to log at first, but potentially upgraded to warn if it works properly. If interested people check through the filter log every once in awhile, we should be able to catch this more quickly. Folly Mox (talk) 13:44, 18 November 2024 (UTC)

I would echo the key point made by User:Folly Mox, User:Pol098, User:GreenC, and previously by User:Manifestation. When a citation template with a valid archive-url correctly sets url-status=usurped etc, it should not be perpetually flagged with a top-of-the-screen "Script warning ... maintenance message" that prominently, confusingly, and unhelpfully encourages all future editors to waste time diagnosing a citation problem that doesn't exist. I'm sure the warning message was well-intended, but in this case it's doing more harm than good. —173.56.111.206 (talk) 07:09, 22 November 2024 (UTC)

User:Trappist the monk, would you be amiable to Folly Mox's suggestion to reparent the tracking category? There have been no objections, only support. It seems like a small enough issue we don't need to reargue it all over again at CFD, this is probably the better place for it anyway. -- GreenC 17:14, 23 November 2024 (UTC)

In the sandbox:

Cite book comparison

Wikitext	{{cite book|archive-date=2024-11-23|archive-url=//archive.org|title=Title|url-status=usurped|url=//example.com}}
Live	Title. Archived from the original on 2024-11-23.{{cite book}}: CS1 maint: unfit URL (link)
Sandbox	Title. Archived from the original on 2024-11-23.

Articles with |url-status=unfit and |url-status=usurped are categorized in Category:CS1: unfit URL.

—Trappist the monk (talk) 20:47, 23 November 2024 (UTC)

"Ambiguous" numerical month dates leading to many errors

This topic has been brought up at least twice, Help talk:Citation Style 1/Archive 33#edtf date formats as cs1|2 date parameter values and Help talk:Citation Style 1/Archive 44#Fix the date formatting, but to no avail.

Many scientific journals use YYYY-MM format dates and don't bother that they might be interpreted as a range of two years (it's almost impossible in this context). These dates are imported by a gadget which automatically converts URLs into cite templates, but this type of format is prohibited on Wikipedia, leading to CS1 errors. I don't know which gadget is that and where is its talk page so I decided to write here.

Why wouldn't anyone fix the issue? There are so many possible solutions: automatically convert to the desired format (which is what currently done manually by Ira Leviton, Paul2520 and perhaps some other users, I'm pretty sure they have never seen a single YYYY-YY date), show an error etc. 5.178.188.143 (talk) 21:06, 14 November 2024 (UTC)

P. S. And by the way, Citation bot apparently makes such changes in an entirely automatic fashion, without ever verifying that the date was actually YYYY-MM not YYYY-YY.

It is always helpful to link to example diffs, or pages with a problem, when reporting an issue. Please do so. – Jonesey95 (talk) 14:23, 16 November 2024 (UTC)

https://en.wikipedia.org/w/index.php?title=Steven_Kistler&diff=prev&oldid=1257506607 5.178.188.143 (talk) 16:05, 16 November 2024 (UTC)

That diff shows Citation Bot fixing an unambiguous YYYY-MM problem. – Jonesey95 (talk) 02:10, 17 November 2024 (UTC)

According to a thread a few up from one of the ones mentioned in the OP, this "gadget" is Citoid, the Foundation's essentially unmaintained citation problem generator. Tracked at phab:T132308 (2016, Open, High priority, no assignee). Folly Mox (talk) 15:32, 16 November 2024 (UTC)

What's wrong with Wikimedia Foundation that they can't fix a high-priority bugs in eight years, aren't they swimming in money and volunteers? 5.178.188.143 (talk) 16:01, 16 November 2024 (UTC)

To be fair, there was a lot of progress made in 2021, including global updates to the Citoid codebase and local updates to Module:CS1. The Foundation devs and contractors tend not to prioritise enwiki specific concerns, and focus on things they presume will benefit all / many projects in the Wikimedia ecosystem.

I don't think it would be super unreasonable if the Module were updated to convert YYYY-NN to month year when NN is in the range (01,12). Citing a year range with an ambiguous abbreviated terminus is fair game for miscorrection.

But, it's easy for me to say that, since I've never actually touched the code and have no responsibility to update it when features are requested. I might also be wrong about the surrounding issues, having not fully read through Wikipedia talk:Manual of Style/Dates and numbers/Archive 160 § ISO 8601 YYYY-MM Calendar Date Format (June 2020). Folly Mox (talk) 17:42, 16 November 2024 (UTC)

The issue is that formats like 2010-11 cannot be interpreted automatically by the module because they are ambiguous. Someone needs to figure out what the original intent of the date is, because that information is not present in the text. Is it supposed to be 2010–2011 or November 2010? Because the module does not have the information to disambiguate it, it should not try. —David Eppstein (talk) 20:04, 16 November 2024 (UTC)

It's never, ever 2010-2011 5.178.188.143 (talk) 10:14, 17 November 2024 (UTC)

It's not an error or bug. ISO 8601 style dates (yyyy-mm and yyyy-mm-dd) are common in many parts of the world and progressively becoming more common in English speaking parts of the world - at least for official forms, engineering and multinational organisations. Among other reasons, I love it for putting dates in computer file names because it also sorts alphabetically. According to WP:DATERANGE, year ranges should be written as 1881–1886, not 1881–86 - so you should never have a year range like 2010-11. If you do see 2010-11 then look around and see if there are other dates like 2010-05 (obviously not a valid year range). The cite templates know about ISO 8601 style dates, so if you have {{use dmy dates}} or {{use mdy dates}} at the top of the article then the cite templates will transform it into the appropriate style.  Stepho  talk  10:42, 17 November 2024 (UTC)

Cite dictionary issue with entry-url

{{cite dictionary |dictionary=[[Oxford English Dictionary]] |entry-url=http://www.oed.com/view/Entry/135679?rskey=7ZL0rI&result=3&isAdvanced=false |entry-url-access=subscription |title=oxymoron |url=https://www.oed.com/dictionary |access-date=26 February 2013}}

renders as

"oxymoron". Oxford English Dictionary. Retrieved 26 February 2013.

The rendered citation uses the value of |url=, not, as expected, |entry-url=. Paradoctor (talk) 19:37, 16 November 2024 (UTC)

Too many urls:

{{cite dictionary |dictionary=[[Oxford English Dictionary]] |entry-url=http://www.oed.com/view/Entry/135679?rskey=7ZL0rI&result=3&isAdvanced=false |entry-url-access=subscription |entry=oxymoron |access-date=26 February 2013}}

"oxymoron". Oxford English Dictionary. Retrieved 26 February 2013.

—Trappist the monk (talk) 19:57, 16 November 2024 (UTC)

Thanks! Paradoctor (talk) 20:23, 16 November 2024 (UTC)

:A comment about the documentation: while |entry-url= isn't included in the listed parameters, it is discussed, and the use of both |url= and |entry-url= in an example is given (dictionary is an alias of encyclopedia):

• "{{cite encyclopedia |encyclopedia=Biographical Memoirs |volume=82 |date=2003 |given=Arnel R. |surname=Hallauer |entry=John David Axtell |publisher=[[National Academies Press]] |publication-place=Washington, D.C. |language=en |url=https://www.nap.edu/catalog/10683/biographical-memoirs-volume-82 |entry-url=https://www.nap.edu/read/10683/chapter/2}}

  Hallauer, Arnel R. (2003). "John David Axtell". Biographical Memoirs. Vol. 82. Washington, D.C.: National Academies Press.

Above is an example of using {{para|entry-url}} to link to the cited entry in the encyclopedia while also using {{para|url}} to link to the encyclopedia as a whole."

Best wishes, Pol098 (talk) 20:37, 16 November 2024 (UTC)

In OP's example, it is not possible to use |url= to link the [dictionary] as a whole because |dictionary=[[Oxford English Dictionary]]; you cannot link the Oxford English Dictionary text to two separate targets at the same time.

—Trappist the monk (talk) 20:58, 16 November 2024 (UTC)

Error related to Template:CS1 language sources

Category:Articles with Moldovan-language sources (ro-md), which uses Template:CS1 language sources (which talk page redirects here) has an error.

• The error does not explain how or what should be done.
• The category isn't added to Category:Language templates errors.

Gonnym (talk) 13:52, 17 November 2024 (UTC)

That was Editor Error living up to their username. {{CS1 language sources}} is for categories with the name structure:

Category:CS1 <language name>-language sources (<tag>)

For categories with the name structure:

Category:Articles with <language name>-language sources (<tag>)

use {{Non-English-language sources category}}.

Preview is your friend; use it.

—Trappist the monk (talk) 15:12, 17 November 2024 (UTC)

Sorry. It seems I copied from the wrong page and I didn't understand the error message. --Error (talk) 00:32, 18 November 2024 (UTC)

Double-checking regarding year disambiguation

When a citation uses a letter e.g. |year=1997a, the COinS metadata is unaltered, right? Remsense ‥ 论 18:17, 17 November 2024 (UTC)

{{cite book |title=Title |date=1997a}}

'"`UNIQ--templatestyles-0000009B-QINU`"'<cite class="citation book cs1">''Title''. 1997a.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=book&rft.btitle=Title&rft.date=1997&rfr_id=info%3Asid%2Fen.wikipedia.org%3AHelp+talk%3ACitation+Style+1" class="Z3988"></span>

Title. 1997a.

—Trappist the monk (talk) 18:25, 17 November 2024 (UTC)

Thank you! I guess I meant to clarify that this format has the intended, recommended effect, but since it's plainly listed I'm not quite sure what I was worried about. Remsense ‥ 论 18:28, 17 November 2024 (UTC)

URL for original edition of book

There is a book where only the original edition has an open access online copy, seen at {{Kelley 1975}} (created for use with {{sfn}}). The URL links to the 1955 edition, but the citation includes information about both the 1st (via |orig-date) and 2nd editions. Should there be an |orig-url, or is there a concise way to indicate that a link is to an older edition in {{cite book}}? Tule-hog (talk) 18:53, 17 November 2024 (UTC)

Don't confuse the reader by specifying the second edition and then linking to the 1955 (1st?) edition. Those are two different sources with different bibliographic details so cite the one you consulted, You can modify the template so that you can specify one or the other but don't mash two sources into one template.

—Trappist the monk (talk) 19:10, 17 November 2024 (UTC)

(Yes - 1st=1955, 2nd=1975.) Given the two editions are page-for-page almost identical, wouldn't it be to the benefit of readers and editors to include the link? The book is cited across many articles, and it seems unclean to include both editions separately on each just for the sake of supplying a link, and best practice to cite the most recent edition regardless of availability (with some exceptions). Tule-hog (talk) 19:35, 17 November 2024 (UTC)

(Apologies if I misinterpreted and you were referring to modifying {{cite book}}!) Tule-hog (talk) 19:36, 17 November 2024 (UTC)

That is still two sources with two separate and different sets of bibliographic details:

Kelley, John L. (1955). General Topology. New York: D. Van Nostrand.

Kelley, John L. (1975). General Topology (2nd ed.). New York: Springer-Verlag. ISBN 978-0-387-90125-1.

Were the bibliographic details the same edition-to-edition, then |orig-date=1955 and |url=https://archive.org/details/GeneralTopologyJohnL.Kelley might be acceptable. As those details are not the same edition-to-edition, I do not think that |orig-date= and |url= are appropriate.

You might change the template so that it renders something like this:

Kelley, John L. (1975). General Topology (2nd ed.). New York: Springer-Verlag. ISBN 978-0-387-90125-1. (1955 edition)

This complies with the one-source-one-template rule and still gives you the link to the first edition.

—Trappist the monk (talk) 22:45, 17 November 2024 (UTC)

Title case

As of now, WP:CS1#Titles and chapters says, "Use title case unless the cited source covers a scientific, legal or other technical topic and sentence case is the predominant style in journals on that topic. Use either title case or sentence case consistently throughout the article."

Is this the consensus of the community? Because it does not appear to be enforced consistently in Wikipedia among featured articles. Look at the current WP:TFA, Donkey Kong Country, for example. The articles' citations do not consistently use title case or sentence case in its titles, but instead, use the title case or sentence case depending on what the source cited uses. And prior to the peer review for Bejeweled (video game) just now, I've never been asked to follow this guideline.

Honestly, in my opinion, regarding articles and chapters in particular, I think it's best to just use whichever case the source uses. If the source uses title case, use title case. If the source uses sentence case, use sentence case. After all, it's more accurate to the source and is just more convenient when citing sources, especially since most news sources use sentence case for their articles titles. Lazman321 (talk) 18:20, 18 November 2024 (UTC)

It's the guidance at MOS:TITLECAPS. Rjjⁱⁱⁱ (talk) 03:41, 19 November 2024 (UTC)

That doesn't really answer my question. MOS:TITLECAPS says, "WP:Citing sources § Citation style permits the use of pre-defined, off-Wikipedia citation styles within Wikipedia, and some of these expect sentence case for certain titles (usually article and chapter titles). Title case should not be imposed on such titles under such a citation style consistently used in an article." Essentially, it defers to whatever the official guidelines of a particular citation style are, and the guidelines for CS1 are what I'm contesting right now.

What I asked was whether there was a consensus on this matter. Right now, I'm looking through forum discussions, and the most extensive discussion I could find was from 2017 in Wikipedia talk:Citing sources/Archive 44#Title case? in which the general attitude appeared to be that sentence case was fine for titles of articles and chapters. A user from that discussion, SMcCandlish, essentially reinforced this at Help talk:Citation Style 1/Archive 92#Article titles this very year. Is that the consensus, and if so, would it be best for this page to be changed and accommodate it? Lazman321 (talk) 04:29, 20 November 2024 (UTC)

I read the guidance at WP:CS1#Titles and chapters, which you challenge, as mainly concerned with titles of larger works. Its sentences on short works is an aside explaining a different styling. My practice is to apply title case for longer works, and leave shorter works as I find them. In general, MOS:TITLECAPS wins. -- Michael Bednarek (talk) 09:41, 20 November 2024 (UTC)

Personally, I apply title case to the titles of major works (e.g. journals, book titles, websites etc...) per MOS:TITLECAPS, and sentence case to sub-sections of it (article title, chapter titles, etc...). "Article about interesting things" in Journal of Stuff, "Chapter 2: The return of the mad Czar" in The History of Czars. This is how I've seen in done in virtually all well-formatted articles, and most citation guides. If someone used title case across the board, I won't edit war over it, but I find it very strange. Headbomb {t · c · p · b} 12:20, 20 November 2024 (UTC)

That is my preference as well. But MathSciNet and zbMATH, the two major bibliographic databases for mathematics, use sentence case for book titles (but not journal titles), so that at least is a well-established alternative convention in some fields. —David Eppstein (talk) 19:50, 20 November 2024 (UTC)

The idiosyncrasies of such databases should be ignored in favour of MOS:TITLECAPS. War and peace a historical novel, as used at OCLC 656581151, is an abomination. -- Michael Bednarek (talk) 23:31, 20 November 2024 (UTC)

News aggregators parameter

For a source via a news aggregator (e.g. Yahoo News), in {{Citation}} and variants, should we use the |via= or |publisher= parameter for the aggregator?

E.g. should we do |newspaper=The New York Times |via=Yahoo News? seefooddiet (talk) 02:23, 19 November 2024 (UTC)

Yes, because Yahoo News is the content deliverer.

—Trappist the monk (talk) 03:52, 19 November 2024 (UTC)

'Reformat dates' function

Hi! I'm trying to figure out the date reformatting function: Module:Citation/CS1/Date validation#L-841. I see that the module can convert dates to {{#time:n F Y|2024-10-10}} -> 10 October 2024, is it possible to convert in {{#time:n xg Y|2024-10-10}} (month in genitive form) -> 10 October 2024?

But I need to save {{#time:F Y|2024-10-10}} -> October 2024 option. Iniquity (talk) 20:35, 20 November 2024 (UTC)

It is not really clear to me what it is that you are asking. cs1|2 doesn't use the #time parser function to do date conversions.

The #time parser is not used because we can't write something like:

{{#time:Y-m-d|10 octobre 2024}}

on the French Wikipedia; doing so results in This despite the #time parser's ability to render this at en.wiki:

{{#time:n F Y|2024-10-10|fr}} → 10 octobre 2024

You would think that, for an 'international' project, accepting dates with local-language month names as input would go hand-in-hand with rendering local-language month names.

—Trappist the monk (talk) 22:47, 20 November 2024 (UTC)

Thanks for the answer! I mean that now the 'long' array from 'date_names' in Module:Citation/CS1/Configuration is used to form the date. There the months are in the nominative case, but for the Russian language the genitive case is needed for 'dmy' form and nominative case for 'my' form. Is it possible to add an additional array with genitive case? Iniquity (talk) 05:09, 21 November 2024 (UTC)

Just for clarity, you want:

10 октября 2024 ← {{#time:n xg Y|2024-10-10|ru}} – genitive for all 'dmy' dates; including ranges? what about mdy?

октябрь 2024 ← {{#time:F Y|2024-10-10|ru}} – nominative for 'my' dates only; including ranges?

#time parser function alludes to other languages that have nominative/genitive date forms. Do they follow the same rules as the Russian dates?

I have some ideas for resolution of this issue. I'll think more on it. My time is occupied elsewhere so I won't be able to get to this until later this week or next week. In the meantime, here is your assignment:

1. MediaWiki supports about 350 editions of Wikipedia. Assemble a list of those Wikipedia-edition languages that have nominative/genitive date forms.
2. determine which date formats from the above assembled list need nominative month names and which formats need genitive names.

—Trappist the monk (talk) 15:36, 21 November 2024 (UTC)

10 октября 2024 ← {{#time:n xg Y|2024-10-10|ru}}
My mistake, must be j not n - {{#time:j xg Y|2024-10-10|ru}}

genitive for all 'dmy' dates; including ranges?
Yes.

what about mdy?
We dont use this format, we can leave the nominative case, but I found something, I'll write it below.

октябрь 2024 ← {{#time:F Y|2024-10-10|ru}} – nominative for 'my' dates only; including ranges?
Yes, but the first letter of the first month must be capitalized.

#time parser function alludes to other languages that have nominative/genitive date forms. Do they follow the same rules as the Russian dates?
This is a relatively complex issue, I found such a list of formats for each language. And now it seems to me that the genitive case is not the only problem of internalization:
https://codesearch.wmcloud.org/core/?q=dmy+date&files=languages%2Fmessages&excludeFiles=&repos= Iniquity (talk) 18:42, 21 November 2024 (UTC)

That can't be the whole list can it? Why is ru.wiki not on that list?

—Trappist the monk (talk) 22:41, 21 November 2024 (UTC)

This is a complete list, you just need to load the remaining lines, messageRU.php there.

Iniquity (talk) 06:38, 22 November 2024 (UTC)

I think it is possible to use lang:formatDate for catch necessary formats. Iniquity (talk) 18:55, 21 November 2024 (UTC)

lang:formatDate() is the Scributo version of the #time parser function. Try this in a module debug console at ru.wiki:

=mw.language.getContentLanguage():formatDate ('j F Y') → 21 ноябрь 2024

I used that to get the month name. Then, I turned it round and attempted to get a YYYY-MM-DD date from the Russian DMY:

=mw.language.getContentLanguage():formatDate ('Y-m-d', '21 ноябрь 2024') → Ошибка Lua: bad argument #2 to 'formatDate': invalid timestamp '21 ноябрь 2024' ... and some other error message stuff

To prove that the call was structured correctly, I changed 'ноябрь' to 'November':

=mw.language.getContentLanguage():formatDate ('Y-m-d', '21 November 2024') → 2024-11-21

mw.language:formatDate() will not work for date format conversion in Module:Citation/CS1/Date validation.

—Trappist the monk (talk) 22:41, 21 November 2024 (UTC)

Yes, I know :( It doesn't work well with anything that isn't ISO. But it converts ISO to the required format well. Iniquity (talk) 06:39, 22 November 2024 (UTC)

I would like to separately tell you that we have adopted a local rule that all service dates must be machine-readable (to simplify the transfer of information from wiki to wiki) and we convert them into ISO using a bot.

I tried to globalize it (meta:Requests for comment/Technical agreement on dates and times) somehow, but I didn't succeed very well. Iniquity (talk) 10:39, 24 November 2024 (UTC)

I was curious to see how your list of 70 matches direct testing of the time parser returns for each of the language names taken from Module:Citation/CS1/Configuration (the inter_wiki_map table). So I wrote Module:Sandbox/trappist the monk/genitive. You can see the results by adding one of these to a sandbox page:

{{#invoke:Sandbox/trappist the monk/genitive|main|a-m}}

{{#invoke:Sandbox/trappist the monk/genitive|main|n-z}}

where a-m and n-z match the first letter of a language tag. These are lua set patterns: lang:match ('^[a-m]') etc.

Alas, you can't do a-z, nor can you have a-m and n-z on the same page at the same time, because the time parser chokes and emits the confusing error message: For an explanation, see Phab:T299909 and the linked discussion.

When the test is run for each range, they find 143 languages where at least one month name returned by {{#time:F|2024-mm-01}} (mm is month number 1–12) differs from the month name returned by {{#time:xg|2024-mm-01}}.

Do all of these languages use nominative/genitive dating? I don't know.

—Trappist the monk (talk) 18:34, 25 November 2024 (UTC)

Wow! Thanks for this research. I think there are more differences because the time functions use the standard language fallback scheme from MediaWiki: https://codesearch.wmcloud.org/core/?q=fallback&files=languages%2Fmessages&excludeFiles=&repos= Iniquity (talk) 18:52, 25 November 2024 (UTC)

mw.language:formatDate() won't work for this application because it does not accept (so far as I can tell from
the documentation) a language parameter;
You can use mw.language.new( code ):formatDate( format, timestamp, local ) Iniquity (talk) 19:25, 25 November 2024 (UTC)

Nope. From the documentation: "There is a limit of 200 on the number of distinct language codes that may be used on a page. Exceeding this limit will result in errors."

—Trappist the monk (talk) 19:38, 25 November 2024 (UTC)

I'm talking about the language parameter :) Iniquity (talk) 05:13, 26 November 2024 (UTC)

diff
{{#invoke:Sandbox/Iniquity|main|a-l}}{{#invoke:Sandbox/Iniquity|main|m-z}} Iniquity (talk) 16:58, 26 November 2024 (UTC)

As idea: make a setting that will allow you to switch on the formatDate conversion function. Only ISO dates are passed to this function, and CS1 module only converts incoming dates to ISO format. Iniquity (talk) 17:35, 2 December 2024 (UTC)

Original title

I was editing Dobermann and I found a book edited with two different titles in two different editions; in {{cite book}} there's no parameter |orig-title= (unlike |orig-year=}}; my workaround was that: {{cite book |last1=Scott |first1=John Paul |last2=Fuller |first2=John L. |orig-year=1965 |year=1975 |title=Dog Behavior: the Genetic Basis |edition=''Genetics and the Social Behavior of the Dog'' new |location=Chicago and London |publisher=University of Chicago Press |isbn=0-226-74335-7 |url=https://archive.org/details/dogbehaviorgenet00scot |via=Internet Archive}}, yielding (Genetics and the Social Behavior of the Dog new ed.). The first edition was published in 1965 as Genetics and the Social Behavior of the Dog and the book itself is is better known with that title. Is it acceptable?-- Carnby (talk) 20:44, 20 November 2024 (UTC)

Do not abuse cs1|2 parameters. Cite the source that you consulted. If you consulted both, cite both in separate templates. Do not mash both sources into a single template.

—Trappist the monk (talk) 21:06, 20 November 2024 (UTC)

Thank you. Fixed.-- Carnby (talk) 22:07, 20 November 2024 (UTC)

Cite book editor names

In the Template:Cite book template data, the author first name parameters are named "First name", "First name 2", "First name 3" etc. The last names, masks and links follow this convention, as do the translator first names and last names.

But, when it comes to the editors, it follows the separate convention "Last name of second editor", "Last name of third editor" etc. for the editor first names, last names, masks and links.

Why is this, and can the editor parameter named be changed to conform? It is a wonderful world (talk) 17:10, 21 November 2024 (UTC)

Do you have an example in mind? Because I really don't know see what problem you're having with parameter names. For authors, |lastn=/|firstn=, for editors, |editor-lastn=/|editor-firstn=. If you want to be ultrapedantic, you can even use |author-lastn=/|author-firstn= instead of |lastn=/|firstn=. Headbomb {t · c · p · b} 18:14, 21 November 2024 (UTC)

@Headbomb Thank you for asking for clarification, I forgot to say that I saw this when using the add template function in the visual editor (the puzzle piece icon in the toolbar). It made it more confusing when scrolling through the parameters. It is a wonderful world (talk) 18:19, 21 November 2024 (UTC)

TemplateData, inexplicably, is structured programming code that is part of the unprotected documentation. In this case, It is a wonderful world, that means that you can edit the TemplateData section yourself. Happy editing, and be careful! – Jonesey95 (talk) 21:03, 21 November 2024 (UTC)

@Jonesey95 Thanks for clarifying! I thought I better exercise caution thanks to how much this template is used. It is a wonderful world (talk) 21:09, 21 November 2024 (UTC)

Query regarding geo-fenced reference urls

Bringing here from Wikipedia talk:Featured list candidates#Query regarding geo-fenced reference urls: User:MPGuy2824 has a citation to a site that geofences the website to be only be accessible within India (example url). How should this be delimited? "|url-access=limited" seems likely, but the doc wording for that is "free access is subject to limited trial and a subscription is normally required", which isn't the same thing. Another editor has suggested just calling it "|url-status=dead" to force the archive link to be the main, but that's also not true. Is there an existing standard for this situation? --PresN 16:41, 22 November 2024 (UTC)

Are you sure that you have supplied the correct information here? So far as I can tell, https://old.eci.gov.in/files/file/3614-punjab-general-legislative-election-2017/ has never been in Election Commission of India, the article mentioned at WT:FLC.

For me, somewhere in the wastelands of North America, that url is dead. Were I to encounter it in the wild, I would mark it with {{dead link}}. Archive.org does not have a snapshot of that url; I didn't bother looking in other archives. If there is no archived snapshot, |url-status=dead is not an appropriate 'solution'.

—Trappist the monk (talk) 17:13, 22 November 2024 (UTC)

The list in question is List of constituencies of the Punjab Legislative Assembly; it has, for example, in ref 7 a link to [1], which never resolves for me in America, with an archive at [2], which does. --PresN 22:44, 22 November 2024 (UTC)

I looked at the archived snapshot. It looks more-or-less like a link farm with apparently related links (Archive Delimitation Orders) linking back to itself (or another archive snapshot of the same page). Not at all clear what that source is supposed to be supporting.

Since the article has been promoted to FA (not something that I would have done given the piss-poor quality of this one link and assuming that the other links to the same domain would be similar), does this topic still require some sort of answer?

—Trappist the monk (talk) 00:39, 23 November 2024 (UTC)

No, sounds like the answer to "how should we handle geo-fenced urls" is "the Election Commission of India, when viewed through the Internet Archive, has an ugly website", so I guess we're good here. --PresN 21:25, 23 November 2024 (UTC)

HugeDomains

Special:Diff/1254741850/1256841759 recently brought to attention. Do we have title traps for tracking cats? -- GreenC 17:07, 23 November 2024 (UTC)

We do, but in a different form: hugedomains.com which seems to have been the form used when we first created the generic title list; see Help talk:Citation Style 1/Archive 70 § Wayback Machine. Sandbox tweaked:

Cite book comparison

Wikitext	{{cite book|title=Some.domain.name for sale - HugeDomains}}
Live	Some.domain.name for sale - HugeDomains.
Sandbox	Some.domain.name for sale - HugeDomains. {{cite book}}: Cite uses generic title (help)

And still finds the original:

Cite book comparison

Wikitext	{{cite book|title=Some.domain.name for sale - HugeDomains.com}}
Live	Some.domain.name for sale - HugeDomains.com. {{cite book}}: Cite uses generic title (help)
Sandbox	Some.domain.name for sale - HugeDomains.com. {{cite book}}: Cite uses generic title (help)

—Trappist the monk (talk) 22:53, 23 November 2024 (UTC)

Usage of the quote parameter

I'm adding/updating {{cite web}} entries on articles of towns and cities in Poland. The citation is to an official Polish website. Unfortunately, but not surprisingly, the website is almost entirely in Polish. I wish to add instructions to the citation that show how to perform the relevant search. At the moment, it seems as if the only way I can do this is to use the "quote" parameter. See, for example, this edit. I realise that this is not the intended use of this parameter, but it seems the best fit for what I'm trying to achieve. Is there another more appropriate way of doing what I'm trying here? Does there need to be a new parameter, for example? Regards, Kiwipete (talk) 03:36, 24 November 2024 (UTC)

Don't abuse cs1|2 template parameters. Put that extra stuff inside the <ref>...</ref> tags after the template's closing }}.

—Trappist the monk (talk) 03:49, 24 November 2024 (UTC)

@Trappist the monk - like this? [3]. Kiwipete (talk) 07:20, 25 November 2024 (UTC)

Requested edit to Module:Citation/CS1/Configuration

As with my previous edit request to the Configuration subpage, I have amended the local variable script_lang_codes to support an additional language being tagged in citation titles and chapter titles (this time Cherokee chr). As with last time, I have also amended the whole variable definition to balance the line-wrapping better, so please take the whole variable definition (lines 1177–1183).

Again, this is in no way urgent; the existing code correctly adds the IETF language tag to the text, this edit will merely suppress the error message reading Invalid |script-title=: unknown language code that appears when an unrecognised ISO 639 code is used and the resulting categorisation into Category:CS1 errors: script parameters. — OwenBlacker (he/him; Talk) 19:43, 25 November 2024 (UTC)

And as before, there is no need for hurry.

—Trappist the monk (talk) 20:02, 25 November 2024 (UTC)

I agree, but I don't see why you've set |answered=yes on {{Requested edit}}; won't that mean that it is more likely to get overlooked? OwenBlacker (he/him; Talk) 20:38, 25 November 2024 (UTC)

The live module suite is updated from the sandboxen. Your change is in Module:Citation/CS1/Configuration/sandbox so won't be overlooked when next we do an update.

—Trappist the monk (talk) 21:04, 25 November 2024 (UTC)

Oh, do those happen regularly? — OwenBlacker (he/him; Talk) 23:33, 25 November 2024 (UTC)

No. Headbomb {t · c · p · b} 00:34, 26 November 2024 (UTC)

Then surely {{Requested edit}} should keep |answered=no until the change is rolled out? — OwenBlacker (he/him; Talk) 16:43, 26 November 2024 (UTC)

No, that just clutters Category:Wikipedia fully protected edit requests. The change is noted and queued for the next cs1|2 Module-suite update.

—Trappist the monk (talk) 19:30, 26 November 2024 (UTC)

Semi-protected edit request on 26 November 2024

Additional Reference with my permission as author: https://la84.s3.amazonaws.com/assets/LA84WaterPolo_2021.pdf 2600:8802:5700:5ED:E90D:5669:A932:53C (talk) 17:33, 26 November 2024 (UTC)

Peter L. Snyder, Ph.D. permission for submitting book to wikkipedia 2600:8802:5700:5ED:E90D:5669:A932:53C (talk) 17:35, 26 November 2024 (UTC)

 Not done: This is definitely not the right page to make whatever request this is you are making. PianoDan (talk) 18:00, 26 November 2024 (UTC)

This page (Help talk:Citation Style 1) is for discussion on how CS1 templates format citations, not about which books can be used to cite what. Discussion about citing this book would belong at Talk:Water polo. Discussion about the book's reliability in general would be at Wikipedia:Reliable sources/Noticeboard. Good luck, Rjjⁱⁱⁱ (talk) 23:34, 26 November 2024 (UTC)

Semi-protected edit request on 26 November 2024 (2)

Author permission to publish book: https://la84.s3.amazonaws.com/assets/LA84WaterPolo_2021.pdf through the website LA84Foundation.com 2600:8802:5700:5ED:E90D:5669:A932:53C (talk) 17:52, 26 November 2024 (UTC)

 Not done: Duplicate invalid request. PianoDan (talk) 18:00, 26 November 2024 (UTC)

Internet archive print disability book links

There are a number of links to books which have since lost their accessibility to the general public on Internet Archive (e.g., [4] and [5] of the same book). These are now "[books] available [only] to patrons with print disabilities."

Should the links like these which are not accessible to users without print disabilities be removed, or would it be possible to add another |url-access parameter to signify this? Tule-hog (talk) 20:48, 28 November 2024 (UTC)

Alternatively (as with {{Hopcroft and Ullman 1979}}) should the link be appended to a reference a note? Tule-hog (talk) 01:33, 29 November 2024 (UTC)

DOI prefix limits should be bumped.

We have DOI prefixes in the 10.70000s now. The limit should be bumped to 10.80000s Headbomb {t · c · p · b} 04:05, 1 December 2024 (UTC)

Protected edit request on 1 December 2024

Can someone please add the parameters {{{quote-p}}} and {{{quote-pp}}} as aliases of {{{quote-page}}} and {{{quote-pages}}} respectively to all citation templates, excluding {{cite episode}}, {{cite podcast}}, {{cite AV media}}, {{cite mailing list}}, {{cite newsgroup}}, {{cite serial}}, {{cite sign}} and {{cite speech}}, because they're shorter forms of those parameters, and because the parameters {{{p}}} and {{{pp}}} are already aliases of {{{page}}} and {{{pages}}} respectively on all citation templates excluding those aformentioned ones? PK2 (talk; contributions) 06:42, 1 December 2024 (UTC)

This is something that needs further discussion and later will get synced through the periodic release process if wanted, not something an admin watching the edit requests queue should do immoderately, so deactivating the edit request template. * Pppery * _{it has begun...} 17:31, 1 December 2024 (UTC)

Another generic title

Hello, another generic title that we should be tracking is |title=x.com. There are about 600 of these at the moment. Keith D (talk) 21:23, 1 December 2024 (UTC)

spurious errors when fetching identifier limit data from commons

cs1|2 stores identifier limit values in tabular data on commons: c:Data:CS1/Identifier limits.tab. This little file allows us to keep identifier limits for all wikis using a recent version of the cs1|2 module suite up to date. Alas, there is some sort of spurious 'something' that sometimes causes the data fetch to fail. Currently, when a failure occurs, all cs1|2 templates on a page render a shrieking-red error message: and complaints at various help and village pump pages. The fix is a null edit.

I have tweaked the sandbox so that it traps the boolean return, sets the identifier limits to 99,999,999,999 which will cause all limit checks to pass, and adds the page to Category:CS1 maint: ID limit load fail. Articles collected in the category can be null edited to clear the category. Unlike all other maintenance categories, this category does not have an accompanying maintenance message because it would be repeated by every cs1|2 template.

I tested this new code by disabling the category namespace limit so that a cs1|2 template in my sandbox would emit the error category when I forced a boolean false return from the data fetch.

—Trappist the monk (talk) 01:15, 2 December 2024 (UTC)

This seems like a functional workaround. Is it worth reporting a bug to Phabricator to get at the root cause, which may be affecting other processes on MediaWiki sites? A developer may be able to poke through logs to find out why this failure is occurring. – Jonesey95 (talk) 21:38, 2 December 2024 (UTC)

There is Phab:T229742 which may be related.

—Trappist the monk (talk) 22:32, 2 December 2024 (UTC)

Update s2cid max limit

I'm getting the "Check |s2cid= value" error when I tried to add reference for the paper https://api.semanticscholar.org/CorpusID:274306220, which has ID of 274306220, larger than the currently configured limit of 274000000. Slovborg (talk) 02:17, 2 December 2024 (UTC)

cite episode id parameter silently ignored

{{cite episode}} currently silently ignores |id=. I have been using it to add IMDb identifiers to some items, eg. Special:Diff/1261220079 using {{IMDb ID}}. I propose that we display the |id= parameter just like most other CS1 templates. A more elaborate discussion of IMDb in particular as an identifier is at Wikipedia talk:IMDb link templates § IMDB as an identifier in citations. Daask (talk) 22:44, 4 December 2024 (UTC)

|id= was:

• initially supported at this edit 25 May 2009
• reverted at this edit 7 August 2009
• updated to use Template:Citation/core and simultaneously usurped as a vehicle to support |network= and |station= at this edit 2 April 2012

Because it was the goal of the wikitext-to-module conversion to be transparent, it was necessary to overwrite whatever might be assigned to |id=. I do not recall any discussion here suggesting that we should change that.

I am not enthusiastic about making a change just to support an identifier for a source that editors at WP:RS/P have determined to be generally unreliable.

—Trappist the monk (talk) 00:20, 5 December 2024 (UTC)

I've commented at the other discussion, there's general agreement that IMDb should not appear in references. I don't see how a courtesy link to an unreliable source can help with verification. -- LCU ActivelyDisinterested «@» °∆t° 01:16, 5 December 2024 (UTC)