ಮಾಡ್ಯೂಲ್ ಚರ್ಚೆಪುಟ:Citation/CS1/Feature requests

message: This page is used to make requests for new features for the Lua based CS1 templates. Please understand that the priority is to update and debug the older templates before implementing new features. Completed feature requests are archived at Module talk:Citation/CS1/Feature_requests/Completed

message: Titles should be wrapped with markup indicating the language. --— Gadget850 (Ed) talk 14:37, 29 March 2013 (UTC)
replies: text: How would this actually work?  You have some template examples in mind maybe?  Dragons flight (talk) 18:57, 8 April 2013 (UTC)
replies: text: :See .  --  Gadget850 talk 23:38, 26 April 2013 (UTC)
replies: text: ::Let me be a bit more specific.  First, which elements would you have the  apply markup to?  Title?  Title and Chapter?  Title and Periodical?  Secondly, do you want to use the existing templates, e.g. actually call  when getting ?  Or is it sufficient to bypass the templates and just add a span and (sometimes) a category?  Also, is there a automated way of knowing that "Spanish" maps to "es", etc.?  Dragons flight (talk) 23:52, 26 April 2013 (UTC)
replies: text: :::I was looking at that. We will have to roll our own, as I don't see a template that converts the full language name to the ISO form. Or, we could create a new 'lang' parameter that uses the ISO and overrides 'language'. I would think we could apply dir="rtl" where applicable. Might be best to do this in a separate module that could be used elsewhere. --  Gadget850 talk 00:53, 27 April 2013 (UTC)
replies: text: ::::I habitually enter, say, , then have to go back and change it :-( Your proposed new  parameter would be much appreciated. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 16:19, 17 May 2013 (UTC)

text: I think this ought to wait until someone converts the language template tree to Lua, so we have a good list of code-to-language mappings.  What's needed basically already exists, but as presently implemented its scattered across hundreds of lang subtemplates, which isn't very usable for us.  Dragons flight (talk) 22:32, 20 May 2013 (UTC)
replies: text: :I'm not sure what "the language template tree" is, but there's already a language name library available in Lua: #invoke:Sandbox/Liangent/LanguageName|languageName|es}} -> . Liangent (talk) 12:55, 29 May 2013 (UTC)
 I believe that this request has been implemented. Example: 
– Jonesey95 (talk) 04:34, 20 December 2013 (UTC)
The code to language conversion is done, but not the language markup. 
The above example, renders as (less COinS):

text: Will Ferrell. La Casa de Mi Padre (in Spanish).
What we need is:

text: Will Ferrell. La Casa de Mi Padre (in Spanish).
See .
--  Gadget850 talk 13:12, 20 April 2014 (UTC)
thread_title:  Language 

message: The CSS styling for  has been defaulted, so it now formats the contents as italics, while adding the semantic meaning of a title. Thus the current use of italics to format the main work title can be replaced by .
--— Gadget850 (Ed) talk 01:04, 28 March 2013 (UTC)
* What a contorted way to confuse everyone everywhere: Everyone knows that most titles are to be placed in quotation marks, as article titles which far outnumber others. Historically, book titles were underlined, because in handwritten documents, the cursive script is somewhat italicized, and the underlined text was obviously a book/film title. In the search for distinctive vocabulary, we have been calling each "" with the term "cite" as the markup used to display a citation. Then we introduce a cite-tag "" which forces the rare use of italic text, to all text, within .... Naturally, most normal humans will begin to associate the term "cite text" with the styling as italic text. What a contorted way to confuse everyone, everywhere. I have a strong hunch the cite-tag will not be very much help in the long run. -Wikid77 (talk) 04:12, 28 March 2013 (UTC)
replies: text: would be used internally in the template, so I am confused as to how anyone would be confused. It has an HTML semantic value indicating the title of a work. If we want to add the semantics for an included work title which is marked in quotes, then we can easily style the tag. And with almost half a million uses of cite book alone, I would not call the italic title rare. --— Gadget850 (Ed) talk 09:30, 28 March 2013 (UTC)
replies: text: :Isn't this the problem the IP was discussing earlier, where we're really using the "title" paremeter for multiple semantic functions? Choess (talk) 18:11, 29 March 2013 (UTC)
replies: text: ::I refactored the original proposal to indicate that by title I meant the main work title. Currently, we have no separation of presentation and content. That is, the format of the main work title is always italics, and the included work is always in quotes. This presentation should be moved to CSS. Wrapping the main work title in  will present the title in italics by default. We can add a class to present the included title in quotes.

text: ::Since this would be a new feature, I will be moving this to Module talk:Citation/CS1/Feature requests. --— Gadget850 (Ed) talk 18:53, 29 March 2013 (UTC)
replies: text: :::To expand on separation of presentation and content: currently the templates include both content and presentation, that is the markup used to style the content as italics, in quotes or bold. Hard coding the presentation means that readers cannot style citations as they desire and it limits template portability. Presentation should be done in CSS. Currently the  tag has a default style of italics and has the semantic meaning of a title.

text: :::For an included work title that is presented in quotes, we can create a class with CSS styling. For example the class includedtitle:

text: :::Then you simply wrap the content in  causing the font to show as normal and the content wrapped in quotes.

text: :::  --— Gadget850 (Ed) talk 14:58, 30 March 2013 (UTC)
replies: text: ::::This allows the style to be customized per Wikipedia language version. In the CSS above, \22  is the hex code for the standard quote mark. This can be replaced with other marks: see Non-English usage of quotation marks. --  Gadget850 (Ed) talk 00:17, 12 April 2013 (UTC)
thread_title:  Presentation and content 

message: The COinS implementation guide specifies that, at least for the first author of a work, it should be possible to separate their name into first name(s), last name, and suffix. When the  templates were created, they were regarded solely as presentational, and separate parameters for suffixes weren't thought to be worth implementing. Scanning the ends of first1, first2, editor1,...and so forth for "Sr", "Jr", "II", and "III" should probably pick up most of the citations where suffixes should be moved to their own parameters. Choess (talk) 15:26, 30 March 2013 (UTC)
replies: text: We should still add parameters for those oddball suffixes. --  Gadget850 (Ed) talk 16:58, 30 March 2013 (UTC)
replies: text: :Sorry, I combined two thoughts. We'd need new "suffix*" parameters for names in general, which could be used for any suffix. The scanning I mentioned could be for a (temporary?) maintenance category to identify citations that would need to be edited to use the new parameters. Choess (talk) 17:15, 30 March 2013 (UTC)
replies: text: ::See Suffix (name). We have no guidelines for suffixes, but you are discussing generational suffixes. I need to check some style guides to see if we should include academic, professional, religious or honorary suffixes. --  Gadget850 (Ed) talk 17:20, 30 March 2013 (UTC)
replies: text: :::OpenURL (COinS) only provides a field for "name suffixes", not titles or degrees. Choess (talk) 17:32, 30 March 2013 (UTC)
thread_title:  Name suffixes 

message: Add 'translator' parameters. Should show preceded by "Translated by". --  Gadget850 (Ed) talk 19:51, 1 April 2013 (UTC)
replies: text: I would appreciate this feature. Could you code this in the same way as authors and editors (eg: "last1=|first1=" etc.), as some works have multiple translators. Mindmatrix 03:20, 2 April 2013 (UTC)
replies: text: :Just like 'last' and 'first', there would be an unlimited number. --  Gadget850 (Ed) talk 09:38, 2 April 2013 (UTC)
thread_title:  Translator 

message: Can someone familiar with this module add code to enable Internet Archive links for books etc. For example, the open library code OL16525337M is the book "A concise etymological dictionary of the English language", which also has LCCN 11035890 and Internet Archive code cu31924008779690. Thanks. Mindmatrix 03:20, 2 April 2013 (UTC)
replies: text: And Google Books ls_XijT33IUC. What other archive systems are used? --  Gadget850 (Ed) talk 09:42, 2 April 2013 (UTC)
replies: text: :at WebCite users can archive single webpages. the Internet Archive also crawls for site/page snapshots and these may follow the rate of change of the originals. Google Books is different, as it may act more like an online publisher than an archival service. 70.19.122.39 (talk) 00:25, 3 April 2013 (UTC)
Here is the id_handler example for LCCN from Module:Citation/CS1/Configuration.
parameters = {'LCCN', 'lccn'}                    How specified in the citation template, i.e. LCCN=
link = 'Library of Congress Control Number'      Wikipage to link to at the ID label
label = 'LCCN'                                   Text to use for the ID label
mode = 'external'                                Indicates an external link (the typical case)
prefix = 'http://lccn.loc.gov/'                  Start of the url to use with the ID
suffix =                                       Anything to include in the url after the ID
COinS = 'rft.lccn'                               Where to map the data in COinS
encode = false                                   Whether the ID must be urlencoded
separator = ' '                             Separator to use between the ID label and the ID
When given LCCN=123456, this generates output that looks like:
LCCN 123456 = LCCN 123456
If you can figure out how to update the fields for Internet Archive, Google Books, or some other ID scheme, then they would be easy to add.  A few ID schemes (including Open Library) don't easily map to this format and have to be specially handled, so that is possible too, but it would take more effort.  Dragons flight (talk) 19:13, 8 April 2013 (UTC)

text: Internet Archive has various media (text, audio, video), but they all appear to have the same URL pattern (https://archive.org/details/identifier). Should we create one entry and disregard type, or create separate entries for each, some of which may have subtypes? (For example, some of the audio files could use a handler for Live Music Archive instead of Internet Archive.) I think one handler is probably the better option. Mindmatrix 15:53, 10 April 2013 (UTC)
replies: text: :In general, I tend to think that less is more in cases like this unless there is a strong reason to differentiate.  However, I don't really know much about the Internet Archive, so I'm not really a good person to judge.  Dragons flight (talk) 16:37, 10 April 2013 (UTC)
thread_title: Internet Archive

message: Add  as an alias to . Negative logic like setting a parameter to false to enable a feature is foreign to the average editor. 'prearchive' better describes the feature for preemptively archiving the link. --  Gadget850 (Ed) talk 16:30, 6 April 2013 (UTC)
replies: text: I am seeing a number of uses of  which is meaningless. --  Gadget850 talk 12:37, 31 October 2014 (UTC)
thread_title:  prearchive for deadurl 

message: Check for 'postscript' with more than one character. I'm seeing some odd stuff inserted. --  Gadget850 (Ed) talk 19:30, 6 April 2013 (UTC)
replies: text: My present reaction is that it may be too late for this.  There appear to be too many people doing things like , plus User:Citation bot has been putting a message about  in the postscript.  Insisting that it ought to be only one character seems a bit futile at this point.  Dragons flight (talk) 22:25, 20 May 2013 (UTC)
replies: text: :Perhaps just a hidden tracking category to see what is out there. --  Gadget850 talk 02:04, 21 May 2013 (UTC)
thread_title:  postscript check 

message: If a citation includes a wikilink to the current page, it becomes bolded:
Propose: If the wikilink is to the current page, then remove the linking. --  Gadget850 (Ed) talk 16:18, 12 April 2013 (UTC)
replies: text: If this is done, it should be done via CSS.  Removing the irrelevant italics, the output is styled
replies: text: :Module talk:Citation/CS1/Feature requests

text: Setting ".citation .selflink { font-weight:normal; }" will remove the bold.  Dragons flight (talk) 18:05, 12 April 2013 (UTC)

text: If this is done, then it should apply to all links.  I've seen lists of books in author pages where the list is constructed with CS1 templates that include .  See Andrew Hunt §Bibliography.

text: —Trappist the monk (talk) 14:43, 27 April 2013 (UTC)
replies: text: :Yes, the suggested CSS would eliminate the bolding associated with such links regardless of where they occur in the citation.  Adding that (or not) doesn't actually affect the Module, it would need to go in Mediawiki:Common.css (or similar).  Dragons flight (talk) 16:36, 27 April 2013 (UTC)
replies: text: ::Yep, it does.  Tested in my common.css and citation wikilinks to the current page aren't  anymore.  I gather that this change needs to be made to MediaWiki:Common.css.  Shall I make an edit request there?

text: ::—Trappist the monk (talk) 11:43, 28 April 2013 (UTC)

text: It would make more sense to me to throw an error in these cases for correction, as these items of various types (author/title) probably just shouldn't have the links rather than being removed by the template. Where an error might get messy would be in things like cite doi, which are by their nature not necessarily on the page which is linked. Hmm. --Izno (talk) 03:44, 28 April 2013 (UTC)
replies: text: :I'm inclined to disagree.  There is nothing wrong with wikilinks that point to the current page as long as the link is disabled in the citation.  This allows editors to reuse whole citations; it allows  to transclude text from one article to another with self-linking citations intact.  I don't see a need for error messages here.

text: :—Trappist the monk (talk) 11:43, 28 April 2013 (UTC)
replies: text: ::And citation templates. I agree with Trappist. --  Gadget850 talk 13:06, 28 April 2013 (UTC)
replies: text: :::Just exploring another option. I'm not particularly attached to it. --Izno (talk) 13:20, 28 April 2013 (UTC)
replies: text: ::::The CSS can deal easily with redirects and wikilinks that occur in places other than link parameters.  Trying to accomplish the same breadth of error checking in Module logic would be performance prohibitive.  One could check a few of the obvious parameters, e.g. authorlink, but I don't really see how that improves over the CSS suggestion.  Dragons flight (talk) 22:13, 20 May 2013 (UTC)

text: I'd suggest that people make a request for this at MediaWiki talk:Common.css.  Dragons flight (talk) 22:13, 20 May 2013 (UTC)
thread_title:  Check for wikilink to current page 

message: Add 'formatsize' to indicate the size of the linked document. This should show right after 'format' and in the parenthesis. There is already a bot filling in PDF sizes for another template, so it can be repurposed to detect if 'format' is defined, then add 'formatsize' if it isn't already defined. --  Gadget850 talk 18:24, 26 April 2013 (UTC)
replies: text: (format, formatsize)? (Feature request brought to you by Wikipedia:Templates for discussion/Log/2013 April 24#Template:PDFlink.) --Izno (talk) 13:41, 27 April 2013 (UTC)

text: presumably to be filled in for known file types (PDF, XLS, ...), and not for things not in the list like hardcover, handout, etc. For streaming media, the file size is rarely known up front, unless it's hosted as a file (such as on Commons), so perhaps not filled in for video, but perhaps for AVI, MP4, etc. --Lexein (talk) 03:36, 28 April 2013 (UTC)
replies: text: :video is not a format, but a medium, and should be inserted as a value for type (per the so-called documentation). video formats are: (various) tape formats, (various) disc formats, film etc. AVI, MP4, etc. are not video formats: they are digital file formats and should be used with the appropriate (digital) type = webcast/e-video/downloadable media etc.

text: :the confusion begins with type, a parameter name that only a geek would love, since it can mean anything. apparently, aliasing it with "medium" would be too obvious for some people.

text: :get yer stories straight!

text: :70.19.122.39 (talk) 12:54, 29 April 2013 (UTC)

text: It occurs to me that we might alleviate some of the confusion going forward by aliasing  as  to emphasize that we are talking about a digital file.  If that were done, a new size parameter could be called .  Dragons flight (talk) 15:52, 29 April 2013 (UTC)
replies: text: :'urlformat' might be better, since it indicates that it modifies 'url', since there seems to be confusion. Then 'urlsize'.  --  Gadget850 talk 16:08, 29 April 2013 (UTC)
replies: text: ::I'm not sure about 'urlformat' (as opposed to 'fileformat').  My initial reaction is that 'urlformat' suffers much the same problem as 'format', in that people may be inclined to assume it means the format of the work described at the other end of the URL and put things like "book" or "video" in there.  'fileformat' seems closer to the intended use.  Dragons flight (talk) 22:06, 20 May 2013 (UTC)
thread_title:  Format size 

message: Could anybody move it to Lua? --DixonD (talk) 09:26, 10 May 2013 (UTC)
replies: text: it has some novel parameters, including the unique facility of editor-specified page section links (). in the doc, this parameter perhaps belongs under "In-source locations" rather than under "Title"? while useful, the parameter name anchor is confusing and should be more user-friendly.

text: i also like that any or all wikisource-related icons can be hidden.

text: the doc also misidentifies type: this parameter does not provide "additional information about the media type of the source". the medium is fixed for all wikisource sources: it is a digital, online host, formatted as a wiki. as documented at the template page, type provides information about the  or  of the source.

text: 70.19.122.39 (talk) 17:45, 11 May 2013 (UTC)

text: I've done a few more conversions this last weekend.  I've been handling these roughly in order by number of transclusions.  The 1100 uses of cite wikisource is roughly in the middle of the list of what is left.  We'll probably get to it eventually, but it will likely be months before all of the 20+ minor templates are converted.  Dragons flight (talk) 22:38, 20 May 2013 (UTC)
thread_title:  [[Template:Cite wikisource]] 

message: We should add an ORCID parameter for each author (and possibly one for ISNI) as discussed at Help talk:Citation Style 1/Archive 2#ORCID Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 15:41, 17 May 2013 (UTC)
replies: text: If I understand correctly, the proposal is to create a parameter for each author that could specify their associated ORCID, and if there is no local wikilink for that author then to add an external link from the author's name to the associated ORCID database entry?  Dragons flight (talk) 02:20, 21 May 2013 (UTC)
replies: text: :Why would it be dependent on the authorlink? If the page is ported to another site, that link may not exist. --  Gadget850 talk 02:28, 21 May 2013 (UTC)
replies: text: ::If there is an article about an author, then the ORCID link will be on that page. It seems unnecessary to include it in every reference, but I'd be content that we did, if that's what others want. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 13:21, 29 May 2013 (UTC)

text: :Yes. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 13:21, 29 May 2013 (UTC)
thread_title:  ORCID 

message: We should add HTML classes, identifying the various parameter values, by way of a microformat, as discussed at Module talk:Citation/CS1/Archive 6#HTML classes. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 16:13, 17 May 2013 (UTC)
thread_title:  HTML classes 

message: :See also above #Template:Cite wikisource
The  is not used for many of the templates that call wikisource  (See for example  -- There are currently over 12,000 articles in :ವರ್ಗ:Wikipedia articles incorporating text from the 1911 Encyclopædia Britannica of which over 3,000 link to wikisource).  
For wikisource to be used for templates such as  it would need to be refocused.  The reason why it is not used very much is because not all the articles in these large encyclopaedias have been ported to Wikisource. So we need two parameters one to handle the case were the text is available on wikisource and one where it is not. As over time more more encyclopaedias and other large works will gradually be made available on Wikisource, this problem of gradual availability will not go away in the foreseeable future.
The way this problem is currently handled is to use  and place a wrapper around it (I have [User:PBS/Notes#List of PD Templates|list of dozens] on my notes page), most of which use as a de facto standard:
*title= —  is used for non-wikisource articles
*wstitle=  —  is used for wikisource articles
The different scripts wrapped around   handle the specific requirements, but most are similar (and some of these parameters are hard coded):
*iconstr — can be one of two icons  and  depending on whether wstitle is set.
*noicon —  to turn off the display of the lead icon.
*prescript —  for handling attribution as per WP:PLAGIARISM. In most cases this string is ""
*inline  —  alters the wording of the prescript from "This article" to "One or more of the preceding sentences"
*wstitle —  if the title is on wikisource, otherwise use "title="
*prewstitle —  needed for the wikisource prestring starts [[s:...
*postwstitle —  needed for the wikisource poststing ends  ...]]
*display —  used as a display in place of "wstitle=" so that things like disambiguation extensions can be hidden.
*Sometimes the handling of the Wikisource string, involves including other parameter(s)such as  or  or whatever into prewstitle or postwstitle  — see for example . Most of the templates that use "wstitle=" will only set the "url=" it "title=" is set.
It seems to me that it should be fairly easy to incorporate these requirements into this module and allow much of the code in the current scripts could be junked as it would allow all the other parameters standard to be passed in without the need to do so explicitly (as had to be done previously). -- PBS (talk) 13:22, 14 June 2013 (UTC)
thread_title:  Wikisource 

message: Why is there a restriction on using "chapter" and "section" at the same time? It seems to me there are legitimate need for the two to be used at the same time.Here is a book which has volume, sections and chapters:
*Bowen, Dr. Henry Lee; 1953; "Chapter 9. Victory in China"; The Army Air Forces in World War II; Volume V The Pacific: Matterhorn to Nagasaki June 1944 to August 1945; Section II, Aid to China: The Theater Air Forces in CBI; University of Chicago Press.
-- PBS (talk) 13:33, 14 June 2013 (UTC)
replies: text: 'section' originates from . When I merged it into , I made 'section' and 'chapter' aliases. See below for more. --  Gadget850 talk 17:42, 14 June 2013 (UTC)
replies: text: :I think that is not the best way to go. I have shown you above an example of where a book uses sections and chapters. -- PBS (talk) 09:27, 15 June 2013 (UTC)
thread_title:  Chapter and section 

message: A part= parameter would be useful, see for example:
* The United Service Journal and Naval and Military Magazine where there are volumes divided into two parts for each year in the volume.
*
*
-- PBS (talk) 13:41, 14 June 2013 (UTC)
replies: text: Also useful would be column (col.), paragraph (para.); track; hours, minutes and seconds; act, scene, canto, book, part, folio, stanza, back cover, liner notes, indicia, colophon, dust jacket, verse and probably a lot more. But this is why we have the catchall 'at' field where you can add free text where 'chapter' and 'page' don't exactly fit. --  Gadget850 talk 17:45, 14 June 2013 (UTC)
replies: text: :By that argument volume may as well be removed! A difference is made between chapter and page. A similar difference needs to be made between volume and part. In parts page numbering often restarts. Most of the items you have listed in your first sentence are attributes of the same physical book (and are other ways of pinpointing information within a physical book). Part is different, it frequently describes a physical book with its own page numbering. -- PBS (talk) 09:26, 15 June 2013 (UTC)
thread_title:  Part 

message: If the value ends in punctuation, then suppress the separator/postscript to prevent extra punctuation. Example:
--  Gadget850 talk 14:05, 21 July 2013 (UTC)
thread_title:  Separator suppression 

message: This is a reminder, in case it hasn't been implemented yet, of the RfC re consistent date location, Help_talk:Citation_Style_1/Archive_3#RFC:_Consistent_date_location. – Jonesey95 (talk) 14:18, 19 November 2013 (UTC)
thread_title:  Consistent date location 

message: Our documentation says not to use wikilinks in author parameters. We could create a hidden error message and category for articles that have wikilinks in author parameters. It may be possible for a bot to then convert these links to authorlink parameters. 
See discussion at User_talk:Citation_bot#removal_of_authors. – Jonesey95 (talk) 15:48, 30 January 2014 (UTC)
thread_title:  Detect and report wikilinks in author parameters 

message: Integrate  into the CS1 templates. This would take two parameters:  and . --  Gadget850 talk 12:45, 31 March 2014 (UTC)
thread_title:  Sfnref 

message: An idea posted by  elsewhere, recorded here for posterity: "Add code to Module:Citation/CS1 that will put citations with |authorn=et al. into a separate specific category." 
I imagine this as a maintenance category rather than a "CS1 error" / "incorrect syntax" category. Let's discuss at some point to see if there are editors interested in filling in the remaining authors, editors who object to people doing so, or other opinions/ideas. – Jonesey95 (talk) 15:53, 14 May 2014 (UTC)
replies: text: Also when et al. is included in .

text: I think its an error condition; et al. is not an authors name, it is simply an indicator that there are unlisted authors.  I'm wondering if there shouldn't be some mechanism by which editors can inform the template that not all authors are listed so that Module:Citation/CS1 will add a properly formatted et al. to the citation but that same et al. won't be included in the COinS metadata (as happens now with ).  This is much like  except that all of the authors included in the citation template are displayed  followed by et al. – perhaps,  or something similar.

text: —Trappist the monk (talk) 18:07, 14 May 2014 (UTC)
thread_title:  Add "authorn=et al." to a maintenance category 

message: Currently, supplying a parameter of the form "|arxiv=1409.7951 [physics.atom-ph]" produces a messy error:
And trying [ doesn't improve it all that much:
It would be nice if there were some way to include the arXiv class in new-style identifiers.  It's not critical, but it's normally included in arXiv citations in print, and if it's WP:MOS to omit it, a comment in the template docs would be nice.
In Lua, I imagine simply expanding the syntax of legal arxiv identifiers would be simplest, but an additional template parameter in the style of Template:Cite arxiv is also okay.  The latter allows a class, but has the problem that it's not possible to list journal, volume, issue, page numbers, etc. for papers that are published peer-reviewed:
Thank you! 71.41.210.146 (talk) 12:30, 1 October 2014 (UTC)
replies: text: What is an arXiv class? --  Gadget850 talk 14:23, 1 October 2014 (UTC)
replies: text: :The arXiv classification is explained here and here. The folks at arXiv.org recommend including it in citations, but we do not render it well. It appears to me that it would best be included in CS1 templates as a separate parameter to make validation, presentation, and linking easier. – Jonesey95 (talk) 15:44, 1 October 2014 (UTC)
replies: text: :: The arXiv used to assign submission identifiers that started with a subject classification.  This was annoyig if a paper was originally misclassified; reclassifying it required assigning a new identifier.  In 2007, they changed to a system where permanent identifiers were purely numerical, with the classification appended as extra information.  It's not essential, but customarily appended as additional information about a paper. 71.41.210.146 (talk) 21:33, 1 October 2014 (UTC)
thread_title:  arXiv class would be nice 

message: Create a UAfeatures parameter, where features depended upon by the referenced media to present the referenced information are specified. e.g. Cookies, Javascript, Flash. — Preceding unsigned comment added by Mattmill30 (talk • contribs) 03:54, 17 November 2014‎ (UTC)
thread_title:  UA features 

message: Trappist the monk at Help talk:Citation Style 1 sent me over here.
I’d like to request the support of circa year ranges in CS1, for example "c. 303 – c. 325" (which is the format per MOS:DATERANGE).
The last paragraph of the lead of Development of the New Testament canon contains several CS1 date errors ("Check date values in: |date= (help)".  For example, the citation  renders as "".  According to MOS:DATERANGE the preferred form would be "c. 303 – c. 325", although that produces the same error.  "303–325" works, but omits the circa.  "c. 303" works, but omits the range.  I've tried various other combinations without success.
At least for the Eusebius reference, it's a series of several writings, and the approximate range of years in which they were written is known, but not the exact dates.  For example, because of the dedication of the last part, it's known to have been completed before 325, but whether it was 323 or 324 is not known.  Some of that is covered at Church History (Eusebius).  I believe the same applies to the start date.  So using circa is reasonable.
Any other suggestions welcome.  Rwessel (talk) 21:02, 4 December 2014 (UTC)
replies: text: I support this request. We get requests related to "c." more frequently than any other date-related request than I can think of (now that ranges are generally supported). In many cases, we suggest using  and putting the publication date of the actual publication being cited in , but citation templates are often used to provide a consistent format for a list of publications within the body of an article, in which case  is not desirable. – Jonesey95 (talk) 23:14, 4 December 2014 (UTC)
replies: text: :We could use the same date algorithm but simply allow c. and AD before the date and BC, AD, BCE, and CE after the date (if I am reading WP:ERA correctly). --  Gadget850 talk 20:07, 7 December 2014 (UTC)
replies: text: ::Any thoughts on when such a change might be implemented, or a possible work-around?  Rwessel (talk) 07:12, 5 January 2015 (UTC)

text: ::Allow me to second Rwessel's last post. This is a serious readability issue for such a long list of references, which is difficult enough to read without the error messages. Texas Dervish (talk) 19:40, 6 January 2015 (UTC)
thread_title:  Circa year ranges - CS1 date error at [[Development of the New Testament canon]] 

message: May be we could improve the accessdate checking to rule out improbable dates of access. Probably the date when wiki was started should be an earliest possible accessdate. Have just seen article List of department stores of the United Kingdom with some accessdates of 1914! Keith D (talk) 19:20, 7 December 2014 (UTC)
replies: text: Since  requires URL (and maybe also requires that Wikipedia existed), we could set a minimum year. The World Wide Web article says that the oldest known web page dates from 1991.

text: We could also test the access-date for future dates. I believe that we already test the year for dates greater than next year (since publications like magazines can have next year in their date). – Jonesey95 (talk) 19:26, 7 December 2014 (UTC)
replies: text: :What should be the limit for future access dates? It would seem that the minimum must be current server date+1 because 12:00:00 UTC today is 00:00:00 tomorrow in New Zealand.

text: :* – UTC time when this page last refreshed (Purge)

text: :* – NZST (UTC+12)

text: :* – NZDT (UTC+13)

text: :Accepting current UTC date+1 allows editors to enter their local 'today's' date without error.  If they use their local 'tomorrow's' date, there will be an error message for at most 24 hours after which there is no error.

text: :—Trappist the monk (talk) 20:38, 7 December 2014 (UTC)
replies: text: ::Looks good to me. --  Gadget850 talk 22:16, 7 December 2014 (UTC)
replies: text: :::Same here. Keith D (talk) 22:36, 7 December 2014 (UTC)
replies: text: ::::Today+1 is fine with me. I sometimes enter a date that is tomorrow (to me) when it is already tomorrow in the UTC time zone (I know, UTC isn't really a time zone, but you get the idea). – Jonesey95 (talk) 00:04, 8 December 2014 (UTC)
replies: text: :::::The current method of checking errors only considers information stored in the template (and could presumably consider the system time). If someone enters a date 2 days in the future, and no one does anything about it, after a day passes the error message will go away. I think that really diminishes the usefulness of the message. Jc3s5h (talk) 18:24, 14 January 2015 (UTC)
replies: text: :::::: Do you have a proposal that is better than the one above? – Jonesey95 (talk) 23:28, 14 January 2015 (UTC)
replies: text: ::::::: I don't have a better proposal. In a much more restricted editing environment, where the editing software knew that a citation was being entered (as in Microsoft Word) I would block the edit from happening at all, but the Wikipedia editing environment is too flexible for that. Jc3s5h (talk) 21:32, 15 January 2015 (UTC)
replies: text: ::::::::So what's the current status of this request? If it makes a difference, I'm fine leaving future alone if it will get it moved in faster...Naraht (talk) 22:44, 15 January 2015 (UTC)
Making notes to myself for this topic.  mw:Extension:Scribunto/Lua_reference_manual#mw.language:formatDate refers to mw:Help:Extension:ParserFunctions#.23time.
Wikipedia started  15 January 2001.  Using  we can get the number of seconds since 1970-01-01T00:00:00 UTC for the dates 2001-01-15, keyword 'today', and keyword 'tomorrow':
*2001-01-15 →  → 
*today →  → 
*tomorrow →  → 
So then the value in  must not convert to less than 979516800 seconds nor more than  (tomorrow).
—Trappist the monk (talk) 17:56, 2 April 2015 (UTC)
thread_title: Improve accessdate checking

message: :see also: Module talk:Citation/CS1/Feature requests#Add "authorn=et al." to a maintenance category
Detect "et al." in an author field. --  Gadget850 talk 02:03, 14 December 2014 (UTC)
replies: text: And having detected it, what then?

text: —Trappist the monk (talk) 03:13, 14 December 2014 (UTC)
replies: text: :Trigger an error. I have recently found it in author fields for some reason. --  Gadget850 talk 23:31, 14 December 2014 (UTC)
replies: text: ::Yeah, so have I.  In fact, Monkbot, when it finds et al. in , is guilty of converting it to   But I guess I was looking for some sort of idea about what should be done instead of simply adding an error message.  What do we suggest that editors should do to get CS1/2 to display et al. outside of misusing , , and ?  Do we tweak the definition of  so that when  the rendered author list has et al. but the COinS data does not.  This might also be applied to .  We could invent  and  or some such similar to do the same sort of thing.  We'd need to worry about interaction with  when the author list has more than n authors so that  and  don't both add et al. to a rendered citation.

text: ::—Trappist the monk (talk) 11:36, 15 December 2014 (UTC)
replies: text: :::I usually see  or  with multiple authors and et al. --  Gadget850 talk 14:36, 15 December 2014 (UTC)
thread_title:  et al. 

message: We currently convert hyphens and em dashes in page rages to the proper en dash. Do so for dates as well. --  Gadget850 talk 19:04, 12 January 2015 (UTC)
replies: text: Some hyphens in dates, such as in the YYYY-MM-DD format, should stay as hyphens, so the programming will need to have a bit of subtlety. – Jonesey95 (talk) 21:56, 12 January 2015 (UTC)
thread_title:  Convert dashes in dates