Help talk:Citation Style 1
This is the talk page for discussing improvements to the Help:Citation Style 1 and the CS1 templates page. |
|
Archives: Index, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 62, 63, 64, 65, 66, 67, 68, 69, 70, 71, 72, 73, 74, 75, 76, 77, 78, 79, 80, 81, 82, 83, 84, 85, 86, 87, 88, 89, 90, 91, 92, 93, 94, 95, 96, 97Auto-archiving period: 20 days |
To help centralize discussions and keep related topics together, the talk pages for all Citation Style 1 and Citation Style 2 templates and modules redirect here. A list of those talk pages and their historical archives can be found here. |
This help page does not require a rating on Wikipedia's content assessment scale. It is of interest to multiple WikiProjects. | ||||||||||||||||||||||||||||
|
Other talk page banners | ||||
|
|
Internet archive print disability book links
[edit]There are a number of links to books which have since lost their accessibility to the general public on Internet Archive (e.g., [1] and [2] 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)- @Tule-hog: I don't think any of the values in the current current scheme accurately represent the access status you have described. I'd be inclined to leave
|url-access=
blank and create a new template to indicate this information after the citation template, similar to many of the templates in Category:External link note templates. Daask (talk) 17:06, 16 December 2024 (UTC)- I went with
{{Internet Archive patrons}}
as a temporary solution, which allows for tracking pages (and ref-templates) that use it (which should make future modifications more streamline-able). Tule-hog (talk) 17:14, 16 December 2024 (UTC)- User:Tule-hog, the book is fully searchable (click the magnifying glass). And, you can open it to any page like page 42. This is the same as many books at Google Books. I would be careful about tagging books as "inaccessible" because there are many levels and types of access, beyond complete full access. We certainly don't tag Google Books. Also, access levels can change on a whim of the library based on publisher requirements, it's not set in stone, trying to maintain those tags over the years will be impossible. It's really beyond our scope or need. Readers are expected to be able to navigate and understand external websites. -- GreenC 00:24, 17 December 2024 (UTC)
- That particular book is not fully browsable, click 'next page'.
- To clarify: are you in favor of deprecating
url-access
entirely, or are you making a point about Internet Archive's collections? Tule-hog (talk) 00:39, 17 December 2024 (UTC)- "Fully browsable" is a rare condition for (copyright) books, at any website. At Internet Archive, for example, permissions can include:
- Full access for everyone
- Full access if you login
- Full access if you are disabled
- Some book pages browsable for everyone
- Some book pages browsable if you login
- Search access for everyone but not browsable
- Search access if you login but not browsable
- There are other permissions controlling access to files
- Also, these permissions can, and frequently do, change at the whim of Internet Archive and the publishers, at any time. Including new types of permissions.
- So my question is how you plan on communicating AND maintaining this information on Wikipedia for the next 20 years for millions of books.
- Also, this is only one website. Google Books has similar gradations, is even more complex, and more opaque how it works. For these reasons we don't track the precise levels of access. It's generally understood that any copyright material is by default probably going to have some restrictions. It's a matter of practicality. -- GreenC 02:50, 17 December 2024 (UTC)
- "Fully browsable" is a rare condition for (copyright) books, at any website. At Internet Archive, for example, permissions can include:
- User:Tule-hog, the book is fully searchable (click the magnifying glass). And, you can open it to any page like page 42. This is the same as many books at Google Books. I would be careful about tagging books as "inaccessible" because there are many levels and types of access, beyond complete full access. We certainly don't tag Google Books. Also, access levels can change on a whim of the library based on publisher requirements, it's not set in stone, trying to maintain those tags over the years will be impossible. It's really beyond our scope or need. Readers are expected to be able to navigate and understand external websites. -- GreenC 00:24, 17 December 2024 (UTC)
- I went with
- @Tule-hog: I don't think any of the values in the current current scheme accurately represent the access status you have described. I'd be inclined to leave
DOI prefix limits should be bumped.
[edit]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)
- Seconding this! —Collint c 22:10, 17 December 2024 (UTC)
- If that is true, why (as I write this) is Category:CS1 errors: DOI empty?
{{PAGESINCATEGORY:CS1 errors: DOI}}
→ 0
- —Trappist the monk (talk) 22:47, 17 December 2024 (UTC)
- @Trappist the monk: The article Kiwai Island has a DOI of 10.70460/jpa.v7i1.183 in reference #1 that is incorrectly giving a "
Check |doi= value
" error. Could you please help fix this? GoingBatty (talk) 19:41, 19 December 2024 (UTC)
- @Trappist the monk: The article Kiwai Island has a DOI of 10.70460/jpa.v7i1.183 in reference #1 that is incorrectly giving a "
- Fixed in sandbox:
Wikitext | {{cite journal
|
---|---|
Live | McNiven, Ian J (2016). "Stone Axes as Grave Markers on Kiwai Island Fly River Delta Papua New Guinea". Journal of Pacific Archaeology. 7 (1): 74–83. doi:10.70460/jpa.v7i1.183. {{cite journal}} : Check |doi= value (help)
|
Sandbox | McNiven, Ian J (2016). "Stone Axes as Grave Markers on Kiwai Island Fly River Delta Papua New Guinea". Journal of Pacific Archaeology. 7 (1): 74–83. doi:10.70460/jpa.v7i1.183. |
spurious errors when fetching identifier limit data from commons
[edit]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: Lua error in Module:Citation/CS1/Configuration at line 2083: attempt to index a boolean value 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)
cite episode id parameter silently ignored
[edit]{{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)
Request to edit note at top of Category:CS1 maint: unflagged free DOI
[edit]Hi there! Could someone please update the note at the top of Category:CS1 maint: unflagged free DOI? It mentions an issue affecting 17 Wikipedia articles, but there are now less than 10 articles in the category. Thanks! GoingBatty (talk) 17:45, 8 December 2024 (UTC)
- See WP:BOLD. Also, I wonder why it dropped from 17. There hasn't been a template update in ages... I suspect someone performed bad fixes just to avoid the categorization. Headbomb {t · c · p · b} 12:15, 10 December 2024 (UTC)
- @Headbomb: See WP:BOLD#Be careful. I don't know what the correct change should be, so it's better to get consensus here. GoingBatty (talk) 19:38, 19 December 2024 (UTC)
Links to preprint archives
[edit]It is usefull to have the link to arXiv with its own identification numbers in the citation template, but
- why bioRχiv with the identification identical with the preprint DOI number,
- why not viXra with specific identifiers (as arXiv), and
- why not other archives without specific identifiers (only preprint DOI as in bioRχiv), as medRχiv (https://www.medrxiv.org/), ChemRxiv (https://chemrxiv.org/), EarthArXiv (https://eartharxiv.org/), PsyArXiv (https://osf.io/preprints/psyarxiv), ResearchSquare (https://www.researchsquare.com/) etc.?
Petr Karel (talk) 10:47, 10 December 2024 (UTC)
Proposal: Replace "biorxiv=" by "preprint DOI=" to include other preprint archives. The link to preprint is usefull when the final version is not free to access. --Petr Karel (talk) 11:19, 10 December 2024 (UTC)
- Simply put, there's almost nothing on vixra we should want to cite. It is not a reliable source, worse than your usual repository of preprints. It's a nutjob farm. Headbomb {t · c · p · b} 12:13, 10 December 2024 (UTC)
- If you want to include a courtesy link to the free preprint, along with a citation to the print version, you can do so after the template but before the closing ref tag. As an example:
<ref>{{cite journal |author=Author |title=Title |journal=Journal |url=https://journal.org}} [https://eartharxiv.org/ Free to access preprint]</ref>
- Gives you the following:
- Author. "Title". Journal. Free to access preprint
-- LCU ActivelyDisinterested «@» °∆t° 14:36, 10 December 2024 (UTC)- I realize this is not the right place to bring this up, but the Visual Editor should really offer better support for this. Rjjiii (talk) 22:34, 10 December 2024 (UTC)
- That workaround feels like a kludge. I would prefer to see preprint URL support integrated into the template as a
preprint-url
parameter, which for some reason, has not yet been proposed in any of the 96 archive pages of this talk page. The WP:PREPRINT guideline states, "links to such repositories can be used as open-access links for papers which have been subsequently published in acceptable literature", and it would be useful for the template to link to both the paywalled published version and the unpaywalled preprint without any extra workaround. Using a template parameter would also make the preprint URL more machine-readable, compared to using a separate link.For example, I recently cited the following source:- Crowston, Kevin; Wei, Kangning; Howison, James; Wiggins, Andrea (5 March 2008). "Free/Libre open-source software development: What we know and what we do not know". ACM Computing Surveys. 44 (2). Association for Computing Machinery: 7:1–7:35. doi:10.1145/2089125.2089127. ISSN 0360-0300. Retrieved 15 December 2024.
- I wanted to also include a link to this preprint of the article hosted by the Internet Archive. It would have been nice to have a
preprint-url
parameter that would have allowed me to do this in the {{Cite journal}} template. — Newslinger talk 22:30, 15 December 2024 (UTC)- I've been just putting the preprint URL in
|url=
, because the publisher's version is already linked from|doi=
. I realize this creates some confusion about which version the person creating the reference is actually looking at. I don't usually verify that the versions are identical, but if I have significant doubt, I include citations for both the preprint and the final published version in the same<ref>...</ref>
with "Republished as/from" between them, with the first citation being the one I was actually looking at. The word "republished" to me leaves open the possibility of more substantial changes than "reprinted". I am surprised that neither Wikipedia:Citing sources § Say where you read it nor Wikipedia:Citing sources § Dates and reprints discuss the issue specifically. I welcome feedback from other editors on my practices. - The issue of multiple versions of a work is bigger than just preprints, and
|preprint-url=
feels to me like a partial solution to a bigger problem. In some fields (eg. economics, public policy) working papers with multiple drafts distributed over many years are normal prior to publication. Daask (talk) 16:42, 16 December 2024 (UTC)- I've also done that before, and I agree that it can be confusing for the reader, which is why I'm hesitant to include preprints in the
url
parameter now. Since the sole purpose of thepreprint-url
parameter would be to present the reader with an open-access link, I don't think it would be necessary to link multiple drafts in the citation template. — Newslinger talk 08:53, 17 December 2024 (UTC)
- I've also done that before, and I agree that it can be confusing for the reader, which is why I'm hesitant to include preprints in the
- I've been just putting the preprint URL in
Cite chapter in book with no editor
[edit]I read part of Help talk:Citation Style 1/Archive 61#Time to fix "In: <title>"? (and somewhat related Help talk:Citation Style 1/Archive 10#Foreword|) and I am not exactly clear on the result of that discussion.
I would like to discuss a related use case to those above discussions which is old books where you have a collection of works in a single book with no editor. This was apparently somewhat common in miscellanies and anthologies compiled in the middle ages. Here is a pretty good example of a miscellany with no editor but with named contributors and chapters: https://mvm.dhil.lib.sfu.ca/manuscript/109. The issue with the current implementation is that the citation will look like the author of the chapter is the author of the entire book because there is no "in."
I don't have many examples but I have seen the form "chapter" in "book name," without an attribution to any editor, in history journals, so I think this may be common practice.
So I guess my post has multiple aspects:
1. Do journals use the "chapter" in "book name" form even with no editor? How commonplace is this? My assumption right now is that it is somewhat common.
2. Should we support such a feature? My thought here is that we should.
3. How should this be supported? We can support this feature without necessarily implementing "in" for all book chapters. We could do so by using a new parameter "chapter author," which would then always use "in," without having to use it in all cases, for example. There could be multiple ways to achieve this result. I would not like a solution that leaves the
Any thoughts or questions on the above would be appreciated. I apologize if this is already a settled point. I did my best to search for previous discussions by searching "no editor" and '"editor" "is unknown"' in the archive. Lastly, if this is already supported, I suggest it be made more clear in the documentation as I could not find it.
(edit: Reading 'Time to fix "In: <title>"?' again, it is actually the exact same issue. I'm not sure what I thought it meant when I first read it. Somehow I thought it was about citing a chapter of a book where the entire book was written by one author.) J2UDY7r00CRjH (talk) 22:43, 12 December 2024 (UTC)
- J2UDY7r00CRjH, it sounds here like the problem statement is a citation like
Author, Chapter. "Chapter title". Edited Volume
gives the impression that the chapter author contributed all the chapters, but the theory of change is thatAuthor, Chapter. "Chapter title". In Edited Volume
will convey the correct impression?I don't have an alternative solution to propose, but I do note that the opposite problem – volume or even series editors being attributed authorship of chapters – is more common by at least an order of magnitude. Folly Mox (talk) 13:45, 13 December 2024 (UTC)- >the theory of change is that Author, Chapter. "Chapter title". In Edited Volume will convey the correct impression?
- Yes, additionally, it seems that some styles already use this format. I first saw it in this journal article: https://www.tandfonline.com/doi/full/10.1080/09596410.2017.1401797 (paywalled) (Screenshot of the relevant citation) (link to the cited book).
- Looking further, I found that the APA Publication Manual (7th Edition) seems to follow this rule:
Example 47. Entry in a dictionary, thesaurus, or encyclopedia, with group author
American Psychological Association. (n.d.). Positive transference. In APA dictionary of psychology. Retrieved August 31, 2019, from https://dictionary.apa.org/positive-transference
Merriam-Webster. (n.d.). Self-report. In Merriam-Webster.com dictionary. Retrieved July 12, 2019, from https://www.merriam-webster.com/dictionary/self-report- This is made more explicit in other guides:
- 1.
- >Chapter in a book
- >If there is no editor, include the word "In" before the book title. (link)
- 2.
- >Chapters, Short Stories, Essays, or Articles From a Book (Anthology or Collection)
- >[..] Note: If there is no editor given you may leave out that part of the citation.(link). This one is a bit ambiguous about what "that part of the citation" refers to. I don't think it includes "in."
- 3.
- This academia.stackexchange post
- So the second reason is to be in line with other citation styles. However, I'm not an expert on citation style and I may be missing something. I found these links above by searching 'how to cite volume with "no editor"' on Google. J2UDY7r00CRjH (talk) 18:52, 13 December 2024 (UTC)
- I think I agree that
In Edited Volume
is clearer. I wonder if instead of a whole new set of|chapter-authorn=
parameters and their attendant-link=
s,-mask
s etc, an easier implementation might be a specific override value for|editor=
, so if it has that value thenIn
will appear before the book title (kinda like how|author-mask=
will display text exactly as formatted, except numeric values which it displays as a string of dashes). Folly Mox (talk) 21:45, 13 December 2024 (UTC)- An override value for the editor field would also work. Is there a standard value used for such cases? I think "editor=unknown" would work here. J2UDY7r00CRjH (talk) 23:21, 14 December 2024 (UTC)
- I think I agree that
Omitting location parameter when implied by the publisher
[edit]Presently, H:CS1 says The location parameter should be omitted when it is implied by the name of the work, e.g. The Sydney Morning Herald. Does this also apply to the name of the publisher, e.g. Cambridge University Press? I've only just realized I've been conflating the two. Remsense ‥ 论 19:29, 14 December 2024 (UTC)
- I don't think this advice is valid for publishers like CUP, OUP; they often publish in various locations. OTOH, it's probably trivial and doesn't matter. -- Michael Bednarek (talk) 08:54, 15 December 2024 (UTC)
- In my mind, omitting location would imply publication in the eponymous location. But yes, I'm thinking of how necessary the parameter even is in many situations. Remsense ‥ 论 08:59, 15 December 2024 (UTC)
Citeref: if no year, use year from date
[edit]Citeref is an html ID that is used to connect template:harv and template:sfn to cs1.
Problem to be solved:
An SQL search over linter errors of citerefs with the same id gives that around 280k do not have any number, so no year. It does make sense to look if the year can be fetched from elsewhere. CS1 alone makes 1.7 million out of 3.8 million duplicate IDs, so something has to be done, the status quo is not an feasible outcome.
Expected breakages:
https://en.wikipedia.org/w/index.php?search=hastemplate%3A%22Cite+journal%22+hastemplate%3A%22Harvard+citation%22+insource%3A%2F%5C%7B%5C%7Bharvard+citation%5C%7C%5Ba-zA-Z%5C%7C%5D%2B%5C%7D%5C%7D%2F&title=Special:Search&profile=advanced&fulltext=1&ns0=1 shows that among the usages of cite journal and harv there is only one that does not have a number, Gordon Pask with its reference to Green, but that reference does not have an date, so it will not be affected by the change. Among the usages of cite journal and harv there are none with only page and not date, so nothing expected to break there. Overall, I do expect breakages, but that that they fix more duplicate ID's than they cause issues with harv. One could do an interim solution with both IDs showing up, causing no breakages for harv and sfn in the meantime.
Solution:
It does make sense to look for an year in date, when year is not given. An editor is not likely to duplicate the year when the date has already been given.
Add the following to line 4115 of Module:Citation/CS1, keeping the line break that is there.
if Year == nil or "" then Year = string.match(Date, "%d%d%d%d") end
Snævar (talk) 15:00, 15 December 2024 (UTC)
- Having the same CITEREF in articles that do not use short form references is not an error that needs solving.
- The year in
|date=
is already used if it is part of the cite. However the example in Gordon Peak (CITEREFGreen) has no|date=
parameter only|access-date=
and|archive-date=
neither of which would be appropriate to include in a short form reference. -- LCU ActivelyDisinterested «@» °∆t° 16:35, 15 December 2024 (UTC) - (edit conflict)
- No. At Module:Citation/CS1 line 4114 is this:
local year = first_set ({Year, anchor_year}, 2); -- Year first for legacy citations and for YMD dates that require disambiguation
- Normally,
Year
has been set tonil
before this point in the code.anchor_year
comes from Module:Citation/CS1/Date validation. - This example has
|date=
but does not have|year=
:{{cite book |title=Title |last=Greene |first=EB |date=15 December 2024}}
→ Greene, EB (15 December 2024). Title.'"`UNIQ--templatestyles-00000049-QINU`"'<cite id="CITEREFGreene2024" class="citation book cs1">Greene, EB (15 December 2024). ''Title''.</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=2024-12-15&rft.aulast=Greene&rft.aufirst=EB&rfr_id=info%3Asid%2Fen.wikipedia.org%3AHelp+talk%3ACitation+Style+1" class="Z3988"></span>
- Note the value assigned to the
id=
attribute in the<cite>
tag; it has the year portion from|date=
. - If you know of cs1|2 templates that do not include the year portion from a publication-date parameter (
|date=
,|publication-date=
,|year=
) in theCITEREF
anchor id, I'd like to see it. - Editors do
duplicate the year when the date has already been given
; Category:CS1 maint: date and year wouldn't be needed else. - It used to be that cs1 templates did not automagically create
CITEREF
anchor ids. Some time back, there was discussion: - Editors in those discussions decided that all cs1|2 templates would create
CITEREF
anchor ids, needed or not; the automagicCITEREF
anchor id can be suppressed with|ref=none
. This linter thing is an artefact of that decision. - —Trappist the monk (talk) 17:01, 15 December 2024 (UTC)
Using 'First' and 'last' over 'author' parameter
[edit]Template:Citation states that |first=
and |last=
are preferred over |author=
. I recently edited some citations accordingly and was reverted. Is there a reason |first=
and |last=
are preferred, or is this indeed a non-issue? Random86 (talk) 00:42, 16 December 2024 (UTC)
- Names are not universally consistent either in publishing or the world at large—given authors are generally identified primarily by surname, one can make a clear case for explicit specification. Remsense ‥ 论 00:47, 16 December 2024 (UTC)
- Also, separating them out is necessary if you want short footnotes ({{sfn}}) to link to the reference without a lot of extra hassle working around the lack of surnames. —David Eppstein (talk) 06:01, 16 December 2024 (UTC)
- Separate first/last names are generally better. As said above,
{{sfn}}
and the like work much better with last names. It also allows better web searching for a reference when the source website changes between using between "Dee Lightful", "D. Lightful" or "Lightful". However, sometimes it is hard for us English speakers to know which part of a non-English name is the family name and which is the personal name - eg, in Foo Ling Yu many Westerners don't realise that Foo is the family name (ie the last name in western terms, even though it is at the start of the name) and Ling-Yu is the personal part of her name (ie, the first name in western terms). There are also a few Western names that are hard (eg Douglas, Michael vs Michael, Douglas). Which is why the author field is allowed and does not produce errors - it is the ultimate fallback when you do not know the correct order. Which means that the reverter was quite wrong to revert you based on faulty logic. Stepho talk 08:01, 16 December 2024 (UTC)- The parameters are perhaps misnamed as they really mean "given name" and "family name" regardless of name order, rather than first and last. But of course there are cultures (like say Iceland) where names don't work like that. —David Eppstein (talk) 08:25, 16 December 2024 (UTC)
- Well, what they really mean is "surname" and "not surname". Remsense ‥ 论 08:27, 16 December 2024 (UTC)
- Difficult to generalise: Saddam Hussein al Tikriti: 2nd name father's "forename", no family name, normal (not informal) single-word name Saddam. Federico del Sagrado Corazón de Jesús García Lorca; normal Spanish surname García, but known, unusually, by mother's surname Lorca. María-José Pérez de Gómez, known sometimes as M-J Pérez, others as Sra [de] Gómez. Pol098 (talk) 11:58, 16 December 2024 (UTC)
- True. But if you look at the revert there were only 2 names changed (although multiple times each): "Benjamin, Jeff" and "Caulfield, Keith". Both English. Both already separated into surname, comma, given name. No complications. No non-English names. Also, they are displayed to the reader exactly the same but as separate fields they are much more suitable for computer processing. There was no reason whatsoever for the revert apart from WP:JUSTDONTLIKEIT. Stepho talk 04:45, 17 December 2024 (UTC)
- Difficult to generalise: Saddam Hussein al Tikriti: 2nd name father's "forename", no family name, normal (not informal) single-word name Saddam. Federico del Sagrado Corazón de Jesús García Lorca; normal Spanish surname García, but known, unusually, by mother's surname Lorca. María-José Pérez de Gómez, known sometimes as M-J Pérez, others as Sra [de] Gómez. Pol098 (talk) 11:58, 16 December 2024 (UTC)
- One can also use the aliases
|given=
and|surname=
for these parameters. Kanguole 12:11, 16 December 2024 (UTC)- Thank you. That's new to me and I will probably start using it. Stepho talk 04:45, 17 December 2024 (UTC)
- Unfortunately, Wikipedia:ProveIt presently undoes this. I should probably write a script that switches an article the other way, since the solution for automated RETAIN-vio is more automation, of course. Remsense ‥ 论 22:18, 17 December 2024 (UTC)
- ProveIt makes several changes to parameters, which it really shouldn't. One of the worst occurs when a reference has multiple authors – ProveIt renames the first one as
|first=
and|last=
and moves the others later in the reference. (If Citation bot encounters these, it will change them to|first1=
and|last1=
, ready for ProveIt to "fix" them again.) It really should not be used on articles that already have consistent citations. Kanguole 22:28, 17 December 2024 (UTC)- I mostly used it before for its consistent ordering and spacing, but now I mostly avoid it, and make sure to manually tweak where it violates RETAIN. Remsense ‥ 论 22:30, 17 December 2024 (UTC)
- ProveIt makes several changes to parameters, which it really shouldn't. One of the worst occurs when a reference has multiple authors – ProveIt renames the first one as
- Unfortunately, Wikipedia:ProveIt presently undoes this. I should probably write a script that switches an article the other way, since the solution for automated RETAIN-vio is more automation, of course. Remsense ‥ 论 22:18, 17 December 2024 (UTC)
- Thank you. That's new to me and I will probably start using it. Stepho talk 04:45, 17 December 2024 (UTC)
- Well, what they really mean is "surname" and "not surname". Remsense ‥ 论 08:27, 16 December 2024 (UTC)
- The parameters are perhaps misnamed as they really mean "given name" and "family name" regardless of name order, rather than first and last. But of course there are cultures (like say Iceland) where names don't work like that. —David Eppstein (talk) 08:25, 16 December 2024 (UTC)
- Separate first/last names are generally better. As said above,
Generic title
[edit]Registered & Protected by MarkMonitor is a generic title string. -- GreenC 00:59, 19 December 2024 (UTC)
Cite case causes CS1 errors
[edit]{{Cite case}} maps |court=
to |agency=
, which is no longer supported by {{cite book}} -- see MKUltra#cite_note-107. This was brought up at Template talk:Cite case a few months ago by @DocWatson42 and @Isaidnoway, but I'm bringing it here since this is a better-watched talk page. Jay8g [V•T•E] 04:24, 20 December 2024 (UTC)
- I remapped it to
|series=
, which renders in the same position in the citation. Hopefully no court cases are part of a series. Haven't checked all 52 transclusions, but none of the dozen or so I checked are in Category:Pages using duplicate arguments in template calls, so it seems fine. No documentation at this template. Folly Mox (talk) 17:04, 21 December 2024 (UTC)
Placement of "translator"/"page" fields
[edit]Greetings and felicitations. When "translator" and "page" fields are used together in "Cite journal", it results in this:
- Fujimoto, Yukari (2012). "Takahashi Macoto: The Origin of Shōjo Manga Style". Mechademia. 7 (1). Translated by Thorn, Rachel: 24–55. doi:10.5749/minnesota/9780816680498.003.0002. ISBN 978-0-8166-8049-8.
ISTM that the "translator" field should be followed by a period, or be placed before the volume/issue number fields, or after the pages field. —DocWatson42 (talk) 05:48, 20 December 2024 (UTC)
- Yeah, a known flaw but a pain to fix. If we really need to fix it, we should revisit the placement of all rendered parameters. As it is now, the code that orders the cs1|2 template parameters is ugly and confusing.
- For this particular case, if one follows the doi link to the publisher's website, Oxford Academic identifies "Takahashi Macoto: The Origin of Shōjo Manga Style" as a chapter in the book Mechademia 7: Lines of Sight. It would seem then that
{{cite book}}
would be the appropriate template. I don't have access to the source, but Oxford Academic's recommended citation does not include Rachel Thorn (with an 'N'). The recommended citation lists a co-author(?) 'Matt Thorm' (with an 'M'). So, perhaps the correct template looks like this (without|translator=
):{{Cite book |last=Fujimoto |first=Yukari |author-link=Yukari Fujimoto |last2=Thorm |first2=Matt |date=2012 |chapter=Takahashi Macoto: The Origin of Shōjo Manga Style |editor-last=Lunning |editor-first=Frenchy |title=Mechademia 7: Lines of Sight |pages=24–55 |doi=10.5749/minnesota/9780816680498.003.0002 |isbn=978-0-8166-8049-8}}
- Fujimoto, Yukari; Thorm, Matt (2012). "Takahashi Macoto: The Origin of Shōjo Manga Style". In Lunning, Frenchy (ed.). Mechademia 7: Lines of Sight. pp. 24–55. doi:10.5749/minnesota/9780816680498.003.0002. ISBN 978-0-8166-8049-8.
- or with
|translator=
:{{Cite book |last=Fujimoto |first=Yukari |author-link=Yukari Fujimoto |last2=Thorm |first2=Matt |date=2012 |chapter=Takahashi Macoto: The Origin of Shōjo Manga Style |editor-last=Lunning |editor-first=Frenchy |title=Mechademia 7: Lines of Sight |translator=[[Rachel Thorn|Thorn, Rachel]] |pages=24–55 |doi=10.5749/minnesota/9780816680498.003.0002 |isbn=978-0-8166-8049-8}}
- Fujimoto, Yukari; Thorm, Matt (2012). "Takahashi Macoto: The Origin of Shōjo Manga Style". In Lunning, Frenchy (ed.). Mechademia 7: Lines of Sight. Translated by Thorn, Rachel. pp. 24–55. doi:10.5749/minnesota/9780816680498.003.0002. ISBN 978-0-8166-8049-8.
- —Trappist the monk (talk) 16:44, 20 December 2024 (UTC)
- I don't have time right now to reply in full, but Mechademia is a journal in the form of a book, and the correct spelling of the particular author's name is Matt Thorn. —DocWatson42 (talk) 20:14, 20 December 2024 (UTC)
module suite update 28–29 December 2024
[edit]I propose to update the cs1|2 module suite over the weekend 28–29 December 2024. Here are the changes:
- convert Category:CS1 maint: unfit URL to properties cat Category:CS1: unfit URL; discussion
Module:Citation/CS1/Configuration:
- update emoji zwj table to Unicode v16.0; nothing changed except version and date;
- add script lang codes 'az', 'chr', 'zgh';
- add free DOI registrants 10.18637 – Foundation for Open Access Statistic, 10.1016/j.proche – Procedia Chemistry
- convert Category:CS1 maint: unfit URL to properties cat Category:CS1: unfit URL
- relax 'HugeDomains' generic title search; discussion
Module:Citation/CS1/Identifiers:
- fix extended free doi bug; discussion
- bump 5-digit doi prefix limit; discussion
Module:Citation/CS1/Utilities:
- reworked hyphen_to_dash(); discussion
—Trappist the monk (talk) 01:57, 21 December 2024 (UTC)
- I don't have an opinion on most of these but am very happy to see the hyphen-to-dash fix. Thanks! —David Eppstein (talk) 06:01, 21 December 2024 (UTC)
- Instead of Category:CS1: unfit URL could it be Category:CS1: usurped URL - it is the majority by about 3:1: unfit 11,000, usurped 46,000. The usurped will grow indef due to WP:JUDI. -- GreenC 06:21, 21 December 2024 (UTC)
- Makes sense just to reparent the existing cat:
usurped
is a subtype ofunfit
. Thanks for all your work, Trappist. Folly Mox (talk) 16:46, 21 December 2024 (UTC)- Just so I understand what you are saying: You think that
|url-status=unfit
should categorize to Category:CS1: unfit URL and|url-status=usurped
should categorize to Category:CS1: usurped URL where the latter is a sub-category of the former? Do we really need two categories? - —Trappist the monk (talk) 19:10, 21 December 2024 (UTC)
- Just so I understand what you are saying: You think that
- Makes sense just to reparent the existing cat: