-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 11/27/2011 11:20 AM, Marc Petit-Huguenin wrote: > On 11/27/2011 10:36 AM, John C Klensin wrote: > > >> --On Sunday, November 27, 2011 08:20 -0800 Marc Petit-Huguenin >> <petithug@xxxxxxx> wrote: > >>> The problem here is that RFC and Internet-Drafts are not plain >>> ASCII. They are technically in a special format that I would >>> call "line-printer ready text file", and ASCII is the >>> encoding, not the format. What is needed is: >>> >>> - - A mime-type for line-printer ready text (say text/lp) >>> - - An heuristic to recognize text/lp files (it's too late for >>> a specific extension). Apache HTTP server can use the AddType >>> directive for these files[1]. - - A program to display text/lp >>> files, one at least for each platform. If someone take care >>> of the mime-type, I'll write the program to display correctly >>> text/lp files on the Android platform. > >> Out of curiosity (and again my better judgment about getting >> further involved in this discussion), why do you think > >> text/lp >> is needed and not >> text/plain; charset="US-ASCII"; format=lp" >> ? > > Did not think of that, that's better IMO. Apache can do this (the link I gave > in a previous email is now returning "text/plain; format=lp; charset=us-ascii"). http://ietf.implementers.org/mime/rfc5928.txt now returns text/lp http://ietf.implementers.org/format/rfc5928.txt now returns text/plain;format=lp - -- Marc Petit-Huguenin Personal email: marc@xxxxxxxxxxxxxxxxxx Professional email: petithug@xxxxxxx Blog: http://blog.marc.petit-huguenin.org -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iEYEARECAAYFAk7SjvwACgkQ9RoMZyVa61dwmQCaAhj6WDUNR3Zvv04jSA2Xs65y 2LcAn3vLq1/LOUxyfTCpkHzPKvHfj42f =ba/+ -----END PGP SIGNATURE----- _______________________________________________ Ietf mailing list Ietf@xxxxxxxx https://www.ietf.org/mailman/listinfo/ietf