|
From: Dan M. <d-...@uc...> - 2001-09-11 03:53:26
|
On Mon, 10 Sep 2001, David Merrill wrote: > I'm having a problem with serving the images that are referenced in > docbook documents in scrollkeeper. What is the plan for identifying > them, and any other binaries that might be a part of the document? There are no plans for this. The main assumption I've been working on is that there is always one main document file, and that any other files needed are known about by this file or by the document processor for the particular file type. (eg. HTML and DocBook files typically refer to images by their relative path. DocBook docs typically need a DTD and stylesheet, but it is assumed that your DocBook setup understands how to find these files.) > Can I assume all binaries will be in the same directory that the > source sgml file is in? I suppose this would be a packaging > requirement for scrollkeeper? No, you can't assume that. In fact, you'll find that most GNOME documents place their screenshots in a subdirectory called figures/, or sometimes even figs/ or images/. In other cases, you'll find entities in a subdirectory as well. I expect this to be common in non-GNOME documents as well. Generally, we wanted ScrollKeeper to place as few restrictions and burdens on its users (ie. doc writers, hackers, and packagers) as possible. In particular, we didn't want to restrict what document formats people use or where the documents are stored. Dan |