Documentation file format
jralls at ceridwen.us
Mon Dec 16 23:40:31 EST 2013
On Dec 16, 2013, at 4:32 PM, Mike Alexander <mta at umich.edu> wrote:
> On Dec 16, 2013, at 5:49 PM, John Ralls <jralls at ceridwen.us> wrote:
>> All of which is utterly moot, because it doesn’t work with our documents: It requires that you open each file separately for editing. It will display the whole document just fine, but it won’t let you edit anything that’s in a separate file. It’s too dumb, even when the master document is opened as a document set, to go look at the master document for the attribute references, so none of the chapter files will load.
> Editing entities inline is tougher than you think because entities can have quite a different environment than the parent document. This is probably not true of GnuCash documents, but in the general case can be. I was involved in implementing that one time and it's not trivial. It's more likely that they allow editing of XIncludes inline than entities (although I haven't looked so I don't know for sure) and we could probably change things to use them instead of entities.
You misunderstand: XMLEditor refuses to edit the included files from the master document. That's OK, they say that you have to load the module files separately, and provide a context menu item to do so if you load the master doc as a "document set". The problem is that when you try to load that module file, XMLEditor *errors out* because it can't resolve the entities in the module file.
The obvious work around (I think) is to put the DTD references containing the entities in the Document element of every module, but that makes maintenance a bit of a headache if you need to change the list of DTDs.
More information about the gnucash-devel