Gnus development mailing list
 help / color / mirror / Atom feed
* content-transfer-encoding
@ 2001-01-09 10:37 vvv
  0 siblings, 0 replies; 11+ messages in thread
From: vvv @ 2001-01-09 10:37 UTC (permalink / raw)


[-- Attachment #1: Type: text/plain, Size: 1384 bytes --]

Hi,

rfc2045 has the following requirement:

 RFC> It should also be noted that, by definition, if a composite entity                                                           
 RFC> has a transfer-encoding value such as "7bit", but one of the enclosed                                                        
 RFC> entities has a less restrictive value such as "8bit", then either the                                                        
 RFC> outer "7bit" labelling is in error, because 8bit data are included,                                                          
 RFC> or the inner "8bit" labelling placed an unnecessarily high demand on                                                         
 RFC> the transport system because the actual included data were actually                                                          
 RFC> 7bit-safe.                                                                                                                   

but when gnus sends a multipart messages, it does not set the
content-transfer-encoding=8bit of the whole message when one of the
parts has 8bit (or content-transfer-encoding=binary when one of the
parts has binary CTE).

by default, the CTE, if omitted, is assumed to be 7bit (as stated in
the same RFC).

This message has a part with 8bit CTE, but gnus does not set the 8bit
CTE for the whole message.

Best,
v.

[-- Attachment #2: Type: text/plain, Size: 37 bytes --]

this part has a 8bit CTE:
проба пера

^ permalink raw reply	[flat|nested] 11+ messages in thread
* Content-Transfer-Encoding
@ 2000-01-13 10:23 Shigeki Uno
  2000-01-13 11:14 ` Content-Transfer-Encoding Katsumi Yamaoka
  0 siblings, 1 reply; 11+ messages in thread
From: Shigeki Uno @ 2000-01-13 10:23 UTC (permalink / raw)


Hello.

I write a e-mail message in Japanese and send it as usual,
so "Content-Transfer-Encoding" line in header shows *quoted-printable*.
But some japanese can't read this *quoted-printable* encoded messages.

Following is the example I send to myself:
-----start of headers----- 
To: Shigeki Uno <shigeki@mediawars.ne.jp>
Subject: test 
From: Shigeki Uno <shigeki@mediawars.ne.jp> 
Date: 13 Jan 2000 18:29:33 +0900 
User-Agent: Gnus/5.0804 (Gnus v5.8.4) Emacs/20.5
Message-ID: <86hfgitj42.fsf@mediawars.ne.jp> 
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-2022-jp
Content-Transfer-Encoding: quoted-printable <-------- HERE 

Here is sentences written in japanese...

-----end of headers-----

I want to encode messages "7bit" type automatically. 
How do I do that ?

Thanks.
-- 
Shigeki Uno <mailto:shigeki@mediawars.ne.jp>



^ permalink raw reply	[flat|nested] 11+ messages in thread
end of thread, other threads:[~2001-01-09 10:37 UTC | newest]

Thread overview: 11+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2001-01-09 10:37 content-transfer-encoding vvv
  -- strict thread matches above, loose matches on Subject: below --
2000-01-13 10:23 Content-Transfer-Encoding Shigeki Uno
2000-01-13 11:14 ` Content-Transfer-Encoding Katsumi Yamaoka
2000-01-13 17:02   ` Content-Transfer-Encoding Shigeki Uno
2000-01-13 23:52     ` Content-Transfer-Encoding Katsumi Yamaoka
2000-01-14 18:18       ` Content-Transfer-Encoding Shigeki Uno
2000-04-21 13:22       ` Content-Transfer-Encoding Lars Magne Ingebrigtsen
2000-04-21 19:24         ` Content-Transfer-Encoding Pavel Janik ml.
2000-04-22  0:16           ` Content-Transfer-Encoding Lars Magne Ingebrigtsen
2000-04-22  8:43             ` Content-Transfer-Encoding Pavel Janik ml.
2000-04-22 12:28               ` Content-Transfer-Encoding Lars Magne Ingebrigtsen

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).