From: "Eren Türkay" <eren@hambedded.org>
To: openembedded-devel <openembedded-devel@lists.openembedded.org>
Subject: UTF-8 Encoding Problem in List Archives
Date: Wed, 4 Sep 2013 10:53:04 +0200 [thread overview]
Message-ID: <20130904085304.GA94916@airo.local> (raw)
[-- Attachment #1: Type: text/plain, Size: 688 bytes --]
Hello,
I noticed that commit e-mails in openembedded-commits list archives do
not have UTF-8 support for headers. Although the patch e-mail contains
charset="utf-8", the archive subject is not human-readable, which makes
my name (probably others) unreadable.
Please look at the end of the page below:
http://lists.openembedded.org/pipermail/openembedded-commits/2013-September/thread.html
It seems that this is a mailman encoding problem.
Of course, I can use ASCII characters only in my name. However, it is
2013 and the world should have fixed these kind of problems long ago :)
Regards,
Eren
--
. 73! DE TA1AET
http://linkedin.com/in/erenturkay
[-- Attachment #2: Type: application/pgp-signature, Size: 850 bytes --]
reply other threads:[~2013-09-04 8:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20130904085304.GA94916@airo.local \
--to=eren@hambedded.org \
--cc=openembedded-devel@lists.openembedded.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.