User talk:Eliyak

From Wikisource
Latest comment: 7 years ago by Hesperian in topic removal of admin rights due to inactivity
Jump to navigation Jump to search

The Sources and Analogues of 'A Midsummer-Night's Dream'


Thanks for the rename - it looks a lot better in the categories now!--Laverock ( Talk ) 21:46, 16 January 2011 (UTC)Reply

Problematic pages in PotM


Was there alternate copies of the vol. 1 PotM, the pages Page:Ornithological biography, or an account of the habits of the birds of the United States of America, volume 1.djvu/373 and Page:Ornithological biography, or an account of the habits of the birds of the United States of America, volume 1.djvu/374 have a crease/fold on the page and we are going to need to check the text for a few lines. — billinghurst sDrewth 07:49, 9 February 2011 (UTC)Reply

This "woodpecker report" is found in many other "bird books" - the following 2 have the missing content needed for this particular work...
I've taken the liberty of adding the 3(?) ommissions but did not feel comfortable marking it proofread. — George Orwell III (talk) 08:59, 9 February 2011 (UTC)Reply
Sorry for not responding sooner, I was on vacation. I think if the correct text can be linked from the talk page, it can be marked proofread. --Eliyak T·C 22:38, 17 February 2011 (UTC)Reply

Images used in PotM


Wondering if you approve of the derivatives of plate images that I have been touching up for use in this month's PotM... Please let me know if they are acceptable, and whether their placement (and size settings) "in the Main" is also appropriate or not. Suggestions and/or criticisms welcomed! Thank you, Londonjackbooks (talk) 18:39, 14 February 2011 (UTC)Reply

Help with Hebrew


On this page: fr:Page:Dictionnaire de Trévoux, 1771, I.djvu/37 there is some illegible text near the bottom of the right-hand column. I pulled the JP2's and it looks like it could be "Aleph Yod" but I really have no idea if that makes sense in context. It looks like they are discussing the Hebrew and Greek (and to some extent the Aramaic) of Matthew but I can't tell if the characters I think I see make sense. I can post somewhere or e-mail you the single jp2 if you want to see as it's still not all there but what is there is clearer than in the djvu. My French is not at all good, so if you don't know French best to chat with phe or Pathoschild or someone else fluent. Thanks.--Doug.(talk contribs) 21:15, 14 March 2011 (UTC)Reply

Index:Horsemanship for Women.djvu


Could you please put images on the above index, so it can be upgraded to Proofread. --kathleen wright5 (talk) 13:11, 31 March 2011 (UTC)Reply

Done as of 23:13, 14 April 2011 (UTC) --kathleen wright5 (talk) 23:13, 14 April 2011 (UTC)Reply



Thanks for your kind words on my Mishnah work. I've been trying to get to Mishnayot that have some relevance to the weekly Torah parshah. But generally speaking, this is a fine time of year to be filling in Avot. And its contents reward attention. I invite you to join me in that project, if you are so inclined. Thanks again. -- Dauster (talk) 09:46, 1 June 2011 (UTC)Reply

Automatic "Kapitel" Formatting for Jewish Texts


I've posted this question at Dovi's page but seems he hasn't read it yet; perhaps you can help? [1] Namely, is there a way to get automatic "kapitel" styling on our texts, i.e. first word in each paragraph large and bold, as is the traditional print in many Jewish books and this would be in accordance with Wikiproject standards I believe I read that the Wiki text should resemble the original prints as much as possible.

Also re: "{{Hebrewtop}}" and "{{Hebrewbottom}}" formatting such as on [2] it seems to give a nice face to the otiyot however the lines do not wrap, so long lines just run off the page. Any ideas for this?

Thank you! Nissimnanach (talk) 17:44, 20 July 2011 (UTC)NissimnanachReply

Page:Adjustment Team.djvu/1


How about validating the title page? --kathleen wright5 (talk) 08:54, 15 August 2011 (UTC)Reply

Also there's something wrong with page 2 in mainspace. --kathleen wright5 (talk) 09:02, 15 August 2011 (UTC)Reply

Insular script


Do you think it possible to create representations of Insular script using Typography templates? If so or not so, your comments would be welcomed at Wikisource:Scriptorium#Runic like characters — a guide?. ----Gavin Collins (talk|contribs) 17:28, 9 January 2012 (UTC)Reply

You're invited to Wikimedia events in June and July: bot, script, template, and Gadget makers wanted


I invite you to the yearly Berlin hackathon, 1-3 June. Registration is now open. If you need financial assistance or help with visa or hotel, then please register by May 1st and mention it in the registration form.

This is the premier event for the MediaWiki and Wikimedia technical community. We'll be hacking, designing, teaching, and socialising, primarily talking about ResourceLoader and Gadgets (extending functionality with JavaScript), the switch to Lua for templates, Wikidata, and Wikimedia Labs.

We want to bring 100-150 people together, including lots of people who have not attended such events before. User scripts, gadgets, API use, Toolserver, Wikimedia Labs, mobile, structured data, templates -- if you are into any of these things, we want you to come!

I also thought you might want to know about other upcoming events where you can learn more about MediaWiki customization and development, how to best use the web API for bots, and various upcoming features and changes. We'd love to have power users, bot maintainers and writers, and template makers at these events so we can all learn from each other and chat about what needs doing.

Check out the the developers' days preceding Wikimania in July in Washington, DC and our other events.

Best wishes! - Sumana Harihareswara, Wikimedia Foundation's Volunteer Development Coordinator. Please reply on my talk page at Sumanah (talk) 01:11, 9 April 2012 (UTC)Reply

Help with Hebrew



May I prevail on you to check Page:Eight chapters of Maimonides on ethics.djvu/178 please?

Hesperian 12:04, 29 June 2012 (UTC)Reply

Thanks! Hesperian 13:44, 29 June 2012 (UTC)Reply

I just discovered {{Hebrew missing}} and Category:Pages with missing Hebrew characters! Hesperian 07:58, 30 June 2012 (UTC)Reply

I see my work is cut out for me! --Eliyak T·C 04:48, 1 July 2012 (UTC)Reply

Progress on search results?



I've been mindful of your comment in passing about how we should see positive search engine results in about two weeks or so but I've been like crack addict ever since our "break-through", checking daily for any change(s). Well today there was a dramatic jump in the number of entries containing the '- Wikisource, the free online library' tag-line. A search for "Leo_Tolstoy" now comes up (for me) on the 2nd page at roughly the 19th hit returned as well. The cached entry for Leo_Tolstoy shows June 28th and that one still has the Author: prefix in the title tag to boot. Hoo-ray!!!

After looking over the pages and pages of the new results, I'm not so sure including the tag-line for all the namespaces and associated talk pages is beneficial, desired or even warranted by the community at large. What are your thoughts about limiting the tag-line to just the 3 primary namespaces promoting works or relevant subdirectories to works (the main, Author: and Portal: + maybe Category: & File: as well)? Primarily, I'm not so sure the tag-line is a welcomed addition to User: accounts & their talk pages without actually asking for some sort of community consent first, but also don't see how it helps the remaining namespaces, such as Template: or MediaWiki:, used for the most part just to facilitate the operation of content in the primary and sub-primary namespaces. So am I being too uptight about this? Appreciate your thoughts in advance. -- George Orwell III (talk) 23:12, 5 July 2012 (UTC)Reply



Eliyak, thanks for your sterling work on matching vol 3 of 1001 nights. As you might guess I'm experimenting on this because it's a good example of a book in a mess, though a bit larger than sensible for an experiment. I see your fixes to the page took about 45 minutes which is encouraging for a text of about 350 pages. Doing the identification of page-breaks offline takes me at least 35 seconds per page so that's a 5 times speedup. Of course there are bugs in the routine so they need to be fixed first. And I haven't yet tried stage 2, the Split, which is supposed to take longer. I see Phe hasn't made any changes since April so I don't know who looks after the code. Do you know where the code is? Chris55 (talk) 08:04, 14 July 2012 (UTC)Reply

Header template


Eliyak, I'm getting template errors on The Book of the Thousand Nights and a Night/Volume 3/ab and I wonder if your change to put in 2 extra headers has anything to do with it. I thought there was a strict limit on the number of compulsory args to avoid all sorts of errors in editing old headers. Chris55 (talk) 16:13, 15 July 2012 (UTC)Reply

huh, I can be as blind as any bat! Thanks. Chris55 (talk) 16:26, 15 July 2012 (UTC)Reply

Page Triage


Have you looked over the new patrolling feature I proposed us enabling at the Scriptorium? It does not interfere with the current method of patrolling so no one would be forced to switch if it were brought in. --BirgitteSB 01:31, 19 July 2012 (UTC)Reply



Eliyak, You may see on the MOTM page that I've finally come round to your campaign for categorising, albeit with a difference. However I've realised that I can't get the sort of information I want using the standard interface to WS and wonder what the way ahead is. One seems to be by getting a proper account on the toolserver but I've also heard about other sort of shell access to the wikis. Are these different or the same thing and which is the way to go? I've used the toolserver once or twice via their query server but that's not very satisfactory. Also do I need support from another user? Chris55 (talk) 16:41, 30 July 2012 (UTC)Reply

Social media & Tumblr


With regards to Wikisource:WikiProject Social media and your transitional government, I was wondering if we should set up a Tumblr page for English Wikisource. (Probably "" or "".) It seems like an easy way forward for social media and Wikisource outreach. We could start somewhat slowly with maybe a post every one or two weeks: things like the featured text, the proofread of the month (and its conclusion). We can use the tumblr for these kinds of project announcements to begin with, maybe adding quick posts for new texts when they're added to the main page list. If it's successful, we can expand on the posts (perhaps soliciting suggestions on the project talk page). Do you think I/we should go ahead with this? - AdamBMorgan (talk) 21:52, 17 September 2012 (UTC)Reply

Trial run now operating: When you get back to Wikisource, I will add you as a Tumblr admin per the WikiProject. - AdamBMorgan (talk) 19:31, 8 October 2012 (UTC)Reply



Any chance you could try and work out a way to format this using your music template?

(One thing that's missing from your template set is 'signatures' both time and key.) IMG (talk) 12:41, 30 September 2012 (UTC)Reply

format page


Hello Eliyak! Kind person, please format your pages before saving so that the m-dash connects to the words around it. Okay? Happy New Year 2013! —Maury (talk) 06:21, 2 January 2013 (UTC)Reply

I agree with your view 100 percent. I was doing the same as you because it looks better to me. I was just told to do different. I have been validating your pages and naturally I followed that rule (?). It's no big thing either way imho. Have a great New Year. —Maury (talk) 06:44, 2 January 2013 (UTC)Reply

Wikisource User Group


Wikisource, the free digital library is moving towards better implementation of book management, proofreading and uploading. All language communities are very important in Wikisource. We would like to propose a Wikisource User Group, which would be a loose, volunteer organization to facilitate outreach and foster technical development, join if you feel like helping out. This would also give a better way to share and improve the tools used in the local Wikisources. You are invited to join the mailing list 'wikisource-l' (English), the IRC channel #wikisource, the facebook page or the Wikisource twitter. As a part of the Google Summer of Code 2013, there are four projects related to Wikisource. To get the best results out of these projects, we would like your comments about them. The projects are listed at Wikisource across projects. You can find the midpoint report for developmental work done during the IEG on Wikisource here.

Global message delivery, 23:21, 24 July 2013 (UTC)

Commons File Update


I updated the Commons file here at Commons (new file has eyes), but the updated file does not show on Wikisource. Does it take time? Or did I do the linkage wrong? Nissimnanach (talk) 19:31, 22 October 2013 (UTC)NissimkaufmannReply



...for your trust. ~ DanielTom (talk) 20:59, 25 September 2013 (UTC)Reply

You seem to know your way around...


...javascript; could I impose upon that knowledge and ask you a thing or two about a section in our MediaWiki:PageNumbers.js file??
specifically the function add_page_container() part copied to the window below.....

function add_page_container(){
        if(wgNamespaceNumber!=0 && wgNamespaceNumber!=114 ) return; 
        var id = null;
        if(wgAction=="view"||wgAction=="purge") id = "#bodyContent"; 
        if(wgAction=="submit") id = "#wikiPreview"; 
        if (!id) return;
        if( document.getElementById("text-wrap") ) return;

        if(wgNamespaceNumber!=114 ) { if( !self.proofreadpage_source_href && get_elements_by_classname("pagenum","span").length==0 ) return; }

	var t = get_elements_by_classname("text","div"); 
        for(var i=0; i<t.length; i++)  t[i].className =""; 
        t = get_elements_by_classname("lefttext","div"); 
        for(var i=0; i<t.length; i++)  t[i].className =""; 
        t = get_elements_by_classname("centertext","div"); 
        for(var i=0; i<t.length; i++)  t[i].className =""; 
        t = get_elements_by_classname("indented-page","div"); 
        for(var i=0; i<t.length; i++)  t[i].className =""; 
        t = get_elements_by_classname("prose","div"); 
        for(var i=0; i<t.length; i++)  t[i].className ="";

        $('div#contentSub').nextUntil('div.printfooter').wrapAll("<div id='text-wrap'><div id='text-container'><div id='text'></div></div></div><div style='clear:both'></div>");

I'm mostly concerned with the second to last line setting up the .prepend (more on that later) but for starters can you just look over the section in general and make sure we're not handicapped through scripting neglect or something?

For instance, shouldn't if(wgNamespaceNumber!=0 && wgNamespaceNumber!=114 ) really be if(wgNamespaceNumber == 0 || wgNamespaceNumber == 114)??? (again - I have no clue but "&&" seems to indicate an "and" condition when it should be either namespace --> "||" = "or" <-- no?). Anyway, I'm worried the script is outdated and needs tweaking/cleaning/etc.

If this is not your bag, then please do not worry about and forget I asked. Thanks either way. -- George Orwell III (talk) 02:10, 26 October 2013 (UTC)Reply

Well, I must give credit where credit is due - You Da' Man !!!!!! Since the switch to load during vs. afterwards, everything is as I had hoped for & more. Two points remain outstanding - ones that weren't part of the original .js but were haphazardly added as gadgets when they didn't work in the old ThomasV development.

  1. While some folks like (or have blindly accepted?) the gray-highlight feature, the option to disable it via it's gadget (adds self.proofreadpage_disable_highlighting = true; to User:s local common.js file) seems kind of overkill. For example, I prefer to disable it because, more often than not, the end point or points are beyond the viewable screen area anyway; requiring a scroll and losing the mouseover in the process. Is there anyway to make life easier and have the enabling/disabling of the highlight feature part of the left-hand side's Display options menu as a toggle like 'Show / Hide page links' currently are?
  2. Generally the same issue as above but with the enabling of inline page links rather than the usual forced margin display (self.proofreadpage_numbers_inline = true;) instead. It seems to me making a toggle switching between inline & marginalized page links also under the Display options menu would be better than the current option of adding it via Gadget (if it can be done that is).

I'd also like to note that under the current PageNumbers.js with inline page links enabled, the automatic disabling of what of course would be the redundant gray-highlighting feature still takes place as it did before but the hide/show toggle has no effect on the inline links whereas (at least for me) this was only mode where hide/show actually worked before undertaking the optimizations over the past week or so.

I hope this can be fixed - where hide/show works regardless of marginalized or inline page links being selected & in use.

TIA (really - you have no idea how long & how much this file has driven me nuts; thanks again). -- George Orwell III (talk) 22:08, 8 November 2013 (UTC)Reply



Hi Eliyak, I'm writing to you as you made the last edit to the page Template:Translation_header. The fields do not include one for translator, and the article says the translator will automatically be assigned the value "Wikisource." But further below in the Template:Translation_header#JavaScript_extraction section it does have a field for translator that seems to be variable. Should Translation works indeed have the translator specified? Nissimnanach (talk) 18:31, 28 October 2013 (UTC)NissimnanachReply

PageNumber.js backgound info


Saw some of the remarks to yourself and figure I'd try to fill in the blanks or layout the history for you so you can move forward with removing the crap that no-longer/never served a purpose.

The first thing you should know is that the reason there are three wrapping DIV containers instead of just the "logical" two (1 for floating page link 'columns' &/or floating navigation headers and another for the actual content transcluded in from the Page: namespace) is because the DIV block that we have today - assigned the id mw-content-text & class mw-content-ltr (or rtl for right to left languages) - did not exist in the skin.php(s) generating the basic layouts at the time of roll-out. More percisely, the DIV existed but had no class nor id given to it. This caused all sorts of headaches for ThomasV because he did not seem to know how to manipulate that 'naked' DIV; instead he worked around it (to put it nicely).

This is why the header template was wrapped in its own DIV and assigned the id headertemplate and the original wrapping scheme started with a DIV outside of the edit-box (DIV#contentSub) and ended with the CAT bar divs. This was contrary to what was first "advertised" prior to roll out - things like the navigation header, it's footer, any license banner(s), the later VIAF info-bar and the ever present category bar were all not suppose to be subject to Dynamic Layout resizing (why should they be? They are suppose disappear on User print and in Book compilation/creation anyway). But since he couldn't manipulate that 'naked' DIV block, DIV#text-wrapper became the faux substitute for what is properly DIV#mw-content-text today. ThomasV pretty much left the project soon after - never bringing the DIVS into alignment nor as was originally advertised all this time. In short, the concept really only needed 2 DIV wrappers to work - DIV#text-wrap, the faux DIV#mw-content-text, was relegated to just setting up position:relative; margin-left:3em; for the other two DIVs that followed it.

Second, the only reason those classes are stripped prior to being 'wrapped-up' is to avoid some long resolved margin setting inheritance problem. Anybody who used inline styles rather than those 4 or 5 defined classes always had their settings incorporated into the default Dynamic Layout settings & quickly learned it was better to stop adding custom settings (Dynamic layouts did not play well with some User: prefered settings at all - the Statutes at Large project comes to mind).

So while the practice of adding any of those DIVs with classes that now get stripped has pretty much stopped, its best to keep the stripping function in there just to cover any grandfathered-in old works that still have them.

Hope that helps. -- George Orwell III (talk) 06:12, 10 November 2013 (UTC)Reply

Thanks GO3, that's useful to know. --Eliyak T·C 06:27, 10 November 2013 (UTC)Reply

what does the match= parameter do?


Another unfinished bit to this fabulous disaster - Side-by-Side now DoubleWiki. Thankfully, it was pruned from the ProofReading scheme (the best that I could tell that is) and made into its own extension. I believe the Bilingual_link(?) portion in our MediaWiki:Common.js file is still integrated with it somehow (another "pushed upgrade" that should have been made an optional Gadget for Users rather than universal, imho).

In a nutshell, it allows side-by-side viewing of a single work in English and some other language's version at once. See it in action...

... and since standards & practices on the most basic of transcription elements currently vary from domain to domain - this too is only useful to the folks who contribute a work in more than one language domain themselves.

Personally, I have yet to find a work that actually renders usefully from one column to the other all the way to the end - usually the offset between the two versions becomes so great, one or the other scrolls out of screen view or, even better, one language has all the chapters on one mainspace page while another has broken the chapters out onto their own subpages.

The concept seems sound however, but without any real coordination, its not very useful (thank God its a stand-alone, again, as far as I can tell - seperate from the current PR regime). Just note that it seems like it was actually part of this mess - to what degree & when; I cannot say. -- George Orwell III (talk) 07:00, 10 November 2013 (UTC)Reply

following you along is like


... a private lesson in scripting :) I'm picking up more about JQuery just following you along than any website ever did - that much is for sure!

Anyway, I've loaded your test script and thought I better remind you of a thing or two now that I just remembered them myself.

First, I'm pretty sure I recall Tpt (maybe even ThomasV) say there is something (or some things?) that are not exactly 100% the same when testing PR extension/DynLayouts in namespaces other than the main namespaces - like the current subpage(s) of your User: space hosting the testbed example(s). I believe that this is/was the case due to certain css/php settings only "pointing" to elements & their attributes as defined specifically for instances detected in the main namespace only. This imbalance was probably compounded further by the recent introduction of the Translation: mainspace, but that is most likely a seperate issue than the current goal here.

I understand testing in the User: was unavoidable but I figure best mention the possibilty that even once your done "testing" to your satisfaction & move your .js to the MediWiki space - you should not be surprised if bits & pieces don't work the same as they did under your User: space. -- George Orwell III (talk) 23:07, 12 November 2013 (UTC)Reply

Probably also a private lesson in how many little mistakes one can make in scripting! I'm learning a lot myself, too. My main sources are and google generally. I know things will be different "in production," but hopefully not too different. Also, since it seems that private JS loads before the public JS, I should be able to do a "private screening" before going live.

Second, I was wondering to myself how MediaWiki:Proofreadpage pagenum template fits into the ongoing process of development/testing - not that I understood how or why it was put into play by the PR extension before these latest refinements began either - but I was always concerned that this template existed ontop of the stuff already coming down from the extension's php files & in addition to any of the supporting scripts like PageNumbers.js called "locally". Isn't this faux-template "getting in the way" at this point of your attempted overhauls? (of course, I could be totally off-base in my assumption here.) Thanks again & please reply, if at all, only when you have the time & the urge. No problems with that on my end. -- George Orwell III (talk) 23:07, 12 November 2013 (UTC)Reply

I think the "template" is necessary to some extent, since it is used by the Proofreadpage extension directly, and the information it pulls in is necessary to have in *some* format. JS can't bring in that info unless it's already on the page ("in the DOM"). So the template actually gives us more control by giving the ability to modify the format of that HTML without actually going into the extension PHP code. --Eliyak T·C 01:49, 13 November 2013 (UTC)Reply
18 Novemeber

It seems your changes work well enough in that nobody has "complained" about anything to date. I've also put dozens and dozens of examples to task under the changes and, again, all seems just fine -- save that one text character offset thing at the first-child of the div_highlight container. At least for me, after the first embedded page link transcluded "in" from the Page: namespace, every mouseover activating the gray highlight field(s) start at the wrong position (always 2nd text character from the left of the start of the target word where a page break exists). The last (or third child) always ends properly when the page break occurs between paragraphs or with a 'space' when the page break occurs mid-paragaph.

This leads me to believe the 1 character offset is somehow tied to the automatic space insterted at the end of one page being transcluded in and the start of the following page being transcluded in & not so much with anything in the .js itself (I've tinkered with the "math" found in the first child of the container in PageNumbers.js with no change; still off by one). This "theory" is supported by the instances where the templates for hyphenated word starts & ends are put to use across page breaks within a paragraph spanning more than 1 page. The highlight feature is unable to process this and the highlight ends & starts at the begining of the word rather than at the point where the now mainspace removed hyphen is suppose to be in the Page namespace.

Anyway, if this one character offset thing can be overcome (?refresh offsets way after the end of last transcluded page inserts all those extra spaces [only to strip them down to just a single space @ final rendering] maybe?), your refinements work perfectly!! -- George Orwell III (talk) 03:19, 19 November 2013 (UTC)Reply

The hws/hwe issue is because hws does not actually transclude anything from the first page, and it is hwe that shows the full word. The reason is that as you have noted, MediaWiki inserts a space between pages.
In other news, I think I may have fixed your problem (an IE8 bug?). Let me know if my latest edit did the trick. --Eliyak T·C 04:35, 19 November 2013 (UTC)Reply
Sure did!... Perfect. -- George Orwell III (talk) 05:47, 19 November 2013 (UTC)Reply

Hey again,

I've been seeing a lot of folks claiming when they 1st click-in to a transcluded page, they are automatically seeing the page in Layout 2 when no forcing of Layout 2 is present. Could this behavior be caused by the cookie thing you added at the begining of MediaWiki:PageNumbers.js?

I'm about to remove it (since it says remove after a week or so anyway) but I'm hoping I don't botch things up on top of wondering if could possibly be the cause of the "skipping" of Layout 1 thing some folks are seeing? Thanks for your attention (& sorry for being a pain). -- George Orwell III (talk) 00:41, 19 December 2013 (UTC)Reply

TOC limit Template


w:Template:TOC_limit doesn't seem to work: see Chayey Moharan. Thanks! Nissimnanach (talk)Nissimnanach

Abracadabra hocus pocus! --Eliyak T·C 04:58, 25 November 2013 (UTC)Reply

Thanks, it's beautiful! Nissimnanach (talk) 17:18, 25 November 2013 (UTC)NissimnanachReply

Hmm -- worked before; appears to have reverted and it's not working. ? Nissimnanach (talk) 03:01, 11 December 2013 (UTC)NissimnanachReply

Looks good on my end... --Eliyak T·C 01:26, 19 December 2013 (UTC)Reply

Rename template doesn't work


Please see Kitzur_Shulchan_Aruch -- the

{{rename media|newname|reason}}

w:Template:Rename_media template from Wikipedia does not work. Gracias! Nissimnanach (talk) 18:02, 9 January 2014 (UTC)NissimnanachReply

Fyi on main page css


Actually, MediaWiki:Common.css/Mainpage.css held the stuff for the main page formatting but since none of it seem to apply anymore, it was no longer called to be loaded (I could be wrong about that however). Either way, you should revive that css instead of lumping it with the rest of the "orphans" imho. -- George Orwell III (talk) 06:26, 24 January 2014 (UTC)Reply

Sounds right to me. I'll leave it as is until it gets promoted to actually being used on the main page. --Eliyak T·C 06:28, 24 January 2014 (UTC)Reply

Question about your reorganization at



I see you have reorganized the pages at this work by adding them to "Translation:". I added "Translation:" to the sub pages so that the linking would work. Two of the links do not seem to go to their sub pages. Would you know what happened to these sub pages? Did they get orphaned somewhere?

Thanks, Shemindex (talk) 14:49, 17 February 2014 (UTC)Reply

Thanks for cleaning up my mess. I'm thinking that those pages may never have been created; as you can see, the text is not complete in any case. If you think this is not the case, let me know. --Eliyak T·C 02:29, 18 February 2014 (UTC)Reply
I was not the user who started chapter 3 so maybe that was never created. I am relatively sure that I translated chapter 432 since I see that I started 433. Shemindex (talk) 17:10, 19 February 2014 (UTC)Reply
I did some searches, and was unable to find either chapter 3 or 432, even when I looked through all deleted pages starting with "Aru". I did see that you created 431 in July 2012, but 433 in July 2013. I'm not sure, but I can't find any evidence of either page being started... --Eliyak T·C 22:33, 19 February 2014 (UTC)Reply
Thank you for checking. Sorry for the bother, I must be mistaken. Shemindex (talk) 01:31, 24 February 2014 (UTC)Reply

Gadgetize a magicword?


Do you know if it is possible to "load" a magic-word on every page I view via a Gadget or something?

The magicword I'm most thinking of is ( {{noexternallanglinks}} ). It retards the generation of interlinks from Wikidata on any page where such links exist. -- George Orwell III (talk) 02:24, 2 March 2014 (UTC)Reply


Hi again,

When you have some time, could you please review/revise the "cookie" relationship between MediaWiki:Base.js and MediaWiki:PageNumbers.js now that the former is no longer being loaded from old.wikisource. Call me crazy, but the whole approach to creating the Display options portlet seems contrary to the way collapsible nav panes are setup in the Skins, collapsibleNav.js.

At the very least, what is started in Base doesn't seem optimal when continued in PageNumbers. -- George Orwell III (talk) 11:03, 26 March 2014 (UTC)Reply

Shulhan Aruch


I see that you did some editing of the shulhan aruch a couple of years ago. Thought you might like to know that there is a site which has a basic translation which could be used as an editing baseDfrankfurter (talk) 05:01, 31 May 2016 (UTC)Reply

removal of admin rights due to inactivity


Hi Eliyak,

The consensus at your annual admin confirmation is that your rights be removed due to inactivity. If you should return to the Wikisource soon, you may request immediate restoration of your admin rights. Sorry to have lost you from the site; I hope you're well and enjoying life. Thanks for all your contributions! Hesperian 04:42, 1 March 2017 (UTC)Reply