On Nov 19, 2007, at 3:02 AM, Julian Reschke wrote: > Maciej Stachowiak wrote: >> ... >>> But not with things like InputStreamReader, right? So sorry, I >>> still believe that the requirement to support single CRs >>> introduces completely useless complexity. (As the introduction of >>> a new text-based format anyway.) >> For browser-hosted implementations, it's easier if newline rules >> are consistent between different text-based formats. This argues >> for allowing CR in this format. >> ... > > I simply don't buy that this is sufficient reason to violate the > base RFC. This is a new MIME type, not text/html. If you don't want > to obey the text/* rules, use application/*. (for instance, that was > done for the Relax NG Compact format -- http://www.iana.org/assignments/media-types/application/relax-ng-compact-syntax) > . Aren't RFCs supposed to be based on "rough consensus and running code"? It seems like the running code out there for handling text/* MIME types on the web allows CR. Sounds to me like the RFC needs fixing. Regards, MaciejReceived on Monday, 19 November 2007 11:38:35 UTC
This archive was generated by hypermail 2.4.0 : Saturday, 9 October 2021 18:44:24 UTC