User talk:Billinghurst

A noun and a verb were dating but they broke up because the noun was too possessive.

	This user has alternate accounts named SDrewthbot & SDrewth.

billinghurst (talk page)

(Archives index, Last archive)

IRC cloak request: I confirm that my freenode nick is sDrewth

Note: Please use informative section titles that give some indication of the message.

Wikisource has a number of active Wikiprojects that could use your help in tackling these large additions to our library. United States Executive Orders Project Work: Portal:Executive Orders of the President of the United States

TO DO — DNB footer initials

• Update docs Done
• Look to manage new, eg. DNB HMS-r
• Work on 1912, check completeness of 1901
• HWP duplicates and will need disambiguating Author:Hugh Wodehouse Pearse // Author:Herbert Woodfield Paul

Support request with team editing experiment project

Dear tech ambassadors, instead of spamming the Village Pump of each Wikipedia about my tiny project proposal for researching team editing (see here: https://meta.wikimedia.org/wiki/Grants:IdeaLab/Research_team_editing), I have decided to leave to your own discretion if the matter is relevant enough to inform a wider audience already. I would appreciate if you could appraise if the Wikipedia community you are more familiar with could have interest in testing group editing "on their own grounds" and with their own guidance. In a nutshell: it consists in editing pages as a group instead of as an individual. This social experiment might involve redefining some aspects of the workflow we are all used to, with the hope of creating a more friendly and collaborative environment since editing under a group umbrella creates less social exposure than traditional "individual editing". I send you this message also as a proof that the Inspire Campaign is already gearing up. As said I would appreciate of *you* just a comment on the talk page/endorsement of my project noting your general perception about the idea. Nothing else. Your contribution helps to shape the future! (which I hope it will be very bright, with colors, and Wikipedia everywhere) Regards from User:Micru on meta.

Perelman School of Medicine at the University of Pennsylvania

Note to self and anyone else interested.

Category:Perelman School of Medicine at the University of Pennsylvania should it be a portal too? If yes, we really need a means to autopopulate (minor) portals so we do not have do lots of work in that space.

If it is not, we need to look to adapt {{authority control}} so it can be utilised with arbitrary access to WD so AC can be filled on such a page. — billinghurst sDrewth 06:26, 20 April 2017 (UTC)

Move template data to WD

Category:Pages using authority control with parameters has pages with {{authority control}} data that should be housed on the WD page of the item. Look to set to utilise PLbot to move the data to WD, save some queries on its use and set up tracking. Need to be a good lad and set up fully-fledged maintenance pages. Oh for more time! — billinghurst sDrewth 06:31, 20 April 2017 (UTC)

https://books.google.com/books?id=F4EsAAAAYAAJ import

import work so we can migrate text French Constitution of 1848

AutoWikiBrowser question...

Hi Billinghurst,

As you may remember from the far off past, I'm working on Volume 33 of the US Statutes at Large. The private acts section in Volume II contains almost endless repetitions of a specific block of boilerplate text: "Be it enacted by the Senate and House of Representatives of the United States of America in Congress assembled, that the Secretary of the Interior be, and he is hereby, authorized and directed to place on the pension roll, subject to the provisions and limitations of the pension laws, the name of " etc., etc. Of course, the actual detail of the target text which ultimately needs to be corrected to the above will contain a potentially massively variable number of errors from Tesseract - and of course because of the pagination of the USStat, some of the sidenotes will usually be blended into the body text, further increasing the automation challenge! I have asked on https://en.wikipedia.org/wiki/Wikipedia_talk:AutoWikiBrowser if this is a use case which might be appropriate for AutoWikiBrowser, but I thought I would ask you if you had any experience of anyone using AWB on WS, and if so whether (if you know anything about it) you thought it would be appropriate for me to try, and, if so, whose consent I would need? I've also left a question for Tarmstro99 on his talk page about whether his bot would be an appropriate alternative means of trudging through this boilerplate, but I think he must be on vacation. Conceptually, I still think that Tesseract should be the right place to do this, but that is way beyond my capacity!!! Thanks CharlesSpencer (talk) 09:49, 17 July 2017 (UTC)

Page watcher jumping in. I have used AWB for a number of almost identical tasks on this very project. In my experience, the best thing to do is to go through a few dozen titles and load up a list of the most common transcription errors, and run that for the entire index. Cheers! BD2412 T 13:33, 17 July 2017 (UTC)

If you have a standard set of text on many pages, I would recommend that we template it. Then we can extract that text with a regex and add the template. Just makes the whol proofreading so much easier. — billinghurst sDrewth 15:27, 17 July 2017 (UTC)

Indeed! That would actually be useful across tens of thousands of pages, since the language at issue is not restricted to this volume. I did a test run of typo fixes with AWB, made 962 edits and barely dented the majority of scannos. BD2412 T 16:22, 17 July 2017 (UTC)

I wrote a template (Template:USStatPension) back in 2010 with your valuable assistance, Billinghurst, and that of George Orwell III, but it's almost as time consuming to use as editing it by hand (with the obvious exception of the numbered section tagging, which the template does do very well). I was looking for a more brute force means of ploughing automatically through hundreds of pages... I suppose what I'm saying is that I would be far happier if the manual intervention was retyping the names of the individual pensioners than if it were manually picking bits of mangled sidenote out of the preceding boilerplate. CharlesSpencer (talk) 11:41, 18 July 2017 (UTC)

Okay, I had a little time today to have a look, rather than just answer out of my (...). Standard AWB is not the answer here as it relies on the internal text, or the right anchors to know the internal text; it may work with an AWB module but you would need someone to build such. If you are saying that you can look at the pages, and take out the variable text for the page, then it is almost something that you can do within a spreadsheet in a columnar form,
scan_page Page_no. Name field1 field2 ...
then inject the template components into the regular intervening points between the columns, then get a bot to take components in order line by line or something interpret and apply per scan_page. For something like that we might be better prodding user:Mpaa for a proper bot. — billinghurst sDrewth 08:51, 19 July 2017 (UTC)

Fantastic! Thank you for looking into it. I had once considered trying to go offline completely and use mail merge through Word and Excel to solve the problem, so I know exactly what you mean, and that is definitely doable from a data extraction point of view. I suspect that chapters broken across pages will still pose a manual problem, but that would be a tiny element compared to the bulk of the chapters being ploughed through by a bot. Let me check in with user:Mpaa and see if he can help. Thanks again CharlesSpencer (talk) 15:11, 19 July 2017 (UTC)

User:CharlesSpencer, let me know if you need help.— Mpaa (talk) 16:32, 23 July 2017 (UTC)

Thanks Mpaa, as soon as I've got a good dataset assembled in Excel, I'll be in touch. Might be a while, though, I'm afraid! Thanks. CharlesSpencer (talk) 06:14, 25 July 2017 (UTC)

Tech News: 2017-30

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• CSS in templates will be stored in a separate page in the future. This will make it easier to make templates look good on mobile devices. This now works on mediawiki.org and Wikitech. It will come to more wikis later. [1][2][3]
• .mw-ui-constructive modifier class is deprecated and has been removed. [4]

Changes later this week

• The new version of MediaWiki will be on test wikis and MediaWiki.org from 25 July. It will be on non-Wikipedia wikis and some Wikipedias from 26 July. It will be on all wikis from 27 July (calendar).
• It will be possible to restrict who can send you notifications on a wiki. This new feature will accessible in your preferences, in the Notifications tab, on Wednesday, July 26. Please see the documentation. [5]

Meetings

• You can join the next meeting with the Editing team. During the meeting, you can tell developers which bugs you think are the most important. The meeting will be on 25 July at 19:00 (UTC). See how to join.
• You can join the Wikimedia Foundation July 2017 Metrics & Activities Meeting. The meeting is about how Wikipedia and the Wikimedia movement are perceived and understood by the world. The meeting will be on 27 July at 19:00 (UTC). See the agenda and how to join.

Future changes

• New Filters for Edit Review, at the moment available as a Beta feature, will be released by default for the Recent Changes in September.

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

15:57, 24 July 2017 (UTC)

Collaboration products newsletter: 2017-07

Latest news from the Wikimedia Collaboration team, about Notifications, Flow and Edit Review Improvements. Please tell other users about these changes. Not all changes will affect you.

What's new?

The team is currently working on three main goals, which we expect to complete this summer or in September:

1. Graduate New Filters for Edit Review core features out of beta:
   • The core New Filters features slated to become standard parts of Recent Changes are the ones that have been out in beta for a while and fully road-tested by the community.
   • These include the new filtering interface, the machine-learning filter groups “User Intent Predictions” and “Quality Predictions,” the highlighting tools, the ability to save your filter settings for later use, and the new filter groups: “Watchlisted pages,” “Last revision” and "User registration and experience."
   • There’s a list of “blocker” tasks we need to complete before these features are ready to graduate out of beta.
   • We expect to release those features by default in September. A more precise message will be sent to communities. If you have questions about it, you can write a message on Mediawiki.org, in any language.
2. Extend the New Filters to Watchlist: The Watchlists of very active editors can include thousands of pages. To help these busy folks keep up with their work, we’re adding the New Filters UX and tools to Watchlist. The Watchlist and Recent Changes pages are similar, but there is some work involved in adapting the tools to their new setting. That work should be ready some time in late summer or early fall. Stay tuned for an announcement!
3. Continuing work on “Integrated Filters”:
   • While the New Filters for Edit Review beta brought probably 70% of the old-style Recent Changes features into the new user interface, it left some behind—like the Tag and Namespace filters and the controls for the number of days searched and number of results presented. As the name is meant to suggest, “Integrated filters” integrates those old-style tools into the new UI.
   • It also adds some new tools users have asked for, such as:
     • “Live updates” which provides a near real-time automatic refresh of the Recent Changes page.
     • Category filters, which enable users to search by category.
     • User filters, which let you define searches that include or exclude edits by particular users.
   • We will put the community-defined related links that cluster at the top of most Recent Changes pages into a collapsible panel, in order to clarify the Recent Changes page.

We should note that it’s not certain these last two additions will make the cut for inclusion this year. If you want a make the case for either one, we want to hear from you.

Edit Review Improvements [More information • Help pages]

Recent changes

• Some styling adjustments are ongoing on the filters for recent changes. [6]
• RecentChanges with the Beta feature were very slow to load on Wikidata. It is now fixed. [7]
• In the Beta feature, you can try the Live Updates feature. Just add &liveupdate=1 at the end of the URL in Recent Changes page. [8]

Future changes

• ORES review tool will be deployed to Romanian and Albanian Wikipedia soon. These wikis will be able to use predictions filters. To have the predictions filters on your wiki, you need to work on the labeling campaign for your wiki or request it. [9]
• Sometimes the RecentChanges page were reloading before the filters have ended to be loaded. It is going to be fixed. [10]

Notifications [More information • Help pages]

Recent changes

• It is now possible to display the number of unread notifications in the browser title bar, using a gadget. [11]

Future changes

• It will be possible to restrict who can send you notifications on a wiki. This new feature will accessible in your preferences, in the Notifications tab, on Wednesday, July 26. [12]
  • The documentation is ready to be translated.

Collaboration team's newsletter prepared by the Collaboration team and posted by bot • Give feedback • Subscribe or unsubscribe.

16:43, 24 July 2017 (UTC)

Index:Goody Two-Shoes (1881).djvu

Firstly, My apologies for an over-reaction to your comments elsewhere.

Moving on, I found that this was one of the first works I contributed to on English Wikisource and was therefore wanting some feedback on how to bring it up to the best standard possible. In reviewing it carefully I am STILL finding some f vs long-s, I'd missed on at least 2 passes, and so am intending to give it a 3rd.

You had validated a page in this work at some point, so I thought I would ask if you were planning on returning to it at some point? ShakespeareFan00 (talk) 21:45, 31 July 2017 (UTC)

Tech News: 2017-31

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Problems

• Some pages show the error Lua error in mw.wikibase.entity.lua at line 34: The entity data must be a table obtained via mw.wikibase.getEntityObject. This problem happens on pages with a Lua module that uses Wikidata. The developers are working on fixing the problem. You can fix a page by opening it for editing and then saving without changing anything. [13]
• Wikidata and German Wikipedia could not be edited for an hour on 28 July. You can read why and how we could avoid it in the future in the incident report.

Changes later this week

• Some wikis already have the larger and brighter OOjs UI edit page buttons. All remaining wikis except Commons will have these from 1 August. [14]
• The new version of MediaWiki will be on test wikis and MediaWiki.org from 1 August. It will be on non-Wikipedia wikis and some Wikipedias from 2 August. It will be on all wikis from 3 August (calendar).

Meetings

• You can join the next meeting with the Editing team. During the meeting, you can tell developers which bugs you think are the most important. The meeting will be on 1 August at 19:00 (UTC). See how to join.

Future changes

• The default font in the edit window will soon change for some users. Instead of using the browser default it will be monospace. Users can change this in their preferences. This should only change this for some users on Macs and iOS devices. [15]

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

21:45, 31 July 2017 (UTC)

Re deleted author page

Hi. The It's a beautiful day story was released under a CC license. It was deleted here because its Spanish counterpart was deleted, but it has since been restored (for several months now). I think it should be restored along with the corresponding author page. I'm sorry if this causes any inconvenience, I don't mean to cause any. --201.215.141.30 02:01, 4 August 2017 (UTC)

The work was deleted as non-notable, not due to any other deletion. The place for the discussion about the work is WS:PD. — billinghurst sDrewth 02:19, 4 August 2017 (UTC)

Page:The Cutter's Practical Guide 1898 Edition Part 1.djvu/28

Thanks for re-reading this. I'd been using {{frac}} for consistency of appearance across the whole work in respect of fractions that didn't have a unicode point.

If you feel this isn't a major issue, is there a script for "regularising" fractions across an entire work? {{frac}} was used extensively in this one, and I had not been changing it.ShakespeareFan00 (talk) 11:56, 4 August 2017 (UTC)

If you want, it is possible. I am unsure about doing it, I have read some concerns on rendering of unicode fractions vs. other methods.— Mpaa (talk) 20:51, 4 August 2017 (UTC)

@Mpaa: why would do some creation of something that may look like something, rather than utilise the actual characters, per Wikisource:Style manual. If we take that path where do we stop? Isn't rendering a browser issue? If you do a copy and paste you get 1⁄3 not ⅓ which is essentially changing the context of the work. That is not a proper transcription. — billinghurst sDrewth 05:11, 5 August 2017 (UTC)

I was just concerned about readability, people read what is rendered. Maybe there is no issue at all with support of these characters in browsers/fonts/devices. As far as copy paste, 1/3 or ⅓ it is always 0.3333... to me. Anyhow, no big deal. If one wants to replace, I can attempt something, sticking to this: http://unicodefractions.com/.— Mpaa (talk) 08:02, 5 August 2017 (UTC)

My point was that it is 3 characters, not the one. — billinghurst sDrewth 11:33, 5 August 2017 (UTC)

Page:Dictionary of National Biography volume 40.djvu/22

This page had a red-linked {{GFRB}} template, which I updated to {{DNB GFRB}}, I hope this was acceptable, as I saw the relevant page in a query I had to find typo templates. ShakespeareFan00 (talk) 13:03, 4 August 2017 (UTC)

Tech News: 2017-32

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• You can now see which Wikipedia language versions are read in a specific country. This tool is called Wikipedia Views Visualized. [16]
• The Architecture Committee is now the Wikimedia Technical Committee. You can read the charter. [17]

Problems

• You can get an email when a page on your watchlist was edited. You can choose not to get emails for minor edits. There is a bug that means that you then don't get an email when someone does a normal edit after a minor edit. The developers are working on fixing this. Until it has been fixed you can activate "Email me also for minor edits of pages and files" at the bottom of "User profile" in your preferences if you want to. [18]
• The thanks button sometimes didn't work for mobile users. This was because of a new bug and has now been fixed. [19]

Changes later this week

• The new version of MediaWiki will be on test wikis and MediaWiki.org from 8 August. It will be on non-Wikipedia wikis and some Wikipedias from 9 August. It will be on all wikis from 10 August (calendar).

Future changes

• Editors and readers who still use Internet Explorer 8 on Windows XP will not be able to use Wikipedia. Internet Explorer 8 on Windows XP can't connect securely to the wikis. When we allow them to do so it means that we get less security for everyone else. If you use Internet Explorer 8 on Windows XP you can install Firefox 52 ESR instead. Around 0.1% of the traffic to the Wikimedia wikis comes from Internet Explorer 8 on Windows XP. [20]
• Links to sections on Wikipedia don't work well in languages that don't use the Latin script. The URL in the address bar in your browser shows Latin characters like .D0.A1.D1.81.D1.8B.D0.BB.D0.BA.D0.B8 instead of the section heading in the wiki's language. Links to sections in non-Latin scripts will be in the script of that wiki in the future. This will happen in the next few months. [21][22]
• Wiki pages printed by the web browser "Print" function will have an updated style. This new style will be similar to the when you download a page as PDF. It will be better at showing tables, infoboxes and headings. [23][24]

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

21:45, 7 August 2017 (UTC)

Tech News: 2017-33

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• Bureaucrats can now set users as confirmed. Previously only stewards could do this on most wikis. Nothing will change for wikis that have previously decided to let administrators set users as confirmed. [25]

Problems

• The symbols in the language list that show that an article is good or featured in that language doesn't work. Links to the Commons category in the sidebar doesn't work either. The developers are working on fixing it. [26][27]

Changes later this week

• The new version of MediaWiki will be on test wikis and MediaWiki.org from 15 August. It will be on non-Wikipedia wikis and some Wikipedias from 16 August. It will be on all wikis from 17 August (calendar).

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

23:28, 14 August 2017 (UTC)

Centering images for mobile view

Is using <center> the best/only current method for correct mobile rendering of centered images? Londonjackbooks (talk) 02:27, 17 August 2017 (UTC)

Just wondering why you would say that rather than use the image position component wiki style [[File:Example.jpg|center]], unless needing to style within a table due to surrounding text. — billinghurst sDrewth 03:56, 17 August 2017 (UTC)

[[File:Example.jpg|center]] does not render as centered in mobile view. [28] Londonjackbooks (talk) 09:09, 17 August 2017 (UTC)

Correction: does not usually render as centered in mobile view. The image in Meynell's Preludes title page is centered (but line spacing is off); the rest of the images within the text are displayed left in mobile view. Londonjackbooks (talk) 10:09, 17 August 2017 (UTC)

Gotcha. There is a whole lot going wrong in mobile view with images and tables having centering removed. Best that it goes back to the community and if the community is not liking it then probably then through phabricator as something addressed to those developers of the skins. — billinghurst sDrewth 23:02, 17 August 2017 (UTC)

Anything I can do? keeping in mind my limited knowledge of magic? Londonjackbooks (talk) 23:11, 17 August 2017 (UTC)

I think that you can do it perfectly. Describe the two situations, and the problem with the mobile view from a visual perspective, and what you would like the solution to be. No requirement to get into the technical components. — billinghurst sDrewth 23:22, 17 August 2017 (UTC)

Sorry to go on, but where should I bring it up? Scriptorium? I will try to address it tomorrow morning. Londonjackbooks (talk) 23:42, 17 August 2017 (UTC)

Yes. — billinghurst sDrewth 01:33, 18 August 2017 (UTC)