This is an archive of past discussions about User:WikiWikiWayne. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page.
Hi, Doc James. Having a space before the trailing slash is standard stuff. For a few reasons. Firstly, it makes the coding more readable, especially for low vision editors. The space used to be required to ensure HTML parsers treated the trailing slash as an unrecognised attribute. It in essence constitutes syntax to promote transparency towards the semantics of the wikikicode tags. The trailing slash creates a self-closing tag. Before the space is what does the magic, and the forward slash instructs the magic to cease. You may notice that if you leave the trailing slash out complete that it throws a huge green error in the references section. Read up on HTML, XHTML, and XML W3C.
By the way, "<ref name=NIH2014 />" is similar, but not identical to "<ref name=NIH2014></ref>"
It is a shortcut to a similar end.
As for the line feeds, start a new section on a talk page, and you will see that the system always throws in a line feed above a section header, and one right below it. This also helps our low-vision editors. The one above the section header helps the system not get grumpy and lose track of where a new section starts. Having fun! Cheers! {{u|Checkingfax}} {Talk}06:55, 28 November 2017 (UTC)
Hi, Doc James. One more thing. Open your text editor, and paste this in: "<ref name=NIH2014/>"
Then, click on the little broom icon in your text editor and see what happens. I would say that there was a huge consensus to add that broom. Just sayin' - Having fun! Cheers! {{u|Checkingfax}} {Talk}09:24, 30 November 2017 (UTC)
Hi, Doc James. I have the Vector skin (default) installed. I see the broom icon in the text editor. There is a band of buttons and drop-downs: bold, italics, broom, signature/timestamp, link, embedded file, smart linking, advanced drop-down, special characters drop-down, help drop-down, cite drop-down. The broom is right above the drop-down box for Templates. Having fun! Cheers! {{u|Checkingfax}} {Talk}19:04, 30 November 2017 (UTC)
auto-formatHi, Doc James. I have outlined the broom in red. There is also a tool-tip on a mouse hover (also outlined in red): the broom icons official name is auto-format - see the tool-tip. Having fun! Cheers! {{u|Checkingfax}} {Talk}23:28, 30 November 2017 (UTC)
Incoming:Next Structured Commons IRC office hour will be on Tuesday, February 13, 2018, at 18:00 UTC.
Past: Tech-talk about knowledge technologies, featuring Wikidata, DBpedia, and Histropedia at Jakarta Digital Valley, Jakarta, Indonesia on Dec 8, 2017. Slides are available at Slideshare link.
Structured Data on Commons: Participate in this survey to help the team understand which tools and functionalities are most important to the Commons and Wikidata communities
QuickStatements now has a CSV-like import function (under "import commands")
Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.
A new tag marks edits where a redirect was created or removed. This still works when the editor writes something else in the edit summary. You can see the tags for example in the recent changes feed, article history, user contributions or on your watchlist. [2]
If you use Chrome on Android, you can now use the print to PDF button to create a PDF of an article. [3]
Filter by number of edits or filter by time range have been grouped on a same menu on the recent changes page if you use the new filters. The "View new changes since $1" link is now more prominent. [4]
Some of the web fonts that were provided by the Universal Language Selector extension are being removed. This is to reduce the load time on pages. The web fonts were added many years ago to help users read text in scripts which did not have fonts or had broken fonts. This is not the case any more. You can check the status page for a list of all web fonts and whether they are currently being used and especially for special requirements. [5]
Changes later this week
The new version of MediaWiki will be on test wikis and MediaWiki.org from 12 December. It will be on non-Wikipedia wikis and some Wikipedias from 13 December. It will be on all wikis from 14 December (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 12 December at 19:30 (UTC). See how to join.
You can join the technical advice meeting on IRC. During the meeting, volunteer developers can ask for advice. The meeting will be on 13 December at 16:00 (UTC). See how to join.
Thank you for checking up on all my 'fax' and displaying the rarest quality that exists in an editor - a sense of humor. The Very Best of Regards, Barbara (WVS)✐✉17:16, 16 December 2017 (UTC)
Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.
Tech News
Because of the holidays the next issue of Tech News will be sent out on 8 January 2018.
Problems
When you import a page from another wiki the usernames of the users who edited the article on the wiki you imported it from are shown in the article history. This should link to the users on the original wiki. A script to fix this caused problems for Wikidata and German Wikipedia. It also created a large number of SUL accounts on wikis where editors had never edited. [6]
Some bot owners got email about their bots logging in from a new computer. If this is from one or a couple of wikis, you can turn these messages off in your preferences on those wikis until the problem has been solved. If not, you can report more about the problem in Phabricator.
Changes later this week
There is no new MediaWiki version this week. There will be no new MediaWiki version next week either.
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 19 December at 19:30 (UTC). See how to join.
Future changes
Files on Commons will have structured metadata in the future. The developers are now looking for examples of different kinds of metadata to make sure they are aware of them when they build prototypes for structured data on Commons. You can read more and help by giving examples of interesting media files.
The Structured Commons team are making sure Commons work with structured data. If you regularly contribute to Commons and Wikidata you can answer a survey that helps the team prioritise the tools that are important for the Commons and Wikidata communities. The survey ends on 22 December. You can read more on Commons. You can also help the team decide on better names for "captions" and "descriptions". This ends on 3 January 2018.
Final step towards being able to store statements on Forms of a Lexeme
Disabled RDF support for Lexemes as the mapping isn't defined yet (phabricator:T182660)
Adding some more smart tracking for Lua usage so we better know which properties from an item are used on a Wikipedia article even when the whole item is loaded (phabricator:T179923)
The filters are now deployed as a default feature on all wikis on RecentChanges and RecentChangesLinked pages.
The filters are still available as a Beta feature on all wikis on Watchlists. Please try them!
LiveUpdates have been deployed as a default feature for all wikis.
On wikis using Extension:Translate, translated messages can now be filtered. System messages can be filtered as well, on all wikis. [7]
"View new changes since $1" link is now more prominent, to invite users to use that native feature to update the list of results. [8]
Pagination and time period selectors are now combined and located on the right on left-to-right wikis. [9]
When a user wanted to click outside of the filter menu to close it, it was possible to click on "revert" link by accident. It is not possible anymore. [10]
It is now possible to filter the following events using the Tags menu: Making a page a redirect, Changing redirect target, Changing an existing redirect into a non-redirect, Blanking of the page, Removing more than 90% of a page content, Rolling back an edit. [11]
Some design improvements have been done to Related Changes page to integrate the new filters. [12]
"Save current filter settings" menu and legend overlapped the results. This is now fixed. [13]
Some small design improvements have been done. [14]
Now Content Translation prevents source and target language to be set to same language. [15]
The dialog for selecting article to translate is standardized. It introduces a new component that is used for the selected page on both the "New translation" dialog and the "Suggested pages" list. [16]
More space is given to the language filter, to increase responsiveness and show more language names without truncation. [17]
While searching for a new page to translate, duplicates are not shown anymore for user search input. [18]
Various PHP warnings and JavaScript errors have been fixed. [19][20]
Hello copy editors! Welcome to the December 2017 GOCE newsletter, which contains nine months(!) of updates. The Guild has been busy and successful; your diligent efforts in 2017 has brought the backlog of articles requiring copy edit to below 1,000 articles for the first time. Thanks to all editors who have contributed their time and energy to help make this happen.
Our copy-editing drives (month-long backlog-reduction drives held in odd-numbered months) and blitzes (week-long themed editing in even-numbered months) have been very successful this year.
March drive: We set out to remove April, May, and June 2016 from our backlog and all February 2017 Requests (a total of 304 articles). By the end of the month, all but 22 of these articles were cleared. Officially, of the 28 who signed up, 22 editors recorded 257 copy edits (439,952 words). (These numbers do not always make sense when you compare them to the overall reduction in the backlog, because not all editors record every copy edit on the drive page.)
April blitz: This one-week copy-editing blitz ran from 16 through 22 April; the theme was Requests. Of the 15 who signed up, 9 editors completed 43 articles (81,822 words).
May drive: The goals were to remove July, August, and September 2016 from the backlog and to complete all March 2017 Requests (a total of 300 articles). By the end of the month, we had reduced our overall backlog to an all-time low of 1,388 articles. Of the 28 who signed up, 17 editors completed 187 articles (321,810 words).
June blitz: This one-week copy-editing blitz ran from 18 through 24 June; the theme was Requests. Of the 16 who signed up, 9 editors completed 28 copy edits (117,089 words).
2017 Coordinator elections: In June, coordinators for the second half of 2017 were elected. Jonesey95 moved back into the lead coordinator position, with Miniapolis stepping down to remain as coordinator; Tdslk and Corinne returned as coordinators, and Keira1996 rejoined after an extended absence. Thanks to all who participated!
July drive: We set out to remove August, September, October, and November 2016 from the backlog and to complete all May and June 2017 Requests (a total of 242 articles). The drive was an enormous success, and the target was nearly achieved within three weeks, so that December 2016 was added to the "old articles" list used as a goal for the drive. By the end of the month, only three articles from 2016 remained, and for the second drive in a row, the backlog was reduced to a new all-time low, this time to 1,363 articles. Of the 33 who signed up, 21 editors completed 337 articles (556,482 words).
August blitz: This one-week copy-editing blitz ran from 20 through 26 August; the theme was biographical articles tagged for copy editing for more than six months (47 articles). Of the 13 who signed up, 11 editors completed 38 copy edits (42,589 words).
September drive: The goals were to remove January, February, and March 2017 from the backlog and to complete all August 2017 Requests (a total of 338 articles). Of the 19 who signed up, 14 editors completed 121 copy edits (267,227 words).
October blitz: This one-week copy-editing blitz ran from 22 through 28 October; the theme was Requests. Of the 14 who signed up, 8 editors completed 20 articles (55,642 words).
November drive: We set out again to remove January, February, and March 2017 from the backlog and to complete all October 2017 Requests (a total of 207 articles). By the end of the month, these goals were reached and the backlog shrank to its lowest total ever, 997 articles, the first time it had fallen under one thousand (click on the graph above to see this amazing feat in graphical form). It was also the first time that the oldest copy-edit tag was less than eight months old. Of the 25 who signed up, 16 editors completed 159 articles (285,929 words).
2018 Coordinator elections: Voting is open for the election of coordinators for the first half of 2018. Please visit the election page to vote between now and December 31 at 23:59 (UTC). Thanks for participating!
Housekeeping note: We do not send a newsletter before (or after) every drive or blitz. To have a better chance of knowing when the next event will start, add the GOCE's message box to your watchlist.
Thank you all again for your participation; we wouldn't be able to achieve what we have without you! Cheers from your GOCE coordinators: Jonesey95, Miniapolis, Corinne, Tdslk, and Keira1996.
Hi, Corinne. In this case, I unlinked it, cleaned it up a bit here, and expanded it a bit, and created an external links section here. It is late, and my word choices may be improved. Please double check my work. Thank you for asking! I made some of my standard cleanup and accessibility edits too. Having fun! Cheers! {{u|Checkingfax}} {Talk}13:28, 25 December 2017 (UTC)
Wikidata weekly summary #292
Here's your quick overview of what has been happening around Wikidata over the last week.
Hello, Checkingfax – I was just looking at the latest edits to Hilton Hotels & Resorts, and I see an editor moved several images to the left side. Since I use a laptop, I keep my screen set at 125% resolution. At that resolution, the text is squeezed into a narrow column between images at the left and the right. At 110%, it's not so bad, but the text is still in a narrow column in the middle of the page (in "Notable events"). At 100%, it's all right, I suppose. What do you think? I also think the image at the left of the Hilton Hanoi Opera hotel is a little large.
Lists of works of individuals or groups, such as bibliographies, discographies, filmographies, album personnel and track listings, as well as timelines or chronologies, are typically presented in simple list format, though it is expected that the information will be supported elsewhere in the article by prose analysis of the main points, and that if the lists become unwieldy, they are split off into stand-alone lists per WP:Summary style. [emphasis mine]
The new version of MediaWiki will be on test wikis and MediaWiki.org from 12 December. It will be on non-Wikipedia wikis and some Wikipedias from 13 December. It will be on all wikis from 14 December (calendar).
You can join the technical advice meeting on IRC. During the meeting, volunteer developers can ask for advice. The meeting will be on 13 December at 16:00 (UTC). See how to join.
The Wikipedia Library
The filters are now deployed as a default feature on all wikis on RecentChanges and RecentChangesLinked pages.
Template:No space joiner bold middot no space non joiner has been nominated for deletion. You are invited to comment on the discussion at the template's entry on the Templates for discussion page. Jc86035 (talk) 13:20, 24 December 2017 (UTC)
.jpg)
.jpg)
