You can use eZ publish to store information like this. Take for example look at the documentation done in eZ publish.
However you should split the book up in several smaller pieces. E.g. every chapter and sub chapter should be made as a separate object. This will enable simpler navigation and simpler management of content parts.
You can make this work with an import/export to docbook, but this does not exist and has to be written.
... or you can use the new open office extension (beta) and convert via openoffice. All content is stored in ez in xml, so writing an export extension is "easily" possible.
Yes, I have also assessed OpenOffice writer as an emerging, key authoring tool. Others may know better, but for me so far it looks like eZ publish is best suited for web publishing of the various parts written with OOo.
When we talk about a whole book or a set of books that also should be published on papers (hardcopy), they will typical need created table of contents (with toc.depth), chapter and section numbers, page numbers and indexes. I haven't seen that eZ publish can do this during the pdf generation process.
This can be created with OpenOffice in addition to create and work with master documents and subdocuments, features suited for working with long documents like books. OpenOffice can also export to pdf directly.
Another possibility I have waited for should mature, is the preliminary OpenOffice projects to use OpenOffice as an xml editor for DocBook. Using this Docbook filter and tools it might be possible to read and write docbook xml format. Docbook to pdf is well suited for book production:
http://xml.openoffice.org/xmerge/docbook/temp_test_only.html http://de.openoffice.org/doc/sonstiges/docbook-user-guide-de.pdf
Terje J. Hanssen
You must be logged in to post messages in this topic!
