tomc@modcomp.uucp (Tom Cianflone) (03/22/91)
We are starting to look into CDROM publishing and need information on the process itself and customer acceptability. Let me define our application: We want to do away with the volumes of hard copy documentation we usually send along with our products. Instead, we are thinking of supplying the documentation on CDROM. I've heard that DEC, among others, is doing this already. (Is this just a rumor?) Any case studies, pointers to articles or books about the subject, or any info you have the time to type in or have online would be appreciated. Also, if there is another group in which this post might get better response, please let me know. Comp.text was the only one I saw that came close. My questions follow: The Technologies and the Process 1. How are images stored on CDROM? Are page images stored bitmapped so they can simply be displayed without processing on a graphics terminal? 2. If not 1, then are they in some page description language such as PostScript? This would require images to be processed before they could be displayed and would affect access times, it would seem to me. 3. What about access and retrieval software? Are there companies that offer turnkey systems where all we have to do is have our manuals mastered onto CDROM and their system does the search, display, and print handling? 4. Is there a difference in approach in just storing manuals on CDROM for online retrieval and later setting up some kind of hypertext system to access the information. We would like not to embark on a path from which we will have to retreat later to do hypertext, if we get around to it. 5. What format and medium do CDROM mastering houses want to receive from us with which to produce the master? Customer Acceptability The only way I can see this working is that we would provide one set of hard copy with the system. The customer would also have to have the CDROM drive and any other special hardware it would take to view the manuals online. I suspect that this would require a bitmapped graphics terminal of some sort, no? Then, if they wanted more hard copy, they could either photocopy the hardcopy they got (they won't like this) or print out additional sets of the manuals. This latter approach means they have to have the right printer to do the job. So, how do you sell the customer on buying stuff that he needs only for looking at the documentation? Granted, if we distributed software on CDROM, they would already have the drive. But how about the bitmapped terminal? In the realtime programming environment we sell to, ASCII terminals are still the standard terminals people work at. Without hard copy, a programmer would either have to have a terminal on which to view the docs, or go to a central terminal to do this (ha!). A windows terminal would be ideal - you could program in one window and read the manual in another. But does that make windowing terminals a prerequisite for using our documentation? And a decent laser printer to handle the printing of additional manuals? Buying hardware solely for the purpose of reading documentation seems to be a big drawback from the customer's perspective. Well, as you can see, we need some sound guidance on this topic. Any case studies, pointers to articles or books about the subject, or any info you have the time to type in or have online would be appreciated. Thanks! -- Regards, Tom Cianflone <uunet!modcomp!tomc> -or- <modcomp!tomc@uunet.uu.net>