[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: Need switch to control xref linkend attr type (Re: DOCBOOK: notes androles)
>From: "G.L. Grobe" <gary@grobe.net> >To: docbook@lists.oasis-open.org >Subject: DOCBOOK: notes and roles >Date: Mon, 02 Sep 2002 01:55:12 -0500 > >What tag can be used to make something a future reference, or to let >the reader know that these features are to be included in a future >release? Yo Grobe! (Sorry, couldn't help myself) A co-worker recently complained to me about this very thing! "I want to put an xref, but I don't yet have anything for it to point at". He wanted to have some sort of means by which to disable the declarative referential integrity checking functionality supplied by the linkend attribute's IDREF type. I thought this was a horrible idea, until I realized that there could simply be a parameter entity used for this attribute type. In draft-mode, the document could find some means to override it to 'NMTOKEN', while it could revert to the standard 'IDREF' value, otherwise. Of course, the stylesheets would have to do something sensible, in such cases. At least I know how to do it - and knowing is half the battle. :) Shall I submit a RFE? Matt _________________________________________________________________ Send and receive Hotmail on your mobile device: http://mobile.msn.com
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC