Docbook никуда не годится.

> ну где я возьму работающий FO-форматтер

Ну ты посмотрел хотя бы, приличия ради, в сторону DITA OT.

http://dita-ot.sourceforge.net/ :

> Key output targets are XHTML, HTML Help, PDF2 (processed using the Idiom plug-in and RenderX XEP)

http://www.renderx.com/download/personal.html :

> RenderX is pleased to offer a Free, Personal Edition of our software for non-commercial use.

Наверное, я что-то не понимаю... Впрочем, я действительно посмотрю на нее поближе. [безнадежно упавшим голосом] А больше, значит, ничего? Спасибо. Наверное, пойду я лучше перечитывать Гуссенса с Самариным...

Я тут почитал немного, и у меня сложилось впечатление. что DITA мне подходит еще меньше, чем Docbook. Docbook меня не устраивает реализацией, а DITA вообще ориентирована на другие цели:

http://www.dclab.com/dita_docbook.asp :

db: DocBook is a document type definition (DTD) for writing technical books and articles, with the structure that such forms imply.

dita: DITA is both a DTD and a set of rules for writing online contextual documentation such as software help files.

db: Simple. Can usually be downloaded and set up in a day.

dita: More complex. Usually requires more time and some technical expertise.

db: Well supported by the XML community

dita: Small but strong, growing community

db: With a little development, DocBook can do what DITA is attempting on a smaller scale

dita: DITA is impressively engineered, but can be too industrial-strength

http://drmacros-xml-rants.blogspot.com/2008/04/choosing-xml-schema-docbook-or... :

If you are looking for a documentation schema that you can just pick up and use and you don't need the modularity features of DITA (that is, you don't need the functionality of DITA maps) then DocBook probably makes the most sense for the reasons Richard cites, namely that there are more element types of likely utility out of the box and the processing infrastructure is more mature and better documented.

http://xml.coverpages.org/DocBook-DITA-customDTD.html :

As for whether to start with DocBook or DITA, my standard guidance is:

* If you need to get started immediately, want to initially invest as close to zero as you can, and your primary task is to produce typical technical manuals, use DocBook.

* If you have any requirement for re-use, specialization, or modular delivery AND you can afford a little up-front investment in analysis, specialization, and tool development, then use DITA.

The tradeoff is that DITA is, as currently defined, less well suited to book production out of the box — you can do everything you need but it may require more effort on your part (for example, DITA 1.0 is underspecified for index markup, something the DITA Technical Committee is discussing right now). Also, the current free DITA tool kits are not as functionally complete as the comparable DocBook tool kits are.