Thanks for the clarifications, Michelloe. :-) > We have a tool chain for docbook->html/pdf. > Here is 15-step tutorial to guide you through > Docbook->HTML using just command-line: > ttp://www.opensolaris.org/os/community/documentation/d > oc_collab/tutorial/
Right, I had forgotten this (perhaps partly because I haven't played with it much, not having taken the XML Kool-Aid yet. :-) ) > Here is a link to downloads and information about how > to do docbook to HTML transformations using > DocBookTrans GUI tool and to do other docbook > transformations, like to PDF: > http://www.opensolaris.org/os/community/documentation/ > doc_collab/tools/ I was speaking more to the Sun-original/SolBook books on docs.sun.com, but you're right, that only tells part of the story. I may have tightened my response too narrowly, based on my reading of Peter's question. > The Solaris Express books (those for which we publish <isnip> > push to opensolaris. Ibid. > Basically, we have one more phase before we get to > full-blown SCM hosted doc repositories, but we're > well on our way. Hope this helps. > > -Michelle Peter, I may have framed my response in too narrow a scope, based upon my (perhaps incorrect?) reading of your post. I was assuming you were speaking directly to the manuals (xxx-yyyy) on docs.sun.com. As Michelle has pointed out, the documentation scope has widened with the formation of the OS Documentatioon forum. I don't think you can call it a fork, as much as it is a thickening of the soup. I would hesitate to call it a layer, as that implies one is over the other. Rather, the efforts here (like the Express Books) are meant to be additional to all levels of (previous Sun-written) documentation on docs.sun.com, giving a fuller understanding. Would that be a decent way to say it, Michelle? Michelle certainly also knows more about what happens outside the discussions on this forum (such as at Sun), so I bow to her fuller understanding. :-) Rainer This message posted from opensolaris.org
