On Tue, Aug 07, 2012 at 06:37:05PM -0400, David Nalley wrote: > Hi folks. > > I experienced a problem today building the docs set now that we have > an entity in place. The problem that I found was: (building with > --format=test succeeds, but specifying a real output fails complaining > about not being able to locate an entity.)
Yes. I think the problem is actually that some files do not have a DTD at all. So they don't tell Publican to look for cloudstack.ent. When I started doing the license clean up, some of the files had no DTD at all - so I thought that was because they were pulled into other files as includes and didn't need the DTD. That seems to be an error on my part - so once I finish licensing & fixing the DTDs in the rest of the files on my list, I'll go back and make sure that they all have the proper DTD. > The problem is, that when compiling to a real output format it expects > to find Doc_name.ent - and of course that isn't there. cloudstack.ent > is the only thing present. If there are no declared entities, you > never see a problem. However, publican.cfg declares the name to be: > release-notes-3.0.4, however there are a number of these, so my > supposition is that it's all designed to work with a single set of XML > documents and picking which are included for any given document > produced. I don't think it'll matter what the publican.cfg declares as long as the XML files have the pointer to cloudstack.ent > So how do we solve this. symlink a .ent to cloudstack.ent file for > each doc produced? Create a directory to house all of the XML files > and symlink them as appropriate to the document they are to be > included in? Something else? I'll fix the missing DTD/ENTITY declaration and make sure everything compiles. That should leave us in good shape unless I've missed something. -- Joe Brockmeier http://dissociatedpress.net/ Twitter: @jzb
