Re: [email Tutorial] Create your own and free of charge email Network in less than 10 minutes
Stefan Claas <[email protected]>
| Newsgroups | alt.cypherpunks,alt.privacy,alt.privacy.anon-server |
|---|---|
| Organization | i2pn2 (i2pn.org) |
| Message-ID | <[email protected]> |
Fritz Wuehler wrote: > In article <[email protected]> > Stefan Claas <[email protected]> wrote: > > Fritz Wuehler wrote: > > > In article <[email protected]> > > > Anonymous <[email protected]> wrote: > > > > Stefan Claas wrote: > > > > > > > > As you see, no MIME headers for international characters are needed. > > > > > > That kind of MIME-free magic is beyond a Taiwanese who's used to use a > > > Big5 character set, and me. So it looks as if generations of Internet > > > programmers were wrong thinking MIME encoding is of any importance. > > > > > > Or does Class once again demonstrate his own incompetence in dealing > > > with MIME encoding by idealizing homebrew ASCII-only crippleware? > > > > Do us all a favor and test it by yourself. > > No. As we're not only interested in your success, but even more in the > reason why it works you'd better do us all a favour and explain how the > recipient of a two byte message knows that those aren't two ASCII > characters but instead it's one of the more that 13 thousand Chinese > characters from the 2-byte Big5 character table. Please enlighten us! > UTF-8 is the default for modern protocols (HTTP, JSON, etc.). Go assumes UTF-8 unless told otherwise (e.g., []byte → string). Big5 vs. UTF-8: Big5 needs external context (e.g., "this is Big5") to avoid ambiguity with ASCII. UTF-8 embeds the context in the byte patterns. Regards Stefan