Help talk:Citation Style 1/Archive 2

From Wikipedia, the free encyclopedia

Archive 1Archive 2Archive 3Archive 4Archive 5

Capitalization of web sites in references

I believe I have seen somewhere that only the first letter of a website is to be capitalized in the references section "for example, "LATimes.com" should appear as "Latimes.com". If this is in fact the case, I believe it would be wise to note this in the Template:cite web. Zepppep (talk) 16:38, 30 September 2012 (UTC)

Citation style 1 does not seem to have a rule about this. If a rule is established, I would think one would want to mention it in all the CS1 templates, because many books, journals, newspapers, etc., are cited from their websites rather than the paper version. There is some merit to just using copy and paste to put a URL into a citation, and thus reduce the possibility of a typographical error. Jc3s5h (talk) 16:59, 30 September 2012 (UTC)
I don't think that MOS guidelines - certain to have exceptions - should be enforced through citation templates. Do we need a rule here? bobrayner (talk) 17:05, 30 September 2012 (UTC)
I am not worried about books or newspapersfor those in fact should be capitalized appropriately. Websites, however, often times appear as a single word (some might employ some use of hyphens, such as Baseball-Reference.com) and also employ a lot of abbreviations.
I am almost certain I've read that only the first letter of a website should be capitalizedafter searching on a few different occasions, I haven't been able to fully retrace my steps. I shall check the MoS again (if anyone knows, feel free to link!), or perhaps other nooks and crannies. If it is indeed a rule, then I would encourage mention of it in the template because it's easily one of the most abused reference offensives out there. If it wasn't an oft abused stylistics offense I wouldn't suggest specific mention. Zepppep (talk) 17:32, 30 September 2012 (UTC)
The name of the site at http://www.latimes.com/ is Los Angeles Times. --- Gadget850 (Ed) talk 20:36, 30 September 2012 (UTC)
Yes, that's the name. How about http:///www.nytimes.com? A lot of editors will put "work= or newspaper=NYTimes.com", even though it is simply the newspaper in a different medium. If the article/blog is mentioned in the web format only, however, they may very well put "work=NYTimes.com" when I believe it should be "work=Nytimes.com". Zepppep (talk) 04:39, 1 October 2012 (UTC)
Exactly. There seems to be some confusion here between "name of a website" and the url that points to it. E.g., "http://www.latimes.come/" is a url. And though it has been years since I've seen the relevant RFC I suspect that the general practice (if not the rule) is still that urls are case insensitive, so capitalization is irrelevant. ~ J. Johnson (JJ) (talk) 21:11, 30 September 2012 (UTC)
The protocol and domain name of a URL are case-insensitive, but the portion after the third slash may or may not be case-sensitive depending upon the software used by the server. For example, the URLs http://en.wikipedia.org/wiki/Template:Esp http://en.wikipedia.org/wiki/Template:ESp and http://en.wikipedia.org/wiki/Template:ESP are all different. --Redrose64 (talk) 21:57, 30 September 2012 (UTC)
The address portion of the URL could be the name of the website, in the case of certain websites that brand themselves using ".com" as part of their name. The name for the newspaper in Ann Arbor, Michigan is AnnArbor.com, and like the online editions of its sister papers, it can also be accessed through the localized pages at MLive.com, http://www.annarbor.com/ and http://www.mlive.com/ann-arbor/ respectively. Imzadi 1979  21:37, 30 September 2012 (UTC)
For sure, some sites think it's cool to use their url as a "name", and use capitalization to make it more readable. But making the name (or title) look like a url does not make it a url; it's still just a name.
As to urls, there is, as Redrose points out, a caveat: the first single slash delimits the first part of the url (which is the domain name, and capitalization is as I said above) from the rest, which is file-system specific. And the file server may (or not) observe capitalization. In that regard it would be flat out error for "style" to over-rule technical reality. "AnnArbor.com/Forum" will probably work the same as "annarbor.com/Forum", but "annarbor.com/fORum" might not. ~ J. Johnson (JJ) (talk) 22:57, 30 September 2012 (UTC)
Regardless, I often view the page source and grab the content of the <title>. Doesn't work for every site, but most reliable sources will use a proper title. --- Gadget850 (Ed) talk 01:49, 1 October 2012 (UTC)

If a website chooses to use its domain name as its name in general writing, it is a proper name and perhaps a trademark. It should be capitalized as the name-holder prefers, barring typographical difficulties such as mirror-image letters. As for the original poster's contention that only the first letter should be capitalized, it was reasonable to bring up that contention in the hope someone else would be able to find a Wikipedia policy or guideline that calls for that, or a reliable source indicating it is common English usage. But perhaps we have reached the point that we shouldn't give that contention further contention until a suitable source is found. Jc3s5h (talk) 14:41, 1 October 2012 (UTC)

Is this really the place for a MOS discussion? LeadSongDog come howl! 06:29, 2 October 2012 (UTC)
Yes, where someone proposes to have the template reflect some style. But I think in this instance it has been adequately shown that capitalization of urls (whether of the domain name part, or the file-system part) is not something a template should be messing with. Hopefully that is settled. ~ J. Johnson (JJ) (talk) 23:14, 2 October 2012 (UTC)

BTW, it's me: I'm one of those editors who adds work=NYTimes.com, primarily because that's how the paper names its own site, and matches the proper capitalization of an abbreviation of the paper's name with ".com" appended. And yes, I'm one of those editors (oh dear) who thinks that Wikipedia should call things by the names and capitalizations offered by their copyright and trademark holders, or creators where such usage does not violate PROMO or the principle of least offense. Pardon me, dear, what was that word we reserved for people like that? Oh, yes, that's right: monsters, horrible horrible monsters. --Lexein (talk) 00:10, 21 October 2012 (UTC)

What's wrong with |work=New York Times? nytimes.com (HOweVEr yOU waNT to CApiTAliZE it) is not its name, it is its web address. —David Eppstein (talk) 00:15, 21 October 2012 (UTC)
Exactly the point I made earlier. The publication title is shown in the masthead of the page; where that is not clear, it is usually also in the <title> tag.
Should we clarify this in the documentation? --- Gadget850 (Ed) talk 01:39, 21 October 2012 (UTC)
WP:SAYWHEREYOUREADIT says Say where you read it. The paper publication might not have carried the piece we're citing, and if it did, we don't know the page or section, so the masthead name is ambiguous for our purpose, and misleading. That is why I feel it's more descriptive to list work=NYTimes.com, the domain, not the full URL, and not the masthead name. Also listing publisher=New York Times Company is, of course, awesome. --Lexein (talk) 12:55, 21 October 2012 (UTC)
Continue as you will; others will certainly fix it. --- Gadget850 (Ed) talk 13:21, 21 October 2012 (UTC)
Thanks for terminating civil discussion with a threat to stalk, without bothering to respond to the points, or thesis, raised. --Lexein (talk) 23:06, 21 October 2012 (UTC)
As previously noted, capitalization of domain names probably does not matter. But in general, we should not be changing capitalization. Even if (say) "NYTimes.com" is better (clearer?) than "nytimes.com", that is for them to do, not us.
I think what Lexein really wants is a way of distinguishing the website of the newspaper from the newspaper itself. I think this is a legitimate problem (I recently encountered the same problem with Scientific American). Lexein attempts a resolution by using the domain name to imply a website (a dubious approach), then wants to dress up the domain name capitalizing it. The real issue is distinguishing websites, but that is not what we are discussing here; it should have a new thread. ~ J. Johnson (JJ) (talk) 20:04, 21 October 2012 (UTC)
An article that appears in The New York Times could appear as follows:
  • Reporter, Joe (January 1, 1901). "An Article Never Online". The New York Times. p. 1. ISSN 0362-4331.
  • Reporter, Joe (January 1, 1951). "An Article in Print and Online Archives". The New York Times. p. 1. ISSN 0362-4331. Retrieved October 21, 2012.
  • Reporter, Joe (January 1, 2001). "An Article Never in Print". The New York Times. Retrieved October 21, 2012.
Notice how the presence or absence of page numbers, ISSNs, hyperlinks, and access dates indicates if an article is available online, in print, or both. I've done this with articles from The Mining Journal in Marquette, Michigan, because not all of their articles are repeated online each day. Some of the articles I've used at County Road 595 (Marquette County, Michigan) have hyperlinks (and even pre-emptively archived links) and some do not, but all of them have the page numbers and ISSN from the print edition. The one article from The Morning Sun in Mount Pleasant, Michigan, was online-only, so it lacks an ID or page number. Imzadi 1979  22:33, 21 October 2012 (UTC)
J. Johnson: C'mon, don't talk about editors. The nytimes.com searchbar has this obvious text: "Search All NYTimes.com", so the capitalization is indeed theirs, not mine, ffs. There's no dubious approach to associating domain name and website for our purposes: Wikipedia is no stranger to protocol-stripping URLs (http://nytimes.com) for discussion of websites (nytimes.com) in articles to avoid bare urls. If you're arguing that work=The New York Times website is best, I'd shrug, and not revert it if I saw it. But I'd fight for work=AnnArbor.com - heh.
Imzadi: I don't think implication is enough. We naively do not know if a modern item was ever, or never, in print, seeing only its web instance. We may know later, from news archive services, and/or citation services. I still think work=NYTimes.com is defensible as identifying where I read it. --Lexein (talk) 23:06, 21 October 2012 (UTC)
Well, since the newspaper published thrice weekly in print for Ann Arbor, Michigan, is titled AnnArbor.com on its masthead, which matches the online edition, that would be correct. However, the name for the online edition of The New York Times is just that. Hopefully you don't revert people correcting citations to use the proper publication name, per the websites' mastheads or <title></title> attributes. BTW, let me clarify something. I consult both the online and print editions of The Mining Journal when I use the combined citation; had I not been able to consult the print edition, I'd only cite the online edition sans ISSN and page number reference. Imzadi 1979  23:28, 21 October 2012 (UTC)
To reiterate, the masthead searchbar has this obvious text: "Search All NYTimes.com", so the name, and capitalization is indeed theirs, not mine. So your argument really is not with me, it is with the Gray Lady herself, until the literal text "NYTimes.com" is removed from the masthead of the online edition. --Lexein (talk) 00:30, 22 October 2012 (UTC)
Searchbar? Huh? What if it showed Search this web site? The masthead shows The New York Times; I see "NYTimes.com Search" on the search page, but not on the main page. This is starting to feel like a greased pig. --- Gadget850 (Ed) talk 02:21, 22 October 2012 (UTC)
Okay, "searchbox", then. See screengrab. "NYTimes.com" appears on all pages but the homepage, including "Today's Paper". Greased pig? The original post was about capitalizing domains, which I do. Interestingly, the Sydney Morning Herald declares the domain fully lowercase, so I may have been doing that one wrong. Since work=domain.tld is accepted, I can be persuaded to keep lowercase as in latimes.com (since they show so in <title> text), and NYTimes.com (since they specify on-page). (To be honest, I'll still want to capitalize LATimes.com). --Lexein (talk) 07:01, 22 October 2012 (UTC)
I suppose we should be thankful you don't insist on writing . —David Eppstein (talk) 07:08, 22 October 2012 (UTC)
I swear that looks like "Los Ungeles", or, The Ungulates, which includes camels, which inspired CamelCaps titles (used on early wikis), presented as a deprecated capitalization example above. --Lexein (talk) 07:53, 22 October 2012 (UTC)
Yes indeed. Lexein, I think you misunderstand what I've said. First, let's not confuse the name of a publication, or website, with its url. (Which can be difficult, given that some sites incorporate their domain name into their proper name.) Second, I am not saying that a domain name should or should not be capitalized, I'm saying that we defer to the site's preferences. That the NYT has a web designer that used a capitalized form of their domain name certainly confuses matters, even gives others some license to do likewise, but we should be careful to not "improve" a domain name (or any part of a url) used as a url. ~ J. Johnson (JJ) (talk) 18:33, 22 October 2012 (UTC)

Using "page" as an alias for "pages"

Is it technically feasible to have "page" become an alias for "pages" and have the "pages" parameter detect the presence of any dashes, endashes, or mdashes, or commas to toggle "pp." instead of "p."? The difference between these two parameters I think is subtle and most editors in a hurry will not learn the difference. Unless a book uses really bizarre page numbering with dashes, this seems like a possibility. Jason Quinn (talk) 16:12, 25 September 2012 (UTC)

  • Consider option pages only: It would be easier to auto-adjust only option "pages=" which seems the worst case, as wrong in perhaps 45,000 articles as 9% incorrect (91% ok) but could auto-adjust most (as 99% ok). That would avoid issues people have raised here. See 2 sub-threads: #Feasible and fast for "pages=n", and also "#Cite_quick detects "pages=n" as singular". -Wikid77 12:27/13:12, 3 October 2012 (UTC)
The issue is performance. Detection would have to be with string templates which are notorious for eating resources. I looked at something similar for detecting first names ending in a period so if the spearator was a period it would suppress it. --- Gadget850 (Ed) talk 17:32, 25 September 2012 (UTC)
Another issue is that there are always boundary cases (e.g. page numbers with hyphens in them) that will be interpreted incorrectly by code trying to be smart, forcing us to define additional parameters to allow us to work around the problem. Sometimes it's better just to keep things simpler. —David Eppstein (talk) 17:48, 25 September 2012 (UTC)
I would counter that while the current solution using two parameters dependent on context is simple from an implementation perspective, it is not "simple" from a usability perspective. Jason Quinn (talk) 18:56, 25 September 2012 (UTC)
There are bots which try to be clever and amend e.g. |page=8, 10 to |pages=8, 10 or |pages=8 to |page=8, but they do sometimes make incorrect changes such as those mentioned above involving hyphens etc. A human check is always better than leaving the guesswork to automatic systems. --Redrose64 (talk) 19:09, 25 September 2012 (UTC)
I found a bot which makes such amendments, see here. No bad edits found yet. --Redrose64 (talk) 23:03, 12 October 2012 (UTC)
See this thread and follow either of the two diff links in the grey box. The bot assumed that a hyphenated identifier of a single page was a page range and amended accordingly. --Redrose64 (talk) 15:30, 25 October 2012 (UTC)
I fail to see that any usability difficulty has been shown. Currently matters are quite simple: "page" is singular, "pages" is plural. If I forget the "s" the result is obvious enough to find and fix. Without having to second guess whether the software is being devious. ~ J. Johnson (JJ) (talk) 23:14, 25 September 2012 (UTC)
And there are definitely cases where books use something like "18-12" to mean the 12th page in the 18th chapter. Ucucha (talk) 00:13, 26 September 2012 (UTC)
My experience suggests that editors misuse those two parameters a lot. I myself at one point thought that "pages" referred to total pages because I hadn't read the documentation. I use the Reftoolbar (2.0b), as I suspect many people do. The entry forms on this gadget need some improvement. There needs to be some re-arrangement of items for more logical grouping. There needs to be more tooltips with descriptions and important notes. There needs to be some addition/deletion of items based on commonality of usage. This might be a good project for mw:Micro Design Improvements. Jason Quinn (talk) 22:27, 26 September 2012 (UTC)
Those certainly seem like worthwhile improvements, but do not constitute a problem with p/pp. (Except for failure to read the documentation, but that is generic.) And the miniscule advantage of trying to surmise an editor's intent seems vastly outweighed by the performance cost. ~ 18:25, 27 September 2012 (UTC)
I disagree with you. 1) There is a problem with p/pp for the reasons stated above. 2) Software that is unintuitive is a problem and existence of documentation is not a reason to ignore it. 3) The advantage would not be minuscule. 4) Performance concerns are a valid concern but not too much (see Wikipedia:Don't worry about performance). Regarding the other improvements we agree upon, yesterday I made a post about them on the Reftoolbar talk page. Jason Quinn (talk) 21:08, 27 September 2012 (UTC)
  Strange, I thought I was agreeing with you to the extent that Refbar can be improved, the documentation generally can be improved, and that failure to RTMF is a general problem. (No? Perhaps you want to be more specific?) But as I said, all of those, as "usability problems" are not relevant to this alleged p/pp problem. As to whether "p=" versus "pp=" is unintuitive, well, perhaps if you have never seen any kind of bibliography before, which doesn't look like a s/w problem.
  And you should read Wikipedia:Don't worry about performance more carefully. Such as the bit that "you, as a user, should not worry about site performance" (bolding removed, italics added). Or (under Editors still have a role to play): "Particularly in the area of template design, optimising server performance is important ...." And I am inclined to believe Ed's statement (above) that there would be a performance issue. ~ J. Johnson (JJ) (talk) 22:42, 27 September 2012 (UTC)
We agree that Reftoolbar and the cite documentation can be improved. The disagreement in my last comment was only concerning "p/pp". I think I misinterpreted what you wrote about documentation. Maybe about your stance on p/pp too. Regarding documentation, I just want to reiterate that good design can lessen the need for the user to read the documentation and sometimes eliminate it altogether. The less the user has to read the documentation, the better. I say this because I want to assert that documentation that properly describes the functions of software is not an argument for the current design/implementation of those functions. I think we'd agree on those points too. Regarding "p/pp", it's not clear to me where you stand except for thinking that the suggestion is infeasible. It may be. I did argue why I thought there was an issue with two parameters doing essentially the same job. So when you wrote that my idea "did not constitute a problem with p/pp" it seems to me a rejection of my assertion that there is a problem with p/pp. From my point of view, it boils down to, "Yes, there is a usability issue with having to parameters to handle page numbers. Would having a single parameter that autoformat's the entry be worthwhile?" Clearly both you and Ed believe no and that the "fix" would be infeasible. That's fine. If it's infeasible, it's infeasible. I am not saying that my idea is feasible. Just proposing it. What's unclear to me is to what extent you agree with me that there is a problem with the two parameters in the first place. Your last message seemed like you took personal offense. None was intended so I hope you don't take a disagreement too emotionally, especially when they may arise simply out of misunderstandings. Jason Quinn (talk) 01:08, 28 September 2012 (UTC)
So your concern is solely with p/pp, and not those other issues? Okay, I'm glad that is sorted out. I have run now, but will try to get back to you tomorrow. ~ J. Johnson (JJ) (talk) 23:09, 28 September 2012 (UTC)
Even if a reliably accurate algorithm existed for determining when to use the abbreviation "p.", or "pp.", or neither, it is bound to give rise to additional processing time, so we should not attempt to introduce one to the Citation Style 1 or Citation Style 2 templates as they stand because users do worry about performance. There are users who actively seek to eliminate these templates precisely because they are slow. Look at discussions earlier on, also at WP:VPT, concerning the time it takes to preview Barack Obama, for example. Any attempt to introduce smart code for p./pp. will definitely slow the templates down even further, thus giving more ammunition to the "delete them all" group. --Redrose64 (talk) 08:44, 28 September 2012 (UTC)
in general though, the performance argument is often spurious. users do not worry about performance afaik. Some editors (a small user subset) do. Preview is an editor function; its performance should not determine the fate of the citation system, which unlike performance, is not only an application of actual policy (WP:V) but may be also useful to the entire, much larger universe of users. at some point it has to be decided whether speed is better than completeness in an online encyclopedia, with actual proof offered that the largest by far group of users (the readers) prefers one over the other. until then policy should take precedence. 70.19.122.39 (talk) 14:12, 28 September 2012 (UTC)
And it is editors, not users, who need to consider whether using |page=, |pages= or |at= is most appropriate. --Redrose64 (talk) 16:42, 28 September 2012 (UTC)
  Jason: let's take this back to the top. You asked if it was "technically feasible" to have the software determine the proper use of "p." versus "pp." depending on the supplied values. To answer very narrowly, I believe the specific answer is "yes, it is technically feasible".
  But as has been explained here, this in no way means it would be a good thing to do. Especially as there would undoubtably be performance issues. Which you said we should not worry about (per WP:PERF), which I say you have misunderstood. You might not agree, but at this point it appears consensus is against you.
  Now where you are being annoying is, in having asked a simple question in a seeming simple desire to know the answer, you now argue the point. It seems that, after all, it was a loaded question, that you really have an agenda, and that you want an answer other than what you have gotten. Which agenda is based on a postulated "usability issue". Sorry, but 1) I (for one, and I believe the others here as well) do not see that you have demonstrated any usability issue, and 2) I really do not feel like arguing the point.
  If the bottom line is (as you said above) that you are "unclear" as to the extent I may agree with you "that there is a problem", then I can resolve this very readily: No, I do not agree that there is a "usability" problem. Beyond that, I do not care to argue the point.
~ J. Johnson (JJ) (talk) 18:56, 29 September 2012 (UTC)
While you may be able to get the template to detect whether there is a hyphen or dash in the page field (with uncertain performance implications) what there appears to be no solution for is how to determine whether this is a page range or some other page numbering system - numbering schemes like 5-103 are not that uncommon and need to be accomodated. This kills this proposal dead in the water.Nigel Ish (talk) 19:54, 29 September 2012 (UTC)

Feasible and fast for "pages=n"

It would be easier to auto-adjust option "pages=" which seems the worst case (leave "page=" separate), as pages=n is wrong in perhaps 45,000 articles as 9% incorrect (91% ok), but an auto-adjust of "pages=" could fix most, as then 99% correct use of "p." singular. I have run a "feasibility study" and found it feasible and quick (1/1,000 second) to detect a typical page-range "3-7" or comma-set "3, 7" or ampersand-pair ("5 & 9"). However, to reduce confusion, I would limit use to "pages=" rather than "page=" which could still be reserved for hyphenated page numbers, such as "A-7". Otherwise, "pages=A-7" would be considered as plural range "pp. A-7" but "page=A-7" would still be "p. A-7". If every citation used "pages=" then the extra overhead would be less than 1/3 second for every 200 citations combined. For citations which used singular parameter "page=" there would be no extra overhead. We can get lightning-fast performance from smart templates if we are careful about where to add clever features, and I have seen many people using "pages=56" to show incorrect "pp. 56". Templates can perform amazing tasks, such as:

  • {{convert/spell |17,000,000,000,001 |mi|ly|abbr=off}} seventeen trillion and one miles (2.8918325153954 light-years)

A better quick algorithm to detect the plural "pp." would be:

{{#iferror: {{#expr: {{{pages|528-32}}}00000 }}
| pp.
|{{#ifexpr:{{{pages|528-32}}}00000 < 1 |pp.|p.}}
}}

Any alpha page id would be treated as plural, such as "pages=A7" but that allows "pages=iv - 2" to correctly show "pp."

Anyway, I think "pages=56" could be detected, very quickly, as being "p." singular. In fact, I think I have added that to Template:Cite_quick. -Wikid77 (talk) 21:25, 2 Oct., 12:27/15:19, 3 October 2012 (UTC)

Hmm, that is an interesting idea. If I understand you correctly, you are suggesting that |pages= should render as "page" where it finds only a single page value. (But not having |page= expand to "pages", which is the initial proposal.) I speculate that the argument for this is that many editors have templates with "pages", and don't take the "s" off when the have only a single page number. (And perhaps the counter-argument is that templates should not condone sloppiness or laziness, but should issue big, red warnings?) I see one possible problem, where editors have intended (or understood) |pages= to be a page count, which is properly "pages" with a single number. Perhaps that should be deemed a misuse of the template? ~ J. Johnson (JJ) (talk) 23:34, 2 October 2012 (UTC)
The example templates have "pages=" which fosters incorrect use: So, the widespread use of the plural form "pages=n" is likely caused by some blank example templates showing option "pages=" rather than "page". As for the count of total pages, some people use "pages=999 pages" which would show as "pp. 999 pages" either way. -Wikid77 12:27, 3 October 2012 (UTC)
Yes, that last bit is a definite error, but not, I think, one that the template should try to anticipate and correct. ~ J. Johnson (JJ) (talk) 17:49, 3 October 2012 (UTC)

Cite_quick detects "pages=n" as singular

I have upgraded fast Template:Cite_quick to detect when only one page number is placed in "pages=n" to show "p." rather than "pp." for a singular page number. Examples:

  • {{cite web | title=My page | pages=56 }} "My page". p. 56. {{cite web}}: Missing or empty |url= (help)
  • {{cite quick|web|title=My page|pages=56}}
  • {{cite quick|web|title=My page|pages=5-9}}
  • {{cite quick|book|title=My book|pages=3, 4, 9}}
  • {{cite quick|book|title=My book|pages=34.2}}
  • {{cite quick|book|title=My book|pages=34/38}}
  • {{cite quick|book|title=My book|pages=3, 4-6, 9}}
  • {{cite quick|book|title=My book|pages=5 & 93}}
  • {{cite quick|book|title=My page|pages=34&ndash;37}}
  • {{cite quick|news|title=My page|pages=890}}
  • {{cite quick|book|title=My book|pages=890 pages}}
  • {{cite quick|journal|title=Paper|work=Science|pages=701 ' 'ff ' '}}

Since the method seems to work, I think it could be used in {cite_web}, {cite_book} or {cite_journal}, etc. Assuming only half of citations use "pages=..." then the overhead would average 1/2000th second per citation, or total 1/10th second more for 200 cites (half using "page=" or none). -Wikid77 (talk) 13:12/13:42/15:19, 3 October 2012 (UTC)

Cite_web/sandbox4 detects "pages=n" as singular

I have also upgraded fast Template:Cite_web/sandbox4 to detect when only one page number is placed in "pages=n" to show "p." rather than "pp." for a singular page number. Examples:

  • {{cite web | title = My page | pages=56 }} "My page". p. 56. {{cite web}}: Missing or empty |url= (help)
  • {{cite web/sandbox4|title=My page|pages=56}} "My page". p. 56.
  • {{cite web/sandbox4|title=My page|pages=5-9}} "My page". pp. 5-9.
  • {{cite web/sandbox4|title=My page|pages=3, 4, 9}} "My book". pp. 3, 4, 9.
  • {{cite web/sandbox4|title=My page|pages=34.2}} "My book". p. 34.2.
  • {{cite web/sandbox4|title=My page|pages=34/38}} "My book". pp. 34/38.
  • {{cite web/sandbox4|title=My page|pages=3, 4-6, 9}} "My book". pp. 3, 4-6, 9.
  • {{cite web/sandbox4|title=My page|pages=5 & 93}} "My book". pp. 5 & 93.
  • {{cite web/sandbox4|title=My page|pages=34&ndash;37}} "My book". pp. 3437.
  • {{cite web/sandbox4|title=My page|pages=890}} "My page". p. 890.

Since the page format works for {cite_web}, then similar logic could be used in {cite_book}. -Wikid77 (talk) 08:03, 5 October 2012 (UTC)

(Digression into use of citation templates)

70.19.122.39, there is no policy requirement to use citation templates; they are only one of many acceptable ways to provide citations. Jc3s5h (talk) 16:48, 28 September 2012 (UTC)

nowhere did i suggest that a citation system is policy. what i said was that cs1 is a templated application of policy, and i would not force anyone to use it. conversely i am not going to agree when someone forces me not to. let's run down the obvious:
  • a citation system has no independent justification. it only exists to apply verification. it is only a component, an important one, of a larger work. therefore the presence, quality and readability of citations directly impacts the enclosing work. this is obvious
  • unlike other citation systems that mainly support original research, such as in sholarly journals, nonfiction lit, theses, etc. the wikipedia citation system exists to provide a modicum of relevance to the whole project. this is because this is an encyclopedia that "anyone can edit". unlike in other encyclopedias (most of which have no need for a formal citation system) editors and contributors are not vetted, and it cannot be presumed they are experts, knowledgeable or neutral in what they write. therefore, the wikipedia citation system has a unique role, and its relative importance is magnified. this is obvious.
  • unlike the target readership of other applications with citation systems, the readership of wikipedia cannot be presumed to be knowledgeable or experts. the citation system should therefore be more readable and complete than other systems whose intended audience is relatively familiar with the subject(s). this is obvious.
  • to help both nonexpert readers and nonexpert editors, the wikipedia citation system should have a measure of stability and consistency in presentation. this is obvious.
  • verification is not art or creative endeavor. it is painstaking drudgery. it follows logically that its associated citation system is helped along by standardisation and not by free-form idiosyncracy. this is obvious.
so now you make the call on whether a templated, properly optimized citation system is needed, and whether it should be subservient to nebulous (because they are not measured properly) claims of performance. i'm sure readers will appreciate getting potentially lower quality content, if only they can get it faster. in the meantime, anyone can ponder whether a built-in editor is needed in wikipedia. personally i cannot find another wikipedia tool that is more redundant. there's an absolute glut of good quality text+image editors for free out there. i think that in-place editing may actually represent a significant drag in system resources and performance. ofcourse i have no properly researched proof. but from what i've seen, this is par for the course here. in any case, i'm done with repeating all the obvious stuff. good luck everybody. 70.19.122.39 (talk) 13:52, 29 September 2012 (UTC)
I agree with Redrose64 on his last. And this is the talk page for CS1, which uses templates. When Lua is installed and stable, we can look at this again. --- Gadget850 (Ed) talk 01:32, 29 September 2012 (UTC)

Publication type

Prior discussion at /Archive_1#Cite_journal seems not to have concluded. {{cite journal}} takes the |type=Systematic review as in

Bloggins J (2012 Oct 24). "Recent advances in stuffology" (Systematic review). {{cite journal}}: Check date values in: |date= (help); Cite journal requires |journal= (help)

Somehow though, adding the |journal=Curr Stuff suppresses the display of |type=, as in

Bloggins J (2012 Oct 24). "Recent advances in stuffology". Curr Stuff (Systematic review). {{cite journal}}: Check date values in: |date= (help)

Can this please be corrected? LeadSongDog come howl! 17:31, 24 October 2012 (UTC)

  • Fix with Citation/core/sandbox: I have a fix in Template:Citation/core/sandbox. The problem was 2 ways to show the title of "Periodical" and I have added TitleType so that both will show the TitleType. The problem has also existed with {cite_news}, similar parameters:
  • {{cite news |author=Bloggins J |title=Recent advances in stuffology |type=Systematic review|newspaper=Curr Stuff|date=2012 Oct 24}}
    Result:
    Bloggins J (2012 Oct 24). "Recent advances in stuffology". Curr Stuff (Systematic review). {{cite news}}: Check date values in: |date= (help)
    Expected:
    Bloggins J (2012 Oct 24). "Recent advances in stuffology". Curr Stuff (Systematic review).
The extra "TitleType" in {Citation/core/sandbox} should fix the problem.
Perhaps use "format=(...)". There is also the option to instead use current parameter "format=Systematic review" as follows:
  • {{cite journal |author=Bloggins J |title=Recent advances in stuffology |format=Systematic review|newspaper=Curr Stuff|date=2012 Oct 24}}
    Result:
    Bloggins J (2012 Oct 24). "Recent advances in stuffology". Curr Stuff. {{cite journal}}: |format= requires |url= (help); Check date values in: |date= (help)
However, the parameter "type=" would be used to appear after the journal's title (not after the article title, where "(format)" appears). -Wikid77 (talk) 20:20/20:47, 24 October 2012 (UTC)
Please don't misuse format in that manner.
format: Format of the work referred to by url; examples: PDF, DOC, XLS...
If you were to use format in that manner for {{cite journal}}, then you would have to use it for all citations in the article.
The better solution would be to enable type. --- Gadget850 (Ed) talk 21:06, 24 October 2012 (UTC)
Thank you for addressing that. I agree with Gadget850, that would be an abuse of |format=. So far as reasonable, we should try to mirror standard elements of bibliographic metadata, such as the Dublin Core or x.39. What we name these elements on WP doesn't matter so much (we do after all have entrenched choices), but commingling their purposes does. LeadSongDog come howl! 16:40, 25 October 2012 (UTC)

Avoiding double-dots

I have created a fast utility, Template:Hasdot to check when a parameter ends with "." or wikilinked dot "[[Washington, D.C.]]" for limited use in rare cases. It is preferred that editors omit the dots when possible, such as by using the form "Washington, DC" (with no dots). Earlier, we had discussed having the templates remove double-dots ("..") for parameters which end with dot "." but that would increase the expansion-depth usage of Template:Citation/core, which would impact infoboxes where {cite_web} entries are automatically generated, perhaps causing those articles with infoboxes to exceed the expansion-depth limit. Now, next year, the Lua version can be enhanced to omit the double-dot ".." when it occurs. However, for now, it would be too risky to use {hasdots} for all cases, but perhaps some of the 24-25 cite forks could be changed to remove the end-dot, before invoking Template:Citation/core, such as in the "agency=Time Inc." or similar. Remember that only the "big 4 cites" (web/book/news & journal) need to be limited for total resources, whereas the other forks could have some more-extravagant options added, this year. Using Template:Hasdot will increase a template's expansion depth by +6 levels, even though it can check 200 names per second for the "." ending. -Wikid77 (talk) 18:26, 24 October 2012 (UTC)

I proposed something like this a while back Template talk:Citation/core/Archive 13#Duplicated period, but it added too much overhead. See User:Gadget850/Remove trailing period. When including publishers and agencies, we advise against including the corporate designator. --- Gadget850 (Ed) talk 23:25, 24 October 2012 (UTC)
Since when (where?) is the abbreviation for "District of Columbia" done with out periods? ~ J. Johnson (JJ) (talk) 20:49, 25 October 2012 (UTC)

Cite family templates parameter name styling

If you glance at the parameters listed at {{citation}} you can find at least four different parameter-name styles. Parameters can have names that are hyphenated (|editor-first=), underscored (|trans_title=), and two versions of run-on (|accessdate=, |YearNote=).

I recently had a need for |trans_title= which I don't often use. Because there is no consistency in the parameter naming conventions in the citation family of templates (nor, it seems, in many other templates) after a couple of failed attmpts to get the parameter right (|transtitle= and |trans-title=) I had to go look it up.

Can we pick one style for parameters, document that style, and deprecate the other styles? This change would need to be accomplished across all of the citation family. I can certainly help with the documentation.

Trappist the monk (talk) 16:40, 27 October 2012 (UTC)

Consider having a "help" parameter suggest the option names; see further below, "Have a "help" parameter correct options". -Wikid77 05:36, 28 October 2012 (UTC)
The Citation template is not part of Citation Style 1. Jc3s5h (talk) 16:57, 27 October 2012 (UTC)
But it does use {{citation/core}}, as does CS1 and the parameters are mostly the same, and they use mostly common documentation. As various editors have added parameters over the years, they have use various styles. The problem is that editors have been accustomed to these quirks, and there are many tools programmed around these parameters. YearNote is only used in core. --- Gadget850 (Ed) talk 17:05, 27 October 2012 (UTC)

@Editor Jc3s5h: If this is not the right place for this discussion, tell me where to take it.

@Editor Gadget850: I'm not arguing for removal of the "old" parameters. They can stay – they have to because otherwise thousands of templates would be broken. What I am requesting is additional synonymous parameters that all adhere to a single uniform style so that future (and current) editors don't have to learn about the quirks of some long-past editor's naming preference. Am I making any sense?

Trappist the monk (talk) 17:21, 27 October 2012 (UTC)

If this were specific to {{citation}} it should be on the talk page for that template or maybe in Help talk:Citation Style 2, but this is also relevant to the CS1 templates. In any case, the way the templates are currently implemented, every additional synonym for a parameter slows things down, and they are already slower than they should be. In addition, adding more synonyms does not seem like a good solution to the problem that we already have too many synonyms. —David Eppstein (talk) 18:44, 27 October 2012 (UTC)
If synonyms aren't a good solution, what is a good solution? Or, is the problem of non-standardized parameter name styles insoluble? not worth fixing? a symptom of other more complex problems? something else?
Trappist the monk (talk) 19:08, 27 October 2012 (UTC)
Synonyms are a good solution provided they are sensible choices, and don't cause trouble elsewhere. But when a given parameter has several synonyms, this can slow down template processing. For example, {{Citation/core}} has a parameter |Surname1=, which has no synonyms - but it's coded so that under certain circumstances, if it's blank or absent, |EditorSurname1= is used instead. These two parameters are passed in from {{citation}} as follows:
|Surname1 = {{{last|{{{surname|{{{last1|{{{surname1|{{{author1|{{{author|{{{authors|}}}}}}}}}}}}}}}}}}}}}
|EditorSurname1 = {{{editor-last|{{{editor-surname|{{{editor1-last|{{{editor1-surname|{{{editor1|{{{editor|{{{editors|}}}}}}}}}}}}}}}}}}}}}
These are used left to right, and as soon as a match is found, the rest are discarded. Thus, if a given use of {{citation}} has |last1=Smith |surname=Jones |authors=Brown, only Jones will be displayed, because {{{surname comes earlier than {{{last1 and {{{authors.
So, in this case, |last= is the primary parameter, and |surname=|last1=|surname1=|author1=|author=|authors= are its synonyms, in descending order of precedence. |editor-last= is also a primary parameter, and also has six synonyms.
Since they are used left to right, it's sensible for the most-used forms to be at the left, and the least-used forms at the right, in order to improve processing time in the majority of pages. --Redrose64 (talk) 19:42, 27 October 2012 (UTC)
FYI: That order is for {{citation}}. I recently optimized and standardized the the CS1 templates (it also made template comparison a lot easier). See Help:Citation Style 1/snippets. --- Gadget850 (Ed) talk 01:52, 28 October 2012 (UTC)
I know that it's for {{citation}} that's why I mentioned that template name twice in my post; I chose that template specifically because it's the one named in the very first sentence of this thread. --Redrose64 (talk) 12:58, 28 October 2012 (UTC)
I just glanced through Help:Citation Style 1/snippets and noticed that the order of parameter evaluation in the periodical sections seems odd. First there is:
|Periodical={{{work|{{{journal|{{{newspaper|{{{magazine|{{{periodical|}}}}}}}}}}}}}}}
then there is
|At={{#if: {{{journal|{{{periodical|{{{magazine|{{{work|}}}}}}}}}}}}
Why, in |At=, is there not |newspaper= and why does |work= come last?
Trappist the monk (talk) 14:34, 28 October 2012 (UTC)
Good point. I updated the snippets and will update the templates when there is a need. --- Gadget850 (Ed) talk 15:43, 28 October 2012 (UTC)
@Redrose64: I've learned something. Thanks. I was under the misconception that the template parameters were processed individually, left to right when clearly, that isn't true.
Trappist the monk (talk) 14:34, 28 October 2012 (UTC)
  • Have a "help" parameter correct options: In general, there will always be suggestions for better parameter names, or questions why the names are not easier. The experimental Template:Fcite_web offers the user suggestions for parameter names:

         {{Fcite_web |help |title=''Mein Seite''|trans-title=My Page}}

The tactic is to incur the slow, tedious help processing, to check the user's parameters, only when parameter 1 is "help" (or some common parameter is misspelled) to trigger all parameters to be checked for coherent usage. For example {cite_web} could warn:
  • {{cite_web |help |last=Doe|author=Doe Jones}}
    Cite_web: Found "last=Doe" & "author=Doe Jones" - use one, not both.
I have run some template-timing tests to show how 50 parameters could be tested, only when "help" or emergency, with no processing delay when the help-section was skipped for correct citations. -Wikid77 05:36, 28 October 2012 (UTC)
I think that I'm of two minds with this. I like code that emits useful, non-cryptic error messages. But. Editors are selfish. We will generally do what is most convenient so I suspect that editors using |help will fairly often leave the parameter in the cite – Yep, the cite displays the correct stuff, next edit ... – so it will be processed and thus incur the time penalty of spell-checking the template parameters until some other editor notices it and removes |help. One simple way to help ensure that |help parameters get removed sooner rather than later might be to always render the citation in red when |help is included.
Since processing time is important, and I know that it is from reading your posts elsewhere on the topic, having a uniform standard for template parameter name style will ease the processing load because it will reduce the number of possible names to check. Editors can be trained. We can learn to use |editor-last= instead of |editor-surname= (in my limited time editing wp, I don't recall ever seeing any use of a |surname= type parameter).
Choose a standard parameter name style. Add aliases where necessary. Publish the documentation with the new name style. Announce that the old style names will be deprecated on some date certain. Run a robot to change existing cites to the new name style (do this over all name spaces). At the specified date, deprecate names in the old style. Any new parameters must adhere to the standard name style before they are added to the templates. Have I missed anything?
Trappist the monk (talk) 14:34, 28 October 2012 (UTC)

Looking through the listed parameters in Editor Gadget850's Help:Citation Style 1/snippets, these are the parameters that, in a non-hyphenated and non-underscored world (which I think is the path of least resistance), should have aliases to provide the CS1 templates with a singular parameter name style:

  • publication-date – add alias publicationdate (or perhaps better, pubdate)
  • contribution-url – publicationurl (puburl)
  • editor-last – editorlast, editorlast1, ... (like authorlink1 is done)
  • editor-first – editorfirst, editorfirst1, ...
  • editor-link – editorlink, editorlink1, ...
  • asin-tld – asintld
  • author-separator – authorseparator (authorsep)
  • author-name-separator – authornameseparator (namesep)
  • display-authors – displayauthors (dispauthors)
  • trans_chapter – transchapter
  • trans_title – transtitle
  • doi_brokendate – doibrokendate
  • doi_inactivedate – doiinactivedate
  • template doc demo – templatedocdemo

These aliases already exist but the order of precedence in Help:Citation Style 1/snippets should be swapped so that:

  • chapter-url is secondary to chapterurl
  • author-mask is secondary to authormask

On a different note, why don't |ARXIV=, |ASIN-TLD=, |BIBCODE= and |ZBL= (in §identifiers) have upper case versions like the others in that section? Are both cases necessary? This section seems to be the only place where both cases are used.

Trappist the monk (talk) 00:55, 29 October 2012 (UTC)

I meant to mention this before: we use the term alias instead of synonym, but we know what you mean.
On your last: Again, different editors make for different standards. I added ASIN-TLD to core and asin-tld to each template; since it was new, I chose to keep the template version lower case.
Every added alias makes the template a bit bigger and adds some overhead. Using an order where the most used alias is first reduces overhead. I reordered some of the aliases when I reorganized all of the templates last month. We have a discussion above about reducing the aliases. --- Gadget850 (Ed) talk 10:02, 29 October 2012 (UTC)
Ok, thanks, I've changed synonym to alias in my last two posts.
You wrote "... different editors make for different standards." That is the problem. Template editors forget or ignore the fact that their templates are used by editors who work in article space. For those article-space editors, it is incumbent upon the template editors to make the templates as easy to use as possible. One sure way of making templates as easy to use as possible is to have one, uniform parameter name style so that article-space editors only need remember the parameter name not whether this particular parameter includes a hyphen or an underscore or doesn't include either – the case that I tried, apparently unsuccessfully, to describe in my opening remarks.
Yes, adding these aliases will make the templates larger, but it's for a good cause. And, if we do the things that I've suggested, the deprecated parameters can go away and the template size will shrink.
I presume that you are referring to this discussion in archive 1? If so, you and I appear to be in agreement on many points. Doesn't seem that much has come from that discussion except your work that you've noted in this discussion. How can I help?
Trappist the monk (talk) 13:24, 29 October 2012 (UTC)

Edit request on 10 November 2012

la:Formula:Cite book
Please add the above interwiki wikilink, which directs to the version in the Latin Wikipedia.
Peaceray (talk) 03:37, 10 November 2012 (UTC) I've moved this request from Template talk:Cite book. — Mr. Stradivarius (have a chat) 06:21, 10 November 2012 (UTC)

Done. Actually, this needed to be added to Template:Cite book/doc, which is unprotected, so you could have done it yourself. I have made the edit for you, however. Best — Mr. Stradivarius (have a chat) 05:07, 10 November 2012 (UTC)
OK, mahalo! I will check the doc pages going forward. Peaceray (talk) 19:59, 10 November 2012 (UTC)

Bug for reffed interlanguage links?

language=Swedish not categorizing

Discuss phase-in of Lua-based citations

Others in Template:cite web?

Citation Style documentation

Example headings?

Cite manual— merge to Cite book

Title case means....

adding |agency=

Cite web or WebCite?

Translator parameter in Cite book

Class

What does [u.a] mean?

missing space between language and title?

archive 2

Chapters and editors don't mix

Title not italic

Sections within a webpage

Cite video: rename

Cite sign → Cite AV media

Edit request for Template:Cite AV media

Edit request

{{Cite web}} bug?

Bug: issue not showing up

Using {{Cite news}} to cite web-archived physical newspaper

Original URL not rendering

Reuse of a named book citation, with a different page number?

Template:Cite episode

Cite book: chapter

Accessdate vs. Publication Date

Seasons & Episodes

Template Cite book: "Translated by John Smith."

Please change embedded explanation of "Work" in cite web template to match its description in documentation

Cite additional archived pages

Cite book from an on-line source

Citing newspapers by contemporary title

Citing newspaper ads and editorials

Is chapterurl broken?

Position of "location" versus "agency" fields

"Notes" parameter

Lua coming for more testing

Bug/typo in all cite templates

Slightly smaller typeface for the "retrieved" date?

Lua

Cite web - full parameter

Deprecated parameters

When a journal article has two years of publication, one electronical and one print year

Comparison of markup and Lua-based cites

format PDF in the Template:Cite journal/doc examples

The use of accessdate when a page is archived or dead

Error conditions

Cite encylopedia - Lua

Page enumeration conflicts

|publication-date= does not pass data to {{harv}} when verbose

How to Cite eBooks

Cite pmid

Multiple ISBNs

{{Cite book}}

Cite web format and language parameter position in rendered citation

Edit request

lastauthoramp parameter

lua: author masking

lua: |type= in {{cite news}}

lua: |format= in {{cite journal}}

lua: |department=

{{Cite journal}}: no harvid anchor with author's name in quotes

A teaser, but it's way past my bedtime

lua: |origyear= does not display when no author

Module talk:Citation/CS1

Media notes

Lang templates

Cite episode: producer and writer

Translator

lua: en dash (multiple entries) in |volume=

Parameter="origyear"

Cite web - broken display in some cases?

Press release format

"Work" Parameter for Website Citation

ORCID

Naming the illustrator or photographer in Cite book

Should the original url= be required when using archiveurl=

Consistency between work and publisher parameters in citation templates

Need help

Parameter |day of week= is broken

My Funny Valentine

Template:Cite web

Template:Cite web

Documentation: Full parameter set

ISBN

URL is not parsed correctly

section parameter missing

Cite book, at= should not be overridden by page=, simultaneous use should not be an error

Citation error query

Category:Pages using citations with accessdate and no URL

Discussion regarding the usage and cleaning of accessdate

Having an editor results in "In"?

Authorformat parameter

'Cite web' used more than once.

Proposal for comment parameter

Cite-web#language

Template:Cite web#Title Unclear

Editors in addition to authors

Full date not showing in "cite web" template

"eds." not appearing in cite encyclopedia template

Cite episode deprecated parameters

"Googlebooks" parameter

How to give author names in different scripts?

Please help make documentation consistent

csdoc and maps

Proper style for PDF page mismatch?

Proposal to rename tracking categories

Embedding a page-specific url within Cite_book when the book has its own article

What happened to sectionurl?

Related Articles

Wikiwand AI