On Thu, 18 Oct 2001, Michael Smith wrote:
> However we decide to model it, it seems like Refentry needs to be
> allowed in there somewhere.
Agreed.
> And if we do add a recursive topic element to divcomponent.mix, I too
> would be strongly opposed to allowing it to contain other sectioning
> ele
On Thu, 18 Oct 2001, Michael Smith wrote:
> But the content model Norm proposed for Topic is recursive, just like
> the one for Section is -- that is, a Topic can contain other Topics,
> nested indefinitely. So you could do:
>
>
> How to Drive
>
> Start to start your car
>
>
That's what I come up with whenever I try to develop a DTD for online
help... I think it's the correct approach.
Gershon
On Thu, 18 Oct 2001, Dave Pawson wrote:
> Using the 'dita' logic, wouldn't that then be a collection of individual
> topics?
> I.e. a super-topic?
> topic: what the engine is
Phillip,
Did you update the fields in the RTF file after generating the RTF? One
needs to open the RTF file in Word, select all (Ctrl+A) and the update
fields (F9). That should do the trick.
Gershon
On Thu, 18 Oct 2001, Phillip Shelton wrote:
> I am using Jade and the DSSSL1.73 style sheets ag
Norm,
I'm busy customizing the DocBook DTD and came across the following bug in
xbpoolx.mod.
Instead of:
]]>
is written:
]]>
Of course, the DTD works correctly, since it's only a documentation bug,
but you may as well fix it.
Gershon
Im all for this addition too. I currently use with hardcoded
screens, which have to be changed "in place" for each release. It would be
much easier to use file entities with to manage these.
Gershon
--
To unsubscribe from this
