Timeline for What should be done about content with poor spelling, grammar or formatting?
Current License: CC BY-SA 3.0
8 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
May 11, 2011 at 18:51 | comment | added | Stu Pegg | I think one of the strengths of editing is that OPs that later return to their question will see the edits and hopefully learn something from them (not even necessarily in terms of language). For example, I learned a lot from edits on Gaming.SE about getting to the point of a question (and the merits of double-checking before posting). | |
May 10, 2011 at 4:03 | vote | accept | Kit Menke | ||
May 10, 2011 at 2:56 | comment | added | Alex Angas Mod | Here's the policy for Stack Overflow. As far as I know it applies to the other SE sites as well. | |
May 9, 2011 at 20:39 | comment | added | tekiegreg | Multi-lingual issues are a sensitive one, I like this as an option here, maybe allowing non-English or poor English speakers to post in their native language then allowing the community to translate. Maybe building some sort of feature into Stackexchange to allow a person to translate and/or view the translation in a different language. Thoughts there? | |
May 9, 2011 at 20:21 | history | edited | Alex AngasMod | CC BY-SA 3.0 |
Formatting (ha ha)
|
May 9, 2011 at 20:21 | comment | added | Alex Angas Mod | I agree. We also have to remember that there are a number of users that don't have a good grasp of English. If someone regularly formats incorrectly or always writes "Hi" and their name then they need education, but spelling and grammar we can't do much about. | |
May 9, 2011 at 16:43 | comment | added | Kit Menke Mod | Yeah I think this is what I was getting at... as long as we can figure out what is being asked, then we should edit the question. Otherwise, comment asking for clarification or close. | |
May 9, 2011 at 16:34 | history | answered | tekiegreg | CC BY-SA 3.0 |