可以对 PDF 文档进行注释。我相信大多数 PDF 阅读器都支持这种开箱即用的方式。例如，我确信 Mac OS X 上的预览功能确实如此。
当您返回带有注释的 PDF 时，您可以返回并相应地编辑 LaTeX 源。我认为与 Word 相比，您失去的是轻松突出显示多个文档修订之间的更改的能力。如果您只与一名审稿人进行一轮评审，这并不是什么大问题，但如果这是一个需要多轮反馈和修改的大型编辑项目，那么规模就不会那么大了。
The problem with sending someone LaTeX source is that unless they're a LaTeX user themselves they are unlikely to have the necessary software installed. I would recommend sending a PDF, which anyone can typically read on any platform.
It is possible to make annotations to PDF documents. I believe most PDF readers support this out of the box. I'm certain, for example, that Preview on Mac OS X does.
When you get back the PDF with annotations, you can go back and edit the LaTeX sources accordingly. What I think you lose vs. Word is the ability to easily highlight the changes between multiple document revisions. This is not a big deal if you're doing one round with one reviewer, but it doesn't scale so well if this is a major editing project with many rounds of feedback and revisions.
Then, as you make all the changes, use standard VCS tools to track all the different versions of your .tex files. A git repo and a good diff viewer is all you need. This workflow scales much better than sending MS Word files all around your office.
发布评论
评论（2）
向某人发送 LaTeX 源代码的问题在于，除非他们本身就是 LaTeX 用户，否则他们不太可能安装必要的软件。我建议发送 PDF，任何人通常都可以在任何平台上阅读。
可以对 PDF 文档进行注释。我相信大多数 PDF 阅读器都支持这种开箱即用的方式。例如，我确信 Mac OS X 上的预览功能确实如此。
当您返回带有注释的 PDF 时，您可以返回并相应地编辑 LaTeX 源。我认为与 Word 相比，您失去的是轻松突出显示多个文档修订之间的更改的能力。如果您只与一名审稿人进行一轮评审，这并不是什么大问题，但如果这是一个需要多轮反馈和修改的大型编辑项目，那么规模就不会那么大了。
The problem with sending someone LaTeX source is that unless they're a LaTeX user themselves they are unlikely to have the necessary software installed. I would recommend sending a PDF, which anyone can typically read on any platform.
It is possible to make annotations to PDF documents. I believe most PDF readers support this out of the box. I'm certain, for example, that Preview on Mac OS X does.
When you get back the PDF with annotations, you can go back and edit the LaTeX sources accordingly. What I think you lose vs. Word is the ability to easily highlight the changes between multiple document revisions. This is not a big deal if you're doing one round with one reviewer, but it doesn't scale so well if this is a major editing project with many rounds of feedback and revisions.
PDF 更容易阅读，因为您不必在心里解析所有语法开销。在 http://en.wikipedia.org/wiki/Comparison_of_notetake_software 上检查哪些 PDF 阅读器支持注释
然后，当您进行所有更改时，使用标准 VCS 工具来跟踪 .tex 文件的所有不同版本。一个 git 存储库和一个好的 diff 查看器就足够了。此工作流程的扩展性比在办公室各处发送 MS Word 文件要好得多。
PDFs are easier to read, as you don't have to mentally parse all the syntactic overhead. Check which PDF readers support annotations on http://en.wikipedia.org/wiki/Comparison_of_notetaking_software
Then, as you make all the changes, use standard VCS tools to track all the different versions of your .tex files. A git repo and a good diff viewer is all you need. This workflow scales much better than sending MS Word files all around your office.