User talk:George Orwell III

From Wikisource
Jump to: navigation, search
George Orwell III (talk page)

(Archives index, Last archive) Note: Please use informative section titles that give some indication of the message.


Template:PermissionOTRS is top presenting[edit]

Would you please add to future work list, a review of Template:PermissionOTRS as it seems to be top presenting on Rabbit: A Compiler for Scheme, and inline it is at the bottom of the page. Thanks. — billinghurst sDrewth 03:38, 13 January 2016 (UTC)

@Billinghurst: All our M-box, A-box, T-box and similar "box" based banners are based on Wikipedia's implementation and are suppose to "group" together when one or more of the family of box templates are present. Since they are not content, they should not appear in the content area -- as is the case even on Wikipedia article talk pages. So they can all appear before the namespace header at the top or before the category "bar" on the bottom when it comes to Wikisource's "implementation" of this particular Wikipedia scheme.

That said, I can attempt to convert the current OTRS banner from its current "box" based format to a license based one -- which I think we can both agree should have been the appropriate foundation for something "license related" to begin with -- to resolve the positioning issue you raised if that is agreeable(?) to you. Let me know either way. Please note: I'm almost at the point of declaring a wikibreak since my free time is nearly nonexistent nowadays. -- George Orwell III (talk) 22:28, 18 January 2016 (UTC)

MediaWiki:PageNumbers.js and erroneous linkage to Main Page[edit]

I hope you might be able to fill in the gaps in my own faulty memory.

For some reason I recall being very interested in cases when PageNumbers.js generated page links which did not "point" back into the Page: name space but instead resolved to $wgArticlePath; and to my frustration not being able to find a suitable example to complete investigations due to (some random idiot) "fixing" the then-issue and killing further investigation cold.

Now, to my intense annoyance I have found such an example: Mexico,_as_it_was_and_as_it_is#x yet cannot recall the purpose for which it was so essential to follow up (it was perhaps somehow related to the issue you and I mutually resolved upon reflecting red-links through to the offset-left page numbering?) Apologies for this rave: if it makes sense please treat me like the idiot I clearly am and kindly or otherwise set me straight. However if it does not make sense then dismiss me for a fool. AuFCL (talk) 03:50, 16 January 2016 (UTC)

It all has something to do with the near-random case of a page-boundary occurring such that mediawiki maps the "marker" to a <tr> as occurs in the above example:
<tr class="pagenum ws-pagenum" id="x" data-page-number="x"></tr>
—as opposed to the "normal" case where a <span>² (isn't that pathological enough all of itself?) is produced (e.g. just above the prior error):
<span><span class="pagenum ws-pagenum" id="ix" data-page-number="ix" title="Page:Mexico_as_it_was_and_as_it_is.djvu/22"></span></span>
—and (presumably) PageNumbers.js gets confused and generates the default page link instead of a proper one. AuFCL (talk) 04:22, 16 January 2016 (UTC)
Aha! No title for
			'<a href= "' + page_url + action_str + '"' +
				class_str +
				' title= "' + mw.html.escape( page_title ) + '">' +
				mw.html.escape( name ) +
—to work upon! So PageNumbers.js is the victim not the perpetrator. The real issue is (oh ${Gods}!) further upstream. This is going to need a larger hammer than even I can persuade you to wield… AuFCL (talk) 04:30, 16 January 2016 (UTC)
O.K. lost in a world of Gerrit but currently suspect is:
	 * Returns titles of a page namespace page from name of scan and page number
	 * If the title with an internationalized number doesn't exist and a page with
	 * arabic number exists, the title for the arabic number is returned
	 * @param $scan string scan name
	 * @param $number int page number
	 * @return Title|null
	protected static function getPageTitle( $scan, $number ) {
		global $wgContLang;

		$i18nNumber = $wgContLang->formatNum( $number, true );
		$title = Title::makeTitleSafe( self::getPageNamespaceId(), $scan . '/' . $i18nNumber );
		if ( $i18nNumber != $number && !$title->exists() ) {
			$arabicTitle = Title::makeTitleSafe( self::getPageNamespaceId(), $scan . '/' . $number );
			if ( $arabicTitle->exists() ) {
				return $arabicTitle;
		return $title;
—out of ProofreadPage.body.php, or whatsoever its derivative may have become. Giving up for now (my failure). AuFCL (talk) 04:57, 16 January 2016 (UTC)
(Also (entirely unrelated because the process clearly does not work™): MediaWiki talk:Gadget-Easy LST.js AuFCL (talk) 05:42, 16 January 2016 (UTC))
Further down in ProofreadPage.body.php (in rather large function renderPages()) it appears the selected page is passed through MediaWiki:Proofreadpage pagenum template. Possibility for a debugging check/breakpoint (obviously on Test2! Not here!)? AuFCL (talk) 09:12, 16 January 2016 (UTC)
@AuFCL: Just dropping you a note that I stopped by and am now aware of your post but will need some time to absorb and then look into this further. -- George Orwell III (talk) 22:34, 18 January 2016 (UTC)

I see one of your fav. toys has "returned"[edit] I'll lay off and let your fun continue. AuFCL (talk) 09:18, 23 January 2016 (UTC)

A floating image caption problem[edit]

Hi. I ran into a problem of a three line caption for {{FIS}} floating image HERE, which I tried to display properly but couldn't. Could you please look at it? Sorry to have forgotten. — Ineuw talk 01:22, 29 January 2016 (UTC)

I somewhat brutally simplified things. Hope that was O.K. AuFCL (talk) 01:48, 29 January 2016 (UTC)
Nothing brutal about it, thanks.  — Ineuw talk 05:39, 29 January 2016 (UTC)

Dear ${MONEY} why‥[edit]

‥(that got your attention!)‥are you persisting with this? Didn't you get the memo to the effect #wikiEditor-section-characters is so much closer to the hierarchy you seek? AuFCL (talk) 07:12, 30 January 2016 (UTC)

I understand that; I'm pondering options that go beyond altering just the character set(s) is all. -- George Orwell III (talk) 07:44, 30 January 2016 (UTC)
Of course I was teasing. As it stands I am but guessing what you are really trying to achieve. AuFCL (talk) 08:37, 30 January 2016 (UTC)

valign/valignb usage associated with TOCs pretty useless[edit]

I noted your experiment and reversal here. It is stating to grate that the so-called CSS maintainers seem to lack motivation or ability to come up with useful cases so here comes trouble! If this is too dumb to contemplate then kindly restore your cerebral content from a recent backup as appropriate. You do take back-ups frequently don't you?

To be serious, a table representing a TOC rarely is a useful target for "traditional" classes "valign" or "valignb" and related. The most common case for three-or-more columns is for the first column cells to be top-aligned; and the third, fourth etc. to be bottom-aligned. By stretching a point I'd suggest applying hanging indentation to the second column alone, and whitespace:nowrap to the others. To save bloating your talk-page please see User:AuFCL/SandBox if interested. I am sure you will think of improvements. AuFCL (talk) 05:34, 7 February 2016 (UTC)

I'm of the same mind and spent a bit of yesterday separating .table-c75vtop into .tablev75 and .valign, etc. just for that reason & so I can eventually "bot out" the .valign and .valignb classes altogether (less than 250 uses I [believe]) to something-better-that-is-yet-to-be-defined.

And I'm also already thinking the same re: typical 1st, 2nd and 3rd cell usage as well but not convinced its worth it because of the table spanning more than one Page; transclusion thing. FuaxTables based on divs [apparently] eliminates all of that (proof-of-concept done btw).

So I was going to do something like you have in your sandbox now but only establishing the 1st and last cells with pseudo classes like :first-child / :last-child / :first-of-type / :last-of-type / etc. at first but now I'll play with your example next instead. -- George Orwell III (talk) 05:55, 7 February 2016 (UTC)

Light the blue touch-paper and stand well clear. Thought this might stir up a reaction. AuFCL (talk) 06:24, 7 February 2016 (UTC)

Need help in Bengali Wikisource[edit]

I have just import MediaWiki:Common.js to our MediaWiki:Common.js. Our main issue at mainspace page (NS:0) where trancluted page link shown as garbage. Please check at s:bn:চাঁদের পাহাড়/দ্বিতীয় পরিচ্ছেদ, you could see it. The MediaWiki:PageNumbers.js is also load from enws. ButMediaWiki:PageNumbers.js when I MediaWiki:PageNumbers.js load from old wikisource, the pagenumber shown properly instead of garbage. But then dynamic page layout with pagelayout option not working. So could you please check MediaWiki:PageNumbers.js to fix the issue in for Bengali Wikipedia. OR we can load MediaWiki:PageNumbers.js from local bnws with necessary change to fix this issue. Jayantanth (talk) 17:08, 7 February 2016 (UTC)

The bottom line is that the English variant, as "ugly garbage" the embedded links back to the Page: namespace may appear, still WORKS when you click on it. This and the fact the Display Options also work means there is nothing really 'broken' here on the English side. The major reason "we" moved away from importing oldwikisource variants was that only bits and pieces of the advertised options actually worked. You should try copying their mul:MediaWiki:Base.js and mul:MediaWiki:Proofreadpage pagenum template to see if that helps anything.

Either way, the root of the problem "seems" to be a language based one -- specifically the Arabic numbers (integers 1, 2, 3, etc.) are not being recognized and converted to their Bengali counterparts when using our script(s) causing the conversion to hex or whatever that is. I'm to sorry to say I have no idea how to fix something like that. You should try asking mul:User:Tpt or mul:User:Phe instead. -- George Orwell III (talk) 18:47, 7 February 2016 (UTC)

Thank you George Orwell III for prompt reply. As of now I have just copy paste the code mul:MediaWiki:Proofreadpage pagenum template to s:bn:MediaWiki:Proofreadpage pagenum template. Now garbage has gone. Previously that was copypaste from ENWS. But Now another issue comes, "Page links displayed/hidden" and "Page links beside text/within text" vanish from side menu. Only "Display option" exits. Any idea how to recover side menu options as ENWS? Jayantanth (talk) 19:54, 7 February 2016 (UTC)
Fixed the issues after some trial and error. change the code s:bn:MediaWiki:Proofreadpage pagenum template. The same code of ENWS, just without of <includeonly></includeonly>. Now work perfect.Jayantanth (talk) 20:50, 7 February 2016 (UTC)

how to download from google books?[edit]

This book's upload, did you download it from Google? And if so, could you please post an image of the webpage? The reason for asking an image to see if I can access the same page from a Canadian IP. Have not been able to download any books directly from Google, and don't know why. Thanks. — Ineuw talk 23:15, 8 February 2016 (UTC)

@Ineuw: Have you tried toollabs:bub/ ? — billinghurst sDrewth 01:08, 9 February 2016 (UTC)
Thanks. Didn't know about this. Will try it later tonight. — Ineuw talk 03:03, 9 February 2016 (UTC)
@Ineuw: - What is so "wrong" this file that you can't collect your senses and go to the sources parameter of the book template for the link I used from Google Books? -- George Orwell III (talk) 00:09, 13 February 2016 (UTC)

A different note on mediawiki:PageNumbers.js (& mea culpa)[edit]

You might cast your memory back to my influencing you to make this change? Well this proves there is a bug of minor consequence remaining—to which I currently have not the slightest inkling of a solution. In other words I realise now I mislead you at the time!

It appears if the very first item on a transcluded page happens to be a red-link itself, the page_span.parentNode.nextSibling logic as it stands homes in to the wrong DOM node with this result. I am undecided as to whether this issue is unique to the first page in the transclusion set; or perhaps the parser hierarchy has subtly changed since PageNumbers.js traversal logic was established. Either way, two heads aware of matter better than one?

This is far from being a priority matter; just a note you might find of interest. AuFCL (talk) 21:10, 10 February 2016 (UTC)

I am a bit lost - mostly because I do not "see" anything wrong (redlinked) at the example DNB page you linked. Can you elaborate? -- George Orwell III (talk) 00:17, 13 February 2016 (UTC)