From: Artur H. <ko...@pl...> - 2003-09-07 08:05:52
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I would like to add something from me. > > My first thoughts, having read the Web Site, is that the > > principles of "generguide" must embody a broader concept > > that can be applied independent of the DTD or XML Schema > > used to create the XML Instances. Consequently, I think that > > the principles should cater to a wider group of document > > types. While Simplified DocBook is great for the purpose of > > illustrating the concepts of "generguide" I think that the > > application should be easily applied to the other doctypes. Well, the one main ideas (as I correctly understand) is to provide framework for using modular documentation. This idea and tools we use are DTD or Schema independent. They just process XML files and these XML files contains DTD declaration. So tools don't know anything about particular DTD indeed. Almost. 1. We have created xinclude DTD extension for DocBook but if another DTD will be used than another DTD extension can be created if necessary (some of other DTDs can have built-in xinclude support) and in fact it is not visible 'outside' XML files because it is used as DTD, so our tools are not dependent on it. 2. We use DocBook-XSL set for generating target formats from source XML files. This XSL set is designed especially for DocBook files. I mean our scripts points to this particular XSL templates. However, again, it can be easy changed just by script customization. 3. Well, yes, we use SDocBook internally for our documents and recommend it for other users. But it is the best supported DTD I know. At least the best supported DTD in open source/free applications of this kind. I mean these XLS templates which allows to generate target formats such as HTML, PDF, XHTML, WinHelp, LaTeX and some others. So, we should not have many problems with customization for other documents types while they are XML files and unless you want to join documents using different DTDs. However if you mean not XML files as you are talking about different types, than I must agree. Up to now we have been concentrating on XML files and including for our concept, for example TeX files, can be a little be more complex but not impossible. We are going to provide command line, automatic tools for processing our files as for example they are similar tools programming languages. We want to: 1. allow anybody generate chosen target format of documentation in very easy way with minimal installation effort. 2. allow to run these tools such as cron tasks 3. allow our framework to be integrated with other environments such as IDE or documentation editing tools. So I don't expect we will be able to support for example MSOffice documents in short time. Cameron I anything I wrote above is nonsense, please correct me. Artur - -- Artur Hefczyc "Don't change people, just live with them." Open Source Developer: http://www.geotools.org/ http://generguide.sourceforge.net/ http://wttools.sourceforge.net/ http://maven-plugins.sourceforge.net/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE/Wua90/6x1bjSKPkRAuULAKCfTavIlOerCVRgf5e1BtgvLzYCNwCfUBao H+JLgPCQHmuqqYRUKlrxNro= =yvqk -----END PGP SIGNATURE----- |