[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: DOCBOOK: Re: Which attribute to use for context-sensitive help?
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 / Tom.Slee@sybase.com was heard to say: | There are a few problems with that approach. | | One is that the developers supply the context ID. We have experimented | before with both (a) the writers writing material first, and supplying the | context ID (element ID attribute) to the developers, and (b) designing | conventions so the writers know what context ID the developers will choose. | In the end, however, the extra level of indirection provides a flexibility | that helps. | | I have to admit that I stumbled across another issue that answers your | question, but may also scupper the approach I was going to take. That is, | several context IDs may point to the same topic. So we may go with | maintaining an external text file of mappings in the end. Well, you can always have <sect1 id="realid" role="context1 context2 context3"> As for what attribute to use, I dunno. I suppose I'd pick one of the effectivity attributes, maybe UserLevel. For no particular reason. Be seeing you, norm - -- Norman Walsh <ndw@nwalsh.com> | Of all the preposterous http://www.oasis-open.org/docbook/ | assumptions of humanity over Chair, DocBook Technical Committee | humanity, nothing exceeds most of | the criticisms made on the habits | of the poor by the well-housed, | well-warmed, and well-fed.--Herman | Melville -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: Processed by Mailcrypt 3.5.7 <http://mailcrypt.sourceforge.net/> iD8DBQE+J1uoOyltUcwYWjsRAofXAJ996igqWTJz3odTvVO+0ehCJxk0zwCggRNG 9MnW+tNr9x+AlZhDPOuSsMo= =Ds9y -----END PGP SIGNATURE-----
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC