From: Keutgen, Walter (walter.keutgen@be.unisys.com)
Date: Tue Mar 28 2006 - 10:08:40 CST
Nick,
ftp://ftp.rfc-editor.org/in-notes/rfc2152.txt.
As I read this text:
There are 2 encoding rules
Rule 1 is for characters in 'Set D' and sometimes ('optionally') 'Set 0'
Rule 2 is for other characters ('Unicode characters') and Set 0 when rule 1 cannot be applied.
Rule 2 specifies the following stages:
1) Unicode UTF-16 Big Endian
2) Transform the corresponding bytes by the
'Base64 content transfer encoding algorithm as defined in RFC 2045, modified to
omit the "=" pad character...'
There are some examples. Try the rules on the examples.
Best regards
Walter
THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers.
-----Original Message-----
From: unicode-bounce@unicode.org [mailto:unicode-bounce@unicode.org] On Behalf Of Kornkreismuster@web.de
Sent: Dienstag, den 28. März 2006 17:08
To: unicode@unicode.org
Subject: UTF-7 - I'm not really smarter
Hi!
I read the RFC 2152 and I don't understand, wheter this UTF-7 encodes another encoding such as UTF-8 or does encode the Unicode codecharts directly.
Reading this RFC, I got the feeling it only encodes UTF-16 encoded Texts, but I think that's not true.
Regards,
Nick Jenzowsky
__________________________________________________________________________
Erweitern Sie FreeMail zu einem noch leistungsstärkeren E-Mail-Postfach!
Mehr Infos unter http://freemail.web.de/home/landingpad/?mc=021131
This archive was generated by hypermail 2.1.5 : Tue Mar 28 2006 - 10:10:48 CST