Related Entries

Processing e-mail attachments properly
The Cranky User
Building accessible tables
Inaccessible accessibility
Day 10 gets me stumped!

« Bye bye HP Pavilion!
» Great recipes

Accessibility guidelines

Download from Dartmouth college. Good information, but they chose to put it up as a Word document. Not really following...

Download from Dartmouth college. Good information, but they chose to put it up as a Word document. Not really following their own advise :-(

Putting web content in Microsodt Word is one of the plagues that I’m still trying to find a solution to. Even people who agree that Word is not a portable solution still sing to a different tune if it is their job to put in content.

What I think will work (atleast for engineers) is a solution or tool that is
- easy to type in. Structured text is great.
- easy to categorize as chapters and sections. I think a Zope solution wherein chapters can be folders and sections can be individual documents within the folders will work the best.
- capable of producting document in multiple formats; at the very minimum in HTML, split HTML, PDF and Microsoft CHM (compiled help)
- capable of doing version control. This is one area where Zope still falls short. May be ZCVSMixin will help.
- capable of implementing work flows. Zope CMF comes to mind.
- talk back enabled.

Zope book and developer’s guide is done in a similar way, except that it doesn’t stay within Zope, but in the file system. Will Zope Corp. be interested in making this a product?

DocBook format is ideal for documentation, but it is so insultingly complex to use. Are there any WYSIWYG tools for DocBook?

//-->