User talk:Cky2250/Archive 1
This is an archive of past discussions with User:Cky2250. 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. |
Archive 1 | Archive 2 |
Welcome!
Hello, Cky2250, and welcome to Wikipedia! Thank you for your contributions, especially what you did forThe Elder Scrolls V: Skyrim. I hope you like the place and decide to stay. Here are a few links to pages you might find helpful:
- Introduction to Wikipedia
- The five pillars of Wikipedia
- How to edit a page and How to develop articles
- How to create your first article
- Simplified Manual of Style
Please remember to sign your messages on talk pages by typing four tildes (~~~~); this will automatically insert your username and the date. If you need help, check out Wikipedia:Questions, ask me on my talk page, or ask your question on this page and then place {{help me}}
before the question. Again, welcome! Soetermans. T /C 10:03, 10 August 2013 (UTC)
- Concerning Template: Video game engines, it shouldn't be placed on the articles of individual games. There are hundreds of video games out there, to have a quite large infobox without any relevant information to the article itself isn't noteworthy, like for Skyrim, its usage of a particular engine isn't that remarkable to have it there. Articles on video game engines on the other hand can definitely use it. Thanks, and happy editing. --Soetermans. T / C 10:11, 10 August 2013 (UTC) --Soetermans. T / C 10:11, 10 August 2013 (UTC)
Recent reference fixes
Hey, saw you deleted Project Anarchy engine which I put in the wrong place-open source (thanks for that), but since I'm new here, I don't understand why you deleted it from the section "with related games". Now I put the engine under "freeware" section which should be correct, but how do I know it won't be deleted again?
Hi, thanks for your edits. There are a couple issues though.
Please don't set {{reflist}} to have 4 or even 3 columns unless references are using a really short format. This is a lot and the vast majority of our readers are not on a wide enough resolution to make it preferable. Please see Template:Reflist#Practices.
Secondly, this edit added{{linkrot}} to an article with fully filled reference citations. In addition we don't add generic expand tags to articles, as this is rather unhelpful, it is quite clear it needs expansion. Not to mention you added {{expand-section}} in place of a deprecated{{expand}}, which is not how it is supposed to be used. — HELLKNOWZ ▎TALK 15:19, 17 August 2013 (UTC)
- If you look at the page you will see [1][2][3][4][5] this is a link rot. It is not correctly assigned to text. Cky2250(talk) 15:27, 17 August 2013 (UTC)
- It seems you do not quite understand what WP:LINKROT is and what the purpose of the template is. It doesn't matter if the reference is or isn't attached to any text, what matters is that it doesn't use URLs without any extra information about the source. Adding text next to the references does not affect link rot, this change shows -- any link rot problems would still be there (if there were any). The closest problem tag we have for this is{{citation style}}. (P.S. I'll reply here in the future.) 15:42, 17 August 2013 (UTC)
- When you see [1] in a reference section it appears to be a WP:Bare URLs. While I am going from page to page looking for linkrot I spotted this as one. It does not mean I do not understand what WP:LINKROT is; the format for the reference was wrong. Either way you take this the error is fixed. Cky2250 (talk) 16:44, 17 August 2013 (UTC)
- Oh, I see. You mistook [1] for [1] because it appeared in the Reference section. When you said you saw [1][2][3][4][5], you really meant [1][2][3][4][5]. Sorry I misunderstood you, but technically this was still a slight mistake on your part as there was no linkrot. Anyway, I put the references inline to avoid further issues. — HELLKNOWZ ▎TALK 17:16, 17 August 2013 (UTC)
- When you see [1] in a reference section it appears to be a WP:Bare URLs. While I am going from page to page looking for linkrot I spotted this as one. It does not mean I do not understand what WP:LINKROT is; the format for the reference was wrong. Either way you take this the error is fixed. Cky2250 (talk) 16:44, 17 August 2013 (UTC)
- It seems you do not quite understand what WP:LINKROT is and what the purpose of the template is. It doesn't matter if the reference is or isn't attached to any text, what matters is that it doesn't use URLs without any extra information about the source. Adding text next to the references does not affect link rot, this change shows -- any link rot problems would still be there (if there were any). The closest problem tag we have for this is{{citation style}}. (P.S. I'll reply here in the future.) 15:42, 17 August 2013 (UTC)
Translations
Hello Cky. Please note that WP:TRANSLATION is the correct procedure for translating articles from other language Wikipedias if you're not able to do it properly yourself--Jac16888 Talk 09:25, 21 August 2013 (UTC)
Wholesale Reversion
Hello Sky, you reverted my entire edit on the ARMA 2article, rather than reverting just the removal(s) you disagreed with. I also did some copyediting in the gameplay section to organize the info better, and I think it's obviously much better, but which you also reverted, perhaps inadvertently. I've restored this editing, and hope you can be more careful in the future. See Wikipedia:Restoring_part_of_a_reverted_edit for wikipedia guidelines in this area. Pro crast in a tor (talk) 10:48, 25 August 2013 (UTC)
- I did review your entire edit and kept areas and made more improvements. This article needs a lot of work. Go back and review your change to mine (edit). Every edit you change you remove context while also fixing sentences. I reverted your edit in the past for removing way too much context. It isn't like it was pointless paragraphs of information. Cky2250 (talk) 13:25, 25 August 2013 (UTC)
Disambiguation link notification for August 27
Hi. Thank you for your recent edits. Wikipedia appreciates your help. We noticed though that you've added some links pointing todisambiguation pages. Such links are almost always unintended, since a disambiguation page is merely a list of "Did you mean..." article titles. Read the FAQ • Join us at theDPL WikiProject.
- Positech Games (check to confirm | fix with Dab solver)
- added links pointing to DRM, Game developer, Arcade and Kudos
It's OK to remove this message. Also, to stop receiving these messages, follow these opt-out instructions. Thanks,DPL bot (talk) 11:14, 27 August 2013 (UTC)
Template:Bohemia Interative has been nominated for deletion. You are invited to comment on the discussion at the template's entry on the Templates for discussion page. Cky2250 (talk) 01:22, 13 September 2013 (UTC)
PlayStation 4
You have reverted edits by Shrine Maiden twice without an edit summary 1 2. Please provide a reason next time. I am undoing it for now. DragonZero (Talk · Contribs) 23:02, 19 September 2013 (UTC)
- The wiki function I am using auto sets everything. There must be a bug in it. Cky2250 (talk) 00:10, 20 September 2013 (UTC) They were reverted due to irrelevants to an encyclopedia.
Hello, Cky2250. I wanted to let you know that I’m proposing an article that you started, Farming Simulator, for deletion because I don't think it meets our criteria for inclusion. If you don't want the article deleted:
- edit the page
- remove the text that looks like this:
{{proposed deletion/dated...}}
- save the page
Also, be sure to explain why you think the article should be kept in your edit summary or on the article's talk page. If you don't do so, it may be deleted later anyway.
You can leave a note on my talk page if you have questions. Green Cardamom (talk) 07:04, 28 September 2013 (UTC)
Radeon HD 8000 Series
I have removed the {{prod}} tag from Radeon HD 8000 Series, which you proposed for deletion. I'm leaving this message here to notify you about it. If you still think the article should be deleted, please don't add the {{prod}} template back to the article. Instead, feel free to list it at Wikipedia:Articles for deletion. Thanks! --DrSeehas (talk) 13:40, 30 September 2013 (UTC)
- the HD 8000 series very much does exist for mobile, desktop and apu, device IDs don't lie. Matthew Smith (talk) 07:11, 1 October 2013 (UTC)
Your reverts
Please read WP:Categorization before reverting. Thanks, Sir Lothar (talk) 04:15, 20 October 2013 (UTC)
- I told you, don't revert it - it's against categorization rules on Wikipedia. The article should be in lowest category possible - that's why: Hidden & Dangerous -> 2k Czech games -> Video games developed in the Czech Republic by company -> Video games developed in the Czech Republic hierarchy. Hidden & Dangerous is already in 2k Czech games, so there's no need to put it in upper categories. Sir Lothar (talk) 13:06, 20 October 2013 (UTC)
MfD nomination of Module:Video game multiple reviews/testcases
Module:Video game multiple reviews/testcases, a page you substantially contributed to, has been nominated for deletion. Your opinions on the matter are welcome; please participate in the discussion by adding your comments at Wikipedia:Miscellany for deletion/Module:Video game multiple reviews/testcases and please be sure to sign your comments with four tildes (~~~~). You are free to edit the content of Module:Video game multiple reviews/testcases during the discussion but should not remove the miscellany for deletion template from the top of the page; such a removal will not end the deletion discussion. Thank you. Cky2250 (talk) 17:44, 21 October 2013 (UTC)
MfD nomination of Module:Video game multiple console reviews/testcases
Module:Video game multiple console reviews/testcases, a page you substantially contributed to, has been nominated for deletion. Your opinions on the matter are welcome; please participate in the discussion by adding your comments at Wikipedia:Miscellany for deletion/Module:Video game multiple console reviews/testcases and please be sure to sign your comments with four tildes (~~~~). You are free to edit the content of Module:Video game multiple console reviews/testcases during the discussion but should not remove the miscellany for deletion template from the top of the page; such a removal will not end the deletion discussion. Thank you. Cky2250 (talk) 17:55, 21 October 2013 (UTC)
You are now a template editor
Your account has been granted the template editor
user right, allowing you to edit templates and modules that have been protected with template protection. It also allows you to bypass the title blacklist, giving you the ability to create and edit edit notices.
You can use this user right to perform maintenance, answer edit requests, and make any other simple and generally uncontroversial edits to templates, modules, and edit notices. You can also use it to enact more complex or controversial edits, after those edits are first made to a test sandbox, and their technical reliability as well as their consensus among other informed editors has been established.
Before you use this user right, please read Wikipedia:Template editor and make sure you understand its contents. In particular, you should read the section on wise template editing and the criteria for revocation. This user right gives you access to some of Wikipedia's most important templates and modules; it is critical that you edit them wisely and that you only make edits that are backed up by consensus. It is also very important that no-one else should be allowed to access your account. You may wish to take a few moments to secure your password.
If you do not want this user right, you may ask any administrator to remove it for you at any time.
Useful links:
- All template-protected pages
- Request fully-protected templates or modules be downgraded to template protection
Happy template editing! — Mr. Stradivarius ♪ talk ♪ 15:06, 28 October 2013 (UTC)
In regards to your question about merging templates
I noticed on WP:RTE that you had asked a question regarding how to form consensus to merge templates. One of the forums that can be used to form consensus for the merging of templates is WP:TFD. If you follow the instructions on there, you can start a conversation to form consensus for template merges. Hope that information helps! Steel1943 (talk) 17:36, 28 October 2013 (UTC)
Your merge proposal.
You should make a post here: Wikipedia talk:WikiProject Video games. It will help notify more editors who are active in the WikiProject. The1337gamer (talk) 18:18, 28 October 2013 (UTC)
Script error
This script error must be related to you recent changes to the template & script. Please look into it. ☺ · Salvidrim! · ✉ 03:42, 1 November 2013 (UTC)
- Fixed it. Was a stray |. Is there any work being done to prevent that stray character from creating a script error? ☺ · Salvidrim! · ✉ 03:45, 1 November 2013 (UTC)
- (talk page stalker) It looks like a type check in pairsByKeys would fix it, like this. I haven't tested that yet though. — Mr. Stradivarius ♪ talk ♪ 04:16, 1 November 2013 (UTC)
- Thanks Mr. Stradivarius that fixed the problem, I will add it to the final code now.Cky2250 (talk) 04:26, 1 November 2013 (UTC)
- Cheers! :D ☺ · Salvidrim! · ✉ 04:27, 1 November 2013 (UTC)
- Done
- Cheers! :D ☺ · Salvidrim! · ✉ 04:27, 1 November 2013 (UTC)
- Thanks Mr. Stradivarius that fixed the problem, I will add it to the final code now.Cky2250 (talk) 04:26, 1 November 2013 (UTC)
Welcome to The Wikipedia Adventure!
- Hi! We're so happy you wanted to play to learn, as a friendly and fun way to get into our community and mission. I think these links might be helpful to you as you get started.
- -- 19:54, 2 August 2013 (UTC)
Mission 1 | Mission 2 | Mission 3 | Mission 4 | Mission 5 | Mission 6 | Mission 7 |
Say Hello to the World | An Invitation to Earth | Small Changes, Big Impact | The Neutral Point of View | The Veil of Verifiability | The Civility Code | Looking Good Together |
November 2013
Hello, I'm BracketBot. I have automatically detected that your edit to RL circuit may have broken the syntax by modifying 1 "()"s and 1 "{}"s likely mistaking one for another. If you have, don't worry: just edit the page again to fix it. If I misunderstood what happened, or if you have any questions, you can leave a message on my operator's talk page.
- List of unpaired brackets remaining on the page:
- :<math>\omega = \frac{1}{2} L I^{2} (1-e^{-2 \frac(R}{L} t})</math>
Thanks, BracketBot (talk) 20:25, 4 November 2013 (UTC) Hello, I'm BracketBot. I have automatically detected that your edit to List of Humble Bundles may have broken the syntax by modifying 1 "{}"s. If you have, don't worry: just edit the page again to fix it. If I misunderstood what happened, or if you have any questions, you can leave a message on my operator's talk page.
- List of unpaired brackets remaining on the page:
- [[Neil Gaiman]] and [[Dave McKean]]|Year=1989-1992|Raised=US$1.20+ M|Purchases=84,220|Avg=$14.28}}
Thanks, BracketBot (talk) 17:42, 15 November 2013 (UTC)
File:Humble Bundle Total Purchases.jpg listed for deletion
A file that you uploaded or altered, File:Humble Bundle Total Purchases.jpg, has been listed at Wikipedia:Files for deletion. Please see the discussion to see why it has been listed (you may have to search for the title of the image to find its entry). Feel free to add your opinion on the matter below the nomination. Thank you. Stefan2 (talk) 22:21, 4 November 2013 (UTC)
Problems with upload of File:Humble Bundle Total Raised.svg
Thanks for uploading File:Humble Bundle Total Raised.svg. You don't seem to have said where the image came from, who created it, or what the copyright status is. We require this information to verify that the image is legally usable on Wikipedia, and because most image licenses require giving credit to the image's creator.
To add this information, click on this link, then click the "Edit" tab at the top of the page and add the information to the image's description. If you need help, post your question on Wikipedia:Media copyright questions.
For more information on using images, see the following pages:
Thank you for your cooperation. --ImageTaggingBot (talk) 00:05, 5 November 2013 (UTC)
User:Sohambanerjee1998/AutoWikiBrowser.
{{User:Sohambanerjee1998/AutoWikiBrowser|Cky2250}}
Saw that you recently got AutoWikiBrowser rights, would use this userbox which I created instead? Sohambanerjee1998 08:41, 5 November 2013 (UTC)
Talkback
You can remove this notice at any time by removing the {{Talkback}} or {{Tb}} template.
You can remove this notice at any time by removing the {{Talkback}} or {{Tb}} template.
VG reviews
Hi Cky, could you do me a quick favour when you get a chance? I've noticed several video game articles I've worked on have a broken template in the reception section where-ever any additional info has been added to the title parameter. For example Asphalt 8, Real Racing 3, Shadowgun, Dead Space. All of these templates featured a line break after the title and then (iOS version) written in a smaller font. All were fine until recently, so it must be an edit made to the main template in the last while. I tried using the subtitle parameter, but still couldn't get it to work (you can have a look here). Cheers. Bertaut (talk) 23:15, 5 November 2013 (UTC)
- Thanks for the report, it is do to the wiki syntax and the <br> the way the code works is the title is also put into the class and the <br> or any other syntax within a <> breaks it. Use subtitle for what you are trying to do. Also for future notice never user <br> it will break the html use <br />. I will also see if the class is needed and will remove this problem if no one has been using the class. So to repeat myself I have fixed Asphalt 8 look how it is done and use it on the other pages you have been working on. Good luck.—CKY2250 ταικ 00:13, 6 November 2013 (UTC)
- Great. I see what you've done alright. Thanks. Bertaut (talk) 01:45, 6 November 2013 (UTC)
They are being used now, so the don't exactly qualify for TFD anymore... Epicgenius(give him tirade • check out damage) 17:52, 9 November 2013 (UTC)
- Is there a point of having a template that consists of only words. There is no need for this.—CKY2250 ταικ 17:54, 9 November 2013 (UTC)
- Yes, they're supposed to be put in station layout links (like this: [[{{S-line/NYCS right/Second}} (IND Second Avenue Line)|{{S-line/NYCS right/Second}}]] so that when the terminus changes from 96th Street to 125th Street, it could be easily edited, rather than having to edit the source on all the template's transclusions. Epicgenius(give him tirade • check out damage) 18:01, 9 November 2013 (UTC)
- For these type of template it is best to put a notice.
<noinclude>{{Notice|This template is used for changes over many templates. Please do not remove or alter.}}</noinclude>
—CKY2250 ταικ 18:43, 9 November 2013 (UTC)
- For these type of template it is best to put a notice.
- Sorry it took so long for the reply, as I was at a party. I will do that. Epicgenius(give him tirade • check out damage) 03:53, 10 November 2013 (UTC)
A bowl of strawberries for you!
Thanks for your work in adding TemplateData to some of the high-use templates. I appreciate it and hope that it will make editing easier for everyone who uses VisualEditor. Whatamidoing (WMF) (talk) 18:50, 11 November 2013 (UTC) |
- Thanks mate.—CKY2250 ταικ 20:49, 11 November 2013 (UTC)
Xbox One talkpage
Yes, I've had several problems with her in the past. She doesn't always seem to have the best of intentions...but the discussion does seem like it could be a recurring problem. I could see many a fanboy trying to argue over its use, so it's probably good to have a discussion about it prevalent on the talk page (or archives). Sergecross73 msg me 14:38, 14 November 2013 (UTC)
- If you feel that's necessary, I have no problem with it. Even collapsing it, I'm not extremely against it, I just think it could maybe help avoid future problems if it were more openly readable. Sergecross73 msg me 14:46, 14 November 2013 (UTC)
RE Big Bang Theory
- I've looked it over some. I can see both sides to this one. On one hand, you're right, they're very similar, and one's clearly based off of the other. On the other hand, I can see their point too, albeit similar titles, disambiguation terms, like "(television show)" usually aren't assigned unless the titles are exactly the same. Also, sadly, the world cares more about sitcoms than science, so sometimes that happens when you're dealing with science vs. pop culture type scenarios.
- You're free to start up a requested move on it; worst case scenario is, it fails, right? They said its been discussed before; make sure it didn't close a like within the last few weeks, or it could be considered disruptive to retry again so quickly. Otherwise, consensus can change, so there's no problem in bringing it up again. (However, when you've got a few people who are against it strongly like they are, they may end up being the first couple !votes in the RM, which could direct the lest of the discussions if people see a bunch of "Opposes" right off the bat. But that can't be helped. Just saying it could happen. Sergecross73 msg me 16:39, 14 November 2013 (UTC)
User talk:Epicgenius
Look, I understand you're trying to help a friend out, but you're not helping. Referring to other editors as trolls can only serve to feed the flames. In addition, it's a personal attack and I can block you for it. Your earlier comment on the talk page, "As a page stalker myself there is nothing wrong with what Epicgenius has done", was already not helpful since I don't believe you have enough experience to make that judgment. And besides, what you did on Peter Stuyvesant was asinine enough already: one could argue that you baited BMK into breaking 3R on an article you had never shown interest in (and that's the definition of WP:HOUNDING). So take my advice: stay out of it, and if you wish to offer support, do it in a positive way. Thank you. Drmies (talk) 23:52, 19 November 2013 (UTC)
- If you want to ban be go ahead, I need a break from wikipedia since I guess I don't help out here anyhow. That guy never reverted my edit, he broke the 3RR before I made my refert. So I have no idea what you're talking about man. You are very unclear in how i stand in Epicgenius and the other guys dispute. My consensus: So again just ban me for a few months do not ban me for 24 hours ban me for a few months or a couple of years, maybe by then I will have cooled down enough, since admins hardly understand.—CKY2250 ταικ 00:28, 20 November 2013 (UTC)
- Yeah, this admin indeed hardly understands what you're trying to say. I think I've been very clear, and it should be clear to anyone who reads that talk page and the ANEW report. Let me put it another way: don't call others trolls unless you can put your money where your mouth is. Which, in this case, you can't. Thank you. Drmies (talk) 00:33, 20 November 2013 (UTC)
- You know what, you're right: BMK did not revert after you--possibly because they had too much sense (though they have admitted not having enough sense to stop before 3R). You reverted BMK and filed an edit warring report at ANEW. Now tell me that's not asinine. But hey, don't listen if you don't care. I didn't come here to block (or "ban"), I came here to give you some advice, that's all. Drmies (talk) 00:36, 20 November 2013 (UTC)
VisualEditor newsletter for November 2013
Since the last newsletter, the VisualEditor team has worked on some feature changes, major infrastructure improvements to make the system more stable, dependable and extensible, some minor toolbar improvements, and fixing bugs.
A new form parsing library for language characters in Parsoid caused the corruption of pages containing diacritics for about an hour two weeks ago. Relatively few pages at the English Wikipedia were affected, but this created immediate problems at some other Wikipedias, sometimes affecting several dozen pages. The development teams for Parsoid and VisualEditor apologize for the serious disruption and thank the people who reported this emergency at Wikipedia:VisualEditor/Feedback and on the public IRC channel, #mediawiki-visualeditor.
There have been dozens of changes since the last newsletter. Here are some of the highlights:
- Accidental deletion of infoboxes and other items: You now need to press the Delete or ← Backspace key twice to delete a template, reference or image. The first time, the item becomes selected, and the second time, it is removed. The need to press the delete key twice should make it more obvious what you are doing and help avoid accidental removals of infoboxes and similar (bug 55336).
- Switch from VisualEditor to the wikitext editor: A new feature lets you make a direct, one-way editing interface change, which will preserve your changes without needing to save the page and re-open it in the wikitext editor (bug 50687). It is available in a new menu in the action buttons by the Cancel button (where the "Page Settings" button used to be). Note that this new feature is not currently working in Firefox.
- Categories and Languages are also now directly available in that menu. The category suggestions drop-down was appearing in the wrong place rather than below its input box, which is now fixed. An incompatibility between VisualEditor and the deployed Parsoid service that prevented editing categories and language links was fixed.
- File:, Help: and Category: namespaces: VisualEditor was enabled for these namespaces the on all wikis (bug 55968), the Portal: and Viquiprojecte: namespaces on the Catalan Wikipedia (bug 56000), and the Portal: and Book: namespaces on the English Wikipedia (bug 56001).
- Media item resizing: We improved how files are viewed in a few ways. First, inline media items can now be resized in the same way that has been possible with block ones (like thumbnails) before. When resizing a media item, you can see a live preview of how it will look as you drag it (bug 54298). While you are dragging an image to resize it, we now show a label with the current dimensions (bug 54297). Once you have resized it, we fetch a new, higher resolution image for the media item if necessary (bug 55697). Manual setting of media item sizes in their dialog is nearly complete and should be available next week. If you hold down the ⇧ Shift key whilst resizing an image, it will now snap to a 10 pixel grid instead of the normal free-hand sizing. The media item resize label now is centered while resizing regardless of which tool you use to resize it.
- Undo and redo: A number of improvements were made to the transactions system which make undoing and redoing more reliable during real-time collaboration (bug 53224).
- Save dialogue: The save page was re-written to use the same code as all other dialogs (bug 48566), and in the process fixed a number of issues. The save dialog is re-accessible if it loses focus (bug 50722), or if you review a null edit (bug 53313); its checkboxes for minor edit, watch the page, and flagged revisions options now layout much more cleanly (bug 52175), and the tab order of the buttons is now closer to what users will expect (bug 51918). There was a bug in the save dialog that caused it to crash if there was an error in loading the page from Parsoid, which is now fixed.
- Links to other articles or pages sometimes sent people to invalid pages. VisualEditor now keeps track of the context in which you loaded the page, which lets us fix up links in document to point to the correct place regardless of what entry point you launched the editor from—so the content of pages loaded through
/wiki/Foobar?veaction=edit
and/enwiki/w/index.php?title=Foobar&veaction=edit
both now have text links that work if triggered (bug 48915). - Toolbar links: A bug that caused the toolbar's menus to get shorter or even blank when scrolled down the page in Firefox is now fixed (bug 55343).
- Numbered external links: VisualEditor now supports Parsoid's changed representation of numbered external links (bug 53505).
- Removed empty templates: We also fixed an issue that meant that completely empty templates became impossible to interact with inside VisualEditor, as they didn't show up (bug 55810).
- Mathematics formulae: If you would like to try the experimental LaTeX mathematics tool in VisualEditor, you will need to opt-in to Beta Features. This is currently available on Meta-wiki, Wikimedia Commons, and Mediawiki.org. It will be available on all other Wikimedia sites on 21 November.
- Browser testing support: If you are interested in technical details, the browser tests were expanded to cover some basic cursor operations, which uncovered an issue in our testing framework that doesn't work with cursoring in Firefox; the Chrome tests continue to fail due to a bug with the welcome message for that part of the testing framework.
- Load time: VisualEditor now uses content language when fetching Wikipedia:TemplateData information, so reducing bandwidth use, and users on multi-language or multi-script wikis now get TemplateData hinting for templates as they would expect (bug 50888).
- Reuse of VisualEditor: Work on spinning out the user experience (UX) framework from VisualEditor into oojs-ui, which lets other teams at Wikimedia (like Flow) and gadget authors re-use VisualEditor UX components, is now complete and is being moved to a shared code repository.
- Support for private wikis: If you maintain a private wiki at home or at work, VisualEditor now supports editing of private wikis, by forwarding the Cookie: HTTP header to Parsoid (
$wgVisualEditorParsoidForwardCookies
set to true) (bug 44483). (Most private wikis will also need to install Parsoid and node.js, as VisualEditor requires them.)
Looking ahead:
- VisualEditor will be released to some of the smaller Wikipedias on 02 December 2013. If you are active at one or more smaller Wikipedias where VisualEditor is not yet generally available, please see the list at VisualEditor/Rollouts.
- Public office hours on IRC to discuss VisualEditor with Product Manager James Forrester will be held on Monday, 2 December, at 1900 UTC and on Tuesday, 3 December, at 0100 UTC. Bring your questions. Logs will be posted on Meta after each office hour completes.
- In terms of feature improvements, one of the major infrastructure projects affects how inserting characters works, both using your computer's built-in Unicode input systems and through a planned character inserter tool for VisualEditor. The forthcoming rich copying and pasting feature was extended and greater testing is currently being done. Work continues to support the improved reference dialog to quickly add citations based on local templates.
If you have questions or suggestions for future improvements, or if you encounter problems, please let everyone know by posting a note at Wikipedia:VisualEditor/Feedback. Thank you! Whatamidoing (WMF) 22:30, 20 November 2013 (UTC)
Please come back
I read your user page and was sad that you will no longer be able to help. If there are users who are arrogant, refuse to deal with them. However, we really need your help. Epicgenius (talk) 22:15, 28 November 2013 (UTC)
- I'd like to help, but it is too much work to deal with. I'd rather help the United States Air Force as an engineer than articles that change every day.—CKY2250 ταικ 22:17, 28 November 2013 (UTC)
- Hey, you're back! You could work with templates instead. Most of them change less often. Epicgenius (talk) 22:22, 28 November 2013 (UTC)
- I'm not back... lol. I just watch all the things changing on wikipedia, I've grown to not trust it anymore -- that would be different 2 months ago.—CKY2250 ταικ 22:28, 28 November 2013 (UTC)
- Well, okay. Just remember that Wikipedia is as stressful as real life is, and many people eventually learn to accept it. Epicgenius (talk) 15:01, 29 November 2013 (UTC)
Re:Template:Video game reviews
A few points:
- "The lead of the documentation page", aka the part of {{Video game reviews/doc}} that is above the table of contents, makes no mention of the "state" field.
- A grep for "state" (or "collapse") shows that the state field is referenced in two places: 'General->Usage', and 'Template Data'. (And the examples, but without description). In both of those places, the default is listed as expanded.
- If you write documentation that requires updates in three places every time something changes, then that is poor documentation that is destined to contradict itself eventually. Documentation, especially documentation for a small script, should be clear and concise.
- None of this should have been a change in the first place- the template you were replacing did not autocollapse by default (if and only if a title was set, let's not get into how the 'title' field in your version changed the functionality of the template beyond adding a title), so the new version should not have autocollapsed by default. This was a bugfix, not a feature request.
- While we're on the subject of the template, it was poor form of you to replace a table generator with an incredibly longwinded lua script with minimal commenting (particularly since most editors on wiki don't know lua, even the ones who are programmers in real life)- it's cute that you think you can promise that you are going to maintain it forever, but that's not how software development works. You could get bored of wiki, you could get sick, you could get shot (you are in the military, neh?), or you could, as you did, simply expect that all discussions about the reviews template take place on a talk page watched by 10 people, rather than on the wikiproject that uses the template's talk page, which is read by hundreds, and get blindsided by feature requests/bug reports. When you write code for a collaborative software project, it needs to be clean and well-commented, since other people are going to be editing it. Really, when you write code for anything beyond a personal project, it should be clean and well-commented, since someone else will always come along to work on it later. You never fully own a piece of code unless it's only on your personal machine. --PresN 04:51, 8 December 2013 (UTC)
- I did read it. There is nowhere in the lead of the documentation, nor anywhere elsewhere in the documentation not already mentioned above, that talks about the 'state' field or about the template being collapsed or not that has not been updated to reflect that not setting the state variable leaves the template as uncollapsed with a show/hide button. This leads to the conclusion that (a) you don't actually know what the documentation says, (b) you don't actually know what your code is doing, (c) you didn't actually read what I wrote above, or (d) some combination of (a)-(c). If by me being "100% the reason why [you] don't use wikipedia anymore" you mean that you can't take the idea that you are not always right and that other people are going to edit things that you've edited, which is the conclusion I've drawn from this conversation and your responses in the section above this, then I don't really feel bad- you don't seem to be suited to working in a collaborative environment. --PresN 05:24, 8 December 2013 (UTC)
VisualEditor newsletter • 19 December 2013
Since the last newsletter, the VisualEditor team has worked on some toolbar improvements, fixing bugs, and improving support for Indic languages as well as other languages with complex characters. The current focus is on improving the reference dialog and expanding the new character inserter tool.
There have been dozens of changes since the last newsletter. Here are some of the highlights:
- Rich copying and pasting is now available. If you copy text from another website, then character formatting and some other HTML attributes are preserved. This means, for example, that if you copy a pre-formatted suggested citation from a source like this, then VisualEditor will preserve the formatting of the title in the citation. Keep in mind that copying the formatting may include formatting that you don't want (like section headings). If you want to paste plain, unformatted text onto a page, then use Control+⇧ Shift+V or ⌘ Command+⇧ Shift+V (Mac).
- Auto-numbered external links like [1] can now be edited just like any other link. However, they cannot be created in VisualEditor easily.
- Several changes to the toolbar and dialogs have been made, and more are on the way. The toolbar has been simplified with a new drop-down text styles menu and an "insert" menu. Your feedback on the toolbar is wanted here. The transclusion/template dialog has been simplified. If you have enabled mathematical formula editing, then the menu item is now called the formula editor instead of LaTeX.
- There is a new character inserter, which you can find in the new "insert" menu, with a capital Omega ("Ω"). It's a very basic set of characters. Your feedback on the character inserter is wanted here.
- Saving the page should seem faster by several seconds now.
- It is now possible to access VisualEditor by manually editing the URL, even if you are not logged in or have not opted in to VisualEditor normally. To do so, append
?veaction=edit
to the end of the page name. For example, changehttps://en.wikipedia.org/wiki/Special:Random
tohttps://en.wikipedia.org/wiki/Special:Random?veaction=edit
to open a random page in VisualEditor. This is intended to support bug testing across multiple browsers, without requiring editors to login repeatedly.
Looking ahead: The transclusion dialog will see further changes in the coming weeks, with a simple mode for single templates and an advanced mode for more complex transclusions. The new character formatting menu on the toolbar will get an arrow to show that it is a drop-down menu. The reference dialog will be improved, and the Reference item will become a button in the main toolbar, rather than an item in the Insert menu.
If you have questions or suggestions for future improvements, or if you encounter problems, please let everyone know by posting a note at Wikipedia:VisualEditor/Feedback. Thank you! Whatamidoing (WMF) (talk) 20:49, 19 December 2013 (UTC)
WikiProject Video Games Newsletter, Quarter 4, 2013
The WikiProject Video Games Newsletter
Volume 6, No. 4 — 4th Quarter, 2013
Previous issue | Index | Next issue
Project At a Glance
As of Q4 2013, the project has:
|
Content
|
VisualEditor newsletter for Janaury 2014
Since the last newsletter, the VisualEditor team has worked mostly minor features and fixing bugs. A few significant bugs include working around a bug in CSSJanus that was wrongly flipping images used in some templates in right-to-left (RTL) environments (bug 50910) a major bug that meant inserting any template or other transclusion failed (bug 59002), a major but quickly resolved problem due to an unannounced change in MediaWiki core, which caused VisualEditor to crash on trying to save (bug 59867). This last bugs did not appear on any Wikipedia. Additionally, significant work has been done in the background to make VisualEditor work as an independent editing system.
As of today, VisualEditor is now available as an opt-out feature to all users at 149 active Wikipedias.
- The character inserter tool in the "Insert" menu has a very basic set of characters. The character inserter is especially important for languages that use Latin and Cyrillic alphabets with unusual characters or frequent diacritics. Your feedback on the character inserter is requested. In addition to feedback from any interested editor, the developers would particularly like to hear from anyone who speaks any of the 50+ languages listed under Phase 5 at mw:VisualEditor/Rollouts, including Breton, Mongolian, Icelandic, Welsh, Afrikaans, Macedonian, and Azerbaijani.
- meta:Office hours on IRC have been heavily attended recently. The next one will be held this coming Wednesday, 22 January at 23:00 UTC.
- You can now edit some of the page settings in the "options" dialog –
__NOTOC__
and__FORCETOC__
as selection (forced on, forced off, or default setting; bugs 56866 and 56867) and__NOEDITSECTION__
as a checkbox (bug 57166). - The automated browser tests were adjusted to speed them up and bind more correctly to list items in lists, and updated to a newer version of their ruby dependencies. You can monitor the automated browser tests' results (triggered every twelve hours) live on the server.
- Wikipedia:VisualEditor/User guide was updated recently to show some new and upcoming features.
Looking ahead: The character formatting menu on the toolbar will get a drop-down indicator next Thursday. The reference and media items will be the first two listed in the Insert menu. The help menu will get a page listing the keyboard shortcuts. Looking further out, image handling will be improved, including support for alignment (left, right, and center) and better control over image size (including default and upright sizes). The developers are also working on support for editing redirects and image galleries.
Subscriptions to this newsletter are managed at Wikipedia:VisualEditor/Newsletter. Please add or remove your name to change your subscription settings. If you have questions or suggestions for future improvements, or if you encounter problems, please let everyone know by posting a note at Wikipedia:VisualEditor/Feedback. Thank you! Whatamidoing (WMF) 20:15, 17 January 2014 (UTC)
Speedy deletion nomination of Razer Comms
Hello Cky2250,
I wanted to let you know that I just tagged Razer Comms for deletion, because it seems to be promotional, rather than an encyclopedia article.
If you feel that the article shouldn't be deleted and want more time to work on it, you can contest this deletion, but please don't remove the speedy deletion tag from the top.
You can leave a note on my talk page if you have questions. Op47 (talk) 19:23, 25 January 2014 (UTC)
VisualEditor Newsletter—February 2014
Since the last newsletter, the VisualEditor team has worked on some small changes to the user interface, such as moving the reference item to the top of the Insert menu, as well as some minor features and fixing bugs, especially for rich copying and pasting of references.
The biggest change was the addition of more features to the image dialog, including the ability to set alignment (left, right, center), framing options (thumbnail, frame, frameless, and none), adding alt text, and defining the size manually. There is still some work to be done here, including a quick way to set the default size.
- The main priority is redesigning the reference dialog, with the goal of providing autofill features for ISBNs and URLs and streamlining the process. Current concept drawings are available at mw:VisualEditor/Design/Reference Dialog. Please share your ideas about making referencing quick and easy with the designers.
- A few bugs in the existing reference dialog were fixed. The toolbar was simplified to remove galleries and lists from the reference dialog. When you re-use references, it now correctly displays the references again, rather than just the number and name. If you paste content into a dialog that can't fit there (e.g.
==section headings==
in references), it now strips out the inappropriate HTML. - You can now edit image galleries inside VisualEditor. At this time, the gallery tool is a very limited option that gives you access to the wikitext. It will see significant improvements at a later date.
- The character inserter tool in the "Insert" menu is being redesigned. Your feedback on the special character inserter is still wanted, especially if you depend on Wikipedia's character inserters for your normal editing rather than using the ones built into your computer.
- You can now see a help page about keyboard shortcuts in the page menu (three bars next to the Cancel button) (T54844).
- If you edit categories, your changes will now display correctly after saving the page (T50560).
- Saving the page should be faster now (T61660).
- Any community can ask to test a new tool to edit TemplateData by leaving a note at T53734.
Looking ahead: The link tool will tell you when you're linking to a disambiguation or redirect page. The warning about wikitext will hide itself after you remove the wikitext markup in that paragraph. Support for creating and editing redirects is in the pipeline. Looking further out, image handling will be improved, including default and upright sizes. The developers are also working on support for viewing and editing hidden HTML comments, some behavioral magic words like DISPLAYTITLE, and in-line language setting (dir="rtl"
).
If you have questions or suggestions for future improvements, or if you encounter problems, please let everyone know by posting a note at Wikipedia:VisualEditor/Feedback. Thank you! Whatamidoing (WMF) 04:21, 20 February 2014 (UTC)
VisualEditor newsletter—March 2014
Since the last newsletter, the VisualEditor team has mostly worked on changes to the template and image dialogs.
The biggest change in the last few weeks was the redesign of the template dialog. The template dialog now opens in a simplified mode that lists parameters and their descriptions. (The complex multi-item transclusion mode can be reached by clicking on "Show options" from inside the simplified template dialog.) Template parameters now have a bigger, auto-sizing input box for easier editing. With today's update, searching for template parameters will become case-insensitive, and required template parameters will display an asterisk (*) next to their edit boxes. In addition to making it quicker and easier to see everything when you edit typical templates, this work was necessary to prepare for the forthcoming simplified citation dialog. The main priority in the coming weeks is building this new citation dialog, with the ultimate goal of providing autofill features for ISBNs, URLs, DOIs and other quick-fills. This will add a new button on the toolbar, with the citation templates available picked by each wiki's community. Concept drawings can be seen at mw:VisualEditor/Design/Reference Dialog. Please share your ideas about making referencing quick and easy with the designers.
- The link tool now tells you when you're linking to a disambiguation or redirect page. Pages that exist, but are not indexed by the search engine, are treated like non-existent pages (T56361).
- Wikitext warnings will now hide when you remove wikitext from the paragraph you are editing.
- The character inserter tool in the "Insert" menu has been slightly redesigned, to introduce larger buttons. Your suggestions for more significant changes to the special character inserter are still wanted.
- The page options menu (three bars, next to the Cancel button) has expanded. You can create and edit redirect pages, set page options like
__STATICREDIRECT__
,__[NO]INDEX__
and__
[NO]NEWEDITSECTION__
, and more. New keyboard shortcuts are listed there, and include undoing the last action, clearing formatting, and showing the shortcut help window. If you switch from VisualEditor to wikitext editing, your edit will now be tagged. - It is easier to edit images. There are more options and they are explained better. If you add new images to pages, they will also be default size. You can now set image sizes to the default, if another size was previously specified. Full support for upright sizing systems, which more readily adapt image sizes to the reader's screen size, is planned.
- VisualEditor adds fake blank lines so you can put your cursor there. These "slugs" are now smaller than normal blank lines, and are animated to be different from actual blank lines.
- You can use the Ctrl+Alt+S or ⌘ Command+⌥ Option+S shortcuts to open the save window, and you can preview your edit summary when checking your changes in the save window.
- After community requests, VisualEditor has been deployed to the Interlingual Occidental Wikipedia, the Portuguese Wikibooks, and the French Wikiversity.
- Any community can ask for custom icons for their language in the character formatting menu (bold, italic, etc.) by making a request on Bugzilla or by contacting Product Manager James Forrester.
The developers apologize for a regression bug with the deployment on 6 March 2014, which caused the incorrect removal of |upright
size definitions on a handful of pages on the English Wikipedia, among others. The root cause was fixed, and the broken pages were fixed soon after.
Looking ahead: Several template dialogs will become more compact. Looking further out, the developers are also working on support for viewing and editing hidden HTML comments. You will be able to see the Table of Contents change live as you edit the page, rather than it being hidden. In-line language setting (dir="rtl"
) may be offered to a few Wikipedias soon.
If you have questions or suggestions for future improvements, or if you encounter problems, please let everyone know by posting a note at Wikipedia:VisualEditor/Feedback or by joining the office hours on 19 April 2014 at 2000 UTC. Thank you! MediaWiki message delivery (talk) 22:44, 20 March 2014 (UTC)
The WikiProject Video Games Newsletter, Q1 2014
The WikiProject Video Games Newsletter
Volume 7, No. 1 — 1st Quarter, 2014
Previous issue | Index | Next issue
Project At a Glance
As of Q1 2014, the project has:
|
Content
|
VisualEditor newsletter—April 2014
Since the last newsletter, the VisualEditor team has mostly worked on performance improvements, image settings, and preparation for a simplified citation template tool in its own menu.
- In an oft-requested improvement, VisualEditor now displays red links (links to non-existent pages) in the proper color. Links to sister projects and external URLs are still the same blue as local links.
- You can now open templates by double-clicking them or by selecting them and pressing Return. This also works for references, images, galleries, mathematical equations, and other "nodes".
- VisualEditor has been disabled for pages that were created as translations of other pages using the Translate extension (common at Meta and MediaWiki.org). If a page has been marked for translation, you will see a warning if you try to edit it using VisualEditor.
- When you try to edit protected pages with VisualEditor, the full protection notice and most recent log entry are displayed. Blocked users see the standard message for blocked users.
- The developers fixed a bug that caused links on sub-pages to point to the wrong location.
- The size-changing controls in the advanced settings section of the media or image dialog were simplified further. VisualEditor's media dialog supports more image display styles, like borderless images.
- If there is not enough space on your screen to display all of the tabs (for instance, if your browser window is too narrow), the second edit tab will now fold into the drop-down menu (where the "Move" item is currently housed). On the English Wikipedia, this moves the "Edit beta" tab into the menu; on most projects, it moves the "Edit source" tab. This is only enabled in the default Vector skin, not for Monobook users. See this image for an example showing the "Edit source" and "View history" tabs after they moved into the drop-down menu.
- After community requests, VisualEditor has been deployed as an opt-in feature at Meta and on the French Wikinews.
Looking ahead: A new, locally controlled menu of citation templates will put citations immediately in front of users. You will soon be able to see the Table of Contents while editing. Support for upright image sizes (preferred for accessibility) is being developed. In-line language setting (dir="rtl"
) will be offered as a Beta Feature soon. Looking further out, the developers are also working on support for viewing and editing hidden HTML comments. It will be possible to upload images to Commons from inside VisualEditor.
If you have questions or suggestions for future improvements, or if you encounter problems, please let everyone know by posting a note at Wikipedia:VisualEditor/Feedback or by joining the office hours on Monday, 19 May 2014 at 18:00 UTC. If you'd like to get this on your own page, subscribe at Wikipedia:VisualEditor#Newsletter for English Wikipedia only or at meta:VisualEditor/Newsletter for any project. Thank you! Whatamidoing (WMF) (talk) 20:23, 23 April 2014 (UTC)
Because you thanked me
You thanked me for one of my recent edits, so here is a heart-felt... YOU'RE WELCOME! It's a pleasure, and I sincerely hope that you enjoy your continued improvement of this inspiring encyclopedia! – Paine |
18:58, 20 May 2014 (UTC)
VisualEditor newsletter—May 2014
Did you know?
Since the last newsletter, the VisualEditor team has mostly worked on the new citation tool, improving performance, reducing technical debt, and other infrastructure needs.
The biggest change in the last few weeks is the new citation template menu, labeled "⧼visualeditor-toolbar-cite-label⧽". The new citation menu offers a locally configurable list of citation templates on the main toolbar. It adds or opens references using the simplified template dialog that was deployed last month. This tool is in addition to the "⧼visualeditor-dialogbutton-reference-tooltip⧽" item in the "Insert" menu, and it is not displayed unless it has been configured for that wiki. To enable this tool on your wiki, see the instructions at VisualEditor/Citation tool.
Eventually, the VisualEditor team plans to add autofill features for these citations. When this long-awaited feature is created, you could add an ISBN, URL, DOI or other identifier to the citation tool, and VisualEditor would automatically fill in as much information for that source as possible. The concept drawings can be seen at mw:VisualEditor/Design/Reference Dialog, and your ideas about making referencing quick and easy are still wanted.
- There is a new Beta Feature for setting content language and direction. This allows editors who have opted in to use the "Language" tool in the "Insert" menu to add HTML span tags that label text with the language and as being left-to-right (LTR) or right-to-left (RTL), like this:
<span lang="en" dir="ltr">English</span>
. This tool is most useful for pages whose text combines multiple languages with different directions, common on Right-to-Left wikis. - The tool for editing mathematics formulae in VisualEditor has been slightly updated and is now available to all users, as the "⧼math-visualeditor-mwmathinspector-title⧽" item in the "Insert" menu. It uses LaTeX like in the wikitext editor.
- The layout of template dialogs has been changed, putting the label above the field. Parameters are now called "fields", to avoid a technical term that many editors are unfamiliar with.
- TemplateData has been expanded: You can now add "suggested" parameters in TemplateData, and VisualEditor will display them in the template dialogs like required ones. "Suggested" is recommended for parameters that are commonly used, but not actually required to make the template work. There is also a new type for TemplateData parameters: wiki-file-name, for file names. The template tool can now tell you if a parameter is marked as being obsolete.
- Some templates that previously displayed strangely due to absolute CSS positioning hacks should now display correctly.
- Several messages have changed: The notices shown when you save a page have been merged into those used in the wikitext editor, for consistency. The message shown when you "⧼visualeditor-toolbar-cancel⧽" out of an edit is clearer. The beta dialog notice, which is shown the first time you open VisualEditor, will be hidden for logged-in users via a user preference rather than a cookie. As a result of this change, the beta notice will show up one last time for all logged-in users on their next VisualEditor use after Thursday's upgrade.
- Adding a category that is a redirect to another category prompts you to add the target category instead of the redirect.
- In the "Images and media" dialog, it is no longer possible to set a redundant border for thumbnail and framed images.
- There is a new Template Documentation Editor for TemplateData. You can test it by editing a documentation subpage (not a template page) at Mediawiki.org: edit mw:Template:Sandbox/doc, and then click "Manage template documentation" above the wikitext edit box. If your community would like to use this TemplateData editor at your project, please contact product manager James Forrester or file an enhancement request in Bugzilla.
- There have been multiple small changes to the appearance: External links are shown in the same light blue color as in MediaWiki. This is a lighter shade of blue than the internal links. The styling of the "Style text" (character formatting) drop-down menu has been synchronized with the recent font changes to the Vector skin. VisualEditor dialogs, such as the "⧼visualeditor-toolbar-savedialog⧽" dialog, now use a "loading" animation of moving lines, rather than animated GIF images. Other changes were made to the appearance upon opening a page in VisualEditor which should make the transition between reading and editing be smoother.
- The developers merged in many minor fixes and improvements to MediaWiki interface integration (e.g., edit notices), and made VisualEditor handle Education Program pages better.
- At the request of the community, VisualEditor has been deployed to Commons as an opt-in. It is currently available by default for 161 Wikipedia language editions and by opt-in through Beta Features at all others, as well as on several non-Wikipedia sites.
Looking ahead: The toolbar from the PageTriage extension will no longer be visible inside VisualEditor. More buttons and icons will be accessible from the keyboard. The "Keyboard shortcuts" link will be moved out of the "Page options" menu, into the "Help" menu. Support for upright image sizes (preferred for accessibility) and inline images is being developed. You will be able to see the Table of Contents while editing. Looking further out, the developers are also working on support for viewing and editing hidden HTML comments. VisualEditor will be available to all users on mobile devices and tablet computers. It will be possible to upload images to Commons from inside VisualEditor.
If you have questions or suggestions for future improvements, or if you encounter problems, please let everyone know by posting a note at mw:VisualEditor/Feedback or by joining the office hours on Thursday, 19 June 2014 at 10:00 UTC. If you'd like to get this newsletter on your own page (about once a month), please subscribe at w:en:Wikipedia:VisualEditor/Newsletter for English Wikipedia only or at meta:VisualEditor/Newsletter for any project. Thank you! Whatamidoing (WMF) 22:16, 21 May 2014 (UTC)
VisualEditor global newsletter—June 2014
Did you know?
The VisualEditor team is mostly working to fix bugs, improve performance, reduce technical debt, and other infrastructure needs. You can find on Mediawiki.org weekly updates detailing recent work.
- They have moved the "Keyboard shortcuts" link out of the "Page options" menu, into the "Help" menu. Within dialog boxes, buttons are now more accessible (via the Tab key) from the keyboard.
- You can now see the target of the link when you click on it, without having to open the inspector.
- The team also expanded TemplateData: You can now add a parameter type "
date"
for dates and times in the ISO 8601 format, and "boolean"
for values which are true or false. Also, templates that redirect to other templates (like{{citeweb}}
→{{cite web}}
) now get the TemplateData of their target (bug 50964). You can test TemplateData by editing mw:Template:Sandbox/doc. - Category: and File: pages now display their contents correctly after saving an edit (bug 65349, bug 64239)
- They have also improved reference editing: You should no longer be able to add empty citations with VisualEditor (bug 64715), as with references. When you edit a reference, you can now empty it and click the "use an existing reference" button to replace it with another reference instead.
- It is now possible to edit inline images with VisualEditor. Remember that inline images cannot display captions, so existing captions get removed. Many other bugs related to images were also fixed.
- You can now add and edit
{{DISPLAYTITLE}}
and__DISAMBIG__
in the "Page options" menu, rounding out the full set of page options currently planned. - The tool to insert special characters is now wider and simpler.
Looking ahead
The VisualEditor team has posted a draft of their goals for the next fiscal year. You can read them and suggest changes on MediaWiki.org.
The team posts details about planned work on VisualEditor's roadmap. You will soon be able to drag-and-drop text as well as images. If you drag an image to a new place, it won't let you place it in the middle of a paragraph. All dialog boxes and windows will be simplified based on user testing and feedback. The VisualEditor team plans to add autofill features for citations. Your ideas about making referencing quick and easy are still wanted. Support for upright image sizes is being developed. The designers are also working on support for viewing and editing hidden HTML comments and adding rows and columns to tables.
Supporting your wiki
Please read VisualEditor/Citation tool for information on configuring the new citation template menu, labeled "⧼visualeditor-toolbar-cite-label⧽". This menu will not appear unless it has been configured on your wiki.
If you speak a language other than English, we need your help with translating the user guide. The guide is out of date or incomplete for many languages, and what's on your wiki may not be the most recent translation. Please contact me if you need help getting started with translation work on MediaWiki.org.
VisualEditor can be made available to most non-Wikipedia projects. If your community would like to test VisualEditor, please contact product manager James Forrester or file an enhancement request in Bugzilla.
Please share your questions, suggestions, or problems by posting a note at mw:VisualEditor/Feedback or by joining the office hours on Saturday, 19 July 2014 at 21:00 UTC (daytime for the Americas and Pacific Islands) or on Thursday, 14 August 2014 at 9:00 UTC (daytime for Europe, Middle East, Asia).
To change your subscription to this newsletter, please see the subscription pages on Meta or the English Wikipedia. Thank you! Whatamidoing (WMF) (talk) 04:59, 25 June 2014 (UTC)
The WikiProject Video Games Newsletter, Q2 2014
The WikiProject Video Games Newsletter
Volume 7, No. 2 — 2nd Quarter, 2014
Previous issue | Index | Next issue
Project At a Glance
As of Q2 2014, the project has:
|
Content
|
MediaWiki message delivery (talk) 04:06, 4 July 2014 (UTC)
VisualEditor newsletter—July and August 2014
The VisualEditor team is currently working mostly to fix bugs, improve performance, reduce technical debt, and other infrastructure needs. You can find on Mediawiki.org weekly updates detailing recent work.
The biggest visible change since the last newsletter was to the dialog boxes. The design for each dialog box and window was simplified. The most commonly needed buttons are now at the top. Based on user feedback, the buttons are now labeled with simple words (like "Cancel" or "Done") instead of potentially confusing icons (like "<" or "X"). Many of the buttons to edit links, images, and other items now also show the linked page, image name, or other useful information when you click on them.
- Hidden HTML comments (notes visible to editors, but not to readers) can now be read, edited, inserted, and removed. A small icon (a white exclamation mark on a dot) marks the location of each comments. You can click on the icon to see the comment.
- You can now drag and drop text and templates as well as images. A new placement line makes it much easier to see where you are dropping the item. Images can no longer be dropped into the middle of paragraphs.
- All references and footnotes (
<ref>
tags) are now made through the "⧼visualeditor-toolbar-cite-label⧽" menu, including the "⧼visualeditor-dialogbutton-reference-tooltip⧽" (manual formatting) footnotes and the ability to re-use an existing citation, both of which were previously accessible only through the "Insert" menu. The "⧼visualeditor-dialogbutton-referencelist-tooltip⧽" is still added via the "Insert" menu. - When you add an image or other media file, you are now prompted to add an image caption immediately. You can also replace an image whilst keeping the original caption and other settings.
- All tablet users visiting the mobile web version of Wikipedias will be able to opt-in to a version of VisualEditor from 14 August. You can test the new tool by choosing the beta version of the mobile view in the Settings menu.
- The link tool has a new "Open" button that will open a linked page in another tab so you can make sure a link is the right one.
- The "Cancel" button in the toolbar has been removed based on user testing. To cancel any edit, you can leave the page by clicking the Read tab, the back button in your browser, or closing the browser window without saving your changes.
Looking ahead
The team posts details about planned work on the VisualEditor roadmap. The VisualEditor team plans to add auto-fill features for citations soon. Your ideas about making referencing quick and easy are still wanted. Support for upright image sizes is being developed. The designers are also working on support for adding rows and columns to tables. Work to support Internet Explorer is ongoing.
Feedback opportunities
The Editing team will be making two presentations this weekend at Wikimania in London. The first is with product manager James Forrester and developer Trevor Parscal on Saturday at 16:30. The second is with developers Roan Kattouw and Trevor Parscal on Sunday at 12:30.
Please share your questions, suggestions, or problems by posting a note at the VisualEditor feedback page or by joining the office hours discussion on Thursday, 14 August 2014 at 09:00 UTC (daytime for Europe, Middle East and Asia) or on Thursday, 18 September 2014 at 16:00 UTC (daytime for the Americas; evening for Europe).
If you'd like to get this newsletter on your own page (about once a month), please subscribe at w:en:Wikipedia:VisualEditor/Newsletter for English Wikipedia only or at Meta for any project. Thank you! Whatamidoing (WMF) (talk) 18:14, 8 August 2014 (UTC)
The WikiProject Video Games Newsletter, Q3 2014
The WikiProject Video Games Newsletter
Volume 7, No. 3 — 3rd Quarter, 2014
Previous issue | Index | Next issue
Project At a Glance
As of Q3 2014, the project has:
|
|
Content
|
MediaWiki message delivery (talk) 00:30, 2 October 2014 (UTC)
VisualEditor newsletter—September and October 2014
Since the last newsletter, the Editing team has reduced technical debt, simplified some workflows for template and citation editing, made major progress on Internet Explorer support, and fixed over 125 bugs and requests. Several performance improvements were made, especially to the system around re-using references and reference lists. Weekly updates are posted on Mediawiki.org.
There were three issues that required urgent fixes: a deployment error that meant that many buttons didn't work correctly (bugs 69856 and 69864), a problem with edit conflicts that left the editor with nowhere to go (bug 69150), and a problem in Internet Explorer 11 that caused replaced some categories with a link to the system message, MediaWiki:Badtitletext (bug 70894) when you saved. The developers apologize for the disruption, and thank the people who reported these problems quickly.
Increased support for devices and browsers
Internet Explorer 10 and 11 users now have access to VisualEditor. This means that about 5% of Wikimedia's users will now get an "Edit" tab alongside the existing "Edit source" tab. Support for Internet Explorer 9 is planned for the future.
Tablet users browsing the site's mobile mode now have the option of using a mobile-specific form of VisualEditor. More editing tools, and availability of VisualEditor on smartphones, is planned for the future. The mobile version of VisualEditor was tweaked to show the context menu for citations instead of basic references (bug 68897). A bug that broke the editor in iOS was corrected and released early (bug 68949). For mobile tablet users, three bugs related to scrolling were fixed (bug 66697, bug 68828, bug 69630). You can use VisualEditor on the mobile version of Wikipedia from your tablet by clicking on the cog in the top-right when editing a page and choosing which editor to use.
TemplateData editor
A tool for editing TemplateData will be deployed to more Wikipedias soon. Other Wikipedias and some other projects may receive access next month. This tool makes it easier to add TemplateData to the template's documentation. When the tool is enabled, it will add a button above every editing window for a template (including documentation subpages). To use it, edit the template or a subpage, and then click the "Edit template data" button at the top. Read the help page for TemplateData. You can test the TemplateData editor in a sandbox at Mediawiki.org. Remember that TemplateData should be placed either on a documentation subpage or on the template page itself. Only one block of TemplateData will be used per template.
Other changes
Several interface messages and labels were changed to be simpler, clearer, or shorter, based on feedback from translators and editors. The formatting of dialogs was changed, and more changes to the appearance will be coming soon, when VisualEditor implements the new MediaWiki theme from Design. (A preview of the theme is available on Labs for developers.) The team also made some improvements for users of the Monobook skin that improved the size of text in toolbars and fixed selections that overlapped menus.
VisualEditor-MediaWiki now supplies the mw-redirect
or mw-disambig
class on links to redirects and disambiguation pages, so that user gadgets that colour in these in types of links can be created.
Templates' fields can be marked as 'required' in TemplateData. If a parameter is marked as required, then you cannot delete that field when you add a new template or edit an existing one (bug 60358).
Language support improved by making annotations use bi-directional isolation (so they display correctly with cursoring behaviour as expected) and by fixing a bug that crashed VisualEditor when trying to edit a page with a dir
attribute but no lang
set (bug 69955).
Looking ahead
The team posts details about planned work on the VisualEditor roadmap. The VisualEditor team plans to add auto-fill features for citations soon, perhaps in late October.
The team is also working on support for adding rows and columns to tables, and early work for this may appear within the month. Please comment on the design at Mediawiki.org.
In the future, real-time collaborative editing may be possible in VisualEditor. Some early preparatory work for this was recently done.
Supporting your wiki
At Wikimania, several developers gave presentations about VisualEditor. A translation sprint focused on improving access to VisualEditor was supported by many people. Deryck Chan was the top translator. Special honors also go to संजीव कुमार (Sanjeev Kumar), Robby, Takot, Bachounda, Bjankuloski06 and Ата. A summary of the work achieved by the translation community has been posted here. Thank you all for your work.
VisualEditor can be made available to most non-Wikipedia projects. If your community would like to test VisualEditor, please contact product manager James Forrester or file an enhancement request in Bugzilla.
Please join the office hours on Saturday, 18 October 2014 at 18:00 UTC (daytime for the Americas; evening for Africa and Europe) and on Wednesday, 19 November at 16:00 UTC on IRC.
Give feedback on VisualEditor at mw:VisualEditor/Feedback. Subscribe or unsubscribe at Meta. To help with translations, please subscribe to the Translators mailing list or contact Elitre at Meta. Thank you!
VisualEditor newsletter—November 2014
Since the last newsletter, the Editing Team has fixed many bugs and requests, and worked on support for editing tables and for using non-Latin languages. Their weekly updates are posted on Mediawiki.org. Informal notes from the recent quarterly review were posted on Meta.
Recent improvements
The French Wikipedia should see better search results for links, templates, and media because the new search engine was turned on for everyone there. This change is expected at the Chinese and German Wikipedias next week, and eventually at the English Wikipedia.
The "pawn" system has been mostly replaced. Bugs in this system sometimes added a chess pawn character to wikitext. The replacement provides better support for non-Latin languages, with full support hopefully coming soon.
VisualEditor is now provided to editors who use Internet Explorer 10 or 11 on desktop and mobile devices. Internet Explorer 9 is not supported yet.
The keyboard shortcuts for items in the toolbar's menus are now shown in the menus. VisualEditor will replace the existing design with a new theme from the User Experience / Design group. The appearance of dialogs has already changed in one Mobile version. The appearance on desktops will change soon. (You can see a developer preview of the old "Apex" design and the new "MediaWiki" theme which will replace it.)
Several bugs were fixed for internal and external links. Improvements to MediaWiki's search solved an annoying problem: If you searched for the full name of the page or file that you wanted to link, sometimes the search program could not find the page. A link inside a template, to a local page that does not exist, will now show red, exactly as it does when reading the page. Due to a error, for about two weeks this also affected all external links inside templates. Opening an auto-numbered link node like [2] with the keyboard used to open the wrong link tool. These problems have all been fixed.
TemplateData
The tool for quickly editing TemplateData will be deployed to all Wikimedia Foundation wikis on Thursday, 6 November. This tool is already available on the biggest 40 Wikipedias, and now all wikis will have access to it. This tool makes it easier to add TemplateData to the template's documentation. When the tool is enabled, it will add a button above every editing window for a template (including documentation subpages). To use it, edit the template or a subpage, and then click the "Edit template data" button at the top. Read the help page for TemplateData. You can test the TemplateData editor in a sandbox at Mediawiki.org. Remember that TemplateData should be placed either on a documentation subpage or on the template page itself. Only one block of TemplateData will be used per template.
You can use the new autovalue setting to pre-load a value into a template. This can be used to substitute dates, as in this example, or to add the most common response for that parameter. The autovalue can be easily overridden by the editor, by typing something else in the field.
In TemplateData, you may define a parameter as "required". The template dialog in VisualEditor will warn editors if they leave a "required" parameter empty, and they will not be able to delete that parameter. If the template can function without this parameter, then please mark it as "suggested" or "optional" in TemplateData instead.
Looking ahead
Basic support for inserting tables and changing the number of rows and columns in tables will appear next Wednesday. Advanced features, like dragging columns to different places, will be possible later. The VisualEditor team plans to add auto-fill features for citations soon. To help editors find the most important items more quickly, some items in the toolbar menus will be hidden behind a "More" item, such as "underlining" in the styling menu. The appearance of the media search dialog will improve, to make picking between possible images easier and more visual. The team posts details about planned work on the VisualEditor roadmap.
The user guide will be updated soon to add information about editing tables. The translations for most languages except Spanish, French, and Dutch are significantly out of date. Please help complete the current translations for users who speak your language. Talk to us if you need help exporting the translated guide to your wiki.
You can influence VisualEditor's design. Tell the VisualEditor team what you want changed during the office hours via IRC. The next sessions are on Wednesday, 19 November at 16:00 UTC and on Wednesday 7 January 2015 at 22:00 UTC. You can also share your ideas at mw:VisualEditor/Feedback.
Also, user experience researcher Abbey Ripstra is looking for editors to show her how they edit Wikipedia. Please sign up for the research program if you would like to hear about opportunities.
If you would like to help with translations of this newsletter, please subscribe to the Translators mailing list or contact us directly, so that we can notify you when the next issue is ready. Subscribe or unsubscribe at Wikipedia:VisualEditor/Newsletter. Thank you!
— Whatamidoing (WMF) 20:41, 6 November 2014 (UTC)
VisualEditor newsletter—December 2014
Did you know?
Since the last newsletter, the Editing Team has fixed many bugs and worked on table editing and performance. Their weekly status reports are posted on Mediawiki.org. Upcoming plans are posted at the VisualEditor roadmap.
VisualEditor was deployed to several hundred remaining wikis as an opt-in beta feature at the end of November, except for most Wiktionaries (which depend heavily upon templates) and all Wikisources (which await integration with ProofreadPage).
Recent improvements
Basic support for editing tables is available. You can insert new tables, add and remove rows and columns, set or remove a caption for a table, and merge cells together. To change the contents of a cell, double-click inside it. More features will be added in the coming months. In addition, VisualEditor now ignores broken, invalid rowspan
and colspan
elements, instead of trying to repair them.
You can now use find and replace in VisualEditor, reachable through the tool menu or by pressing ⌃ Ctrl+F or ⌘ Cmd+F.
You can now create and edit simple <blockquote>
paragraphs for quoting and indenting content. This changes a "Paragraph" into a "Block quote".
Some new keyboard sequences can be used to format content. At the start of the line, typing "* " will make the line a bullet list; "1. " or "# " will make it a numbered list; "==" will make it a section heading; ": " will make it a blockquote. If you didn't mean to use these tools, you can press undo to undo the formatting change. There are also two other keyboard sequences: "[[" for opening the link tool, and "{{" for opening the template tool, to help experienced editors. The existing standard keyboard shortcuts, like ⌃ Ctrl+K to open the link editor, still work.
If you add a category that has been redirected, then VisualEditor now adds its target. Categories without description pages show up as red.
You can again create and edit galleries as wikitext code.
Looking ahead
VisualEditor will replace the existing design with a new theme designed by the User Experience group. The new theme will be visible for desktop systems at MediaWiki.org in late December and at other sites early January. (You can see a developer preview of the old "Apex" theme and the new "MediaWiki" one which will replace it.)
The Editing team plans to add auto-fill features for citations in January. Planned changes to the media search dialog will make choosing between possible images easier.
Help
- Share your ideas and ask questions at mw:VisualEditor/Feedback.
- Translations of the user guide for most languages are oudated. Ukrainian, Portuguese, Spanish, French, and Dutch translators are nearly current. Please help complete the current translations for users who speak your language.
- Talk to the Editing team during the office hours via IRC. The next session is on Wednesday, 7 January 2015 at 22:00 UTC.
- File requests for language-appropriate "Bold" and "Italic" icons for the character formatting menu in Phabricator.
- The design research team wants to see how real editors work. Please sign up for their research program.
If you would like to help with translations of this newsletter, please subscribe to the Translators mailing list or contact us directly, so that we can notify you when the next issue is ready. Subscribe or unsubscribe at Meta.
Thank you! WhatamIdoing (WMF) (talk) 23:37, 20 December 2014 (UTC)
The WikiProject Video Games Newsletter, Q4 2014
The WikiProject Video Games Newsletter
Volume 7, No. 4 — 4th Quarter, 2014
Previous issue | Index | Next issue
Project At a Glance
As of Q4 2014, the project has:
|
Content
|
MediaWiki message delivery (talk) 16:22, 7 January 2015 (UTC)
VisualEditor News 2015—#1
Since the last newsletter, the Editing Team has fixed many bugs and worked on VisualEditor's appearance, the coming Citoid reference service, and support for languages with complex input requirements. Status reports are posted on Mediawiki.org. Upcoming plans are posted at the VisualEditor roadmap.
The Wikimedia Foundation has named its top priorities for this quarter (January to March). The first priority is making VisualEditor ready for deployment by default to all new users and logged-out users at the remaining large Wikipedias. You can help identify these requirements. There will be weekly triage meetings which will be open to volunteers beginning Wednesday, 11 February 2015 at 12:00 (noon) PST (20:00 UTC). Tell Vice President of Engineering Damon Sicore, Product Manager James Forrester and other team members which bugs and features are most important to you. The decisions made at these meetings will determine what work is necessary for this quarter's goal of making VisualEditor ready for deployment to new users. The presence of volunteers who enjoy contributing MediaWiki code is particularly appreciated. Information about how to join the meeting will be posted at mw:Talk:VisualEditor/Portal shortly before the meeting begins.
Due to some breaking changes in MobileFrontend and VisualEditor, VisualEditor was not working correctly on the mobile site for a couple of days in early January. The teams apologize for the problem.
Recent improvements
The new design for VisualEditor aligns with MediaWiki's Front-End Standards as led by the Design team. Several new versions of the OOjs UI library have also been released, and these also affect the appearance of VisualEditor and other MediaWiki software extensions. Most changes were minor, like changing the text size and the amount of white space in some windows. Buttons are consistently color-coded to indicate whether the action:
- starts a new task, like opening the ⧼visualeditor-toolbar-savedialog⧽ dialog: blue ,
- takes a constructive action, like inserting a citation: green ,
- might remove or lose your work, like removing a link: red , or
- is neutral, like opening a link in a new browser window: gray.
The TemplateData editor has been completely re-written to use a different design (T67815) based on the same OOjs UI system as VisualEditor (T73746). This change fixed a couple of existing bugs (T73077 and T73078) and improved usability.
Search and replace in long documents is now faster. It does not highlight every occurrence if there are more than 100 on-screen at once (T78234).
Editors at the Hebrew and Russian Wikipedias requested the ability to use VisualEditor in the "Article Incubator" or drafts namespace (T86688, T87027). If your community would like VisualEditor enabled on another namespace on your wiki, then you can file a request in Phabricator. Please include a link to a community discussion about the requested change.
Looking ahead
The Editing team will soon add auto-fill features for citations. The Citoid service takes a URL or DOI for a reliable source, and returns a pre-filled, pre-formatted bibliographic citation. After creating it, you will be able to change or add information to the citation, in the same way that you edit any other pre-existing citation in VisualEditor. Support for ISBNs, PMIDs, and other identifiers is planned. Later, editors will be able to contribute to the Citoid service's definitions for each website, to improve precision and reduce the need for manual corrections.
We will need editors to help test the new design of the special character inserter, especially if you speak Welsh, Breton, or another language that uses diacritics or special characters extensively. The new version should be available for testing next week. Please contact User:Whatamidoing (WMF) if you would like to be notified when the new version is available. After the special character tool is completed, VisualEditor will be deployed to all users at Phase 5 Wikipedias. This will affect about 50 mid-size and smaller Wikipedias, including Afrikaans, Azerbaijani, Breton, Kyrgyz, Macedonian, Mongolian, Tatar, and Welsh. The date for this change has not been determined.
Let's work together
- Share your ideas and ask questions at mw:VisualEditor/Feedback.
- Please help complete translations of the user guide for users who speak your language.
- Join the weekly bug triage meetings beginning Wednesday, 11 February 2015 at 12:00 (noon) PST (20:00 UTC). Information about how to join the meeting will be posted at mw:Talk:VisualEditor/Portal shortly before the meeting begins. Contact James F. for more information.
- Talk to the Editing team during the office hours via IRC. The next session is on Thursday, 19 February 2015 at 19:00 UTC.
Subscribe or unsubscribe at Wikipedia:VisualEditor/Newsletter. Translations are available through Meta. Thank you! Whatamidoing (WMF) 20:23, 2 February 2015 (UTC)
The WikiProject Video Games Newsletter, Q1 2015
The WikiProject Video Games Newsletter
Volume 8, No. 1 — 1st Quarter, 2015
Previous issue | Index | Next issue
Project At a Glance
As of Q1 2015, the project has:
|
Content
|
MediaWiki message delivery (talk) 15:46, 1 April 2015 (UTC)
VisualEditor News #2—2015
Since the last newsletter, the Editing Team has fixed many bugs and worked on VisualEditor's performance, the Citoid reference service, and support for languages with complex input requirements. Status reports are posted on Mediawiki.org. The worklist for April through June is available in Phabricator.
The weekly task triage meetings continue to be open to volunteers, each Wednesday at 11:00 (noon) PDT (18:00 UTC). You do not need to attend the meeting to nominate a bug for consideration as a Q4 blocker. Instead, go to Phabricator and "associate" the Editing team's Q4 blocker project with the bug. Learn how to join the meetings and how to nominate bugs at mw:Talk:VisualEditor/Portal.
Recent improvements
VisualEditor is now substantially faster. In many cases, opening the page in VisualEditor is now faster than opening it in the wikitext editor. The new system has improved the code speed by 37% and network speed by almost 40%.
The Editing team is slowly adding auto-fill features for citations. This is currently available only at the French, Italian, and English Wikipedias. The Citoid service takes a URL or DOI for a reliable source, and returns a pre-filled, pre-formatted bibliographic citation. After creating it, you will be able to change or add information to the citation, in the same way that you edit any other pre-existing citation in VisualEditor. Support for ISBNs, PMIDs, and other identifiers is planned. Later, editors will be able to improve precision and reduce the need for manual corrections by contributing to the Citoid service's definitions for each website.
Citoid requires good TemplateData for your citation templates. If you would like to request this feature for your wiki, please post a request in the Citoid project on Phabricator. Include links to the TemplateData for the most important citation templates on your wiki.
The special character inserter has been improved, based upon feedback from active users. After this, VisualEditor was made available to all users of Wikipedias on the Phase 5 list on 30 March. This affected 53 mid-size and smaller Wikipedias, including Afrikaans, Azerbaijani, Breton, Kyrgyz, Macedonian, Mongolian, Tatar, and Welsh.
Work continues to support languages with complex requirements, such as Korean and Japanese. These languages use input method editors ("IMEs”). Recent improvements to cursoring, backspace, and delete behavior will simplify typing in VisualEditor for these users.
The design for the image selection process is now using a "masonry fit" model. Images in the search results are displayed at the same height but at variable widths, similar to bricks of different sizes in a masonry wall, or the "packed" mode in image galleries. This style helps you find the right image by making it easier to see more details in images.
You can now drag and drop categories to re-arrange their order of appearance on the page.
The pop-up window that appears when you click on a reference, image, link, or other element, is called the "context menu". It now displays additional useful information, such as the destination of the link or the image's filename. The team has also added an explicit "Edit" button in the context menu, which helps new editors open the tool to change the item.
Invisible templates are marked by a puzzle piece icon so they can be interacted with. Users also will be able to see and edit HTML anchors now in section headings.
Users of the TemplateData GUI editor can now set a string as an optional text for the 'deprecated' property in addition to boolean value, which lets you tell users of the template what they should do instead (T90734).
Looking ahead
The special character inserter in VisualEditor will soon use the same special character list as the wikitext editor. Admins at each wiki will also have the option of creating a custom section for frequently used characters at the top of the list. Instructions for customizing the list will be posted at mediawiki.org.
The team is discussing a test of VisualEditor with new users, to see whether they have met their goals of making VisualEditor suitable for those editors. The timing is unknown, but might be relatively soon.
Let's work together
- Share your ideas and ask questions at mw:VisualEditor/Feedback.
- Can you translate from English into any other language? Please check this list to see whether more interface translations are needed for your language. Contact us to get an account if you want to help!
- The design research team wants to see how real editors work. Please sign up for their research program.
- File requests for language-appropriate "Bold" and "Italic" icons for the character formatting menu in Phabricator.
Subscribe, unsubscribe or change the page where this newsletter is delivered at Meta. If you aren't reading this in your favorite language, then please help us with translations! Subscribe to the Translators mailing list or contact us directly, so that we can notify you when the next issue is ready. Thank you!
-Whatamidoing (WMF) (talk), 17:50, 3 April 2015 (UTC)
VisualEditor News #3—2015
Since the last newsletter, the Editing Team has created new interfaces for the link and citation tools, as well as fixing many bugs and changing some elements of the design. Some of these bugs affected users of VisualEditor on mobile devices. Status reports are posted on Mediawiki.org. The worklist for April through June is available in Phabricator.
A test of VisualEditor's effect on new editors at the English Wikipedia has just completed the first phase. During this test, half of newly registered editors had VisualEditor automatically enabled, and half did not. The main goal of the study is to learn which group was more likely to save an edit and to make productive, unreverted edits. Initial results will be posted at Meta later this month.
Recent improvements
Auto-fill features for citations are available at a few Wikipedias through the citoid service. Citoid takes a URL or DOI for a reliable source, and returns a pre-filled, pre-formatted bibliographic citation. If Citoid is enabled on your wiki, then the design of the citation workflow changed during May. All citations are now created inside a single tool. Inside that tool, choose the tab you want (⧼citoid-citeFromIDDialog-mode-auto⧽, ⧼citoid-citeFromIDDialog-mode-manual⧽, or ⧼citoid-citeFromIDDialog-mode-reuse⧽). The cite button is now labeled with the word "⧼visualeditor-toolbar-cite-label⧽" rather than a book icon, and the autofill citation dialog now has a more meaningful label, "⧼Citoid-citeFromIDDialog-lookup-button⧽", for the submit button.
The link tool has been redesigned based on feedback from Wikipedia editors and user testing. It now has two separate sections: one for links to articles and one for external links. When you select a link, its pop-up context menu shows the name of the linked page, a thumbnail image from the linked page, Wikidata's description, and/or appropriate icons for disambiguation pages, redirect pages and empty pages. Search results have been reduced to the first five pages. Several bugs were fixed, including a dark highlight that appeared over the first match in the link inspector (T98085).
The special character inserter in VisualEditor now uses the same special character list as the wikitext editor. Admins at each wiki can also create a custom section for frequently used characters at the top of the list. Please read the instructions for customizing the list at mediawiki.org. Also, there is now a tooltip to describing each character in the special character inserter (T70425).
Several improvements have been made to templates. When you search for a template to insert, the list of results now contains descriptions of the templates. The parameter list inside the template dialog now remains open after inserting a parameter from the list, so that users don’t need to click on "⧼visualeditor-dialog-transclusion-add-param⧽" each time they want to add another parameter (T95696). The team added a new property for TemplateData, "Example", for template parameters. This optional, translatable property will show up when there is text describing how to use that parameter (T53049).
The design of the main toolbar and several other elements have changed slightly, to be consistent with the MediaWiki theme. In the Vector skin, individual items in the menu are separated visually by pale gray bars. Buttons and menus on the toolbar can now contain both an icon and a text label, rather than just one or the other. This new design feature is being used for the cite button on wikis where the Citoid service is enabled.
The team has released a long-desired improvement to the handling of non-existent images. If a non-existent image is linked in an article, then it is now visible in VisualEditor and can be selected, edited, replaced, or removed.
Let's work together
- Share your ideas and ask questions at mw:VisualEditor/Feedback.
- The weekly task triage meetings continue to be open to volunteers, each Wednesday at 12:00 (noon) PDT (19:00 UTC). Learn how to join the meetings and how to nominate bugs at mw:Talk:VisualEditor/Portal. You do not need to attend the meeting to nominate a bug for consideration as a Q4 blocker. Instead, go to Phabricator and "associate" the Editing team's Q4 blocker project with the bug.
- If your Wikivoyage, Wikibooks, Wikiversity, or other community wants to have VisualEditor made available by default to contributors, then please contact James Forrester.
- If you would like to request the Citoid automatic reference feature for your wiki, please post a request in the Citoid project on Phabricator. Include links to the TemplateData for the most important citation templates on your wiki.
Subscribe, unsubscribe or change the page where this newsletter is delivered at Meta. If you aren't reading this in your favorite language, then please help us with translations! Subscribe to the Translators mailing list or contact us directly, so that we can notify you when the next issue is ready. Thank you! Whatamidoing (WMF) (talk) 17:31, 6 June 2015 (UTC)
The WikiProject Video Games Newsletter, Q2 2015
The WikiProject Video Games Newsletter
Volume 8, No. 2 — 2nd Quarter, 2015
Previous issue | Index | Next issue
Project At a Glance
As of Q2 2015, the project has:
|
|
Content
|
MediaWiki message delivery (talk) 13:19, 2 July 2015 (UTC)
VisualEditor News #4—2015
Read this in another language • Local subscription list • Subscribe to the multilingual edition
Since the last newsletter, the Editing Team have been working on mobile phone support. They have fixed many bugs and improved language support. They post weekly status reports on mediawiki.org. Their workboard is available in Phabricator. Their current priorities are improving language support and functionality on mobile devices.
Wikimania
The team attended Wikimania 2015 in Mexico City. There they participated in the Hackathon and met with individuals and groups of users. They also made several presentations about VisualEditor and the future of editing.
Following Wikimania, we announced winners for the VisualEditor 2015 Translathon. Our thanks and congratulations to users Halan-tul, Renessaince, जनक राज भट्ट (Janak Bhatta), Vahe Gharakhanyan, Warrakkk, and Eduardogobi.
For interface messages (translated at translatewiki.net), we saw the initiative affecting 42 languages. The average progress in translations across all languages was 56.5% before the translathon, and 78.2% after (+21.7%). In particular, Sakha improved from 12.2% to 94.2%; Brazilian Portuguese went from 50.6% to 100%; Taraškievica went from 44.9% to 85.3%; Doteli went from 1.3% to 41.2%. Also, while 1.7% of the messages were outdated across all languages before the translathon, the percentage dropped to 0.8% afterwards (-0.9%).
For documentation messages (on mediawiki.org), we saw the initiative affecting 24 languages. The average progress in translations across all languages was 26.6% before translathon, and 46.9% after (+20.3%). There were particularly notable achievements for three languages. Armenian improved from 1% to 99%; Swedish, from 21% to 99%, and Brazilian Portuguese, from 34% to 83%. Outdated translations across all languages were reduced from 8.4% before translathon to 4.8% afterwards (-3.6%).
We published some graphs showing the effect of the event on the Translathon page. Thank you to the translators for participating and the translatewiki.net staff for facilitating this initiative.
Recent improvements
Auto-fill features for citations can be enabled on each Wikipedia. The tool uses the citoid service to convert a URL or DOI into a pre-filled, pre-formatted bibliographic citation. You can see an animated GIF of the quick, simple process at mediawiki.org. So far, about a dozen Wikipedias have enabled the auto-citation tool. To enable it for your wiki, follow the instructions at mediawiki.org.
Your wiki can customize the first section of the special character inserter in VisualEditor. Please follow the instructions at mediawiki.org to put the characters you want at the top.
In other changes, if you need to fill in a CAPTCHA and get it wrong, then you can click to get a new one to complete. VisualEditor can now display and edit Vega-based graphs. If you use the Monobook skin, VisualEditor's appearance is now more consistent with other software.
Future changes
The team will be changing the appearance of selected links inside VisualEditor. The purpose is to make it easy to see whether your cursor is inside or outside the link. When you select a link, the link label (the words shown on the page) will be enclosed in a faint box. If you place your cursor inside the box, then your changes to the link label will be part of the link. If you place your cursor outside the box, then it will not. This will make it easy to know when new characters will be added to the link and when they will not.
On the English Wikipedia, 10% of newly created accounts are now offered both the visual and the wikitext editors. A recent controlled trial showed no significant difference in survival or productivity for new users in the short term. New users with access to VisualEditor were very slightly less likely to produce results that needed reverting. You can learn more about this by watching a video of the July 2015 Wikimedia Research Showcase. The proportion of new accounts with access to both editing environments will be gradually increased over time. Eventually all new users have the choice between the two editing environments.
Let's work together
- Share your ideas and ask questions at Wikipedia:VisualEditor/Feedback.
- Can you read and type in Korean or Japanese? Language engineer David Chan needs people who know which tools people use to type in some languages. If you speak Japanese or Korean, you can help him test support for these languages. Please see the instructions at mw:VisualEditor/IME Testing#What to test if you can help.
- If your wiki would like VisualEditor enabled on another namespace, you can file a request in Phabricator. Please include a link to a community discussion about the requested change.
- Please file requests for language-appropriate "Bold" and "Italic" icons for the styling menu in Phabricator.
- The design research team wants to see how real editors work. Please sign up for their research program.
- The weekly task triage meetings continue to be open to volunteers, usually on Tuesdays at 12:00 (noon) PDT (19:00 UTC). Learn how to join the meetings and how to nominate bugs at mw:VisualEditor/Weekly triage meetings. You do not need to attend the meeting to nominate a bug for consideration as a Q1 blocker, though. Instead, go to Phabricator and "associate" the main VisualEditor project with the bug.
If you aren't reading this in your favorite language, then please help us with translations! Subscribe to the Translators mailing list or contact Elitre directly, so that she can notify you when the next issue is ready. Thank you! Whatamidoing (WMF) (talk) 00:01, 8 August 2015 (UTC)
VisualEditor update
- This note is only delivered to English Wikipedia subscribers of the visual editor's newsletter.
The location of the visual editor's preference has been changed from the "Beta" tab to the "Editing" section of your preferences on this wiki. The setting now says Temporarily disable the visual editor while it is in beta. This aligns en.wiki with almost all the other WMF wikis; it doesn’t mean the visual editor is complete, or that it is no longer “in beta phase” though.
This action has not changed anything else for editors: it still honours editors’ previous choices about having it on or off; logged-out users continue to only have access to wikitext; the “Edit” tab is still after the “Edit source” one. You can learn more at the visual editor’s talk page.
We don’t expect this to cause any glitches, but in case your account no longer has the settings that you want, please accept our apologies and correct it in the Editing tab of Special:Preferences. Thank you for your attention, Elitre (WMF) -16:32, 7 October 2015 (UTC)
The WikiProject Video Games Newsletter, Q3 2015
The WikiProject Video Games Newsletter
Volume 8, No. 3 — 3nd Quarter, 2015
Previous issue | Index | Next issue
Project At a Glance
As of Q3 2015, the project has:
|
Content
|
MediaWiki message delivery (talk) 20:55, 13 October 2015 (UTC)
VisualEditor News #5—2015
Read this in another language • Subscription list for this multilingual newsletter
Since the last newsletter, the VisualEditor Team has fixed many bugs, added new features, and made some small design changes. They post weekly status reports on mediawiki.org. Their workboard is available in Phabricator. Their current priorities are improving support for languages like Japanese and Arabic, making it easier to edit on mobile devices, and providing rich-media tools for formulæ, charts, galleries and uploading.
Recent improvements
Educational features: The first time you use the visual editor, it now draws your attention to the Link and ⧼visualeditor-toolbar-cite-label⧽ tools. When you click on the tools, it explains why you should use them. (T108620) Alongside this, the welcome message for new users has been simplified to make editing more welcoming. (T112354) More in-software educational features are planned.
Links: It is now easier to understand when you are adding text to a link and when you are typing plain text next to it. (T74108, T91285) The editor now fully supports ISBN, PMID or RFC numbers. (T109498, T110347, T63558) These "magic links" use a custom link editing tool.
Uploads: Registered editors can now upload images and other media to Commons while editing. Click the new tab in the "Insert Images and media" tool. You will be guided through the process without having to leave your edit. At the end, the image will be inserted. This tool is limited to one file at a time, owned by the user, and licensed under Commons's standard license. For more complex situations, the tool links to more advanced upload tools. You can also drag the image into the editor. This will be available in the wikitext editor later.
Mobile: Previously, the visual editor was available on the mobile Wikipedia site only on tablets. Now, editors can use the visual editor on any size of device. (T85630) Edit conflicts were previously broken on the mobile website. Edit conflicts can now be resolved in both wikitext and visual editors. (T111894) Sometimes templates and similar items could not be deleted on the mobile website. Selecting them caused the on-screen keyboard to hide with some browsers. Now there is a new "Delete" button, so that these things can be removed if the keyboard hides. (T62110) You can also edit table cells in mobile now.
Rich editing tools: You can now add and edit sheet music in the visual editor. (T112925) There are separate tabs for advanced options, such as MIDI and Ogg audio files. (T114227 and T113354) When editing formulæ and other blocks, errors are shown as you edit. It is also possible to edit some types of graphs; adding new ones, and support for new types, will be coming.
On the English Wikipedia, the visual editor is now automatically available to anyone who creates an account. The preference switch was moved to the normal location, under Special:Preferences.
Future changes
You will soon be able to switch from the wikitext to the visual editor after you start editing. (T49779) Previously, you could only switch from the visual editor to the wikitext editor. Bi-directional switching will make possible a single edit tab. (T102398) This project will combine the "Edit" and "Edit source" tabs into a single "Edit" tab, similar to the system already used on the mobile website. The "Edit" tab will open whichever editing environment you used last time.
Let's work together
- Share your ideas and ask questions at mw:VisualEditor/Feedback. This feedback page uses Flow for discussions.
- Can you read and type in Korean or Japanese? Language engineer David Chan needs people who know which tools people use to type in some languages. If you speak Japanese or Korean, you can help him test support for these languages. Please see the instructions at mw:VisualEditor/IME Testing#What to test if you can help, and report it on Phabricator (Korean - Japanese) or on Wikipedia (Korean - Japanese).
- Local admins can set up the Citoid automatic reference feature for your wiki. If you need help, then please post a request in the Citoid project on Phabricator. Include links to the TemplateData for the most important citation templates on your wiki.
- The weekly task triage meetings are open to volunteers. Learn how to join the meetings and how to nominate bugs at mw:VisualEditor/Weekly triage meetings. You do not need to attend the meeting to nominate a bug for consideration, though. Instead, go to Phabricator and "associate" the main VisualEditor project with the bug.
If you can't read this in your favorite language, then please help us with translations! Subscribe to the Translators mailing list or contact us directly, so that we can notify you when the next issue is ready. Thank you!
— Whatamidoing (WMF) 04:16, 30 October 2015 (UTC)
Enrique Iglesias
Can you change the birth year for spanish singer Enrique Iglesias. he is born 1975 not 1976. His page is semi protected so i can't do it myself. Please! — Preceding unsigned comment added by Annah777 (talk • contribs) 03:35, 20 November 2015 (UTC)
Hi,
You appear to be eligible to vote in the current Arbitration Committee election. The Arbitration Committee is the panel of editors responsible for conducting the Wikipedia arbitration process. It has the authority to enact binding solutions for disputes between editors, primarily related to serious behavioural issues that the community has been unable to resolve. This includes the ability to impose site bans, topic bans, editing restrictions, and other measures needed to maintain our editing environment. The arbitration policy describes the Committee's roles and responsibilities in greater detail. If you wish to participate, you are welcome to review the candidates' statements and submit your choices on the voting page. For the Election committee, MediaWiki message delivery (talk) 16:53, 24 November 2015 (UTC)