On Tue, 13 May 1997, Unicode Discussion wrote:
> Does this mean that new applications should refrain from using LF and CR
> and use the two new control characters instead? How many Unicode
> applications currently understand the Unicode line and paragraph
It is a very good idea to have a line and paragraph separator in
Unicode. But I expect that due to compatibility issues, the old
conventions (CR/LF/CRLF) will be used for a rather long time,
even after UNicode has gained much popularity.
> As for future Unicode apps what about Unicode supporting e-mail apps?
> Will the upcoming Netscape Communicator (most popular commercial Unicode
> capable e-mail client I can think of) send e-mail (and understand) with
> the new markers (providing they're Unicode encoded, of course).
> (targeted towards the Netscape/Unicode group)
Email has very strict restrictions on this. You can't send doublebyte
UTF-16 or UCS-2 in Email. CRLF always has to be present as a line
separator. Unicode in Email is possible with UTF-7 (and CRLF as line
separator) or UTF-8 + BASE64/QuotedPrintable (and CRLF...).
Please see RFC 2045/6/7 for this.
This archive was generated by hypermail 2.1.2 : Tue Jul 10 2001 - 17:20:34 EDT