Wikipedia talk:ProveIt/Archive 2020
 |
Formatting of citations
In my view, it would be much more helpful for editors, making our work easier, if citations were formatted as (look at the code):
Annual Report of the Railroad Commissioners of the State of New York, and of the Reports of the Railroad Corporations. C. Van Benthuysen. 1875. pp. 714–715.
rather than the much more difficult
Annual Report of the Railroad Commissioners of the State of New York, and of the Reports of the Railroad Corporations. C. Van Benthuysen. 1875. pp. 714–715.
There is no downside to this that I can see. It does not make the citation harder for the software to parse. It could be said that it is then harder to read (not my experience), but someone who is reading, as opposed to editing, wouldn't be reading the edit page anyway. When one is searching on an edit page for a citation, the spread-out format makes it easier to find, and it is also easier to deal with one item in a citation, such as publisher. deisenbe (talk) 11:49, 14 March 2020 (UTC)
- @Deisenbe: Maybe you're right, but ProveIt just follows the recommended format as defined in the
formatparameter of template data of the templates, which is usually set to "inline" (see for example here at the very bottom). I think this matter should be decided at the template(s) talk page(s), rather than here, as ProveIt does (and should) follow the recommended format. Sophivorus (talk) 04:04, 19 March 2020 (UTC)
Broken?
I would just like to report that the provided link associated with ProveIt Classic is no longer working, I'm not sure if this is just me but clicking the button moves me to a Verizon error page saying the link does not exist. Cogaidh (talk) 06:08, 29 April 2020 (UTC)
ProveIt does not appear on some pages
ProveIt appears for me on Walter S. Powell and Caleres while using the new editor, but doesn't appear for me on The Party of Moderate Progress Within the Bounds of the Law. I replicated this behavior on Safari and Chrome, although I noticed on chrome the ProveIt button appeared briefly in the corner before disappearing. ProveIt still appears as expected on The Party of Moderate Progress Within the Bounds of the Law in the legacy editor on Chrome, but I have not checked this on Safari. -Furicorn (talk) 18:03, 8 May 2020 (UTC)
General info
Hello! :)
Can someone give me a somewhat detailed answer how do the interfaces of ProveIt change (classic and the new one) from each other and from the interface of the Visual Editor? Also, which of these methods would support easier internationalization? I'm an admin at SqWiki and we've been trying to make the citation process easier for years now and maybe ProveIt can help on that (or maybe VE is enough on its own?) but it's a somewhat crucial condition that whatever that is, it supports i18n good. :) - Klein Muçi (talk) 01:35, 17 August 2020 (UTC)
- Hi! I think it will be easier to try than explain :) This gadget is just designed for citation, but it is not working in VE, because VE has its own citation system: Help:VisualEditor/User guide#Editing references. You can also see Help:Gadget-ProveIt page. Iniquity (talk) 19:12, 17 August 2020 (UTC)
- @Iniquity: hey! Yes, I tried them but all had their drawbacks somehow. The classic version could be localized easily but I couldn't make it work. The upgraded version worked well but it can't be localized. It works with EnWiki rules (the language parameters for examples) and the interface remains in English. As for ProveIt vs VisualEditor, they seemed kind of the same at first glance but the problem is that I work with source code when editing and I'm not sure which one might be easier to grasp from the eyes of a newbie. I read that ProveIt can create a database of used references. If I've understood it correctly, that would be a plus compared to VE I guess. But the problem of localization persists. - Klein Muçi (talk) 01:30, 18 August 2020 (UTC)
- @Klein Muçi Localization problem? It is strange... https://imgur.com/a/UA4JOgA. Iniquity (talk) 09:24, 18 August 2020 (UTC)
- @Iniquity: sorry for the late answer. Yes. While is true that you can translate some things, most of its interface remains in English. The parameters are in English, the way the gadget works in general is with the English language in mind (for example, see what it says for entering language parameters in sources) etc. The classic version allowed you to change all those things but unfortunately, I wasn't able to make it work in our wiki. Maybe I did a JS error somewhere. Not sure. - Klein Muçi (talk) 10:27, 21 August 2020 (UTC)
- @Klein Muçi This is strange, the parameters are completely project dependent and use the language of that project. Can you show what's wrong? Iniquity (talk) 11:20, 21 August 2020 (UTC)
- @Iniquity: sorry for the late answer. Yes. While is true that you can translate some things, most of its interface remains in English. The parameters are in English, the way the gadget works in general is with the English language in mind (for example, see what it says for entering language parameters in sources) etc. The classic version allowed you to change all those things but unfortunately, I wasn't able to make it work in our wiki. Maybe I did a JS error somewhere. Not sure. - Klein Muçi (talk) 10:27, 21 August 2020 (UTC)
- @Klein Muçi Localization problem? It is strange... https://imgur.com/a/UA4JOgA. Iniquity (talk) 09:24, 18 August 2020 (UTC)
- @Iniquity: hey! Yes, I tried them but all had their drawbacks somehow. The classic version could be localized easily but I couldn't make it work. The upgraded version worked well but it can't be localized. It works with EnWiki rules (the language parameters for examples) and the interface remains in English. As for ProveIt vs VisualEditor, they seemed kind of the same at first glance but the problem is that I work with source code when editing and I'm not sure which one might be easier to grasp from the eyes of a newbie. I read that ProveIt can create a database of used references. If I've understood it correctly, that would be a plus compared to VE I guess. But the problem of localization persists. - Klein Muçi (talk) 01:30, 18 August 2020 (UTC)
@Iniquity: for example, when I try it here I get, Last name First name, etc. But some of the parameters are in Albanian so now that you mention it, maybe that's a problem by our side with translation? Also, the tooltips are in English and one of them doesn't really make sense in our project, the one related to the language parameter: The language in which the source is written, if not English... Considering the way we've set up our CS1 module, that advice would be an error even if we substituted English with Albanian. We always put the language of the citation, even on Albanian ones (you get an error if you leave citations without a language parameter). And lastly, the buttons to add new citations almost never seem to work for me in SqWiki. I press them and nothing happens. But some times they do work so I'm not sure why that happens. - Klein Muçi (talk) 11:40, 21 August 2020 (UTC)
- @Klein Muçi Oh, I see, you need to edit a template data of your templates - sq:Stampa:Cito_web#Template_data. Iniquity (talk) 11:45, 21 August 2020 (UTC)
- @Iniquity: okay then. But can something be done about the tooltips? Any way to translate them? Given that we want this tool mostly for new inexperienced with citations users, the tooltips have a big importance on explaining the parameters to them. - Klein Muçi (talk) 11:53, 21 August 2020 (UTC)
- @Klein Muçi tooltips are part of TemplateData too :) 'Description' collumn. Iniquity (talk) 11:56, 21 August 2020 (UTC)
- Oh! Okay then. It's all from our part apparently. Well, that solves it. I'll deal with the translations and we'll start using it. Thank you! :)) - Klein Muçi (talk) 11:58, 21 August 2020 (UTC)
- @Klein Muçi You are welcome! :) I hope the gadget helps you :) Iniquity (talk) 12:02, 21 August 2020 (UTC)
- Oh! Okay then. It's all from our part apparently. Well, that solves it. I'll deal with the translations and we'll start using it. Thank you! :)) - Klein Muçi (talk) 11:58, 21 August 2020 (UTC)
- @Klein Muçi tooltips are part of TemplateData too :) 'Description' collumn. Iniquity (talk) 11:56, 21 August 2020 (UTC)
- @Iniquity: okay then. But can something be done about the tooltips? Any way to translate them? Given that we want this tool mostly for new inexperienced with citations users, the tooltips have a big importance on explaining the parameters to them. - Klein Muçi (talk) 11:53, 21 August 2020 (UTC)
Not working when ported
I'm trying to port this gadget, but it's not working. The [P] logo shows up, and when clicked it changes into a [.] but then doesn't load The console doesn't have any clues, it just says that the website is using deprecated jquery modules. Any ideas?
InnerCitadel (talk) 04:37, 22 August 2020 (UTC)
When the P is clicked the console says "jQuery.fn.andSelf() is deprecated and removed" and "jQuery.fn.unbind() is deprecated" but when I click on the link provided it just takes me to the JMigrate file. I've tried with various skins and having the same problem.
InnerCitadel (talk) 08:38, 23 August 2020 (UTC)
- @User:Iniquity I'm trying to port it to a non-Wikimedia site (wikimsk.org) Any ideas? It's running mediawiki version 1.34. The classic version works but not the new version. InnerCitadel (talk) 22:14, 27 August 2020 (UTC)
How to make a site ProveIt friendly?
Is there a page that describes the proper metadata formatting for a website, that permits ProveIt to most accurately scrape that info from a URL/webpage? -Pete Forsyth (talk) 17:13, 27 August 2020 (UTC)
- Hello :) You can try to find something on this page: mw:Citoid/API. Iniquity (talk) 23:11, 27 August 2020 (UTC)
RfC announce: Citation tools
There is an RfC at Wikipedia talk:Citing sources#RfC: Citation tools regarding whetyer citation tools should allowed. Your input on this question is welcome. --Guy Macon (talk) 22:02, 11 November 2020 (UTC)