User talk:Dairy501/Archive 1

Thank you for joining the Guild!
Hi Dairy501, Thank you for joining the Guild of Copy Editors. I just wanted to say how impressed I was that you tackled a giant article right away, and did a good job editing it. Keep up the good work! Tdslk (talk) 22:20, 3 July 2017 (UTC)

Copy edit review
Hi! I've been randomly picking articles from the July drive to check, and ended up picking your longest one, Steam locomotive. I won't complain, though, I know it took you a lot longer to copyedit it. BTW, very impressed that you took on so many long articles. If you haven't read it already, please take a look at WP:LENGTH for some issues that are frequently seen in long articles.

There were only one or two little things that I would consider "wrong", and easily overlooked on an article of this size. Most of this is nit-picky little things that it would need to pass a good article review. These are things you should try to keep an eye on, but I think everybody misses a little of it. The more you look for this stuff, the easier it'll be to spot and fix it.

So, here are my notes:
 * Wikipedia likes to hyphenate compound modifiers for ease of reading (MOS:HYPHEN). Try to consider clarity issues when placing such hyphens. e.g:
 * edge railed rack and pinion Middleton Railway &rarr; edge-railed rack-and-pinion Middleton Railway
 * Another well known early locomotive &rarr; Another well-known early locomotive
 * a domestic locomotive manufacturing industry &rarr; a domestic locomotive-manufacturing industry
 * pressurised partially water filled area &rarr; pressurised partially water-filled area (words ending in -ly do not need a following hyphen)
 * hot mineral concentrated water &rarr; hot mineral-concentrated water
 * heavy duty chemical water treatment &rarr; heavy-duty chemical water treatment (I feel like water-treatment might also be hyphenated to tighten its association from chemical.)
 * efficient spark arresting device &rarr; efficient spark-arresting device
 * long distance warning &rarr; long-distance warning
 * narrow gauge railway &rarr; narrow-gauge railway (though I know some train-spotters don't care for that)
 * be wary of commas separating compound modifiers:  long, rigid-framed designs &rarr; long rigid-framed designs
 * There was also a tricky one involving a conversion: the only 3 ft 6 in (1,067 mm) gauge engines. The numbers, units and gauge are part of a compound modifier describing engines.  The measurement is generated with  which a customized call to .  I recoded it in convert to produce: 3 ft engines.
 * punctuation
 * Added a few commas, removed one loose comma. Watch for sentences starting with "In".
 * spelling
 * one feed water &rarr; feedwater
 * captions – not everyone copy edits captions, but it's usually simple cleanup work. The main things to watch for are over-capitalization and unneeded terminal punctuation on sentence fragments.
 * Captions should be descriptive but brief; there were a couple that I trimmed as too long (eg: 67 words). Particularly if there's a link, readers can follow that for more information.
 * Manual of Style
 * Year ranges – in prose, two-digit ending years can be used for consecutive years (MOS:DATERANGE), but more often this is used for regular periods of a year or less which overlap a calendar year, such as the winter of 1812-13 or fiscal year 1812-13, also commonly with sports seasons and television seasons.
 * The first practical steam locomotive was created in 1812–13. If this is something like the winter of 1812–13 or fiscal year 1812–13, that should be specified.  If the year is uncertain, it should probably be "created in 1812 or 1813".  If it was built over a two-year period, then "created in 1812–1813" is a little clearer, I think.
 * Puffing Billy, built 1813–14 by engineer William Hedley. – the Puffing Billy article says it was built in 1813, for what that's worth.
 * Algebraic variables should be italicized but instead of using double apostrophes it should go in &lt;var> markup or so it is properly interpreted by screen readers.  (see WP:COMMONMATH)  So for where d is the bore of the cylinder it should be "where d is the bore if the cylinder".
 * Numeros (#) are discouraged. I replaced some of these with "No."  for number, but was cautious about numeros appearing in proper names.  (see MOS:NUMERO)
 * Spanisch-Brötli-Bahn is a bit of a poser. Foreign words get italics, but proper names in foreign languages are generally capitalized but non-italic.  However, looking at the article, the actual official proper name is Schweizerische Nordbahn.  IMO, that would not be italicized, but this informal name, which is descriptive, could be.  I'd still tend to lean away from using italics but I won't say it's wrong.
 * No change needed, but I thought I'd point out there is an inline quotation in the Blower section which is 40 words long. That is the exact threshold beyond which it is recommended to use a block quotation. (Normally I'd use  rather than &lt;blockquote>, I believe it does a better job of handing the metadata.)  (more at MOS:BQ, if interested)
 * prose:
 * Wikipedia tries to use Plain English at about a ninth-grade level, so words like colliery and latterly might be a bit much for the general reader.
 * These usually take the weight of the cylinders in front or of the firebox at the rear end when the width of this exceeds that of the mainframes. This seems awkward/complex to me, and a little jarring at the underlined part.  I added dashes for easier-to-absorb chunks but it might be better to rephrase it:
 * These usually take on weight – of the cylinders at the front or the firebox at the rear — when the width exceeds that of the mainframes.
 * minor tone: lack of coal, plenty of hydroelectricity &rarr; lack of coal, abundant hydroelectricity

Whew. Really good work. Of the dozen articles I checked from the drive, this is definitely in the top two, and pretty impressive for such a long article. Please keep up the good work. – Reidgreg (talk) 23:18, 3 August 2017 (UTC)


 * Thanks for the second pair of eyes on the article, and the great advice. I appreciate the exceptional effort you go to peer checking so many articles, and especially such a long one. I completely missed MOS:NUMERO, and hadn't fully comprehended MOS:HYPHEN, and your explanations were a huge help. I'm sorry for missing some of the captions - couldn't explain why I seem to have completely overlooked about half of the pictures. Many thanks, Dairy&#123;talk&#125; 08:06, 4 August 2017 (UTC)
 * You're welcome! I'm trying to pay-back the help I received when I joined the GOCE a few months ago.  I'm not the best copy-editor so far as writing high-quality prose, but I'm reasonably good at the nit-picky stuff.  Which is a matter of house style, writing encycopedic tone for a general audience, and issues like screen readers and machine translations.  Captions are easy to overlook.  I find it difficult to go back-and-forth from captions to prose – I'll lose my train of thought – so it's usually an afterthought on final-pass of an article.  If being particularly thorough, should also put in descriptive alt text for all the images.
 * Also, I'm really glad you did this article. I was feeling so petty for going a tenth of a percent over your wordcount for longest article.  I just rounded things off and really should have matched yours (15,984 or something similar).
 * Okay, so I've done enough criticizing. Time to make with the award ceremony! – Reidgreg (talk) 13:49, 4 August 2017 (UTC)

GOCE July 2017 drive bling
Really amazing long article counts for two well-earned gold stars! Thanks again for all your hard work! – Reidgreg (talk) 13:56, 4 August 2017 (UTC)

Please comment on Wikipedia talk:Manual of Style/Images
The feedback request service is asking for participation in this request for comment on Wikipedia talk:Manual of Style/Images. Legobot (talk) 04:34, 10 August 2017 (UTC)

Please comment on Template talk:Infobox television channel
The feedback request service is asking for participation in this request for comment on Template talk:Infobox television channel. Legobot (talk) 04:30, 27 August 2017 (UTC)

Tech News: 2017-35
 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
 * Syntax highlighting is now a beta feature on Wikimedia wikis with text written from left to right. It will come to right-to-left wikis later. This beta feature is based on CodeMirror.
 * You will now get a notification when someone tries to log in to your account and fails. If they try from a device or IP address that have logged in to your account before you will be notified after five failed attempts. You can turn this off or choose to get an email notification in your preferences. You can also turn on to get an email when someone logs in to your account from a new device or IP address.

Problems
 * Some pages show the error . This problem happens on pages with a Lua module that use Wikidata. This has now been fixed and no new pages will get this problem. You still need to fix pages that were broken before and still show the error message. You can see how on this page.

Changes later this week
 * You can block users from sending you notifications.
 * Octicons-sync.svg The new version of MediaWiki will be on test wikis and MediaWiki.org from 29 August. It will be on non-Wikipedia wikis and some Wikipedias from 30 August. It will be on all wikis from 31 August (calendar).

Meetings
 * Octicons-sync.svg 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 29 August at 19:00 (UTC). See how to join.
 * Octicons-tools.svg You can join the next meeting with the Technical Committee. The topic this week is Migrate to HTML5 section ids. The meeting will be on 30 August at 21:00 (UTC). See how to join.

Future changes
 * In the future you will have global preferences. This means you could set something in your preferences to work in the same way on all wikis. You will not be forced to use global preferences. The developers are now asking if editors need exceptions. This is where you want to use global settings on almost all wikis, but have some wikis where you want it to work in a different way. If you want this you need to tell the developers now. You can do so on the talk page.
 * New filters for edit review is a beta feature to improve recent changes pages. It will work on watchlists from 5 September.
 * Octicons-tools.svg The jQuery library will be upgraded to version 3 in September 2017. Wikis can ask on Phabricator to get it early, so they can help find and solve problems now.

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.  22:09, 28 August 2017 (UTC)

url-access=restricted vs limited
Hi, in this edit, with the edit summary "fix ref", you changed the url-access for a citation from restricted to limited. I was wondering why you chose limited. As per, the difference between the two are: "limited: there are other constraints (such as a cap on daily views) to freely access this source" and "subscription: the source is only accessible via a paid subscription". The URL whose url-access parameter you changed, on Project MUSE, is paywalled and there does not seem to be a way to view it without a paid subscription; you can see the "Restricted Access" logo. I'd appreciate it if you could let me know if I'm mistaken and there is in fact a way for people to access this resource via that URL freely/without a subscription. Thanks.

Edit: Otherwise I'll change it to subscription. But thank you for catching that what had been written before, restricted, is not a valid input. :) Umimmak (talk) 05:00, 29 August 2017 (UTC)


 * You're right - my bad. Should've been subscription - that was an accident. Thanks for picking up on that! Dairy &#123; talk &#125; 05:07, 29 August 2017 (UTC)
 * Done :) Dairy &#123; talk &#125; 05:12, 29 August 2017 (UTC)


 * Okay thanks :) I just got briefly excited when I thought an editor had uncovered some arcane way for people to view Project MUSE links for free, hehe. Umimmak (talk) 05:14, 29 August 2017 (UTC)

Please comment on Wikipedia talk:Naming conventions (television)
The feedback request service is asking for participation in this request for comment on Wikipedia talk:Naming conventions (television). Legobot (talk) 04:33, 11 September 2017 (UTC)

Please comment on Wikipedia talk:Manual of Style
The feedback request service is asking for participation in this request for comment on Wikipedia talk:Manual of Style. Legobot (talk) 04:31, 27 September 2017 (UTC)

The Bugle: Issue CXXXVIII, October 2017
The Bugle is published by the Military history WikiProject. To receive it on your talk page, please join the project or sign up here. If you are a project member who does not want delivery, please remove your name from this page. Your editors, Ian Rose (talk) and Nick-D (talk) 23:42, 7 October 2017 (UTC)

Please comment on Wikipedia talk:Manual of Style/Capital letters
The feedback request service is asking for participation in this request for comment on Wikipedia talk:Manual of Style/Capital letters. Legobot (talk) 04:27, 13 October 2017 (UTC)

Unblock request
Sorry, I was a bit confused about that – I tried to follow the unblock instructions as best I could. It seems like the account User:Mikehunt69420 has been indef autoblocked on the same IP (not the IP account itself), but the instructions at Unblock-auto said to leave the IP address, so I did that instead. I'm not an expert on how autoblocks work. Regards, Dairy  &#123; talk &#125; 00:12, 24 October 2017 (UTC)
 * Whoops, it literally gives you the unblock template with parameters filled in correctly to use underneath the "you are unable to edit" template. Heh. Should've read that better. Dairy  &#123; talk &#125; 00:50, 24 October 2017 (UTC)
 * No need to apologize. I just wanted to know if you still find yourself unable to edit. ~Anachronist (talk) 04:24, 24 October 2017 (UTC)
 * Yeah “Mikehunt” is autoblocked on the same IP. It’s an educational institution, so not surprising. I’ve noticed a few soft blocks before when logged out; this is the first autoblock. It’s not the only IP I use, but I do use it a fair bit.  Dairy  &#123; talk &#125; 07:40, 24 October 2017 (UTC)
 * All right. To prevent this sort of nuisance from happening again, I have granted you the "IP block exempt" user right, so that future IP blocks won't affect you when you're logged into this account. ~Anachronist (talk) 16:32, 24 October 2017 (UTC)
 * Thanks so much for that. Regards, Dairy  &#123; talk &#125; 08:52, 25 October 2017 (UTC)

Please comment on Wikipedia talk:WikiProject Trains
The feedback request service is asking for participation in this request for comment on Wikipedia talk:WikiProject Trains. Legobot (talk) 04:30, 29 October 2017 (UTC)

The Bugle: Issue CXXXIX, November 2017
The Bugle is published by the Military history WikiProject. To receive it on your talk page, please join the project or sign up here. If you are a project member who does not want delivery, please remove your name from this page. Your editors, Ian Rose (talk) and Nick-D (talk) 13:29, 7 November 2017 (UTC)

Please comment on Talk:Triangle Shirtwaist Factory fire
The feedback request service is asking for participation in this request for comment on Talk:Triangle Shirtwaist Factory fire. Legobot (talk) 04:36, 15 November 2017 (UTC)

Thanks
Dairy501, thanks for your help on St Paul's Cathedral. I'm mostly a part time, here-and-there editor so I get quickly lost when we start talking about fixing templates and such things. Foreignshore (talk) 16:43, 2 December 2017 (UTC)
 * Glad to help! Dairy &#123;talk&#125; 10:03, 3 December 2017 (UTC)

The Bugle: Issue CXL, December 2017
The Bugle is published by the Military history WikiProject. To receive it on your talk page, please join the project or sign up here. If you are a project member who does not want delivery, please remove your name from this page. Your editors, Ian Rose (talk) and Nick-D (talk) 11:16, 10 December 2017 (UTC)

Guild of Copy Editors December 2017 News
MediaWiki message delivery (talk) 20:04, 23 December 2017 (UTC)

The Bugle: Issue CXLI, January 2018
The Bugle is published by the Military history WikiProject. To receive it on your talk page, please join the project or sign up here. If you are a project member who does not want delivery, please remove your name from this page. Your editors, Ian Rose (talk) and Nick-D (talk) 13:15, 8 January 2018 (UTC)

The Bugle: Issue CXLII, February 2018
The Bugle is published by the Military history WikiProject. To receive it on your talk page, please join the project or sign up here. If you are a project member who does not want delivery, please remove your name from this page. Your editors, Ian Rose (talk) and Nick-D (talk) 07:16, 11 February 2018 (UTC)

GOCE February 2018 news
MediaWiki message delivery (talk) 00:00, 25 February 2018 (UTC)

The Bugle: Issue CXLIII, March 2018
The Bugle is published by the Military history WikiProject. To receive it on your talk page, please join the project or sign up here. If you are a project member who does not want delivery, please remove your name from this page. Your editors, Ian Rose (talk) and Nick-D (talk) 10:36, 12 March 2018 (UTC)

The Bugle: Issue CXLIIV, April 2018
The Bugle is published by the Military history WikiProject. To receive it on your talk page, please join the project or sign up here. If you are a project member who does not want delivery, please remove your name from this page. Your editors, Ian Rose (talk) and Nick-D (talk) 09:55, 8 April 2018 (UTC)

The Bugle: Issue CXLIV, May 2018
The Bugle is published by the Military history WikiProject. To receive it on your talk page, please join the project or sign up here. If you are a project member who does not want delivery, please remove your name from this page. Your editors, Ian Rose (talk) and Nick-D (talk) 15:00, 12 May 2018 (UTC)