Groups | Search | Server Info | Login | Register

Groups > comp.mail.mime > #23

Content-Transfer-Encoding: vs. Usenet

Cross-posted to 3 groups.

Followups directed to: news.software.readers, comp.mail.mime

Show all headers | View raw

>>>>> Adam H Kerman <ahk@chinet.com> writes:

	[Cross-posting to news:news.software.readers and setting
	Followup-To: there.  Adding news:comp.mail.mime, on a second
	though.]

[...]

 > In any event, I agree with Ben and continue my boycott of MIME on
 > Usenet, not that anyone cares.

	Personally, I don't care about non-MIME articles, as long as
	they're pure-ASCII.  The only issues with forgoing MIME
	completely I'm aware of are:

	* pure-ASCII is simply not enough for the majority (90% or so)
	  of the world population; (this isn't a problem should Usenet
	  be though of as a kind of pure-English sect; but it isn't);

	* use a non-compliant newsreader to quote MIME-compliant
	  messages, and havoc will ensue.

 > The syntax of the CTE header, which is used to indicate a type of
 > unencoded data

	Is it?

 > OR a mechanism of encoding, is ungrammatical to my ear.

-- 
FSF associate member #7257

Back to comp.mail.mime | Previous | Next — Next in thread | Find similar

Thread

Content-Transfer-Encoding: vs. Usenet Ivan Shmakov <oneingray@gmail.com> - 2013-07-25 15:19 +0000
  Re: Content-Transfer-Encoding: vs. Usenet Ivan Shmakov <oneingray@gmail.com> - 2013-07-25 19:22 +0000

csiph-web