> to render XML documents to pure text presentation.  There will be
>                                                             ^^^^^^^
> > converters from XML to HTML, ms word, ps, pdf and any other types of
> > presentation, suitable for any type of readers.
> 
> Meanwhile I stick with ASCII, which I can grep, cut & paste.
> 
1. You can easily get a very well-formed ASCII file from a XML file.
2. With XML, you can not only grep, cut & paste, but also manage and process it.

For example, I can grep XML files for whose level 2 headings containing 
the string 'file transfer protocol'.  But for ASCII files, this is impossible, because 
1) the computer program does not know where are level 2 headings
2) the string may be split into two lines, grep fails in this situation.

> Also I don't think it will be at all practical to drive email
> discussions
> for ietf drafts if we have to start using XML/HTML/SGML/*ML crap.
>  
> > BTW, there are RFCs (1125, 1129, etc.) only available in ps format, and some
> > provided both text and ps versions.  ASCII text is not enough to describe
> > information.
> 
> Well it worked fine for 2800+ documents and how many today ?
3060+ today, with many ugly figures in '-', '_', 'o', '/', '\' chars, which
is very difficult to read.  In XML, you can even search for figures if 
we develop unified Internet/flowchart/etc DTDs.

> implementations
> of tcp/ip protocols running on how many devices ?
> 
> > I wonder if anyone can write a readable pure text version of ITU-T P.861.
> 
> What P.861 {Objective quality measurement of telephone-band (300-3400 Hz) 
> speech codecs} has to do with tcp/ip and rfc's ???
> 
Yes, their content of P.861 seems have nothing to do with RFCs.  
P.861 is an informational document, like any RFCs.  If a RFC face a 
similar problem like P.861, I wonder how it can describe it clearly in 
pure text.

XML provides a way to describe information in documents, and can be 
easily converted to different types of target formats, such as pure text,
pdf, HTML, etc.   Again: XML is not for display.

> BTW, I hate to pay for ITU documents what are supposed to be public (I
> still
> remember the years old discussion when they ceased to exist available
> for anon ftp)

I hate ITU too. :)

> 
> Regards
> Jorge.
> 
> 
Regards,
Wang Xianzhu


Reply via email to