9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Mathieu Lonjaret" <lejatorn@gmail.com>
To: 9fans@9fans.net
Subject: Re: [9fans] char encoding problem
Date: Mon, 14 Jul 2008 19:17:59 +0200	[thread overview]
Message-ID: <e7ef847fb62639c72e74b073bd122e1b@smgl.fr.eu.org> (raw)
In-Reply-To: <20080714163031.DDC181E8C45@holo.morphisms.net>

[-- Attachment #1: Type: text/plain, Size: 406 bytes --]

% 9p read mail/mbox/40/raw |grep -i '^content'
Content-Type: text/plain; charset=
Content-Transfer-Encoding: 8bit

Does it mean that the character set is in iso-8859-15 but the sender
of the message somehow set it wrongly in the headers to be iso-8859-1?
Hence mailfs is failing at trying to convert it from iso-8859-1 to utf-8
because it trusts what's written in the headers?

Thanks,
Mathieu.

[-- Attachment #2: Type: message/rfc822, Size: 3617 bytes --]

From: "Russ Cox" <rsc@swtch.com>
To: 9fans@9fans.net
Subject: Re: [9fans] char encoding problem
Date: Mon, 14 Jul 2008 12:31:56 -0400
Message-ID: <20080714163031.DDC181E8C45@holo.morphisms.net>

> I have a problem with one specific e-mail in p9p acme Mail: only some
> part of it is displayed (~1/2) when I open it (right click) in acme
> Mail. According to mutt, the encoding is iso-8859-15 and I can read it
> fine there.
> There does not seem to be anything special in the first line which is
> "not there" in acme Mail; some accented characters but not different
> from other ones which appear sooner in the mail.

acme couldn't care less.
mailfs is converting the message to utf-8
(or not) according to the content headers.

9p read mail/mbox/40/raw |grep -i '^content'
might tell something useful,
like what character set the message
is claiming to be in.

russ


  reply	other threads:[~2008-07-14 17:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-11 15:55 Mathieu Lonjaret
2008-07-11 15:56 ` andrey mirtchovski
2008-07-11 19:35   ` Mathieu Lonjaret
2008-07-11 19:54     ` erik quanstrom
2008-07-14 16:31 ` Russ Cox
2008-07-14 17:17   ` Mathieu Lonjaret [this message]
2008-07-14 18:38     ` erik quanstrom

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=e7ef847fb62639c72e74b073bd122e1b@smgl.fr.eu.org \
    --to=lejatorn@gmail.com \
    --cc=9fans@9fans.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).