Wikipedia talk:Basic copyediting
From Wikipedia, the free encyclopedia
| This project page does not require a rating on Wikipedia's content assessment scale. It is of interest to the following WikiProjects: | |||||||||||
| |||||||||||
Pages needing copy-editing
Where is the relevant list - which is what I would expect on coming to this page.
- It is right here: Articles needing copy edit.--Song 21:32, 8 August 2007 (UTC)
Interessante Day1988 (talk) 12:25, 30 October 2022 (UTC)
Broken link?
The link 'Wikipedia:Manual of Style#"See also" and "Related topics" sections' appears to be broken. Is it meant to be 'Help:Section#"See_also"_line_or_section'? JDX 06:09, 16 June 2006 (UTC)
Copy-editing requests
I'm unsure about this, so I'm going to ask here: is there by chance a page where one could request another to copy-edit an article? It's difficult for authors to copy-edit their own material because it's their own writing. For example, I find it hard to edit my work since my eyes seem to avoid what I've typed and I assume it's correct. Is there a page for requesting third parties to copy-edit articles? Never Mystic (tc) 16:49, 9 October 2006 (UTC)
- Yes. Place copyedit, within two curly brackets ({{ }}) at the top of the page. Conor 04:12, 9 November 2006 (UTC)
Scope of copy edits
I'm having difficulty interpreting these guidelines in the case of substantial copyediting changes to an article. It would not be surprising to find an article with several minor spelling / grammar / capitalization / hyphenation issues, and perhaps a couple of easily revised sentence fragments. Is it best to apply all these changes in one go? Or should they be split up, into dozens of individually inconsequential ones? Applied section-by-section for the whole article? Applied like-for-like, i.e. all spelling corrections in one go, hyphenation corrections in one go, etc.? How can one write effective edit summaries when there is broad or extensive copyediting work?
How does reverting work in such a case? If edits are split up, even if only by section, then it becomes difficult to revert an edit early in the history while retaining the later ones. However the other case, the "one big edit," seems just as problematical. Advice to this newcomer would be appreciated! --Iamgrim 22:32, 20 April 2007 (UTC)
- Just make all the changes in one go. This makes the page history easier to read. For the edit summary you can just write something like 'extensive copyediting' or 'various spelling and grammar corrections'. If any reverts are needed they can be achieved by editing the article, if necessary using copy and paste from an earlier version of the article. S Sepp 21:27, 24 April 2007 (UTC)
- I usually edit one section at a time to prevent edit conflicts. But if it's a backwater article, then making it all in one go shouldn't be an issue. Writing "copy-edit" is usually good enough. — Deckiller 21:05, 29 June 2007 (UTC)
- This strikes me as an interesting point. I've noticed that editors are split on this issue; some editors regularly make dozens of small edits one after another with good individual edit summaries, while other editors (like myself) are prone to rewrite an entire 150k article in one go and call it "reworded for clarity". I actually think the former might be preferable, since it gives other editors individual "bites" to digest. However, it can also make the edit history more confusing. Personally, I recommend using small bite-sized edits whenever there's any active or "heated" editing going on, especially in an edit-war zone. But my point here is actually that I think this issue might deserve further discussion, and some guidelines might be in order in the article. I know I had essentially the same question as Iamgrim, back when I started editing. I imagine we're not the only two who have, huh? Eaglizard 23:22, 18 September 2007 (UTC)
- I find that one advantage of doing it in sections or bits is that if you screw up while editing and have to cancel, you don't lose all of the good edits you've made that haven't been saved yet. Sort of like saving a word document frequently. Another is that after editing one section, upon reviewing it you often see other changes to be made. Gets very tiring to keep re-reading if you're doing the whole article at once. Another is that if you have some small notations that explain to others why the change was made, there is less chance of someone reverting the edit because they don't understand the rule of grammar (or whatever) involved. I've sometimes gone overboard on this, which is a mistake, but something like "rm redundancy", "clarity", "punc" "misplaced modifier", etc. can help others to understand why the changes were made (especially the writer whose words are being edited). But that is all just this editor's POV. Regards, Unimaginative Username 05:33, 14 November 2007 (UTC)
External links vs. references
Under Common copy-edits is this bullet point (3rd from the bottom):
- External links generally belong at the end of an article under a heading titled "External links". References are an exception and should match the link in the reference section; these are then handled automatically.
I think the second sentence is very unclear (especially to the newbie), but I'm not sure how to improve it. Probably a couple more sentences will have to be added. I hope someone will help. Thanks! Scrawlspacer 21:02, 29 June 2007 (UTC)
Copy-editing versus NPOV correction
Under "Etiquette", changed the wording to clarify that c/e does not include correcting POV issues, which should be corrected before requesting c/e. Discussion of this issue was at the project "Criteria" page. Unimaginative Username 04:36, 14 November 2007 (UTC)
Disambig?
Don't we want to add also disambiguation of links, with the help of software like Wikipedia Cleaner? Randomblue (talk) 20:54, 13 January 2008 (UTC)
"Article is being copy-edited" tag?
WP:MOS "See also"
This article has just been added to the See also section of WP:MoS, so it could do with a little polish. There was a hidden comment in the first section asking if it was bossy ... it was, a bit, and also longer than it needed to be. I moved it to the lead and shortened it up; is there anything else that needs saying there? - Dan Dank55 (talk) 04:04, 3 April 2008 (UTC)
Avoiding contractions
Is this really consensus? My feeling, based on what many editors seem to do, is no. Overuse of contractions can seem excessively conversational, but I don't think there's any blanket prohibition on using them in articles. Even in academic writing, a prohibition on contractions is in many areas nowadays seen as somewhat old-fashioned and no longer followed. --Delirium (talk) 00:59, 10 April 2008 (UTC)
- AP Style Manual says "Contractions reflect informal speech and writing." TCMOS is silent. You're right that we're nearing a tipping point, because so much "persuasive" speech these days is written in blogs and in the style of blogs. Still, it's important to the project as a whole to have a solid core of articles that sound just as formal as the other online encyclopedias, it helps give us a certain dignity. There's no need for every article to be written in that style, though. As a compromise, we say: if you want to write a featured article, it has to follow WP:MoS, and it's also the "safe" thing to do to follow WP:MoS, because we've put a lot of effort into following the lead of large numbers of professional copywriters. But styles vary; in fact, we've just started conducting a large study of writing style of articles as they first enter WP:GAN, at Good article usage. - Dan Dank55 (talk) 03:08, 10 April 2008 (UTC)
Provide some links
In the section on spelling, it's mentioned that if in doubt, one should "look it up". Would it not be useful to link to Wikipedia:Manual of Style (spelling) or the Language Reference Desk? Zain Ebrahim (talk) 14:03, 29 June 2008 (UTC)
- That's a good idea. For North American articles (particularly US), the best link is http://www.merriam-webster.com/dictionary; AP Stylebook (which most US journalists follow) recommends Websters, with AMHER coming in a close second. But Wikipedia:Manual of Style (spelling) is very helpful, and the REFDESK people are phenomenally good. - Dan Dank55 (talk)(mistakes) 14:29, 29 June 2008 (UTC)
What are long and short form see also links?
Peregrine Fisher (talk) (contribs) 18:07, 12 March 2009 (UTC)
- I'm guessing that "long-form" means a whole section of links under a "See also" subheading, while "short-form" means an italicised See also: line at the top of a section (but if this is true then there's confusion in the sentence about what "section" means; it's used in two places to mean two different things). I don't think it's reasonable to expect readers to understand this sentence as it stands, so I added a "clarification needed" tag. 86.134.43.118 (talk) 14:09, 10 April 2009 (UTC).
- I've clarified as best as I can, though it still reads a little clunky. Rather than start with a confusing example, I've moved this dot point to the end. Adrian J. Hunter(talk•contribs) 14:28, 15 July 2009 (UTC)
Reactions to this page
1. Is this really a good page to have? Should we delete it?
2. It seems like it is missing a lot of the "how to copyedit" info, like how to run through the article, how big of a chunks to do at at time, how to take the article in and out of the queue. Many of these questions are raised on the talk page, so my reaction seems normal. The section at the start seems very basic and in some ways too granular for anyone getting to this page. Also, it seems better said in the Manual of Style, Tony's page, Strunk and White, etc. I'm also not clear if the list is (reasonably) comprehensive, or just a splat. At a minimum, the list ought to be moved to the bottom of the article, after the real thoughts on "how to copyedit" (which need to be developed).
3. The list is a "laundry list", not categorized, not sorted or prioritized. Also, would be helpful to separate basic issues of English language usage, from Wiki conventions (like the article naming capitalization). Of course, really Manual of Style probably does that better.
4. 2 years later and I still had the same reaction to the comment on links in references. Huh?
5. The edit summary stuff was decent and at least really tied into "how to copyedit".
6. The comment to the effect of "if in doubt, don't correct" may be good advice, but certainly NOT for the reason that "someone will definitely fix it otherwise". Would that it were so!
TCO (talk) 02:17, 29 November 2010 (UTC)
- I often add commas, citing this page's comma rule (search for "Vilnius"). That rule can also be found elsewhere, but not with any Wikipedia authority. I seldom if ever refer to the rest of the page. Although I make many of the other copyedits listed, they are also found in the Manual of Style. Art LaPella (talk) 04:51, 29 November 2010 (UTC)
I think that comma rule is just normal grammar. I'm not some magazine editor, just an engineer, but after reading your comment, I walked across the room and grabbed my 12th grade grammar book (Hodge's Harbrace College Handbook) from 20+ years ago. Rule 12.d talked about the use of commas for appositives and subsection (2) talked about geographic commas and gave the city example.
I bet there are about 10 wrong commas within this post, so don't flame me, but, really, I don't see what is so special to make the Vilnius rule need "wiki weight". It's standard usage.
TCO (talk) 06:09, 29 November 2010 (UTC)
- I probably wouldn't add the commas after "Lithuania" and after "1947" otherwise; they get opposition because they look wrong, although punctuation "experts" all seem to like them. Art LaPella (talk) 21:46, 29 November 2010 (UTC)
- My high school education taught me to put a comma before "Lithuania" and before "1947", so perhaps that's what you meant by "geographic commas". I never encountered a "before and after" rule before Wikipedia. Art LaPella (talk) 22:04, 29 November 2010 (UTC)
- If 1947 and Lithuania fall at the end of a clause or sentence, there will be punctuation anyway. Since this is natural for so long and heavy a sentence element, it doesn't come up very often. Septentrionalis PMAnderson 03:07, 22 February 2011 (UTC)

