On 10/25/2010 10:41 AM, Miles Libbey wrote:
ie, Docbook? (Shutters) It is the 'industry standard', but, it would imply that we'll have some transformation scripts to produce both the
I don't know, the experts in the community should decide / work on this :).
HTML and PDFs. Docbook is just XML, so, its more strict than HTML, but there are not many free docbook tools and IMHO don't hide the complexity very well. Regardless, I'm not opposed to tossing the current documentation setup, but, I think we need to be quite clear on the problems we are trying to solve, and make sure the new stuff will really solve them. One problem we'll eventually need to solve is how to do translations. No matter what code the documentation is written in, I don't think that's going to be easily done.
I totally forgot about that. Yes, this is absolutely a requirement going forward with any 'rewrite' of the docs system. I know some people have already completed a chinese version of the docs, yet we have no way of "incorporating" this easily at least. Not to mention how to deal with incremental updates to the docs (how will a translation owner know that a particular piece in the english document has changed?).
Cheers, -- Leif
