[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: DOCBOOK: Re: blockinfo in partintro
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 / Camille Bégnis <camille@mandrakesoft.com> was heard to say: | Norman Walsh wrote: |> / Camille Bégnis <camille@mandrakesoft.com> was heard to say: |> | I was probably sleeping when TC discussed the new blockinfo element. I |> | feel it is also needed in partintro. |> | Rationale: partintro element is found on the same level as appendix, |> | article, chapter, preface, etc. which all bring a *info element. On a |> | system where blocks of information are sliced at this level, an "info" |> | element is badly needed in partintro. |> | |> | I'd like to hear your feeling before filling a RFE. |> You're probably right. Though I don't know if it should be blockinfo |> or partintroinfo. The only reluctance I have is that a part and it's |> introduction would usually share the same metadata, I would imagine. | | I fear I don't agree with that. The part's metadata applies to the | whole part's content, while the partintro's metadata applies only to | the content of the introduction. Fair enough. File that RFE! :-) Be seeing you, norm - -- Norman Walsh <ndw@nwalsh.com> | The human race consists of the http://www.oasis-open.org/docbook/ | dangerously insane and such as are Chair, DocBook Technical Committee | not.--Mark Twain -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: Processed by Mailcrypt 3.5.7 <http://mailcrypt.sourceforge.net/> iD8DBQE+UVYGOyltUcwYWjsRAja7AJ46UKLSz33T4M2CN8jGKx0x4xvt1ACeK+IQ w7JtaO5Cwcbuzt0p33r/KHI= =2YQD -----END PGP SIGNATURE-----
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC