Gnus development mailing list
 help / color / mirror / Atom feed
From: Toby Speight <Toby.Speight@streapadair.freeserve.co.uk>
Subject: Re: Does Gnus UTF-7?
Date: 21 Jul 1999 14:30:49 +0100	[thread overview]
Message-ID: <uhfmyqgdy.fsf@lanber.cam.citrix.com> (raw)
In-Reply-To: andreas.koenig@anima.de's message of "21 Jul 1999 15:14:01 +0200"

Andreas> Andreas J. Koenig <URL:mailto:andreas.koenig@anima.de>

[please respect the Mail-Copies-To header]


0> In <URL:news:sfcvhbegvnf.fsf@andreas.in-berlin.de>, Andreas wrote:

Andreas> X-Mailer: Mozilla 4.04 [en] (WinNT; I)
Andreas> Subject: =?x-UNICODE-2-0-UTF-7?B?QUdST0ItR2VsK08yUS1l?=

>>>>> On 21 Jul 1999 12:25:09 +0100, Toby Speight
>>>>> <Toby.Speight@streapadair.freeserve.co.uk> said:
>>
>> You've gotta laugh.  Base-64 encoding UTF-7?!

0> In article <sfcn1wqgn6u.fsf@andreas.in-berlin.de>, Andreas wrote:

Andreas> That's a valid word according to RFC 2047 (MIME Part Three:
Andreas> Message Header Extensions for Non-ASCII Text).

Yes, I'm aware.  It just seems wasteful for NS to write the above when
=?x-UNICODE-2-0-UTF-7?Q?AGROB-Gel+O2Q-e?= is less bloated.  It's just
*weird* to base64-encode something which is 7-bit-clean (as UTF-7 is).


Andreas> Trying to translate the UTF-7-string to latin isn't possible,
Andreas> but this wasn't my point. I was mainly interested if UTF-7
Andreas> support is there.

Sorry, I wasn't trying to answer your question (I don't know whether
we support UTF-7, but I believe we ought to).  I was just diving down
a side-track.



  reply	other threads:[~1999-07-21 13:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-07-21 10:11 Andreas J. Koenig
1999-07-21 11:25 ` Toby Speight
1999-07-21 13:14   ` Andreas J. Koenig
1999-07-21 13:30     ` Toby Speight [this message]
1999-07-21 16:30       ` Toby Speight
1999-07-22 10:11     ` Hrvoje Niksic
1999-08-02 12:15 ` Jon K Hellan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=uhfmyqgdy.fsf@lanber.cam.citrix.com \
    --to=toby.speight@streapadair.freeserve.co.uk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).