 |
 |
> OK, thinking about this a little more, perhaps it's Star2HTML that is now > mis-configured. > > The underlying assumption about what it does is that it's better to rely > on local documents and if you want to go off site, you'd better have made > that clear (which is why hlink is essential at some stage after creating > the document). > > Perhaps we should change Star2HTML so that all newly created documents all > point their cross-references to the RAL document set instead, and then you > run hlink when you (to quote Norman) have a HTX clue and prefer to use the > local documents when they are available. In which case hlink becomes a > non-essential post-install task, assuming you have good network access > (that wasn't the case when Star2HTML and HTX were conceived). > > Under this scheme hlinking is a specialist AST job, as it has two > documents that want to refer to each other locally. Sounds OK. Would star2html then have a genuine dependancy on htx? In fact the two AST docs are almost entirely independant of each other. They only have a couple of cross-references, so it wouldn't really matter if they were hlinked or not, if all links already pointed correctly to the RAL docs. kaplibs would still have a dependancy on htx. David