Help talk:Citation Style 1

(Redirected from Category talk:CS1 maint: numeric names: editors list)
Latest comment: 3 hours ago by Hako9 in topic Access-date < Date
    Citation templates
    ... in conception
    ... and in reality

    template:cite journal edit

    I am citing an article which was published in two journals (one US and the other UK). This is useful information for readers who may have access to one but not the other. I cannot see how to show this. "postscript=" gives an error message and there does not seem to be any other way. Any suggestions? Dudley Miles (talk) 16:10, 25 March 2024 (UTC)Reply

    You have two sources so use two templates. {{cite journal}} (and all of the other cs1|2 templates) are designed to support one source at a time.
    Trappist the monk (talk) 16:20, 25 March 2024 (UTC)Reply
    Citing the same article as two sources will confuse people as it implies that they are different. Standard academic practice is to say "also published...". It is a weakness in the templates that they do not allow for such useful information to be given. Dudley Miles (talk) 16:53, 25 March 2024 (UTC)Reply
    You are still citing two sources so bibliographic details of the US and UK journals are different. You can write:
    <ref>{{cite journal |author=Author |date= |title= |journal=[the US journal] |volume= |issue= |doi=}}
    *also published in: {{cite journal |author=Author |author-mask=2 |date= |title= |journal=[the UK journal] |volume= |issue= |doi=}}</ref>
    Trappist the monk (talk) 17:13, 25 March 2024 (UTC)Reply
    Thanks. That should work. Dudley Miles (talk) 17:16, 25 March 2024 (UTC)Reply

    removed support for |authors=; what about |people= and |credits=? edit

    I have removed support for the deprecated |authors= parameter from the sandbox:

    Cite book comparison
    Wikitext {{cite book|authors=EB Green|title=Title}}
    Live Title. {{cite book}}: Cite uses deprecated parameter |authors= (help)
    Sandbox Title. {{cite book}}: Unknown parameter |authors= ignored (help)

    This leaves us with |people= and |credits= as the only 'free-form' name-list parameters.

    Support for |people= is documented in {{cite av media}}, {{cite mailing list}}, {{cite map}}, {{citation}}. Search results:

    Using |people=:
    • {{cite av media}} ~7900
    • {{cite mailing list}} none
    • {{cite map}} none
    • {{citation}} ~30
    Using undocumented |credits=:
    • {{cite av media}} none
    • {{cite mailing list}} none
    • {{cite map}} none
    • {{citation}} none

    Support for |credits= is documented in {{cite episode}} and {{cite serial}}. Search results:

    Using |credits=:
    • {{cite episode}} ~3300
    • {{cite serial}} ~30
    Using undocumented |people=:

    It seems to me that {{cite mailing list}}, {{cite map}}, and {{citation}} should not be using |people= and |credits=. No doubt there are templates that use |people= and |credits= aside from those mentioned here but similar searches to those above show relatively low usage counts; fewer than 100 articles for {{cite book}}, {{cite journal}}, {{cite news}}, and {{cite web}} combined. It seems to me that use of these two parameters should be limited to {{cite av media}}, {{cite episode}}, and {{cite serial}}.

    Trappist the monk (talk) 16:43, 25 March 2024 (UTC)Reply

    There having been no comment, I have restricted |people= to {{cite av media}}, {{cite episode}}, and {{cite serial}} in the sandbox. |credits= in the live module is already restricted to {{cite episode}} and {{cite serial}}.
    Trappist the monk (talk) 17:04, 2 April 2024 (UTC)Reply
    The typical freeform list on web, news, etc is |others= which flags CS1 maintenance if |author= or |editor= is not also listed.
    "titl_para". othrs_para. 2000-12-31.{{cite web}}: CS1 maint: others (link)
    This seems fine normally, but may not make sense if authorship is deliberately omitted, such as on many websites, or perhaps on 'zines without bylines (and without a named section editor, I suppose). So this parameter use would make sense in e.g. {{cite web}}, however, if a web page is cited in its entirety, and photographs are separately credited in a heavily-illustrated essay while the editorship is omitted.
    CS1 has no documented explicit parameter value for an unlisted author+editor. I've seen it requested and suggested here to use "n.a." similar to "n.d.", but this is not consistent with major citation styles (and per link, only Chicago ever sanctions "Anon." and dashed-out author entries). SamuelRiv (talk) 12:07, 22 April 2024 (UTC)Reply

    Enable publication-date for {{cite journal}} edit

    This proposal was originally made 6 days ago but my wording and explanations were poor.

    WikiProject Bibliographies is devoted to standalone bibliography articles. Its participants have been responsible for a respectable portion of the List of bibliographies on this project. While many of these bibliographies were written manually from creation, many use citation templates to speed up the process and achieve a lower error rate. Many of the bibliographies that now use manual citations originated with templates and were only converted out of a need to reduce the post-expand include size. Because the works themselves are the subject of the article and require more detail and precision than in regular citations, we often find ourselves pushing the limits of citation templates.

    For most of the additional information, corresponding parameters have already been added to {{cite book}}, because the average bibliography article consists mostly of books. Most of what remains can be added after the template. But there is one parameter missing from {{cite journal}} despite already being available in CS1 and having been incorporated into {{cite book}}, that is somewhat frequently encountered and which would benefit from being enabled for {{cite journal}} as well: publication-date. For any book Title, dated 2005 but published 2006, originally typewritten 1930, the output of {{cite book}} would be: Last, First (2005) [1930]. Title. Publisher (published 2006). Most books with "two dates" are better served by the orig-date parameter than by publication-date. In the example I just gave, a book may have 2006 on its front cover but 2005 on its inside cover, with 2005 corresponding to the date the printing began and 2006 to the date of publication after the printing ended. Or 2005 could be the date the printing of the first volume began and 2006 the date the individual volume was printed. And so on.

    The main reason both have to be given in bibliography articles is because differences in date and publication-date displayed prominently enough on works for the same work to be cited in one date in catalogue/database but under another date in a different catalogue/database. Only the best catalogues/databases have both parameters, and the reader's library or digital library may not be such a catalogue. Because the primary purpose of a bibliography article is to help the reader find works on a given subject, providing both years in our bibliographies allows the reader to search all year values the catalogue could have, in addition to letting them know that they have indeed found the correct work where providing only one date would leave them second guessing (especially if there are title differences). Differences between prominently displayed "date" (Jahrgang, ročnik, rocznik etc.) and date of publication values are actually more common for periodicals ({{cite journal}}) than for books.

    Despite the parameter arguably being more important for {{cite journal}} than for {{cite book}}, it has still not been enabled for the former. The interval-discrepancy between Jahrgang (date) and publication date (publication-date) often varies over time. Discrepancies of interval often arise between Jahrgang and volume number and even year number,[†] so you cannot simply enter the Jahrgang in the volume parameter. And because these are bibliography articles, in which the works are the subject of the article, orig-date is often unavailable, thanks to a work being written or typed at a different date, sometimes long before publication, resulting in the work often being cited or even catalogued by the date of writing. Here are some examples of periodicals requiring a separate publication-date parameter in order of increasing complexity:

    Year number would be the closest value to Jahrgang but discrepancies arise when a year is skipped and if it happens more than once, the interval changes. Fortunately, the year number is rarely encountered in catalogues and citations, so although it would be preferable to have a separate year-number parameter, the current guidelines for placing the "year-related value" in the volume parameter work well enough. At least the result is within the citation. The publication-date parameter is also within the citation for {{cite book}}, as it should be for {{cite journal}}.

    My request is to enable the publication-date parameter for {{cite journal}}. Ivan (talk) 21:34, 25 March 2024 (UTC)Reply

    |publication-date= is already available in {{cite journal}}.
    The following
    {{cite journal |title=title |journal=Journal |date=2006 |publication-date=2007 |orig-date=2005}}
    displays as
    "title". Journal (published 2007). 2006 [2005]. -- LCU ActivelyDisinterested «@» °∆t° 21:56, 25 March 2024 (UTC)Reply
    Thank you! I must have been using it incorrectly. Ivan (talk) 22:19, 25 March 2024 (UTC)Reply
    Happy editing. -- LCU ActivelyDisinterested «@» °∆t° 22:36, 25 March 2024 (UTC)Reply
    Also you signature shouldn't hide your actual username (see WP:CUSTOMSIG/P). -- LCU ActivelyDisinterested «@» °∆t° 22:06, 25 March 2024 (UTC)Reply
    Ideally yes, but I don't want my Cyrillic signature to attract uninvited attention since most of the editors on the articles I usually edit are Croats. Fortunately, this RfC allows for signatures that do not correspond exactly to usernames. Ivan (talk) 22:24, 25 March 2024 (UTC)Reply

    Generic name edit

    Can you add "phone" and "email" to the generic name list so you get a "CS1 errors: generic name" error. Thanks Keith D (talk) 18:50, 26 March 2024 (UTC)Reply

    Language is missing in template edit

    Langauge is needed on if a German langauge citation is added. Langauge can therefor not be omitted. Theking2 (talk) 11:34, 27 March 2024 (UTC)Reply

    Not so. From de:Vorlage:Internetquelle/Doku: "|sprache=de für „deutsch“ ist nicht erforderlich …" [… for German is not required …]. -- Michael Bednarek (talk) 11:57, 27 March 2024 (UTC)Reply
    (edit conflict)
    If one is to believe the wikidata list of wikipedias using Module:Citation/CS1 (Module:Citation/CS1 (Q15403807)), does not support cs1|2. If you are having a problem at, you must discuss the problem there.
    Trappist the monk (talk) 12:03, 27 March 2024 (UTC)Reply

    |at= parameter not used for Cite AV Media? edit

    Hey, so I'd like to create a citation for a film which is one of many as part of a multi-disc/multi-film collection, I was thinking about doing something like:

    • Director, D. (dir.) (2000) [1900]. "Film". In Compiler, C. (ed.). Multi-Disc Set. Publisher.

    But I'd really like to add something like |at=Disc 1, Bonus Features, but it doesn't seem like that parameter is valid for this template? Is there a better way to be doing this? Per WP:SAYWHEREYOUGOTIT I'd like the citation to reflect the specific edition I'm citing. Thanks for any advice! Umimmak (talk) 02:36, 29 March 2024 (UTC)Reply

    |at= is an in-source location parameter. The in-source location parameters supported by {{cite av media}} are |minutes= and |time=. Using either of those as a replacement for |at= is semantically incorrect.
    Seems to me that if you are citing some bonus feature you should be citing the bonus feature's title, not its physical location.
    {{cite av media |section=Bonus Feature Title |title=Multi-Disc Set Title |publisher=Publisher |time=01:23:30}}
    "Bonus Feature Title". Multi-Disc Set Title. Publisher. Event occurs at 01:23:30.
    Trappist the monk (talk) 17:57, 29 March 2024 (UTC)Reply
    Ah didn’t think about |section= okay, thank you! Umimmak (talk) 18:08, 29 March 2024 (UTC)Reply

    Page ranges edit

    Should the documentation for, e.g., |pages=, |quote-pages=, recommend use of {{page range}} or subst:page range when page numbers contain hyphens, e.g., |pages={{page-range|A-3|A-5}}? -- Shmuel (Seymour J.) Metz Username:Chatul (talk) 14:19, 29 March 2024 (UTC)Reply

    I don't think we should recommend its usage. IMO it adds complications to already complicated wiki markup. Now every bot, tool, report etc.. that parses wiki markup needs to deal with this template to extract page information. Really how hard is it to use en dash. CS1-2 could even automatically display it as en dash to avoid all this embeded template complication. -- GreenC 14:29, 29 March 2024 (UTC)Reply
    It is true that cs1|2 render correctly formatted page ranges from improperly formatted source parameters so {{page range}} is not required. But... cs1|2 cannot modify wikisource so for those editors who care, using {{page range}} will (once subst'd) produce the proper format in wikisource. Because {{page range}} auto substs (even inside <ref>...</ref> tags), the embedded template complication isn't much of a complication because auto-substing usually occurs within an hour after the edit is saved.
    Use {{page range}} or don't. Recommend it or don't.
    Trappist the monk (talk) 18:11, 29 March 2024 (UTC)Reply

    Author-link in cite templates edit

      Moved to WT:Cite

    I am working on a request from another user at WP:AWBREQ to add author links to citation templates. The first edit I did on the AWB run ended up with, I believe, 159 {{cite web}} templates for the given author. My regex of course identifies each of those templates for adding in the author link, and I dutifully included the author link in all of them as per the request. But before I do this on the hundreds of pages where this is germane, I was wondering whether we are bound to the MOS guide to only link the first instance in an article, or whether that does not apply to references as well.

    TLDR: Should I add author-link to every citation of a given author, or only the first reference on the page? VanIsaac, GHTV contWpWS 01:34, 30 March 2024 (UTC)Reply

    Typically users spot check citations as required, we don't read every one, so if it was previously linked it wouldn't be obvious. In long lists of cites, it's difficult to impossible to know if another cite already linked it. In practice every cite stands on its own like an independent unit. BTW this is great work you are doing. I had an idea how to do this in another discussion. Basically build a database of existing cases of author-link and the |title=, then find other instances of that title that are missing an author-link and add it there. With some sanity error checks. Could be fully automated. -- GreenC 02:01, 30 March 2024 (UTC)Reply
    This isn't really an issue for discussion here – not changing or improving the cs1|2 templates. You would be better off, I think, discussing at WT:CITE.
    Trappist the monk (talk) 02:07, 30 March 2024 (UTC)Reply
    Ahh, much thanks. I got sent here from the redirect at Template talk:Cite, and assumed this was the clearinghouse for that kind of conversation. I'll bring it up at WP:Cite. — Preceding unsigned comment added by Vanisaac (talkcontribs) 02:52, 30 March 2024 (UTC)Reply

    agency in cite magazine edit

    I came across a case where a cite magazine article from India Today was attributed to an agency (Indo-Asian News Service) with no other byline. {{cite magazine}} did not support use of the |agency= parameter. Should it?  — Archer1234 (t·c) 14:10, 31 March 2024 (UTC)Reply

    Lua error edit

    One of the references at The pen is mightier than the sword#Early pre-enlightenment sources is giving "Lua error in Module:Citation/CS1/Date_validation at line 329: attempt to compare string with number." I can't see anything wrong with it from a quick glance. * Pppery * it has begun... 15:37, 31 March 2024 (UTC)Reply

    Also William Rugge (bishop)#cite_note-21 * Pppery * it has begun... 15:48, 31 March 2024 (UTC)Reply
    Trappist the monk (talk) 15:53, 31 March 2024 (UTC)Reply

    Template:Cite journal/doc edit

    Copy of discussion originally at User talk:Mathglot#Template:Cite journal/doc.

    Hi Mathglot, thank you again for your support in the discussion on Module talk:Footnotes. Given what we just discussed there, could you re-visit and examine the revert you did on my edit on Template:Cite journal/doc on 24 March? I now realize I worded the description on my edit very badly/wrongly, and that I should have used {{SfnRef}} in the example. But otherwise what I did on the page, I feel, is basically in line with the result of that talk:Footnotes discussion, and hope you'll see that too, if you revert the revert (with or without saving). If you still stand by your revert, we could discuss further here. If not, we could move to its talk page and discuss how to improve the doc further with my edit as the base. Yiba (talk | contribs) 14:36, 31 March 2024 (UTC)Reply

      Courtesy link: Module talk:Footnotes§ SfnRef

    Hello again, Yiba. I've moved the discussion here from my Talk page, so other interested editors may participate if they wish; they are unlikely to find it on my Talk page. In addition, there is a lot of previous discussion at Module talk:Footnotes§ SfnRef about this.

    Sorry, I still stand by the revert, or at least, parts of it. My original revert (diff) was motivated by your removal of the "Staff writers" expression from the |author= param when there is no author.

    However, your edit at Template:Cite journal/doc made numerous other changes, unrelated to the "Staff writers" issue. Logistically speaking, that's unfortunate, as several smaller edits with each one targeting a different issue would've made it easier to adjust/revert only that portion which needed it; with one, large, monolithic edit targeting essentially unrelated issues, it becomes harder to deal with. Perhaps I was lazy reverting the whole thing, but given the length and wide scope of the discussion that resulted afterward at Module talk:Footnotes§ SfnRef that seems somewhat vindicated. In any case, I see that you believe portions of your original edit are valid, and should be added to the documentation of either Template:Cite journal/doc (or to Template:SfnRef/doc—it's not clear to me which). In order not to fall into the same problem of long discussion here targeting unrelated or loosely related issues, I propose that we use subsections for each separate topic area of your original edit that you wish to retain. I'll start, right after this message, and I hope you list your issues in one subsection each, so the subtopic discussions remain targeted and on-track. Does that seem reasonable to you? Mathglot (talk) 18:11, 31 March 2024 (UTC)Reply

    The edit you reverted also contained the incorrect assumption that journal name will be used in a CITEREF if author is unavailable, and that |ref='s only use is in the creation of CITEREFs for use with {{sfn}}/{{harv}} templates. As neither of these ideas are correct, it was corrected reverted. -- LCU ActivelyDisinterested «@» °∆t° 18:51, 31 March 2024 (UTC)Reply
    Yes, very reasonable. And ActivelyDisinterested is correct. Thanks to both of you. Yiba (talk | contribs) 02:58, 1 April 2024 (UTC)Reply

    author=Staff writers, no byline edit

    Your edit removed |author=<!--Staff writer(s); no by-line.--> from the doc at Template:Cite journal/doc explaining what to do when there is no author. I restored that information in the revert, and as that wording suggestion is standard use throughout several of the citation parameters; it should remain here as well for consistency, so I am not prepared to self-revert in order to remove it. If you see an argument for doing so, how would you deal with equivalent wording at all the other templates? Mathglot (talk) 18:12, 31 March 2024 (UTC)Reply

    I've never seen the point of doing this, however it's probably something that should be discussed first and implemented across all the citation templates if any change is agreed upon. -- LCU ActivelyDisinterested «@» °∆t° 18:53, 31 March 2024 (UTC)Reply
    I'm a supporter of keeping it, but only for this reason: I sometimes like to do ref-improvement gnoming, and a missing author is kind of a big red flag, but an exceedingly common one, as anyone who has used RefRenamer is aware of; so I go look for the author. If after investigation, I find out that there really isn't one, then I am somewhat resentful of the wasted time I spent looking for it, and wished someone would have added the comment. However, I'm not married to that solution, and I would prefer something like |author=none to an html comment. There is precedent for this in params |type=, |ref=, |title-link=, maybe others, and I think that could be a good solution here as well. Mathglot (talk) 19:19, 31 March 2024 (UTC)Reply
    I could see |author=none as a better idea, the hidden comment doesn't seem a great idea. -- LCU ActivelyDisinterested «@» °∆t° 19:36, 31 March 2024 (UTC)Reply
    Fwiw, WorldCat uses none. Mathglot (talk) 19:48, 31 March 2024 (UTC)Reply
    IMO, "staff writers" is more useful, though not in a good way. To me it means massaged press release or ChatGPT. It means that the real journalists won't give their byline to it. See also Alan Smithee. So IMO more informative than "none". 𝕁𝕄𝔽 (talk) 20:32, 31 March 2024 (UTC)Reply
    Agree it's more informative, at least if people are using it right, because it means we know who wrote it, though not by name: it's the staff of the organization (hopefully they filled out |work= or equiv.) which narrows it down to a few people at a given org. That's different, for me, then |author=Anon. which means the person who wrote it chose not to claim credit, and is listed as "Anonymous" in the work, and could be any author anywhere (see WorldCat usage). Finally, "none" to me means, "I looked hard, and couldn't find it"; i.e. nothing on the title page or cover, web page, or in the html <head> tag author field or any of the usual suspects. But honestly, I don't know if it's reasonable to be able to maintain that level of distinction in a citation template author field. It seems very unlikely someone using a plain-text citation rather than a template would do it, and I don't think the citation templates should be held to a higher standard, just because they are templates.
    The "Staff writers" has been around for many years, long before ChatGPT, and I'm not aware of any connection between the two. Press releases are usually cited to the org., and given their purpose almost always have a contact person in their PR dept for inquiries, regardless who authored the release; not that anybody cares. In most citations, you can already specify |type=press release ({{Citation#Title}}), and that is sufficient, imho. Mathglot (talk) 23:21, 31 March 2024 (UTC)Reply
    I'm pretty sure that we've seen this discussion before. Spend some time trawling the archives (if you do, report back here with links to those past discussions). My recollection is that a past discussion ended up recommending |author=<!--Not stated--> as the unknown-author indicator. See Help:Citation Style 1 § Authors where that is recommended.
    Trappist the monk (talk) 23:38, 31 March 2024 (UTC)Reply
    Thanks all. Seems I need to do a lot of reading before continuing here, but here is my preliminary points:
    1. To me, and from legal points of view, "whom the credit and the responsibility belongs" on a published info is very important.
    2. Staff writers, as long as they write in staff writer position/responsibility, do not normally bear the responsibility nor deserve the credit.
    3. Author= indicates who the credit belongs. This does not defy "Author=publisher/publication_name is not always a bad thing." as publishers often do bear the responsibility for what staff writers write. Also, the argument for Author=Anonymous (by Mathglot) is correct.
    4. Leaving "no byline" and "Author=none" aside for now, therefore I feel Author=Staff_Writer, Staffwriter_Surname, or List_of_Staff_Writers is fundamentally wrong.
    5. From a WikiNewbie view, being asked to input into Author= field while the instruction says "when there is no credited author" is idiotic/confusing.
    6. Yes, I feel other Citing template pages/docs need re-writing for the above reasons, so I'm glad having this discussion here.
    Yiba (talk | contribs) 04:01, 1 April 2024 (UTC)Reply
    With respect to #4 (by the way: please see "Numbered list" at Help:Cheatsheet for how to create numbered lists in wikicode), I wonder if you might misunderstand what is meant by |author=<!--Staff writer(s); no by-line.-->. This is something visible only to editors who look at the wikicode, and not to viewers reading the article. The symbols '<!--' and '-->' are comment begin/end delimiters that hide everything between them from viewers. They can be seen by editors editing the page, and it announces (to editors) that, with or without "no byline", we don't have the name of an author. Mathglot (talk) 04:29, 1 April 2024 (UTC)Reply
    I do understad how <!-- info --> is used, and that the line announces (to editors) that, the words 'Staff Writer' or 'No by-line', or name(s) of staff writer(s) as we don't have the name of an author. But your post made me aware there can be some fundamental misunderstanding on my part in constructing the argument. If you see a possibility, please let me know.   Yiba (talk | contribs) 05:10, 1 April 2024 (UTC)Reply
    This may support understanding my concern. The doc currently states:
    To cite a journal article with no credited author
    {{cite journal |author= |date= |title= |url= |journal= |volume= |issue= |pages= |doi= |access-date= }}
    and I am proposing to change it to:
    {{cite journal |date= |title= |journal= |publisher= |volume= |issue= |pages= |doi= |ref={{SfnRef|anchorname|YEAR}} }}
    which solves the credit issue and explains how to link to the citation when there is no author= . I intend to edit Template:SfnRef to explain why SfnRef is needed, and what anchorname is.
    Yiba (talk | contribs) 05:46, 1 April 2024 (UTC)Reply
    Bold editing is a thing, but honestly, given the number of misunderstandings or simple disagreement or pushback you've gotten so far, I'm not sure that bold editing of the {{SfnRef/doc}} page is likely to have the outcome you desire, as any change is still subject to consensus. For example, I don't see a reason to make the change you just proposed now, and it looks familiar to me; didn't you already propose that, or something very like it, at the Module talk:Footnotes discussion? It might make sense to try and achieve consensus first. Mathglot (talk) 06:36, 1 April 2024 (UTC)Reply
    Hmmm, I am surprised how difficult it is to get my points across on this issue. Let me try a different approach:

    Template:Cite journal/doc and other info pages for these templates 1. Recommends use of |author= when there is no credited author, 2. Recommends use of staff writer names in author= in such case, 3. Do not clearly explain |ref= is needed to link if |author= , |last= , etc. is omitted.
    The above mentioned proposal of mine solves all these problems.

    I hope this is understandable.   Yiba (talk | contribs) 00:14, 2 April 2024 (UTC)Reply
    I think you misunderstand. Recommends use of staff writer names in author= in such case the documentation doesn't suggest this, it suggests adding a note that there is no author credited author. For the purposes of the mediwiki software the |author= parameter is still blank.
    If you don't understand how hidden text work Wikipedia:Manual of Style/Hidden text explains it in detail.
    As explained many times the |ref= field is not just for {{sfnref}}, it is also not part of the general template use (as it's only needed for certain situations).
    The author shouldn't duplicate the |publisher= or |journal= name, as this is just misuse of the field. -- LCU ActivelyDisinterested «@» °∆t° 12:28, 2 April 2024 (UTC)Reply

    Thanks. But |author= is listed in the "Most commonly used parameters" for "To cite a journal article with no credited author". It's clear to me I am failing miserably in building a consensus. Here is my last approach for your enjoyment:

    Suppose I am relatively new to Wikipedia, and find my areas of experience and knowledge can contribute to improve Wikipedia articles, so I decide to edit one of the poorly written articles called ABC Memory. I knew there was a good sidebar article about ABC Memory on BCD Journal, where I used to work, and use some info from the column on the Wikipedia page. The article was not signed, but I know such short pieces are normally written by a staff writer John Jones. As a Wiki editor, I don't even know what CS1 stands for, but decide to use a commonly used citation format:
    {{Sfn |BCD Journal |2020 |page=4 }}
    {{Cite journal |title=ABC Memory |journal=CDF Journal |issue=Spring |date=2020 }}
    I omitted |author= entry because I know (book) 'authors' are credited, paid, and responsible for what he/she writes, and Jones is not yet a Senior Editor who gets to sign (and paid/responsible for) what he/she writes and publishes. I'm not sure if he actually wrote the piece, but I know for a fact he is a staff writer there. The pair doesn't work. Then I find the info "To cite a journal article with no credited author" and try:
    {{Sfn |Jones |2020 |page=4 }}
    {{Cite journal|author=<!--Staff writer(s); no by-line.--> |title=ABC Memory |journal=BCD Journal |issue=Spring |date=2020 }}
    but the pair fails to link.
    {{Sfn |<!--Staff writer(s); no by-line.--> |2020 |page=4 }}
    doesn't work.
    {{Sfn | |2020 |page=4 }}
    {{Cite journal |author= |title=ABC Memory |journal=BCD Journal|issue=Spring|date=2020}}
    doesn't work. (@ActivelyDisinterested Blank pair does not link.)
    {{Sfn |by-line |2020 |page=4 }}
    {{Cite journal |author=no by-line |title=ABC Memory |journal=BCD Journal |issue=Spring |date=2020 }}
    doesn't work. I kept trying because I really don't want to name Jones an author. I'm cornered to give in, but:
    {{Sfn |Jones |2020 |page=4 }}
    {{Cite journal |author=John Jones |title=ABC Memory |journal=BCD Journal |issue=Spring |date=2020 }}
    doesn't work. (! This pair does not link. A bug in CITEREF anchor automatic generation handling |author= . One of the reasons why I think |author= should not be there.)
    {{Sfn |Jones |2020 |page=4 }}
    {{Cite journal |last=Jones |first=John |title=ABC Memory |journal=BCD Journal |issue=Spring |date=2020 }}
    This pair finally works (mind you, without |ref= and the editor being fully aware Jones is a staff writer without any copyright responsibility), and I publish it thinking "Well, this is what Wikipedia documentation instructed me to do."

    John gets sued later because I named him as the source despite my strong preference not to name him the author, and the sidebar column was found to have been written by an outside contributor Mrs.X who obtained the sensitive inside info illegally. Mrs.X has long fled abroad, and BCD Journal ends up paying for the damages and sues me for 90% of it because pageview spiked after my edit and the page attracted 9 times more number of pageviews than their subscription base. You could imagine how 'I' feel about Wikipedia documentation.

    To all of you, I'm sorry to have wasted your time. @Mathglot please don't worry, I will refrain from editing these documentation.   Yiba (talk | contribs) 14:32, 2 April 2024 (UTC)Reply

    {{Sfn |<!--Staff writer(s); no by-line.--> |2020 |page=4 }} is the same as {{sfn||2020|p=4}}.
    You are still not understanding the nature of hidden comments. For all effects they don't exist. If you add a hidden comment to |author= it's the same as the field being blank.
    Also |author= is a substitute for |last= and |first=, so:
    {{Cite journal |author=John Jones |title=ABC Memory |journal=BCD Journal |issue=Spring |date=2020 }} would need {{sfn}} to be setup as {{sfn|John Jones|2020|p=4}} to work.
    I fear any changes you make to the documentation are not going to add much value until you get a better understanding of how things work. -- LCU ActivelyDisinterested «@» °∆t° 16:05, 2 April 2024 (UTC)Reply
    (edit conflict) Responding only to this comment:

    A bug in CITEREF anchor automatic generation handling

    That is not a bug, but an error in the use of sfn parameters. While |last= is recommended in short citations and not |author=, it will still work if you use it properly. For example, this generates #CITEREFJohn_Jones2020 if you place the full author in the Sfn param (not recommended!) and links properly:
    Markup Renders as
    Some fact.{{Sfn|John Jones|2020|page=4}}
    === References ===
    === Bibliography ===
    * {{Cite journal|author=John Jones |title=ABC Memory |journal=BCD Journal }}

    Some fact.[1]

    1. ^ John Jones 2020, p. 4.
    • John Jones (2020). "ABC Memory". BCD Journal.
    but don't do that; please use {{sfn}} following the instructions given in the doc. So I don't see any CITEREF bug here. If I've missed what you meant, please start a new discussion on this page and lay out a description of the bug, along with an example if possible. Thanks, Mathglot (talk) 16:12, 2 April 2024 (UTC)Reply
    Post-ec: I have to agree with AD's comment; if you don't understand how it works and should work, it's hard to see how you can improve the doc, but I appreciate all the effort you have put into trying to improve it as that is a worthwhile goal. Mathglot (talk) 16:26, 2 April 2024 (UTC)Reply
    Completely agree, and please don't take my comments as discouragement. Get some more experience of editing articles, ask questions (there's always someone who will be willing to explain), and if you still interested then improvement will be warmly welcomed. -- LCU ActivelyDisinterested «@» °∆t° 16:41, 2 April 2024 (UTC)Reply

    Add tracking categories for additional foreign language sources? edit

    Apologies if I'm mistaken about something, but should there be Category:CS1 Yue Chinese-language sources (yue) and Category:CS1 Min Nan Chinese-language sources (nan) to match Category:CS1 Chinese-language sources (zh)? See also Category:Articles containing Yue Chinese-language text et al. Remsense 18:33, 3 April 2024 (UTC)Reply

    cs1|2 categorizes the two-character language tags into individual categories because those are the most commonly used languages. All of languages that have three-character language tags (there are some 8000+) are categorized into Category:CS1 foreign language sources (ISO 639-2) sorted by tag. Articles using |language=nan are categorized at N and articles using |language=yue are categorized at Y.
    Alternately there are (imperfect) search results:
    for nan
    for yue
    Trappist the monk (talk) 19:28, 3 April 2024 (UTC)Reply
    Ah, my bad! That's a fine enough solution, thank you. Remsense 20:32, 3 April 2024 (UTC)Reply

    cite report: number, id, docket edit

    Testing {{cite report}}, {{cite tech report}}, and {{cite thesis}} I find that |number=, |docket=, and |id= are used inconsistently in an undocumented manner. (See also previous related discussion: Cite report issue parameter not displaying (May 2023).)

    In report and thesis, |number= appears to not be used at all, while |docket= and |id= are aliases for an ending bare text in report, and separable parameters in thesis (with the word "Docket" prepended, unlike in report). Meanwhile, |number= and |id= are aliases in tech report, also mutually incompatible. Particularly problematic is that |id= is specified as A unique identifier, used where none of the specialized identifiers are applicable -- this is semantically distinct from all uses of |number= in CS1, and from what appears to be their documented metadata.

    {{Cite_report |author=Alex |date=May 1999 |docket=DOC 27 |id=Celex 3334 |number=777 |publisher=BYU |title=Tango}}


    Alex (May 1999). Tango (Report). BYU. DOC 27.


    Alex (May 1999). Tango (Thesis). BYU. Docket DOC 27. Celex 3334.

    Also, I suggest considering again the suggestion of @Tcr25: from the linked previous discussion, that instead of outputting report number/docket at the end of the citation, it should follow the title and document type. Currently it outputs after page number, which only makes sense if it's an external catalogue identifier (like |id= is usually used for) and not, as is often the case with technical reports, splashed across the front page as part of the title. SamuelRiv (talk) 22:16, 4 April 2024 (UTC)Reply

    You should not be surprised that {{cite report}}, {{cite tech report}}, and {{cite thesis}} are 'inconsistent'. Each of those templates was created at different dates by different editors:
    Each of those templates then developed along their own paths until they were each reimplemented using the meta-template {{citation/core}}; again at different dates and different editors:
    • {{cite report}}: 30 November 2011‎ by Editor Fifelfoo
    • {{cite tech report}}: 14 September 2011‎ by Editor Gadget850
    • {{cite thesis}}: 25 March 2011‎ by Editor Headbomb
    Development continued along their own paths until migrated to Module:Citation/CS1; also at different times by me:
    • {{cite report}}: 15 February 2015‎
    • {{cite tech report}}: 9 November 2013
    • {{cite thesis}}: 9 November 2013‎
    I can't speak to the migration to {{citation/core}} but when I migrated these templates to Module:Citation/CS1, the goal was to make the migration more-or-less transparent so differences among them inherited from their individual developmental paths were retained in the module version. No doubt, since those migrations, the individual templates have continued to differ and likely continued to diverge.
    Were these templates developed simultaneously by a single author, they would probably have been much more consistent but that is not the way of a wiki.
    Trappist the monk (talk) 23:38, 4 April 2024 (UTC)Reply
    I'm not sure I understand. Is this acknowledging that this is a bug? If so, is this to imply that current maintainers will address this in a future version, or else give permission for me to fix it now? SamuelRiv (talk) 22:24, 21 April 2024 (UTC)Reply
    All that I provided was a history to explain why those templates are the way they are. Do you need permission to propose a change to these templates? Each module in the suite has a sandbox that anyone can edit so long as they don't break anything.
    Trappist the monk (talk) 15:05, 22 April 2024 (UTC)Reply

    Can "mode=cs1/cs2" be handled like date formatting? edit

    This question stems from a recent realization that the Visual Editor offers the Citation Style 2 {{citation}} template as the default citation method. I remember as a new editor not being clear on why {{cite web}} and {{citation}} had a different appearance. My first thought was the Visual Editor should autofill "mode=cs1" if it's trying to use {{citation}} as a quick machine-generated reference. My second thought was, why do we have to specify in each template usage? {{Use dmy dates}} gives a consistent format to every citation on the page. Can something similar be done with the punctuation format? ({{use cs1}} & {{use cs2}}) Rjjiii (talk) 04:35, 8 April 2024 (UTC)Reply

    I'll just drop my semi-annual comment that the output of CS1 and CS2 are so similar that they could be merged together and the distinction between them finally removed. My preference would be to use the comma separation and capitalization of CS2 with the terminal period of CS1, allowing the option to override that terminal period. If they were harmonized into a single style, it wouldn't matter if someone used {{citation}} and someone else used {{cite web}} on the same article. Imzadi 1979  04:44, 8 April 2024 (UTC)Reply
    {{cs1 config|cs1}} or {{cs1 config|cs2}}
    Trappist the monk (talk) 12:18, 8 April 2024 (UTC)Reply
    That's fantastic! Do you mind if I add some examples to the documentation? Or create a kind of announcement at WP:VPT?
    There's probably no clean answer to this question, but I wonder what it would take make CS1 style the default for citation templates currently using CS2?
    • We could open a discussion at WP:VPT, and post notices. Probably an RfC to show consensus.
    • There are a bunch of niche templates that use {{Citation}}; I could add |mode=cs2 to keep their formatting and post a {{please see}} notice on their talk pages so that it would be opt-in.
    • I'm not too familiar with bots, but if a bot would add {{cs1 config|cs2}} to every article with 3:1 ratio of CS2:CS1 templates, I think that could help to frame this as supporting WP:CITEVAR rather contesting it; a bot adding {{cs1 config}} to pages where {{citation}} is the primary style could also function as a way to announce this editors who want CS2, maybe with a link to the RfC and clear instructions on how to auto-CS2 the content they create.
    I feel like this would be a much cleaner solution than trying to fix the auto-citation in the VisualEditor. Rjjiii (talk) 14:23, 10 April 2024 (UTC)Reply
    If you think that the documentation can be improved, and know how to do it, please do. I fail to understand how WP:VPT is pertinent; in general issues pertaining to cs1|2 are not 'technical'. A clean answer requires a 'clean' description that clearly states your objective. I am not at all clear on what it is that you are asking.
    Trappist the monk (talk) 14:39, 10 April 2024 (UTC)Reply
    I think it would make the citation templates easier to use for editors and more consistent for readers if CS1 becomes the default style. I mention VPT and other areas of discussion because I also think that would be a significant change where people would want advance notice and an explanation. Rjjiii (talk) 15:10, 10 April 2024 (UTC)Reply
    The template should probably be named {{cs config}} rather than {{cs1 config}} btw. Headbomb {t · c · p · b} 23:00, 10 April 2024 (UTC)Reply
    CS1. Is. Too ugly. And it. Would break. A lot. Of formatting. Where editors. Have not anticipated. That lots. Of useless. Periods. Would be added. If CS2 became the default style, as Imzadi suggested, I think it would be less problematic. —David Eppstein (talk) 06:12, 11 April 2024 (UTC)Reply
    I prefer the periods for dividing specific groups of information, not least because I prefer semicolons for dividing author name pairs. As someone who has fixed a lot of |author= parameters with multiple names in them, semicolons are invaluable for denominating a specific author name pair. Commas would hence Suck to then divide authors from whatever comes after.
    I assume this is an actual point in favor of periods rather than mere preference, as voiced above. (I make this comment in the general.) Izno (talk) 17:43, 11 April 2024 (UTC)Reply

    Error tracking category edit

    The documentation for {{Cite AV media notes}} gives examples that use the others= parameter with the name of an artist or band without providing a value for |author= or |editor=. Further, the template documentation makes no mention of the requirement that others= be only used with primrry editorship or authorship information. However, such usage places articles in the Category:CS1 maint: others in cite AV media (notes) category. The documentation there says that the others= can't stand alone.

    Which is correct? -- Mikeblas (talk) 03:13, 9 April 2024 (UTC)Reply

    Ah, I see. Is it that first= and last= used in the examples serve as an alias for the |author parameter? That's not intuitive, as first= and last= are multiple parameters, and author= is singular. And, even if so, the documentation makes no mention of the requirement. -- Mikeblas (talk) 03:20, 9 April 2024 (UTC)Reply
    As the template documentation shows, |author= is an alias of |last=; see Template:Cite AV media notes § Authors. Even the TemplateData 'documentation' (such as it is) shows that these parameters are aliases of each other; see Template:Cite AV media notes § TemplateData.
    The template documentation it is not protected. If you believe that the template documentation can be improved, you are free to do so. The documentation for |last=, |author=, and |others= is at Template:Citation Style documentation/author. Remember that the documentation template is used by all cs1|2 templates. If you use VE, consider improving the TemplateData.
    Similarly, Category:CS1 maint: others in cite AV media (notes) is not protected so you are free to improve the documentation there.
    Trappist the monk (talk) 12:17, 9 April 2024 (UTC)Reply
    I know that I'm allowed to edit the documentation. I'm trying to figure out which is correct: the template documentation, or the error tracking category documentation. It seems like the error tracking category documentation is correct, but I'm not 100% positive. Does anyone know? -- Mikeblas (talk) 15:53, 9 April 2024 (UTC)Reply
    I suppose that both are correct as far as they go. The maintenance categories are added whenever the cs1|2 template does not have any authors or editors but does list others names in |others=.
    Trappist the monk (talk) 14:51, 10 April 2024 (UTC)Reply
    That maintenance category is the subject of several discussions now. Probably we need to modify the documentation at this point specifically to say this maintenance category for this pair of templates is the lowest of low priorities and not to worry about it (for now). Izno (talk) 22:56, 10 April 2024 (UTC)Reply
    It's strange that most of those previous discussions point out the documentation problem, but here we have the claim that the documentation is correct. I have added some notes to the doc about the interplay of the others= parameter.
    FeRDNYC, in one of those older discussions you say that the error message produced here is not actionable. Can you explain why that is? That is, why isn't the remediation action to remove the others= parameter, or place its value in author=? -- Mikeblas (talk) 18:32, 13 April 2024 (UTC)Reply
    It is not obvious what the replacement is in the vast majority of uses of these two templates. People will cite any myriad of values in these parameters that do not obviously to me line up with the intent of |author= or other current equivalents. Take 10.000 Nights of Thunder as a prime example of the use of these templates. The band is not likely to be the author of the liner notes, or at least not all of them, if even the physical notes specify who the author of the notes are (many, maybe even most, probably don't). The current examples at Template:Cite AV media notes reflect this use of placing the artist in |others= and I don't think the documentation there is necessarily wrong to say so. Template:Cite AV media is better in some ways and worse in others as it suggests that we should add the role some significant person to the media played in the |others=, but which again does not necessarily line up with the expectations for |author=. Izno (talk) 20:09, 14 April 2024 (UTC)Reply
    @Mikeblas: Precisely as Izno says: The band is not likely to be the author of the liner notes. It's often extremely difficult to find out who wrote the liner notes for a given piece of media; rarely are they explicitly credited somewhere in the text. But without that information, currently the template "considers itself" incompletely filled out. IMHO that's an unreasonable expectation, making the tracking category nothing but noise. That being said, "working around it" by simply crediting the band as the authors turns the citation from incomplete to incorrect, which is not an improvement. If we want the tracking category to go away, we should make the tracking category go away, not corrupt our citations to satisfy its requirements. FeRDNYC (talk) 13:21, 15 April 2024 (UTC)Reply
    Thanks for the explanation. I guess I'm seeing it as any other staff-written publication. Some specific author(s) certainly wrote an article, but since they're staff, we just credit it to the publisher ... Crediting Blondie or Reuters is just the same. The documentation already advises this usage: author: this parameter is used to hold the name of an organizational author (e.g. a committee) or the complete name (first and last) of a single person;. -- Mikeblas (talk) 13:30, 15 April 2024 (UTC)Reply
    @Mikeblas: We do do that, but only when the organizational author is given a byline, as in Reuters articles. That's a very different situation than crediting a band as the author of their album's liner notes. {{Cite press release}}, for example, explicitly documents and allows for |author=<!--Not stated--> as a parameter, because it's exceedingly common for press releases to be published without a credited author.
    My argument is that {{Cite AV media}} and {{Cite AV media notes}} fall more into the press release category than the {{Cite web}} / {{Cite news}} category. (And, that being said, {{Cite press release|author=<!--Not stated-->|others=something}} will also trigger inclusion in Category:CS1 maint: others.) FeRDNYC (talk) 14:19, 15 April 2024 (UTC)Reply
    I was thinking my Reuters example wasn't really as good a match as I had originally thought. Maybe "The Committee for Studying Something that gets Studied". Might be one, might be multiple authors, but all not specifically named in the Committee's report. Either way, in the case of liner notes or media booklets, it doesn't seem particularly important to note the author -- it's self-published by the band or producer or their publisher. That seems like what we ought to be documenting. Why would {{Cite AV media notes}} not also allow a "not stated" author? -- Mikeblas (talk) 15:16, 15 April 2024 (UTC)Reply

    Template:Cs1 config and Cite templates compatibility edit

    {{cs1 config|name-list-style=vanc}} and cite with non-Latin author generates an error.

    Example (added |name-list-style=vanc to cite to generate error):

    노 성환 (April 2021). "한국 오줌싸개 치유에 대한 비교민속학적 고찰" [Korean Bedwetter and East Asian Folklore]. 비교민속학 (in Korean). 73: 45–88. doi:10.38078/ACF.2021.4.73.45. ISSN 1598-1010. S2CID 238041634. {{cite journal}}: Vancouver style error: non-Latin character in name 1 (help)

    I know translating the author would avoid the error. (There are other work-arounds.) But I believe a specific cite should be able to override a global setting.

    User-duck (talk) 15:34, 10 April 2024 (UTC)Reply

    If you want Vancouver styling you must comply with the (somewhat relaxed) Vancouver system rules. For |name-list-style=vanc, |last<n>= and |first<n>= must hold names written using the Latin character set.
    Trappist the monk (talk) 16:16, 10 April 2024 (UTC)Reply

    Cite magazine parameters edit

    Is it possible to automatically show the volume and issue parameters when first opening it up in the visual editor? And then, perhaps, hide the PMID parameter that does automatically get added; that is more for journals. I do not know of many magazines archived by PubMed. Why? I Ask (talk) 03:04, 13 April 2024 (UTC)Reply

      Done Thanks for the feedback. It may take a bit for the changes to take effect, Rjjiii (talk) 03:16, 13 April 2024 (UTC)Reply
    Thank you! Why? I Ask (talk) 03:21, 13 April 2024 (UTC)Reply

    collaboration parameter in cite journal edit

    I'm citing this paper, which is written by 6 authors on behalf of a wider collaboration. When I cite it in Myalgic encephalomyelitis/chronic fatigue syndrome as [1], it generates an etal, per documentation of the collaboration parameter. Is there a way to stop the etal? With vauthors, I get an error if I simply put the collaboration after the author list. Anybody know a way around this?


    1. ^ Sotzny F, Blanco J, Capelli E, Castro-Marrero J, Steiner S, Murovska M, Scheibenbogen C, et al. (European Network on ME/CFS (EUROMENE)) (June 2018). "Myalgic Encephalomyelitis/Chronic Fatigue Syndrome – Evidence for an autoimmune disease". Autoimmunity Reviews. 17 (6): 601–609. doi:10.1016/j.autrev.2018.01.009. PMID 29635081.

    —Femke 🐦 (talk) 14:08, 13 April 2024 (UTC)Reply

    I count seven names. Doesn't WP:MED somewhere suggest that name lists should be limited to not more than six names? The old {{vcite2 journal}} (now a redirect along with the since deleted Module:ParseVauthors which implemented it) automatically imposed a six name limit. That template was written primarily for use by the WP:MED community.
    I'm not sure that a group of authors writing on behalf of some entity means that the entity is a collaborator. Were it me, I would omit |collaborator= entirely. If you must include EUROMENE, you can write the template:
    {{cite journal |vauthors=Sotzny F, Blanco J, Capelli E, Castro-Marrero J, Steiner S, Murovska M, Scheibenbogen C, ((European Network on ME/CFS (EUROMENE))) |date=June 2018 |title=Myalgic Encephalomyelitis/Chronic Fatigue Syndrome – Evidence for an autoimmune disease |journal=Autoimmunity Reviews |volume=17 |issue=6 |pages=601–609 |doi=10.1016/j.autrev.2018.01.009 |pmid=29635081 |doi-access=free}}
    Sotzny F, Blanco J, Capelli E, Castro-Marrero J, Steiner S, Murovska M, Scheibenbogen C, European Network on ME/CFS (EUROMENE) (June 2018). "Myalgic Encephalomyelitis/Chronic Fatigue Syndrome – Evidence for an autoimmune disease". Autoimmunity Reviews. 17 (6): 601–609. doi:10.1016/j.autrev.2018.01.009. PMID 29635081.
    Trappist the monk (talk) 15:21, 13 April 2024 (UTC)Reply
    I can't count.. Useful to learn of a soft recommendation for 6 authors at MOS:MED! Thanks :). As these people wrote the paper "on behalf of" EUROMENE, that does make it a collaboration, right? Or am I missing what this parameter is supposed to do? Simple solution seems to be to omit the 7th author, and simply use collaboration parameter as is. —Femke 🐦 (talk) 15:30, 13 April 2024 (UTC)Reply
    The documentation for |collaboration= says (in part):
    Name of a group of authors or collaborators
    That, to me, says that the group actually participated in the writing. Because the group participated in the writing, etal is appropriate. When authors write on behalf of a group, the group is not a participant in the writing so should not be listed as a contributor.
    Trappist the monk (talk) 16:40, 13 April 2024 (UTC)Reply
    et al. is not appropriate when the entire group is listed. This has been pointed out and ignored for years now. Headbomb {t · c · p · b} 19:28, 13 April 2024 (UTC)Reply

    How to indicate an issue is a supplement? edit

    What is the proper way to indicate that an issue is a supplement? GobsPint (talk) 19:13, 13 April 2024 (UTC)Reply

    If unnumbered, |issue=Suppl. If numbered, |issue=Suppl. 3. Headbomb {t · c · p · b} 19:33, 13 April 2024 (UTC)Reply

    COinS has rft.part for use with journal objects so we could (should?) add an appropriate parameter: |supplement= that would cause the template to render the 'Suppl.' (cs1) or 'suppl.' (cs2) static text as part of the |issue= rendering. I suppose that the parameter rendering might look like this:
    |volume=V |issue=4 |supplement=3V (4 Suppl. 3)
    |volume=V |issue=4 |supplement=<title>V (4 Suppl. <title>)
    |volume=V |supplement=yesV (Suppl) – where yes is a special keyword; more-or-less equivalent to |issue=Suppl
    Other renderings?
    Trappist the monk (talk) 13:32, 16 April 2024 (UTC)Reply

    CS1 errors: generic name edit

    Hello, the list on the category page includes "email" but does not appear to cause an error. On Politics of Kaliningrad Oblast

    protected, email. "Kaliningrad Separatism Again on the Rise".

    Keith D (talk) 20:57, 15 April 2024 (UTC)Reply

    Fixed in the sandbox.
    {{cite news/new |last=protected |first=email |title=Kaliningrad Separatism Again on the Rise }}
    protected, email. "Kaliningrad Separatism Again on the Rise". {{cite news}}: |first= has generic name (help)
    Trappist the monk (talk) 21:54, 15 April 2024 (UTC)Reply

    The url-access lock icon becomes huge if the linked source is a PDF file edit

    Like this cite magazine from Maidenhead Locator System:

    Tyson, Edmund, N5JTY (January 1989). "Conversion between geodetic and grid locator systems" (PDF). QST Magazine. Newington, CT: American Radio Relay League. pp. 29–30, 43. Retrieved 2018-03-09.{{cite magazine}}: CS1 maint: multiple names: authors list (link) CS1 maint: numeric names: authors list (link)

    Removing ".pdf" from the link makes the lock small again. AstonishingTunesAdmirer 連絡 02:17, 16 April 2024 (UTC)Reply

    On the mobile theme it looks fine.[1] The template's CSS includes "background-size: contain;" for the Vector themes but not Minerva or Timeless. Toggling that off seems to make it the correct size. Rjjiii (talk) 03:13, 16 April 2024 (UTC)Reply
    I'm using the Vector 2010 skin on mobile (using the desktop site), and the icon also looks huge. -- LCU ActivelyDisinterested «@» °∆t° 09:58, 16 April 2024 (UTC)Reply
    Toggling background-size: contain; made no difference for me, but disabling padding: 8px 18px 8px 0px; set the smaller size. (using monobook skin) —  Jts1882 | talk  14:40, 16 April 2024 (UTC)Reply
    Where did you do that? padding: 8px 18px 8px 0px; does not exist in Module:Citation/CS1/styles.css.
    Trappist the monk (talk) 14:47, 16 April 2024 (UTC)Reply
    It's from MediaWiki:Common.css, found it while searching if this bug was reported previously. AstonishingTunesAdmirer 連絡 14:49, 16 April 2024 (UTC)Reply
    You have to toggle the bg-contain rule twice because :not(.skin-minerva):not(.skin-timeless) triggers once for each skin. Removing either this or the padding works. Izno (talk) 16:15, 16 April 2024 (UTC)Reply
    Pinging @Izno who has much more experience with css than I.
    Trappist the monk (talk) 13:16, 16 April 2024 (UTC)Reply
    I've overridden the padding from Common.css in the sandbox, the effects of which can be seen already on this page (since the sandbox styles are presently on the page after the non-sandbox styles). Izno (talk) 16:47, 16 April 2024 (UTC)Reply
    I'm still seeing the over large padlock, should it have changed? -- LCU ActivelyDisinterested «@» °∆t° 18:22, 16 April 2024 (UTC)Reply
    Probably just caching or something. User:Izno/Sandbox is fine for me. Izno (talk) 20:36, 16 April 2024 (UTC)Reply
    Thanks! That fixed it, Rjjiii (talk) 00:25, 17 April 2024 (UTC)Reply

    Mysterious Harv and Sfn no-target error edit

    In Minkowski inequality, the {{sfn}} footnote to Bahouri, Chemin & Danchin 2011 and the reference generated by the template {{Bahouri Chemin Danchin Fourier Analysis and Nonlinear Partial Differential Equations 2011}} are together somehow generating a "Harv and Sfn no-target error" categorization (look at the text of the footnote id="cite_note-FOOTNOTEBahouriCheminDanchin20114-3" in the source of the generated article) but without generating a script-highlighted error nor any actual problem in harv/sfn link targeting. Does anyone know why this error occurs and whether there is something to do (hopefully without having to subst the citation template) to make it go away? —David Eppstein (talk) 06:45, 18 April 2024 (UTC)Reply

    This behaviour is explained at Category:Harv and Sfn template errors#Resolving errors, and the following section, "Current limitations and false-positive errors". It can be resolved by adding the template {{Sfn whitelist}}, or just be ignored. -- Michael Bednarek (talk) 10:38, 18 April 2024 (UTC)Reply
    This is a limitation of the mediawiki software, the check happens before the templates are expanded. -- LCU ActivelyDisinterested «@» °∆t° 11:43, 18 April 2024 (UTC)Reply
    Where do you get that idea? MediaWiki software has nothing to do with this error message. The error message is emitted by Module:Footnotes because the module can only see the wrapper template call in the wikitext. The Module cannot look into the wrapper template to fetch names and date from the wrapped {{cite book}} template. The check occurs during the expansion of each {{sfn}} / {{harv}} template.
    Trappist the monk (talk) 11:56, 18 April 2024 (UTC)Reply
    Sorry I thought the check could only occur at that point due to a limitation of mediawiki, if not could the check not happen later (or the false positive be quashed after the expansion bof the templates)? -- LCU ActivelyDisinterested «@» °∆t° 16:43, 18 April 2024 (UTC)Reply
    Thanks all. sfn whitelist did the trick. Resolving this would have been easier if the error were visible rather than having to grovel through the rendered html source to find the offending citeref. —David Eppstein (talk) 01:10, 19 April 2024 (UTC)Reply
    When the error messages were first introduced we didn't yet have {{sfn whitelist}} or Module:Footnotes/whitelist so editors complained. You can show these error messages with the css described at Category:Harv and Sfn no-target errors#Displaying error messages method 3.
    Trappist the monk (talk) 01:16, 19 April 2024 (UTC)Reply

    Current format for issues is odd, proposal for additional parameters edit

    Some magazines don't advertise the issue number as clearly on the front magazine, and it can take a lot of extra effort to find the correct issue if they are cited but missing important information. We may have to buy the magazine itself just to confirm the issue number and sometimes there is no issue number at all and they label the issue by month/date, or they will have it by Holiday. It would be easier to add an additional parameter specifically for the name of the issue.

    Current version
    <ref name="Famitsu">{{cite magazine |title= パタポン3 |issue=May 5, 2011 |magazine=[[Famitsu]] |language=Japanese |date=April 21, 2011}}</ref>

    "パタポン3". Famitsu (in Japanese). No. May 5, 2011. April 21, 2011.

    Looks awkward with the No. in front of it.

    Proposed change
    <ref name="Famitsu">{{cite magazine |title= パタポン3 |issue-name=May 5, 2011 |magazine=[[Famitsu]] |language=Japanese |date=April 21, 2011}}</ref>

    "パタポン3". Famitsu (in Japanese). May 5, 2011 issue. April 21, 2011.

    ^^A proper issue name.

    <ref name="Famitsu">{{cite magazine |title= パタポン3 |issue-name=May 5, 2011 |issue-Num=999|magazine=[[Famitsu]] |language=Japanese |date=April 21, 2011}}</ref>

    "パタポン3". Famitsu (in Japanese). May 5, 2011 issue (No.999). April 21, 2011.

    ^^For both.

    This will simplify things and make the citation easier to read.Blue Pumpkin Pie (talk) 17:25, 19 April 2024 (UTC)Reply

    Is JSTOR really free access? edit

    I tried to describe jstor-access as registration, because the article in question could only be read if you signed up for a JSTOR account. But I got an error, and the template doc for cite journal says that JSTOR can only be marked as free. While it's true that once you sign up for the site you can read 100 articles without paying, I think it's misleading to mark it as free access, when it isn't actually public. Is there logic behind this that I'm missing? Pingnova (talk) 17:51, 21 April 2024 (UTC)Reply

    We do not highlight the norm. Sources linked from named identifiers (|jstor=, |doi=, etc) are normally hidden behind some sort of paywall or registration barrier. Because that is the normal case, flagging those sources with |jstor-access=registration, |jstor-access=limited, or |jstor-access=subscription is redundant and would add unnecessary clutter to the wikitext and to the rendered reference. When an occasional source at JSTOR is free-to-read, it is appropriate to mark that source with |jstor-access=free.
    Trappist the monk (talk) 18:15, 21 April 2024 (UTC)Reply

    Period following ellipsis and title punctuation edit

    In CS1 style it appears a terminal period is included following exclamation and question marks, but is omitted following ellipses (3 dots) (for fields unenclosed in "quotation marks"):

    • athr_p (2000). J'accuse!. publ_p.
    • athr_p (2000). J'accuse?. publ_p.
    • athr_p (2000). J'accuse... publ_p. [2 dots]
    • athr_p (2000). J'accuse... publ_p. [3 dots]
    • athr_p (2000). J'accuse... publ_p. [4 dots]
    • athr_p (2000), J'accuse..., publ_p [3 dots, mode=cs2]

    I only found one previous post from 2023-11-22 on this. At issue is that no style guide that I know of, that uses terminal punctuation in citations, omits the punctuation following an ellipsis. MLA citation has the ellipsis follow the stop] while APA and Chicago precede a stop (but the latter two refs do not discuss citations). APA has a citation guideline using an ellipsis for 7+ authors without punctuation, but the ellipsis is within the author list and not terminal: "a_1, a_2, ... a_N.". The only style guide saying that an ellipsis should not add adjacent punctuation is Chicago's FAQ response on fiction style.

    Regarding question or exclamation points and the citation style punctuation, they style guides get a bit more subtle. Generally (APA MLA and Chicago) citations usually have periods or commas be superseded by "stronger marks", but when the reading is more prose-like as in a bibliography entry, the comma is retained.

    Given all this, I suggest removing the code that omits citation-style punctuation following 3-dot ellipses. SamuelRiv (talk) 15:17, 22 April 2024 (UTC)Reply

    Twin ISSN in cite journal edit

    The following discussion is closed and will soon be archived.

    Many magazines now have two ISSNs, one for print and one for Internet. In typical printed cites they are published with a comma in between. It would be great if the issn= parameter in {{Cite journal}} would allow that, too. Викидим (talk) 18:47, 23 April 2024 (UTC)Reply

    Are you looking for |eissn= which already exists and can be used with |issn=? And, really, do you need either issn? There are those who believe that issn is mere pointless clutter.
    Trappist the monk (talk) 18:55, 23 April 2024 (UTC)Reply
    Got it, thank you. Will re-address my request to Citer tool creators. To me, ISSN is like ISBN - not necessary, but a useful tool when the cite is unclear / mistyped. Викидим (talk) 19:24, 23 April 2024 (UTC)Reply

    Access-date < Date edit

    Edit preview doesn't show an error if access-date is earlier than date parameter. — hako9 (talk) 01:02, 24 April 2024 (UTC)Reply