From: einars@gmail.com (Einars Lielmanis)
Subject: [sup-talk] UTF-8 woes
Date: Thu, 22 Jan 2009 08:02:24 +0200 [thread overview]
Message-ID: <1232602097-sup-3993@traj> (raw)
Sup is awesome! Good job, William! :-)
Yet, when using it for one day, some minor and less minor suckiness
and breakage in regard of non-english mails emerged as my recipients
started complaining about broken emails. I'm using sup/git under
64-bit arch linux with msmtp for sending, so maybe it would be better
with something sendmail-ish, have no idea, but still:
1. the subject with non-english (e.g, latvian accented) chars gets no
special treatment and safe encoding, and as such gets broken somewhere
on the wire,
2. something about the message text, probably missing
"Content-Transfer-Encoding: 8bit" makes my emails with latvian
characters explode with ugliness for my poor recipients on Outlook;
3. The minor glitch that the Sup's display is slightly messed up, if
the message contains multi-byte characters in headers -- fixed either
very nicely by extending String with length_utf8 (and substr_utf8, and
others as needed) function, and replacing s.length with s.length_utf8
in lib/sup/buffer.rb or by going the ugly way of assuming that all
strings are and will be utf-8 and dropping a horrendous monkeypatch
into the lib/sup/util.rb with
class String
+ def length
+ self.scan(/./u).size
+ end
To see what exactly is wrong with the sending of mails I compared of
how the same mail is sent by mutt and how -- by sup. You can see the
mails here: http://spicausis.lv/sup/ where mail-mutt.txt is good,
mail-sup.txt is bad.
My ruby skills are non-existant yet, but I guess I'll try to whip up
patches for these things today, if somebody with more ruby and sup and
mta shizzle don't beat me to that.
Cheers,
Einar Lielmanis
next reply other threads:[~2009-01-22 6:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-22 6:02 Einars Lielmanis [this message]
2009-01-22 16:16 ` Tyberius Prime
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=1232602097-sup-3993@traj \
--to=einars@gmail.com \
/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