[prev in list] [next in list] [prev in thread] [next in thread] 

List:       sqwebmail
Subject:    [sqwebmail] flowed format (was Re: [sqwebmail] Re: content encoding etc.
From:       Hatuka*nezumi - IKEDA Soji <nezumi () jca ! apc ! org>
Date:       2004-05-19 3:03:59
Message-ID: 20040519120359.086fb50d.nezumi () jca ! apc ! org
[Download RAW message or body]

On Tue, 18 May 2004 07:07:54 -0400
Sam Varshavchik <mrsam@courier-mta.com> wrote:

> > What exactly is the issue with flowed text and East Asian character
> > sets?

Reinke Bonte <rbonte@choicenet.ne.jp> wrote:

> East Asian languages don't use spaces so you can wrap after almost any
> character (there are defined exceptions, which are different per
> language).

However RFC2646 expects that a `soft line break' is shown as a 
word separator (i.e. space).  As a result, some characters will 
be splitted by word separators when the text is shown.  
(Some non-East-Asian languages with some scripts also don't use word 
separators like Latin languages do.)

On the other hand, a long paragraph not containing any spaces
(which often appears in text of non-word-sparator languges/scripts) 
will be encoded to one long line.  Some low-capable MUAs given 
such a long line can crash.

                                 *

Note that some languages can be written by more than one script 
and vice versa.  In such cases some language(s)/script(s) can 
require word-separating and the other(s) can not allow it.

In short, I tried to determin language-script combinations by 
charset names.


  --- nezumi
[prev in list] [next in list] [prev in thread] [next in thread]