Re: report on [bad] status of i18n of gnome apps - somebody should
- From: Vlad Harchev <hvv hippo ru>
- To: evolution-hackers helixcode com
- Cc: Not Zed <notzed ximian com>, Jeffrey Stedfast <fejj ximian com>,Ettore Perazzoli <ettore ximian com>, gnome-hackers gnome org,gnome-i18n gnome org, gnome-devel-list gnome org
- Subject: Re: report on [bad] status of i18n of gnome apps - somebody should
- Date: Mon, 26 Mar 2001 11:58:23 +0500 (SAMST)
On Sun, 25 Mar 2001, Alan Cox wrote:
> > > displays underscores for chars > 127 in subject AFAIR, so please fix
> > > this - that's the most fatal flaw so far that makes it unusable even if it's
> > > used only for reading mails (i.e. if not caring about encodings the messages
> > > are sent with Evo are in)!
> >
> > I'm sorry, but those mailers are totally broken, end of story.
>
> Welcome to the real world. There are two conventions in use
> #1 putting the type into the subject header
> #2 assuming the message encoding
>
> If you don't support these your mailer is junk. Quite possibly perfectly
> gloriously RFC correct, but still junk
Yes, exactly. All russian mail sent with OE will be unreadable if raw text
in headers was unsupported.
Solution is to assume that if header is raw 8bit, assume it has the encoding
of body. This also applies to From:, To: and all other mail headers beside
Subject:.
Interpreting raw headers doesn't break anything (except probably
incompatibility with RFCs) - so please implement it. Feel free to encode
headers in QP when sending of course (but it would be very handy to allow user
to select the transfer-encoding of headers too - to support using broken SMS
gateways or pagers).
Best regards,
-Vlad
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]