The update is finally complete for us. I had some points I wanted to mention in the end which may or may not require an answer.
First of all, thank you for your patience and dedication. You have been helping me personally and us as a community for years now.
Secondly, when we started the update this time, we talked about taking notes that could be added in a help page here in regard to that. If you'd please take another look at the link of my sandbox above, you'll see that its content is "precisely" that. Those are the changes that SqWiki needs to do: Add the code for the missing language parameter category in main, translate 1 line in ~/COinS, switch 3 lines to "True" in ~/Configuration, Exports section and add the code for the d.m.y date format in ~/Date validation (this will be the hardest to achieve during each update when compared with the other 3 changes). Beside that, everything else is copy-pasting. At least, so far. Should I add these notes somewhere? How exactly do I add them? Have we chosen a certain "style" about adding directions? Can I just say what I just said here (copy-paste + these 4 changes + localization at ~/Configuration)?
Speaking of that page, where exactly is that page? I've forgotten its name. And, have there been any more changes in regard to the info table we were setting up some days ago?
And lastly, returning to the date subject, I sure hope we can provide better automatic date formatting by the Mediawiki side in the future. I believe that would help make the CS1 code more elegant in general, remove the need for "local quirky code", like we just added for d.m.y, and also make Smallem's life easier overall. I'd be willing to make some active attempts to help in this direction (as I tried by locating all the date formatting related files in Mediawiki) but I don't know who/where exactly to ask for what. If you can provide any more insight on this problem whatsoever, I'd be interested in knowing.
To end it, I do have 2 other naive questions: When we talked about Smallem's latest regexes there was a moment when you said that you had a vague memory of me saying to you that coupling different parameters together wasn't good for a specific reason. I did couple them (as you saw) and, as I said above, it worked fine. But right after the first edit was made I remembered what that "bad thing" might have been: Take a look at Smallem's contributions and see its summaries. You'll see that most of the messages are gigantic and hard to read and that's because the regex lines are the same way. Having said that, I'd still write them coupled because manually writing ~1300 lines was very tiresome and if they weren't coupled the number would have been much bigger, most likely making me drop the task along the way. But given that we currently have the complete list, is there any find and replace command(s) I can apply to it to make it separate (semi)automatically? I believe there isn't. Also, is there any way to make something like this for generating global date regexes? The benefits would be many and diverse but considering all we said above about Mediawiki's date formatting support, I believe even stronger there isn't. - Klein Muçi ( talk) 01:07, 14 February 2022 (UTC)
|accessdate=June 1, 2015
→ |accessdate=1 qershor 2015
but did not change |date=June 1, 2015
so the citation is still marked as Mirëmbajtja CS1: Datë e përkthyer automatikisht.add everything [you] mentioned above as a comment for SqWiki/SqQuote. The table for Module:Citation/CS1 is currently in my sandbox so you can remember what it looks like.
Yes but ... I was looking for.I have no idea what you are talking about...
|edition=illustrated
en-AU
(Australian), en-CA
(Canadian) en-GB
(British), and en-US
(American). Because that abomination that is ve adds IETF-like language tags to |language=
, cs1|2 now accepts those and categorizes accordingly. Other forms of English not recognized by MediaWiki, for example en-IN
(Indian), are recognized only by the language subtag. A better example might be Portuguese. en.wiki has three categories: Brazilian Portuguese (pt-BR
), European Portuguese (pt-PT
), and Portuguese (pt
).|edition=illustrated
is a problem? You should fix this though:
sq:Moduli:Citation/CS1/Configuration#L-37.'local' = 'kopje e arkivuar',
|edition=
accepts anything except something that looks like 'edition' or an abbreviation threreof{{#tag: categorytree|CS1 foreign language sources}}
(at sq.wiki, this: {{#tag: categorytree|Vetitë CS1: Burime në gjuhë të huaj |depth=}}
de-AT
etc is a complexity that I haven't yet felt like dealing with.{{#language:<language tag>|sq}}
(r"(\{\{\s*cit[aeio][^\}]*\|\s*pmc\s*=\s*)pmc(\d*\s*[\|\}])", r"\1\2"),
|pmc=
and |PMC=
are allowed. No guarantee that the assigned value will have pmc
; could be PMC
; could be some combination of cases.(r"(\{\{\s*cit[aeio][^\}]*\|\s*date\s*=\s*.*)-(.*\s*[\|\}])", r"\1–\2"),
(r"(\{\{\s*cit[aeio][^\}]*\|\s*(?:access\-?|archive\-?|doi\-broken\-|lay\-|pmc\-embargo\-|publication\-|air\-?)?date\s*=\s*\d{1,2})\-(\d{1,2} +[A-Za-z]+ +\d{4})", r"\1–\2"),
Also, just found out that we have deprecated the lay parameters. The problem is that I find the deprecation notice unexplanatory enough. What were lay parameters and what was their function? What exactly would mean building a new template for them? Something like {{Cite lay....}}? We don't have a lot articles using them anyway but I don't know what I should do with the information in those parameters. Can I safely remove them or not. - Klein Muçi ( talk) 13:13, 16 February 2022 (UTC)
|lay-date=
, |lay-format=
, |lay-source=
, and |lay-url=
parameters were intended to provide a method of joining a lay source to a specialist source where the lay source is purportedly more easily understood by the general reader. The problem is that the lay source is missing most of the important bibliographic detail that is expected from a proper citation. These parameters are often used as a way to shoehorn two citations into a template designed to properly render one citation at a time. It was a poor design choice that should never have been implemented.<ref>...</ref>
tags or can be bundled with the other cs1|2 template inside the same <ref>...</ref>
tags. I wrote {{
lay source}}
as one possible way to implement this. Here is a
diff from Altruism where I used {{lay source}}
.\d{1,2})\-(\d{1,2} +[A-Za-z]+ +\d{4})
Maybe if you explain to me in details what each of those components serves for it'd be easier for me. I don't understand the what happens with the curly brackets and how the part in square brackets helps in months exactly. -
Klein Muçi (
talk)
15:39, 17 February 2022 (UTC)(\d{1,2})\-(\d{1,2} +[A-Za-z]+ +\d{4})
1-3 something 1234
\1–\2
(r"(\{\{\s*cit[aeio][^\}]*\|\s*(?:access\-?|archive\-?|doi\-broken\-|lay\-|pmc\-embargo\-|publication\-|air\-?)?date\s*=\s*\d{1,2})\-(\d{1,2} +[A-Za-z]+ +\d{4})", r"\1–\2"),
(r"(\{\{\s*cit[aeio][^\}]*\|\s*(?:access\-?|archive\-?|doi\-broken\-|lay\-|pmc\-embargo\-|publication\-|air\-?)?date\s*=\s*\d{1,2} +[A-Za-z])\-(\d{1,2} +[A-Za-z]+ +\d{4})", r"\1–\2"),
(r"(\{\{\s*cit[aeio][^\}]*\|\s*(?:access\-?|archive\-?|doi\-broken\-|lay\-|pmc\-embargo\-|publication\-|air\-?)?date\s*=\s*\d{1,2} +[A-Za-z]+ +\d{4})\-(\d{1,2} +[A-Za-z]+ +\d{4})", r"\1–\2"),
(r"(\{\{\s*cit[aeio][^\}]*\|\s*(?:access\-?|archive\-?|doi\-broken\-|lay\-|pmc\-embargo\-|publication\-|air\-?)?date\s*=\s*[A-Za-z]+ +\d{4})\-([A-Za-z]+ +\d{4})", r"\1–\2"),
(r"(\{\{\s*cit[aeio][^\}]*\|\s*(?:access\-?|archive\-?|doi\-broken\-|lay\-|pmc\-embargo\-|publication\-|air\-?)?date\s*=\s*[A-Za-z])\-([A-Za-z]+ +\d{4})", r"\1–\2"),
[A-Za-z]+
, right? The others are not season-inclusive because there is no format like 17–18 Spring 2022.{{cite book |title=Title |date= December 2021 – January 2022}}
{{cite book |title=Title |date= December 2021–January 2022}}
|gjuha=
to
sq:Moduli:Citation/CS1/Suggestions. I'm less sanguine about adding that parameter here. In the normal course of things, editors who import a cs1|2 template from sq.wiki to en.wiki wouldn't find |gjuha=
in a properly formed template so having |gjuha=
here is just so much clutter.|gjuha=
. It was just because everyday we stray further from EnWiki's light by doing things like this and, of course, this increases maintenance cost (and shatters my dream of a global CS1 a bit more).{{Cite book|last=Sally Neaum|url={{google books|plainurl=yes|id=fCnZNAEACAAJ}}|title=Child Development for Early Years Students and Practitioners|date=17 May 2013|publisher=SAGE Publications|isbn=978-1-4462-6753-0}}
{{
google books}}
template, it never sees |date=17 May 2013
so Arsimi parafillor will remain in Kategoria:Mirëmbajtja CS1: Datë e përkthyer automatikisht until manually fixed.|year=14 May 1724
. Why such a precise date for such an old book? The fix for |year=
masquerading as |date=
is to create a series of regexes that look for non-year date patterns in |year=
and change |year=
to |date=
. Do this before date translation. For dMy:
(r"(\{\{\s*cit[aeio][^\}]*\|\s*)year(\s*=\s*\d{1,2} +[A-Za-z]+ +\d{4})", r"\1date\2"),
|year=
masquerading as |date=
though I have periodically thought that we should at least have a maint cat for those parameters.I have this regex for fixing case problems with pmc/mr/jfm parameters:
(r"(\{\{\s*cit[aeio][^\}]*\|\s*(?:pmc|mr|jfm)\s*=\s*)(?:pmc|mr|jfm)(\d*\s*[\|\}])", r"\1\2"),
It works fine for its purpose. (Smallem is case insensitive.) However, is there a way to make each parameter pair only with its homologue? I want to know mostly for personal curiosity in regard to further works with regexes in future cases. -
Klein Muçi (
talk)
18:37, 23 February 2022 (UTC)
|pmc=
or |PMC=
. Same for |mr=
, |MR=
, |jfm=
, and |JFM=
.|jfm=
PMCXXXXX or other combinations. I'd like it to work only on the case pmc=pmcXXXX or jfm=jfmXXXX or mr=mrXXXXX. So each parameters only pairs with its homologue. Is it clearer now? -
Klein Muçi (
talk)
22:58, 23 February 2022 (UTC)
|date=
could be more appropriate than |year=
.
(r"(\{\{\s*cit[aeio][^\}]*\|\s*)year(\s*=\s*\d{1,2} +[A-Za-z]+ +\d{4})", r"\1date\2"),
(r"(\{\{\s*cit[aeio][^\}]*\|\s*)year(\s*=\s*\d{1,2}\-d{1,2} +[A-Za-z]+ +\d{4})", r"\1date\2"),
(r"(\{\{\s*cit[aeio][^\}]*\|\s*)year(\s*=\s*[A-Za-z]+ +\d{4})", r"\1date\2"),
(r"(\{\{\s*cit[aeio][^\}]*\|\s*)year(\s*=\s*[A-Za-z]\-[A-Za-z]+ +\d{4})", r"\1date\2"),
(r"(\{\{\s*cit[aeio][^\}]*\|\s*)year(\s*=\s*\d{1,2} +[A-Za-z]\-d{1,2} +[A-Za-z]+ +\d{4})", r"\1date\2"),
(r"(\{\{\s*cit[aeio][^\}]*\|\s*)year(\s*=\s*[A-Za-z]+ +\d{4}\-[A-Za-z]+ +\d{4})", r"\1date\2"),
(r"(\{\{\s*cit[aeio][^\}]*\|\s*)year(\s*=\s*\d{1,2} +[A-Za-z]+ +\d{4}\-d{1,2} +[A-Za-z]+ +\d{4})", r"\1date\2"),
(r"(\{\{\s*cit[aeio][^\}]*\|\s*)year(\s*=\s*[A-Za-z]+ +\d{4}\-\d{4})", r"\1date\2"),
(r"(\{\{\s*cit[aeio][^\}]*\|\s*)year(\s*=\s*[A-Za-z]+ +\d{4}\-\d{2})", r"\1date\2"),
|year=
.\n
, \r
, \t
for LF, CR, and HT should work but the others require encoding. I think that this works: \u00A0
(NBSP), \u200A
(HSP), \u00AD
(SHY) but no guarantees. There are a rare handful of other unicode characters that can just be deleted:
(r"(\{\{\s*cit[aeio][^\}]*\|)U+0009([\|\}])", r"\1 \2"),
U+0009
part should be written differently but I'm wondering about the overall syntax. -
Klein Muçi (
talk)
22:59, 26 February 2022 (UTC)
{{cite book |title=Title with tab character}}
(r"(\{\{\s*cit[aeio][^\}]*)((?:\u0080|\u0081|\u0085|\u0093|\u0094|\u0096|\u0098|\u0099|\u009C|\u009E))", r"\1"),
(r"(\{\{\s*cit[aeio][^\}]*)((?:\u0009|\u000A|\u000D|\u00A0|\u200A))", r"\1 "),
(r"(\{\{\s*cit[aeio][^\}]*)(\u00AD)", r"\1-"),
What do you think? - Klein Muçi ( talk) 01:12, 27 February 2022 (UTC)
I kinda think I've designed them wrongly even though the case you gave me worked as intended. - Klein Muçi ( talk) 01:16, 27 February 2022 (UTC)
#>A
. Click that and the digits are converted to the character. Copy and paste.In the DYK nomination of
Samuel Loudon it is shown as Gwillhickers and I as co-creators. Can you look at the DYK Template to see that this is set correctly, that when the nomination is promoted and Gwillhickers gets a DYK credit, that I also automatically get one also. Thanks.--
Doug Coldwell (
talk)
18:07, 27 February 2022 (UTC)
{{Template:Did you know nominations/Samuel Loudon (printer)}}
I have never had anything to do with dykso I am not an expert. I know nothing so it would be better were you to ask at WT:DYK or some other appropriate venue where you would be talking to someone who knows something.
Maybe not the right place to ask but I was thinking... Can't IABot solve the problems with the aforementioned maint categories? Has there ever been a discussion with its maintainers of this sort you're aware of? - Klein Muçi ( talk) 01:18, 28 February 2022 (UTC)
|title=Archived copy
has almost entirely been filled by IABot. There are others that are doing that now also because it is a uniformly common name that cs1|2 is configured to track. Alas, only in a maint cat so almost no one sees these messages which is why I would like to figure out how to trickle-convert them to error messages.|url-status=live
and |url-status=dead
in the absence of |archive-url=
is mere clutter so we track that. Editor
Rlink2 using some sort of automated or semi automated tool to add |archive-url=
to these cs1|2 templates; see
Special:Contributions/Rlink2.|title=Archived copy
→ IABot finds ways to actually find the correct title → IABot corrects the old mistakes.The reason I insist on this is because IABot is already global and any solutions it is able to bring will also be global,If multiple wikis like the services the bot provides there could be a seperate global bot created to supplement IAbot in archiving and citation matters like this one. Rlink2 ( talk) 19:28, 28 February 2022 (UTC)
You are aware of what Smallem is doing with the spaces. Take a look at this diff. It's a normal one but doesn't the highlighting look strange or confusing to you? Or is it just me that I'm not used with these kinds of diffs? I was wondering if I should report it somewhere as a "failure" or an edge case where it starts breaking. - Klein Muçi ( talk) 10:03, 1 March 2022 (UTC)
This page and this page behave differently. Is that normal? Any idea why? - Klein Muçi ( talk) 02:53, 2 March 2022 (UTC)
The IANA language-subtag-registry file got updated yesterday. Can you rerun the script to update all the data modules? Thank you! Robin van der Vliet (talk) (contribs) 08:35, 3 March 2022 (UTC)
These were facts that I’ve put there, because I’ve been reading accurate history of Blackbeard by the historian Baylus Brooks. The information that you have redone is completely fake, not real at all. Blackbeard's forename, and surname is already known, which is "Edward Thache". Kennythenuker ( talk) 17:57, 5 March 2022 (UTC)
Sorry, I didn’t mean to be a little rude about, I didn’t know that Wikipedia doesn’t care about the truth. My apologies. Kennythenuker ( talk) 18:09, 5 March 2022 (UTC)
I’m sorry for not realizing about what Wikipedia is all about. I appreciate you being honest about it. People make mistakes. No hard feelings! :) Kennythenuker ( talk) 18:38, 5 March 2022 (UTC)
|year=3 March 2022
→ [Smallem helps] → |date=3 March 2022
;|last=Klein Muçi
(actually first + last) Can/Should we do a similar thing like in the case of the "pseudo-maint cat" above and convert these cases to author? I doubt we can provide auto-detection somehow, right? -
Klein Muçi (
talk)
12:46, 6 March 2022 (UTC)|first=
and if found skip. It becomes more complex because these parameters can be enumerated so, unless there were a dire need to do it, I wouldn't.|last=
with a correct last name value while missing the first name value and that shouldn't be converted to |author=
ideally. But I think that would make it impossible right? So the task is more like "convert unmatched |last=
to |author=
", according to what you propose. I'm not sure how dire the need is. I got this idea while manually fixing multiple author names in 1 parameter. What I do is I open the article for edit and search for author= and then skip until I find the one with multiple values and start splitting it. And then I started stumbling upon many articles which didn't have a single author parameter and they still were part of that maint-category. After a while I understood/remembered that author parameters could also be expressed with |last=
and that added a bit of chaos to my method. Not only it introduced a new variable I should be aware of but it also made me search for matching |first=
parameters and values and many times I had to manually switch from |last=
to |author=
because of the reasons explained above and that's when I got the idea. -
Klein Muçi (
talk)
13:22, 6 March 2022 (UTC)Hello, Trappist the monk,
There is a CSD tag SOMEWHERE that is causing Category:Articles containing uncoded-language text to show up as a requested page for speedy deletion. But I can't find the page that was originally CSD tagged. And the category hasn't been emptied yet so it would be a bad idea to delete it. Can you track down the page that has been tagged for deletion and figure out if a mistake has been made? Thanks for any help you can supply. Liz Read! Talk! 23:04, 5 March 2022 (UTC)
Hi, Trappist,
Category:CS1 maint: DOI inactive as of November 2021 showed up as an empty category. Do you expect it to remain empty or is this a periodic emptying of dated categories? Thanks for any help, I'm not sure where to go with this questions about CS1 matters. Liz Read! Talk! 01:05, 9 March 2022 (UTC)
|doi-broken-date=November 2021
to a cs1|2 template but that is no reason to keep the category once it has been emptied. I notice that you deleted the categories for June–September 2021. What is different about this one?|doi-broken-date=
so that we don't have a list of categories dating back to the dawn of wikipedia which must be why there are only six subcats in
Category:CS1 maint: DOI inactive.|doi-broken-date=
parameters so it may be that most of the time there is no reason to create a category that will never be used. Here, editors commonly add |doi-broken-date=
parameters so a new category is created every month, someone or something empties older categories which are then deleted. The emptying process may be an automated tool that attempts to follow the doi. When the tool fails to find the source, it updates |doi-broken-date=
to the current month. I suspect that that is
User:Citation bot but don't know for sure.Keeping up with peculiar global needs in regard to CS1, can we create some error categories about sources missing |trans-title/chapter/etc.(?)=
when |language=
differs from the local one? This can either be an universal proposal (pitchforks and torches aside, EnWiki could also benefit from English translated titles/chapters/etc.(?) in foreign sources, especially those that use different scripts), an only-foreign-wikis feature on or a specific request for SqWiki only. -
Klein Muçi (
talk)
03:18, 10 March 2022 (UTC)
|trans-title=
and its companions. The purpose of a citation is to help the reader locate a copy of the source. If the source only has an original-language title, a translation of that title into the local language isn't going to be much help to the reader because whatever translation is provided in |trans-title=
won't be indexed. When the source itself provides a local-language title, that is the only time that |trans-title=
should be used because when it comes to translations, every translator is different; who is to say which translation not done by the source author is the correct translation.|access-date=
, that is, a detail that is added by the editor, not by the official source. Do you have any information how that parameter is utilized here? Do editors make the same mistaken (?) assumption as I do when it comes to it? Is that really a mistake? I'm asking because, as a wiki that has most of its sources in English, we've treated that parameter really serious, going as far as making it one of the standards articles must conform to if they want the status of featured articles, that is, every foreign title must have its translated form. What you're saying above would change all of that. -
Klein Muçi (
talk)
13:06, 10 March 2022 (UTC)
|trans-title=
does provide a small window of contextbut it won't help the reader locate the source unless the translated title is an 'official' title of the source. As far as I can tell, the cs1|2 documentation does not make that suggestion. The documentation describes what an editor is to give it and how the templates display the result:
|title=
into sq |trans-title=
. If an error message, almost every page will bleed red; as much or more than Mungon ose është bosh parametri |language=. If a maint message, then only those who can see maint messages would see the message. Still a damn big category and no automated way to clear it.Straightforward question: Can I just remove on sight any |Url-status=live
assuming I won't break anything and IABot will deal with any needed details? -
Klein Muçi (
talk)
14:10, 11 March 2022 (UTC)
|Url-status=live
is not a known parameter.|url-status=live
, then maybe:
|archive-url=
is missing or is present without an assigned value, |url-status=
(with any or no assigned value) has no meaning so may be deleted|archive-url=
has an assigned value
|url-status=dead
(|archive-url=
links |title=
) may be deleted because that is the default state|url-status=deviated
, |url-status=unfit
, |url-status=usurped
, |url-status=bot: unknown
require inspection of the url at |url=
after which the parameter may be deleted when appropriate|url-status=live
(|url=
links |title=
) should not be deleted unless you are intent on invoking the wrath of other editors.|url-status=live
would be redundant and could be removed. I also thought that IABot was already checking what URL was live or not continuously and wouldn't let us redirect to an archive link if the main URL was still live so it would fix any problems we would do while working with URLs. What you say is completely different from what I supposed. You say that actually |url-status=dead
is what would cause redundancy. You also say that IABot allows us to switch to archive links even when the URL is still live and that it may be possible to have |url-status=
without |archive-link=
, again something I didn't expect to be possible because of IABot's work. -
Klein Muçi (
talk)
01:06, 12 March 2022 (UTC)
|url-status=live
is redundant when |archive-url=
is omitted or empty so may be (should be) deleted. |url-status=dead
is redundant when |archive-url=
has an assigned value so can be (should be) deleted.|url-access=
; I have not paid attention to its edits except when those edits result in a broken cs1|2 citation template.Template:Lang-grc-x-byzant has been nominated for merging with Template:Lang-grc-x-medieval. You are invited to comment on the discussion at the template's entry on the Templates for discussion page. Thank you. — Mr. Guye ( talk) ( contribs) 18:56, 21 March 2022 (UTC)
Hi, Trappist. Thank you for effecting some cite repair with your edit today to Bergenline Avenue. I do have a couple of questions, though: 1. Is there a specific guideline or MOS to follow that indicates when a dead link should be indicated in a citation's parameter, and when it should be in a separate tag with curly brackets? 2. My observation has been that when information originates with one source, but is re-published by a second one, and that second one is the one cited in an WP article, that the parameter "via" is used for the second one. You changed this to "agency" and "publisher." Again, is there is particular guideline or MOS that requires this change? Thanks again. Nightscream ( talk) 15:41, 22 March 2022 (UTC)
{{cite web|author=Wayne Parry|publisher=[[Associated Press]] |via=[[San Francisco Chronicle]]|url=http://www.sfgate.com/cgi-bin/article.cgi?f=/n/a/2005/12/08/national/w081305S21.DTL|title=Menendez Inspires Pride in Cuban-Americans|language=en-US|url-status=dead|date=December 8, 2005}}
{{
cite web}}
: CS1 maint: url-status (
link)|url-status=dead
is meaningless when |archive-url=
is empty or omitted. Because there is no |archive-url=
, |url-status=dead
contributes nothing so no one knows that the url in |url=
is dead. The parameter's documentation is
here. {{
dead link}}
adds visible notification and categorization; neither of those things are within the |url-status=
remit.|author=
– or appropriate alias(es) – would apply. Since the 'article' came from a news agency, the name of the agency goes in |agency=
. The parameter's documentation is
here. The deliverer (in this case
http://www.sfgate.com) is not different from the publisher (sfgate is the publisher's website) so |via=
does not apply. The parameter's documentation is
here.{{
cite news}}
because the source is a newspaper article.Hi, please see talk page, grateful for your view as a former contributor to this page. Regards, Springnuts ( talk) 09:28, 23 March 2022 (UTC)
Hi Trappist the monk, in this automated , the bot script has replaced the correct IUCN status ("Critically Endangered (Possibly Extinct)" with a simplified version ("Critically Endangered") that results in the "possibly extinct" text being removed from the taxobox.
The source for this info should be taken from the Assessment Information para of the IUCN Red List entry and not the abstract at the top. I am sure that there are many other instances of this change that will now also have to be corrected. 'Cheers, Loopy30 ( talk) 12:17, 23 March 2022 (UTC)
PE
is not a category in either of IUCN2.3 or IUCN3.1. The bot calls the IUCN API with Hemignathus affinis which returns this:
{"name":"hemignathus affinis","result":[{"taxonid":103823664,"scientific_name":"Hemignathus affinis","kingdom":"ANIMALIA","phylum":"CHORDATA","class":"AVES","order":"PASSERIFORMES","family":"FRINGILLIDAE","genus":"Hemignathus","main_common_name":"Maui Nukupuu","authority":"Rothschild, 1893","published_year":2016,"assessment_date":"2016-10-01","category":"CR","criteria":"D","population_trend":"Unknown","marine_system":false,"freshwater_system":false,"terrestrial_system":true,"assessor":"BirdLife International","reviewer":"Butchart, S.H.M. & Symes, A.","aoo_km2":null,"eoo_km2":"22","elevation_upper":2000,"elevation_lower":1000,"depth_upper":null,"depth_lower":null,"errata_flag":null,"errata_reason":null,"amended_flag":null,"amended_reason":null}]}
"category":"CR"
which is what the bot used to replace PE
. Also there is "criteria":"D"
. I have not been able to find anywhere that says that criterion D is defined as 'possibly extinct'. Yes, the phrase 'possibly extinct' appears in the
API's assessment narrative but that is a wholly unstructured wall of text so the bot does not attempt to parse any meaning from it.PE
, the bot will change accordingly. At
this edit, Editor
Dysmorodrepanis~enwiki (apparently no longer with us) predicted that CR (PE) is likely to be adopted by other authorities including the IUCN in the near future.After 15+ years, I'm not going to hold my breath for that. At Wikipedia:Conservation status § Special Wikipedia categories, 'we' (en.wiki) assert that CR (PE) is a special wikipedia category. If that is true then
|status_system=
in {{
speciesbox}}
and {{
taxobox}}
etc should have support for 'our' special wikipedia category so that we don't imply that IUCN have a category that they don't actually support.While the substantive debate should happen on HT:CS1, can you help me understand why err_bad_qid has an errant semicolon in Module:Citation/CS1/testcases/identifiers? int21h ( talk · contribs · email) 16:53, 24 March 2022 (UTC)
err_bad_qid has an errant semicolon? The string 'err_bad_qid' does not appear in Module:Citation/CS1/testcases/identifiers. If you mean the semicolon between error messages in this (from Module talk:Citation/CS1/testcases/identifiers):
{{cite journal/new |title=Title |q=Q}}
{{
cite journal}}
: Cite journal requires |journal=
(
help); Unknown parameter |q=
ignored (
help)|journal=
with an assigned value.You added this comment:
"move this table to Module:Canada NTS/data; rvalues without wikimarkup; load table with mw.loadData()"
I do not know what "rvalues without wikimarkup" means. I want these names wiki-marked-up because I want them to be outputted as links to relevant articles. If Wikidata can be used for this, I would like to be able to do that instead.
-- Denelson 83 22:16, 27 March 2022 (UTC)
"1K13" = "St. Mary's Bay, Newfoundland and Labrador|St. Mary's Bay",
"1K13" = {"St. Mary's Bay, Newfoundland and Labrador", "St. Mary's Bay"},
if titleargs_t1][2]] then
return string.format ('[[%s|%s]]', titleargs_t1][1]], titleargs_t1][2]]);
else
return string.format ('[[%s]]', titleargs_t1]]);
end
article_name_from_qid_get()
to
Module:Canada NTS which will return the local wiki's article name."1K13" = {"Q2879512", "St. Mary's Bay"}, -- St. Mary's Bay, Newfoundland and Labrador
Hello, Trappist! How have you been?
I was wondering something about regex and I thought I could spare myself some hours of research if I asked you, given that you've helped me in the past with many regular expressions.
Is there an elegant way to have a regex that can catch catfishbag, fishcatbag, bagfishcat and all the possible variations + those words individually (cat, fish, bag)? I was thinking maybe somehow utilizing capture groups... maybe... - Klein Muçi ( talk) 15:12, 1 April 2022 (UTC)
\b(fish|bag|cat|catfish|catbag|bagcat|bagfish|fishbag|fishcat|catfishbag|catbagfish|bagcatfish|bagfishcat|fishbagcat|fishcatbag)\b
I am trying to modify the grid function so that it outputs one of four different things, depending on if specific strings exist in the arguments passed to the module from #invoke.
Say the output is "30M11", without any additional arguments from #invoke.
If the string "area" is found in the arguments in #invoke, e.g.,
{{#invoke:Canada NTS|grid|lat=43.6426|lon=79.3871|area}}
then the output should be "30M".
If the string "link" is found in the arguments in #invoke, e.g.,
{{#invoke:Canada NTS|grid|lat=43.6426|lon=79.3871|link}}
then the output should be "[https://maps.canada.ca/czs/index-en.html?bbox=-79.5,43.5,-79,43.75&name=NTS_map_sheet_30M11 30M11]".
But if both "link" and "area" are found as separate arguments in #invoke, e.g.,
{{#invoke:Canada NTS|grid|lat=43.6426|lon=79.3871|link|area}}
then the output should be "[https://maps.canada.ca/czs/index-en.html?bbox=-80,43,-78,44&name=NTS_map_sheet_30M 30M]".
I have already added code to the grid function to calculate the figures in the "bbox=" argument in the hyperlink, now I just need to have the argument-reading routine modified to look for the arguments "area" and "link", however I have not been able to figure this out.
-- Denelson 83 03:54, 7 April 2022 (UTC)
{{#invoke:Canada NTS|grid|lat=43.6426|lon=79.3871}}
→ 30M11{{#invoke:Canada NTS|grid|lat=43.6426|lon=79.3871|area}}
→ invalid NTS series input{{#invoke:Canada NTS|grid|lat=43.6426|lon=79.3871|link}}
→ invalid NTS series input{{#invoke:Canada NTS|grid|lat=43.6426|lon=79.3871|link|area}}
→ invalid NTS series input{{#invoke:Canada NTS|grid|lat=43.6426|lon=79.3871|name}}
→ invalid NTS series input{{#invoke:Canada NTS|grid|lat=43.6426|lon=79.3871|name|area}}
→ invalid NTS series input{{#invoke:Canada NTS|grid|lat=43.6426|lon=79.3871|name|link}}
→ invalid NTS series input{{#invoke:Canada NTS|grid|lat=43.6426|lon=79.3871|name|link|area}}
→ invalid NTS series inputPerfect! Thanks. That merges in the functionality from {{ Canada NTS Map Sheet}}, which means that template can now be tweaked to use this module instead. -- 19:44, 7 April 2022 (UTC)
|blank1_info={{Canada NTS Map Sheet|25|N|10}}
|lat=
/ |lon=
are not provided in the template call) fetches them from wikidata. Sure, one can do this:
{{Canada NTS Map Sheet|lat=63.650|lon=68.517}}
→
25N10
Hill Island|{{{1}}}|{{{2}}}|{{{3}}}
– {{{3}}}
optional|nts=
|lat=
/ |lon=
area
, link
, name
to named parameters |area=
, |link=
, |name=
which all take the single value yes
. This much simplifies handling of the positional series
, area
, sheet
which are now the only positional parameters that will be supported.series
, area
, sheet
are provided, there is no lat/lon so the module can't calculate a bounding box. Leaving the bounding-box query string empty or omitting it entirely doesn't zoom the map to the desired location. Is there a url that works without a bounding box?extents_from_grid()
to account for missing {{{3}}}
(sheet) and made the same tweak in the event that there is also missing {{{2}}}
(area). Is there any reason to support something like {{
Canada NTS Map Sheet|25}}
?The administrator policy has been updated with new activity requirements following a successful Request for Comment.
Beginning January 1, 2023, administrators who meet one or both of the following criteria may be desysopped for inactivity if they have:
Administrators at risk for being desysopped under these criteria will continue to be notified ahead of time. Thank you for your continued work.
22:53, 15 April 2022 (UTC)
Hi, I was just cleaning up Special:WantedTemplates and found one of your pages. Would it be possible to fix this? Thanks! Plastikspork ―Œ(talk) 16:57, 16 April 2022 (UTC)
Thanks, you trashed an hour and a half of editing. You didn't have to delete it, that section was much more practical and quick to understand, and there is no need to search class by class or ship by ship when there is already a section especially that already shows the ships in service in the navy. Gianlucca Cetraro ( talk) 14:09, 19 April 2022 (UTC)
constantly updated by adding new ships or removing them. There is no need to double that maintenance effort by keeping a list of current ships in the United States Navy article.
Hi Trappist, I was wondering why the 'url=usurped' entries in cites are flagged as CS1 errors. What's the intended action? Neils51 ( talk) 14:04, 20 April 2022 (UTC)
|url-access=usurped
causing "CS1 errors"? That should not be happening. |url-access=usurped
does emit a cs1 maintenance message:
|url-status=usurped
emitting the maint message (per your example). Per documentation
here the use of|url-status=usurped
is quite valid so why the CS1 maint message? A maint message of this type implies that there is an action that may be taken to suppress the message? With all other CS1 maint messages, AFAIK, there are actions that may be taken to resolve an error in the markup. Sometimes cites with a |url-status=usurped
actually have the URL returning a 404 and the status may then be flagged as 'dead' however it's a subset.
Neils51 (
talk)
11:58, 21 April 2022 (UTC)
{{cite book |title=Title |url=//example.com |archive-url=//archive.org |archive-date=2022-04-20 |url-status=usurped}}
{{cite book |title=Title |url=//example.com |archive-url=//archive.org |archive-date=2022-04-20}}
Hi. I believe the India Today magazine URLs start with a /magazine/ slug like this one https://www.indiatoday.in/magazine/cover-story/story/20220425-inflation-crisis-of-prices-1937525-2022-04-15 and the normal news website articles doesn't https://www.indiatoday.in/sports/ipl-2022/story/lsg-vs-rcb-ipl-match-31-live-score-lucknow-bangalore-updates-virat-kohli-kl-rahul-1939385-2022-04-19 — DaxServer ( t · m · c) 13:55, 19 April 2022 (UTC)
{{
cite sports}}
template so that we can properly cite the /sports/
article linked by your second example url... Nope.Hello, Monk!
There are a 220 categories for sources in different foreign languages. I was able to finally import and localize them all but I'm not sure in my localizations. I have a vague memory of having this discussion before together and you showed me a list to which I would have to check my translations upon to see if they were correct or no. Maybe I'm wrong. I'd be grateful for any kind of help you can provide in this aspect. - Klein Muçi ( talk) 12:54, 27 April 2022 (UTC)
Follow up question: Can you tell me how many kinds of English-es are there and what are their respective codes? You obviously don't call them "foreign languages" here so I'm not sure where to find that kind of information. I believe English variations are all what's missing from the 220 entries list currently, no? - Klein Muçi ( talk) 12:59, 27 April 2022 (UTC)
ang
: Old Englishen
: Englishenm
: Middle Englishen-au
: Australian Englishen-ca
: Canadian Englishen-gb
: British Englishen-us
: American Englishjam
: Jamaican Creole Englishsimple
: Simple EnglishIf you don't like location, great, but you are now removing an identifier--just a page number isn't sufficient, thanks. Caro7200 ( talk) 18:32, 3 May 2022 (UTC)
{{cite news |last1=Strauss |first1=Neil |title=ROCK REVIEW; Evidence of Mick Jagger's Influence |work=The New York Times |date=3 Sep 1994 |location=1 |page=15}}
|location=1
is meaningless. |location=
is a parameter that holds the geographical location (city) of the publisher – generally not used in {{
cite news}}
except to disambiguate similarly named newspapers. Because that 1
is just that, a '1', without any sort of context and because '1' is not a geographical location, I deleted it. If I have to guess at the meaning of something some editor drops into a cs1|2 template parameter, readers will also have to guess and that is a disservice to them on our part. Better to remove anything that requires readers to guess the meaning.{{cite news |last1=Strauss |first1=Neil |title=ROCK REVIEW; Evidence of Mick Jagger's Influence |newspaper=The New York Times |date=3 September 1994 |at=Section 1, p. 15 |url=https://www.nytimes.com/1994/09/03/arts/rock-review-evidence-of-mick-jagger-s-influence.html |url-access=subscription}}
{{cite news |last1=Strauss |first1=Neil |title=ROCK REVIEW; Evidence of Mick Jagger's Influence |newspaper=The New York Times |date=3 September 1994 |department=Section 1 |page=15 |url=https://www.nytimes.com/1994/09/03/arts/rock-review-evidence-of-mick-jagger-s-influence.html |url-access=subscription}}
{{
cite news}}
supports |location=
for disambiguation. Consider
The Times. There is the UK newspaper, the same title in South Africa, in Chicago, etc. To cite an article in one of the lesser-known newspapers, it is a good idea to say which one so:
{{cite news |title=Article Title |newspaper=The Times |location=Chicago}}
most newspapers have their city in their title; many do, sure, but many do not.
litigateany of this → Help talk:Citation Style 1.
I noticed this diff you made for a citation to a Canadian census. I am concerned that essential data has been removed. The place "Lisgar, Manitoba, Sub-district 14, Rural Township 4" is required information for anyone who wishes to search for the original census data in the archives. Why was it removed? Likewise, "publication-place= Library and Archives Canada" is essential for any research to know where to access the data. Why was it removed? Your response may affect hundreds of articles which I have edited, hence why I asked here, instead of at the Mary Dunn article. Thanks. Flibirigit ( talk) 15:28, 12 May 2022 (UTC)
|place=
which causes
Module:Citation/CS1 to put the article in
Category:CS1 maint: location:
{{Citation|title=[[1911 Canadian Census]]|date=June 1, 1911|last=Mowbray|first=G. E.|place=Lisgar, Manitoba, Sub-district 14, Rural Township 4|publisher=[[Government of Canada]]|publication-place=[[Library and Archives Canada]]|page=24}}
{{
citation}}
: CS1 maint: location (
link)|location=
, |place=
and |publication-place=
are expected to hold geographical locations. In this example template, |place=
and |publication-place=
are misused; see
Template:Citation § Publisher.|publisher=[[Government of Canada]]
is not at |publication-place=[[Library and Archives Canada]]
. When |publication-place=
has an assigned value, |location=
or |place=
gets the news-story's dateline. |title=[[1911 Canadian Census]]
is not a news story so |place=
should not be used.|place=
or |location=
with |publication-place=
will be withdrawn because datelines are not critical to locating a news source. These three parameters will become simple aliases of each other with |location=
as the canonical name.{{citation |last=Mowbray |first=G. E. |date=June 1, 1911 |url= |title=1911 Canadian Census: Lisgar, Manitoba |website=[[Library and Archives Canada]]}}
|url=
parameter with the url of the census facsimile.|publisher=[[Dominion Bureau of Statistics]]
. Will its inclusion help readers locate a copy of the source? If yes, include it; if maybe, then maybe include it; if not, don't include it.|location=
or |place=
and/or |publication-place=
. Of all of those cs1|2 templates, there a 5,981 articles listed in
Category:CS1 maint: location. I suspect that it is very unlikely that something like |location=Edenburg, Aberdeen No. 373, Saskatchewan
would ever legitimately appear in a valid cs1|2 template. Instead, something like |location=Edenburg, Saskatchewan
or |location=Edenburg, SK
would be used.Hi there! I am not sure if this is how I start a "talk" or discussion with your user, but I just wanted to thank you for fixing this citation problem on the page I am currently editing (Islamic Uprising in Syria). I am working on it as part of my University Research work and my deadline is very close so I am not 100% diligent or fast with it, so thank you very much! — Preceding unsigned comment added by KAD2223 ( talk • contribs) 16:26, 26 May 2022 (UTC)
Hello! Can you help me locate a help page that depicts the styling conventions used for inline citations? Matters such as how to act when there are commas or periods close to the text that is being referenced, where exactly to put the ref tag, etc. I remember I've read such rules before somewhere but can't be sure where. - Klein Muçi ( talk) 15:45, 29 May 2022 (UTC)
As in the above example, citation markers are normally placed after adjacent punctuation such as periods (full stops) and commas. For exceptions, see the WP:Manual of Style § Punctuation and footnotes. Note also that no space is added before the citation marker. Citations should not be placed within, or on the same line as, section headings.
{{
User box}}
).Take a look at this edit and the edits that have come recently before it.
Take a look at this regex line:
(r"(\{\{\s*cit[aeio][^\}]*\|\s*gjuh[aeë]\s*=\s*)", r"\1language=")
Is there something in it that may have caused such a behavior? I noticed it completely randomly. The line appears to work as intended on Regex101 so I'm not sure if it the one guilty for that edit or not. I fixed it manually but I got curios and thought I could benefit from your experience. - Klein Muçi ( talk) 01:46, 3 June 2022 (UTC)
\1
capture? What are you really trying to do with this regex? Are you attempting to normalize the spelling of gjuha/gjuhe/gjuhë? If so then, perhaps something like this:
(r"(\{\{\s*cit[aeio][^\}]*\|\s*)gjuh[aeë](\s*=\s*)", r"\1Gjuha\2")
|Gjuha = language=en
so, yeah, you have written the regex wrong. Try this:
(r"(\{\{\s*cit[aeio][^\}]*\|\s*)gjuh[aeë](\s*=\s*)", r"\1language\2")
{{
cite web}}
: Check date values in: |access-date=
and |archive-date=
(
help); More than one of |accessdate=
and |access-date=
specified (
help); More than one of |archivedate=
and |archive-date=
specified (
help); More than one of |archiveurl=
and |archive-url=
specified (
help); Unknown parameter |Gjuha=
ignored (
help); Unknown parameter |accesso=
ignored (|access-date=
suggested) (
help)|produkti_brendshëm_bruto=
, anything assigned to that bogus parameter is not displayed.Template:Cite DMM has been nominated for deletion. You are invited to comment on the discussion at the entry on the Templates for discussion page. Beeswaxcandle ( talk) 00:34, 4 June 2022 (UTC)
Hi i noticed that you undid my revision in barisal page i would like to say barisal does not have its own dialect — Preceding unsigned comment added by 99.237.17.126 ( talk) 18:09, 12 June 2022 (UTC)
</ref>{{cite web|url=https://www.britannica.com/place/Barisal|archive-url=https://www.britannica.com/place/Bangladesh|url-status=alive|archive-date=2014-11-13|title=Bangladesh Bureau of Statistics Region Census 2011 page 30|publisher=Bangladesh Bureau of Statistics|access-date=2022-06-12}}</ref>
{{
cite web}}
: Invalid |url-status=alive
(
help)</ref>https://www.britannica.com/place/Bangladesh
is not an archive snapshot of https://www.britannica.com/place/Barisal
; alive
is not a value supported by |url-status=
; because |archive-url=
does not hold the url of a legitimate archive snapshot, |archive-date=2014-11-13
is completely bogus; the title of the Britanica article is "Barisal", not "Bangladesh Bureau of Statistics Region Census 2011 page 30"; Bangladesh Bureau of Statistics
is not the publisher of Britannica; References are properly wrapped with <ref>...</ref>
tags not </ref>...</ref>
tags.<ref name="Barishal District - barisal.gov.bd">{{cite web|url=http://www.barisal.gov.bd/en|archive-url=http://www.barisal.gov.bd/en|url-status=dead|archive-date=2014-11-13|title=
Barishal District|publisher=Bangladesh National Portal
|access-date=2022-06-12}}</ref>
References
{{
cite web}}
: Check |archive-url=
value (
help)CS1 maint: url-status (
link)
|archive-url=
cannot hold the same value as |url=
– a url cannot be an archive snapshot of itself;
http://www.barisal.gov.bd/en is live so |url-status=dead
is incorrect; |archive-date=2014-11-13
is still bogus. I looked at the source: with the exception of a language selector drop-down box in the upper right corner, there is no mention of languages (Bengali or English) or dialects (any) nor any statement about who speaks whatever languages are used in Barisal or Barishal. I presume that you want to use this source to support the three (not four) remaining bullet points in
Barisal § Languages. If that is the case, you might want to find a better source because this source appears to be inadequate.In Special:Diff/1093331531 on Neil Gaiman you removed the titles from several twitter-linked references as "parameter misuse". However, that caused citation errors: "{{ cite web}}: Missing or empty |title= (help)". Perhaps you could come up with replacement titles instead of just breaking the citations? — David Eppstein ( talk) 23:25, 15 June 2022 (UTC)
that caused citation errors:External link in
|title=
; (
which see).Just wanted to say hello wishing you'll have a good time in summer (assuming it is summer soon where you live). Thank you for all the times you've helped around! :) - Klein Muçi ( talk) 18:19, 20 June 2022 (UTC)
Hello! Can you help me understand why the my-my regex is failing in this edit?
(r"(\{\{\s*cit[aeio][^\}]*\|\s*(?:access\-?|archive\-?|doi\-broken\-|lay\-|pmc\-embargo\-|publication\-|air\-?)?date\s*=\s*)October +(\d{4}) +[\-–] +April +(\d{4})", r"\1 tetor \2 – prill \3"),
This is the corresponding regex if I'm not wrong.
PS: Search for date=October 1836 - April 1837 - Klein Muçi ( talk) 10:42, 24 June 2022 (UTC)
|date=April 1826
→ |date=prill 1826
. If smallem applies the my
regex before it applies the my-my
regex, my
probably changed |date=October 1836 - April 1837
to |date=tetor 1836 - April 1837
. If it did that, the my-my
regex will not work. Order matters: regexes must be organized most-complex-to-least-complex.dmy
becomes dmv
in Albanian. -
Klein Muçi (
talk)
12:13, 24 June 2022 (UTC)
dmv-dmv
mdv-mdv
dm-dmv
md-mdv
md-dv
mv-mv
m-mv
d-dmv
dmv
mdv
mv
Sv-v
Sv4-v2
vmd
vmd
. :/What's wrong in here? (Ref 25) - Klein Muçi ( talk) 12:12, 25 June 2022 (UTC)
The update is finally complete for us. I had some points I wanted to mention in the end which may or may not require an answer.
First of all, thank you for your patience and dedication. You have been helping me personally and us as a community for years now.
Secondly, when we started the update this time, we talked about taking notes that could be added in a help page here in regard to that. If you'd please take another look at the link of my sandbox above, you'll see that its content is "precisely" that. Those are the changes that SqWiki needs to do: Add the code for the missing language parameter category in main, translate 1 line in ~/COinS, switch 3 lines to "True" in ~/Configuration, Exports section and add the code for the d.m.y date format in ~/Date validation (this will be the hardest to achieve during each update when compared with the other 3 changes). Beside that, everything else is copy-pasting. At least, so far. Should I add these notes somewhere? How exactly do I add them? Have we chosen a certain "style" about adding directions? Can I just say what I just said here (copy-paste + these 4 changes + localization at ~/Configuration)?
Speaking of that page, where exactly is that page? I've forgotten its name. And, have there been any more changes in regard to the info table we were setting up some days ago?
And lastly, returning to the date subject, I sure hope we can provide better automatic date formatting by the Mediawiki side in the future. I believe that would help make the CS1 code more elegant in general, remove the need for "local quirky code", like we just added for d.m.y, and also make Smallem's life easier overall. I'd be willing to make some active attempts to help in this direction (as I tried by locating all the date formatting related files in Mediawiki) but I don't know who/where exactly to ask for what. If you can provide any more insight on this problem whatsoever, I'd be interested in knowing.
To end it, I do have 2 other naive questions: When we talked about Smallem's latest regexes there was a moment when you said that you had a vague memory of me saying to you that coupling different parameters together wasn't good for a specific reason. I did couple them (as you saw) and, as I said above, it worked fine. But right after the first edit was made I remembered what that "bad thing" might have been: Take a look at Smallem's contributions and see its summaries. You'll see that most of the messages are gigantic and hard to read and that's because the regex lines are the same way. Having said that, I'd still write them coupled because manually writing ~1300 lines was very tiresome and if they weren't coupled the number would have been much bigger, most likely making me drop the task along the way. But given that we currently have the complete list, is there any find and replace command(s) I can apply to it to make it separate (semi)automatically? I believe there isn't. Also, is there any way to make something like this for generating global date regexes? The benefits would be many and diverse but considering all we said above about Mediawiki's date formatting support, I believe even stronger there isn't. - Klein Muçi ( talk) 01:07, 14 February 2022 (UTC)
|accessdate=June 1, 2015
→ |accessdate=1 qershor 2015
but did not change |date=June 1, 2015
so the citation is still marked as Mirëmbajtja CS1: Datë e përkthyer automatikisht.add everything [you] mentioned above as a comment for SqWiki/SqQuote. The table for Module:Citation/CS1 is currently in my sandbox so you can remember what it looks like.
Yes but ... I was looking for.I have no idea what you are talking about...
|edition=illustrated
en-AU
(Australian), en-CA
(Canadian) en-GB
(British), and en-US
(American). Because that abomination that is ve adds IETF-like language tags to |language=
, cs1|2 now accepts those and categorizes accordingly. Other forms of English not recognized by MediaWiki, for example en-IN
(Indian), are recognized only by the language subtag. A better example might be Portuguese. en.wiki has three categories: Brazilian Portuguese (pt-BR
), European Portuguese (pt-PT
), and Portuguese (pt
).|edition=illustrated
is a problem? You should fix this though:
sq:Moduli:Citation/CS1/Configuration#L-37.'local' = 'kopje e arkivuar',
|edition=
accepts anything except something that looks like 'edition' or an abbreviation threreof{{#tag: categorytree|CS1 foreign language sources}}
(at sq.wiki, this: {{#tag: categorytree|Vetitë CS1: Burime në gjuhë të huaj |depth=}}
de-AT
etc is a complexity that I haven't yet felt like dealing with.{{#language:<language tag>|sq}}
(r"(\{\{\s*cit[aeio][^\}]*\|\s*pmc\s*=\s*)pmc(\d*\s*[\|\}])", r"\1\2"),
|pmc=
and |PMC=
are allowed. No guarantee that the assigned value will have pmc
; could be PMC
; could be some combination of cases.(r"(\{\{\s*cit[aeio][^\}]*\|\s*date\s*=\s*.*)-(.*\s*[\|\}])", r"\1–\2"),
(r"(\{\{\s*cit[aeio][^\}]*\|\s*(?:access\-?|archive\-?|doi\-broken\-|lay\-|pmc\-embargo\-|publication\-|air\-?)?date\s*=\s*\d{1,2})\-(\d{1,2} +[A-Za-z]+ +\d{4})", r"\1–\2"),
Also, just found out that we have deprecated the lay parameters. The problem is that I find the deprecation notice unexplanatory enough. What were lay parameters and what was their function? What exactly would mean building a new template for them? Something like {{Cite lay....}}? We don't have a lot articles using them anyway but I don't know what I should do with the information in those parameters. Can I safely remove them or not. - Klein Muçi ( talk) 13:13, 16 February 2022 (UTC)
|lay-date=
, |lay-format=
, |lay-source=
, and |lay-url=
parameters were intended to provide a method of joining a lay source to a specialist source where the lay source is purportedly more easily understood by the general reader. The problem is that the lay source is missing most of the important bibliographic detail that is expected from a proper citation. These parameters are often used as a way to shoehorn two citations into a template designed to properly render one citation at a time. It was a poor design choice that should never have been implemented.<ref>...</ref>
tags or can be bundled with the other cs1|2 template inside the same <ref>...</ref>
tags. I wrote {{
lay source}}
as one possible way to implement this. Here is a
diff from Altruism where I used {{lay source}}
.\d{1,2})\-(\d{1,2} +[A-Za-z]+ +\d{4})
Maybe if you explain to me in details what each of those components serves for it'd be easier for me. I don't understand the what happens with the curly brackets and how the part in square brackets helps in months exactly. -
Klein Muçi (
talk)
15:39, 17 February 2022 (UTC)(\d{1,2})\-(\d{1,2} +[A-Za-z]+ +\d{4})
1-3 something 1234
\1–\2
(r"(\{\{\s*cit[aeio][^\}]*\|\s*(?:access\-?|archive\-?|doi\-broken\-|lay\-|pmc\-embargo\-|publication\-|air\-?)?date\s*=\s*\d{1,2})\-(\d{1,2} +[A-Za-z]+ +\d{4})", r"\1–\2"),
(r"(\{\{\s*cit[aeio][^\}]*\|\s*(?:access\-?|archive\-?|doi\-broken\-|lay\-|pmc\-embargo\-|publication\-|air\-?)?date\s*=\s*\d{1,2} +[A-Za-z])\-(\d{1,2} +[A-Za-z]+ +\d{4})", r"\1–\2"),
(r"(\{\{\s*cit[aeio][^\}]*\|\s*(?:access\-?|archive\-?|doi\-broken\-|lay\-|pmc\-embargo\-|publication\-|air\-?)?date\s*=\s*\d{1,2} +[A-Za-z]+ +\d{4})\-(\d{1,2} +[A-Za-z]+ +\d{4})", r"\1–\2"),
(r"(\{\{\s*cit[aeio][^\}]*\|\s*(?:access\-?|archive\-?|doi\-broken\-|lay\-|pmc\-embargo\-|publication\-|air\-?)?date\s*=\s*[A-Za-z]+ +\d{4})\-([A-Za-z]+ +\d{4})", r"\1–\2"),
(r"(\{\{\s*cit[aeio][^\}]*\|\s*(?:access\-?|archive\-?|doi\-broken\-|lay\-|pmc\-embargo\-|publication\-|air\-?)?date\s*=\s*[A-Za-z])\-([A-Za-z]+ +\d{4})", r"\1–\2"),
[A-Za-z]+
, right? The others are not season-inclusive because there is no format like 17–18 Spring 2022.{{cite book |title=Title |date= December 2021 – January 2022}}
{{cite book |title=Title |date= December 2021–January 2022}}
|gjuha=
to
sq:Moduli:Citation/CS1/Suggestions. I'm less sanguine about adding that parameter here. In the normal course of things, editors who import a cs1|2 template from sq.wiki to en.wiki wouldn't find |gjuha=
in a properly formed template so having |gjuha=
here is just so much clutter.|gjuha=
. It was just because everyday we stray further from EnWiki's light by doing things like this and, of course, this increases maintenance cost (and shatters my dream of a global CS1 a bit more).{{Cite book|last=Sally Neaum|url={{google books|plainurl=yes|id=fCnZNAEACAAJ}}|title=Child Development for Early Years Students and Practitioners|date=17 May 2013|publisher=SAGE Publications|isbn=978-1-4462-6753-0}}
{{
google books}}
template, it never sees |date=17 May 2013
so Arsimi parafillor will remain in Kategoria:Mirëmbajtja CS1: Datë e përkthyer automatikisht until manually fixed.|year=14 May 1724
. Why such a precise date for such an old book? The fix for |year=
masquerading as |date=
is to create a series of regexes that look for non-year date patterns in |year=
and change |year=
to |date=
. Do this before date translation. For dMy:
(r"(\{\{\s*cit[aeio][^\}]*\|\s*)year(\s*=\s*\d{1,2} +[A-Za-z]+ +\d{4})", r"\1date\2"),
|year=
masquerading as |date=
though I have periodically thought that we should at least have a maint cat for those parameters.I have this regex for fixing case problems with pmc/mr/jfm parameters:
(r"(\{\{\s*cit[aeio][^\}]*\|\s*(?:pmc|mr|jfm)\s*=\s*)(?:pmc|mr|jfm)(\d*\s*[\|\}])", r"\1\2"),
It works fine for its purpose. (Smallem is case insensitive.) However, is there a way to make each parameter pair only with its homologue? I want to know mostly for personal curiosity in regard to further works with regexes in future cases. -
Klein Muçi (
talk)
18:37, 23 February 2022 (UTC)
|pmc=
or |PMC=
. Same for |mr=
, |MR=
, |jfm=
, and |JFM=
.|jfm=
PMCXXXXX or other combinations. I'd like it to work only on the case pmc=pmcXXXX or jfm=jfmXXXX or mr=mrXXXXX. So each parameters only pairs with its homologue. Is it clearer now? -
Klein Muçi (
talk)
22:58, 23 February 2022 (UTC)
|date=
could be more appropriate than |year=
.
(r"(\{\{\s*cit[aeio][^\}]*\|\s*)year(\s*=\s*\d{1,2} +[A-Za-z]+ +\d{4})", r"\1date\2"),
(r"(\{\{\s*cit[aeio][^\}]*\|\s*)year(\s*=\s*\d{1,2}\-d{1,2} +[A-Za-z]+ +\d{4})", r"\1date\2"),
(r"(\{\{\s*cit[aeio][^\}]*\|\s*)year(\s*=\s*[A-Za-z]+ +\d{4})", r"\1date\2"),
(r"(\{\{\s*cit[aeio][^\}]*\|\s*)year(\s*=\s*[A-Za-z]\-[A-Za-z]+ +\d{4})", r"\1date\2"),
(r"(\{\{\s*cit[aeio][^\}]*\|\s*)year(\s*=\s*\d{1,2} +[A-Za-z]\-d{1,2} +[A-Za-z]+ +\d{4})", r"\1date\2"),
(r"(\{\{\s*cit[aeio][^\}]*\|\s*)year(\s*=\s*[A-Za-z]+ +\d{4}\-[A-Za-z]+ +\d{4})", r"\1date\2"),
(r"(\{\{\s*cit[aeio][^\}]*\|\s*)year(\s*=\s*\d{1,2} +[A-Za-z]+ +\d{4}\-d{1,2} +[A-Za-z]+ +\d{4})", r"\1date\2"),
(r"(\{\{\s*cit[aeio][^\}]*\|\s*)year(\s*=\s*[A-Za-z]+ +\d{4}\-\d{4})", r"\1date\2"),
(r"(\{\{\s*cit[aeio][^\}]*\|\s*)year(\s*=\s*[A-Za-z]+ +\d{4}\-\d{2})", r"\1date\2"),
|year=
.\n
, \r
, \t
for LF, CR, and HT should work but the others require encoding. I think that this works: \u00A0
(NBSP), \u200A
(HSP), \u00AD
(SHY) but no guarantees. There are a rare handful of other unicode characters that can just be deleted:
(r"(\{\{\s*cit[aeio][^\}]*\|)U+0009([\|\}])", r"\1 \2"),
U+0009
part should be written differently but I'm wondering about the overall syntax. -
Klein Muçi (
talk)
22:59, 26 February 2022 (UTC)
{{cite book |title=Title with tab character}}
(r"(\{\{\s*cit[aeio][^\}]*)((?:\u0080|\u0081|\u0085|\u0093|\u0094|\u0096|\u0098|\u0099|\u009C|\u009E))", r"\1"),
(r"(\{\{\s*cit[aeio][^\}]*)((?:\u0009|\u000A|\u000D|\u00A0|\u200A))", r"\1 "),
(r"(\{\{\s*cit[aeio][^\}]*)(\u00AD)", r"\1-"),
What do you think? - Klein Muçi ( talk) 01:12, 27 February 2022 (UTC)
I kinda think I've designed them wrongly even though the case you gave me worked as intended. - Klein Muçi ( talk) 01:16, 27 February 2022 (UTC)
#>A
. Click that and the digits are converted to the character. Copy and paste.In the DYK nomination of
Samuel Loudon it is shown as Gwillhickers and I as co-creators. Can you look at the DYK Template to see that this is set correctly, that when the nomination is promoted and Gwillhickers gets a DYK credit, that I also automatically get one also. Thanks.--
Doug Coldwell (
talk)
18:07, 27 February 2022 (UTC)
{{Template:Did you know nominations/Samuel Loudon (printer)}}
I have never had anything to do with dykso I am not an expert. I know nothing so it would be better were you to ask at WT:DYK or some other appropriate venue where you would be talking to someone who knows something.
Maybe not the right place to ask but I was thinking... Can't IABot solve the problems with the aforementioned maint categories? Has there ever been a discussion with its maintainers of this sort you're aware of? - Klein Muçi ( talk) 01:18, 28 February 2022 (UTC)
|title=Archived copy
has almost entirely been filled by IABot. There are others that are doing that now also because it is a uniformly common name that cs1|2 is configured to track. Alas, only in a maint cat so almost no one sees these messages which is why I would like to figure out how to trickle-convert them to error messages.|url-status=live
and |url-status=dead
in the absence of |archive-url=
is mere clutter so we track that. Editor
Rlink2 using some sort of automated or semi automated tool to add |archive-url=
to these cs1|2 templates; see
Special:Contributions/Rlink2.|title=Archived copy
→ IABot finds ways to actually find the correct title → IABot corrects the old mistakes.The reason I insist on this is because IABot is already global and any solutions it is able to bring will also be global,If multiple wikis like the services the bot provides there could be a seperate global bot created to supplement IAbot in archiving and citation matters like this one. Rlink2 ( talk) 19:28, 28 February 2022 (UTC)
You are aware of what Smallem is doing with the spaces. Take a look at this diff. It's a normal one but doesn't the highlighting look strange or confusing to you? Or is it just me that I'm not used with these kinds of diffs? I was wondering if I should report it somewhere as a "failure" or an edge case where it starts breaking. - Klein Muçi ( talk) 10:03, 1 March 2022 (UTC)
This page and this page behave differently. Is that normal? Any idea why? - Klein Muçi ( talk) 02:53, 2 March 2022 (UTC)
The IANA language-subtag-registry file got updated yesterday. Can you rerun the script to update all the data modules? Thank you! Robin van der Vliet (talk) (contribs) 08:35, 3 March 2022 (UTC)
These were facts that I’ve put there, because I’ve been reading accurate history of Blackbeard by the historian Baylus Brooks. The information that you have redone is completely fake, not real at all. Blackbeard's forename, and surname is already known, which is "Edward Thache". Kennythenuker ( talk) 17:57, 5 March 2022 (UTC)
Sorry, I didn’t mean to be a little rude about, I didn’t know that Wikipedia doesn’t care about the truth. My apologies. Kennythenuker ( talk) 18:09, 5 March 2022 (UTC)
I’m sorry for not realizing about what Wikipedia is all about. I appreciate you being honest about it. People make mistakes. No hard feelings! :) Kennythenuker ( talk) 18:38, 5 March 2022 (UTC)
|year=3 March 2022
→ [Smallem helps] → |date=3 March 2022
;|last=Klein Muçi
(actually first + last) Can/Should we do a similar thing like in the case of the "pseudo-maint cat" above and convert these cases to author? I doubt we can provide auto-detection somehow, right? -
Klein Muçi (
talk)
12:46, 6 March 2022 (UTC)|first=
and if found skip. It becomes more complex because these parameters can be enumerated so, unless there were a dire need to do it, I wouldn't.|last=
with a correct last name value while missing the first name value and that shouldn't be converted to |author=
ideally. But I think that would make it impossible right? So the task is more like "convert unmatched |last=
to |author=
", according to what you propose. I'm not sure how dire the need is. I got this idea while manually fixing multiple author names in 1 parameter. What I do is I open the article for edit and search for author= and then skip until I find the one with multiple values and start splitting it. And then I started stumbling upon many articles which didn't have a single author parameter and they still were part of that maint-category. After a while I understood/remembered that author parameters could also be expressed with |last=
and that added a bit of chaos to my method. Not only it introduced a new variable I should be aware of but it also made me search for matching |first=
parameters and values and many times I had to manually switch from |last=
to |author=
because of the reasons explained above and that's when I got the idea. -
Klein Muçi (
talk)
13:22, 6 March 2022 (UTC)Hello, Trappist the monk,
There is a CSD tag SOMEWHERE that is causing Category:Articles containing uncoded-language text to show up as a requested page for speedy deletion. But I can't find the page that was originally CSD tagged. And the category hasn't been emptied yet so it would be a bad idea to delete it. Can you track down the page that has been tagged for deletion and figure out if a mistake has been made? Thanks for any help you can supply. Liz Read! Talk! 23:04, 5 March 2022 (UTC)
Hi, Trappist,
Category:CS1 maint: DOI inactive as of November 2021 showed up as an empty category. Do you expect it to remain empty or is this a periodic emptying of dated categories? Thanks for any help, I'm not sure where to go with this questions about CS1 matters. Liz Read! Talk! 01:05, 9 March 2022 (UTC)
|doi-broken-date=November 2021
to a cs1|2 template but that is no reason to keep the category once it has been emptied. I notice that you deleted the categories for June–September 2021. What is different about this one?|doi-broken-date=
so that we don't have a list of categories dating back to the dawn of wikipedia which must be why there are only six subcats in
Category:CS1 maint: DOI inactive.|doi-broken-date=
parameters so it may be that most of the time there is no reason to create a category that will never be used. Here, editors commonly add |doi-broken-date=
parameters so a new category is created every month, someone or something empties older categories which are then deleted. The emptying process may be an automated tool that attempts to follow the doi. When the tool fails to find the source, it updates |doi-broken-date=
to the current month. I suspect that that is
User:Citation bot but don't know for sure.Keeping up with peculiar global needs in regard to CS1, can we create some error categories about sources missing |trans-title/chapter/etc.(?)=
when |language=
differs from the local one? This can either be an universal proposal (pitchforks and torches aside, EnWiki could also benefit from English translated titles/chapters/etc.(?) in foreign sources, especially those that use different scripts), an only-foreign-wikis feature on or a specific request for SqWiki only. -
Klein Muçi (
talk)
03:18, 10 March 2022 (UTC)
|trans-title=
and its companions. The purpose of a citation is to help the reader locate a copy of the source. If the source only has an original-language title, a translation of that title into the local language isn't going to be much help to the reader because whatever translation is provided in |trans-title=
won't be indexed. When the source itself provides a local-language title, that is the only time that |trans-title=
should be used because when it comes to translations, every translator is different; who is to say which translation not done by the source author is the correct translation.|access-date=
, that is, a detail that is added by the editor, not by the official source. Do you have any information how that parameter is utilized here? Do editors make the same mistaken (?) assumption as I do when it comes to it? Is that really a mistake? I'm asking because, as a wiki that has most of its sources in English, we've treated that parameter really serious, going as far as making it one of the standards articles must conform to if they want the status of featured articles, that is, every foreign title must have its translated form. What you're saying above would change all of that. -
Klein Muçi (
talk)
13:06, 10 March 2022 (UTC)
|trans-title=
does provide a small window of contextbut it won't help the reader locate the source unless the translated title is an 'official' title of the source. As far as I can tell, the cs1|2 documentation does not make that suggestion. The documentation describes what an editor is to give it and how the templates display the result:
|title=
into sq |trans-title=
. If an error message, almost every page will bleed red; as much or more than Mungon ose është bosh parametri |language=. If a maint message, then only those who can see maint messages would see the message. Still a damn big category and no automated way to clear it.Straightforward question: Can I just remove on sight any |Url-status=live
assuming I won't break anything and IABot will deal with any needed details? -
Klein Muçi (
talk)
14:10, 11 March 2022 (UTC)
|Url-status=live
is not a known parameter.|url-status=live
, then maybe:
|archive-url=
is missing or is present without an assigned value, |url-status=
(with any or no assigned value) has no meaning so may be deleted|archive-url=
has an assigned value
|url-status=dead
(|archive-url=
links |title=
) may be deleted because that is the default state|url-status=deviated
, |url-status=unfit
, |url-status=usurped
, |url-status=bot: unknown
require inspection of the url at |url=
after which the parameter may be deleted when appropriate|url-status=live
(|url=
links |title=
) should not be deleted unless you are intent on invoking the wrath of other editors.|url-status=live
would be redundant and could be removed. I also thought that IABot was already checking what URL was live or not continuously and wouldn't let us redirect to an archive link if the main URL was still live so it would fix any problems we would do while working with URLs. What you say is completely different from what I supposed. You say that actually |url-status=dead
is what would cause redundancy. You also say that IABot allows us to switch to archive links even when the URL is still live and that it may be possible to have |url-status=
without |archive-link=
, again something I didn't expect to be possible because of IABot's work. -
Klein Muçi (
talk)
01:06, 12 March 2022 (UTC)
|url-status=live
is redundant when |archive-url=
is omitted or empty so may be (should be) deleted. |url-status=dead
is redundant when |archive-url=
has an assigned value so can be (should be) deleted.|url-access=
; I have not paid attention to its edits except when those edits result in a broken cs1|2 citation template.Template:Lang-grc-x-byzant has been nominated for merging with Template:Lang-grc-x-medieval. You are invited to comment on the discussion at the template's entry on the Templates for discussion page. Thank you. — Mr. Guye ( talk) ( contribs) 18:56, 21 March 2022 (UTC)
Hi, Trappist. Thank you for effecting some cite repair with your edit today to Bergenline Avenue. I do have a couple of questions, though: 1. Is there a specific guideline or MOS to follow that indicates when a dead link should be indicated in a citation's parameter, and when it should be in a separate tag with curly brackets? 2. My observation has been that when information originates with one source, but is re-published by a second one, and that second one is the one cited in an WP article, that the parameter "via" is used for the second one. You changed this to "agency" and "publisher." Again, is there is particular guideline or MOS that requires this change? Thanks again. Nightscream ( talk) 15:41, 22 March 2022 (UTC)
{{cite web|author=Wayne Parry|publisher=[[Associated Press]] |via=[[San Francisco Chronicle]]|url=http://www.sfgate.com/cgi-bin/article.cgi?f=/n/a/2005/12/08/national/w081305S21.DTL|title=Menendez Inspires Pride in Cuban-Americans|language=en-US|url-status=dead|date=December 8, 2005}}
{{
cite web}}
: CS1 maint: url-status (
link)|url-status=dead
is meaningless when |archive-url=
is empty or omitted. Because there is no |archive-url=
, |url-status=dead
contributes nothing so no one knows that the url in |url=
is dead. The parameter's documentation is
here. {{
dead link}}
adds visible notification and categorization; neither of those things are within the |url-status=
remit.|author=
– or appropriate alias(es) – would apply. Since the 'article' came from a news agency, the name of the agency goes in |agency=
. The parameter's documentation is
here. The deliverer (in this case
http://www.sfgate.com) is not different from the publisher (sfgate is the publisher's website) so |via=
does not apply. The parameter's documentation is
here.{{
cite news}}
because the source is a newspaper article.Hi, please see talk page, grateful for your view as a former contributor to this page. Regards, Springnuts ( talk) 09:28, 23 March 2022 (UTC)
Hi Trappist the monk, in this automated , the bot script has replaced the correct IUCN status ("Critically Endangered (Possibly Extinct)" with a simplified version ("Critically Endangered") that results in the "possibly extinct" text being removed from the taxobox.
The source for this info should be taken from the Assessment Information para of the IUCN Red List entry and not the abstract at the top. I am sure that there are many other instances of this change that will now also have to be corrected. 'Cheers, Loopy30 ( talk) 12:17, 23 March 2022 (UTC)
PE
is not a category in either of IUCN2.3 or IUCN3.1. The bot calls the IUCN API with Hemignathus affinis which returns this:
{"name":"hemignathus affinis","result":[{"taxonid":103823664,"scientific_name":"Hemignathus affinis","kingdom":"ANIMALIA","phylum":"CHORDATA","class":"AVES","order":"PASSERIFORMES","family":"FRINGILLIDAE","genus":"Hemignathus","main_common_name":"Maui Nukupuu","authority":"Rothschild, 1893","published_year":2016,"assessment_date":"2016-10-01","category":"CR","criteria":"D","population_trend":"Unknown","marine_system":false,"freshwater_system":false,"terrestrial_system":true,"assessor":"BirdLife International","reviewer":"Butchart, S.H.M. & Symes, A.","aoo_km2":null,"eoo_km2":"22","elevation_upper":2000,"elevation_lower":1000,"depth_upper":null,"depth_lower":null,"errata_flag":null,"errata_reason":null,"amended_flag":null,"amended_reason":null}]}
"category":"CR"
which is what the bot used to replace PE
. Also there is "criteria":"D"
. I have not been able to find anywhere that says that criterion D is defined as 'possibly extinct'. Yes, the phrase 'possibly extinct' appears in the
API's assessment narrative but that is a wholly unstructured wall of text so the bot does not attempt to parse any meaning from it.PE
, the bot will change accordingly. At
this edit, Editor
Dysmorodrepanis~enwiki (apparently no longer with us) predicted that CR (PE) is likely to be adopted by other authorities including the IUCN in the near future.After 15+ years, I'm not going to hold my breath for that. At Wikipedia:Conservation status § Special Wikipedia categories, 'we' (en.wiki) assert that CR (PE) is a special wikipedia category. If that is true then
|status_system=
in {{
speciesbox}}
and {{
taxobox}}
etc should have support for 'our' special wikipedia category so that we don't imply that IUCN have a category that they don't actually support.While the substantive debate should happen on HT:CS1, can you help me understand why err_bad_qid has an errant semicolon in Module:Citation/CS1/testcases/identifiers? int21h ( talk · contribs · email) 16:53, 24 March 2022 (UTC)
err_bad_qid has an errant semicolon? The string 'err_bad_qid' does not appear in Module:Citation/CS1/testcases/identifiers. If you mean the semicolon between error messages in this (from Module talk:Citation/CS1/testcases/identifiers):
{{cite journal/new |title=Title |q=Q}}
{{
cite journal}}
: Cite journal requires |journal=
(
help); Unknown parameter |q=
ignored (
help)|journal=
with an assigned value.You added this comment:
"move this table to Module:Canada NTS/data; rvalues without wikimarkup; load table with mw.loadData()"
I do not know what "rvalues without wikimarkup" means. I want these names wiki-marked-up because I want them to be outputted as links to relevant articles. If Wikidata can be used for this, I would like to be able to do that instead.
-- Denelson 83 22:16, 27 March 2022 (UTC)
"1K13" = "St. Mary's Bay, Newfoundland and Labrador|St. Mary's Bay",
"1K13" = {"St. Mary's Bay, Newfoundland and Labrador", "St. Mary's Bay"},
if titleargs_t1][2]] then
return string.format ('[[%s|%s]]', titleargs_t1][1]], titleargs_t1][2]]);
else
return string.format ('[[%s]]', titleargs_t1]]);
end
article_name_from_qid_get()
to
Module:Canada NTS which will return the local wiki's article name."1K13" = {"Q2879512", "St. Mary's Bay"}, -- St. Mary's Bay, Newfoundland and Labrador
Hello, Trappist! How have you been?
I was wondering something about regex and I thought I could spare myself some hours of research if I asked you, given that you've helped me in the past with many regular expressions.
Is there an elegant way to have a regex that can catch catfishbag, fishcatbag, bagfishcat and all the possible variations + those words individually (cat, fish, bag)? I was thinking maybe somehow utilizing capture groups... maybe... - Klein Muçi ( talk) 15:12, 1 April 2022 (UTC)
\b(fish|bag|cat|catfish|catbag|bagcat|bagfish|fishbag|fishcat|catfishbag|catbagfish|bagcatfish|bagfishcat|fishbagcat|fishcatbag)\b
I am trying to modify the grid function so that it outputs one of four different things, depending on if specific strings exist in the arguments passed to the module from #invoke.
Say the output is "30M11", without any additional arguments from #invoke.
If the string "area" is found in the arguments in #invoke, e.g.,
{{#invoke:Canada NTS|grid|lat=43.6426|lon=79.3871|area}}
then the output should be "30M".
If the string "link" is found in the arguments in #invoke, e.g.,
{{#invoke:Canada NTS|grid|lat=43.6426|lon=79.3871|link}}
then the output should be "[https://maps.canada.ca/czs/index-en.html?bbox=-79.5,43.5,-79,43.75&name=NTS_map_sheet_30M11 30M11]".
But if both "link" and "area" are found as separate arguments in #invoke, e.g.,
{{#invoke:Canada NTS|grid|lat=43.6426|lon=79.3871|link|area}}
then the output should be "[https://maps.canada.ca/czs/index-en.html?bbox=-80,43,-78,44&name=NTS_map_sheet_30M 30M]".
I have already added code to the grid function to calculate the figures in the "bbox=" argument in the hyperlink, now I just need to have the argument-reading routine modified to look for the arguments "area" and "link", however I have not been able to figure this out.
-- Denelson 83 03:54, 7 April 2022 (UTC)
{{#invoke:Canada NTS|grid|lat=43.6426|lon=79.3871}}
→ 30M11{{#invoke:Canada NTS|grid|lat=43.6426|lon=79.3871|area}}
→ invalid NTS series input{{#invoke:Canada NTS|grid|lat=43.6426|lon=79.3871|link}}
→ invalid NTS series input{{#invoke:Canada NTS|grid|lat=43.6426|lon=79.3871|link|area}}
→ invalid NTS series input{{#invoke:Canada NTS|grid|lat=43.6426|lon=79.3871|name}}
→ invalid NTS series input{{#invoke:Canada NTS|grid|lat=43.6426|lon=79.3871|name|area}}
→ invalid NTS series input{{#invoke:Canada NTS|grid|lat=43.6426|lon=79.3871|name|link}}
→ invalid NTS series input{{#invoke:Canada NTS|grid|lat=43.6426|lon=79.3871|name|link|area}}
→ invalid NTS series inputPerfect! Thanks. That merges in the functionality from {{ Canada NTS Map Sheet}}, which means that template can now be tweaked to use this module instead. -- 19:44, 7 April 2022 (UTC)
|blank1_info={{Canada NTS Map Sheet|25|N|10}}
|lat=
/ |lon=
are not provided in the template call) fetches them from wikidata. Sure, one can do this:
{{Canada NTS Map Sheet|lat=63.650|lon=68.517}}
→
25N10
Hill Island|{{{1}}}|{{{2}}}|{{{3}}}
– {{{3}}}
optional|nts=
|lat=
/ |lon=
area
, link
, name
to named parameters |area=
, |link=
, |name=
which all take the single value yes
. This much simplifies handling of the positional series
, area
, sheet
which are now the only positional parameters that will be supported.series
, area
, sheet
are provided, there is no lat/lon so the module can't calculate a bounding box. Leaving the bounding-box query string empty or omitting it entirely doesn't zoom the map to the desired location. Is there a url that works without a bounding box?extents_from_grid()
to account for missing {{{3}}}
(sheet) and made the same tweak in the event that there is also missing {{{2}}}
(area). Is there any reason to support something like {{
Canada NTS Map Sheet|25}}
?The administrator policy has been updated with new activity requirements following a successful Request for Comment.
Beginning January 1, 2023, administrators who meet one or both of the following criteria may be desysopped for inactivity if they have:
Administrators at risk for being desysopped under these criteria will continue to be notified ahead of time. Thank you for your continued work.
22:53, 15 April 2022 (UTC)
Hi, I was just cleaning up Special:WantedTemplates and found one of your pages. Would it be possible to fix this? Thanks! Plastikspork ―Œ(talk) 16:57, 16 April 2022 (UTC)
Thanks, you trashed an hour and a half of editing. You didn't have to delete it, that section was much more practical and quick to understand, and there is no need to search class by class or ship by ship when there is already a section especially that already shows the ships in service in the navy. Gianlucca Cetraro ( talk) 14:09, 19 April 2022 (UTC)
constantly updated by adding new ships or removing them. There is no need to double that maintenance effort by keeping a list of current ships in the United States Navy article.
Hi Trappist, I was wondering why the 'url=usurped' entries in cites are flagged as CS1 errors. What's the intended action? Neils51 ( talk) 14:04, 20 April 2022 (UTC)
|url-access=usurped
causing "CS1 errors"? That should not be happening. |url-access=usurped
does emit a cs1 maintenance message:
|url-status=usurped
emitting the maint message (per your example). Per documentation
here the use of|url-status=usurped
is quite valid so why the CS1 maint message? A maint message of this type implies that there is an action that may be taken to suppress the message? With all other CS1 maint messages, AFAIK, there are actions that may be taken to resolve an error in the markup. Sometimes cites with a |url-status=usurped
actually have the URL returning a 404 and the status may then be flagged as 'dead' however it's a subset.
Neils51 (
talk)
11:58, 21 April 2022 (UTC)
{{cite book |title=Title |url=//example.com |archive-url=//archive.org |archive-date=2022-04-20 |url-status=usurped}}
{{cite book |title=Title |url=//example.com |archive-url=//archive.org |archive-date=2022-04-20}}
Hi. I believe the India Today magazine URLs start with a /magazine/ slug like this one https://www.indiatoday.in/magazine/cover-story/story/20220425-inflation-crisis-of-prices-1937525-2022-04-15 and the normal news website articles doesn't https://www.indiatoday.in/sports/ipl-2022/story/lsg-vs-rcb-ipl-match-31-live-score-lucknow-bangalore-updates-virat-kohli-kl-rahul-1939385-2022-04-19 — DaxServer ( t · m · c) 13:55, 19 April 2022 (UTC)
{{
cite sports}}
template so that we can properly cite the /sports/
article linked by your second example url... Nope.Hello, Monk!
There are a 220 categories for sources in different foreign languages. I was able to finally import and localize them all but I'm not sure in my localizations. I have a vague memory of having this discussion before together and you showed me a list to which I would have to check my translations upon to see if they were correct or no. Maybe I'm wrong. I'd be grateful for any kind of help you can provide in this aspect. - Klein Muçi ( talk) 12:54, 27 April 2022 (UTC)
Follow up question: Can you tell me how many kinds of English-es are there and what are their respective codes? You obviously don't call them "foreign languages" here so I'm not sure where to find that kind of information. I believe English variations are all what's missing from the 220 entries list currently, no? - Klein Muçi ( talk) 12:59, 27 April 2022 (UTC)
ang
: Old Englishen
: Englishenm
: Middle Englishen-au
: Australian Englishen-ca
: Canadian Englishen-gb
: British Englishen-us
: American Englishjam
: Jamaican Creole Englishsimple
: Simple EnglishIf you don't like location, great, but you are now removing an identifier--just a page number isn't sufficient, thanks. Caro7200 ( talk) 18:32, 3 May 2022 (UTC)
{{cite news |last1=Strauss |first1=Neil |title=ROCK REVIEW; Evidence of Mick Jagger's Influence |work=The New York Times |date=3 Sep 1994 |location=1 |page=15}}
|location=1
is meaningless. |location=
is a parameter that holds the geographical location (city) of the publisher – generally not used in {{
cite news}}
except to disambiguate similarly named newspapers. Because that 1
is just that, a '1', without any sort of context and because '1' is not a geographical location, I deleted it. If I have to guess at the meaning of something some editor drops into a cs1|2 template parameter, readers will also have to guess and that is a disservice to them on our part. Better to remove anything that requires readers to guess the meaning.{{cite news |last1=Strauss |first1=Neil |title=ROCK REVIEW; Evidence of Mick Jagger's Influence |newspaper=The New York Times |date=3 September 1994 |at=Section 1, p. 15 |url=https://www.nytimes.com/1994/09/03/arts/rock-review-evidence-of-mick-jagger-s-influence.html |url-access=subscription}}
{{cite news |last1=Strauss |first1=Neil |title=ROCK REVIEW; Evidence of Mick Jagger's Influence |newspaper=The New York Times |date=3 September 1994 |department=Section 1 |page=15 |url=https://www.nytimes.com/1994/09/03/arts/rock-review-evidence-of-mick-jagger-s-influence.html |url-access=subscription}}
{{
cite news}}
supports |location=
for disambiguation. Consider
The Times. There is the UK newspaper, the same title in South Africa, in Chicago, etc. To cite an article in one of the lesser-known newspapers, it is a good idea to say which one so:
{{cite news |title=Article Title |newspaper=The Times |location=Chicago}}
most newspapers have their city in their title; many do, sure, but many do not.
litigateany of this → Help talk:Citation Style 1.
I noticed this diff you made for a citation to a Canadian census. I am concerned that essential data has been removed. The place "Lisgar, Manitoba, Sub-district 14, Rural Township 4" is required information for anyone who wishes to search for the original census data in the archives. Why was it removed? Likewise, "publication-place= Library and Archives Canada" is essential for any research to know where to access the data. Why was it removed? Your response may affect hundreds of articles which I have edited, hence why I asked here, instead of at the Mary Dunn article. Thanks. Flibirigit ( talk) 15:28, 12 May 2022 (UTC)
|place=
which causes
Module:Citation/CS1 to put the article in
Category:CS1 maint: location:
{{Citation|title=[[1911 Canadian Census]]|date=June 1, 1911|last=Mowbray|first=G. E.|place=Lisgar, Manitoba, Sub-district 14, Rural Township 4|publisher=[[Government of Canada]]|publication-place=[[Library and Archives Canada]]|page=24}}
{{
citation}}
: CS1 maint: location (
link)|location=
, |place=
and |publication-place=
are expected to hold geographical locations. In this example template, |place=
and |publication-place=
are misused; see
Template:Citation § Publisher.|publisher=[[Government of Canada]]
is not at |publication-place=[[Library and Archives Canada]]
. When |publication-place=
has an assigned value, |location=
or |place=
gets the news-story's dateline. |title=[[1911 Canadian Census]]
is not a news story so |place=
should not be used.|place=
or |location=
with |publication-place=
will be withdrawn because datelines are not critical to locating a news source. These three parameters will become simple aliases of each other with |location=
as the canonical name.{{citation |last=Mowbray |first=G. E. |date=June 1, 1911 |url= |title=1911 Canadian Census: Lisgar, Manitoba |website=[[Library and Archives Canada]]}}
|url=
parameter with the url of the census facsimile.|publisher=[[Dominion Bureau of Statistics]]
. Will its inclusion help readers locate a copy of the source? If yes, include it; if maybe, then maybe include it; if not, don't include it.|location=
or |place=
and/or |publication-place=
. Of all of those cs1|2 templates, there a 5,981 articles listed in
Category:CS1 maint: location. I suspect that it is very unlikely that something like |location=Edenburg, Aberdeen No. 373, Saskatchewan
would ever legitimately appear in a valid cs1|2 template. Instead, something like |location=Edenburg, Saskatchewan
or |location=Edenburg, SK
would be used.Hi there! I am not sure if this is how I start a "talk" or discussion with your user, but I just wanted to thank you for fixing this citation problem on the page I am currently editing (Islamic Uprising in Syria). I am working on it as part of my University Research work and my deadline is very close so I am not 100% diligent or fast with it, so thank you very much! — Preceding unsigned comment added by KAD2223 ( talk • contribs) 16:26, 26 May 2022 (UTC)
Hello! Can you help me locate a help page that depicts the styling conventions used for inline citations? Matters such as how to act when there are commas or periods close to the text that is being referenced, where exactly to put the ref tag, etc. I remember I've read such rules before somewhere but can't be sure where. - Klein Muçi ( talk) 15:45, 29 May 2022 (UTC)
As in the above example, citation markers are normally placed after adjacent punctuation such as periods (full stops) and commas. For exceptions, see the WP:Manual of Style § Punctuation and footnotes. Note also that no space is added before the citation marker. Citations should not be placed within, or on the same line as, section headings.
{{
User box}}
).Take a look at this edit and the edits that have come recently before it.
Take a look at this regex line:
(r"(\{\{\s*cit[aeio][^\}]*\|\s*gjuh[aeë]\s*=\s*)", r"\1language=")
Is there something in it that may have caused such a behavior? I noticed it completely randomly. The line appears to work as intended on Regex101 so I'm not sure if it the one guilty for that edit or not. I fixed it manually but I got curios and thought I could benefit from your experience. - Klein Muçi ( talk) 01:46, 3 June 2022 (UTC)
\1
capture? What are you really trying to do with this regex? Are you attempting to normalize the spelling of gjuha/gjuhe/gjuhë? If so then, perhaps something like this:
(r"(\{\{\s*cit[aeio][^\}]*\|\s*)gjuh[aeë](\s*=\s*)", r"\1Gjuha\2")
|Gjuha = language=en
so, yeah, you have written the regex wrong. Try this:
(r"(\{\{\s*cit[aeio][^\}]*\|\s*)gjuh[aeë](\s*=\s*)", r"\1language\2")
{{
cite web}}
: Check date values in: |access-date=
and |archive-date=
(
help); More than one of |accessdate=
and |access-date=
specified (
help); More than one of |archivedate=
and |archive-date=
specified (
help); More than one of |archiveurl=
and |archive-url=
specified (
help); Unknown parameter |Gjuha=
ignored (
help); Unknown parameter |accesso=
ignored (|access-date=
suggested) (
help)|produkti_brendshëm_bruto=
, anything assigned to that bogus parameter is not displayed.Template:Cite DMM has been nominated for deletion. You are invited to comment on the discussion at the entry on the Templates for discussion page. Beeswaxcandle ( talk) 00:34, 4 June 2022 (UTC)
Hi i noticed that you undid my revision in barisal page i would like to say barisal does not have its own dialect — Preceding unsigned comment added by 99.237.17.126 ( talk) 18:09, 12 June 2022 (UTC)
</ref>{{cite web|url=https://www.britannica.com/place/Barisal|archive-url=https://www.britannica.com/place/Bangladesh|url-status=alive|archive-date=2014-11-13|title=Bangladesh Bureau of Statistics Region Census 2011 page 30|publisher=Bangladesh Bureau of Statistics|access-date=2022-06-12}}</ref>
{{
cite web}}
: Invalid |url-status=alive
(
help)</ref>https://www.britannica.com/place/Bangladesh
is not an archive snapshot of https://www.britannica.com/place/Barisal
; alive
is not a value supported by |url-status=
; because |archive-url=
does not hold the url of a legitimate archive snapshot, |archive-date=2014-11-13
is completely bogus; the title of the Britanica article is "Barisal", not "Bangladesh Bureau of Statistics Region Census 2011 page 30"; Bangladesh Bureau of Statistics
is not the publisher of Britannica; References are properly wrapped with <ref>...</ref>
tags not </ref>...</ref>
tags.<ref name="Barishal District - barisal.gov.bd">{{cite web|url=http://www.barisal.gov.bd/en|archive-url=http://www.barisal.gov.bd/en|url-status=dead|archive-date=2014-11-13|title=
Barishal District|publisher=Bangladesh National Portal
|access-date=2022-06-12}}</ref>
References
{{
cite web}}
: Check |archive-url=
value (
help)CS1 maint: url-status (
link)
|archive-url=
cannot hold the same value as |url=
– a url cannot be an archive snapshot of itself;
http://www.barisal.gov.bd/en is live so |url-status=dead
is incorrect; |archive-date=2014-11-13
is still bogus. I looked at the source: with the exception of a language selector drop-down box in the upper right corner, there is no mention of languages (Bengali or English) or dialects (any) nor any statement about who speaks whatever languages are used in Barisal or Barishal. I presume that you want to use this source to support the three (not four) remaining bullet points in
Barisal § Languages. If that is the case, you might want to find a better source because this source appears to be inadequate.In Special:Diff/1093331531 on Neil Gaiman you removed the titles from several twitter-linked references as "parameter misuse". However, that caused citation errors: "{{ cite web}}: Missing or empty |title= (help)". Perhaps you could come up with replacement titles instead of just breaking the citations? — David Eppstein ( talk) 23:25, 15 June 2022 (UTC)
that caused citation errors:External link in
|title=
; (
which see).Just wanted to say hello wishing you'll have a good time in summer (assuming it is summer soon where you live). Thank you for all the times you've helped around! :) - Klein Muçi ( talk) 18:19, 20 June 2022 (UTC)
Hello! Can you help me understand why the my-my regex is failing in this edit?
(r"(\{\{\s*cit[aeio][^\}]*\|\s*(?:access\-?|archive\-?|doi\-broken\-|lay\-|pmc\-embargo\-|publication\-|air\-?)?date\s*=\s*)October +(\d{4}) +[\-–] +April +(\d{4})", r"\1 tetor \2 – prill \3"),
This is the corresponding regex if I'm not wrong.
PS: Search for date=October 1836 - April 1837 - Klein Muçi ( talk) 10:42, 24 June 2022 (UTC)
|date=April 1826
→ |date=prill 1826
. If smallem applies the my
regex before it applies the my-my
regex, my
probably changed |date=October 1836 - April 1837
to |date=tetor 1836 - April 1837
. If it did that, the my-my
regex will not work. Order matters: regexes must be organized most-complex-to-least-complex.dmy
becomes dmv
in Albanian. -
Klein Muçi (
talk)
12:13, 24 June 2022 (UTC)
dmv-dmv
mdv-mdv
dm-dmv
md-mdv
md-dv
mv-mv
m-mv
d-dmv
dmv
mdv
mv
Sv-v
Sv4-v2
vmd
vmd
. :/What's wrong in here? (Ref 25) - Klein Muçi ( talk) 12:12, 25 June 2022 (UTC)