User talk:Inductiveload

From Wikisource
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!

Formatting templates...[edit]


Any chance you could examine a template like {{Uksi/paragraph}} or {{cl-act-paragraph}}'s logic at some point. I am starting to wonder if this family of templates should be handled by a module. ShakespeareFan00 (talk) 20:54, 21 January 2018 (UTC)

What exactly do you see to be the problem here? Please give me a specific example (i.e. a link). You say "whitespace related semantic issues" or whatever, but you haven't actually pointed to the problem. For example, I see no linter errors on The Traffic Signs (Welsh and English Language Provisions) Regulations and General Directions 1985 except an obsolete CENTER tag.
And that CENTER tag error came from {{OGL3}} which I've fixed.
Also I don't think spamming the mainspace with hundreds of angry red warnings about the issue is really constructive - perhaps start a maintenance page somewhere to list pages and templates with these issues. "What links here" is enough to find uses of questionable templates then. Normal users don't care abut the parser (not that the message even really says what the problem is), and that's who is affected by that kind of thing. Inductiveloadtalk/contribs 21:19, 21 January 2018 (UTC)
Doubly so when the warning itself contains an unbalanced SPAN tag....
It's also rather hard to work out what is going on where this isn't even documentation on the template pages about what they are even trying to achieve, let alone comments or something in-line to explain the template. Doubly so when there are sub-templates that include the parent templates. And what does "Cl-" mean? Clause? Common law? Cinnamon loaf? Inductiveloadtalk/contribs 22:15, 21 January 2018 (UTC)
The lack of documentation is something that I will need to look into, and about the unbalanced spans, I've commented out the entire warning messages now. It should only categorise.. I will be taking another look at some of the affected templates, when I am less likely to explode. ShakespeareFan00 (talk) 11:21, 22 January 2018 (UTC)

Oh and thanks for the Parser migration guide. Is there a method for proposing that because semi-formal guidelines in Help: ? ShakespeareFan00 (talk) 11:21, 22 January 2018 (UTC)

I have no idea - anyone is free to take the page in whole or part and place content in the Help: namespace, not sure is there is a process. Inductiveloadtalk/contribs 13:00, 22 January 2018 (UTC)

Malformed tables[edit]

Not strictly an Error but in the process of checking for lint errors I came across some table coded like this:-

||content item 1
||content item 2

which based on informal comments, is sub-optimal in at least 2 ways. Linter doesn't check for these currently but a ticket has been raised as task T185203 ...ShakespeareFan00 (talk) 11:43, 22 January 2018 (UTC)

If it's not causing errors and it's not going to break dramatically with the new parser, then why worry too much about it? It's obviously nice to have perfectly formed Wikitext, but that just polish that a reader would never even notice. If the parser can handle it, it's fine: the output HTML will be well formed in any case - there is zero effect to the reader. In the above case, I see expected (and identical) output with both parsers:
  <td>content item 1</td>
  <td>content item 2</td>
Do you have an example of an actual problem you have encountered due to formatting like this? Inductiveloadtalk/contribs 12:58, 22 January 2018 (UTC)
Not yet.. so we can probably not worry about this. ShakespeareFan00 (talk) 14:20, 22 January 2018 (UTC)


This one is ENTIRELY of my own making... Originaly cl-act-paragraph was div based which proved to be incompatible with many other parts of Wikisource.

Not entirely sure how to fix this one, cleanly but as the side-titles were not actually being displayed, I can probbaly remove the usage outright.

Implementing a P DIV switch in the template is another possiblity, but the template is reaching the limits of markup and parser functions... The whole family of templates should probably be converted to LUA code, which should be easier to maintain...

ShakespeareFan00 (talk) 14:20, 22 January 2018 (UTC)

I'm still not entirely clear what these templates do. What is the /x variant? What do the layouts do? What are the various levels? Do these instances just add an anchor? If you have start/end variants, why do you need to put the table in the parameter? They don't seem to do much formatting as it's all done manually in the parameters. These templates are almost impenetrable and totallylargely undocumented, both in terms of a documentation page and inline comments. All I can can tell you is what the linter tells me which is that there is appears to be an unterminated <p> tag in each of the last two template calls on that page. Inductiveloadtalk/contribs 16:47, 22 January 2018 (UTC)
OK I see some documentation on the main template. First question: does the template need to contain the paragraph? Could save yourself a lot of escaping if the template just went at the start of the paragraph (or multi-paragraph block)? Plus page-break spanning would be free then and you wouldn't have to noinclude inside the templates, you'd put it in the header, as normal. Much less scope to have the template upset by the text parameter content if there is no text parameter:
<!-- open some kind of block environment/add anchors etc -->
 | section=.....etc
The text is free to do what it wants <!-- no escaping required here -->

Look, ma! Another paragraph
{{cl-act-paragraph/e}} <!-- probably just a </div> or similar -->
Inductiveloadtalk/contribs 17:21, 22 January 2018 (UTC)
The basic problem at present is that the template wraps a P tag... and you can't put a table inside that. The previous DIV based version of cl-act-paragraph was simplified down to try and get this working. I am increasingly of the view that the problem template should be deleted and someone else starts again, with a nice clean LUA version that can cope with additional situations rather than having to code individual exception clauses, in markup. Could probably add in a wrapper as well, but that's not something for right now ShakespeareFan00 (talk) 20:58, 22 January 2018 (UTC)
Now I'm actually angry, I modify the template so it just passes the text straight thru, and it STILL claims there is something missing an end tag, as you can tell from the history, I've tried SEVERAL methods for trying to get this working. I am having to conclude there is some really obscure interaction occuring. This is now beyond a joke. ShakespeareFan00 (talk) 23:36, 22 January 2018 (UTC)
Note to self, Don't debug your own code when you are getting annoyed with it... You'll miss the obvious mistake :( , and I agree that maybe it's time to rethink the approach entirely... ShakespeareFan00 (talk) 00:17, 23 January 2018 (UTC)


Hi.. I'd attempted to fix a few templates, but it's getting increasingly to the point of WT&&!!&&%% is going on here, with the whitespace handling interactions, between template code, table code, noincludes, pages and transcludes, and I've reached the limit of what I can do.

I hope my changes did NOT break anything, but I am increasingly of the view that the lack of EXPLICIT line/block terminations is a liability...

As for {{cl-act-paragraph}}, It's not salvageable in it's current form... It should be deleted and replaced with something that actually works as intended when Mediawiki is capable of rendering something that complicated without needing to write complex code. ShakespeareFan00 (talk) 21:06, 24 January 2018 (UTC)


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)