ben wrote: > > Actually the case was not for included files (even it's something I > 've been waiting for too ;-) but for some repeated or configurable > text used in the doc. For instance it can be usefull to declare > something like this,avoiding to change a version number in the whole > document (it's only an example): > > <!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook V4.0//EN" [ > <!ENTITY version "1.0.3"> > <!ENTITY project '<emphasis>MyProject</emphasis>'> > ]> > <book> > ... > <para>The release &version; of &project; now supports new > things.</para> > ... > </book> > > I mean that entities should not be seen only as file inclusion.
Of course, we agree on that. Note that we do not plan to support these text entities. Sorry. We just want to implement a simple and handy way to support multi-file documents. And this implementation will be based on standard external entities, not on proprietary mechanisms.
