User talk:Justin86789

Welcome!

Hello, Justin86789, and welcome to Wikipedia! Thank you for your contributions. I hope you like the place and decide to stay. Unfortunately, one or more of the pages you created, such as Boeing 747 100, may not conform to some of Wikipedia's guidelines, and may not be retained.

There's a page about creating articles you may want to read called Your first article. If you are stuck, and looking for help, please come to the Tea House, where experienced Wikipedians can answer any queries you have! Or, you can just type {{helpme}} on this page, followed by your question, and someone will show up shortly to answer your questions. Here are a few other good links for newcomers:

• Starting an article
• Your first article
• Biographies of living persons
• How to write a great article
• The five pillars of Wikipedia
• Help pages
• Tutorial

I hope you enjoy editing here and being a Wikipedian! Please sign your name on talk pages using four tildes (~~~~); this will automatically produce your name and the date. If you have any questions, check out Wikipedia:Questions or ask me on my talk page. Again, welcome! Fnlayson (talk) 13:54, 26 September 2013 (UTC)

Proposed deletion of Boeing 747 100

The article Boeing 747 100 has been proposed for deletion because of the following concern:

No content here and no need for splitting 747-100 content from Boeing 747.

While all constructive contributions to Wikipedia are appreciated, content or articles may be deleted for any of several reasons.

You may prevent the proposed deletion by removing the {{proposed deletion/dated}} notice, but please explain why in your edit summary or on the article's talk page.

Please consider improving the article to address the issues raised. Removing {{proposed deletion/dated}} will stop the proposed deletion process, but other deletion processes exist. In particular, the speedy deletion process can result in deletion without discussion, and articles for deletion allows discussion to reach consensus for deletion. Fnlayson (talk) 13:54, 26 September 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:25, 20 November 2013 (UTC)

November 2013

Hello, I'm Mark Arsten. I wanted to let you know that I undid one of your recent contributions, such as the one you made with this edit to User:Fnlayson, because it didn’t appear constructive to me. If you think I made a mistake, or if you have any questions, you can leave me a message on my talk page. Thanks. Mark Arsten (talk) 01:01, 21 November 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, change https://en.wikipedia.org/wiki/Special:Random to https://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:47, 19 December 2013 (UTC)

Speedy deletion nomination of File:757airchinaufostrike.png

A tag has been placed on File:757airchinaufostrike.png requesting that it be speedily deleted from Wikipedia. This has been done under section F9 of the criteria for speedy deletion, because the image appears to be a blatant copyright infringement. For legal reasons, we cannot accept copyrighted images or text borrowed from other web sites or printed material, and as a consequence, your addition will most likely be deleted. Wikipedia takes copyright violations very seriously and persistent violators will be blocked from editing.

If you think this page should not be deleted for this reason, you may contest the nomination by visiting the page and clicking the button labelled "Click here to contest this speedy deletion". This will give you the opportunity to explain why you believe the page should not be deleted. However, be aware that once a page is tagged for speedy deletion, it may be removed without delay. Please do not remove the speedy deletion tag from the page yourself, but do not hesitate to add information in line with Wikipedia's policies and guidelines. ~SuperHamster Talk Contribs 22:56, 22 December 2013 (UTC)

Proposed deletion of Reeve Aleutian Airways Flight 8

The article Reeve Aleutian Airways Flight 8 has been proposed for deletion because of the following concern:

Non-notable incident: no casualties, no hull loss.

While all constructive contributions to Wikipedia are appreciated, content or articles may be deleted for any of several reasons.

You may prevent the proposed deletion by removing the {{proposed deletion/dated}} notice, but please explain why in your edit summary or on the article's talk page.

Please consider improving the article to address the issues raised. Removing {{proposed deletion/dated}} will stop the proposed deletion process, but other deletion processes exist. In particular, the speedy deletion process can result in deletion without discussion, and articles for deletion allows discussion to reach consensus for deletion. TheLongTone (talk) 09:42, 25 December 2013 (UTC)

Speedy deletion nomination of Reeve Aleutian Airways Flight 8

If this is the first article that you have created, you may want to read the guide to writing your first article.

You may want to consider using the Article Wizard to help you create articles.

A tag has been placed on Reeve Aleutian Airways Flight 8 requesting that it be speedily deleted from Wikipedia. This has been done under section G12 of the criteria for speedy deletion, because the article or image appears to be a clear copyright infringement. This article or image appears to be a direct copy from {{{value1}}}. For legal reasons, we cannot accept copyrighted text or images borrowed from other web sites or printed material, and as a consequence, your addition will most likely be deleted. You may use external websites as a source of information, but not as a source of sentences. This part is crucial: say it in your own words. Wikipedia takes copyright violations very seriously and persistent violators will be blocked from editing.

If the external website or image belongs to you, and you want to allow Wikipedia to use the text or image — which means allowing other people to modify it — then you must verify that externally by one of the processes explained at Wikipedia:Donating copyrighted materials. If you are not the owner of the external website or image but have permission from that owner, see Wikipedia:Requesting copyright permission. You might want to look at Wikipedia's policies and guidelines for more details, or ask a question here.

If you think this page should not be deleted for this reason, you may contest the nomination by visiting the page and clicking the button labelled "Click here to contest this speedy deletion". This will give you the opportunity to explain why you believe the page should not be deleted. However, be aware that once a page is tagged for speedy deletion, it may be removed without delay. Please do not remove the speedy deletion tag from the page yourself, but do not hesitate to add information in line with Wikipedia's policies and guidelines. ...William 23:05, 26 December 2013 (UTC)

Speedy deletion nomination of Reeve Aleutian Airways Flight 8

If this is the first article that you have created, you may want to read the guide to writing your first article.

You may want to consider using the Article Wizard to help you create articles.

A tag has been placed on Reeve Aleutian Airways Flight 8 requesting that it be speedily deleted from Wikipedia. This has been done under section G12 of the criteria for speedy deletion, because the article or image appears to be a clear copyright infringement. This article or image appears to be a direct copy from http://contactapproach.blogspot.ca/2009/11/paper-for-flight-safety_10.html. For legal reasons, we cannot accept copyrighted text or images borrowed from other web sites or printed material, and as a consequence, your addition will most likely be deleted. You may use external websites as a source of information, but not as a source of sentences. This part is crucial: say it in your own words. Wikipedia takes copyright violations very seriously and persistent violators will be blocked from editing.

If the external website or image belongs to you, and you want to allow Wikipedia to use the text or image — which means allowing other people to modify it — then you must verify that externally by one of the processes explained at Wikipedia:Donating copyrighted materials. If you are not the owner of the external website or image but have permission from that owner, see Wikipedia:Requesting copyright permission. You might want to look at Wikipedia's policies and guidelines for more details, or ask a question here.

If you think this page should not be deleted for this reason, you may contest the nomination by visiting the page and clicking the button labelled "Click here to contest this speedy deletion". This will give you the opportunity to explain why you believe the page should not be deleted. However, be aware that once a page is tagged for speedy deletion, it may be removed without delay. Please do not remove the speedy deletion tag from the page yourself, but do not hesitate to add information in line with Wikipedia's policies and guidelines. ...William 23:07, 26 December 2013 (UTC)