hallo adam,
Adam Murdoch-2 wrote: > > We're just writing a user guide here. That's it. > good point ... considering the requirements i do recommend not to use dita. it's much too heavy and it uses old-fashioned technology. but dita has done a very fine analysis of document- processing. i mentioned dita because from some dita-points of view docbook is legacy. trust me in that. so ... i do not recommend docbook either ;-) nor latex ... isnt that mysterious ? Adam Murdoch-2 wrote: > > Which schema would we use in this case? Make one up? Use docbook's? > This tool could be useful for the source -> pdf transformation, but does > it handle the source -> html transformation? > write your documents in xhtml. xhtml is xml and there is a DTD and a Schema for xhtml. the web is the master-content then. this makes community-contributions simple compared to docbook or dita. its also close to upcomming concepts for the semantic web -> rdf(a), microformats. but ... this solution is not good for distibuted content and multichannel output (rtf etc.) also princexml and oxygene are commercial products and might not be an option for an open-source-project. there seems to be no 'real good' solution at the moment. -- View this message in context: http://www.nabble.com/ditch-latex--tp20196953p20218991.html Sent from the gradle-dev mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
