> > Again, I don't see any reason why we should not > consider using > > StarOffice (BTW, it's "StarOffice"--one word, not > "star office") to > > publish the Adm Guide, as well as other Sun > publications. > > You are saying that Sun should start over from > scratch and attempt to > use the wrong kind of tool to attempt to reproduce > all the content at > http://docs.sun.com/app/docs? Good Grief! > > Bob > ====================================== > Bob Friesenhahn > [EMAIL PROTECTED], > http://www.simplesystems.org/users/bfriesen/ > GraphicsMagick Maintainer, > http://www.GraphicsMagick.org/
Well, the best way (& probably the only way) to convince others to use your product, is to use it yourself. The opposite of this moral is the real ugly one: If you (i.e., "Sun") don't use your own product, no one else will. The same theory also goes with Solaris. Actually, once your have the text, an experienced StarOffice user can do all the formatting in "less than an hour" (no kidding). Text is different from Graphics. With a proper collection of template libraries, all you need to do is click, click, and click. I apologize for wasting the bandwidth. As Richard mentioned in a previous reply, this is not a PDF problem. It just so happened that only Sun's documents have problems. This is particularly frustrating as I haven't had time to work around the VirtualBox bug in build 95. This message posted from opensolaris.org _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
