Misplaced Pages

Revision as of 00:06, 1 December 2012

To remain listed at Misplaced Pages:Requests for comment/User conduct, at least two people need to show that they tried to resolve a dispute with this user and have failed. This must involve the same dispute with a single user, not different disputes or multiple users. The persons complaining must provide evidence of their efforts, and each of them must certify it by signing this page with ~~~~. If this does not happen within 48 hours of the creation of this dispute page (which was: 03:22, 30 November 2012 (UTC)), the page will be deleted. The current date and time is: 18:08, 25 December 2024 (UTC).

• Apteva (talk · contribs · logs)

Users should not edit other people's summaries or views, except to endorse them. All signed comments other than your own view or an endorsement should be directed to this page's discussion page.

See also Misplaced Pages:Requests for adminship/Apteva 2.

Statement of the dispute

Apteva has been on a persistent anti-en-dash (and anti-WP:Manual of Style) campaign since August 2012. Although he has failed to gain consensus at every requested move, move review, and other venue where he has been pushing his theory that the MOS is in error about en dashes, he keeps saying that the edit warring will continue. Several of us have told him that we interpret that as a threat, but he persists. This has been a disruptive 3 months, and shows no sign of letting up.

Desired outcome

We desire that Apteva stop the anti-en-dash and anti-MOS behaviors; no new RMs to remove en dashes from titles; no new move reviews to review RMs that close against his theories about en dashes; no new proposals at the MOS to challenge or change the consensus about en dashes; limited, as opposed to dominating, comments in RMs that others initiate about dashes, about the applicability of the MOS in styling in titles, and related topics. Generally, Apteva should learn to get the point, respect consensus, and work collaboratively instead of "my way or the highway".

Description

Since September 24, Apteva has been pushing theories that proper names never have en dashes, e.g. that airport names never have en dashes, that comet names never have en dashes, etc., and that MOS:DASH is in error encouraging usage of the en dash, e.g. in its examples of Comet Hale–Bopp and Mexican–American War, and further that the MOS has no role in styling article titles.

That is comet Hale-Bopp, and Mexican-American War. Spell it correctly. Apteva (talk) 21:45, 30 November 2012 (UTC)

Evidence of disputed behavior

He started by dominating the RFC discussion at Misplaced Pages talk:WikiProject Airports (contributors summary) and at the WT:MOS (contributors summary), especially in his Three corrections section, in each case posting more times than the next two or three contributors combined. This was exasperating. He finally swore off posting at WT:MOS for a while, but this did not last, and he continues to post attempts at rebutting those who disagree with him.

At many points along the way, he would collapse (hide) sections that expressed the views of others, especially when they tried to tell him he was being disruptive. Here and here are examples (in the latter one, he recommended that I file an RFC/U about him, which I'm finally getting to). He changed comments of others, like my complaint about him here. It is notable that another tendentious editor was recently blocked for such "censorship by {{collapse}}" behavior during a similarly singleminded style campaign (against diacritics), at WT:Biographies of living persons#diacriticsagain.

Dicklyon had extensive discussions at Apteva's talk page version of 27 Oct. about Apteva's behavior and theories. Apteva had asserted incivility and toxic and such about some discussions at MOS, but never explained what he meant, which seemed to be that people were not letting him have his way. In the middle of October, he filed complaints at WP:AE about Dicklyon and Neotarf there, and then withdrew them when they got no traction. He copied one of my notices about his AE complaint to AN/I, filing a complaint against himself, essentially, and the followed it up with a complaint about JHunterJ that ended up turning around and biting him for his own hackish wiki-lawyering. Not all of this was about en dashes, but it was all bound up in his anti-MOS campaign.

On 14 November he made several controversial moves to remove en dashes from article titles; these were in airport names, some of them articles Dicklyon had previously moved to have en dashes in this, per MOS guidance, and where Apteva knew he had no support from other editors: , , , and more.

He has started and lost numerous Requested moves discussions to remove en dashes from titles; after losing, he took them to move review to try to get the closes overturned. See in particular both of the October 2012 move reviews and 4 of the November move reviews.

He has pretty much exhausted all possible forum-shopping, and has found essentially zero support among other editors for his idiosyncratic theories (with the exception of Enric Naval on Comet Hale–Bopp for the theory that the IAU should set our style). Instead of accepting the outcome, he remains defiant about the MOS being in error; see this section.

After losing the RMs and MRVs, he started a "my way or the highway" section at WT:MOS#Ending the endash/hyphen warring, and in that section has continued to assert that the MOS is in error and that edit warring over en dashes in titles will continue until it is "fixed". Several editors have told him that comes across as a threat, yet he re-asserts it here.

Applicable policies and guidelines

{List the policies and guidelines that apply to the disputed conduct}

1. WP:CONSENSUS
2. WP:FORUMSHOP
3. WP:PARENT
4. WP:TE
5. WP:DE
6. WP:NOT#SOAPBOX
7. WP:NOT#BATTLEGROUND

Evidence of trying and failing to resolve the dispute

(Provide diffs of the comments. As with anywhere else on this RfC/U, links to entire articles aren't helpful unless the editor created the entire article. Edit histories also aren't helpful as they change as new edits are performed.)

Attempts by certifier Dicklyon

1. Started discussion on Apteva's talk page
2. Started another discussion on Apteva's talk page
3. Started another discussion on Apteva's talk page

Attempts by certifier SMcCandlish

1. Raised behavior issues with Apteva's WT:MOS re-re-re-proposal against en dashes
2. Responding to Apteva's post on my talk page about his behavior (discussion since refactored to User talk:Apteva#MOS)
3. Raised behaviorial issues with Apteva again at WT:MOS in response to his allegations of being "personally attacked" whenever someone disagrees with him

Other attempts

1. I have tried here to help Apteva see that continuing this particular campaign about dashes in proper names has reached the level of disruption. There is overwhelming consensus for the status quo in each of the move requests and various forums, talk pages, etc that this editor has used to make the case against the current style guide's advice on this matter, itself the result of extensive discussion and overwhelming consensus a little over a year ago. The editor's response to me was a restatement of the case and an absolutely mind-blowing claim that There is absolutely no consensus to use an endash. This is one of the clearest consensuses that I have seen in my time working on this project. If this editor can not see that, I think it is long past time that this editor refrained from dealing with style issues, both on the manual of style and on style-related move requests. ErikHaugen (talk | contribs) 21:04, 30 November 2012 (UTC)

   Sorry but this is absolutely absurd. Hyphens are used exclusively in airport names and comet names, and by a 50:1 margin in bridges and wars, such as in Mexican-American War. How can anyone call that an overwhelming consensus to use an endash? The overwhelming consensus is the opposite - to use a hyphen, and the MOS needs to be corrected. Apteva (talk) 21:42, 30 November 2012 (UTC)

Users certifying the basis for this dispute

{Users who tried and failed to resolve the dispute}

1. User:Dicklyon
2. User:SMcCandlish

Other users who endorse this summary

1. JHunterJ (talk) 12:20, 30 November 2012 (UTC)
2. Tony (talk) 13:10, 30 November 2012 (UTC)
3. Phil Bridger (talk) 17:05, 30 November 2012 (UTC)
4. ErikHaugen (talk | contribs) 23:46, 30 November 2012 (UTC)

Response

This section is reserved for the use of the user whose conduct is disputed. Users writing other sections ("Statement of the dispute" and "Outside Views") should not edit the "Response" section, and the person writing this section should not write a view below. Anyone is welcome to endorse this or any other view, but no one except the editor(s) named in the dispute may change the summary here.

This is a pathetic attempt at tar and feathering that serves no purpose on Misplaced Pages. I see errors, and I fix them, plain and simple.

Users who endorse this summary:

Views

This section is for statements or opinions written by users not directly involved with this dispute, but who would like to add a view of the dispute. Users should not edit other people's summaries or views, except to endorse them. All signed comments other than your own view or an endorsement should be directed to this page's discussion page. Users editing other sections ("Statement of the dispute" or "Response") should not normally edit this section, except to endorse another person's view.

Outside view by JHunterJ

Note also the previous AN/I discussion which approached a topic ban for MOS and/or RMs for Apteva, which Apteva then voluntarily took on as a 30-day topic ban. The thirty days ended and Apteva's disruptive editing immediately resumed. Misplaced Pages:Administrators' noticeboard/IncidentArchive773#Apteva.

Users who endorse this summary:

1. JHunterJ (talk) 22:46, 30 November 2012 (UTC)

Outside view by Kurtis

Coming here via Apteva's talk page after giving him some advice about his recently closed RfA, I was initially disheartened to see that an RfC had been filed against him — at the time, I was under the preconceived notion that this step was premature. Then I actually read through the details provided, and now I'm convinced that there is a serious and longstanding problem here.

Speaking only for myself, I don't put that much energy into following the Manuel of Style right down to the letter every time I edit an article. That's not to say it should just be ignored, but that it's unproductive to spend a copius amount of time arguing over style conventions rather than focusing on the really important things (i.e. factual accuracy, citing reliable sources, the scope of the article, etc). Minor stylistic issues should be resolved in short order by being aware of the academically accepted standards. With hyphens and dashes, it is as simple as knowing the conventional usage for each one.

I'll just focus on the standards that apply in this case. En dashes are almost always used for separating compounds which are not singular entities in themselves, such as the Roman–Persian Wars, the Paris–Montpellier route, and various other examples listed under the second category of MOS:ENDASH. There are some exceptions to this: specifically, attributive compound names which exist as a single entity are also separated using an en dash, not a hyphen; the Manuel of Style even lists Comet Hale–Bopp as an example of this.

Apteva is quite firm in his conviction that hyphens should be used instead of en dashes in the aforementioned circumstances. Not only does the Manuel of Style contradict his view, but so does every other source I could find. I'm not sure if he realizes that his campaign against the use of en dashes comes across as willful ignorance to everyone else observing his comments and behaviours, but there is no other term I could use to describe it.

As I see it, he now has two choices:

1. Accept that his views are not widely accepted by the community, that they do not reflect standard English conventions involving to the usage of dashes and hyphens, and that further pursuance of this matter is a complete waste of time and energy for all involved. In other words, he can just drop it.
2. He will wind up being sanctioned, and the limitations applied to him will continue to escalate so long as he continues his pattern of tendentious editing.

Users who endorse this summary:

1. Kurtis (talk) 23:20, 30 November 2012 (UTC)

• The problem is that I would guess that easily 90% of editors neither know nor care to know the difference between a hyphen and an endash. I happen to be one of those who are fully aware of the difference and the correct use of each. There is no style guide in the real world, or grammar guide, that says that Mexican-American War is spelled with an endash, because it simply is not spelled with one 98% of the time - in books that could just as easily used whatever they chose, endash or hyphen, whichever they thought was more correct. Some style guides occasionally give bad advice. Ours is one that is doing that now. The examples of "Delhi–Sidney flight" and "North Carolina–Virginia border" are correct, but if either should become a proper noun, such as "Mexican-American War", or "Roman-Persian Wars", the spelling would change to a hyphen. The hyphen is conveniently located on all keyboards and should be encouraged as a valid option, instead of making everyone use an endash, even when an endash is correct, and using an endash when a hyphen is required, such as in the name of an airport, such as Seattle-Tacoma International Airport, or in a comet, such as Hale-Bopp, is patently absurd. Apteva (talk) 00:06, 1 December 2012 (UTC)

Outside view by ExampleUsername

{Add your summary here. You must use the endorsement section below to sign it. Anyone is welcome to endorse this or any other view, but do not change other people's views.}

Users who endorse this summary:

Reminder to use the talk page for discussion

All signed comments and talk not related to an endorsement should be directed to this page's discussion page. Discussion should not be added below. Discussion should be posted on the talk page. Threaded replies to another user's vote, endorsement, evidence, response, or comment should be posted to the talk page.