I would just do the documentation in Linux too. MS Office can be run using some Wine derivative (or so I'm told), but I would rather use OpenOffice.org for such documents.
If you absolutely have to use Windows, you can boot a virtual machine (using e.g. VirtualBox) and do the dirty work while still having access to your preferred environment.
The teams I've been with always write documentation in Linux. POD makes it very easy to write tolerable-looking man pages, and higher-level ("glossy") documentation can be done with simple tools (HTML), moderate-complexity tools (markdown) or with very complex tools (LaTeX).
To each their own, but I'd avoid the Office and OpenOffice tools like a skunk, because they play so poorly with git, svn, cvs, etc. (diff, blame, merge, etc., just don't work with a big binary pile of data.)
(1) 使用基于网络的文档。示例包括 Google 文档或 wiki。只要您有网络浏览器，就可以查看和编辑文档。
(2)使用跨平台办公套件。我在 Linux 上安装了 OpenOffice.org，它可以打开 Microsoft Office 文件格式，包括新的 .*X 格式。您唯一需要做的就是确保稍后在 Microsoft 产品中打开它，以确保格式仍然良好。
但我个人工作过的每个地方都进行了跨平台开发。在这些情况下，开发计算机通常是 Windows 机器，开发人员要么运行 Linux VM，要么通过 SSH 连接到 Linux 服务器来测试他们在部署环境中的工作。
There are two options that I've seen used.
(1) Use web-based documentation. Examples include Google Docs or a wiki. As long as you have a web browser, you can view and edit the documentation.
(2) Use a cross-platform office suite. I have OpenOffice.org installed on Linux and it can open Microsoft Office file formats, including the new .*X format. The only thing that you need to do is to make sure that you open it in a Microsoft product later to make sure the formatting is still good.
But everyplace that I've personally worked performed cross-platform development. In these cases, the development machines were typically Windows boxes and the developers either ran Linux VMs or SSH'ed into a Linux server to test their work on the deployment environment.
发布评论
评论（4）
我也会在 Linux 中编写文档。 MS Office 可以使用一些 Wine 衍生物来运行（或者我是这么被告知的），但我宁愿使用 OpenOffice.org< /a> 用于此类文件。
如果您绝对必须使用 Windows，您可以启动虚拟机（使用例如 VirtualBox）并执行脏操作工作的同时仍然可以访问您喜欢的环境。
I would just do the documentation in Linux too. MS Office can be run using some Wine derivative (or so I'm told), but I would rather use OpenOffice.org for such documents.
If you absolutely have to use Windows, you can boot a virtual machine (using e.g. VirtualBox) and do the dirty work while still having access to your preferred environment.
我所在的团队总是在 Linux 中编写文档。 POD 使得编写外观还算可以的手册页变得非常容易，并且可以使用简单的工具 (HTML)、中等复杂的工具 (markdown) 或非常复杂的工具 (LaTeX) 来完成更高级别（“光泽”）的文档。
每个人都有自己的想法，但我会像臭鼬一样避免使用 Office 和 OpenOffice 工具，因为它们与 git、svn、cvs 等的配合非常糟糕。（
diff、blame、merge等，只是不适用于大量二进制数据。）The teams I've been with always write documentation in Linux. POD makes it very easy to write tolerable-looking man pages, and higher-level ("glossy") documentation can be done with simple tools (HTML), moderate-complexity tools (markdown) or with very complex tools (LaTeX).
To each their own, but I'd avoid the Office and OpenOffice tools like a skunk, because they play so poorly with git, svn, cvs, etc. (
diff,blame,merge, etc., just don't work with a big binary pile of data.)我见过使用过两种选项。
(1) 使用基于网络的文档。示例包括 Google 文档或 wiki。只要您有网络浏览器，就可以查看和编辑文档。
(2)使用跨平台办公套件。我在 Linux 上安装了 OpenOffice.org，它可以打开 Microsoft Office 文件格式，包括新的 .*X 格式。您唯一需要做的就是确保稍后在 Microsoft 产品中打开它，以确保格式仍然良好。
但我个人工作过的每个地方都进行了跨平台开发。在这些情况下，开发计算机通常是 Windows 机器，开发人员要么运行 Linux VM，要么通过 SSH 连接到 Linux 服务器来测试他们在部署环境中的工作。
There are two options that I've seen used.
(1) Use web-based documentation. Examples include Google Docs or a wiki. As long as you have a web browser, you can view and edit the documentation.
(2) Use a cross-platform office suite. I have OpenOffice.org installed on Linux and it can open Microsoft Office file formats, including the new .*X format. The only thing that you need to do is to make sure that you open it in a Microsoft product later to make sure the formatting is still good.
But everyplace that I've personally worked performed cross-platform development. In these cases, the development machines were typically Windows boxes and the developers either ran Linux VMs or SSH'ed into a Linux server to test their work on the deployment environment.
Steve Streeting 写了一篇有趣的 博客文章关于他的技术文档工具链有以下要求：
Steve Streeting wrote an interesting blog post about his technical documentation tool chain with the following requirements: