44
The StackExchange model is based round the idea that the sites are not forums, but that questions and answers should have some element of generality. As such, 'good' questions should be focussed on the matter in hand, ideally without many things that might make good forum posts. That's one reason that 'thanks' is discouraged and why community edits are ...
42
I think any improvement on an existing answer is valid. It would be far more helpful to have current information than to have outdated yet functional answers. Even if this means you replace 50 lines of code with a new \usepackage and a single command. The reason should be obvious: Answers here are meant to benefit the community, which is always changing.
...
33
I think that editing a question after you've received good answers to it is generally bad practice, especially if it would change the validity of the answers. If what you need could be done with a minimal change, it might be possible to add a comment to each answer with an extra question. This will notify the original answerers and let them update their ...
32
You're dealing with people here, and some people are just different. They may not like other's removing their signatures, their "Thank You's", correcting their CaPiTaLiZaTioNS, ...
Having been here for a while, I have grown accustomed to the communal attitude and nature - something that most likely guided you in your edit. That's honourable, and that's that....
31
My humble attempt. :)
First of all, I'd like to say that I really admire your work in the main SO site. I learned a lot from your answers. It's an honour to have a SO fellow user here. Make yourself at home, I really hope you enjoy this community.
Please, don't take my next lines personal. It's just some humble thoughts about the way I see this specific ...
31
I'd like to sound a note of dissonance.
I understand [Bb]arbara's reasoning. But I think that it is flawed for two reasons:
It is not clear from a post itself that there is a potential for two voices. A post with no capitalisation simply looks like a post with no capitalisation. One has to look further, and know what to look for, to understand the ...
31
I am one of those users who consistently reject removing thanks edits. The Stackoverflow people started an utopia to make the questions anonymized and general as much as possible. Thanking is considered to be somehow useless in terms of know-how. But time showed that every SE site has a different flavor and similarly we have developed a different path in ...
30
It's not really an answer, but my thoughts are too long for a comment. :)
First of all, I'd like to thank you for all the effort you've put into moderncv and the time spent in helping people here. :)
I really share your worries on some MWE lacking the minimal component. Indeed we have quite a bunch of such examples in our community.
I once stumbled upon ...
28
Well we've had this discussion on other grounds too, as you well know, but I think that since the language of the site is English, editing other-language typographical practices doesn't seem to me to be so out of line, especially if the question is already active. While it's true that it could be thought of as too minor an edit, and could be rejected on ...
27
A clear approach doesn't mean that everybody does it the same way, such things can happen.
It also depends on who reviewed your edit: possibly the questioner rejects it, because he posted the "thanks" and wants to keep it. An experienced reviewer may accept it, because a "thanks" below the question doesn't add know-how value to the site in the long sight.
...
25
If you see a question which can be improved, go ahead and edit it. Community editing makes our site outstanding and is a reason for its quality.
Of course we all should edit sensibly. And we should not edit too much in a row to not flood the front page.
Btw. I don't see that it's urgent to remove a friendly "Thanks" in a new question of a new user to avoid ...
24
I would like us to keep in mind, that we would like to respect the reader.
Once written, hundreds or thousands of times read. It's good for the site and for the users and visitors, that the posts are as readable as possible. This includes writing in English as it's the language of this international site, capitalization as it's common practice, and proper ...
23
I don't see why the source of the edit should really be of concern if you have reason enough to think that the edit is helpful. For me, the issue with major edits is mainly if they significantly change the question or answer, (even if good) in which case I'm inclined to be conservative on accepting them. In that case maybe the provenance of the edit might ...
23
Engines & Formats
TeX
pdfTeX (source)
XeTeX (source)
XeLaTeX (source)
LuaTeX (source)
LaTeX (source)
AMS-LaTeX (not usually a separate format) (source)
ConTeXt (source)
AMS-TeX (source)
BibTeX (source)
When one of these names is used as an instruction on a command line, it is almost always lowercase and in code markup, e.g., tex foo.tex, latex bar....
23
To round up the comment thread.
You seemed to be surprised that the edit should be reverted in is entirety rather than being fixed/improved. In fact reverting is the natural action to take in this circumstance.
Someone who decides to edit a question (or answer) can decide to do it at a time convenient for them, and to spend as much or as little time as ...
22
The quality of the answer is important. So it's better to make it clearly understandable, improve your original answer, without edited or 2nd edt remarks. The history can still be read.
To let the reader understand comments, you could add the necessary information in the comment area, following that comment. It belongs there. Perhaps directly address the ...
21
A list of (probably) all posts that show this problem is returned by the following query
https://data.stackexchange.com/tex/query/695628/posts-probably-affected-by
Which returns 11554 postings, this shows all the pre-2014 postings on the site whose initial unedited markdown has a single backslash followed by four spaces, or spaces and a tab. This is a (...
21
On behalf of the team, thank you very much to everyone who participated in fixing the backslash problem. It really was excellent, amazing work. Editing is always underappreciated, and this must have been all the duller to do by hand because it was looking at the same bit of code formatting over and over rather than cleaning up prose.
I apologize for our ...
20
I think I remember a comment of B/barbara somehwere, in which she stated she only uses standard capitalization whenever she's writing on behalf of the AMS. I'm not sure whether or not this is a reason to deviate from this site's style so decisively, but I'd recommend she add a note to her profile about her doing so. Also, it'd be good to a notice (or a link ...
19
I've done this before. My guidelines are:
Keep the original possible duplicate. That was, after all, the majority view. If I disagree with this then I'd want to discuss it first (here or in chat).
Make the plurality clear: "Possible duplicate s" and put them in a list.
Other than that, this is a good idea so long as it really is a possible duplicate and ...
19
I would say that it's up to the owner of the post to decide whether they feel editing the code formatting is okay or not, not a third party. When someone's answer is edited, they are notified and can make the call themselves. Maybe they think of the new code formatting as an improvement and are happy about it; if not they can undo the changes themselves.
19
I completely agree with David's comments. The edit fixed some grammar issues, but also changed the meaning of the question. The problem was in the usage of "all the time that", an almost word by word translation from Italian "tutte le volte che" ("each time" would have been a proper translation). Unfortunately, "all the time" has a different meaning in ...
17
The first thing to bear in mind here is that while there are places where there are StackExchange rules/polices, on editorial matters 'guidelines' is a much more accurate term. (Rules are clearly appropriate for legal matters, for example.) Each StackExchange network site has its own conventions, and those are to some extent 'organic'. They also need to work ...
16
In this one case, yes, Barbara Beeton uses an exclusive no-caps style to distinguish her personal posts from anything official representing the American Mathematical Society. See this question for some more discussion.
Respecting poster's style.
16
Editor Sign Up List
Texmaker:
doncherry (Win7),
hpesoj626 (linux).
Updated 2013-02-28
TeXworks:
Joseph Wright,
tohecz (linux).
Updated 2013-03-09
TeXnicCenter:
Werner,
percusse.
Updated 2013-03-15
TeXStudio:
hpesoj626 (linux).
Updated 2013-03-09
TeXShop:
Alan Munn
Vim:
Psirus.
Updated 2013-03-09
Emacs:
Charles Stewart (OSX, linux),
Tyler Smith.
Updated 2013-...
16
I prefer that the edit isn't just "removed thanks"; however, the first thing I look at when I review an edit is the time when the message was posted. If it's less than a couple of hours I usually don't bother and accept (or improve) the edit, because the edit follows the guidelines (right or wrong, they exist). If the message is older, I accept the edit only ...
16
I think this is a really bad idea. We strive to be an inclusive site, and enforcing such capitalizations is a great way to foster exactly the opposite view: "there are those of us who know the 'right' way and you are in the group that doesn't know the 'right' way."
As for editing, editing a post just for such 'errors' is also inappropriate; if there are ...
16
There is no formal way of preventing this behaviour as editing a post is assumed to improve it, and the subsequent bump is a by-product.
Since the site is community driven, improper use of this technique can be discussed in the chat room - to seek confirmation (just to make sure you're not seeing things that aren't there) and perhaps brought to moderator ...
15
Because.
15
Community editing is part of the way the StackExchange network. Lower reputation users can suggest edits, while people with lots of reputation (over 3k I think) can simply edit directly. So you should feel free to suggest improvements.
The only thing I would ask is that no one overdoes it. Ideally, the front page is mainly made up of new questions. So ...
Only top voted, non community-wiki answers of a minimum length are eligible
