From Wikisource
Jump to: navigation, search
Warning Please do not post any new comments on this page. This is a discussion archive first created on 01 February 2018, although the comments contained were likely posted before and after this date.
See current discussion or the archives index.

Strange business with Eleven years in the Rocky Mountains and a life on the frontier[edit]

I have a strange situation with Eleven years in the Rocky Mountains and a life on the frontier. Following a Match & Split on Chapter III, the page itself seems to still have the text of the entire book on it; however, when I click "edit" I see only a pages index going up through page 23, and no further text on the page after that. I've tried two different browsers, and tried viewing while logged out, so I don't think the issue is specific to me. I also tried purging the cache, to no avail. Any ideas what's going on and how to fix it? -Pete (talk) 18:35, 1 February 2018 (UTC)

Yes check.svg Done Sorry, it was a simple issue...the M&S process had stuck all the extra text on the last page it matched. On the path to fixing it up now... -Pete (talk) 18:56, 1 February 2018 (UTC)

OCR scan is all over the place[edit]

I have read Help:Beginner's guide to proofreading#Common OCR errors but I don't see this error addressed. I am trying to finish A Plea for Vegetarianism and Other Essays and the OCR scan has virtually random word placement. E.g. my next page scans as:

still it

absolutely certain (and this


resource, the great irrefragable



intellectual vigour,

may be





etc. This is maddening. Why does it have this garbled text and how do I fix it so that I can just make small changes to a correct OCR scan instead of retyping the entire work by hand? I have encountered this before with some works I have transcribed (e.g. Aucassin and Nicolette (Bourdillon)) but not others (e.g. The Autobiography of a Catholic Anarchist, Original Stories from Real Life, and Pulchrism: Championing Beauty as the Purpose of Art). A fix to this will save me hundreds of hours of work.—Justin (koavf)TCM 04:57, 3 February 2018 (UTC)

Your editing toolbar should have an OCR button. Click on it and it will give you a much better OCR. Jpez (talk) 05:25, 3 February 2018 (UTC)
Wow. I could kiss you. Thanks, Jpez. —Justin (koavf)TCM 05:50, 3 February 2018 (UTC)
And if that OCR button doesn't give good results, you could also try the Google OCR button: oldwikisource:Wikisource:Google OCR (uses a different OCR system; other than that it's identical in fuction). Sam Wilson 07:39, 3 February 2018 (UTC)
I actually couldn't get the button to display on Do you have any idea why that is? I unselected it and selected it again in my Preferences but it doesn't show up in the Page: namespace for me. —Justin (koavf)TCM 15:08, 3 February 2018 (UTC)
if you go to "preferences > gadgets > Editing tools for Page: namespace", there is a box to check. it stopped working for some preferences for me, but is working now. Slowking4SvG's revenge 00:58, 4 February 2018 (UTC)
That's what I did in my comment above. I'll try again. —Justin (koavf)TCM 05:00, 4 February 2018 (UTC)

Editcount and checkboxes from editing screen displayed awkwardly[edit]

The edit count is outside the subject bar, which is shorter than other wikis. Also, the checkboxes, like "Watch this page", are pushed right by one inch. I filed a Phabricator task (phab:T186442), which is closed as "invalid". The issue turns out to be a local wiki one and that MediaWiki:Gadget-enws-tweaks.css should be fixed, adjusted, or something. I inserted the screenshots at the task; you can go there and see. George Ho (talk) 21:51, 4 February 2018 (UTC)

@George Ho: Please feel welcome to amend your special:mypage/common.css file for the class if it is a problem for you. I am not sure that it is problematic, though we can put it into the review mix. — billinghurst sDrewth 23:21, 4 February 2018 (UTC)
Created my own "common.css". However, what about others using English Wikisource? Other language sites of Wikisource don't have custom-made similar to this, right? George Ho (talk) 23:36, 4 February 2018 (UTC)
Yeah, I said that we would put it in for review (which has been done on css talk page), and as it was a purposeful change at some point reacting to a report alone is not good process. Your report seems to be look alone; nothing that you have said says it has broken functionality. What other sites do, or don't do, is mildly informative, not normative. — billinghurst sDrewth 00:19, 5 February 2018 (UTC)

Proposal for keyboard shortcuts[edit]

I prefer to edit with the keyboard, so shortcuts like "Alt+Shift+E" to edit are valuable. In the Page: namespace, we don't have shortcuts for navigating pages. I'd like to propose that we 1.) add these and 2.) that they should be "Alf+Shift+→", "Alf+Shift+←", and "Alf+Shift+↑", for navigating forwards one page, backwards one page, and to the index. I want to get community feedback and consensus before going to phab:. Thoughts? —Justin (koavf)TCM 19:08, 4 February 2018 (UTC)

I edit mostly on a Macintosh, which has no "alt" key. I sometimes edit from a PC whose keyboard has no arrow keys. Keyboard shortcuts are not likely to be implemented like this when they apply to a single project and cannot be universal. --EncycloPetey (talk) 20:29, 4 February 2018 (UTC)
@EncycloPetey: In yet other systems, e.g. MacOS, the access key is the combination of the control and option keys. In this case, as above, hold down both keys together and then press the shortcut key. I can confirm--I've used them before. There is a MacOS or OS X equivalent to the Windows-style keyboard shortcut. Do you have a suggestion for different keys? —Justin (koavf)TCM 20:39, 4 February 2018 (UTC)
No, I do not. But then I don't think this proposal is necessary or beneficial. --EncycloPetey (talk) 20:40, 4 February 2018 (UTC)
@EncycloPetey: Any more or less so than the other keyboard shortcuts or are your objections basically irrelevant to this particular proposal? —Justin (koavf)TCM 20:51, 4 February 2018 (UTC)
I use keyboard shortcuts to copy, paste, and enter diacriticals all the time. My personal experience causes me to strongly dislike any keyboard shortcut that causes the current page to change. I have lost count of the number of times I have been robbed of much difficult editing, all because some accidental keyboard combination moved me to a new page in the middle of editing. --EncycloPetey (talk) 20:54, 4 February 2018 (UTC)
@EncycloPetey: Fair enough but since you're saying 1.) that you don't use shortcuts and 2.) you are in zero danger of accidentally pressing them, then while your perspective is valuable as far as it goes, it's not really that germane here as the change would have no impact on you and I'm not seeing how it's a possible site-wide problem anymore than any other shortcut (in fact, much less since there is less of a prospect of pressing those buttons accidentally). Anyone else? —Justin (koavf)TCM 21:03, 4 February 2018 (UTC)
No, that's the opposite of what I'm saying. --EncycloPetey (talk) 21:55, 4 February 2018 (UTC)
@EncycloPetey: So you do use MediaWiki shortcuts and there is a high likelihood that you would press "Alf+Shift+↑" on a keyboard that lacks those keys? —Justin (koavf)TCM 04:09, 5 February 2018 (UTC)
I'm sorry that you are not able to understand what I've been saying, but at this point I don't think it's worth my time to continue trying to explain. --EncycloPetey (talk) 04:12, 5 February 2018 (UTC)
@EncycloPetey: Well, thanks again for your perspective. I hope that we can enable shortcut keys for myself and other users who find them more accessible (e.g. those who have difficulty with fine motor skills). If you have some misgivings about these, you can post them elsewhere and maybe it will be more intelligible. —Justin (koavf)TCM 05:52, 5 February 2018 (UTC)
  • Pictogram voting comment.svg Comment All of this relates to mw:extension:ProofreadPage, so probably is best put into and discussed in a phabricator: ticket. It effects all uses of ProofreadPage at all wikisources, in all languages, so even deciding a letter based on English words is presumptive. — billinghurst sDrewth 21:31, 4 February 2018 (UTC)
    As background for a phabricator request, please refer to mw:Help:Keyboard shortcuts. These shortcuts have been around for donkey's years, so the accidental usage of shortcuts in general is unlikely; and generally you are more likely to be trying to save a page, and start to delete it,—BTDT, worn out the t-shirt—which is easily recoverable. — billinghurst sDrewth
    @Billinghurst: Sure, but I wanted to get feedback first to see what other users thought here. I'll open the ticket. phab:T186478. —Justin (koavf)TCM 04:09, 5 February 2018 (UTC)
  • Access keys for page forward/back notwithstanding, here is something that might appeal to people who dislike mouse navigation: User:Inductiveload/quick access.js. It collects all the toolbar and tab links into a single dialog and allows you to filter them and activate with the keyboard. Add the following to your user JS: mw.loader.load('//');. You can invoke it with the "A" access key (so Shift-Alt-A in Firefox). Inductiveloadtalk/contribs 12:11, 5 February 2018 (UTC)

Wikimania 2018 call for submissions now open[edit]

On behalf of the program commmittee of Wikimania 2018 - Cape Town, we are pleased to announce that we are now accepting proposals for workshops, discussions, presentations, or research posters to give during the conference. To read the full instructions visit the event wiki and click on the link provided there to make your proposal:

The deadline is 18 March. This is approximately 6 weeks away.
This year, the conference will have an explicit theme based in African philosophy:

Bridging knowledge gaps, the ubuntu way forward.

Read more about this theme, why it was chosen, and what it means for determining the conference program at the Wikimedia blog. Sincerely, Wittylama 08:22, 5 February 2018 (UTC)

Tech News: 2018-06[edit]

20:51, 5 February 2018 (UTC)


  • The new Wikidata tracking category will appear in Special:TrackingCategories, I couldn't find a specific reference to its name so we will have to look at that when it is rolled out. — billinghurst sDrewth 21:54, 5 February 2018 (UTC)