1796:
checking; centrally coordinated changes in the display format of citations, perhaps even dynamically adjusted to user preferences or output media; generation of indexes for reverse-lookup, which pages in citations are referred to in which articles; potential template features like direct linking to specific pages in conjunction with certain external resources like Google Books; possibility for bots to completely reorganize any information related to citations based on automated scripts would this become necessary in the future - for example because citation templates would be split up into several templates, or all data be moved to
Wikidata; various other external uses which might benefit from information about specific pages in citations, f.e. improved search engine functionality. If we don't store the information in a parameter now, editors will likely have to retrofit it somewhen in the future. Editors working on an article might have the page information readily available right now, so the info could be added with minimal effort, but many of them might not provide it simply because there is no well-defined place to put it. Future editors may not have the reference available to them, but even if they have, looking up the information again takes more time than it would have costed the original editor. That's what I call a "lost opportunity" and a "waste of precious editor time".
1547:
and cons, none of them would break existing citations. I'm open for other solutions as well as how to actually render the output (append the specific pages to the inclusive range, put them in brackets, etc.). What I do not support is to place the specific page outside the cite template as it defeats the whole purpose of using templates to aid machine readability and give a consistent, but still easy and centrally maintainable output. Placing the info outside the template is like missing an opportunity and it puts the burden to maintain such free-flow information on future editors. I see your point that a specific page is a sub-object of a page range covering a whole article, and that it could therefore be put into a different template as well. However, it is trivially easy for bots to extract the info from one template and move it to another large-scale and over millions of articles, would the community decide to reorganize this somewhen in the future. But if the info is only provided as free flow text following a template, reorganizing it requires manual editing. This is why any such info belongs into dedicated parameters, not free-flow text. --
3029:<span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=article&rft.jtitle=kannada.oneindia.com&rft.atitle=%E0%B2%A6%E0%B2%BF%E0%B2%9F%E0%B3%8D%E0%B2%9F+%E0%B2%AA%E0%B3%8D%E0%B2%B0%E0%B2%A4%E0%B2%BF%E0%B2%AD%E0%B2%BE%E0%B2%B5%E0%B2%82%E0%B2%A4+%E0%B2%AA%E0%B3%8A%E0%B2%B2%E0%B3%80%E0%B2%B8%E0%B3%8D+%E0%B2%85%E0%B2%A7%E0%B2%BF%E0%B2%95%E0%B2%BE%E0%B2%B0%E0%B2%BF+%E0%B2%B0%E0%B3%82%E0%B2%AA%E0%B2%BE+%E0%B2%AE%E0%B3%8C%E0%B2%A6%E0%B3%8D%E0%B2%97%E0%B3%80%E0%B2%B2%E0%B3%8D&rft.au=Sagar+Desai%2C+Yadgir&rft_id=http%3A%2F%2Fkannada.oneindia.com%2Fliterature%2Fpeople%2F2012%2F0308-woman-of-substance-d-roopa-moudgil-aid0038.html&rfr_id=info%3Asid%2Fen.wikipedia.org%3AHelp+talk%3ACitation+Style+1%2FArchive+16" class="Z3988": -->
1251:- you turn to date C page 123, start at the beginning of page 123 - no earlier - and go through maybe 3/4 of the page before you find the relevant text, probably stated using slightly different wording, but it's there and supports Claim Y in article X. If you don't find it before you get to page 124, the ref does not support the claim. Either way, job done. Now imagine that ref Z is exactly the same except that it shows "pp. 108-127" - you turn to page 108, where the article begins, and need to go through a little more than fifteen pages before you find Claim Y. If you don't find it by the time you get to page 128, you wonder if you missed it somewhere and check through the whole thing again, by which time you're pissed off with the whole thing. --
1980:, as it happens at the same time when the citation is copied, and the editor who does must have the reference available in order to cite from it, so the effort is minimal. What IMO should be avoided is storing citation-related information outside of a citation template, because this will require manual reediting (instead of bot editing) if the output format of the template or the organization of citations changes in general (for example, when the info is moved to Wikidata). The reediting problem could be solved also by using two templates, but the other issues require all the info to reside in a single template.
1820:, so using such parameters would cause article page ranges and specific pages to be displayed in different locations in a citation, which is highly undesirable as it breaks the logical flow. Even if this wouldn't occur at present, another editor could always add a parameter or the community could decide to change the order of displayed template information for some reason in the future. Therefore, the info should be made part of the template in order to ensure a coherent output in the future without a need for manual reediting.
31:
1824:
as a major problem that we will have to edit the page parameters when copying citation templates to other articles. My point here is that as soon as we've put the information into parameters, we're on the safe side, because it enables bots to convert the information into whatever new format and organization we might need in the future. Much better than not providing the information at all (or in unparsable free-flow text outside a template).
3606:*/". If the timestamp is 14 digits long, a pending "*" should generate a "wildcard" error, because the timestamp is fine. For timestamps of length 1 to 13, we have two error conditions, "timestamp" and "wildcard", but since apparently only one error can be shown at a time, it would be better to display the "wildcard" error first, so that "wildcard" errors would be consistently shown for all cases of "/<timestamp: -->
576:, magazines as well as journals, is to give the full page range. This has various benefits, including showing how big the article is (giving an idea of how much material it has, and how comprehensive). If one uses a source only once, and doesn't want to add a separate short cite simply to provide a specific location, just add the specific page number (or section or whatever) following the citation template. E.g.:
1738:"small problem with links" was back on 4 April, and is about using access dates with specific pagination. As a quick comment on that, I think access dates are generally more appropriately applicable to the whole source. But if someone were to, say, check only one "fact" out of several that were cited from a source, then that access date would be specific in the same manner as pagination, and best handled
2051:
specific usage of a source in an article must be parameterized in some kind of template so that it is readily accessible for some feature we don't yet have. Well, if you want to prepare for that I suggest you urge everyone use Harv, but that is a different question than what we have here. Similarly for any discussion of any new features ("well-defined places"?) that might be added.
3321:
contribution2-de=Vorwort, contribution-author1-en=Contributor, contribution-author2-de=Beitragender. Or we could extend the prefix notation supported by script- parameters to many other parameters as well, like in title=en:Title, title=de:Titel, contribution1=en:Preface, contribution2=de:Vorwort, contribution-author1=en:Contributor, contribution-author2=de:Beitragender.
1988:, as it requires only minimal template editing and basically could be had in days, without breaking any existing citations and without getting in the way of any future developments. Editors could start providing specific page info now, so waiting years for a perfect solution is wasting uncountable opportunities to improve articles in those years.
1964:
cases, and your example further up is one of them) when appending the specific pages cited as free flow text or putting it in another template following the main template. It's only possible when putting all that info into the main template, even if this means that it carries invariable and variable information then. Let's face it: It already
2944:))" error message suppression concept to this (and other parameters which could possibly match parameters like chapter, quote, contribution and their variants)? It would not allow us to prevent the message from occuring proactively (as we cannot predict parameters implemented in the future), but it would be an easy to remember workaround. --
1175:
formal as to use full citation together with short citations, identifying the "specific page(s) or place in a cited source that contains the information that supports the article text" within a cs1|2 template using one of the in-source location parameters is appropriate and should be preferred over listing all of the source's pages.
1125:- of the source is entirely unaffected by what parts are specifically cited in the text, or how many times. If it were otherwise the full citation would have to be modified every time a specific cite was added or removed. If you must use full citations in-line (that is, without short cites) just add the specific locations
1654:
article has a different citation. Also, the cite/citation templates have no way of pointing into an article, to show where the material is used. (Even when named refs are used to create links at specific locations, the contained citation has no way of indicating which source pages are applicable at each location.)
279:
imagine how identifying all of the source's pages in a citation helps a
Knowledge reader verify the content of our articles. Searching through an entire journal article is more difficult than searching through a single page – even if you have an electronic copy and can figure out a workable ctrl+f search term.
3611:
length 0 to 14 and it triggers special behaviour in all such cases. So, if this behaviour is an error for us in a citation template (for normally good reasons), our "wildcard" error message should be shown in all such cases as well instead of only for the special case of a zero-length timestamp. From
3130:
and there are other descriptors that can ofttimes be used in place of 'abstract' in forms similar to those listed above: available, captions, commentary, introduction, manuscript, notes, options, original, originally, partially, portions, preface, subtitles, summary, vernacular, and probably yet more
1983:
In either case, it may still take years before the citation framework gets reorganized to solve some conceptual issues (and when this happens the transition will for sure be bot-assisted, similar to when inter-wiki links or authority control info were moved to
Wikidata), but this should not hinder us
1823:
Regarding "invariability of citations". I see your point here and like that idea in general, but thinking about a better data organization in the future shouldn't hinder us to provide the necessary framework to enter the data now, even if it is following a more pragmatic approach. I don't consider it
1799:
Regarding "providing page ranges as template parameter but specifically referred-to pages outside the template". This approach depends on page ranges to be the last information displayed by citation templates, so that specific page information can be appended outside the template. However, often this
1653:
about how the source is used in an article. Ideally, the citation for a source is (aside from differences of style and presentation) essentially invariant for all articles, regardless of how it is used. Conversely, if the citation template includes each article's specific use of the source, then each
1630:
whether the pagination is single or multiple. The issue is whether the pagination pertains to the entire source, or just the page(s) of the specific material cited. I think the case has been made generally that both are important, and the issue is how to accommodate both. Kanguole suggests a bot, but
1242:
to give the whole page range as an aid to locating the article. Knowledge has
Article X, containing Claim Y, which you doubt, but there is a reference Z. Ref Z indicates that the information may be found in Journal A, article B, date C, p. 123. You go to the library, find (or have brought to you) the
1107:
to indicate "number" - i.e., to distinguish between single and plural. That specific locations are often just single pages, while sources are usually multiple pages, does not warrant this distinction you would overload onto these parameters. Exceptions are common, and your proposal would indeed break
3049:
Relevant to your "working your way through" rather than the technical issue noted above, I do find it a pity that informative language information, like "in
Chinese with English abstract" has now been replaced by "In Chinese and English", which to me means something rather different. Is this a price
1963:
I did state that both page-related infos should be grouped together in a citation (in a format making it possible to distinguish between them, of course), as distributing page-related info all over the place breaks the logical flow for readers. However, this isn't possible (except for in exceptional
365:
I think giving the entire page range might go back to the days when, as a courtesy, libraries would send copies of an article to another library. This way, an engineering major who had a student job as a library aide could make a copy of a French-language history journal while hung over from a party
3567:
is to hold the url of an archived copy of the source that supports the
Knowledge article text. Sending the reader to a search results page does not serve that purpose. Allowing Internet Archive to choose which page it displays is inappropriate. It is the editor's duty to make sure that the value
3525:
The only error condition, which can be considered "harmful" is the "save command" error, so the link should be suppressed only when encountering this case. However, at present, the link is suppressed on all error cases, which is particularly inconvenient, as it makes it even more complicated to fix
2645:
It looks like the check is detecting "type =" in the title field as a missing pipe. That's a false positive. I don't know the best way to fix it, but I replaced "=" with "=", its HTML equivalent, and the error message went away. Not very pretty. I tried {{=}}, but it didn't have any effect.
2100:
of the source should also not change. Now you say you don't mind a little reediting, but wny should every editor that copies a full citation have to delete the previous editor's additions? The only reason you would force this on us is because you want to preserve the specific usage details for some
172:
if the periodical is a magazine and not a scholarly or academic journal. Others apparently disagree with Editor Izno since many many journal cites list all of the pages that an article spans which, to my mind, doesn't really aid the reader in locating the supporting text. I, however, do agree: if
3514:
Shortening the timestamp, the error messages changes to "timestamp", but it should better still display "wildcard" (because this is the stronger error of the two and it can be fixed only by removing the wildcard, not by changing the length of the timestamp, as the error message and explanations at
1546:
My approach was to offer a compromise solution which would allow us to support both, inclusive page ranges and specific pages at the same time, so that editors could either choose their preferred style, or provide both. I made two proposals how to possibly achieve this, and although they have pros
1281:
is that having the source's inclusive page range does NOT preclude specific page numbers. Your example is set up as an either/or, which is a false dichotomy. As I keep saying, you use specific page numbers in the short cites, which are specific to each use of any material. If you don't use a short
318:
If you are trying to find a paper in a bound volume of a journal in a library (and, yes, sometimes you still have to do that!) then the number of the first page is very helpful. The same applies to a chapter in book, or any other kind of contribution you want to find within a printed work. The end
3623:
used as references. In some of these cases, it might make sense to allow wildcards (it definitely does in this particular case). So, we could either strictly rule out the usage of these templates for such purposes, or we could be happy that they are useful for other related formatting purposes as
3600:
Ad 1) Yes, I see why it is displaying a "flag" error, but the purpose of the error message (and related documentation) is to help editors fixing the problem. In this case, the error message is misleading as the problem is the trailing "*", not some flag. Therefore, it would be more appropriate to
1968:
contain variable information right now - and large scale -, so we're not making things worse in any way. (Regarding invariable and variable parts of citations, specific page info is only one variable info, any context-specific info like the handling of languages or dates is another - and larger -
1174:
to list all of the pages occupied by the source material (all of the pages of a journal article, all of the pages of a book chapter). Listing all of the pages may be appropriate in bibliographies or when an article uses full citations with accompanying short citations. When an article is not so
3552:
The required length of a timestamp is 14 digits; any other timestamp length is an error. In this case the error message is correct because the timestamp has the correct length so the error message should not identify it as a failure. For the purposes of this test, a wildcard error message only
2050:
As to where the material specific pages should be included, I have suggested two places. 1) In a short cite (e.g., with Harv). 2) Or, where a source is cited only once and an editor doesn't want to set up a short cite, simply appended to the full citation. To which you object, saying that every
1698:
template or in one of the Harv/sfn family of templates. It's not possible to have an access date or an archive date other than for a URL inside the template; if you provide them in the main citation, they will be ignored unless there is a URL there. Sometimes you can get round this by using e.g.
1075:
On the metadata question, it is fairly clear from the OPENurl specs that rft.pages should only be used when the item cited is part of a collection item, i.e. a journal article or contributed chapter in a book (denoted by rft.genre being article, bookitem or proceedings) and that in such cases it
255:
When citing journal articles, it's standard academic practice to give the page range; similarly when citing chapters in books. The rationale is that in both cases we are dealing with a contribution: the 'published entity' is the journal volume or the book; the page range locates the contribution
3869:
I've modified the test. If the timestamp is incomplete and has a '*' suffix then the archive url is not modified for preview mode. If the timestamp is incomplate but does not have a '*' suffix then the archive url is modified for preview mode so that the timestamp is no longer than six digits
3848:
It would be enough for us to just display "invalid parameter", but if we go the extra mile and display more specific error message for their features, why don't we model the scope of our allowed ranges after their allowed parameter ranges as well? To answer the question, if we have a (14-digit)
3674:
I'm not convinced. We have stated that the requirement for timestamp is 14 digits; anything more or less is an error. A flag is two lowercase letters followed by an underscore; anything different is an error. Perhaps we should get rid of the wildcard error message since '/*/' is a zero-length
1697:
to placing specific pagination (or other specific location information) outside the citation template (I do it all the time); the "small concern" I expressed above was about what happens when it is linked via a URL. This applies whether it's put inside the ref tags but outside the cite/citation
1542:
Just for the records, I was trying to help Naraht as well. I have run into this "problem" often enough and while I typically provide page ranges because it is common practise for journal articles (and because it helps when searching for or trying to obtain an article), I also acknowledge that a
1285:
You also fail to consider what happens when a source is used more than once. In your conception the page range could include every page specifically cited, but there would be no indication of which page goes to which use. For a short but heavily cited source these page numers approach the page
1203:
That documentation is clearly incorrect when the these templates are used in lists, e.g. in bibliographies, further reading lists and targets of short references. I would maintain it also does not describe common practice when these templates are used inside ref tags. The examples in those doc
3831:
Regarding preview. Yes, that's much better already. We could make it even more convenient for editors to select the correct snapshot, if the template would automatically append a "*" to an incomplete timestamp in preview, if it does not contain a "*" already. Thereby, we'd force archive.org to
278:
I might be persuaded that identifying all of the pages of an article or a chapter has value in a bibliographic listing of the author's writings, though I'm not really sure what that value is because identifying both the article title and all of its pages seems redundant to me. I am hard put to
1795:
Regarding "missed opportunities". If information is given as free-flow text outside of any framework, it isn't parsable, so it is lost for machines to read and thereby for any potential output they might generate. Possible benefits from including it in the template: parameter format and range
190:
Indeed, I disagree: the full page range is part of the identification of the article, and it is standard practice to give it for journal articles and contributed chapters of edited books. The specific page number is also useful information, but in these cases it would have to go outside the
3476:
to a defunct site, which, however, is archived at archive.org. Whilst the usage of the template for this purpose is a bit unorthodox, I'd still like to point out a few oddities in the behaviour of the template and error message currently displayed: "|archive-url= is malformed: flag".
3320:
Alternatively and much more flexible, but this would require conceptual changes elsewhere as well, we could allow optional parameter suffixes indicating the language of the argument of a specific parameter, something like title-en=Title, title-de=Titel, contribution1-en=Preface,
388:
I agree with you re the page number where the supporting text can be found, at least for contributions longer than a "few pages". However, I'm not sure there's a consensus for this for journal articles, particularly since it often means multiple references using something like
286:
I think that this 'academic practice' is inappropriate for a general audience; much like abbreviated journal titles are inappropriate for those outside of the specialty. I wonder if this practice is a result of laziness on the part of our editors who are aided by tools like
2476:
could very likely be used to double check the year/date. Quite often, a cite arxiv (say from
September 2012) will be upgraded to a journal cite after it's published (say in January 2013). The bibcode will reflect the actual year of publication, so this should raise a "check
1865:
should be templated (put into parameters), just in case there is some future use for that data. Please note that I am not arguing against templating such data. My argument is that the full citation (as prepared by the cite/citation templates), and particularly the
2871:
Right--that's what I thought I would see with a plain text representation of the regex. The optional white space is obviously the cause of the problem in this instance--thanks wikitext parser not being particularly rigorous with template parameter invocations ;).
2758:(though I know you're watching the page): I'm not sure about using nowiki's to work around this maintenance error. Users unfamiliar with the maintenance category aren't going to understand why we're seemingly adding a nowiki to around the equals sign. Thoughts? --
1503:
I am not aware that you are owed any apologies. I am generally pleased to offer explanations where something is not understood, and to consider why an explanation falls short, but it seems to me that the problem here is due to inattention on your part. ~
3604:
Ad 2) Yes, but for the purpose of helping editors fixing the error, it would be better if the template would generate "wildcard" errors not only for the special case of "/*/" (with zero-length timestamp), but also for any other case of "/<timestamp:
295:{{cite journal|last1=Mosher|first1=DF|last2=Wing|first2=DA|title=Synthesis and secretion of alpha2-macroglobulin by cultured human fibroblasts.|journal=The Journal of experimental medicine|date=1 February 1976|volume=143|issue=2|pages=462-7|pmid=55456}}
3503:
That is, the timestamp is 14 digits long (indicating a date close to the last snapshot before the site went offline) but it deliberately has a "*" suffix added, so that archive.org shows the timeline allowing users to move backwards in time as well.
1150:"An editor may use any one of the following parameters in a given citation to refer to the specific page(s) or place in a cited source that contains the information that supports the article text." – where "one of the following parameters" refers to
1329:
extensively for well over six years. Only yourself and
Kanguole seem to be assuming that Naraht is doing that. I happen to know - having checked Naraht's contributions from just before and just after they posted here - that they were working on
1657:
But to return to the objection, what kind of "opportunity" are we missing if article specific usage is not incorporated into the full citation? What purpose is served? Why should a bot be moving such article specific information anywhere else?
1380:
Redrose64, whether you are speaking for yourself, or for Naraht, my comments are still applicable to your narrative demonstration of why specific page numbers are needed. In which I actually concur. My issue with your comments starts with your
1913:
usage, in polluting the latter with the former. Having specific page numbers following a citation (where they are not otherwise templated) is parsible at least by humans; mixing these kinds of data is unparsible. This amounts to misuse of
780:
the source? Or that when similar parameters, that use the same kind of data, but in different contexts, are given the same names it will blur the distinction, create confusion, and raise questions and discussions exactly as we have here? ~
1976:. It would be nice if any editing could be avoided (but it can't in the current implementation), but I don't consider it a problem to adjust (or delete) the specific page info when copying citations to different articles. This is not
596:
I regularly use this approach, but it does create a small problem with links. If the information is on p.13 and the source is online, it's reasonable to expect a link to this page. So where do you put it? If you use something like
1543:
specific page number makes it easier to verify the information if the article is accessible on a page-by-page basis (online or in front of me), so I would prefer if there would be a dedicated place to put this information as well.
3688:
necessary to link to a wildcard archive listing, then it is not necessary to use cs1|2; for this example (were it appropriate though I think it is not) it would be better to make a simple external wikilink and not use cs1|2 at
3849:
timestamp and append a '*', this should be indicated as "wildcard" error, but if we append a "+" instead (which has no special meaning for archive.org), this could be counted as a "flag" error (or just as "invalid character").
3758:{{cite web/new |title=harri deutsch electronic science (hades) |url=http://www.harri-deutsch.de/ |dead-url=yes |archive-url=http://web.archive.org/web/20131030225414*/http://www.harri-deutsch.de/ |archive-date=2013-10-30}}
3874:{{cite web/new |title=harri deutsch electronic science (hades) |url=http://www.harri-deutsch.de/ |dead-url=yes |archive-url=http://web.archive.org/web/2013103022541*/http://www.harri-deutsch.de/ |archive-date=2013-10-30}}
3928:{{cite web/new |title=harri deutsch electronic science (hades) |url=http://www.harri-deutsch.de/ |dead-url=yes |archive-url=http://web.archive.org/web/2013103022541/http://www.harri-deutsch.de/ |archive-date=2013-10-30}}
1593:
mentioned the possibility of having two sets of page parameters above, but wondered if it was too late for that. The transition might be possible, though. Bots could be designed to do the right thing in most cases.
3978:
I guess we will just have to disagree about wildcards and flags. It seems pointless to continue that discussion since neither of us is convincing the other. Wildcards and flags together in the url are incompatible:
2485:
correspond to a year, while digits 3 and 4 correspond to a month (YY = 91 to 99 = 19YY, YY = 0 to 90 = 20YY). Preprints are updated, and retain their identifier through their lives, but it will mean that the value of
3019:(the sandbox) primarily because I foresee the need for other language code tables (codes for languages not supported by MediaWiki, for instance) so having all language codes in a single location makes sense to me.
204:. But that is clearly not the case being considered. I don't see how I can agree to the page range identifying the article, much less why it should be standard practice when no other types of works do the same. --
3516:
333:
Isn't that why someone invented the table of contents? A proper citation includes the page number where the supporting text can be found. No need to include the article's first page number (or its last).
3832:
display the timeline for the editor to choose from instead of letting archive.org select a nearby snapshot automatically (with sometimes "unexcepted" effects and no easy means to select another). Compare:
2195:. While you are correct that, for citation purposes, we usually are not interested in the number of pages for books themselves, yet we also cite chapters, prefaces, etc. in books, for which an inclusive
2143:
it should be material specific: we don't need to know how many pages the book has, but it is more useful for books than for journals to specify where in the book the relevant information can be found. —
3607:*/" with timestamps of lenght 0 to 14. That's what I meant by "wildcard errors are stronger than timestamp errors". My point is that from archive.org's perspective "*" can be appended to timestamps of
3380:
2996:
122:
I have a fact from a magazine (using cite journal). The article in the magazine goes from page from 11-14, *but* the single fact being referenced is on page 13. So, do I have pages=11-14 or page=13?
959:
The inclusive page numbers cited should encompass the the complete article, not just the portion you used. (Specific page references appear parenthetically at appropriate places in your text ....
1247:
matter is that it has dates and page numbers in the top or bottom margins (of most pages). You don't know if the article begins on page 123 of the issue for date C or on an earlier page, and you
935:§16.106: "Inclusive (first and last) page numbers are usually provided for journal articles in bibliography entries; they not only help the reader find the article but indicate the length of it."
2185:
in books, which is not a good idea: being inconsistent confuses people, and would encourage the "wrong" usage in journals. And such a distinction would be practically impossible when using
3619:. However, our citation templates are used for other purposes as well, for example to format work lists, "further reading" sections or - rarely - "external links" sections, where they are
1631:
I don't see how that could be done (at least not on any inherent distinction of the data), nor how that would be useful, the users of this information being readers and editors, not bots.
1273:
a source specific page numbers (or similar) are certainly helpful (and I would have required), as you have illustrated. And it doesn't appear that anyone here is arguing that we should
2969:
230:. The reader should not be expected to hunt through the entire article to find the supporting statement. The identification of the article is not a reason for using a page range, but
3575:
Perhaps we can allow the archive url to show in preview mode (save command would never show) so that editors can pick one snapshot from a wildcard search result. I'll think on that.
1397:" That Nahrat is not using short cites (which neither I nor Kanguole assume, so you are wrong to suggest that) is perhaps part of the problem, but not necessarily relevant, because
735:
a source, different parameter names would help to distinguish them, while making them equivalent only weakens the distinction, leading to the kind of confusion we have seen here. ~
3317:
Couldn't we define a special separator character, where the evaluation stops, allowing the remainder of the text to be any free-flow text just displayed without any error checking.
1671:. Where I have suggested appending specific pagination to the citation template is for where editors use a source once, and don't want to bother with any kind of short cite. ~
1204:
pages, on the other hand, do describe the usual practice of giving full pages for journal articles and contributed book chapters. It seems we will need an RFC to settle this.
2960:
3024:
Sagar Desai, Yadgir. [Maudgil to transform bold and talented police officer]. ''kannada.oneindia.com'' (in
Kannada)<span class="reference-accessdate": -->
2833:
How? The purpose of the missing pipe test is to find missing pipes. For the purposes of the missing pipe test, a cs1|2 parameter that is missing its pipe looks like this:
3852:
Ad 2) IMO we should instead improve the detection for "wildcard" errors, so that they are displayed whenever a "*" is appended regardless of the length of the timestamp.
3043:
1170:, the assigned value may be a comma separated list of individual pages, an en dash separated page-range, or a combination of both. The documentation does not require
1884:. If Harv is too much trouble for a single-use reference we could look at a special template for that purpose. But no such purpose is served by bastardizing "pages=".
3549:
Flag error because the trailing '*' is occupying the first flag character position, is not a letter, and is not followed by another flag character and an underscore.
3338:
None of the languages are made part of the COinS metadata. But, all of the languages are used to categorize the article page in any of the various subcategories of
529:. It gunks up the appearance of the article and gratuitously splits the information you're looking for into different places, for no benefit at all that I can see. —
3995:
3810:
3695:
3581:
3387:
3346:
3295:
3150:
3142:
3059:
3035:
2976:
2906:
2858:
2753:
2734:
2527:
2463:
2443:
1190:
815:
759:
708:
604:. So you have to put a URL for the whole source, even though it's not actually needed. If designing a citation template from the start, I'd suggest something like
383:
345:
337:
328:
313:
305:
177:
4003:
3864:
3703:
3641:
3413:
3395:
3370:
3354:
3333:
2984:
2517:
3818:
3589:
2544:
Citation bot used to update cite arxiv to cite journal without fixing the year (which may still be the case, but the bot's down so hard to tell at the moment).
1198:
853:
823:
790:
767:
744:
716:
3441:
3023:'"`UNIQ--templatestyles-00000020-QINU`"'<cite id="CITEREFSagar_Desai,_Yadgir" class="citation news cs1 cs1-prop-script cs1-prop-foreign-lang-source": -->
2567:
2535:
1208:
195:
3076:
parameter value is a comma separated list of languages (or ISO 639-1 or -2 codes) recognized by MediaWiki that the module can properly categorize and format.
3072:
holds the language of the source. Extra descriptors don't fit with that basic rule. The rest of the rule is that when there is more than one language, the
2456:
2208:
2152:
556:
1760:
1725:
684:
625:
185:
2990:
2114:
2000:
1927:
1850:
1836:
1556:
1138:
1070:
538:
273:
3665:
If the character appended to the timestamp is a '+' instead of a '*', what then? The flag error message is perfectly adequate for identifying both cases.
3303:
3171:
2914:
2881:
2866:
2767:
2742:
452:
1598:
1460:
1080:
3379:
parameters in any number of the various cs1|2 templates in use in article space. Those descriptors are not languages so the module adds the article to
1513:
1478:
1440:
1357:
1306:
987:
Assuming that there would be only one page to point to, we could solve and support this case without breaking any existing citations simply by allowing
874:
412:
3259:
1222:
950:
Give the inclusive page numbers of the piece you are citing. Be sure to provide the page numbers for the entire piece, not just the material you used.
3527:
1003:
would just point to the page supporting the statement - like a bookmark. There could even be some (limited) error-checking: If both values exist, the
3233:
3196:
2781:
2611:
1108:
many existing citations. Handling exceptions with brackets or such would just make matters more arcane, to the confusion of editors and readers both.
514:
477:
1375:
547:
a source). But it is totally in the wrong place, and reflects a lack of understanding of how to use the available tools. It should be deprecated. ~
2451:
1297:, not of the which parts within it have been used in the WP text. Ideally this description is invariant across all articles, and even all Wikis. ~
1282:
cite - presumably because the source is cited only once - then (as I keep saying) just append the specific page number after the citation template.
2679:
2655:
250:
2772:
I would assume that this special case could be added to the documentation as there are other special encodings discussed in the CS1 doc already.
213:
1143:
cs1|2 does not make a distinction between full citations used with short citations and 'other' citations. The documentation, such as it is, at
749:
I am not at all sure that I understand what it is that you wrote nor how it bears on parameter aliases (which have been in the module since its
1780:
would you care to explain on what kind of "opportunity" are we missing if article specific usage is not incorporated into the full citation? ~
1466:
I'm through here. I came to help Naraht, not to be abused by J. Johnson and find that they are willing to apologise to Naraht and not to me. --
862:
page numbers that the facts were given on. To give more is both misleading and a waste of time for those who later wish to verify my claims. --
159:
844:
within the source. And it is long-established standard practice that the full citation of a source gets the full page range of the source. ~
2795:
2639:
465:
contains the full page range of the article. In addition to the other solutions, the issue can be avoided by using shortened footnotes or
2953:
3453:
1789:
2092:) record every specific use made of a source by every article. That is simply ludicrous. My argument on this (in brief) is that as the
2854:
You and I can immediately see that there isn't a missing pipe here but I am not clever enough to convey how I know that to the module.
2828:
256:
within that entity. When the article or chapter is long, I've usually also given an individual page or pages, outside the template as
3533:
Ideally, there would be some special syntax or parameter to mute the error message to allow "*" to be used in cases such as this one.
3004:
2017:
Perhaps we have gotten a little confused here, but the original question here was whether the page=/pages= parameter should have the
1899:
don't consider it as a major problem that we will have to edit the page parameters when copying citation templates to other articles.
3845:
Ad 1) For archive.org, wildcards and flags are separate features. I haven't tried but I assume they can even occur at the same time.
3205:
because as TTM notes, "there are other descriptors". My thought regarding contribution is that we relax the necessary constraint on
2937:
1680:
1038:
parameter, which could include a comma-separated list of individual pages, all checked to reside inside the page range specified by
979:
590:
260:
says above. However, I've had these 'extra' pages removed by at least one editor on the grounds that it's not normal practice. When
1874:
for that data. If such data must be templated, fine, but that should be done through a template suitable for that purpose, such as
1263:
3718:{{cite web/new |title=Title |url=//example.com |archive-url=https://web.archive.org/web/*///example.com |archive-date=2016-02-06}}
3068:
is a structured parameter (has been since
September 2013) and has rules for what it accepts. The basic rule has always been that
1626:
cited within the source is usually a single page, but often is multiple pages. But lest there be an confusion: the issue here is
375:
142:
3656:– the flag portion of the url path (if present; new form urls only) is not 2 lowercase letters followed by an underscore: 'id_'
1325:), who at no point indicated that they were using short cites - a referencing method that I am very familiar with, having used
3537:
Fortunately, these issues appear to be easy to address by changing the order of tests and modifying the patterns sligthly. --
903:
put in the specific page number(s) where the specific material ("facts") are to be found. That is what would be put into the
264:
is being used for the 'contribution', I'm wondering whether we can provide an extra parameter for the more precise location.
97:
89:
84:
72:
67:
59:
2621:
3601:
display a "wildcard" error. My point is that the check(s) should be refined to display the most appropriate error message.
1589:
Of course sometimes an article is on a single page, and sometimes the sentence you're citing is split between two pages.
1385:" uses the inclusive page range of the source. While you are not explicit about it, your narrative expresses the issue as
3138:
We don't have a mechanism to specify gradations of language use in a source. Perhaps you could invent such a mechanism?
1768:
417:
For journal articles, best practice is to give the full page range. If it's important to know exactly were, you can use
3405:
3362:
3188:
2773:
2588:
that are posted to the arxiv after being published, but these are minorities and should probably be manually bypassed.
1960:
parameters for both infos depending on their preferences (and this is also why the OP came here asking for assistance).
911:
of the source, where it is only part of a larger work (i.e., an article or chapter), is, conventionally, the full (or
543:
I agree with "blight upon the world". {rp} was an attempt to provide a useful bit of information (a specific location
3176:
Semantically this may or may not be correct. Because it may not be a contribution (different author). Perhaps, a new
3016:
1649:
the template, that the purpose of the full citation that such templates produce is entirely about the source itself,
3007:
and am about to add another. These categories are associated with a table of ISO 639-1 codes that has been kept in
2963:), Editor Izno suggested that such a mechanism should not be used. At least that is what I think was the message.
2101:
future use. Which I would not object to, except that within the citation template (and especially pages=) is the
1362:
Just to indicate the way that I've used these... I have never used Shortened Footnotes, but have on occasion used
3647:
3624:
well and offer limited support by providing some means to override the occasional error messages in these cases.
3615:
Ad 4) Yes, (as per our prior discussion about this) I agree with you that wildcards should not be allowed in a
3612:
archive.org's perspective, there is nothing special about the zero-length case, so it shouldn't for us as well.
2598:
2554:
2504:
2224:
966:§ 5.7.6, p. 187: "The entry for a magazine article ends with a colon and the page-number range of the article."
501:
439:
3650:
is in order. That text identifies the location of the error and the requirements for a properly formed flag:
491:
is a blight upon the world though. Better to have bad metadata and correct visual outputs than those horrors.
3083:
Your example is just one of many slightly different forms I've found that include the descriptor 'abstract':
3969:
3915:
3799:
2630:'s missing pipe maintenance indication? Looks like a false positive, but maybe my eyes are deceiving me. --
1341:
1322:
1183:
138:
3870:(yyyymm). This, I think, give the best opportunity of locating a suitable snapshot. Incomplete with '*':
3522:
Only when the "*" is removed, it should display "timestamp" (when the length of the timestamp is invalid).
3494:
3459:
3999:
3814:
3699:
3585:
3391:
3350:
3299:
3146:
3039:
2980:
2910:
2862:
2738:
2531:
2447:
1952:
between them in the future. At present, we have no specific rules for this, and editors use the existing
1194:
819:
763:
712:
581:. All the information is present, in a form and the place where it is understood, unlike the cryptic . ~
341:
309:
181:
2886:
Not really. If the wikitext parser did not allow spaces then the missing pipe test would be like this:
3361:@Trappist: where did you find the descriptor 'abstract' please? Maybe I'm looking at the wrong module?
2432:
2392:
2329:
2289:
403:
protects styles currently in use, so we're stuck with them, and there's no prospect of a change there.
47:
38:
17:
572:
As to the broader issue: it is mostly definitely established standard practice that the citation of a
3987:
3982:
3557:. There isn't any error weighting; all errors are treated the same, none is 'stronger' than another.
3375:
Not in the module code. 'Abstract' and all of the other descriptors that I listed were all found in
2705:
2068:
While we could be in accord on the foregoing, I strongly disagree with you in regards of having the
3526:
the error by simply clicking on the faulty link and selecting one of the available snapshots. (See
2627:
2148:
1334:, which is using the ordinary, everyday, common-or-garden method of placing a cite template inside
1326:
1144:
858:
Where is it written that it is long-established standard practice? When I cite a source, I put the
534:
3840:
3835:
3437:
3339:
3055:
1721:
751:
621:
408:
324:
269:
3860:
3637:
3542:
3409:
3366:
3329:
3192:
2949:
2777:
2712:&rft.btitle=JPL+Small-Body+Database+Search+Engine%3A+spec.+type+%26%2361%3B+Q+%28SMASSII%29
2204:
2110:
1996:
1923:
1846:
1832:
1785:
1756:
1676:
1552:
1509:
1456:
1436:
1302:
1243:
journal in question (which might be a single issue or a bound volume, it doesn't matter). What
1218:
1134:
1066:
975:
849:
786:
740:
680:
586:
552:
221:
167:
117:
2425:
2385:
2322:
2282:
421:
or similar ("See p. 17 in Smith (2012)." / "See p. 17 in Smith J. (2012) "Important article".
3953:
3899:
3783:
3743:
3572:
is valid and points to a correct copy of the source that supports the Knowledge article text.
2897:
and would still find a false positive if the exemplar just happened to be written like this:
2123:
1622:
is usually an "inclusive page range", but sometimes a single page, and the pagination of the
1129:
the citation template (as I have shown, above). That would be much more straight-forward. ~
288:
126:
8:
3511:
The error message indicates a "flag" error, whilst it should indicate a "wildcard" error.
3008:
2651:
2144:
1716:
and basically inventing a contribution title for the specific page, but this is a fudge.
1474:
1353:
1259:
870:
600:, then you can't put an access date in the citation since this produces an error without
530:
246:
2646:
If someone knows a better way, post it here and replace my workaround in the article. –
1011:. One remaining question is how this special case should be rendered - we might put the
301:
The work is done and because it was done by the machine must be correct, right? Hardly.
3433:
3400:
Well then is it only a case of finding the citations with the above incorrectly filled
3051:
2959:
When I suggested double parentheses error suppression for another maintenance message (
2727:&rft.btitle=JPL+Small-Body+Database+Search+Engine%3A+spec.+type+%3D+Q+%28SMASSII%29
2594:
2581:
2550:
2500:
2413:
2373:
2137:
1969:
part, so following your idea, this would have to be split out of the citation as well.)
1717:
1702:
1595:
1590:
1205:
1077:
617:
497:
474:
435:
404:
320:
265:
192:
3941:
3887:
3856:
3771:
3731:
3713:
In the module sandbox I have disabled the wildcard test and added preview detection:
3633:
3538:
3466:
3325:
3286:
3201:
Right, I'm tossing it at the wall. It should be a generic parameter rather than e.g.
2945:
2310:
2270:
2189:
2086:
2076:
1992:
1828:
1775:
1548:
1431:
do more than one thing at a time. Is there any part of this you do not understand? ~
1062:
400:
2523:
I suppose that this could be done. Is there evidence that such a test is necessary?
1269:
You are confusing some things. For finding specific material at a specific location
907:
parameters in Harv. Or following the full citation, as I illustrated above. But the
2606:
2562:
2512:
1661:
If we really need to capture such specific information then the template to use is
1371:
1316:
509:
447:
371:
134:
641:
point to the location of the information within the source: but they do that from
2200:
2106:
1919:
1842:
1800:
condition isn't met, as it depends on the usage of various other parameters like
1781:
1752:
1688:
1672:
1505:
1452:
1432:
1331:
1298:
1214:
1130:
971:
845:
782:
736:
676:
582:
548:
110:
1026:
cannot be used. An alternative approach would be to not change the behaviour of
46:
If you wish to start a new discussion or revive an old one, please do so on the
3681:
3255:
3229:
3167:
2877:
2824:
2763:
2749:
2675:
2647:
2635:
2602:
2558:
2508:
1467:
1346:
1252:
863:
505:
443:
239:
209:
155:
3675:
timestamp. By doing so we avoid the special case that is wildcard detection.
3126:(each of the above can use a comma separator after the first <language: -->
922:§16.3: For an article in a periodical include "Pages occupied by the article."
106:
3530:
for a related discussion how the behaviour could easily be further improved.)
3420:
How about skipping the error checks for parenthesised text? This would allow
2590:
2546:
2496:
1878:
1751:
The objection I was addressing is, of course, that raised by Matthiaspaul. ~
1665:
666:
the tmeplate. Are you sure you have closing braces in the right place? E.g.:
645:
493:
431:
257:
3314:
Are all the languages in the list put into metadata, or only the first one?
1393:
inclusive page range. Which is exactly as Nahrat initially expressed it: "
393:
1948:
in any way, quite to the contrary, I suggested several ways how to better
2664:
1367:
1363:
1312:
970:
And I could go on, but surely this should be sufficient demonstration. ~
523:
485:
468:
367:
130:
3828:
Regarding disabling the wildcard test. Not a good idea IMHO. See below.
3495:
http://web.archive.org/web/20131030225414*/http://www.harri-deutsch.de/
1645:
of the cite/citation template. My position is that it does not belong
1015:
page in brackets or - more pragmatically - just comma-append it to the
3251:
3225:
3163:
2873:
2820:
2759:
2671:
2631:
1121:
What you seem to not recognize is that the full citation - i.e., the
205:
151:
3050:
worth paying for checking that the language is correctly specified?
1019:
range. Another open question is what should be put in the meta-data?
616:
for the location of the information. But I guess it's too late now.
2819:
Is there a way for the templates to avoid these false positives? --
1641:(and perhaps others?) objection to placing the specific pagination
1311:
I am confusing nothing. I am trying to assist the original poster,
519:
I'm not sure I would put it so strongly, but I also quite disllike
108:
3988:
http://web.archive.org/web/200506id_*/http://www.harri-deutsch.de/
3983:
http://web.archive.org/web/200506*id_/http://www.harri-deutsch.de/
2585:
1984:
from providing a well-defined place to put the specific page info
3224:, and have the module figure out how to place the statements. --
1022:
If, however, there are multiple pages supporting the statement,
173:
the fact is on one page, identify that page in the cs1 template.
3933:
3879:
3841:
http://web.archive.org/web/200506*/http://www.harri-deutsch.de/
3763:
3485:
2849:
JPL Small-Body Database Search Engine: spec. type = Q (SMASSII)
111:
3836:
http://web.archive.org/web/200506/http://www.harri-deutsch.de/
3528:
Help talk:Citation Style 1/Archive 13#web.archive.org/save/...
930:§16.50: Inclusive page numbers for chapters or parts of books.
112:
2900:
JPL Small-Body Database Search Engine: spec. type=Q (SMASSII)
2025:
pagination. As to distinguishing them, I say that is simple:
728:
a source (which can be a single page) is NOT the same as the
2033:
the source inclusive page range. Are we agreed on that part?
999:
would then hold the full page range of the article, whereas
944:
MLA-6th specifies inclusive page numbers in various places.
202:
if the entire page range supported the statement being made
3753:
Edit this section and then click the show preview button:
3404:
and parsing the abstract's language into a new parameter?
2972:), the doubled parentheses solution was not well received.
1076:
should be the full page range of the article or chapter.
2233:
is capitalized in cs2 citations. Fixed in the sandbox.
1901:" More troubling is that you fail to grasp that mixing
1095:
Matthiaspaul: No, not at all. The distinction between
662:
parameter shouldn't be affected by anythng that comes
399:, and as I said above, I've had them removed. Anyway,
2708:
to percent encode each character of the html entity:
1415:
using the ordinary, everyday, common-or-garden method
1401:, it is quite possible to use inclusive page ranges (
840:
the same as the page (possibly mulitple pages) of a
579:{{citation ... |pages= 11-14}}, p.13. </ref: -->
2968:
Similarly, with regard to hyphenated page numbers (
3680:Wildcards are the equivalent of a search result.
3127:so the list for 'abstract' is 2× as long as shown)
200:I might agree that you should cite the page range
2096:itself is not changed when ever it is cited, the
1213:Yes, that documentation needs to be corrected. ~
772:What do you not understand: that pagination of a
3723:
3553:occurs when the timestamp is replaced with '*' (
3187:? Presented as "in , abstract in " or similar.
2481:value" flag. Likewise, the first two digits of
2229:I noticed that the static text associated with
461:would pollute the metadata, which assumes that
3517:Category:Pages with archiveurl citation errors
2494:has to be equal or greater to the arxiv date.
1918:, and does not serve the purposes you want. ~
807:is or should be different from the meaning of
799:is or should be different from the meaning of
238:is filled in with the title of the article. --
3684:item 9 discourages search results. If it is
2457:Cross check date/year with arxiv and bibcode?
1277:have specific page numbers for that purpose.
651:. Perhaps you momentarily confused them with
2991:moving list of |script-title= language codes
1861:Your general theme seems to be that data on
795:Why you think that for cs1|2 the meaning of
675:. Otherwise, perhaps you have an example? ~
234:a reason why you should also make sure that
2942:Why don't we extend the "<parameter: -->
2695:Perhaps a better fix is to wrap the '=' in
1897:" in your second paragraph, it is odd you "
1186:(and other of the cs1|2 templates as well).
1058:parameter, it could be treated as an alias.
1007:range should include the page specified by
957:§5.7.1 (articles in periodicals), p. 183: "
291:which returned this when I gave it a PMID:
3934:"harri deutsch electronic science (hades)"
3880:"harri deutsch electronic science (hades)"
3764:"harri deutsch electronic science (hades)"
1812:etc. Such info is displayed after that of
776:itself is not the same as pagination of a
3381:Category:CS1 maint: Unrecognized language
3250:is global to all CS1 templates though. --
3015:. I have decided to move the table into
3005:Category:CS1 uses foreign language script
2997:Category:CS1 maint: Unrecognized language
2133:should be source inclusive. However, for
1618:Kanguole touches an important point: the
1427:. The only problem is if you try to make
925:§16.5: Examples of inclusive page ranges.
3480:The provided parameters are as follows:
3025:. Retrieved <span class="nowrap": -->
2846:That pattern exactly matches with this:
915:) page range of the whole source. E.g.:
14:
3646:Perhaps a reread of the error message
3424:to be flagged as an error, but accept
2129:(the original question), I agree that
1184:Template:Cite_book#In-source_locations
44:Do not edit the contents of this page.
918:CMS-13, Ch. 16, Bibliographic forms:
721:That is not a good idea. In that the
3426:|language=Chinese (English abstract)
2626:Is there a fix that can be made for
1182:Similar instruction can be found at
608:for the full page range and reserve
25:
3454:archive-url error checking oddities
3430:|language=Chinese (Eglish abstract)
2995:I have been working my way through
2408:. Translated by Translator. Others.
2368:. Translated by Translator. Others.
23:
3102:with abstract in <language: -->
2890:<legitimate parameter name: -->
2837:<legitimate parameter name: -->
2305:, translated by Translator, Others
2265:, translated by Translator, Others
1405:the source) and specific page(s) (
319:page is just convention, I think.
24:
4021:
3017:Module:Citation/CS1/Configuration
1345:. No short cites, none at all. --
3555:http://web.archive.org/web/*/...
2688:is a legitimate cs1|2 parameter.
29:
1734:Oops, got my threads confused.
1451:Oops! My profound apologies. ~
655:in the citation/cite templates?
3120:(abstract in <language: -->
13:
1:
3106:abstract in <language: -->
2840:<optional white space: -->
2838:<optional white space: -->
669:{{citation ... |pages= 11-14
3563:I disagree. The purpose of
3486:http://www.harri-deutsch.de/
3246:might work--I don't know if
2622:Pipe missing -- specific fix
1940:No, I never proposed to mix
1279:What you seem to have missed
7:
1907:source inclusive page range
1145:Help:Citation_Style_1#Pages
1050:parameter exists without a
995:to exist at the same time.
10:
4026:
3428:at the price of accepting
3160:|contribution-lang=English
3131:that I haven't discovered.
2580:There are some cases like
2001:12:04, 30 April 2016 (UTC)
1928:22:29, 29 April 2016 (UTC)
1851:19:42, 28 April 2016 (UTC)
1837:08:58, 28 April 2016 (UTC)
1790:21:56, 26 April 2016 (UTC)
1761:19:34, 24 April 2016 (UTC)
1726:10:19, 24 April 2016 (UTC)
1681:22:25, 23 April 2016 (UTC)
1599:23:08, 22 April 2016 (UTC)
1557:22:48, 22 April 2016 (UTC)
1514:19:55, 21 April 2016 (UTC)
1479:19:01, 21 April 2016 (UTC)
1461:18:25, 21 April 2016 (UTC)
1441:00:24, 21 April 2016 (UTC)
1376:02:21, 20 April 2016 (UTC)
1358:00:10, 20 April 2016 (UTC)
1307:18:09, 19 April 2016 (UTC)
1264:11:08, 19 April 2016 (UTC)
1223:18:03, 19 April 2016 (UTC)
1209:22:37, 18 April 2016 (UTC)
1199:22:16, 18 April 2016 (UTC)
1139:21:27, 18 April 2016 (UTC)
1081:21:11, 18 April 2016 (UTC)
1071:20:01, 18 April 2016 (UTC)
18:Help talk:Citation Style 1
3952:is malformed: timestamp (
3898:is malformed: timestamp (
3742:is malformed: timestamp (
3022:
2706:Module:Citation/CS1/COinS
2400:
2360:
2344:
2297:
2257:
2241:
2181:in journals differs from
1895:need for manual reediting
1841:This needs some study. ~
1446:Naraht, please not Nahrat
1147:has this first sentence:
980:22:06, 9 April 2016 (UTC)
875:22:27, 8 April 2016 (UTC)
854:20:55, 8 April 2016 (UTC)
824:09:48, 8 April 2016 (UTC)
791:17:31, 6 April 2016 (UTC)
768:23:58, 5 April 2016 (UTC)
745:22:53, 5 April 2016 (UTC)
717:00:08, 5 April 2016 (UTC)
685:23:09, 4 April 2016 (UTC)
626:20:18, 4 April 2016 (UTC)
591:19:49, 4 April 2016 (UTC)
557:19:43, 4 April 2016 (UTC)
539:18:49, 4 April 2016 (UTC)
515:18:17, 4 April 2016 (UTC)
478:17:48, 4 April 2016 (UTC)
453:17:31, 4 April 2016 (UTC)
413:16:52, 4 April 2016 (UTC)
376:14:35, 4 April 2016 (UTC)
346:12:44, 4 April 2016 (UTC)
329:12:32, 4 April 2016 (UTC)
314:11:16, 4 April 2016 (UTC)
274:07:52, 4 April 2016 (UTC)
251:07:44, 4 April 2016 (UTC)
214:01:39, 4 April 2016 (UTC)
196:01:05, 4 April 2016 (UTC)
186:00:54, 4 April 2016 (UTC)
160:00:45, 4 April 2016 (UTC)
143:00:15, 4 April 2016 (UTC)
4004:11:44, 11 May 2016 (UTC)
3865:19:36, 10 May 2016 (UTC)
3819:14:17, 10 May 2016 (UTC)
3704:13:37, 10 May 2016 (UTC)
3642:10:13, 10 May 2016 (UTC)
3590:00:21, 10 May 2016 (UTC)
3499:|archive-date=2013-10-30
3442:16:26, 10 May 2016 (UTC)
3414:14:54, 10 May 2016 (UTC)
3275:so neither are global.
2355:|translator=Translator}}
2252:|translator=Translator}}
1634:I would like to examine
1293:is a description of the
3924:Incomplete without '*':
3679:
3673:
3396:21:38, 9 May 2016 (UTC)
3371:20:31, 9 May 2016 (UTC)
3355:21:38, 9 May 2016 (UTC)
3340:Category:CS1 properties
3334:19:55, 9 May 2016 (UTC)
3304:17:15, 9 May 2016 (UTC)
3260:15:23, 9 May 2016 (UTC)
3234:15:23, 9 May 2016 (UTC)
3197:15:09, 9 May 2016 (UTC)
3172:12:45, 9 May 2016 (UTC)
3151:17:54, 8 May 2016 (UTC)
3097:with <language: -->
3092:(with <language: -->
3088:abstract (your example)
3060:16:04, 8 May 2016 (UTC)
3044:15:35, 8 May 2016 (UTC)
3003:language categories to
2999:and have added two new
2985:21:14, 9 May 2016 (UTC)
2954:19:41, 9 May 2016 (UTC)
2915:17:24, 9 May 2016 (UTC)
2882:15:26, 9 May 2016 (UTC)
2867:15:01, 9 May 2016 (UTC)
2829:14:26, 9 May 2016 (UTC)
2782:20:37, 9 May 2016 (UTC)
2768:19:51, 9 May 2016 (UTC)
2743:13:50, 9 May 2016 (UTC)
2680:13:45, 9 May 2016 (UTC)
2656:13:27, 9 May 2016 (UTC)
2640:12:44, 9 May 2016 (UTC)
2612:02:26, 8 May 2016 (UTC)
2568:21:17, 5 May 2016 (UTC)
2536:10:54, 5 May 2016 (UTC)
2518:01:30, 5 May 2016 (UTC)
2452:13:26, 7 May 2016 (UTC)
2209:22:25, 3 May 2016 (UTC)
2153:22:35, 2 May 2016 (UTC)
2115:21:35, 2 May 2016 (UTC)
1870:parameteer therein, is
1395:pages=11-14 or page=13?
1166:In the description for
832:): the page range of a
3156:|contribution=Abstract
3087:with <language: -->
2796:Avoid false positives?
2700:. Replacing '=' with
2225:translator static text
2177:That would mean that
1409:the source) TOGETHER,
1383:Now imagine that ref Z
1339:tags, see for example
3283:alias when used with
3013:format_script_value()
2340:Cite book comparison
1893:As you eschewed any "
1289:The bottom line: the
830:as I have said before
803:and that the meaning
42:of past discussions.
3782:is malformed: flag (
3271:are both aliases of
3064:The problem is that
2943:=((<argument: -->
2889:<white space: -->
2836:<white space: -->
2468:I was thinking that
2237:Citation comparison
1942:specific pages cited
1903:specific pages cited
1863:specific pages cited
1413:short cites. E.g., "
3472:template to format
3222:|contribution-lang=
3026:7 May</span: -->
3009:Module:Citation/CS1
2891:<equal sign: -->
2839:<equal sign: -->
2721:...</nowiki: -->
2698:...</nowiki: -->
2431:CS1 maint: others (
2391:CS1 maint: others (
2341:
2328:CS1 maint: others (
2288:CS1 maint: others (
2238:
1769:page question/break
1418:{Cite magazine|...|
1327:Shortened footnotes
150:The single page. --
3960:Unknown parameter
3906:Unknown parameter
3790:Unknown parameter
3110:(<language: -->
3027:2016</span: -->
2938:Error suppression?
2805:Brief answer: nope
2424:has generic name (
2384:has generic name (
2339:
2321:has generic name (
2281:has generic name (
2236:
1946:source page ranges
1714:|contribution-url=
1591:User:Peter coxhead
948:§ 5.6.7, p. 158: "
940:§16.114: Examples.
673:, . </ref: -->
3996:Trappist the monk
3811:Trappist the monk
3696:Trappist the monk
3582:Trappist the monk
3388:Trappist the monk
3347:Trappist the monk
3296:Trappist the monk
3143:Trappist the monk
3119:<language: -->
3115:<language: -->
3114:<language: -->
3109:<language: -->
3105:<language: -->
3101:<language: -->
3096:<language: -->
3091:<language: -->
3086:<language: -->
3036:Trappist the monk
2977:Trappist the monk
2934:
2933:
2907:Trappist the monk
2859:Trappist the monk
2754:Trappist the monk
2735:Trappist the monk
2628:(86039) 1999 NC43
2528:Trappist the monk
2464:Trappist the monk
2444:Trappist the monk
2440:
2439:
2337:
2336:
2023:material specific
1624:specific material
1620:source pagination
1463:
1447:
1399:AS I KEEP SHOWING
1389:specific page(s)
1191:Trappist the monk
816:Trappist the monk
760:Trappist the monk
752:first incarnation
730:specific page(s)
709:Trappist the monk
423:Important Journal
384:Trappist the monk
338:Trappist the monk
306:Trappist the monk
178:Trappist the monk
146:
129:comment added by
103:
102:
54:
53:
48:current talk page
4017:
3973:
3967:
3963:
3957:
3951:
3947:
3945:
3937:
3929:
3919:
3913:
3909:
3903:
3897:
3893:
3891:
3883:
3875:
3803:
3797:
3793:
3787:
3781:
3777:
3775:
3767:
3759:
3747:
3741:
3737:
3735:
3727:
3719:
3655:
3571:
3566:
3556:
3471:
3465:
3431:
3427:
3423:
3422:|language=Chines
3403:
3378:
3290:
3282:
3278:
3274:
3270:
3266:
3249:
3245:
3241:
3223:
3216:
3208:
3204:
3186:
3179:
3161:
3157:
3075:
3071:
3067:
3031:
3014:
3011:in the function
3002:
2801:
2800:
2757:
2728:
2722:
2713:
2703:
2699:
2687:
2669:
2663:
2610:
2566:
2516:
2493:
2489:
2484:
2483:|arxiv=YYMM.####
2480:
2475:
2471:
2467:
2436:
2429:
2423:
2419:
2417:
2409:
2396:
2389:
2383:
2379:
2377:
2369:
2356:
2342:
2338:
2333:
2326:
2320:
2316:
2314:
2306:
2293:
2286:
2280:
2276:
2274:
2266:
2253:
2239:
2235:
2232:
2198:
2194:
2188:
2184:
2180:
2142:
2136:
2132:
2128:
2122:
2091:
2085:
2081:
2075:
2028:
2019:source inclusive
1959:
1955:
1917:
1883:
1877:
1869:
1819:
1815:
1811:
1807:
1803:
1779:
1742:of the template.
1715:
1711:
1707:
1701:
1692:
1670:
1664:
1470:
1450:
1445:
1430:
1349:
1344:
1338:
1337:...</ref: -->
1255:
1173:
1169:
1161:
1157:
1153:
1102:
1098:
1057:
1053:
1049:
1045:
1041:
1037:
1033:
1029:
1025:
1018:
1014:
1010:
1006:
1002:
998:
994:
990:
906:
866:
810:
806:
802:
798:
754:
703:
699:
695:
691:
674:
661:
654:
650:
644:
637:
633:
615:
611:
607:
603:
599:
580:
528:
522:
513:
490:
484:
472:
464:
460:
451:
420:
398:
392:
387:
296:
263:
242:
237:
229:
225:
171:
145:
123:
113:
81:
56:
55:
33:
32:
26:
4025:
4024:
4020:
4019:
4018:
4016:
4015:
4014:
3965:
3961:
3959:
3949:
3948:
3939:
3938:
3932:
3927:
3911:
3907:
3905:
3895:
3894:
3885:
3884:
3878:
3873:
3795:
3791:
3789:
3779:
3778:
3769:
3768:
3762:
3757:
3739:
3738:
3729:
3728:
3722:
3717:
3653:
3569:
3564:
3554:
3469:
3463:
3456:
3429:
3425:
3421:
3401:
3376:
3284:
3280:
3276:
3272:
3268:
3264:
3247:
3243:
3239:
3238:Alternatively,
3221:
3214:
3206:
3203:|abstract-lang=
3202:
3185:
3181:
3178:|abstract-lang=
3177:
3159:
3155:
3073:
3069:
3065:
3028:.</cite: -->
3012:
3000:
2993:
2940:
2935:
2806:
2798:
2747:
2726:
2720:<nowiki: -->
2719:
2718:whereas, using
2711:
2701:
2697:<nowiki: -->
2696:
2685:
2667:
2661:
2660:Right, I tried
2624:
2589:
2545:
2495:
2491:
2487:
2482:
2478:
2473:
2469:
2461:
2459:
2430:
2421:
2420:
2411:
2410:
2404:
2390:
2381:
2380:
2371:
2370:
2364:
2354:
2352:
2350:
2348:
2327:
2318:
2317:
2308:
2307:
2301:
2287:
2278:
2277:
2268:
2267:
2261:
2251:
2249:
2247:
2245:
2230:
2227:
2201:J. Johnson (JJ)
2196:
2192:
2186:
2182:
2178:
2140:
2134:
2130:
2126:
2120:
2107:J. Johnson (JJ)
2089:
2083:
2079:
2073:
2026:
1957:
1953:
1920:J. Johnson (JJ)
1915:
1881:
1875:
1872:the wrong place
1867:
1843:J. Johnson (JJ)
1817:
1813:
1809:
1805:
1801:
1782:J. Johnson (JJ)
1773:
1771:
1753:J. Johnson (JJ)
1713:
1709:
1705:
1699:
1693:I don't object
1686:
1673:J. Johnson (JJ)
1668:
1662:
1506:J. Johnson (JJ)
1468:
1453:J. Johnson (JJ)
1433:J. Johnson (JJ)
1428:
1417:": <ref: -->
1347:
1340:
1335:
1332:Alpha Phi Omega
1299:J. Johnson (JJ)
1253:
1215:J. Johnson (JJ)
1171:
1167:
1159:
1155:
1151:
1131:J. Johnson (JJ)
1100:
1096:
1055:
1051:
1047:
1043:
1039:
1035:
1031:
1027:
1023:
1016:
1012:
1008:
1004:
1000:
996:
992:
988:
972:J. Johnson (JJ)
904:
864:
846:J. Johnson (JJ)
808:
804:
800:
796:
783:J. Johnson (JJ)
750:
737:J. Johnson (JJ)
701:
697:
696:are aliases of
693:
689:
677:J. Johnson (JJ)
667:
659:
652:
648:
642:
635:
631:
613:
609:
605:
601:
598:
583:J. Johnson (JJ)
577:
549:J. Johnson (JJ)
526:
520:
492:
488:
482:
466:
462:
458:
430:
418:
396:
390:
381:
294:
261:
240:
235:
227:
219:
165:
124:
120:
115:
114:
109:
77:
30:
22:
21:
20:
12:
11:
5:
4023:
4013:
4012:
4011:
4010:
4009:
4008:
4007:
4006:
3992:
3991:
3990:
3985:
3976:
3975:
3974:
3925:
3922:
3921:
3920:
3871:
3853:
3850:
3846:
3843:
3838:
3833:
3829:
3807:
3806:
3805:
3804:
3751:
3750:
3749:
3748:
3711:
3710:
3709:
3708:
3707:
3706:
3691:
3690:
3687:
3678:
3676:
3672:
3669:
3668:
3667:
3666:
3660:
3659:
3658:
3657:
3630:
3629:
3628:
3625:
3613:
3602:
3593:
3592:
3577:
3576:
3573:
3561:
3558:
3550:
3535:
3534:
3531:
3523:
3520:
3512:
3501:
3500:
3497:
3491:
3488:
3474:external links
3455:
3452:
3451:
3450:
3449:
3448:
3447:
3446:
3445:
3444:
3418:
3417:
3416:
3384:
3359:
3358:
3357:
3343:
3322:
3318:
3315:
3312:
3311:
3310:
3309:
3308:
3307:
3306:
3292:
3279:is also not a
3269:|contribution=
3244:|section-lang=
3236:
3207:|contribution=
3183:
3180:that requires
3139:
3134:
3133:
3132:
3128:
3124:
3123:
3122:
3117:
3112:
3107:
3103:
3099:
3094:
3089:
3079:
3078:
3077:
3030:</span: -->
3001:|script-title=
2992:
2989:
2988:
2987:
2973:
2965:
2964:
2939:
2936:
2932:
2931:
2930:
2929:
2928:
2927:
2926:
2925:
2924:
2923:
2922:
2921:
2920:
2919:
2918:
2917:
2903:
2902:
2901:
2895:
2894:
2893:
2892:<value: -->
2855:
2852:
2851:
2850:
2844:
2843:
2842:
2841:<value: -->
2808:
2807:
2804:
2799:
2797:
2794:
2793:
2792:
2791:
2790:
2789:
2788:
2787:
2786:
2785:
2784:
2731:
2730:
2729:
2716:
2715:
2714:
2691:
2690:
2689:
2684:Yes. Because
2623:
2620:
2619:
2618:
2617:
2616:
2615:
2614:
2573:
2572:
2571:
2570:
2539:
2538:
2524:
2458:
2455:
2438:
2437:
2402:
2398:
2397:
2362:
2358:
2357:
2351:|others=Others
2346:
2335:
2334:
2299:
2295:
2294:
2259:
2255:
2254:
2248:|others=Others
2243:
2226:
2223:
2222:
2221:
2220:
2219:
2218:
2217:
2216:
2215:
2214:
2213:
2212:
2211:
2199:is helpful. ~
2164:
2163:
2162:
2161:
2160:
2159:
2158:
2157:
2156:
2155:
2145:David Eppstein
2059:
2058:
2057:
2056:
2055:
2054:
2053:
2052:
2041:
2040:
2039:
2038:
2037:
2036:
2035:
2034:
2008:
2007:
2006:
2005:
2004:
2003:
1989:
1981:
1970:
1961:
1933:
1932:
1931:
1930:
1888:
1887:
1886:
1885:
1856:
1855:
1854:
1853:
1825:
1821:
1797:
1770:
1767:
1766:
1765:
1764:
1763:
1746:
1745:
1744:
1743:
1729:
1728:
1710:|contribution=
1639:Matthiaspaul's
1616:
1615:
1614:
1613:
1612:
1611:
1610:
1609:
1608:
1607:
1606:
1605:
1604:
1603:
1602:
1601:
1572:
1571:
1570:
1569:
1568:
1567:
1566:
1565:
1564:
1563:
1562:
1561:
1560:
1559:
1544:
1527:
1526:
1525:
1524:
1523:
1522:
1521:
1520:
1519:
1518:
1517:
1516:
1490:
1489:
1488:
1487:
1486:
1485:
1484:
1483:
1482:
1481:
1448:
1426:.</ref: -->
1378:
1287:
1283:
1249:shouldn't care
1236:
1235:
1234:
1233:
1232:
1231:
1230:
1229:
1228:
1227:
1226:
1225:
1187:
1178:
1177:
1176:
1164:
1163:
1162:
1114:
1113:
1112:
1111:
1110:
1109:
1088:
1087:
1086:
1085:
1084:
1083:
1059:
1020:
968:
967:
963:
962:
954:
953:
942:
941:
937:
936:
932:
931:
927:
926:
923:
894:
893:
892:
891:
890:
889:
888:
887:
886:
885:
884:
883:
882:
881:
880:
879:
878:
877:
812:
778:section within
756:
705:
656:
570:
569:
568:
567:
566:
565:
564:
563:
562:
561:
560:
559:
531:David Eppstein
363:
362:
361:
360:
359:
358:
357:
356:
355:
354:
353:
352:
351:
350:
349:
348:
334:
302:
299:
298:
297:
282:
281:
280:
174:
162:
119:
118:page question?
116:
107:
105:
104:
101:
100:
95:
92:
87:
82:
75:
70:
65:
62:
52:
51:
34:
15:
9:
6:
4:
3:
2:
4022:
4005:
4001:
3997:
3993:
3989:
3986:
3984:
3981:
3980:
3977:
3971:
3955:
3950:|archive-url=
3943:
3935:
3931:
3930:
3926:
3923:
3917:
3901:
3896:|archive-url=
3889:
3881:
3877:
3876:
3872:
3868:
3867:
3866:
3862:
3858:
3854:
3851:
3847:
3844:
3842:
3839:
3837:
3834:
3830:
3827:
3826:
3825:
3824:
3823:
3822:
3821:
3820:
3816:
3812:
3801:
3785:
3780:|archive-url=
3773:
3765:
3761:
3760:
3756:
3755:
3754:
3745:
3740:|archive-url=
3733:
3725:
3721:
3720:
3716:
3715:
3714:
3705:
3701:
3697:
3693:
3692:
3685:
3683:
3677:
3671:
3670:
3664:
3663:
3662:
3661:
3652:
3651:
3649:
3645:
3644:
3643:
3639:
3635:
3631:
3626:
3622:
3618:
3614:
3610:
3603:
3599:
3598:
3597:
3596:
3595:
3594:
3591:
3587:
3583:
3579:
3578:
3574:
3570:|archive-url=
3565:|archive-url=
3562:
3559:
3551:
3548:
3547:
3546:
3544:
3540:
3532:
3529:
3524:
3521:
3518:
3513:
3510:
3509:
3508:
3505:
3498:
3496:
3493:|archive-url=
3492:
3490:|dead-url=yes
3489:
3487:
3483:
3482:
3481:
3478:
3475:
3468:
3461:
3443:
3439:
3435:
3434:Peter coxhead
3419:
3415:
3411:
3407:
3399:
3398:
3397:
3393:
3389:
3385:
3382:
3374:
3373:
3372:
3368:
3364:
3360:
3356:
3352:
3348:
3344:
3341:
3337:
3336:
3335:
3331:
3327:
3323:
3319:
3316:
3313:
3305:
3301:
3297:
3293:
3288:
3263:
3262:
3261:
3257:
3253:
3237:
3235:
3231:
3227:
3219:
3215:|contributor=
3212:
3200:
3199:
3198:
3194:
3190:
3184:some language
3175:
3174:
3173:
3169:
3165:
3154:
3153:
3152:
3148:
3144:
3140:
3137:
3136:
3135:
3129:
3125:
3118:
3113:
3108:
3104:
3100:
3095:
3090:
3085:
3084:
3082:
3081:
3080:
3063:
3062:
3061:
3057:
3053:
3052:Peter coxhead
3048:
3047:
3046:
3045:
3041:
3037:
3032:
3020:
3018:
3010:
3006:
2998:
2986:
2982:
2978:
2974:
2971:
2967:
2966:
2962:
2958:
2957:
2956:
2955:
2951:
2947:
2916:
2912:
2908:
2904:
2899:
2898:
2896:
2888:
2887:
2885:
2884:
2883:
2879:
2875:
2870:
2869:
2868:
2864:
2860:
2856:
2853:
2848:
2847:
2845:
2835:
2834:
2832:
2831:
2830:
2826:
2822:
2818:
2817:
2816:
2815:
2814:
2813:
2812:
2811:
2810:
2809:
2803:
2802:
2783:
2779:
2775:
2771:
2770:
2769:
2765:
2761:
2755:
2751:
2746:
2745:
2744:
2740:
2736:
2732:
2725:
2724:
2717:
2710:
2709:
2707:
2694:
2693:
2692:
2683:
2682:
2681:
2677:
2673:
2666:
2659:
2658:
2657:
2653:
2649:
2644:
2643:
2642:
2641:
2637:
2633:
2629:
2613:
2608:
2604:
2600:
2596:
2592:
2587:
2583:
2579:
2578:
2577:
2576:
2575:
2574:
2569:
2564:
2560:
2556:
2552:
2548:
2543:
2542:
2541:
2540:
2537:
2533:
2529:
2525:
2522:
2521:
2520:
2519:
2514:
2510:
2506:
2502:
2498:
2465:
2454:
2453:
2449:
2445:
2434:
2427:
2415:
2407:
2403:
2399:
2394:
2387:
2375:
2367:
2363:
2359:
2347:
2343:
2331:
2324:
2312:
2304:
2300:
2296:
2291:
2284:
2272:
2264:
2260:
2256:
2244:
2240:
2234:
2210:
2206:
2202:
2191:
2176:
2175:
2174:
2173:
2172:
2171:
2170:
2169:
2168:
2167:
2166:
2165:
2154:
2150:
2146:
2139:
2125:
2118:
2117:
2116:
2112:
2108:
2104:
2099:
2095:
2088:
2078:
2071:
2070:full citation
2067:
2066:
2065:
2064:
2063:
2062:
2061:
2060:
2049:
2048:
2047:
2046:
2045:
2044:
2043:
2042:
2032:
2024:
2020:
2016:
2015:
2014:
2013:
2012:
2011:
2010:
2009:
2002:
1998:
1994:
1990:
1987:
1982:
1979:
1975:
1971:
1967:
1962:
1951:
1947:
1943:
1939:
1938:
1937:
1936:
1935:
1934:
1929:
1925:
1921:
1912:
1911:less coherent
1908:
1904:
1900:
1896:
1892:
1891:
1890:
1889:
1880:
1873:
1864:
1860:
1859:
1858:
1857:
1852:
1848:
1844:
1840:
1839:
1838:
1834:
1830:
1826:
1822:
1810:|archive-url=
1798:
1794:
1793:
1792:
1791:
1787:
1783:
1777:
1762:
1758:
1754:
1750:
1749:
1748:
1747:
1741:
1737:
1733:
1732:
1731:
1730:
1727:
1723:
1719:
1718:Peter coxhead
1704:
1696:
1690:
1685:
1684:
1683:
1682:
1678:
1674:
1667:
1659:
1655:
1652:
1648:
1644:
1640:
1637:
1632:
1629:
1625:
1621:
1600:
1597:
1592:
1588:
1587:
1586:
1585:
1584:
1583:
1582:
1581:
1580:
1579:
1578:
1577:
1576:
1575:
1574:
1573:
1558:
1554:
1550:
1545:
1541:
1540:
1539:
1538:
1537:
1536:
1535:
1534:
1533:
1532:
1531:
1530:
1529:
1528:
1515:
1511:
1507:
1502:
1501:
1500:
1499:
1498:
1497:
1496:
1495:
1494:
1493:
1492:
1491:
1480:
1476:
1472:
1465:
1464:
1462:
1458:
1454:
1449:
1444:
1443:
1442:
1438:
1434:
1425:
1421:
1416:
1412:
1408:
1404:
1400:
1396:
1392:
1388:
1384:
1379:
1377:
1373:
1369:
1365:
1361:
1360:
1359:
1355:
1351:
1343:
1333:
1328:
1324:
1321:
1318:
1314:
1310:
1309:
1308:
1304:
1300:
1296:
1292:
1291:full citation
1288:
1284:
1280:
1276:
1272:
1268:
1267:
1266:
1265:
1261:
1257:
1250:
1246:
1241:
1240:not necessary
1224:
1220:
1216:
1212:
1211:
1210:
1207:
1202:
1201:
1200:
1196:
1192:
1188:
1185:
1181:
1180:
1179:
1165:
1149:
1148:
1146:
1142:
1141:
1140:
1136:
1132:
1128:
1124:
1120:
1119:
1118:
1117:
1116:
1115:
1106:
1094:
1093:
1092:
1091:
1090:
1089:
1082:
1079:
1074:
1073:
1072:
1068:
1064:
1060:
1021:
986:
985:
984:
983:
982:
981:
977:
973:
965:
964:
960:
956:
955:
951:
947:
946:
945:
939:
938:
934:
933:
929:
928:
924:
921:
920:
919:
916:
914:
910:
909:full citation
902:
898:
876:
872:
868:
861:
857:
856:
855:
851:
847:
843:
839:
835:
831:
827:
826:
825:
821:
817:
813:
794:
793:
792:
788:
784:
779:
775:
771:
770:
769:
765:
761:
757:
753:
748:
747:
746:
742:
738:
734:
733:
727:
726:
720:
719:
718:
714:
710:
706:
688:
687:
686:
682:
678:
672:
665:
657:
647:
640:
629:
628:
627:
623:
619:
618:Peter coxhead
595:
594:
593:
592:
588:
584:
575:
558:
554:
550:
546:
542:
541:
540:
536:
532:
525:
518:
517:
516:
511:
507:
503:
499:
495:
487:
481:
480:
479:
476:
470:
459:|pages=14–19
456:
455:
454:
449:
445:
441:
437:
433:
429:(4):14–19.")
428:
424:
419:|pages=14–19
416:
415:
414:
410:
406:
405:Peter coxhead
402:
395:
385:
380:
379:
378:
377:
373:
369:
347:
343:
339:
335:
332:
331:
330:
326:
322:
321:Peter coxhead
317:
316:
315:
311:
307:
303:
300:
293:
292:
290:
285:
284:
283:
277:
276:
275:
271:
267:
266:Peter coxhead
259:
254:
253:
252:
248:
244:
233:
223:
222:cite magazine
217:
216:
215:
211:
207:
203:
199:
198:
197:
194:
189:
188:
187:
183:
179:
175:
169:
168:cite magazine
163:
161:
157:
153:
149:
148:
147:
144:
140:
136:
132:
128:
99:
96:
93:
91:
88:
86:
83:
80:
76:
74:
71:
69:
66:
63:
61:
58:
57:
49:
45:
41:
40:
35:
28:
27:
19:
3968:suggested) (
3966:|url-status=
3914:suggested) (
3912:|url-status=
3857:Matthiaspaul
3808:
3798:suggested) (
3796:|url-status=
3752:
3712:
3634:Matthiaspaul
3620:
3616:
3608:
3568:assigned to
3539:Matthiaspaul
3536:
3506:
3502:
3479:
3473:
3457:
3406:72.43.99.146
3363:72.43.99.130
3326:Matthiaspaul
3217:
3210:
3189:65.88.88.200
3033:
3021:
2994:
2946:Matthiaspaul
2941:
2774:72.43.99.130
2723:gives this:
2625:
2460:
2441:
2422:|translator=
2405:
2382:|translator=
2365:
2353:|title=Title
2319:|translator=
2302:
2279:|translator=
2262:
2250:|title=Title
2231:|translator=
2228:
2124:cite journal
2105:for that. ~
2102:
2097:
2093:
2069:
2030:
2022:
2018:
1993:Matthiaspaul
1985:
1977:
1973:
1965:
1949:
1945:
1941:
1910:
1906:
1902:
1898:
1894:
1871:
1862:
1829:Matthiaspaul
1776:Matthiaspaul
1772:
1739:
1735:
1694:
1660:
1656:
1650:
1646:
1642:
1638:
1635:
1633:
1627:
1623:
1619:
1617:
1549:Matthiaspaul
1423:
1420:pages= 11-14
1419:
1414:
1410:
1406:
1402:
1398:
1394:
1390:
1386:
1382:
1336:<ref: -->
1319:
1294:
1290:
1278:
1274:
1270:
1248:
1244:
1239:
1237:
1126:
1122:
1104:
1063:Matthiaspaul
1034:, but add a
969:
958:
949:
943:
917:
912:
908:
900:
896:
895:
859:
841:
837:
833:
829:
777:
773:
731:
729:
724:
722:
670:
668:<ref: -->
663:
660:|accessdate=
638:
578:<ref: -->
573:
571:
544:
426:
422:
366:last night.
364:
231:
201:
125:— Preceding
121:
78:
43:
37:
3209:to require
2670:as well. --
2349:{{cite book
2103:wrong place
2098:description
1950:distinguish
1364:Template:rp
1123:description
723:page range
191:template.
36:This is an
3962:|dead-url=
3908:|dead-url=
3792:|dead-url=
3627:Ad 5) Yes.
3402:|language=
3377:|language=
3182:|language=
3074:|language=
3070:|language=
3066:|language=
2246:{{citation
1972:Regarding
1909:makes for
1689:J. Johnson
1048:|bookmark=
1046:). If the
1036:|bookmark=
836:itself is
606:|pagespan=
401:WP:CITEVAR
289:RefToolbar
98:Archive 20
90:Archive 18
85:Archive 17
79:Archive 16
73:Archive 15
68:Archive 14
60:Archive 10
3964:ignored (
3910:ignored (
3794:ignored (
3648:help text
3617:reference
3519:suggest).
3462:uses the
3281:|chapter=
3277:|section=
3273:|chapter=
3265:|section=
3248:|section=
3240:|section=
3111:abstract)
3093:abstract)
2750:Jonesey95
2702:=
2648:Jonesey95
2586:1303.7403
2474:|bibcode=
2414:cite book
2374:cite book
2345:Wikitext
2242:Wikitext
2138:cite book
1978:reediting
1974:reediting
1703:cite book
1342:this edit
1127:following
913:inclusive
897:Of course
828:Because (
3942:cite web
3888:cite web
3772:cite web
3732:cite web
3560:Correct.
3507:Issues:
3467:cite web
3287:cite map
3158:and new
3116:abstract
3098:abstract
2599:contribs
2591:Headbomb
2555:contribs
2547:Headbomb
2505:contribs
2497:Headbomb
2401:Sandbox
2311:citation
2298:Sandbox
2271:citation
2190:citation
2087:cite xxx
2077:citation
1905:in with
1596:Kanguole
1323:contribs
1206:Kanguole
1078:Kanguole
502:contribs
494:Headbomb
475:Kanguole
440:contribs
432:Headbomb
258:Kanguole
228:|page=13
193:Kanguole
139:contribs
127:unsigned
3724:"Title"
3682:WP:ELNO
3460:article
2704:forces
2603:physics
2559:physics
2509:physics
2470:|arxiv=
2197:|pages=
2183:|pages=
2179:|pages=
2131:|pages=
2027:|pages=
1958:|pages=
1916:|pages=
1868:|pages=
1818:|pages=
1740:outside
1736:Peter's
1643:outside
1636:Peter's
1429:|pages=
1411:without
1172:|pages=
1168:|pages=
1156:|pages=
1101:|pages=
1056:|pages=
1040:|pages=
1032:|pages=
1017:|pages=
1005:|pages=
997:|pages=
993:|pages=
842:section
809:|pages=
702:|pages=
664:outside
653:|pages=
506:physics
463:|pages=
444:physics
262:|pages=
236:|title=
39:archive
3686:really
3211:either
2686:|type=
2492:|date=
2488:|year=
2479:|year=
2094:source
1954:|page=
1814:|page=
1802:|issn=
1695:per se
1647:inside
1471:rose64
1407:within
1387:either
1368:Naraht
1350:rose64
1313:Naraht
1295:source
1286:range.
1271:within
1256:rose64
1238:It is
1152:|page=
1105:solely
1097:|page=
1052:|page=
1044:|page=
1028:|page=
1024:|page=
1013:|page=
1009:|page=
1001:|page=
989:|page=
905:|p/pp=
901:should
867:rose64
860:actual
834:source
801:|page=
774:source
698:|page=
630:Well,
574:source
545:within
457:Using
368:Jc3s5h
243:rose64
131:Naraht
3484:|url=
3458:This
2607:books
2582:arXiv
2563:books
2513:books
2406:Title
2366:Title
2361:Live
2303:Title
2263:Title
2258:Live
2072:(via
2029:gets
1806:|doi=
1708:with
1424:p. 13
602:|url=
510:books
448:books
16:<
4000:talk
3970:help
3954:help
3916:help
3900:help
3861:talk
3815:talk
3800:help
3784:help
3744:help
3700:talk
3689:all.
3654:flag
3638:talk
3586:talk
3543:talk
3438:talk
3410:talk
3392:talk
3367:talk
3351:talk
3330:talk
3300:talk
3267:and
3256:talk
3252:Izno
3242:and
3230:talk
3226:Izno
3193:talk
3168:talk
3164:Izno
3162:? --
3147:talk
3056:talk
3040:talk
2981:talk
2970:here
2961:here
2950:talk
2911:talk
2878:talk
2874:Izno
2863:talk
2825:talk
2821:Izno
2778:talk
2764:talk
2760:Izno
2752:and
2739:talk
2676:talk
2672:Izno
2652:talk
2636:talk
2632:Izno
2595:talk
2551:talk
2532:talk
2501:talk
2472:and
2448:talk
2433:link
2426:help
2393:link
2386:help
2330:link
2323:help
2290:link
2283:help
2205:talk
2149:talk
2119:For
2111:talk
2031:only
1997:talk
1966:does
1944:and
1924:talk
1879:Harv
1847:talk
1833:talk
1786:talk
1757:talk
1722:talk
1712:and
1677:talk
1666:Harv
1553:talk
1510:talk
1475:talk
1457:talk
1437:talk
1372:talk
1354:talk
1317:talk
1303:talk
1260:talk
1245:does
1219:talk
1195:talk
1160:|at=
1135:talk
1099:and
1067:talk
1042:(or
1030:and
991:and
976:talk
899:you
871:talk
850:talk
820:talk
805:|pp=
787:talk
764:talk
741:talk
713:talk
700:and
694:|pp=
692:and
681:talk
658:The
646:Harv
636:|pp=
634:and
622:talk
614:|pp=
612:and
587:talk
553:talk
535:talk
498:talk
436:talk
409:talk
372:talk
342:talk
325:talk
310:talk
270:talk
247:talk
226:and
218:Use
210:talk
206:Izno
182:talk
164:And
156:talk
152:Izno
135:talk
3621:not
3609:any
3605:-->
2490:or
2082:or
2021:or
1986:now
1651:not
1628:not
1469:Red
1422:},
1348:Red
1275:not
1254:Red
1103:is
1054:or
865:Red
838:not
797:|p=
690:|p=
632:|p=
610:|p=
473:.
394:sfn
241:Red
4002:)
3958:;
3946::
3944:}}
3940:{{
3904:;
3892::
3890:}}
3886:{{
3863:)
3855:--
3817:)
3788:;
3776::
3774:}}
3770:{{
3736::
3734:}}
3730:{{
3702:)
3640:)
3632:--
3588:)
3545:)
3470:}}
3464:{{
3440:)
3432:.
3412:)
3394:)
3369:)
3353:)
3332:)
3324:--
3302:)
3289:}}
3285:{{
3258:)
3232:)
3220:a
3218:or
3213:a
3195:)
3170:)
3149:)
3058:)
3042:)
2983:)
2952:)
2913:)
2880:)
2872:--
2865:)
2827:)
2780:)
2766:)
2741:)
2678:)
2668:}}
2662:{{
2654:)
2638:)
2605:/
2601:/
2597:/
2561:/
2557:/
2553:/
2534:)
2511:/
2507:/
2503:/
2450:)
2418::
2416:}}
2412:{{
2378::
2376:}}
2372:{{
2315::
2313:}}
2309:{{
2275::
2273:}}
2269:{{
2207:)
2193:}}
2187:{{
2151:)
2141:}}
2135:{{
2127:}}
2121:{{
2113:)
2090:}}
2084:{{
2080:}}
2074:{{
1999:)
1991:--
1926:)
1882:}}
1876:{{
1849:)
1835:)
1827:--
1808:,
1804:,
1788:)
1759:)
1724:)
1706:}}
1700:{{
1679:)
1669:}}
1663:{{
1555:)
1512:)
1477:)
1459:)
1439:)
1403:of
1391:or
1374:)
1356:)
1305:)
1262:)
1221:)
1197:)
1158:,
1154:,
1137:)
1069:)
1061:--
978:)
873:)
852:)
822:)
789:)
766:)
755:).
743:)
732:in
725:of
715:)
683:)
671:}}
649:}}
643:{{
639:do
624:)
589:)
555:)
537:)
527:}}
524:rp
521:{{
508:/
504:/
500:/
489:}}
486:rp
483:{{
471:}}
469:rp
467:{{
446:/
442:/
438:/
425:.
411:)
397:}}
391:{{
374:)
344:)
327:)
312:)
272:)
249:)
232:is
224:}}
220:{{
212:)
184:)
170:}}
166:{{
158:)
141:)
137:•
94:→
64:←
3998:(
3994:—
3972:)
3956:)
3936:.
3918:)
3902:)
3882:.
3859:(
3813:(
3809:—
3802:)
3786:)
3766:.
3746:)
3726:.
3698:(
3694:—
3636:(
3584:(
3580:—
3541:(
3436:(
3408:(
3390:(
3386:—
3383:.
3365:(
3349:(
3345:—
3342:.
3328:(
3298:(
3294:—
3291:.
3254:(
3228:(
3191:(
3166:(
3145:(
3141:—
3121:)
3054:(
3038:(
3034:—
2979:(
2975:—
2948:(
2909:(
2905:—
2876:(
2861:(
2857:—
2823:(
2776:(
2762:(
2756::
2748:@
2737:(
2733:—
2674:(
2665:=
2650:(
2634:(
2609:}
2593:{
2584::
2565:}
2549:{
2530:(
2526:—
2515:}
2499:{
2466::
2462:@
2446:(
2442:—
2435:)
2428:)
2395:)
2388:)
2332:)
2325:)
2292:)
2285:)
2203:(
2147:(
2109:(
1995:(
1956:/
1922:(
1845:(
1831:(
1816:/
1784:(
1778::
1774:@
1755:(
1720:(
1691::
1687:@
1675:(
1551:(
1508:(
1473:(
1455:(
1435:(
1381:"
1370:(
1366:.
1352:(
1320:·
1315:(
1301:(
1258:(
1217:(
1193:(
1189:—
1133:(
1065:(
974:(
961:"
952:"
869:(
848:(
818:(
814:—
811:.
785:(
762:(
758:—
739:(
711:(
707:—
704:.
679:(
620:(
585:(
551:(
533:(
512:}
496:{
450:}
434:{
427:6
407:(
386::
382:@
370:(
340:(
336:—
323:(
308:(
304:—
268:(
245:(
208:(
180:(
176:—
154:(
133:(
50:.
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.