Ah, I see it in the rfc2629 DTD. In the <rfc> element, add a 'category=' attribute. Valid values: std|bcp|info|exp|historic. -Scott- > -----Original Message----- > From: Addison Phillips [mailto:addison.phillips at quest.com] > Sent: Wednesday, May 11, 2005 5:00 PM > To: Scott Hollenbeck; Randy Presuhn; LTRU Working Group > Subject: RE: [Ltru] Re: [psg.com #938] should introduction > allude tointendedbcp status? > > Thanks. > > Addison > > Addison P. Phillips > Globalization Architect, Quest Software > Chair, W3C Internationalization Core Working Group > > Internationalization is not a feature. > It is an architecture. > > > -----Original Message----- > > From: Scott Hollenbeck [mailto:sah at 428cobrajet.net] > > Sent: 2005?5?11? 13:54 > > To: Addison Phillips; 'Randy Presuhn'; 'LTRU Working Group' > > Subject: RE: [Ltru] Re: [psg.com #938] should introduction allude > > tointendedbcp status? > > > > > There is no way that I know of to insert this value except by > > > editing the generated document by hand. > > > > Actually, I believe it *is* doable with xml2rfc. I don't > have access > > to my references to confirm my suspicion, but I can check in the > > morning. > > > > -Scott- > > > _______________________________________________ Ltru mailing list Ltru at lists.ietf.org https://www1.ietf.org/mailman/listinfo/ltru
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.