[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [docbook] Re: How to handle lost functionality regarding thetoc element and lot element in DocBook 5
Norm, Thanks. The note I was referring to was in the specification. Table 1 says that lot, lotentry, tocback, tocchap, tocfront, toclevel1, toclevel2, toclevel3, toclevel4, toclevel5, tocpart are Replaced by simpler tocdiv element. I haven't checked the How To; it may also need some changes. Since an empty toc is valid, I can recode <lot role="figure"/> with <toc remap="lot" role="figure"/>. We may add a class attribute to toc to provide an enumerated list of values; it makes it easier on new authors. I tested against the role version against the V5.0b5 RelaxNG and it validates. Just a matter of changing the match in our XSLT. Thanks again. Larry Rowland On Thu, 2006-04-20 at 09:23 -0400, Norman Walsh wrote: > / "Rowland, Larry" <larry.rowland@hp.com> was heard to say: > | as a child of chapter or appendix to trigger the ToC generation. It > | would be desirable to preserve this capability in the new version of > | DocBook. > > Indeed. > > | The writeup for DocBook 5.0 says <tocdiv> replaces the functionality of > | <lot>, but it was not clear how this would work. > > I think that's a small error in the howto. It'd be clearer to say that > "toc" replaces "lot". > > | If eliminating <lot> is desirable, perhaps we could use an empty ToC > | with a class attribute or something similar. > > Yep. And you can do that today :-) DocBook 5.0 allows an empty <toc/>. > > Be seeing you, > norm >
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]