User talk:Fresternoch

Fresternoch, you are invited to the Teahouse

Hi Fresternoch! Thanks for contributing to Wikipedia. Be our guest at the Teahouse! The Teahouse is a friendly space where new editors can ask questions about contributing to Wikipedia and get help from peers and experienced editors. I hope to see you there! Technical 13 (I'm a Teahouse host) Visit the Teahouse This message was delivered automatically by your robot friend, HostBot (talk) 16:08, 30 May 2014 (UTC)

June 2014

Hello, I'm BracketBot. I have automatically detected that your edit to Piano Sonata No. 28 (Beethoven) 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:

• his command. He used the lowest E (contra E) on the piano at the climax of the fugue （mm. 192-200) and near the end. More than 330 measures in length, the fourth movement is the longest and the

It's OK to remove this message. Also, to stop receiving these messages, follow these opt-out instructions. Thanks, BracketBot (talk) 18:08, 16 June 2014 (UTC)

Keyboard Sonata No. 49 (Haydn）

Shouldn't this be titled Keyboard Sonata No. 59 (Haydn）? Nthep (talk) 16:49, 29 June 2014 (UTC)

A belated welcome!

Sorry for the belated welcome, but the cookies are still warm!

Here's wishing you a belated welcome to Wikipedia, Fresternoch. I see that you've already been around a while and wanted to thank you for your contributions. Though you seem to have been successful in finding your way around, you may benefit from following some of the links below, which help editors get the most out of Wikipedia:

• Introduction
• The five pillars of Wikipedia
• How to edit a page
• Help pages
• How to write a great article
• Editor's index to Wikipedia

Also, when you post on talk pages you should sign your name using four tildes (~~~~); that should automatically produce your username and the date after your post.

I hope you enjoy editing here and being a Wikipedian! If you have any questions, feel free to leave me a message on my talk page, consult Wikipedia:Questions, or place {{helpme}} on your talk page and ask your question there.

Again, welcome! Vanjagenije (talk) 19:11, 29 June 2014 (UTC)

Études-Tableaux, Op. 33

This is an automated message from CorenSearchBot. I have performed a web search with the contents of Études-Tableaux, Op. 33, and it appears to include material copied directly from http://musescore.com/user/19710/scores/143619.

It is possible that the bot is confused and found similarity where none actually exists. If that is the case, you can remove the tag from the article. The article will be reviewed to determine if there are any copyright issues.

If substantial content is duplicated and it is not public domain or available under a compatible license, it will be deleted. For legal reasons, we cannot accept copyrighted text or images borrowed from other web sites or printed material. You may use such publications as a source of information, but not as a source of sentences. See our copyright policy for further details. (If you own the copyright to the previously published content and wish to donate it, see Wikipedia:Donating copyrighted materials for the procedure.) CorenSearchBot (talk) 17:16, 28 July 2014 (UTC)

Reference Errors on 28 July

Hello, I'm ReferenceBot. I have automatically detected that an edit performed by you may have introduced errors in referencing. It is as follows:

• On the Études-Tableaux, Op. 39 page, your edit caused a broken reference name (help). (Fix | Ask for help)

Please check this page and fix the errors highlighted. If you think this is a false positive, you can report it to my operator. Thanks, ReferenceBot (talk) 00:27, 29 July 2014 (UTC)

Disambiguation link notification for July 29

Hi. Thank you for your recent edits. Wikipedia appreciates your help. We noticed though that when you edited Études-Tableaux, Op. 33, you added a link pointing to the disambiguation page Ivanovka. 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 the DPL WikiProject.

It's OK to remove this message. Also, to stop receiving these messages, follow these opt-out instructions. Thanks, DPL bot (talk) 08:57, 29 July 2014 (UTC)

Disambiguation link notification for August 5

Hi. Thank you for your recent edits. Wikipedia appreciates your help. We noticed though that when you edited Nach Bach (Rochberg), you added a link pointing to the disambiguation page Fantasia. 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 the DPL WikiProject.

It's OK to remove this message. Also, to stop receiving these messages, follow these opt-out instructions. Thanks, DPL bot (talk) 09:36, 5 August 2014 (UTC)

Your recent edits

Hello and welcome to Wikipedia. When you add content to talk pages and Wikipedia pages that have open discussion (but never when editing articles), please be sure to sign your posts. There are two ways to do this. Either:

1. Add four tildes ( ~~~~ ) at the end of your comment; or
2. With the cursor positioned at the end of your comment, click on the signature button ( or ) located above the edit window.

This will automatically insert a signature with your username or IP address and the time you posted the comment. This information is necessary to allow other editors to easily see who wrote what and when.

Thank you. --SineBot (talk) 23:50, 6 August 2014 (UTC)

Exaggerated claims

Hi Fresternoch. I see you have removed the "Master Editor" template (which in effect claimed you have been on Wikipedia for over six years and made over 42,000 edits). You could have replaced it with a more modest service award that accurately reflects your time and edit level on Wikipedia, but this is up to you, of course. There is a more serious issue, however, in that you are still claiming to have rollback, reviewer, and autopatrolled status. The displayed banners for each of these has a "click to verify" link, and in all three cases these fail to verify you have these privileges, which are user access levels granted to editors who have a track record demonstrating their trustworthiness. By falsely displaying these templates, you undermine the credibility of other claims to authority which are more difficult to verify, such as that you have earned postgraduate degrees. I strongly suggest that you remove these demonstrably false claims, which you may have placed there without realizing they are not just personal declarations, but must be earned. Best wishes.—Jerome Kohl (talk) 22:20, 7 August 2014 (UTC)

Bold text and section headings

Please stop adding bold text attributes to article section headings. It does not affect the appearance of the text (which is bold automatically) and just results in a bot fixing it as a syntax error. Thanks. JohnInDC (talk) 06:21, 8 August 2014 (UTC)

Disambiguation link notification for August 12

Hi. Thank you for your recent edits. Wikipedia appreciates your help. We noticed though that when you edited Nach Bach, you added a link pointing to the disambiguation page Dynamics. 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 the DPL WikiProject.

It's OK to remove this message. Also, to stop receiving these messages, follow these opt-out instructions. Thanks, DPL bot (talk) 09:19, 12 August 2014 (UTC)

Beethoven sonata op 109

Hi Fresternoch. Thanks for your work on Piano Sonata No. 30 (Beethoven). You'll see that I've just made some edits which reverse several of yours, which I did with great regret and after much thought, so please let me explain.

First, a couple of errors:

• Movt 2 isn't the first prestissimo movement in a Beethoven sonata -- look at the last movement of his first sonata.
• Variation 3 isn't forte throughout -- see bars 8, 12 and 24.
• Variation 4 probably isn't the longest in duration. With repeats there are 32 bars played slightly slower than the theme's tempo, whereas variation 6 has 51 bars played at the theme's tempo. Variation 6 would normally take longer, though it may depend on the performer to some extent.
• Duration of 15-20 minutes for movement 3 is wildly out, so I suspect you've done some original research there. There's a wide range -- I've seen 8:30 and over 15 minutes, but never higher. Normal in top professional performances appears to be around 11:30 - 12 minutes.

In an encyclopedic article like this, we concentrate on facts. Subjective statements like saying that the first movement is "very clean and compressed", or "The character is gentle again, after the energetic outburst of Variation 3" aren't very helpful, and even if we want them, they should only be included when they are attributed to a highly respected source and properly cited. If Daniel Barenboim said it, we can say that he said it, but otherwise ...

Just one detail: in something like "mm. 188-203" the mm stands for measures (plural). For a single measure, we just write "m. 188". But measures is American English, and this article is written in British English, and we don't change from an article's established English version. I've restored "bars" and also reverted to using in-variation bar numbers rather than whole-movement bar numbers, because this is easier for readers using editions that don't print whole-movement bar numbers (like the Schenker edition).

Once again, sorry to undo so much of your contribution, and I hope you won't mind. If you want to take up any issues about it with me, I'll keep your talk page watch listed for a few days, or we can discuss it on the article talk page if you prefer.

Kind regards, --Stfg (talk) 15:59, 15 June 2015 (UTC)

Sorry, I don't have time for a full explanation now, pretty busy atm, can you please keep my talk page in the watchlist longer? I will try to get back here as early as I can.

Thanks for understanding, --Fresternoch (talk)

No problem. Will do. --Stfg (talk) 08:25, 19 June 2015 (UTC)

VisualEditor News #4—2015

Read this in another language • Local subscription list • Subscribe to the multilingual edition

Did you know?

You can add quotations marks before and after a title or phrase with a single click.

Select the relevant text. Find the correct quotations marks in the special character inserter tool (marked as Ω in the toolbar).

Click the button. VisualEditor will add the quotation marks on either side of the text you selected.

You can read and help translate the user guide, which has more information about how to use VisualEditor.

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)

VisualEditor News #5—2015

Read this in another language • Subscription list for this multilingual newsletter

Did you know?

You can use the visual editor on smartphones and tablets.

Click the pencil icon to open the editor for a page. Inside that, use the gear menu in the upper right corner to "Switch to visual editing".

The editing button will remember which editing environment you used last time, and give you the same one next time. The desktop site will be switching to a system similar to this one in the coming months.

You can read and help translate the user guide, which has more information about how to use the visual editor.

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 Cite 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 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)

ArbCom elections are now open!

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) 17:07, 24 November 2015 (UTC)