User talk:Dalba/Archive 1

From Meta, a Wikimedia project coordination wiki
Jump to navigation Jump to search

Welcome to Meta!

Hello, Dalba/Archive 1. Welcome to the Wikimedia Meta-Wiki! This website is for coordinating and discussing all Wikimedia projects. You may find it useful to read our policy page. If you are interested in doing translations, visit Meta:Babylon. You can also leave a note on Meta:Babel or Wikimedia Forum (please read the instructions at the top of the page before posting there). Happy editing!

Hi Trijnstel, and thanks for all your helps and efforts for the project. Best regards :) -- Dalba(talk) 25 Khordad 1391/ 04:12, 14 June 2012 (UTC)[reply]

Translation notification: FDC portal/Proposals/CentralNotice2012

Hello دالبا,

You are receiving this notification because you signed up as a translator to فارسی on Meta. The page FDC portal/Proposals/CentralNotice2012 is available for translation. You can translate it here:

The priority of this page is بالا. The deadline for translating this page is 2012-10-15.

This banner will invite logged-in editors on all projects to participate in the current public review phase about funding requests by 12 organizations, regarding more than 10 million US dollars of donation money. (Questions about the translation notification system can be asked at [1], and you can manage your subscription at [2].)

Your help is greatly appreciated. Translators like you help Meta to function as a truly multilingual community.

Thank you!

Meta translation coordinators‏, 08:07, 14 October 2012 (UTC)

Translation notification: Fundraising 2012/Translation/AdrianneW Appeal

Hello دالبا,

You are receiving this notification because you signed up as a translator to فارسی on Meta. The page Fundraising 2012/Translation/AdrianneW Appeal is available for translation. You can translate it here:

The priority of this page is متوسط. The deadline for translating this page is 2012-10-31.

Your help is greatly appreciated. Translators like you help Meta to function as a truly multilingual community.

Thank you!

Meta translation coordinators‏, 17:10, 23 October 2012 (UTC)

Translation notification: Fundraising 2012/Translation/Landing Page and Banner messages

Hello دالبا,

You are receiving this notification because you signed up as a translator to فارسی on Meta. The page Fundraising 2012/Translation/Landing Page and Banner messages is available for translation. You can translate it here:

The priority of this page is بالا. The deadline for translating this page is 2012-10-26.

Update: New facts banners ___URGENT___

Your help is greatly appreciated. Translators like you help Meta to function as a truly multilingual community.

Thank you!

Meta translation coordinators‏, 07:59, 24 October 2012 (UTC)

Translation notification: Fundraising 2012/Translation/Poongothai Appeal

Hello دالبا,

You are receiving this notification because you signed up as a translator to فارسی on Meta. The page Fundraising 2012/Translation/Poongothai Appeal is available for translation. You can translate it here:

The priority of this page is متوسط. The deadline for translating this page is 2012-10-31.

Your help is greatly appreciated. Translators like you help Meta to function as a truly multilingual community.

Thank you!

Meta translation coordinators‏, 14:52, 25 October 2012 (UTC)

Translation notification: Fundraising 2012/Translation/Ravan Appeal

Hello دالبا,

You are receiving this notification because you signed up as a translator to فارسی on Meta. The page Fundraising 2012/Translation/Ravan Appeal is available for translation. You can translate it here:

The priority of this page is متوسط. The deadline for translating this page is 2012-11-03.

Your help is greatly appreciated. Translators like you help Meta to function as a truly multilingual community.

Thank you!

Meta translation coordinators‏, 15:26, 29 October 2012 (UTC)

Translation notification: Fundraising 2012/Translation/MikeC Appeal

Hello دالبا,

You are receiving this notification because you signed up as a translator to فارسی on Meta. The page Fundraising 2012/Translation/MikeC Appeal is available for translation. You can translate it here:

The priority of this page is متوسط. The deadline for translating this page is 2012-11-07.

Your help is greatly appreciated. Translators like you help Meta to function as a truly multilingual community.

Thank you!

Meta translation coordinators‏, 22:47, 31 October 2012 (UTC)

Translation notification: Fundraising 2012/Translation/MikeC Appeal

Hello دالبا,

You are receiving this notification because you signed up as a translator to فارسی on Meta. The page Fundraising 2012/Translation/MikeC Appeal is available for translation. You can translate it here:

The priority of this page is متوسط. The deadline for translating this page is 2012-11-07.

Your help is greatly appreciated. Translators like you help Meta to function as a truly multilingual community.

Thank you!

Meta translation coordinators‏, 22:48, 31 October 2012 (UTC)

Translation notification: Fundraising 2012/Translation/MikeC Appeal

Hello دالبا,

You are receiving this notification because you signed up as a translator to فارسی on Meta. The page Fundraising 2012/Translation/MikeC Appeal is available for translation. You can translate it here:

The priority of this page is متوسط. The deadline for translating this page is 2012-11-07.

Your help is greatly appreciated. Translators like you help Meta to function as a truly multilingual community.

Thank you!

Meta translation coordinators‏, 04:48, 1 November 2012 (UTC)

Translation notification: Wikimedia Highlights, September 2012

Hello دالبا,

You are receiving this notification because you signed up as a translator to فارسی on Meta. The page Wikimedia Highlights, September 2012 is available for translation. You can translate it here:



Please consider helping non-English-language Wikimedia communities to stay updated on the most important Wikimedia Foundation activities, MediaWiki development work and other international Wikimedia news from September. You are receiving this message because you signed up to the translation notification system. Questions about this system can be asked at [3], and you can manage your subscription at [4].

Your help is greatly appreciated. Translators like you help Meta to function as a truly multilingual community.

Thank you!

Meta translation coordinators‏, 11:34, 1 November 2012 (UTC)

Translation notification: Fundraising 2012/Translation/Srikeit&Noopur Appeal

Hello دالبا,

You are receiving this notification because you signed up as a translator to فارسی on Meta. The page Fundraising 2012/Translation/Srikeit&Noopur Appeal is available for translation. You can translate it here:

The priority of this page is بالا. The deadline for translating this page is 2012-11-14.

Your help is greatly appreciated. Translators like you help Meta to function as a truly multilingual community.

Thank you!

Meta translation coordinators‏, 11:55, 9 November 2012 (UTC)

Translation notification: Fundraising 2012/Translation/Landing Page and Banner messages

Hello دالبا,

You are receiving this notification because you signed up as a translator to فارسی on Meta. The page Fundraising 2012/Translation/Landing Page and Banner messages is available for translation. You can translate it here:

The priority of this page is بالا. The deadline for translating this page is 2012-11-21.

Your help is greatly appreciated. Translators like you help Meta to function as a truly multilingual community.

Thank you!

Meta translation coordinators‏, 16:54, 14 November 2012 (UTC)

Translation notification: Fundraising 2012/Translation/Thank you letter

Hello دالبا,

You are receiving this notification because you signed up as a translator to فارسی on Meta. The page Fundraising 2012/Translation/Thank you letter is available for translation. You can translate it here:

The priority of this page is بالا. The deadline for translating this page is 2012-11-21.

Your help is greatly appreciated. Translators like you help Meta to function as a truly multilingual community.

Thank you!

Meta translation coordinators‏, 14:41, 15 November 2012 (UTC)

2016 Community Wishlist Survey

Hi,

You’re getting this message because you participated in the 2015 Community Wishlist Survey and we want to make sure you don't miss it this year – or at least can make the conscious choice to ignore if it you want to. The 2015 survey decided what the Community Tech team should work on during 2016. It was also the focus of Wikimedia hackathons and work by other developers. You can see the status of wishes from the 2015 wishlist at 2015 Community Wishlist Survey/Results.

The 2016 Community Wishlist Survey is now open for wishes. You can create proposals until November 20. You will be able to vote on which wishes you think are best or most important between November 28 and December 12. /Johan (WMF) (talk) via MediaWiki message delivery (talk) 11:17, 14 November 2016 (UTC)[reply]

Yadkard translation?

Hi there. Is there a way to translate Yadkard to work for other wikis? While we have the Citoid now on Polish Wikipedia, I prefer to work in sfn-style refs anyway - and your splendid tool works with them. Sadly, there's no easy way to convert English WP's sfn to Polish odn template, let alone convert all those cite book, cite journal and whatnot to the single Template:Cytuj we use at pl.wiki (it's great, it formats itself basing on the fields you use). So, is there a way to add Polish as an option in Yadkard? Halibutt (talk) 20:18, 20 July 2017 (UTC)[reply]

Hi Halibutt! Thanks for your interest in Yadkard. Unfortunately, as it currently stands there is no easy way to add new languages. It's not totally impossible though, for example there is also a localized version of Yadkard for Persian Wikipedia running at http://tools.wmflabs.org/yadfa/ . The problem is that each new language will require localizing a few Python/HTML/CSS modules, which is a technical and time-consuming work. I need to simplify the code to ease the process of i18n and add instructions on how to add new languages.
Another issue is maintaining separate web-services on tools.wmflabs.org which seems to be inefficient (both in terms of resources used and maintenance).
To address this issue I may need to create a single web-service which will allow users to localize the output by choosing their preferred language/project via a simple drop-down menu. It requires rewriting and changing the structure of some parts of the source code.
Alas, I probably will not be able to investigate these ideas in a near future due to lack of spare time, but I do have them in mind.
Dalba 06:30, 21 July 2017 (UTC)[reply]
Thanks for the info, I'll stick to using it for en.wp for now then :) Halibutt (talk) 09:49, 21 July 2017 (UTC)[reply]

JSTOR account redistribution (The Wikipedia Library)

Hi - according to our records you received a free account for JSTOR through The Wikipedia Library. Because we’ve used up all of our allocated accounts, and it’s been some time since they were distributed, we want to redistribute any accounts that aren’t being used to users on our waitlist.

If you’re still using, or plan to use, your JSTOR access, no problem! Simply head over to the Library Card platform, log in, and request a renewal of your account. You should be able to do this from your user page, or the JSTOR signup page. If you can’t find the renewal button, or have any other issues or questions about this, please feel free to leave a message on my talk page. We’ll begin redistributing inactive accounts in September; if you request renewal after then we will only be able to reactivate your account if we have spots remaining. Thanks, MediaWiki message delivery (talk) 13:32, 20 August 2018 (UTC)[reply]

Citer

does not work for any web-page on this news-domain, which is rapidly becoming a major source in Indian ecosystem. Citoid does not work, either. Also, please ask folks to report bugs over here rather than your Wikitech t/p. Wikitech is not under CentralAuth and we need to create a separate account to access it; even anonymous editing is disallowed. The lesser hoops to submit feedback, the more will be recieved. Regards, Winged Blades of Godric (talk) 15:30, 12 March 2019 (UTC)[reply]

@Winged Blades of Godric. I've updated citer. It should now be able to process ThePrint URLs. Also updated the talk page link. Thanks for the feedback. ‍Dalba 11:23, 15 March 2019 (UTC)[reply]
Many thanks for your prompt response. Winged Blades of Godric (talk) 05:45, 22 March 2019 (UTC)[reply]

Citer problem 2019-05-16 12:33pm PDT

Hi, currently dropping in a URL, https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-0708 & seeing this in response:

{{sfn | ''{{title}}''}}

* {{cite web | website={{title}} | url={{websiteUrl}} | ref={{sfnref | {{title}}}} | access-date=2019-05-16}}

and:

<ref name="{{title}}">{{cite web | website={{title}} | url={{websiteUrl}}}} | access-date=2019-05-16}}</ref>

Yours, Peaceray (talk) 19:33, 16 May 2019 (UTC)[reply]

Seeing the problem in Edge, Chrome, & IE. Don't have access to Firefox on my current computer. Peaceray (talk) 19:37, 16 May 2019 (UTC)[reply]
Hi, Peaceray. Unfortunately I don't think I can fix this one. Citer uses the meta tags on a webpage, if available, to gather the citation info. Looking at the source code of that webpage I can see the following:
    <meta property="og:title" ng-attr-content="{{windowTitle}}" />
    <meta property="og:site_name" ng-attr-content="{{title}}" />
    <meta property="og:description" ng-attr-content="{{pageDescription}}" />
    <meta property="og:type" content="website" />
    <meta property="og:url" ng-attr-content="{{websiteUrl}}" />
Even if I make Citer somehow detect the inappropriateness of the gathered data, there is currently no simple way for it to find the correct ones since that page requires a JavaScript-enabled browser to load completely, but Citer does not process the JavaScript portion of pages right now (for performance reasons, and also, it's a complicated process).
Dalba 00:35, 17 May 2019 (UTC)[reply]
Ah, yes. OK, you shouldn't muck with things to handle a truly exceptional outlier. Peaceray (talk) 21:09, 17 May 2019 (UTC)[reply]

Citer bugs

Hi, thanks for maintaining the citer tool, it is very useful for making good citations quickly. I've encountered a two bugs that I hope you might take a look at. First, some non-functional DOIs (particularly with the IEEE journals):

  • 10.1109/TIM.1985.4315297
  • 10.1109/TIM.1976.6312276
  • 10.1524/teme.1979.514524.jg.59

These DOI do seem to work on the DOI wikipedia reference generator, so maybe this is fixable? Second issue is something I've only seen with the APS journals, which work but sometimes are mysteriously missing the page number:

  • 10.1103/PhysRevB.71.045110
  • 10.1103%2FPhysRevLett.102.017002

The DOI reference generator also fails to work on these ones, so maybe APS just has bad metadata on their website. Let me know what you think. Forbes72 (talk) 21:35, 1 June 2019 (UTC)[reply]

Hi, Forbes72! Thanks for reporting this. I fixed the issue for the first three DOIs. It was a bug in Citer, expecting the `volume` value to be numeral-only.
Regarding the missing page numbers, Citer is using http://api.crossref.org/ . For the last two DOIs crossref does not provide any page numbers, but Citer always adds a `|page=` to the generated journal template in hope of making it easier for the end user to add the page parameter manually.
Dalba 06:18, 2 June 2019 (UTC)[reply]
That makes sense. Thanks for improving the tool! Forbes72 (talk) 19:17, 2 June 2019 (UTC)[reply]

More citer bugs

Mostly citer has been pretty reliable. However, I thought I'd let you know of a few more DOIs that citer returns only an error. The same DOIs work on DOI Wikipedia Reference Generator, so I think we can conclude that these are citer bugs and not crossref problems.

  • 10.1007/JHEP10(2017)157
  • 10.1088/0004-637X/705/1/978
  • 10.1126/science.1169101

Maybe these are not too difficult to troubleshoot? Sorry I don't have the programming knowledge to be more specific here. Forbes72 (talk) 03:08, 17 August 2019 (UTC)[reply]

@Forbes72:, I just fixed and updated citer. Thanks for reporting the issue. Dalba 05:58, 17 August 2019 (UTC)[reply]
Looks great! Thanks. Forbes72 (talk) 18:16, 17 August 2019 (UTC)[reply]

doi 10.1093/ww/9780199540884.013.U245351 updating only cite

it is not creating cite web or cite journal or other. it is just creating cite. Leela52452 (talk) 10:41, 30 March 2020 (UTC)[reply]

The CrossRef server describes this DOI as a "reference-entry". I'm not sure what kind of citation template is appropriate for this type. I checked Citoid's result and it creates a general citation, too. Dalba 00:09, 3 April 2020 (UTC)[reply]

citer

Thanks for the tool. It simplifies my life. It would be even more useful if I could easily use it for other Wikipedias than the English one. Maybe one day you could make it output templates for other wikis, have a project/language switch in the UI, ..?--Cartoffel (talk) 16:17, 5 September 2020 (UTC)[reply]

I'm glad to hear that it's been useful to you. Your suggestion totally makes sense, thanks, but unfortunately I'm very busy these days with several other projects. Implementing it requires some major refactoring in code . . . can't make any promises, but I'll keep it mind. Dalba 04:24, 6 September 2020 (UTC)[reply]

Citer query

I too want to thank you for creating such a fabulous time-saving tool. Just one thing, which may be down to the site rather than the tool, I've noticed that it never picks up the author on the newer style of ABC News articles, for example this one. I usually add the authors manually afterwards, and overwrite with "website =ABC News |publisher =Australian Broadcasting Corporation", no biggie, but thought I'd mention it just in case there's a possible programming solution. Laterthanyouthink (talk) 14:01, 7 September 2020 (UTC)[reply]

Thanks for the feedback. I've updated author detection algorithm of Citer. It should work now. Regarding the publisher, in short, the site does not introduce itself like that and I don't want to rely on domain/url-specific settings... Dalba 16:24, 25 September 2020 (UTC)[reply]
Hi Dalba, sorry for the late response but I didn't get notified and have only just spotted your response now, when I came looking for another reason... I did notice that the ABC citations had improved, so thanks very much for that, mostly 100% now, which is great. (I mostly only add the publisher if it seems necessary to avoid confusion with the American ABC.) Another thing I've noticed on and off (I don't think it happens all the time, but I don't always check), which may be something to do with time zones(?), is that the date sometimes shows the previous day's date, for example with this Guardian article, the date comes out as 14 June. Not a big worry, but just passing on FYI in case you want to tinker some more. Laterthanyouthink (talk) 00:55, 25 November 2020 (UTC)[reply]
Hi Laterthanyouthink. Me too, I can hardly find time to visit the wiki these days :) Sometimes sites provide contradicting information. For example the article mentions "Thu 14 Jun 2018 19.00 BST" right under the author name and there is also a <meta property="article:published_time" content="2018-06-14T18:00:07.000Z"/> tag inside the source code of the page. "14 June" does not seem wrong to me here, even though that's one day earlier than the date in the URL itself. Dalba 13:36, 8 January 2021 (UTC)[reply]
p.s. I forgot to add that I'm very impressed with its citing of scientific journal articles - does a great job in seconds, compared with much longer time needed for manual construction! Laterthanyouthink (talk) 00:57, 25 November 2020 (UTC)[reply]
Thank you! :) Dalba 13:36, 8 January 2021 (UTC)[reply]

Another minor issue

Hi again. I don't know whether it's just a problem with this source, but Citer doesn't seem to pick up the authors from InDaily, such as this one. Not serious, but thought I'd let you know FWIW, in case there is a simple fix. Laterthanyouthink (talk) 11:04, 22 December 2020 (UTC)[reply]

Hi again! Yes check.svg Done I've tuned the algorithm a little bit. It should be working now. I just hope it won't cause too many false positives in other cases. Dalba 13:39, 8 January 2021 (UTC)[reply]
Thanks very much, Dalba. I'll keep an eye on it, but hopefully won't be pestering you with any further issues! Laterthanyouthink (talk) 01:14, 9 January 2021 (UTC)[reply]

Citer in other languages

Citation templates in wp:it are slightly different from those of wp:en. Is there a solution to use the tool in wp:other languages? TX!--Tytire (talk) 19:06, 5 June 2021 (UTC)[reply]

Hi, Tytire! Unfortunately Citer does not currently support other languages. Dalba 09:47, 6 June 2021 (UTC)[reply]

dead-url -> url status

Hi, thanks for the great tool, I love how it expands archive.org URLs (any chance for archive.is?); I just wanted to alert you that 'dead-url=yes' parameter has changed to 'url-status=dead'. Quuux (talk) 07:19, 19 September 2019 (UTC)[reply]

Hi Quuux, I've update the parameter name. Thanks for bringing my attention to it. Regarding http://archive.is/, it should be possible, but I'm busy these days and I don't know when I'll be able to take a close look. Dalba 13:30, 19 September 2019 (UTC)[reply]

NCBI

https://www.ncbi.nlm.nih.gov/books/NBK53329/

And I got it all the time in the past few days that "HTTP error:

One or more of the web resources required to create this citation are not accessible at this moment." --It's gonna be awesome (talk) 08:24, 28 June 2019 (UTC)[reply]

It seems that www.ncbi.nlm.nih.gov is not accessible from Toolforge:
$ hostname
tools-sgebastion-08

$ nslookup www.ncbi.nlm.nih.gov
;; Got SERVFAIL reply from 208.80.154.143, trying next server
Server:         208.80.154.24
Address:        208.80.154.24#53

** server can't find www.ncbi.nlm.nih.gov: SERVFAIL
The same command works fine on my PC. My guess is that the issue resides in the Toolforge's DNS or is a configuration problem on www.ncbi.nlm.nih.gov. In either case I don't think there is much that I can do to resolve it.
P.S: Also tried Citoid. It fails with "We couldn't make a citation for you" error.
Dalba 09:22, 28 June 2019 (UTC)[reply]
@Dalba: I tried Citoid and it did fail with "We couldn't make a citation for you" error. --It's gonna be awesome (talk) 14:12, 30 June 2019 (UTC)[reply]
Just checked this and works now. Dalba 08:19, 21 April 2022 (UTC)[reply]

Citer bug

huffington post links like this one https://www.huffpost.com/entry/france-bans-spanking-kids-with-new-law_n_5873ccc1e4b02b5f858a39ff return a generic title with no authors etc. eg ref name="HuffPost is now a part of Verizon Media" cite web | title=HuffPost is now a part of Verizon Media | website=HuffPost is now a part of Verizon Media | url=https://www.huffpost.com/entry/france-bans-spanking-kids-with-new-law_n_5873ccc1e4b02b5f858a39ff | access-date=Feb 2, 2020 . I don't know if it's fixable on your end or the websites fault. Hydromania (talk) 05:17, 2 February 2020 (UTC)[reply]

Hi Hydromania, unfortunately I don't think I can fix this in a general way. The website requires Citer to accept a data agreement, but obviously Citer is not smart enough to do that. What Citer actually receives is a page with the following text:
Your data, your experience
HuffPost is part of Verizon Media. Click 'I agree' to allow Verizon Media and our partners to use cookies and similar technologies to access your device and use your data (including location) to understand your interests, and provide and measure personalised ads. We will also provide you with personalised ads on partner products. Learn more about how we use your data in our Privacy Centre. Once you confirm your privacy choices here, you can make changes at any time by visiting your Privacy Dashboard.
Click 'Learn More' to learn and customise how Verizon Media and our partners collect and use data.
[I agree] [Learn more]
Dalba 10:29, 3 February 2020 (UTC)[reply]

enwiki ending need for |ref=harv for Module:Citation/CS1

Hi, Dalba. FYI, I just saw at wikipedia:en:User talk:Citation bot#remove ref=harv that |ref=harv will be generated by default from wikipedia:en:Module:Citation/CS1. Peaceray (talk) 18:04, 18 April 2020 (UTC)[reply]

Hi. Thanks for letting me know. I've updated citer accordingly. Dalba 08:35, 28 April 2020 (UTC)[reply]

Many thanks for Citer

What a brilliant tool you have given us! I must have send you a friendly thought a thousand times, and now I'm here to say: thank you!

Citer used to be able to make citations directly from archived URLs in the Wayback machine, including filling in all those pesky fields that go with them in the citation template. That feature seems to have been lost at some point the last year. It would be wonderful if it is possible to get it back. Once again, thank you very much. Best regards, Sam Sailor 12:09, 10 June 2021 (UTC)[reply]

Hi, Sam! Thank you! That means a lot to me.
Could you provide sample URLs that Citer fails at them? I just tested [5] and it seems to be working. Dalba 03:44, 12 June 2021 (UTC)[reply]
Clicking the bookmarklet on http://web.archive.org/web/20210612025330/https://www.nytimes.com/2021/06/11/technology/apple-google-leak-investigation-data-requests.html takes me to http://web.archive.org/web/20210612025330/https://tools.wmflabs.org/citer/citer.fcgi?user_input=http%3A%2F%2Fweb.archive.org%2Fweb%2F20210612025330%2Fhttps%3A%2F%2Fwww.nytimes.com%2F2021%2F06%2F11%2Ftechnology%2Fapple-google-leak-investigation-data-requests.html&dateformat=%B+%d,+%Y
I then tried to copy-paste http://web.archive.org/web/20210612025330/https://www.nytimes.com/2021/06/11/technology/apple-google-leak-investigation-data-requests.html into https://citer.toolforge.org/ and that works perfectly, forgive me for not trying that to begin with.
So, something is wrong on my end somehow. What could it be?
My bookmarklet should be correct: javascript:void(window.open('https://tools.wmflabs.org/citer/citer.fcgi?user_input='+encodeURIComponent(location.href)+'&dateformat=%25B+%25d%2C+%25Y')) Thanks again, Sam Sailor 05:30, 12 June 2021 (UTC)[reply]
Sam, you're totally right! The bookmarklet does not work correctly on archive.org. The reason, I think, is that archive.org messes with the internal open function of the web page, so that every URL that one tries to open will be redirected to archive.org's equivalent of it. I searched for workarounds, but none of them worked. I guess we'll have to use Citer directly in this case :(, at least until a workaround is found, which I'm not sure exists/is worth creating a much more complicated bookmarklet just for one site. Dalba 03:07, 13 June 2021 (UTC)[reply]
What you say sounds reasonable, Dalba. Mam'noon! Sam Sailor 04:28, 13 June 2021 (UTC)[reply]

who.int

@Dalba: Citer fails for the https version of this URL. It works for the non-https version. (Similar behavior for other URLs at who.int)

--Whywhenwhohow (talk) 06:30, 24 January 2022 (UTC)[reply]

There was a bug here. I think it is resolved now. Thanks for reporting the issue. Dalba 16:07, 17 February 2022 (UTC)[reply]

Date lag

Hi Dalba - me again. I thought that I had raised this once before, but I don't see it here. It's about the date quite often showing the date before publication rather than the date shown on the web page, and I wondered if it's something to do with the date lag in the eastern hemisphere. I use Australian sources quite a lot, and I've noticed it particularly with ABC News pages, but also with InDaily. Could this be something to do with the date stamp of the page being in UTC instead of being converted to the local time zone (or one of them - I assume that ABC would use EST)? Just a thought. 114.30.100.149 11:13, 19 February 2022 (UTC)[reply]

Hi. Sorry for my late responses. Could you provide some links that have this issue? My initial guess is that the date is correct, but may differ a little from what actually appears on the page. Sometime websites provide different metadata for their articles than the ones actually shown to end users. You may check the source code of such webpages to see if there is such metadata by searching for the wrong date. Most browsers show the the source code of a webpage using `Ctrl+U` keyboard shortcut. Dalba 04:59, 23 February 2022 (UTC)[reply]
Hi, sorry, a late response from me too, as I didn't get notification of the update and don't often log in to Wikimedia, but just noticed something else today. Thanks for yours. A short while ago, I was using the citer tool to create a citation for this URL: https://www.morningtonisland.com.au/arts, which worked fine but I noticed the access-date was 27 Feb, whereas it is 28 Feb where I live (Adelaide, South Australia). However, having just tried it again now, it now returns 28 Feb! I will attempt to look at the source code of pages as you suggest, and also report back to you with a specific example next time I notice the other date issue. (Sorry, I see the problem - I was not logged in before. Also, should change my Wikimedia name to be the same as my Wikipedia one...) Picadder (talk) 00:15, 28 February 2022 (UTC)[reply]
Coincidentally, I have had occasion to try Ctrl/U for a different reason, in dispute with a recalcitrant seller, and I wanted to check the date that these t&c were uploaded, so tried ctrl/U on it, but cannot find a specific date (at least, not by looking for "2022"). Can you assist in showing me how to find the date on this one, please? https://ameliasaustralia.com/pages/terms-of-use Picadder (talk) 05:36, 28 February 2022 (UTC)[reply]
Unfortunately I cannot find a date either. It's almost impossible to know the exact date if the server does not provide it (or if you don't trust the information the server provides). For popular webpages one might be able to deduce an estimate by looking at the date of the cached versions of the webpage in services like Wayback Machine, but I'm afraid that might not help in this case. Dalba 03:56, 1 March 2022 (UTC)[reply]
Okay, no worries, thanks for trying. Picadder (talk) 10:37, 1 March 2022 (UTC)[reply]
That's true. Citer does not know where you live, so it fills the access-date using the toolforge's webserver date which I believe is UTC. I might be able to add a feature to inspect user's timezone somehow, but I probably won't due to privacy reasons. Dalba 04:07, 1 March 2022 (UTC)[reply]
Ah, I see. I'm sure it doesn't matter that much. Is the page date issue related to discrepancies between when the page publishes according to UTC and the local date that it actually publishes on the article? I don't suppose it really matters either, just one of those niggling things that I spot occasionally! Thanks for following up, anyway. The tool is really a great timesaver so not going to worry about this. Oh, one other minor thing that I have noticed, this one consistently, is that it always lower-cases "the" in The Guardian - is that because they publish it that way? Picadder (talk) 10:37, 1 March 2022 (UTC)[reply]
Just FYI, I just came across an example: https://www.abc.net.au/news/2022-02-27/turtle-hatchlings-monitored-on-avoid-island/100847916 - apparently posted on the 27th (which is also part of the url), but citer says 26th. Picadder (talk) 10:45, 2 March 2022 (UTC)[reply]
This is interesting. If you disable the JavaScript of your browser the article shows "Posted Sat 26 Feb 2022", but with JavaScript enabled, it changes to "Posted Sun 27 Feb 2022". Anyway, finding the date line is hard and error-prone for computer, since there is no standard way of expressing it. Meta tags on the other hand are defined in a more standard way, therefore citer tries to use meta tags if it finds one. In this case it finds the following meta tag inside the source code of the page:
 <meta data-react-helmet="true" property="article:published_time" content="2022-02-26T20:47:00+00:00"/>
Dalba 04:33, 3 March 2022 (UTC)[reply]
"the Guardian" is another case of meta tags taking priority:
<meta property="og:site_name" content="the Guardian"/>
Dalba 04:39, 3 March 2022 (UTC)[reply]
Ah, I see. Interesting! And that's cool - I learnt a new thing (how to disable javascript in Firefox). Thanks for the explanation. Picadder (talk) 03:09, 5 March 2022 (UTC)[reply]

sanofi.com

Citer removes hyphen characters from this URL. It also places the URL in the website field.

--Whywhenwhohow (talk) 06:52, 7 February 2022 (UTC)[reply]

If you look at the html source code of the page you'll see that sanofi.com is misusing meta tags:
<meta content="https://www.sanofi.com/media-room/press-releases/2022/2022-02-04 23-00-00 2379517"  property="og:url" />
<meta content="https://www.sanofi.com/en/media-room/press-releases/2022/2022-02-04-23-00-00-2379517"  property="og:site_name" />
I'm not going to implement a fix for this; you may want to contact the website's admin. Dalba 09:10, 17 February 2022 (UTC)[reply]

cen.acs.org

Citer fails for this URL
--Whywhenwhohow (talk) 06:45, 24 January 2022 (UTC)[reply]
cen.acs.org uses JavaScript and cookies to prevent bots from crawling their website. Without the cookies the server response looks like this:
$ curl https://cen.acs.org/pharmaceuticals/drug-discovery/How-Pfizer-scientists-transformed-an-old-drug-lead-into-a-COVID-19-antiviral/100/i3
<html style="height:100%"><head><META NAME="ROBOTS" CONTENT="NOINDEX, NOFOLLOW"><meta name="format-detection" content="telephone=no"><meta name="viewport" content="initial-scale=1.0"><meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1"><script type="text/javascript" src="/_Incapsula_Resource?SWJIYLWA=719d34d31c8e3a6e6fffd425f7e032f3"></script></head><body style="margin:0px;height:100%"><iframe id="main-iframe" src="/_Incapsula_Resource?SWUDNSAI=31&xinfo=5-37758187-0%200NNN%20RT%281645103975751%2018%29%20q%280%20-1%20-1%20-1%29%20r%280%20-1%29%20B12%284%2c315%2c0%29%20U5&incident_id=484000650050968331-150946707254022213&edet=12&cinfo=04000000&rpinfo=0&cts=u%2b8REw3kg%2bLkfCFPxJ%2bUR3Cdrv2w6xRBfp9ClVu%2bT7oyVKLetFaIzqR6O1XTNYKJ&mth=GET" frameborder=0 width="100%" height="100%" marginheight="0px" marginwidth="0px">Request unsuccessful. Incapsula incident ID: 484000650050968331-150946707254022213</iframe></body></html>
I think Citer won't be able to handle this one either, sorry :( Dalba 13:28, 17 February 2022 (UTC)[reply]

Citer doesn't recognize url

For some reason, it's only the AKC urls - https://www.akc.org/dog-breeds/american-bulldog/ I've tried clearing cache, reloading, using Chrome & Safari. Nada. Atsme📞📧 14:16, 20 April 2022 (UTC)[reply]

The size of the web page was unusually large. Citer refuses to process large documents to avoid any malicious requests and/or wasting processing time. Anyway, the previous size limit seemed to be too small, I've increased it to 10MB. That fixed the problem for this case. The size limit may still be too restrictive for some webpages. I may reconsider the size in the future. Thanks for reporting the issue. Dalba 06:03, 21 April 2022 (UTC)[reply]
They have recently added video, which may contribute to the larger size? More resources are adding various types of media so it's probably time to increase the size limit for those of us who are highly dependent on your wonderful tool. Atsme📞📧 12:37, 21 April 2022 (UTC)[reply]

Citer date bug

The citer template has an edge case bug for dates on the first day of the month. It uses the previous month in the date. For example, for the URL https://www.bbc.com/news/world-us-canada-59843627, with the date format 1 January 2020, it generates output containing the date 1 December 2021 instead of 1 January 2022. (It happens on the first of any month -- the year change is unrelated). --Whywhenwhohow (talk) 02:47, 1 January 2022 (UTC)[reply]

Each click of a date format at the top of the page changes the month to an earlier month.
  • Click January 1, 2020 gets November 1, 2021
  • Click Jan 1, 2020 gets Oct 1, 2021
  • Click 1 January 2020 gets 1 September 2021
  • Click 1 Jan 2020 gets 1 Aug 2021
--Whywhenwhohow (talk) 07:28, 1 January 2022 (UTC)[reply]
@Whywhenwhohow, you're right. There was a timezone conversion bug. I think I've fixed it with the latest update. Thanks for reporting the issue. Dalba 11:29, 1 January 2022 (UTC)[reply]
It looks like there is still a bug. Using the 2020-01-01 format for the URL above displays December 31 instead of January 1. Then clicking any other date format changes the displayed date to December 30. --Whywhenwhohow (talk) 19:01, 1 January 2022 (UTC)[reply]
@Whywhenwhohow, I cannot reproduce the issue anymore. Try clearing your browser's cache or if possible on another computer. Dalba 15:39, 2 January 2022 (UTC)[reply]

┌─────────────────────────────────┘
It exhibits the same behavior elsewhere. It decrements the date and the access-date.

Start with date format "2020-01-01" for the BBC URL and see date=2022-01-01[1]

Click date format "1 January 2020" (or any other date format) and see date=31 December 2021[2]

Click date format "2020-01-01" and see date=2021-12-31[3]

Click date format "1 January 2020" (or any other date format) and see date=30 December 2021[4]

Click date format "2020-01-01" and see date=2021-12-30[5]

Click date format "1 January 2020" (or any other date format) and see date=29 December 2021[6]

References

  1. "Betty White: Biden leads tributes for Golden Girls actress". BBC News. 2022-01-01. Retrieved 2022-01-02. 
  2. "Betty White: Biden leads tributes for Golden Girls actress". BBC News. 31 December 2021. Retrieved 1 January 2022. 
  3. "Betty White: Biden leads tributes for Golden Girls actress". BBC News. 2021-12-31. Retrieved 2022-01-01. 
  4. "Betty White: Biden leads tributes for Golden Girls actress". BBC News. 30 December 2021. Retrieved 31 December 2021. 
  5. "Betty White: Biden leads tributes for Golden Girls actress". BBC News. 2021-12-30. Retrieved 2021-12-31. 
  6. "Betty White: Biden leads tributes for Golden Girls actress". BBC News. 29 December 2021. Retrieved 30 December 2021. 
I see what you mean, Whywhenwhohow, but unfortunately I can not reproduce. On my machine the converted dates all keep pointing to January 1st.
Which browser are you using? Have you tried latest version of Firefox? (I'm not suggesting that you should change your browser, just want to figure out if it is browser-related.)
Also, if you don't mind sharing, what timezone is your computer set on? Is it Greenwich Mean Time/Pacific Standard Time/etc? Dalba 04:43, 3 January 2022 (UTC)[reply]
It happens in Chrome and Firefox using EST. Can you try it on a mobile device and see how it behaves there? --Whywhenwhohow (talk) 07:57, 3 January 2022 (UTC)[reply]
@Whywhenwhohow, thanks. I was able to reproduce and debug the issue in EST timezone and came up with a fix. I've updated citer. Dalba 08:39, 7 January 2022 (UTC)[reply]
Thank you. Whywhenwhohow (talk) 19:39, 8 January 2022 (UTC)[reply]