blocks|key|432728|text|大多数wiki支持通过PDF导出，例如：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|432729|432730|MediaWiki+PDF+Export+|unordered-list-item|offset|length|432731|DokuWiki+PDF+Export|432732|TWiki+PDF+Export|432733|432734|entityMap|0|LINK|mutability|MUTABLE|url|http://www.mediawiki.org/wiki/Extension:Pdf_Export|1|http://www.dokuwiki.org/plugin:html2pdf|2|http://www.wikimatrix.org/wiki/TWiki:PDF%2520Export^0|0|0|0|K|0|0|0|J|1|0|0|G|2|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|10|8|@]|9|@$F|11|G|12|1|13]]|A|$]]|$1|H|3|I|5|E|7|14|8|@]|9|@$F|15|G|16|1|17]]|A|$]]|$1|J|3|K|5|E|7|18|8|@]|9|@$F|19|G|1A|1|1B]]|A|$]]|$1|L|3|-4|5|6|7|1C|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|1D|8|@]|9|@]|A|$]]]|N|$O|$5|P|Q|R|A|$S|T]]|U|$5|P|Q|R|A|$S|V]]|W|$5|P|Q|R|A|$S|X]]]]

Most wikis support export via PDF e.g.:

<ul>
<li><a href="http://www.mediawiki.org/wiki/Extension:Pdf_Export" rel="nofollow noreferrer">MediaWiki PDF Export</a> </li>
<li><a href="http://www.dokuwiki.org/plugin:html2pdf" rel="nofollow noreferrer">DokuWiki PDF Export</a></li>
<li><a href="http://www.wikimatrix.org/wiki/TWiki:PDF%20Export" rel="nofollow noreferrer">TWiki PDF Export</a></li>
</ul>

blocks|key|1078348|text|您目前是如何存储帮助源的？是MS+Word文件、MS+help还是LaTeX？|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1078349|如果您将帮助源文件置于版本控制之下，那么您将获得wiki的所有好处，而无需迁移到新系统-人们可以轻松地对帮助文件进行编辑-这些更改可以被跟踪、恢复等，并且您可以像以前一样获得美化的手册。|1078350|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

How are you storing the help source at the moment? Is it MS Word files, MS help, LaTeX?

If you put your help source files under version control then you will get all the benefits of a wiki without having to migrate to a new system - people can make edits to the help files easily - those changes can be tracked, reverted etc. and you get the prettified manuals as before.

blocks|key|1083649|text|您可以编写一些东西，从维基生成LaTeX并将手册呈现为PDF。使用像hyperref这样的包，您可以将交叉引用保留为超链接。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1083650|此外，您可以将来自多个源的内容集成到LaTeX文档中，该文档可以与wiki内容混合和匹配。您还可以设置体系结构，以便它可以支持任意方向的交叉引用。|1083651|Framemaker还可以使用生成的MIF文件来支持这一点，您也可以以类似的方式使用Lout，或者将您的wiki内容转换为docbook,，这将允许您使用该格式的许多呈现选项中的任何一个。|1083652|顺便说一句，下面的Stackoverflow帖子讨论了维护文档的各种系统。|1083653|1083654|Application+(Not+a+Markup+Language)+for+Producing+a+User+Manual|unordered-list-item|1083655|Can+LaTeX+be+used+for+producing+any+documentation+that+accompanies+software?|1083656|What+tools+are+used+to+write+documentation?|1083657|What+tools+does+your+team+use+for+writing+user+manuals?|1083658|How+best+to+write+documentation+(ideally+in+latex)+targeting+both+the+web+(html)+and+paper+(pdf)?+|1083659|Best+tool(s)+for+working+with+DocBook+XML+documents?|1083660|What+is+the+recommended+toolchain+for+formatting+XML+DocBook?|1083661|Is+a+successor+for+TeX/LaTeX+in+sight?|1083662|1083663|entityMap|0|LINK|mutability|MUTABLE|url|http://www.ctan.org/|1|http://www.tug.org/applications/hyperref/|2|http://www.adobe.com/uk/products/framemaker/?sdid=EGQWM|3|http://help.adobe.com/en_US/FrameMaker/9.0/MIF_Reference/MIF_Reference.pdf|4|http://lout.wiki.sourceforge.net/|5|http://www.docbook.org/|6|https://stackoverflow.com/questions/371654/application-not-a-markup-language-for-producing-a-user-manual|7|https://stackoverflow.com/questions/501241/can-latex-be-used-for-producing-any-documentation-that-accompanies-software|8|https://stackoverflow.com/questions/12537/what-tools-are-used-to-write-documentation|9|https://stackoverflow.com/questions/314117/what-tools-does-your-team-use-for-writing-user-manuals|10|https://stackoverflow.com/questions/409717/how-best-to-write-documentation-ideally-in-latex-targeting-both-the-web-html|11|https://stackoverflow.com/questions/55622/best-tools-for-working-with-docbook-xml-documents|12|https://stackoverflow.com/questions/122752/what-is-the-recommended-toolchain-for-formatting-xml-docbook|13|https://stackoverflow.com/questions/303877/is-a-successor-for-tex-latex-in-sight^0|F|5|0|Y|8|1|0|0|0|A|2|I|3|3|16|4|4|1P|8|5|0|0|0|0|1R|6|0|0|24|7|0|0|17|8|0|0|1J|9|0|0|2Q|A|0|0|1G|B|0|0|1P|C|0|0|12|D|0|0^^$0|@$1|2|3|4|5|6|7|20|8|@]|9|@$A|21|B|22|1|23]|$A|24|B|25|1|26]]|C|$]]|$1|D|3|E|5|6|7|27|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|28|8|@]|9|@$A|29|B|2A|1|2B]|$A|2C|B|2D|1|2E]|$A|2F|B|2G|1|2H]|$A|2I|B|2J|1|2K]]|C|$]]|$1|H|3|I|5|6|7|2L|8|@]|9|@]|C|$]]|$1|J|3|-4|5|6|7|2M|8|@]|9|@]|C|$]]|$1|K|3|L|5|M|7|2N|8|@]|9|@$A|2O|B|2P|1|2Q]]|C|$]]|$1|N|3|O|5|M|7|2R|8|@]|9|@$A|2S|B|2T|1|2U]]|C|$]]|$1|P|3|Q|5|M|7|2V|8|@]|9|@$A|2W|B|2X|1|2Y]]|C|$]]|$1|R|3|S|5|M|7|2Z|8|@]|9|@$A|30|B|31|1|32]]|C|$]]|$1|T|3|U|5|M|7|33|8|@]|9|@$A|34|B|35|1|36]]|C|$]]|$1|V|3|W|5|M|7|37|8|@]|9|@$A|38|B|39|1|3A]]|C|$]]|$1|X|3|Y|5|M|7|3B|8|@]|9|@$A|3C|B|3D|1|3E]]|C|$]]|$1|Z|3|10|5|M|7|3F|8|@]|9|@$A|3G|B|3H|1|3I]]|C|$]]|$1|11|3|-4|5|6|7|3J|8|@]|9|@]|C|$]]|$1|12|3|-4|5|6|7|3K|8|@]|9|@]|C|$]]]|13|$14|$5|15|16|17|C|$18|19]]|1A|$5|15|16|17|C|$18|1B]]|1C|$5|15|16|17|C|$18|1D]]|1E|$5|15|16|17|C|$18|1F]]|1G|$5|15|16|17|C|$18|1H]]|1I|$5|15|16|17|C|$18|1J]]|1K|$5|15|16|17|C|$18|1L]]|1M|$5|15|16|17|C|$18|1N]]|1O|$5|15|16|17|C|$18|1P]]|1Q|$5|15|16|17|C|$18|1R]]|1S|$5|15|16|17|C|$18|1T]]|1U|$5|15|16|17|C|$18|1V]]|1W|$5|15|16|17|C|$18|1X]]|1Y|$5|15|16|17|C|$18|1Z]]]]

You can write something that generates <a href="http://www.ctan.org" rel="nofollow noreferrer">LaTeX</a> from the wiki and renders a manual to PDF. With packages like <a href="http://www.tug.org/applications/hyperref/" rel="nofollow noreferrer">hyperref</a> you can retain cross-references as hyperlinks. 

Additionally, you can integrate content from multiple sources such as a data dictionary into the LaTeX document, which can be mixed and matched with the wiki content. You could also set the architecture up so it can support cross-referencing that goes either way.

<a href="http://www.adobe.com/uk/products/framemaker/?sdid=EGQWM" rel="nofollow noreferrer">Framemaker</a> could also support this using generated <a href="http://help.adobe.com/en_US/FrameMaker/9.0/MIF_Reference/MIF_Reference.pdf" rel="nofollow noreferrer">MIF</a> files, and you could also use <a href="http://lout.wiki.sourceforge.net/" rel="nofollow noreferrer">Lout</a> in a similar way or convert your wiki content to <a href="http://www.docbook.org/" rel="nofollow noreferrer">docbook,</a> which would allow you to use any of the many rendering options available to that format.

As an aside, the following Stackoverflow postings discuss various systems for maintaining documentation.

<ul>
<li><a href="https://stackoverflow.com/questions/371654/application-not-a-markup-language-for-producing-a-user-manual">Application (Not a Markup Language) for Producing a User Manual</a></li>
<li><a href="https://stackoverflow.com/questions/501241/can-latex-be-used-for-producing-any-documentation-that-accompanies-software">Can LaTeX be used for producing any documentation that accompanies software?</a></li>
<li><a href="https://stackoverflow.com/questions/12537/what-tools-are-used-to-write-documentation">What tools are used to write documentation?</a></li>
<li><a href="https://stackoverflow.com/questions/314117/what-tools-does-your-team-use-for-writing-user-manuals">What tools does your team use for writing user manuals?</a></li>
<li><a href="https://stackoverflow.com/questions/409717/how-best-to-write-documentation-ideally-in-latex-targeting-both-the-web-html">How best to write documentation (ideally in latex) targeting both the web (html) and paper (pdf)? </a></li>
<li><a href="https://stackoverflow.com/questions/55622/best-tools-for-working-with-docbook-xml-documents">Best tool(s) for working with DocBook XML documents?</a></li>
<li><a href="https://stackoverflow.com/questions/122752/what-is-the-recommended-toolchain-for-formatting-xml-docbook">What is the recommended toolchain for formatting XML DocBook?</a></li>
<li><a href="https://stackoverflow.com/questions/303877/is-a-successor-for-tex-latex-in-sight">Is a successor for TeX/LaTeX in sight?</a></li>
</ul>

blocks|key|1078420|text|我点击了Node的链接，偶然发现了一些我认为值得注意的mediawiki页面。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1078421|1078422|Extension:OpenDocument+Export|unordered-list-item|offset|length|1078423|Extension:PDF+Writer|1078424|Category:Data+extraction+extensions|1078425|1078426|entityMap|0|LINK|mutability|MUTABLE|url|http://www.mediawiki.org/wiki/Extension:OpenDocument_Export|1|http://www.mediawiki.org/wiki/Extension:PDF_Writer|2|http://www.mediawiki.org/wiki/Category:Data_extraction_extensions^0|0|0|0|T|0|0|0|K|1|0|0|Z|2|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|10|8|@]|9|@$F|11|G|12|1|13]]|A|$]]|$1|H|3|I|5|E|7|14|8|@]|9|@$F|15|G|16|1|17]]|A|$]]|$1|J|3|K|5|E|7|18|8|@]|9|@$F|19|G|1A|1|1B]]|A|$]]|$1|L|3|-4|5|6|7|1C|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|1D|8|@]|9|@]|A|$]]]|N|$O|$5|P|Q|R|A|$S|T]]|U|$5|P|Q|R|A|$S|V]]|W|$5|P|Q|R|A|$S|X]]]]

I followed Node's links and came across some mediawiki pages that I thought were noteworthy.

<ul>
<li><a href="http://www.mediawiki.org/wiki/Extension:OpenDocument_Export" rel="nofollow noreferrer">Extension:OpenDocument Export</a></li>
<li><a href="http://www.mediawiki.org/wiki/Extension:PDF_Writer" rel="nofollow noreferrer">Extension:PDF Writer</a></li>
<li><a href="http://www.mediawiki.org/wiki/Category:Data_extraction_extensions" rel="nofollow noreferrer">Category:Data extraction extensions</a></li>
</ul>

blocks|key|3652941|text|Madcap+Flare是一个帮助和手动创作工具，它使用超文本标记语言作为每个主题的源。您可以很容易地对Wiki页面进行大量导入。然后需要一些清理，但在此之后，您有一个很好的单一来源系统，可以输出CHM，web浏览的帮助，PDF，DOC/DOCX等。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3652942|entityMap|0|LINK|mutability|MUTABLE|url|http://www.madcapsoftware.com/products/flare/^0|0|C|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

<a href="http://www.madcapsoftware.com/products/flare/" rel="nofollow noreferrer">Madcap Flare</a> is a help-and-manual authoring tool that uses HTML for the source of each topic. You could pretty easily do a mass import of the Wiki pages. Would then require some cleaning but after that you have a nice single-source system that can output CHM, web-browsable help, PDF, DOC/DOCX, etc.

blocks|key|1083739|text|我给出了一个可能对"wiki+to+PDF“部分有用的previous+answer+--看看使用开放源码的PediaPress代码或功能。您也可以从它获得ODF，尽管它们的PDF已经相当漂亮(但我想您可能想为您的公司重新命名和重新设计它)。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1083740|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/447216/web-pages-to-print-media-solutions/618009#618009^0|R|F|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

I gave a <a href="https://stackoverflow.com/questions/447216/web-pages-to-print-media-solutions/618009#618009">previous answer</a> which may be useful for the "wiki to PDF" part -- look at using the open source PediaPress code or functionality. You can get ODFs from it too, although their PDFs are already quite pretty (but you might want to rebrand it and restyle it for your company I suppose).

We're in the middle of deploying a new software system to lot's of users in lot's of places (200+ users over 8 countries). In the past we've written a manual for the users, then update it every so often. This works ok, in that all the users ahve the same manual and it covers the main things but it has it's problems, like it doesn't get updated that often, we sometimes miss updates, and some users will have old copies.

We've been talking about using a wiki during the testing and deployment phases to build a knowledge base about the system. Ideally we'd then like some way to convert that into some form fo electronic document that we can then 'pretty-fie' and send out as the official manual, as well as letting users use and update the wiki.

Has anyone else done anything similar ? Any suggestions for wiki systems, workflows, document formats etc?

Workflow to Turn Wiki content into a system manual

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我们正在为很多地方的用户(超过8个国家的200+用户)部署一个新的软件系统。在过去，我们为用户编写了一份手册，然后每隔一段时间更新一次。这工作的很好，因为所有的用户都有相同的手册，它涵盖了主要的东西，但它也有它的问题，比如它不经常更新，我们有时会错过更新，一些用户会有旧的副本。我们一直在讨论在测试和部署阶段使用wiki...

问将Wiki内容转换为系统手册的工作流程
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问将Wiki内容转换为系统手册的工作流程EN