User talk:Inductiveload

From Wikisource
(Redirected from User talk:InductiveBot)
Jump to: navigation, search

Inductiveload User Area
Main User Page Talk Page Gallery Contributions

Phil Trans - Illuminated Initial - W.pngELCOME to my user talk page. Feel free to leave me a message if there is a problem or you would like my help, or anything else.

I am also active on Commons. If you would like help with a file I uploaded or would like me to make a file for you, please ask at my user talk page there. If the request is Wikisource-centred, ask here.

Anything you write on this page will be archived, so please be polite (I will be more amenable then) and don't write anything you will regret later! My purpose here is to make interesting and useful documents open to the public. I am never trying to make trouble, and any problems can almost certainly be resolved quickly and easily if everyone stays calm.

Please sign your posts by typing four tildes (~~~~) after your post, and continue conversations where they start.This helps to keep discussions coherent for future readers! If I leave a message on your page, then please reply continue there. My replies to messages on this page will be here.

Older dicussions from this page are stored in archives. Especially interesting or detailed topics are kept in sub-archives. Below is a list of all archives and sub-archives:
Wikisource user page Commons user page Wikibooks user page Wikipedia user page

TUSC token 918678eb806b340b1408614584aaa822[edit]

I am now proud owner of a TUSC account!


Hi, recently you asked for Wikisource support.

Meanwhile I found time to make a quick test in both regular and Wikisource Page:/Index: environment. My impression was that all content model obstacles have been removed now.

Today I learnt that you are running a bot. Then it will be easy for you to change in JavaScript load statement from r.js (r for release) into d.js (d for debug/development). The version info on special page should turn into -2.13.

If there are any complaints please do not hesitate to notify me. If everything is going well, this will be disseminated also as r.js occasionally.

Greetings --PerfektesChaos (talk) 14:50, 7 February 2018 (UTC)

  • I just uploaded a multilingual Wikisource namespace version -2.14.
    • I would recommend not to fork but to keep global versions.
    • One idea I would like to implement if there are some hours left unused is a self-learning category name procedure. Once an unknown category ID has been encountered a system message was not loaded in time. However, the category ID might be memorized on local browser storage. From next page visit on it might be added to the system messages decorating table entries. Some time later it will be added to the JS code as well.
    • The linter framework has been born last summer and is still growing up. We will see where it goes for.
  • The JS startup code has to decide very fast whether the current context is a candidate for linter analysis. It is loaded into all pages and should not consume more resources than really needed. If there are some suspicious numbers 102, 104, 106, 108, 110, 112 it is okay to look at the content model.
Enjoy --PerfektesChaos (talk) 20:35, 7 February 2018 (UTC)
@PerfektesChaos: That's now working for me here at enWS. I'm not planning on forking, I just could try out different IDs from a local server I keep running anyway! Thank you for the quick fix! Inductiveloadtalk/contribs 21:01, 7 February 2018 (UTC)
@PerfektesChaos: Thanks for the updates for the WSes; it seems to be running fine previously from my global.js page through from very light usage. Thanks Inductiveload for getting local customisations identified and suggested. — billinghurst sDrewth 21:43, 7 February 2018 (UTC)
Wikisource support is now live for all.
If you have activated your own version I recommend to return to upstream now, since an automatic handler for unknown error types is now implemented.
Best --PerfektesChaos (talk) 10:05, 18 February 2018 (UTC)
@PerfektesChaos:, any chance to have also header/footer included in lint checking? Very often checking a page in read mode is not the same as checking in edit mode and it is a bit confusing. Thanks.— Mpaa (talk) 20:54, 26 February 2018 (UTC)
“Any chance” – this is a tricky expression.
Say never never.
However, I have a pile of Wiki work to do and I am committed over years.
There is one regular button, as in any text view and source code editing, feeding the body field.
The minor fields would need their own buttons.
I would not expect them this year. If you see such buttons one day, donate to amnesty international.
Until then there is the C&P way over special page.
Sincerely --PerfektesChaos (talk) 16:20, 28 February 2018 (UTC)
OK, I'll take it as a sarcastic "no". Thanks.— Mpaa (talk) 22:58, 28 February 2018 (UTC)

lintHint – split header and body[edit]

Hi, I received a complaint on dewiki.

  • In these cases {{TOCstyle|header=yes}} has been put into header region.
  • {{TOCstyle|completing=yes|model=CD.P ... }} is in the body field.
  • {{TOCstyle|header=yes}} is opening <div><ol>
  • The body contains the adjacent </ol></div>.
  • Naturally, lintHint is detecting that body contains no complete HTML, and header would do so either.

I don’t see that lintHint can be of any help here nor being modified.

  • From my point of view, it is no valid strategy to distribute a self-contained thing over various fields.
  • I would expect to get every field independent, complete and closed in itself.
  • However, I have no idea of customs or practises or namespaces on Wikisource projects.

Please solve this issue internally within enWS and contact the user directly.

TIA --PerfektesChaos (talk) 11:36, 12 March 2018 (UTC)

This was the reason for my question above.— Mpaa (talk) 22:57, 12 March 2018 (UTC)
Hi @PerfektesChaos: - the triple-input field form is how Wikisource performs proofreading of scanned works. The top and bottom fields are for the header and footer of the page, which are not transcluded, the central field is content that is transcluded into the mainspace. These elements are done on the server side, by the proofread-page extension. The actual Page-namespace content Wikitext then looks something like this:
<noinclude><pagequality level=\"3\" user=\"Inductiveload\" />HEADER CONTENT</noinclude>MAIN CONTENT<noinclude>FOOTER CONTENT</noinclude>

Whereas the transcluded mainspace content is just:

I understand that it may not be practical to adapt your tooling to accommodate the Wikisource projects (which, AFAIK, all use the proofread-page extension). However, I also don't think there is a way to "solve the issue internally", as the extension is a core part of how Wikisource operates. I am also not in any kind of admin position that means I speak for the project or any other user. Kind regards, Inductiveloadtalk/contribs 12:03, 14 March 2018 (UTC)

Share your experience and feedback as a Wikimedian in this global survey[edit]

WMF Surveys, 18:36, 29 March 2018 (UTC)

Reminder: Share your feedback in this Wikimedia survey[edit]

WMF Surveys, 01:34, 13 April 2018 (UTC)

Your feedback matters: Final reminder to take the global Wikimedia survey[edit]

WMF Surveys, 00:44, 20 April 2018 (UTC)