![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
> At present, RFCs can be supplied in either ASCII only, or in both > ASCII and Postscript format.... My own preference is to follow direction pointed out by Marshall Rose in "Writing I-Ds and RFCs using XML" RFC2629. It provides semantic labelling of the parts of the document, thus making it better material for more next-generation search engines. Plus it can be readily converted to either raw ascii or HTML and thus has a degree of output device independence. And it's still in ascii (actually UTF-8) that one can read by eye if necessary, digitally sign (once folks settle on a standard method), and "grep". Yes, drawings and graphics would still be an nuisance. --karl--
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.