# Reviewing Suggested Edits

As part of the mod tools, there is a tool to review and approve suggested edits. The "review suggested edits" shows something like below which is not of much help to review and approve the edit.

It makes more sense, especially on math.se, to show the final form of the post, including the typeset i.e the form it would appear on screen once it has been posted/approved.

This is of more relevance to math.se since most of suggested edits have got to do with some typesetting changes. It is hard to figure out what exactly the changes are and how they affect the post without looking at how they appear on the screen.

-
Two work-arounds: (a) click on the "improve" button, which will bring up a normal editing screen and you can read the final forms. Downside is that then the edit will appear to be from you and not the person who proposed the edit. (b) If you are sure that the edits are only about math display and not about content, then click approve, navigate to the question, and read it over to see if you "really" approve. –  Willie Wong Aug 18 '11 at 20:04
@Willie: My impression was that if you make no changes in the "improve" screen, it actually does not let you implement the edit from there (so there is no danger of the edit being incorrectly attributed); hence in my answer below I suggested pressing the back button and using the "approve" button. –  Zev Chonoles Aug 18 '11 at 20:05
and (c) undergo intensive training with Knuth or Lamport in the secluded mountains of California for 3 months thereby acquiring the secret skill of parsing (La)TeX in your head. =p –  Willie Wong Aug 18 '11 at 20:06
@Willie: Another way to master that is to write the macros and their output on the bottom of beer mugs. This is a great way to train, since you engrave the compilation into your subconscious! –  Asaf Karagila Aug 18 '11 at 20:13
I don't think this can be changed at the math.se level; but perhaps you can ask in meta.stackoverflow for a change, perhaps a link to a "Preview changes" like Wikipedia has. –  Arturo Magidin Aug 18 '11 at 20:21
@Arturo: I posted on meta.stackoverflow few minutes back meta.stackexchange.com/questions/103018/… –  user17762 Aug 18 '11 at 20:23
@Asaf Ah, so that explains why the swag mug design is taking so long... –  Bill Dubuque Aug 18 '11 at 22:48
@Sivaram: Well, it got closed as a duplicate, even though it was by no means a duplicate of the indicated post: you weren't complaining that there was "too much noise", you were asking for more stuff to be put there, in a way. –  Arturo Magidin Aug 19 '11 at 3:03
This is very interesting. There is an option, when reviewing suggested edits, to show the "actual" posts rather than the markdown differences. However, because of how the diff engine identifies and renders changes, it causes breaks in the MathJax that results in actual changes to the TeX not being displayed as their final result. Compare markdown diff with final diff, it's quite odd. I'll see if anyone knows if this can be altered in any fashion. –  Grace Note Aug 19 '11 at 15:40

I had also been quite annoyed by this aspect of reviewing proposed edits. However, one solution is to click the "improve" button, which will show you exactly what you want (what the end result of the proposed edit would look like), and then if it is satisfactory, just hit the "back" button and approve it.

-
@Willie: Yes. I have been doing what you and Zev have suggested. But am finding it increasing annoying. –  user17762 Aug 18 '11 at 20:06
@Siv: I agree that it would be a good feature to have. Hence my comments are mere workarounds, not real answers. –  Willie Wong Aug 18 '11 at 20:08
+1: This is what I always do, and I am used to it now (I used to find it annoying at some point in the past). –  Aryabhata Aug 18 '11 at 20:42
I do that, but I'm slow and I often find that somebody's already approved it once I hit Back... :D –  J. M. is back. Aug 19 '11 at 0:47

Well, not an entire solution, but simply click the small icon on the left to show the post in pure markup without rendering:

-
I just tried that. It doesn't actually help since the changed $\LaTeX$ is not compiled. –  Asaf Karagila Sep 2 '11 at 6:48
yes, it is at best a minor workaround for now –  Jeff Atwood Sep 2 '11 at 6:51