This is an archive of past discussions. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page. |
Archive 35 | ← | Archive 40 | Archive 41 | Archive 42 | Archive 43 | Archive 44 | Archive 45 |
[Note: this was previously part of "Demarcation of cite interview", but I (E to the Pi times i) split it into its own section.]
Looking at
Izno's example usage more closely, I have a question. If other citation templates can utilize |interviewer-last=
and |interviewer-first=
, why do we need {{cite interview}}?
E to the Pi times i (
talk |
contribs) 15:50, 17 March 2018 (UTC)
{{
cite press release}}
?|type=Interview
. Another way to accomplish this is implementing the CS1 module to add (Interview) after any citations which use |interviewer-last=
and |interviewer-first=
. In the interrim of implementation, interviews could use |type=
.|type=
, |interviewer-last=
, |interviewer-first=
), then I see no reason to use {{cite interview}} when it doesn't (and probably shouldn't have to try to) accomodate the formatting all types of publication the interview may be published in.{{
cite press release}}
into {{
cite news}}
and then required editors to know to set |type=Press release
. A handful of the cs1 templates automatically set |type=
: {{
cite AV media}}
, {{cite interview}}
, {{
cite mailing list}}
, {{
cite map}}
, {{
cite podcast}}
, {{
cite press release}}
, {{
cite report}}
, {{
cite techreport}}
, and {{
cite thesis}}
.{{cite interview}}
could use a tweak. It doesn't handle pagination correctly if written as a journal cite; renders the same as magazine, news, and generic 'work' cites:
Wikitext | {{cite interview
|
---|---|
Live | "Title". Journal (Interview). 1 (4): 7. |
Sandbox | "Title". Journal (Interview). 1 (4): 7. |
{{cite whatever}}
to make them 'smart enough' to do the 'right thing' in the presence of |interviewer=
. I was musing about an entire redesign of cs1 and, though I didn't write about it, thinking about how such changes might effect downstream tools and other users.{{
cite interview}}
will need continuous tweaks?{{cite interview}}
but not by much (and we should probably continue to support it because en.wiki isn't the only wiki to use the cs1 module suite).There's no reason why errors shouldn't be flagged and tracked in draft space. It's time to enable this. Headbomb { t · c · p · b} 16:27, 24 February 2018 (UTC)
@ this talk page's article, My bad. unintentional, this may be how I learn to revert (vandalism or good faith), I'm all ears Deermouse ( talk) 22:32, 25 March 2018 (UTC)
This cite template gives an "ASIN uses ISBN" error:
"General Hospital: Luke & Laura (Lovers on the Run) Vol. 1". Burbank, California: ABC Studios. February 2, 1994. ASIN 6303007759. Retrieved September 27, 2016.
Is this ASIN really an ISBN? It passes the checksum test, but I am unable to find any verification that it is really an ISBN. Here's another one:
"Clay Pigeon".
PolyGram Filmed Entertainment.
Universal City, California:
Universal Studios. April 27, 1999.
ISBN
6305353212. Retrieved November 21, 2016. {{
cite web}}
: Check |isbn=
value: invalid group id (
help)
"Clay Pigeon". PolyGram Filmed Entertainment. Universal City, California: Universal Studios. April 27, 1999. ASIN 6305353212. Retrieved November 21, 2016.
When I click to follow the ISBN link, I get nothing but dead ends, even using the Amazon link at Special:BookSources. When I follow the ASIN link for the same number, I get an Amazon page.
Wikipedia:WikiProject Check Wikipedia/ISBN errors shows these "ISBN" values starting with 63 as errors. I don't know what CheckWiki's methodology is.
List of ISBN identifier groups does not show a country for 10-digit ISBNs starting with 63. Neither does the International ISBN Agency. – Jonesey95 ( talk) 14:34, 27 March 2018 (UTC)
|asin=63...
is not an isbn then perhaps we might tweak the module code to exclude such asin numbers from the category.i note recent conflict on reference using cite web in film article.
reference about aggregator website, example rotten tomatoes, metacritic, box office mojo. name of website usually go in work=, website=.
but some user do not like italic that work=, website=, put on name. they do following:
does italic matter? does work=, publisher= difference matter?
discussion previous at Wikipedia talk:WikiProject Film#i comment about reference format. IUpdateRottenTomatoes ( talk) 18:03, 27 March 2018 (UTC)
In the past I used the dead-url parameter (I think) to indicate that the URL for the citation no longer worked, and someone needed to look at it, i.e. find an archived version or a new version of the page. However, from reading the documentation and using it again now, it looks like this is no longer the intended usage of dead-url. It doesn't show up anywhere, there is no hidden category, etc. What is the correct usage of dead-url and what parameter can I use to indicate dead links? Or should it be in a separate {{ dead link}} template? — Ynhockey ( Talk) 12:33, 17 February 2018 (UTC)
|dead-url=
nor has that functionality ever been implemented. The parameter is ignored except when the cs1|2 template uses both |archive-url=
and |archive-date=
. There is no cs1|2-specific parameter to indicate that a url is dead so the {{
dead link}}
template should be used to do that (outside of the cs1|2 template).|dead-url=
is intended to be used in conjunction with archived urls, the name should have reflected that to avoid obvious confusion by users.
Jason Quinn (
talk) 13:58, 17 February 2018 (UTC)
|<name>-url=
parameters take urls as their assigned values. I have never gotten sufficient traction to deprecate |dead-url=
and replace it with with something more appropriate. This morning I was thinking that |use-archive=
url-state
/url-status
before. (Russian Wikipedia allows HTTP codes in the field as well, which might be an interesting addition here, especially for IABot.) --
Izno (
talk) 15:33, 17 February 2018 (UTC)
|archive-state=
(or |archive-status=
or |archive-display=
) so that the three |archive-*=
arguments are easier to remember and kept together as a set. It's also more clear referring to the state of the archive, and not the url, which is the main source of confusion. Should the archive come first or second in display is the underlying question. --
Green
C 19:46, 17 February 2018 (UTC)
|archive-display=
among the three. In each case the association is much clearer. The problem with |dead-url=
is that it looks self-explanatory (seeming to answer the question "does the url work?") but it is not.
Jason Quinn (
talk) 02:26, 18 February 2018 (UTC)state of the archivebut rather it's the state of the url which can be: live, dead, unfit, usurped, or unknown. This suggests that the parameter name must refer to the url somehow so parameter names like
|url-state=
or |url-status=
(credit an IP editor for those names, not me) should be preferred over an |archive-*=
name.|dead-url=
accepts yes
, true
, y
, no
, unfit
, usurped
, bot: unknown
. If we shift to use |url-state=
, then the accepted parameter values become: dead
, live
(the default), unfit
, usurped
, bot: unknown
.|url-state=dead
as being more clear than |dead-url=yes
in terms of clearing up the confusion what the argument is meant for. --
Green
C 19:56, 18 February 2018 (UTC)
|url-is=
(dead
, live
, ...) Got anything better?|archive-disp=url-unfit
, |archive-disp=url-dead
, |archive-disp=url-live
etc.. or drop the "url" part altogether. What the option-switches do is described in the docs, but the argument name makes it clear it is mainly being used for archive display, what most people use it for. --
Green
C 17:03, 19 February 2018 (UTC)|deadurl=
gets added - my bot WaybackMedic removes strays, and Cyberpower678's IABot marks links dead regardless. --
Green
C 19:55, 17 February 2018 (UTC)
|dead-url=
would be deprecated when the new parameter is implemented, and the two would operate in parallel (but not simultaneously) through the transition period – which could be quite long. A bot task could be developed to convert existing |dead-url=
to the new parameter (iabot and wayback medic might implement that as well). At some point in the future when the count of articles using |dead-url=
drops below an acceptable number, support for it is removed. This is, more-or-less, how we handle all deprecated parameters (which all have had the possibility of breaking external tools).|dead-url=
with a missing or empty |archive-url=
. They could assume the url is dead act accordingly (add an archive) - probably a safe bet in most cases since how else would a stray |deadurl=
with a "yes" value get added unless a human thought the URL was dead. --
Green
C 19:56, 18 February 2018 (UTC)
many other tools ...so it is the tool maintainers' responsibility to keep up with us and to join in these conversations to say why we should or should not do what we propose to do.
|dead-url=
) which I don't think is too common. I haven't been logging this, but just added logs so the next time it runs it will record how common it is within a set of articles (probably 100k to 200k articles will get processed). Granted, bot maintenance is not ideal as long-term is not guaranteed. --
Green
C 17:03, 19 February 2018 (UTC)@
Trappist the monk and
GreenC: Another possible parameter which I don't see suggested above is Edit: I did not realize there were more than two parameters, otherwise I would not have suggested that. I am curious why those parameters were added, so I may go back and look at prior discussions.
E to the Pi times i (
talk |
contribs) 22:20, 27 March 2018 (UTC)
|use-archive=
(or |use-archive-url=
, but I prefer the former). This would explicitely state what the parameter does, and because of the "use" verb, there is little opportunity for confusion (though if you see possible confusion, please tell me). This parameter could take true and false like |dead-url=
currently does.
E to the Pi times i (
talk |
contribs) 19:17, 19 March 2018 (UTC)
|url=
. The parameter isn't a boolean so the parameter name and all of its acceptable values 'should' read somewhat sensibly. I don't think that |use-archive=unfit
is any better than |dead-url=unfit
and neither (I think) are as good as |url-state=unfit
(which would require new values dead
and live
in place of yes
and no
). Alas, |use-archive=yes
conveys nothing about the 'why' we should be using the archive.I too am (a little) confused about |dead-url=
. Looks like it was originally intended as a "yes"/"no" parameter to link the title to the original or archived URL (with the other being available). The values "usurped" and "unfit" were added to cover situations were the URL was still "live" but either was "usurped" by another unrelated site or a site "unfit" for viewing (and therefore no reason to view original site). I have encounter many sites that redirect an "unknown" page to another (usually "home") page on the site. A similar situation occurs when the referenced page contents change (e.g. "Home"). In both of these cases, I attempt to find an appropriate archive page and use |dead-url=yes
to link the title to the archived page. I do not think this is the correct usage of this parameter. I do think the parameter should be renamed and appropriate values defined. I have a slight preference for |url-state=
with values like: valid
, dead
, redirected
, volatile
, usurped
, and unfit
. usurped
and unfit
would be two were the original link would need to be supressed.—
User-duck (
talk) 22:06, 27 March 2018 (UTC)
P.S. Remember, there can be more than one URL specified in some citation templates (e.g. {{ cite book}})— User-duck ( talk) 22:06, 27 March 2018 (UTC)
{{
cite book}} has |url=
and |chapter-url=
parameters to link the specified URL with the appropriate field in the citation. Some archive websites provide access to the entire book and a URL for the entire book can be included. I assume the same is true for chapters as well. They may also provide access to a specific page. Google Books URLs often link to specific pages or portions of pages but seldom entire books. Editors have used |url=
or |chapter-url=
the for these URLs. I feel this is an incorrect usage of the parameter(s). I believe a |page-url=
parameter would be useful for linking a specified page with a page URL. I have used several methods to work-around the issue, but they are work-arounds.—
User-duck (
talk) 23:00, 27 March 2018 (UTC)
I've used "cite book" with "|isbn=1234567". Is there a way to make an automated bot built into wikipedia do research based on the quoted isbn number to fill in the author and publisher information? Thanks. Adrian816 ( talk) 21:27, 28 March 2018 (UTC)
For book having isbn 978-0-85412-822-8, copyright of the Handbook of Doctrine published by the Salvation Army is held "in trust" by a specific employee of the organisation, the General. While wikipedia allows a number of types of information to be included like publisher, there's no tag for " |copyright=The General of The Salvation Army".
On the relevant page of the book is: c 2010 The General of The Salvation Army This edition published 2010
therefore full citation of this book needs to include the copyright holder and printing company name for wikipedia to have full information.
There's also "Printed by" information for this book, in this case "UK Territory Print & Design Unit".
Please can someone look into getting wikipedia software updated to include these tags: |copyright= |printed-by=
Thanks Adrian816 ( talk) 22:29, 28 March 2018 (UTC)
|copyright=
and |printed-by=
negligibly add to the ability to verify sources.
E to the Pi times i (
talk |
contribs) 23:17, 28 March 2018 (UTC)
lang
shortcut to {{
Cite web}}{{{lang}}}
should be a shortcut for {{{language}}}
as it would be much easier and when I write "language" I usually shorten it to "lang" anyway. –
Nixinova ⟨
T |
E ⟩ 04:07, 31 March 2018 (UTC)
|language=
does have the alias |in=
which to me, is poorly chosen. I used to see it quite a lot in
Category:CS1 maint: Unrecognized language when editors meant that a source was |in=
some other larger work. I would be fine with deprecating |in=
and then, if a shorter version of |language=
is really needed, adding |lang=
.|in=
as well as adding a |lang=
as a synonym for |language=
. --
Izno (
talk) 14:03, 31 March 2018 (UTC)
|in=
in {{
cite web}}, and they were all being used incorrectly. Let's deprecate that one. –
Jonesey95 (
talk) 14:23, 31 March 2018 (UTC)
|in=
and adding a |lang=
. --
Emir of Wikipedia (
talk) 14:40, 31 March 2018 (UTC)|in=
is confusing since it make it look like it refers to the "in Smith, J. (ed) Title part of an editor work. If |lang=
us accepted as an alias (which I'm fine with), it should cover all templates, not just {{
cite web}}.
Headbomb {
t ·
c ·
p ·
b} 18:50, 31 March 2018 (UTC)|in=
. I'm mildly against adding |lang=
, though; it's unambiguous enough but I think there is enough unnecessary variation in parameter names already. —
David Eppstein (
talk) 19:35, 31 March 2018 (UTC)lang
was deliberately avoided? Commons and Wikidata, as the two WMF multilingual projects, support several schemes for display of multilingual content. For templates it is commons to use the Autotranslate mechanism and template, which uses the lang
parameter. On Commons and Wikidata templates avoid assigning their own use to a lang
parameter to avoid incompatibility with Autotranslate. Probably not a direct concern for CS1 on en.WP, and I don't think either Commons or Wikidata currently make use of CS1, but something to consider. —
RP88 (
talk) 19:38, 31 March 2018 (UTC)
|lang=
or |language=
too? If it is just the former then it is something to consider, but if it is both then if it was really a big issue it would have been brought up anyway.
Emir of Wikipedia (
talk) 19:40, 31 March 2018 (UTC)
The citation
appears as
{{
cite journal}}
: Check |zbl=
value (
help)with an error message "Check |zbl= value (help)". I have checked the zbl= value, and it is correct. Please correct this so that the reference can be formatted with its correct zbl id. — David Eppstein ( talk) 07:15, 3 April 2018 (UTC)
|zbl=
,
Zbl
06684722, that the citation template again does not like. Where is the source for the information that this parameter must be of the form "nnnn.nnnnn"? Because apparently this is incorrect. —
David Eppstein (
talk) 07:23, 3 April 2018 (UTC)Not a Zbl; that identifier is a JFM:
— Trappist the monk ( talk) 10:31, 3 April 2018 (UTC)
This help request has been answered. If you need more help, you can , contact the responding user(s) directly on their user talk page, or consider visiting the Teahouse. |
but the help page cite tweet doesn't have the infobox on the template. Can the infobox listing the different variations of cite... be added to the cite tweet page please. The infobox looks like a global template, but it lacks cite tweet Please fix the cite tweet help page, and amend the infobox on this help page to include cite tweet thanks Adrian816 ( talk) 23:01, 3 April 2018 (UTC)
{{
cite tweet}}
is not a cs1 template because it does not directly use either of
Module:Citation/CS1 or {{
citation/core}}
. For that reason, {{cite tweet}}
is a meta template and meta templates do not belong in the cs1 'infobox'.Hi all. As you probably noticed recently, the WMF released a dataset on the works cited on En-Wiki that included a few select identifiers (particularly ISBNs, WorldCat IDs and DOIs): https://blog.wikimedia.org/2018/04/05/ten-most-cited-sources-wikipedia/ . One of the challenges with this dataset: is that it only works, when their are identifiers including in citations. Could we create a tracking category, which helps identify citations from the Journal/Book citations that don't include any identifier? This could help empower community members to help better populate those citation data, so that future analysis could include more of our citations? Secondly to make this a manageable backlog: could we create a variable for citations in those sets for "no identifier available" -- which could allow folks to review the citation, and then confirm that it in fact can not be tied to an identifier (and put those items in another tracking category?) Generally Books and Journals should be things with some type of identifier, otherwise the templates are probably be used for the wrong thing (i.e. published reports or magazines, which should be cited using one of the more specific templates). Thanks much, Sadads ( talk) 14:47, 14 April 2018 (UTC)
I am working with an editor at bn.wiki to implement the cs1|2 module suite there; discussion on my talk page.
I have moved the definitions of the various separator and postscript characters out of Module:Citation/CS1/sandbox into the presentation table in Module:Citation/CS1/Configuration/sandbox.
Because Bengali does not use western style digits, and also because Lua does not understand non-western digits, a couple of tweaks were necessary to support enumerated parameter names written wholly in Bengali.
These changes should be transparent to the en.wiki module suite:
Wikitext | {{cite book
|
---|---|
Live | Brown, Red; Orange, Yellow; Green, Blue. Title. |
Sandbox | Brown, Red; Orange, Yellow; Green, Blue. Title. |
Wikitext | {{citation
|
---|---|
Live | Brown, Red; Orange, Yellow; Green, Blue, Title |
Sandbox | Brown, Red; Orange, Yellow; Green, Blue, Title |
Wikitext | {{cite book
|
---|---|
Live | Brown R, Orange Y, Green B. Title. |
Sandbox | Brown R, Orange Y, Green B. Title. |
Wikitext | {{citation
|
---|---|
Live | Brown R, Orange Y, Green B, Title |
Sandbox | Brown R, Orange Y, Green B, Title |
— Trappist the monk ( talk) 12:34, 14 April 2018 (UTC)
|publication-date=
and |year=
, both of which, when used alone in a cs1|2 template are promoted to |date=
, are returning incomplete error messages:
quietly converting hyphens to dashes. See this discussion.
|date=২০১৮-০৫-০৭
string.match()
function looking to match the pattern '%d%d%d%d%-%d%d%-%d%d'
which worked fine as long as the digits were western (0–9) single-byte digits (because the Lua string library operates on bytes). But, Bengali digits are three bytes each. Here is the percent encoded version of the example date:
%E0%A7%A8%E0%A7%A6%E0%A7%A7%E0%A7%AE-%E0%A7%A6%E0%A7%AB-%E0%A7%A6%E0%A7%AD
২০১৮-০৫-০৭
as a ymd date so it silently converted the hyphens to endashes giving this result:
string.match()
to mw.ustring.match()
which operates on Unicode characters, so that ymd format dates are recognized and skipped when the module does the hyphen conversion.Something I noticed re translators and periods, as a heads up:
{{cite journal|last=Author|first=A.
|translator-last=Translator|translator-first=T.
|title=Title|journal=Journal|date=2018|volume=1|page=100}}
Author, A. (2018). "Title". Journal. 1. Translated by Translator, T.: 100.{{ cite journal}}
:|last=
has generic name ( help)
{{cite journal|author=Aut.–A.C.R.O.N.Y.M.
|translator=Transl.–A.C.R.O.N.Y.M.
|title=Title|journal=Journal|date=2018|volume=1|page=100}}
Aut.–A.C.R.O.N.Y.M. (2018). "Title". Journal. 1. Translated by Transl.–A.C.R.O.N.Y.M.: 100.
The "extra" full stop gets removed if |first=
or |author=
ends with a period but the same fix hasn't been yet been applied to |translator-first=
or |translator=
.
I'm also not sure off the top of my head of a real source that might need to be cited as such (but it's within the realm of possibility), but I also just now discovered if there is no listed author, but is a listed translator, there is an errant period at the beginning:
{{cite journal
|translator-last=Translator|translator-first=T.
|title=Title|journal=Journal|date=2018|volume=1|page=100}}
"Title". Journal. 1. Translated by Translator, T.: 100 2018.{{ cite journal}}
:|translator-last=
has generic name ( help)
Thanks, hopefully this is of use :) Umimmak ( talk) 10:33, 25 April 2018 (UTC)
|others=
and |interviewer=
and only for {{
cite journal}}
and {{
citation}}
when a 'work' parameter is set (though for this case, it isn't an issue for {{citation}}
because the element separator is a comma). Fixed, I think in the sandbox:Wikitext | {{cite journal
|
---|---|
Live | Author, A. "Title". Journal. Others O. {{
cite journal}} : |last= has generic name (
help)
|
Sandbox | Author, A. "Title". Journal. Others O. {{
cite journal}} : |last= has generic name (
help)
|
Wikitext | {{cite journal
|
---|---|
Live | Author, A. "Title". Journal. Interviewed by Interviewer I. {{
cite journal}} : |last= has generic name (
help)
|
Sandbox | Author, A. "Title". Journal. Interviewed by Interviewer I. {{
cite journal}} : |last= has generic name (
help)
|
Wikitext | {{cite journal
|
---|---|
Live | Author, A. "Title". Journal. Interviewed by Interviewer I. Others O. {{
cite journal}} : |last= has generic name (
help)
|
Sandbox | Author, A. "Title". Journal. Interviewed by Interviewer I. Others O. {{
cite journal}} : |last= has generic name (
help)
|
Wikitext | {{cite journal
|
---|---|
Live | Author, A. "Title". Journal. Translated by Translator T. {{
cite journal}} : |last= has generic name (
help)
|
Sandbox | Author, A. "Title". Journal. Translated by Translator T. {{
cite journal}} : |last= has generic name (
help)
|
Wikitext | {{cite journal
|
---|---|
Live | Author, A. "Title". Journal. Translated by Translator T. Others O. {{
cite journal}} : |last= has generic name (
help)
|
Sandbox | Author, A. "Title". Journal. Translated by Translator T. Others O. {{
cite journal}} : |last= has generic name (
help)
|
Wikitext | {{cite journal
|
---|---|
Live | Author, A. "Title". Journal. Interviewed by Interviewer I. Translated by Translator T. {{
cite journal}} : |last= has generic name (
help)
|
Sandbox | Author, A. "Title". Journal. Interviewed by Interviewer I. Translated by Translator T. {{
cite journal}} : |last= has generic name (
help)
|
Wikitext | {{cite journal
|
---|---|
Live | Author, A. "Title". Journal. Interviewed by Interviewer I. Translated by Translator T. Others O. {{
cite journal}} : |last= has generic name (
help)
|
Sandbox | Author, A. "Title". Journal. Interviewed by Interviewer I. Translated by Translator T. Others O. {{
cite journal}} : |last= has generic name (
help)
|
Wikitext | {{cite journal
|
---|---|
Live | Author, A. "Title". Journal. Interviewed by Interviewer I. Translated by Translator T. Others O. {{
cite journal}} : |last= has generic name (
help)
|
Sandbox | Author, A. "Title". Journal. Interviewed by Interviewer I. Translated by Translator T. Others O. {{
cite journal}} : |last= has generic name (
help)
|
safe_join()
uses a series of Lua pattern matching string functions to do its work. The Lua string library works well at en.wiki becase our terminal characters are all single byte characters. At bn.wiki, the terminal character is the dari ('।', Unicode U+0964 Devanagari Danda) which is a three-byte character. For safe_join()
to properly recognize that character requires that we use the Ustring library function which are significantly slower than their equivalent String library function. So that en.wiki doesn't take a performance hit and to make the code compatible with bn.wiki and others that use multi-byte terminal characters, safe_join()
now inspects the terminal character and chooses the appropriate library functions before it does its work.safe_join()
is no longer required...|chapter=
has these aliases: |contribution=
, |entry=
, |article=
, and |section=
.
Associated with |chapter=
are: |chapter-format=
, |chapter-url=
, and |chapter-url-access=
. We should have similar parameters for all of the |chapter=
aliases but don't.
I have added these to Module:Citation/CS1/Configuration/sandbox:
|entry-format=
, |article-format=
|entry-url=
, |article-url=
|contribution-url-access=
, |entry-url-access=
, |article-url-access=
, |section-url-access=
— Trappist the monk ( talk) 11:47, 24 May 2018 (UTC)
An editor from Australia brought up an interesting point in
this discussion that the |archivedate=
can actually pre-date the publication of the underlying source due to time zone shifts. For example a news report published noon Monday in Australia might have an |archivedate=
of Sunday, which is nonsensical (archive.org is located in San Francisco and probably uses GMT). So the editor has been entering the day they created the archive relative to their location in Australia, which then gets changed by bots trying to keep the snapshot date in sync with the |archivedate=
(
example). The source of the confusion appears to be the CS1 documentation which ambiguously says "Date when the original URL was archived" .. is the date relative to the archive service provider or the archiving user location?
As I see it, there's no reason to record when the editor created the archive (information more often than not unknown since the archive was created by someone else); the reader only needs to know the webarchive service date so they know how to retrieve it, the only purpose of having a |archivedate=
. As such, would it make sense to change the documentation to reflect that dates are relative to the service provider date. --
Green
C 15:25, 19 April 2018 (UTC)
|archive-url=
to include the word 'snapshot':
I added this. Took the opportunity to additionally add "templated dates are discouraged" since it is also documented elsewhere due to COIN data. -- Green C 02:53, 21 April 2018 (UTC)
|archive-url=
documentation?Since this module is being continuously copied and overwritten to wikidata, I guess this is the place to report errors of that copy as well. On Wikidata the id_handlers cannot provide a valid sitelink by the code:
text = external_link_id({link = handler.link, label = handler.label, prefix=handler.prefix,id=id,separator=handler.separator, encode=handler.encode, access=access}) .. (inactive or '')
"handler.link" just doesn't work on Wikidata. The QID should be also provided in Module:Citation/CS1/Configuration, and link is compiled as something like "d:QID". Of course a site server checking would also be needed to be able to decide which link configuration to use:
_linkconfig = string.match(mw.site.server, "wikidata") or "sitelink"
-- Pzgulyas ( talk) 15:14, 20 March 2018 (UTC)
Continuously copied and overwritten to wikidate? (emphasis mine) What do you mean by that?
"handler.link" just doesn't work on Wikidata?
I added a real-life example to d:Wikidata:Sandbox, please see the red links. Please also try changing the display language to something different than English, which highlights another malfunction: The property P577 (publication date) should be queried in language-independent manner in Cite Q template, the simpler {{#property:P577|from={{{1}}}}} doesn't work in Wikidata well.-- Pzgulyas ( talk) 11:46, 21 March 2018 (UTC)
continuously copied...question.
{{
cite Q}}
should be directed to
Template talk:cite Q. That template fetches data from wikidata and then hands it off to {{
citation}}
for rendering. {{citation}}
,
Module:Citation/CS1, and associated modules do not use wikidata for anything.@ Trappist the monk:: Don't feel be opposed, I'm trying to answer your questions one-by-one:
continuously copied...: I mean, it was copied in the past, and any changes on wikidata will be overwritten from enwiki in the future.
The red links occur because...: I know the reason why they occur, but the fix should be done in this software. E.g. the link that points here to Digital object identifier on wikidata should point to d:Q25670. Currently the Q number is not available in the Module:Citation/CS1/Configuration, and should be added.
This is the expected behavior, isn't it?...: No, the expected behavior is that they point to the correspondig wikidata Q object.
Dates are problematic. (...) editors there must modify the code as necessary to support their local date formats...: Here the case is different. There is no need to support local date formats, only when reading the date property, it must be ensured that the data is passed in a way that the rest of the code understands. Querying the property with #property:P577 is not appropriate, this must be replaced by a piece of lua code.
Questions and comments concerning (...) should be directed to...: You are right about
{{
cite Q}}
, but the problem is caused by the codes in
Module:Citation/CS1/Configuration and
Module:Citation/CS1/Identifiers, both of which talk pages are redirected here, I guess for the sake of keeping the discussion in a centralized place.-- Pzgulyas ( talk) 13:41, 21 March 2018 (UTC)
[[Digital object identifier|doi]]
[[d:Q25670|doi]]
this_wiki_code = mw.language.getContentLanguage():getCode()
article = mw.wikibase.getEntity ('Q25670'):getSitelink (this_wiki_code .. 'wiki')
link = '[[' .. this_wiki_code .. ':' .. article .. ']]'
this_wiki_code
to 'es'article
to 'Identificador de objeto digital'link = '[[' .. 'es' .. ':' .. 'Identificador de objeto digital' .. ']]'
→ [[es:Identificador de objeto digital]]
→
es:Identificador de objeto digitalthis_wiki_code = mw.language.getContentLanguage():getCode()
for me, sets this_wiki_code
to 'en' regardless of user preferences language setting.{{cite journal/new |title=A Higher Level Classification of All Living Organisms |doi=10.1371/JOURNAL.PONE.0119248 |pmc=4418965 |pmid=25923521}}
{{
cite journal}}
: Cite journal requires |journal=
(
help)CS1 maint: unflagged free DOI (
link)
'"`UNIQ--templatestyles-000000A9-QINU`"'<cite class="citation journal cs1">[https://www.ncbi.nlm.nih.gov/pmc/articles/PMC4418965 "A Higher Level Classification of All Living Organisms"]. [[doi (identifier)|doi]]:[https://doi.org/10.1371%2FJOURNAL.PONE.0119248 10.1371/JOURNAL.PONE.0119248]. [[PMC (identifier)|PMC]] <span class="id-lock-free" title="Freely accessible">[https://www.ncbi.nlm.nih.gov/pmc/articles/PMC4418965 4418965]</span>. [[PMID (identifier)|PMID]] [https://pubmed.ncbi.nlm.nih.gov/25923521 25923521].</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=article&rft.atitle=A+Higher+Level+Classification+of+All+Living+Organisms&rft_id=https%3A%2F%2Fwww.ncbi.nlm.nih.gov%2Fpmc%2Farticles%2FPMC4418965%23id-name%3DPMC&rft_id=info%3Apmid%2F25923521&rft_id=info%3Adoi%2F10.1371%2FJOURNAL.PONE.0119248&rft_id=https%3A%2F%2Fwww.ncbi.nlm.nih.gov%2Fpmc%2Farticles%2FPMC4418965&rfr_id=info%3Asid%2Fen.wikipedia.org%3AHelp+talk%3ACitation+Style+1%2FArchive+42" class="Z3988"></span> <span class="cs1-visible-error citation-comment"><code class="cs1-code">{{[[Template:cite journal|cite journal]]}}</code>: </span><span class="cs1-visible-error citation-comment">Cite journal requires <code class="cs1-code">|journal=</code> ([[Help:CS1 errors#missing_periodical|help]])</span><span class="cs1-maint citation-comment">CS1 maint: unflagged free DOI ([[:Category:CS1 maint: unflagged free DOI|link]])</span>
If it is decided going this way, language code on wikidata can be queried by print(mw.getCurrentFrame():preprocess('{{int:lang}}'))
--
Pzgulyas (
talk) 09:02, 22 March 2018 (UTC)
{{int:lang}}
doesn't work at en.wiki; → ⧼lang⧽. The tone of your post suggests to me that you believe that the 'partial answer' that I described above is: wrong? flawed? misguided? something else? If that is your belief then what is the better way?I'm really sorry for my previous short answer, I like your solution. Just I wrote from work office, and suddenly some work appeared to be done, so I apologize. I think what you have done, is the right fix. I think for the language code querying method selection you may use some test like string.match(mw.site.server, "wikidata")
--
Pzgulyas (
talk) 10:11, 23 March 2018 (UTC)
I have hacked d:Template:Cite Q and d:Module:Citeq so that dates extracted from wikidata are always rendered dmy in English regardless of the user's interface language choice.
While doing that, I wondered if it was even necessary. What protections does wikidata provide? Are dates in wikidata validated and so guaranteed to be correct? If so, then much the cs1|2 date validation is not required for dates taken from wikidata. But, it's still problematic because editors can override |date=
in {{cite Q}}
; can still provide |access-date=
so these must be validated.
— Trappist the monk ( talk) 11:05, 24 March 2018 (UTC)
I think we should allow in press and forthcoming preprints to be cited on Wikipedia, at least if a public URL is available for WP:V. Currently, cite templates produce an error message if "In press" is used with the date parameter of these templates. I propose that
|date=
in citation templates. I think this involves changing function check_date in
Module:Citation/CS1/Date validation|date=
is "In press" or "Forthcoming", citation templates display an error message if access-date is empty, and show the access-date parameter even if no URL is given. This is a new use for |access-date=
, but I think it is better than creating a new parameter just for this purpose.I suggest that proposal 3 depends on proposal 2, and proposal 2 depends on proposal 1, but proposal 1 does not depend on 1 or 2. What do others think? Daask ( talk) 11:55, 23 April 2018 (UTC)
More and more, book chapters are published electronically and have their own doi. we already have parameter chapter-url; in my view it would be useful to have chapter-doi as well. Is that do-able? thanks. Jytdog ( talk) 18:10, 28 April 2018 (UTC)
|id={{
doi}}
to provide a second option. But I can't see a reason for systematically including the book DOI if the chapter DOI will easily lead the reader to the same place in a click or two.
Umimmak (
talk) 14:42, 29 April 2018 (UTC)There is a discussion at Template talk:Cite tweet#Non text tweets about citing tweets that contain links, images, etc. Please comment over there. wumbolo ^^^ 14:57, 29 April 2018 (UTC)
|issue=
informationI updated the documentation of the |issue=
parameter to account for cases like "#293, Vol. 24, No. 5" (i.e., two different kinds of issue numbering), by adding the instruction "When a total issue number and an issue within a volume are both given – e.g., "#293, Vol. 24, No. 5" – this can be coded as |volume=24
|issue=5 [total issue #293]
."
[1]; the documentation has for years already accounted for issue naming, with "When the issue has a special title of its own, this may be given, in italics, along with the issue number, e.g. |issue=2, ''Modern Canadian Literature''
." This was not only reverted, but the revert included removal of both of these instructions, with an edit summary that doesn't make much sense to me: "no; abusing |issue= is no substitute for abusing |page=; one piece of information per parameter"
[2]. Using |issue=
for issue information is not "abuse" of the parameter, it's what the parameter exists for. Nor is there any principle here of "one piece of information per parameter", or we'd have separate parameters for middle names of authors, separate parameters for countries of city locations, separate parameters for days and months in dates, separate parameters for subtitles, and so on.
The problem to solve is that people are randomly actually abusing completely unrelated parameters like |page=
and |publisher=
to try to shoe-horn complex issue information into the template, when it obviously belongs in |issue=
. But not obviously enough, or people wouldn't be doing that and we wouldn't need to have clearer documentation.
The only other alternative it to introduce yet more parameters for such things, and I think that's a terrible idea. So, I think this version should be restored. — SMcCandlish ☏ ¢ 😼 12:28, 5 February 2018 (UTC)
|volume=
when a cumulative issue number is supplied in |issue=
. For the issue-number-issue-title question, we have two fundamentally different pieces of information: the number is the basic descriptive unit typical of almost all periodicals and issue titles are generally rare special cases where the title merely supplements the issue number. Choose one, do not include wiki markup because the value assigned to |issue=
is made part of the metadata.|title=
and |chapter=
(and their aliases) because titles often mix upright and italic fonts for good reason (scientific names, for example).I think the simplest way to handle this would be to not consider |number=
and |issue=
aliases when they are both listed. Or at least you could have |number-issue=yes
to overide them being considered aliases. This way you could use
{{cite magazine|author=A. Uthor |year=2010 |title=Things and stuff |magazine=Magazine Weekly |volume=7 |issue=245 |number=5|pages=24–445 |number-issue=yes}}
to generateor
{{cite journal|author=A. Uthor |year=2010 |title=Things and stuff |journal=Magazine Weekly |volume=7 |issue=245 |number=5|pages=24–445 |number-issue=yes}}
to generateThis would solve a crapton of issues. Headbomb { t · c · p · b} 17:51, 21 March 2018 (UTC)
On the page Yang Jisheng (statesman), there is a possible issue with the citation for the article "Lǐ Dàzhāo de Zuòyòumíng", which possesses an original title that uses Chinese characters. This does not appear to be merely a problem with my computer or browser, as I have tried multiple examples of each. The template {{ Cite web}} was used for that particular citation. Between "Lǐ Dàzhāo de Zuòyòumíng" (title) and the same in Chinese characters (script-title) there appears to be a line break where there should not be one. Do other users observe the same issue? (Is this a problem in other articles?) Please advise if script-title is broken or if I am overlooking a simple solution. Simply removing the parameter script-title might solve the problem, but it is an issue if our citations are unable to display Chinese text. RexSueciae ( talk) 21:51, 29 April 2018 (UTC)
Reduce the citation to just a wikilink:
[http://cpc.people.com.cn/BIG5/64162/64172/85037/85038/7104292.html "Lǐ Dàzhāo de Zuòyòumíng" <bdi lang="zh" >李大釗的座右銘</bdi>
Place it directly at the left margin in show preview (for me) splits the wikilink at the <bdi>...</bdi>
tag:
"Lǐ Dàzhāo de Zuòyòumíng" 李大釗的座右銘
Indent with definition list markup (:
):
renders correctly.
Same experiments, but replace <bdi>...</bdi>
with <span>...</span>
:
"Lǐ Dàzhāo de Zuòyòumíng" 李大釗的座右銘
Indent with definition list markup (:
):
Both render correctly in show preview. Saving this page now to see what happens.
— Trappist the monk ( talk) 22:47, 29 April 2018 (UTC)
But ... but ... Argh. So I saved my edit above and both the <bdi>...</bdi>
and <span>...</span>
tests whether against the left margin or indented rendered correctly. As a further experiment, I null edited the page and got a different result: same as I get in show preview. It is interesting that in show preview, the Chinese characters in <bdi>...</bdi>
(indented) are not part of the wikilink when they should be.
I'm seeing this with the latest Chrome browser (only one on my machine).
I can only conclude that this is not a |script-title=
issue but appears to be a mediawiki issue with <bdi>...</bdi>
. Perhaps I'll think on this some more and then take it to
WP:VPT
— Trappist the monk ( talk) 23:01, 29 April 2018 (UTC)
This is an archive of past discussions. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page. |
Archive 35 | ← | Archive 40 | Archive 41 | Archive 42 | Archive 43 | Archive 44 | Archive 45 |
[Note: this was previously part of "Demarcation of cite interview", but I (E to the Pi times i) split it into its own section.]
Looking at
Izno's example usage more closely, I have a question. If other citation templates can utilize |interviewer-last=
and |interviewer-first=
, why do we need {{cite interview}}?
E to the Pi times i (
talk |
contribs) 15:50, 17 March 2018 (UTC)
{{
cite press release}}
?|type=Interview
. Another way to accomplish this is implementing the CS1 module to add (Interview) after any citations which use |interviewer-last=
and |interviewer-first=
. In the interrim of implementation, interviews could use |type=
.|type=
, |interviewer-last=
, |interviewer-first=
), then I see no reason to use {{cite interview}} when it doesn't (and probably shouldn't have to try to) accomodate the formatting all types of publication the interview may be published in.{{
cite press release}}
into {{
cite news}}
and then required editors to know to set |type=Press release
. A handful of the cs1 templates automatically set |type=
: {{
cite AV media}}
, {{cite interview}}
, {{
cite mailing list}}
, {{
cite map}}
, {{
cite podcast}}
, {{
cite press release}}
, {{
cite report}}
, {{
cite techreport}}
, and {{
cite thesis}}
.{{cite interview}}
could use a tweak. It doesn't handle pagination correctly if written as a journal cite; renders the same as magazine, news, and generic 'work' cites:
Wikitext | {{cite interview
|
---|---|
Live | "Title". Journal (Interview). 1 (4): 7. |
Sandbox | "Title". Journal (Interview). 1 (4): 7. |
{{cite whatever}}
to make them 'smart enough' to do the 'right thing' in the presence of |interviewer=
. I was musing about an entire redesign of cs1 and, though I didn't write about it, thinking about how such changes might effect downstream tools and other users.{{
cite interview}}
will need continuous tweaks?{{cite interview}}
but not by much (and we should probably continue to support it because en.wiki isn't the only wiki to use the cs1 module suite).There's no reason why errors shouldn't be flagged and tracked in draft space. It's time to enable this. Headbomb { t · c · p · b} 16:27, 24 February 2018 (UTC)
@ this talk page's article, My bad. unintentional, this may be how I learn to revert (vandalism or good faith), I'm all ears Deermouse ( talk) 22:32, 25 March 2018 (UTC)
This cite template gives an "ASIN uses ISBN" error:
"General Hospital: Luke & Laura (Lovers on the Run) Vol. 1". Burbank, California: ABC Studios. February 2, 1994. ASIN 6303007759. Retrieved September 27, 2016.
Is this ASIN really an ISBN? It passes the checksum test, but I am unable to find any verification that it is really an ISBN. Here's another one:
"Clay Pigeon".
PolyGram Filmed Entertainment.
Universal City, California:
Universal Studios. April 27, 1999.
ISBN
6305353212. Retrieved November 21, 2016. {{
cite web}}
: Check |isbn=
value: invalid group id (
help)
"Clay Pigeon". PolyGram Filmed Entertainment. Universal City, California: Universal Studios. April 27, 1999. ASIN 6305353212. Retrieved November 21, 2016.
When I click to follow the ISBN link, I get nothing but dead ends, even using the Amazon link at Special:BookSources. When I follow the ASIN link for the same number, I get an Amazon page.
Wikipedia:WikiProject Check Wikipedia/ISBN errors shows these "ISBN" values starting with 63 as errors. I don't know what CheckWiki's methodology is.
List of ISBN identifier groups does not show a country for 10-digit ISBNs starting with 63. Neither does the International ISBN Agency. – Jonesey95 ( talk) 14:34, 27 March 2018 (UTC)
|asin=63...
is not an isbn then perhaps we might tweak the module code to exclude such asin numbers from the category.i note recent conflict on reference using cite web in film article.
reference about aggregator website, example rotten tomatoes, metacritic, box office mojo. name of website usually go in work=, website=.
but some user do not like italic that work=, website=, put on name. they do following:
does italic matter? does work=, publisher= difference matter?
discussion previous at Wikipedia talk:WikiProject Film#i comment about reference format. IUpdateRottenTomatoes ( talk) 18:03, 27 March 2018 (UTC)
In the past I used the dead-url parameter (I think) to indicate that the URL for the citation no longer worked, and someone needed to look at it, i.e. find an archived version or a new version of the page. However, from reading the documentation and using it again now, it looks like this is no longer the intended usage of dead-url. It doesn't show up anywhere, there is no hidden category, etc. What is the correct usage of dead-url and what parameter can I use to indicate dead links? Or should it be in a separate {{ dead link}} template? — Ynhockey ( Talk) 12:33, 17 February 2018 (UTC)
|dead-url=
nor has that functionality ever been implemented. The parameter is ignored except when the cs1|2 template uses both |archive-url=
and |archive-date=
. There is no cs1|2-specific parameter to indicate that a url is dead so the {{
dead link}}
template should be used to do that (outside of the cs1|2 template).|dead-url=
is intended to be used in conjunction with archived urls, the name should have reflected that to avoid obvious confusion by users.
Jason Quinn (
talk) 13:58, 17 February 2018 (UTC)
|<name>-url=
parameters take urls as their assigned values. I have never gotten sufficient traction to deprecate |dead-url=
and replace it with with something more appropriate. This morning I was thinking that |use-archive=
url-state
/url-status
before. (Russian Wikipedia allows HTTP codes in the field as well, which might be an interesting addition here, especially for IABot.) --
Izno (
talk) 15:33, 17 February 2018 (UTC)
|archive-state=
(or |archive-status=
or |archive-display=
) so that the three |archive-*=
arguments are easier to remember and kept together as a set. It's also more clear referring to the state of the archive, and not the url, which is the main source of confusion. Should the archive come first or second in display is the underlying question. --
Green
C 19:46, 17 February 2018 (UTC)
|archive-display=
among the three. In each case the association is much clearer. The problem with |dead-url=
is that it looks self-explanatory (seeming to answer the question "does the url work?") but it is not.
Jason Quinn (
talk) 02:26, 18 February 2018 (UTC)state of the archivebut rather it's the state of the url which can be: live, dead, unfit, usurped, or unknown. This suggests that the parameter name must refer to the url somehow so parameter names like
|url-state=
or |url-status=
(credit an IP editor for those names, not me) should be preferred over an |archive-*=
name.|dead-url=
accepts yes
, true
, y
, no
, unfit
, usurped
, bot: unknown
. If we shift to use |url-state=
, then the accepted parameter values become: dead
, live
(the default), unfit
, usurped
, bot: unknown
.|url-state=dead
as being more clear than |dead-url=yes
in terms of clearing up the confusion what the argument is meant for. --
Green
C 19:56, 18 February 2018 (UTC)
|url-is=
(dead
, live
, ...) Got anything better?|archive-disp=url-unfit
, |archive-disp=url-dead
, |archive-disp=url-live
etc.. or drop the "url" part altogether. What the option-switches do is described in the docs, but the argument name makes it clear it is mainly being used for archive display, what most people use it for. --
Green
C 17:03, 19 February 2018 (UTC)|deadurl=
gets added - my bot WaybackMedic removes strays, and Cyberpower678's IABot marks links dead regardless. --
Green
C 19:55, 17 February 2018 (UTC)
|dead-url=
would be deprecated when the new parameter is implemented, and the two would operate in parallel (but not simultaneously) through the transition period – which could be quite long. A bot task could be developed to convert existing |dead-url=
to the new parameter (iabot and wayback medic might implement that as well). At some point in the future when the count of articles using |dead-url=
drops below an acceptable number, support for it is removed. This is, more-or-less, how we handle all deprecated parameters (which all have had the possibility of breaking external tools).|dead-url=
with a missing or empty |archive-url=
. They could assume the url is dead act accordingly (add an archive) - probably a safe bet in most cases since how else would a stray |deadurl=
with a "yes" value get added unless a human thought the URL was dead. --
Green
C 19:56, 18 February 2018 (UTC)
many other tools ...so it is the tool maintainers' responsibility to keep up with us and to join in these conversations to say why we should or should not do what we propose to do.
|dead-url=
) which I don't think is too common. I haven't been logging this, but just added logs so the next time it runs it will record how common it is within a set of articles (probably 100k to 200k articles will get processed). Granted, bot maintenance is not ideal as long-term is not guaranteed. --
Green
C 17:03, 19 February 2018 (UTC)@
Trappist the monk and
GreenC: Another possible parameter which I don't see suggested above is Edit: I did not realize there were more than two parameters, otherwise I would not have suggested that. I am curious why those parameters were added, so I may go back and look at prior discussions.
E to the Pi times i (
talk |
contribs) 22:20, 27 March 2018 (UTC)
|use-archive=
(or |use-archive-url=
, but I prefer the former). This would explicitely state what the parameter does, and because of the "use" verb, there is little opportunity for confusion (though if you see possible confusion, please tell me). This parameter could take true and false like |dead-url=
currently does.
E to the Pi times i (
talk |
contribs) 19:17, 19 March 2018 (UTC)
|url=
. The parameter isn't a boolean so the parameter name and all of its acceptable values 'should' read somewhat sensibly. I don't think that |use-archive=unfit
is any better than |dead-url=unfit
and neither (I think) are as good as |url-state=unfit
(which would require new values dead
and live
in place of yes
and no
). Alas, |use-archive=yes
conveys nothing about the 'why' we should be using the archive.I too am (a little) confused about |dead-url=
. Looks like it was originally intended as a "yes"/"no" parameter to link the title to the original or archived URL (with the other being available). The values "usurped" and "unfit" were added to cover situations were the URL was still "live" but either was "usurped" by another unrelated site or a site "unfit" for viewing (and therefore no reason to view original site). I have encounter many sites that redirect an "unknown" page to another (usually "home") page on the site. A similar situation occurs when the referenced page contents change (e.g. "Home"). In both of these cases, I attempt to find an appropriate archive page and use |dead-url=yes
to link the title to the archived page. I do not think this is the correct usage of this parameter. I do think the parameter should be renamed and appropriate values defined. I have a slight preference for |url-state=
with values like: valid
, dead
, redirected
, volatile
, usurped
, and unfit
. usurped
and unfit
would be two were the original link would need to be supressed.—
User-duck (
talk) 22:06, 27 March 2018 (UTC)
P.S. Remember, there can be more than one URL specified in some citation templates (e.g. {{ cite book}})— User-duck ( talk) 22:06, 27 March 2018 (UTC)
{{
cite book}} has |url=
and |chapter-url=
parameters to link the specified URL with the appropriate field in the citation. Some archive websites provide access to the entire book and a URL for the entire book can be included. I assume the same is true for chapters as well. They may also provide access to a specific page. Google Books URLs often link to specific pages or portions of pages but seldom entire books. Editors have used |url=
or |chapter-url=
the for these URLs. I feel this is an incorrect usage of the parameter(s). I believe a |page-url=
parameter would be useful for linking a specified page with a page URL. I have used several methods to work-around the issue, but they are work-arounds.—
User-duck (
talk) 23:00, 27 March 2018 (UTC)
I've used "cite book" with "|isbn=1234567". Is there a way to make an automated bot built into wikipedia do research based on the quoted isbn number to fill in the author and publisher information? Thanks. Adrian816 ( talk) 21:27, 28 March 2018 (UTC)
For book having isbn 978-0-85412-822-8, copyright of the Handbook of Doctrine published by the Salvation Army is held "in trust" by a specific employee of the organisation, the General. While wikipedia allows a number of types of information to be included like publisher, there's no tag for " |copyright=The General of The Salvation Army".
On the relevant page of the book is: c 2010 The General of The Salvation Army This edition published 2010
therefore full citation of this book needs to include the copyright holder and printing company name for wikipedia to have full information.
There's also "Printed by" information for this book, in this case "UK Territory Print & Design Unit".
Please can someone look into getting wikipedia software updated to include these tags: |copyright= |printed-by=
Thanks Adrian816 ( talk) 22:29, 28 March 2018 (UTC)
|copyright=
and |printed-by=
negligibly add to the ability to verify sources.
E to the Pi times i (
talk |
contribs) 23:17, 28 March 2018 (UTC)
lang
shortcut to {{
Cite web}}{{{lang}}}
should be a shortcut for {{{language}}}
as it would be much easier and when I write "language" I usually shorten it to "lang" anyway. –
Nixinova ⟨
T |
E ⟩ 04:07, 31 March 2018 (UTC)
|language=
does have the alias |in=
which to me, is poorly chosen. I used to see it quite a lot in
Category:CS1 maint: Unrecognized language when editors meant that a source was |in=
some other larger work. I would be fine with deprecating |in=
and then, if a shorter version of |language=
is really needed, adding |lang=
.|in=
as well as adding a |lang=
as a synonym for |language=
. --
Izno (
talk) 14:03, 31 March 2018 (UTC)
|in=
in {{
cite web}}, and they were all being used incorrectly. Let's deprecate that one. –
Jonesey95 (
talk) 14:23, 31 March 2018 (UTC)
|in=
and adding a |lang=
. --
Emir of Wikipedia (
talk) 14:40, 31 March 2018 (UTC)|in=
is confusing since it make it look like it refers to the "in Smith, J. (ed) Title part of an editor work. If |lang=
us accepted as an alias (which I'm fine with), it should cover all templates, not just {{
cite web}}.
Headbomb {
t ·
c ·
p ·
b} 18:50, 31 March 2018 (UTC)|in=
. I'm mildly against adding |lang=
, though; it's unambiguous enough but I think there is enough unnecessary variation in parameter names already. —
David Eppstein (
talk) 19:35, 31 March 2018 (UTC)lang
was deliberately avoided? Commons and Wikidata, as the two WMF multilingual projects, support several schemes for display of multilingual content. For templates it is commons to use the Autotranslate mechanism and template, which uses the lang
parameter. On Commons and Wikidata templates avoid assigning their own use to a lang
parameter to avoid incompatibility with Autotranslate. Probably not a direct concern for CS1 on en.WP, and I don't think either Commons or Wikidata currently make use of CS1, but something to consider. —
RP88 (
talk) 19:38, 31 March 2018 (UTC)
|lang=
or |language=
too? If it is just the former then it is something to consider, but if it is both then if it was really a big issue it would have been brought up anyway.
Emir of Wikipedia (
talk) 19:40, 31 March 2018 (UTC)
The citation
appears as
{{
cite journal}}
: Check |zbl=
value (
help)with an error message "Check |zbl= value (help)". I have checked the zbl= value, and it is correct. Please correct this so that the reference can be formatted with its correct zbl id. — David Eppstein ( talk) 07:15, 3 April 2018 (UTC)
|zbl=
,
Zbl
06684722, that the citation template again does not like. Where is the source for the information that this parameter must be of the form "nnnn.nnnnn"? Because apparently this is incorrect. —
David Eppstein (
talk) 07:23, 3 April 2018 (UTC)Not a Zbl; that identifier is a JFM:
— Trappist the monk ( talk) 10:31, 3 April 2018 (UTC)
This help request has been answered. If you need more help, you can , contact the responding user(s) directly on their user talk page, or consider visiting the Teahouse. |
but the help page cite tweet doesn't have the infobox on the template. Can the infobox listing the different variations of cite... be added to the cite tweet page please. The infobox looks like a global template, but it lacks cite tweet Please fix the cite tweet help page, and amend the infobox on this help page to include cite tweet thanks Adrian816 ( talk) 23:01, 3 April 2018 (UTC)
{{
cite tweet}}
is not a cs1 template because it does not directly use either of
Module:Citation/CS1 or {{
citation/core}}
. For that reason, {{cite tweet}}
is a meta template and meta templates do not belong in the cs1 'infobox'.Hi all. As you probably noticed recently, the WMF released a dataset on the works cited on En-Wiki that included a few select identifiers (particularly ISBNs, WorldCat IDs and DOIs): https://blog.wikimedia.org/2018/04/05/ten-most-cited-sources-wikipedia/ . One of the challenges with this dataset: is that it only works, when their are identifiers including in citations. Could we create a tracking category, which helps identify citations from the Journal/Book citations that don't include any identifier? This could help empower community members to help better populate those citation data, so that future analysis could include more of our citations? Secondly to make this a manageable backlog: could we create a variable for citations in those sets for "no identifier available" -- which could allow folks to review the citation, and then confirm that it in fact can not be tied to an identifier (and put those items in another tracking category?) Generally Books and Journals should be things with some type of identifier, otherwise the templates are probably be used for the wrong thing (i.e. published reports or magazines, which should be cited using one of the more specific templates). Thanks much, Sadads ( talk) 14:47, 14 April 2018 (UTC)
I am working with an editor at bn.wiki to implement the cs1|2 module suite there; discussion on my talk page.
I have moved the definitions of the various separator and postscript characters out of Module:Citation/CS1/sandbox into the presentation table in Module:Citation/CS1/Configuration/sandbox.
Because Bengali does not use western style digits, and also because Lua does not understand non-western digits, a couple of tweaks were necessary to support enumerated parameter names written wholly in Bengali.
These changes should be transparent to the en.wiki module suite:
Wikitext | {{cite book
|
---|---|
Live | Brown, Red; Orange, Yellow; Green, Blue. Title. |
Sandbox | Brown, Red; Orange, Yellow; Green, Blue. Title. |
Wikitext | {{citation
|
---|---|
Live | Brown, Red; Orange, Yellow; Green, Blue, Title |
Sandbox | Brown, Red; Orange, Yellow; Green, Blue, Title |
Wikitext | {{cite book
|
---|---|
Live | Brown R, Orange Y, Green B. Title. |
Sandbox | Brown R, Orange Y, Green B. Title. |
Wikitext | {{citation
|
---|---|
Live | Brown R, Orange Y, Green B, Title |
Sandbox | Brown R, Orange Y, Green B, Title |
— Trappist the monk ( talk) 12:34, 14 April 2018 (UTC)
|publication-date=
and |year=
, both of which, when used alone in a cs1|2 template are promoted to |date=
, are returning incomplete error messages:
quietly converting hyphens to dashes. See this discussion.
|date=২০১৮-০৫-০৭
string.match()
function looking to match the pattern '%d%d%d%d%-%d%d%-%d%d'
which worked fine as long as the digits were western (0–9) single-byte digits (because the Lua string library operates on bytes). But, Bengali digits are three bytes each. Here is the percent encoded version of the example date:
%E0%A7%A8%E0%A7%A6%E0%A7%A7%E0%A7%AE-%E0%A7%A6%E0%A7%AB-%E0%A7%A6%E0%A7%AD
২০১৮-০৫-০৭
as a ymd date so it silently converted the hyphens to endashes giving this result:
string.match()
to mw.ustring.match()
which operates on Unicode characters, so that ymd format dates are recognized and skipped when the module does the hyphen conversion.Something I noticed re translators and periods, as a heads up:
{{cite journal|last=Author|first=A.
|translator-last=Translator|translator-first=T.
|title=Title|journal=Journal|date=2018|volume=1|page=100}}
Author, A. (2018). "Title". Journal. 1. Translated by Translator, T.: 100.{{ cite journal}}
:|last=
has generic name ( help)
{{cite journal|author=Aut.–A.C.R.O.N.Y.M.
|translator=Transl.–A.C.R.O.N.Y.M.
|title=Title|journal=Journal|date=2018|volume=1|page=100}}
Aut.–A.C.R.O.N.Y.M. (2018). "Title". Journal. 1. Translated by Transl.–A.C.R.O.N.Y.M.: 100.
The "extra" full stop gets removed if |first=
or |author=
ends with a period but the same fix hasn't been yet been applied to |translator-first=
or |translator=
.
I'm also not sure off the top of my head of a real source that might need to be cited as such (but it's within the realm of possibility), but I also just now discovered if there is no listed author, but is a listed translator, there is an errant period at the beginning:
{{cite journal
|translator-last=Translator|translator-first=T.
|title=Title|journal=Journal|date=2018|volume=1|page=100}}
"Title". Journal. 1. Translated by Translator, T.: 100 2018.{{ cite journal}}
:|translator-last=
has generic name ( help)
Thanks, hopefully this is of use :) Umimmak ( talk) 10:33, 25 April 2018 (UTC)
|others=
and |interviewer=
and only for {{
cite journal}}
and {{
citation}}
when a 'work' parameter is set (though for this case, it isn't an issue for {{citation}}
because the element separator is a comma). Fixed, I think in the sandbox:Wikitext | {{cite journal
|
---|---|
Live | Author, A. "Title". Journal. Others O. {{
cite journal}} : |last= has generic name (
help)
|
Sandbox | Author, A. "Title". Journal. Others O. {{
cite journal}} : |last= has generic name (
help)
|
Wikitext | {{cite journal
|
---|---|
Live | Author, A. "Title". Journal. Interviewed by Interviewer I. {{
cite journal}} : |last= has generic name (
help)
|
Sandbox | Author, A. "Title". Journal. Interviewed by Interviewer I. {{
cite journal}} : |last= has generic name (
help)
|
Wikitext | {{cite journal
|
---|---|
Live | Author, A. "Title". Journal. Interviewed by Interviewer I. Others O. {{
cite journal}} : |last= has generic name (
help)
|
Sandbox | Author, A. "Title". Journal. Interviewed by Interviewer I. Others O. {{
cite journal}} : |last= has generic name (
help)
|
Wikitext | {{cite journal
|
---|---|
Live | Author, A. "Title". Journal. Translated by Translator T. {{
cite journal}} : |last= has generic name (
help)
|
Sandbox | Author, A. "Title". Journal. Translated by Translator T. {{
cite journal}} : |last= has generic name (
help)
|
Wikitext | {{cite journal
|
---|---|
Live | Author, A. "Title". Journal. Translated by Translator T. Others O. {{
cite journal}} : |last= has generic name (
help)
|
Sandbox | Author, A. "Title". Journal. Translated by Translator T. Others O. {{
cite journal}} : |last= has generic name (
help)
|
Wikitext | {{cite journal
|
---|---|
Live | Author, A. "Title". Journal. Interviewed by Interviewer I. Translated by Translator T. {{
cite journal}} : |last= has generic name (
help)
|
Sandbox | Author, A. "Title". Journal. Interviewed by Interviewer I. Translated by Translator T. {{
cite journal}} : |last= has generic name (
help)
|
Wikitext | {{cite journal
|
---|---|
Live | Author, A. "Title". Journal. Interviewed by Interviewer I. Translated by Translator T. Others O. {{
cite journal}} : |last= has generic name (
help)
|
Sandbox | Author, A. "Title". Journal. Interviewed by Interviewer I. Translated by Translator T. Others O. {{
cite journal}} : |last= has generic name (
help)
|
Wikitext | {{cite journal
|
---|---|
Live | Author, A. "Title". Journal. Interviewed by Interviewer I. Translated by Translator T. Others O. {{
cite journal}} : |last= has generic name (
help)
|
Sandbox | Author, A. "Title". Journal. Interviewed by Interviewer I. Translated by Translator T. Others O. {{
cite journal}} : |last= has generic name (
help)
|
safe_join()
uses a series of Lua pattern matching string functions to do its work. The Lua string library works well at en.wiki becase our terminal characters are all single byte characters. At bn.wiki, the terminal character is the dari ('।', Unicode U+0964 Devanagari Danda) which is a three-byte character. For safe_join()
to properly recognize that character requires that we use the Ustring library function which are significantly slower than their equivalent String library function. So that en.wiki doesn't take a performance hit and to make the code compatible with bn.wiki and others that use multi-byte terminal characters, safe_join()
now inspects the terminal character and chooses the appropriate library functions before it does its work.safe_join()
is no longer required...|chapter=
has these aliases: |contribution=
, |entry=
, |article=
, and |section=
.
Associated with |chapter=
are: |chapter-format=
, |chapter-url=
, and |chapter-url-access=
. We should have similar parameters for all of the |chapter=
aliases but don't.
I have added these to Module:Citation/CS1/Configuration/sandbox:
|entry-format=
, |article-format=
|entry-url=
, |article-url=
|contribution-url-access=
, |entry-url-access=
, |article-url-access=
, |section-url-access=
— Trappist the monk ( talk) 11:47, 24 May 2018 (UTC)
An editor from Australia brought up an interesting point in
this discussion that the |archivedate=
can actually pre-date the publication of the underlying source due to time zone shifts. For example a news report published noon Monday in Australia might have an |archivedate=
of Sunday, which is nonsensical (archive.org is located in San Francisco and probably uses GMT). So the editor has been entering the day they created the archive relative to their location in Australia, which then gets changed by bots trying to keep the snapshot date in sync with the |archivedate=
(
example). The source of the confusion appears to be the CS1 documentation which ambiguously says "Date when the original URL was archived" .. is the date relative to the archive service provider or the archiving user location?
As I see it, there's no reason to record when the editor created the archive (information more often than not unknown since the archive was created by someone else); the reader only needs to know the webarchive service date so they know how to retrieve it, the only purpose of having a |archivedate=
. As such, would it make sense to change the documentation to reflect that dates are relative to the service provider date. --
Green
C 15:25, 19 April 2018 (UTC)
|archive-url=
to include the word 'snapshot':
I added this. Took the opportunity to additionally add "templated dates are discouraged" since it is also documented elsewhere due to COIN data. -- Green C 02:53, 21 April 2018 (UTC)
|archive-url=
documentation?Since this module is being continuously copied and overwritten to wikidata, I guess this is the place to report errors of that copy as well. On Wikidata the id_handlers cannot provide a valid sitelink by the code:
text = external_link_id({link = handler.link, label = handler.label, prefix=handler.prefix,id=id,separator=handler.separator, encode=handler.encode, access=access}) .. (inactive or '')
"handler.link" just doesn't work on Wikidata. The QID should be also provided in Module:Citation/CS1/Configuration, and link is compiled as something like "d:QID". Of course a site server checking would also be needed to be able to decide which link configuration to use:
_linkconfig = string.match(mw.site.server, "wikidata") or "sitelink"
-- Pzgulyas ( talk) 15:14, 20 March 2018 (UTC)
Continuously copied and overwritten to wikidate? (emphasis mine) What do you mean by that?
"handler.link" just doesn't work on Wikidata?
I added a real-life example to d:Wikidata:Sandbox, please see the red links. Please also try changing the display language to something different than English, which highlights another malfunction: The property P577 (publication date) should be queried in language-independent manner in Cite Q template, the simpler {{#property:P577|from={{{1}}}}} doesn't work in Wikidata well.-- Pzgulyas ( talk) 11:46, 21 March 2018 (UTC)
continuously copied...question.
{{
cite Q}}
should be directed to
Template talk:cite Q. That template fetches data from wikidata and then hands it off to {{
citation}}
for rendering. {{citation}}
,
Module:Citation/CS1, and associated modules do not use wikidata for anything.@ Trappist the monk:: Don't feel be opposed, I'm trying to answer your questions one-by-one:
continuously copied...: I mean, it was copied in the past, and any changes on wikidata will be overwritten from enwiki in the future.
The red links occur because...: I know the reason why they occur, but the fix should be done in this software. E.g. the link that points here to Digital object identifier on wikidata should point to d:Q25670. Currently the Q number is not available in the Module:Citation/CS1/Configuration, and should be added.
This is the expected behavior, isn't it?...: No, the expected behavior is that they point to the correspondig wikidata Q object.
Dates are problematic. (...) editors there must modify the code as necessary to support their local date formats...: Here the case is different. There is no need to support local date formats, only when reading the date property, it must be ensured that the data is passed in a way that the rest of the code understands. Querying the property with #property:P577 is not appropriate, this must be replaced by a piece of lua code.
Questions and comments concerning (...) should be directed to...: You are right about
{{
cite Q}}
, but the problem is caused by the codes in
Module:Citation/CS1/Configuration and
Module:Citation/CS1/Identifiers, both of which talk pages are redirected here, I guess for the sake of keeping the discussion in a centralized place.-- Pzgulyas ( talk) 13:41, 21 March 2018 (UTC)
[[Digital object identifier|doi]]
[[d:Q25670|doi]]
this_wiki_code = mw.language.getContentLanguage():getCode()
article = mw.wikibase.getEntity ('Q25670'):getSitelink (this_wiki_code .. 'wiki')
link = '[[' .. this_wiki_code .. ':' .. article .. ']]'
this_wiki_code
to 'es'article
to 'Identificador de objeto digital'link = '[[' .. 'es' .. ':' .. 'Identificador de objeto digital' .. ']]'
→ [[es:Identificador de objeto digital]]
→
es:Identificador de objeto digitalthis_wiki_code = mw.language.getContentLanguage():getCode()
for me, sets this_wiki_code
to 'en' regardless of user preferences language setting.{{cite journal/new |title=A Higher Level Classification of All Living Organisms |doi=10.1371/JOURNAL.PONE.0119248 |pmc=4418965 |pmid=25923521}}
{{
cite journal}}
: Cite journal requires |journal=
(
help)CS1 maint: unflagged free DOI (
link)
'"`UNIQ--templatestyles-000000A9-QINU`"'<cite class="citation journal cs1">[https://www.ncbi.nlm.nih.gov/pmc/articles/PMC4418965 "A Higher Level Classification of All Living Organisms"]. [[doi (identifier)|doi]]:[https://doi.org/10.1371%2FJOURNAL.PONE.0119248 10.1371/JOURNAL.PONE.0119248]. [[PMC (identifier)|PMC]] <span class="id-lock-free" title="Freely accessible">[https://www.ncbi.nlm.nih.gov/pmc/articles/PMC4418965 4418965]</span>. [[PMID (identifier)|PMID]] [https://pubmed.ncbi.nlm.nih.gov/25923521 25923521].</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=article&rft.atitle=A+Higher+Level+Classification+of+All+Living+Organisms&rft_id=https%3A%2F%2Fwww.ncbi.nlm.nih.gov%2Fpmc%2Farticles%2FPMC4418965%23id-name%3DPMC&rft_id=info%3Apmid%2F25923521&rft_id=info%3Adoi%2F10.1371%2FJOURNAL.PONE.0119248&rft_id=https%3A%2F%2Fwww.ncbi.nlm.nih.gov%2Fpmc%2Farticles%2FPMC4418965&rfr_id=info%3Asid%2Fen.wikipedia.org%3AHelp+talk%3ACitation+Style+1%2FArchive+42" class="Z3988"></span> <span class="cs1-visible-error citation-comment"><code class="cs1-code">{{[[Template:cite journal|cite journal]]}}</code>: </span><span class="cs1-visible-error citation-comment">Cite journal requires <code class="cs1-code">|journal=</code> ([[Help:CS1 errors#missing_periodical|help]])</span><span class="cs1-maint citation-comment">CS1 maint: unflagged free DOI ([[:Category:CS1 maint: unflagged free DOI|link]])</span>
If it is decided going this way, language code on wikidata can be queried by print(mw.getCurrentFrame():preprocess('{{int:lang}}'))
--
Pzgulyas (
talk) 09:02, 22 March 2018 (UTC)
{{int:lang}}
doesn't work at en.wiki; → ⧼lang⧽. The tone of your post suggests to me that you believe that the 'partial answer' that I described above is: wrong? flawed? misguided? something else? If that is your belief then what is the better way?I'm really sorry for my previous short answer, I like your solution. Just I wrote from work office, and suddenly some work appeared to be done, so I apologize. I think what you have done, is the right fix. I think for the language code querying method selection you may use some test like string.match(mw.site.server, "wikidata")
--
Pzgulyas (
talk) 10:11, 23 March 2018 (UTC)
I have hacked d:Template:Cite Q and d:Module:Citeq so that dates extracted from wikidata are always rendered dmy in English regardless of the user's interface language choice.
While doing that, I wondered if it was even necessary. What protections does wikidata provide? Are dates in wikidata validated and so guaranteed to be correct? If so, then much the cs1|2 date validation is not required for dates taken from wikidata. But, it's still problematic because editors can override |date=
in {{cite Q}}
; can still provide |access-date=
so these must be validated.
— Trappist the monk ( talk) 11:05, 24 March 2018 (UTC)
I think we should allow in press and forthcoming preprints to be cited on Wikipedia, at least if a public URL is available for WP:V. Currently, cite templates produce an error message if "In press" is used with the date parameter of these templates. I propose that
|date=
in citation templates. I think this involves changing function check_date in
Module:Citation/CS1/Date validation|date=
is "In press" or "Forthcoming", citation templates display an error message if access-date is empty, and show the access-date parameter even if no URL is given. This is a new use for |access-date=
, but I think it is better than creating a new parameter just for this purpose.I suggest that proposal 3 depends on proposal 2, and proposal 2 depends on proposal 1, but proposal 1 does not depend on 1 or 2. What do others think? Daask ( talk) 11:55, 23 April 2018 (UTC)
More and more, book chapters are published electronically and have their own doi. we already have parameter chapter-url; in my view it would be useful to have chapter-doi as well. Is that do-able? thanks. Jytdog ( talk) 18:10, 28 April 2018 (UTC)
|id={{
doi}}
to provide a second option. But I can't see a reason for systematically including the book DOI if the chapter DOI will easily lead the reader to the same place in a click or two.
Umimmak (
talk) 14:42, 29 April 2018 (UTC)There is a discussion at Template talk:Cite tweet#Non text tweets about citing tweets that contain links, images, etc. Please comment over there. wumbolo ^^^ 14:57, 29 April 2018 (UTC)
|issue=
informationI updated the documentation of the |issue=
parameter to account for cases like "#293, Vol. 24, No. 5" (i.e., two different kinds of issue numbering), by adding the instruction "When a total issue number and an issue within a volume are both given – e.g., "#293, Vol. 24, No. 5" – this can be coded as |volume=24
|issue=5 [total issue #293]
."
[1]; the documentation has for years already accounted for issue naming, with "When the issue has a special title of its own, this may be given, in italics, along with the issue number, e.g. |issue=2, ''Modern Canadian Literature''
." This was not only reverted, but the revert included removal of both of these instructions, with an edit summary that doesn't make much sense to me: "no; abusing |issue= is no substitute for abusing |page=; one piece of information per parameter"
[2]. Using |issue=
for issue information is not "abuse" of the parameter, it's what the parameter exists for. Nor is there any principle here of "one piece of information per parameter", or we'd have separate parameters for middle names of authors, separate parameters for countries of city locations, separate parameters for days and months in dates, separate parameters for subtitles, and so on.
The problem to solve is that people are randomly actually abusing completely unrelated parameters like |page=
and |publisher=
to try to shoe-horn complex issue information into the template, when it obviously belongs in |issue=
. But not obviously enough, or people wouldn't be doing that and we wouldn't need to have clearer documentation.
The only other alternative it to introduce yet more parameters for such things, and I think that's a terrible idea. So, I think this version should be restored. — SMcCandlish ☏ ¢ 😼 12:28, 5 February 2018 (UTC)
|volume=
when a cumulative issue number is supplied in |issue=
. For the issue-number-issue-title question, we have two fundamentally different pieces of information: the number is the basic descriptive unit typical of almost all periodicals and issue titles are generally rare special cases where the title merely supplements the issue number. Choose one, do not include wiki markup because the value assigned to |issue=
is made part of the metadata.|title=
and |chapter=
(and their aliases) because titles often mix upright and italic fonts for good reason (scientific names, for example).I think the simplest way to handle this would be to not consider |number=
and |issue=
aliases when they are both listed. Or at least you could have |number-issue=yes
to overide them being considered aliases. This way you could use
{{cite magazine|author=A. Uthor |year=2010 |title=Things and stuff |magazine=Magazine Weekly |volume=7 |issue=245 |number=5|pages=24–445 |number-issue=yes}}
to generateor
{{cite journal|author=A. Uthor |year=2010 |title=Things and stuff |journal=Magazine Weekly |volume=7 |issue=245 |number=5|pages=24–445 |number-issue=yes}}
to generateThis would solve a crapton of issues. Headbomb { t · c · p · b} 17:51, 21 March 2018 (UTC)
On the page Yang Jisheng (statesman), there is a possible issue with the citation for the article "Lǐ Dàzhāo de Zuòyòumíng", which possesses an original title that uses Chinese characters. This does not appear to be merely a problem with my computer or browser, as I have tried multiple examples of each. The template {{ Cite web}} was used for that particular citation. Between "Lǐ Dàzhāo de Zuòyòumíng" (title) and the same in Chinese characters (script-title) there appears to be a line break where there should not be one. Do other users observe the same issue? (Is this a problem in other articles?) Please advise if script-title is broken or if I am overlooking a simple solution. Simply removing the parameter script-title might solve the problem, but it is an issue if our citations are unable to display Chinese text. RexSueciae ( talk) 21:51, 29 April 2018 (UTC)
Reduce the citation to just a wikilink:
[http://cpc.people.com.cn/BIG5/64162/64172/85037/85038/7104292.html "Lǐ Dàzhāo de Zuòyòumíng" <bdi lang="zh" >李大釗的座右銘</bdi>
Place it directly at the left margin in show preview (for me) splits the wikilink at the <bdi>...</bdi>
tag:
"Lǐ Dàzhāo de Zuòyòumíng" 李大釗的座右銘
Indent with definition list markup (:
):
renders correctly.
Same experiments, but replace <bdi>...</bdi>
with <span>...</span>
:
"Lǐ Dàzhāo de Zuòyòumíng" 李大釗的座右銘
Indent with definition list markup (:
):
Both render correctly in show preview. Saving this page now to see what happens.
— Trappist the monk ( talk) 22:47, 29 April 2018 (UTC)
But ... but ... Argh. So I saved my edit above and both the <bdi>...</bdi>
and <span>...</span>
tests whether against the left margin or indented rendered correctly. As a further experiment, I null edited the page and got a different result: same as I get in show preview. It is interesting that in show preview, the Chinese characters in <bdi>...</bdi>
(indented) are not part of the wikilink when they should be.
I'm seeing this with the latest Chrome browser (only one on my machine).
I can only conclude that this is not a |script-title=
issue but appears to be a mediawiki issue with <bdi>...</bdi>
. Perhaps I'll think on this some more and then take it to
WP:VPT
— Trappist the monk ( talk) 23:01, 29 April 2018 (UTC)