Skip to main content
added 16 characters in body
Source Link

When I am fortunate enough to have a paper get accepted for publication, I often dread the final round of proofreading before I submit the LaTeX source files. Often, I read the paper start to finish multiple times and make incremental/superficial changes, but always have a difficult time calling it properly "proofread". In addition, I find this approach (multiple full proofreads) seems less useful for checking technical aspects of a paper (e.g., mathematical derivations or involved pseuedo-code) which is arguably more important.

I am wondering what types of routines people have developed for this situation. I would prefer to be much more systematic, as my current approach is both inefficient (time-wise) and doesn't seem very effective. Specifically, what do you do in order to call the paper "proofread" and feel comfortable sending it off to never be edited again?

When I am fortunate enough to have a paper get accepted for publication, I often dread the final round of proofreading before I submit the LaTeX source files. Often, I read the paper multiple times and make incremental/superficial changes, but always have a difficult time calling it properly "proofread". In addition, I find this approach (multiple full proofreads) seems less useful for checking technical aspects of a paper (e.g., mathematical derivations or involved pseuedo-code) which is arguably more important.

I am wondering what types of routines people have developed for this situation. I would prefer to be much more systematic, as my current approach is both inefficient (time-wise) and doesn't seem very effective.

When I am fortunate enough to have a paper get accepted for publication, I often dread the final round of proofreading before I submit the LaTeX source files. Often, I read the paper start to finish multiple times and make incremental/superficial changes, but always have a difficult time calling it properly "proofread". In addition, I find this approach (multiple full proofreads) seems less useful for checking technical aspects of a paper (e.g., mathematical derivations or involved pseuedo-code) which is arguably more important.

I am wondering what types of routines people have developed for this situation. I would prefer to be much more systematic, as my current approach is both inefficient (time-wise) and doesn't seem very effective. Specifically, what do you do in order to call the paper "proofread" and feel comfortable sending it off to never be edited again?

Source Link

Routine for effectively proofreading accepted paper

When I am fortunate enough to have a paper get accepted for publication, I often dread the final round of proofreading before I submit the LaTeX source files. Often, I read the paper multiple times and make incremental/superficial changes, but always have a difficult time calling it properly "proofread". In addition, I find this approach (multiple full proofreads) seems less useful for checking technical aspects of a paper (e.g., mathematical derivations or involved pseuedo-code) which is arguably more important.

I am wondering what types of routines people have developed for this situation. I would prefer to be much more systematic, as my current approach is both inefficient (time-wise) and doesn't seem very effective.