- From: Julian Reschke <julian.reschke@gmx.de>
- Date: Sat, 10 Mar 2012 23:09:23 +0100
- To: Larry Masinter <masinter@adobe.com>
- CC: Paul Hoffman <paul.hoffman@vpnc.org>, xml2rfc list <xml2rfc@ietf.org>, "public-i18n-core@w3.org" <public-i18n-core@w3.org>
On 2012-03-10 23:00, Larry Masinter wrote: > I'm trying to solve a local problem of making the IRI internet drafts more useful, through a change to (or a pre-processor for) xml2rfc. I do not wish to open the "What formats are allowed for RFCs" can of worms, please stay completely shut. The current policy, however, allows for PDF editions of RFCs. My only question is how to best accomplish, using xml2rfc, this limited design goal. > > So no, this is *not* a discussion for rfc-interest, because I do not at all wish to change the current policy, which I think allows everything I'd like to accomplish. > > I'm *only* talking about how best to change xml2rfc to be useful in producing submissions which are consistent with existing policy. > > Larry You could just use rfc2629.xslt and rfc2629toFop.xslt, which should work fine with non-ASCII characters. For "down-conversion" to the all-ASCII format we'd need a simple XSLT that strips or converts the examples. (Stripping will be easier :-) Best regards, Julian
Received on Saturday, 10 March 2012 22:09:57 UTC